Deutschmann Script language The heart of the Deutschmann UNIGATE® / Gateway series Flexible solutions are needed. With the usual configuration tools for protocol converters and gateways, the user has to work with the specifications of the manufacturer. To change this unfortunate condition Deutschmann developed its own script language as early as in 2001. The user only needs to process the data of the bus and barely has to look after the special characteristics of the fieldbus. The Protocol Developer supports a variety of functions to fit the received or to send data into the right “form”. Mathematics- or memory processing commands are known from other Script languages and are easy to understand implemented, even for laymen. The neatly arranged selection of examples enables a quick introduction to laymen. Another highlight is the included debug functionality. The common functionalities such as Single-step, running and stopping on breakpoint are available. Great emphasis is put on data security. You can activate special error detection routines on request. Since version V.3.0.0The Protocol Developer offers modern icons for the toolbar, a simplification of the configuration, an extended syntax highlighting and an auto-completion of commands. In addition, the handling of the variables has been optimized and the user experience in the debugger has been improved. What exactly is a Script? A script is a sequence of commands executed in a given order. A command is always asmall, firmly outlined task. The script language also knows commands that control theprogram flow in the script, which is why you can assemble even complex processeswith these simple commands. Protocol Developer Download The current version can be downloaded in the Download area under Software. Protocol Developer - Surface Version InfoDeclarationsCommunicationFlow ControlDevice ControlData ManipulationMathBus SpecificDivers For all Script commands we offer here at examples to download. Communication with 3964R or 3964 needs an initialization before data exchange is possible. You need to set the ReceiveBuffer and the maximum number of bytes to receive. This script demonstrates the conversion of a buffer containing an IP-address as an ASCII-String into a Long variable. This long variable could be used wherever an IP-address is necessary. Sets the given parameter to the const-value. The parameter is one of the parameters defined for this command, the value must be one of the valid values for this parameter. This command calculates a checksum with the given method for a number of bytes in the device's memory. The variable source is a buffer containing the data the checksum should be calculated for. Destination is a word variable which holds the checksum after the routine finishes with return code OK. The number of characters is a variable which holds the number of bytes the checksum should be calculated for. Checksum method defines which method should be used for calculation. This command is used for assigning the result of a mathematical or logical operation of exactly two operators to a given variable. If you like to use CAN Layer 2 we provide a mechanism to access every CAN Message without any Filter. Please note that in this case, the data format for ReadBus and Write bus differs from other functionality. From now on, we have The COB-ID of the message to be read or send in the first 2 bytes of the data area. Use this command if you like to change its data format. It is possible to convert 3 bytes ASCII to a binary word value or vice versa. All known conversion types are usable either for source and for destination, so data conversion is possible from every data representation to another. this command copies a number of bytes from a source to a destination. A Source is given by a variable identifier and an offset within the source buffer. The destination is also given by a variable identifier and the offset is given in a variable too. Copy a number of bytes from one variable to another. The number of bytes is a variable containing the number of bytes, Source and Destination are meant to be Buffer variables; it is also possible to use an ordinal variable as a byte, word or long instead. If necessary it is possible to indicate an ordinal variable. Every Script MUST have the following ObjectTable, and length MUST be: ((number of objects) + 2) * 12 If length is not correct, there will be big problems by running the script! var a_ObjectTable : buffer[48]; (2 Objects + 2) * 12 = 48 This line MUST done befor CANopen-objects will be created InitObjectTable ( 2 , a_ObjectTable[0] ) ; 2=number of objects A constant value is transfered into the memory used by the given variable. This command is used to predefine a variable with a constant value. Execution of the actual script is delayed for given time. The time is in milliseconds and can take directly values from 0 to 65535. It is not possible to hold the time in a variable. This command exchanges data with DIN 19244 routine. Sendbuffer and Receivebuffer must have a special data format. See DIN19244 specification for details. After data was sent by the gateway the routine waits for a response. Example for Script DeviceNet parameter into the EDS file and the settings of the script. This file generates an empty but valid script this script only contains information about its last compilation This script realized a script for our filedbus-fieldbus gateway where one side is CANopen This script realized a script for our filedbus-fieldbus gateway where one side is CANopen. This script realized a script for our filedbus-fieldbus gateway where one side is DeviceNet This script realized a script for our fieldbus-fieldbus gateway where one side is Ethernet This script realized a script for our filedbus-fieldbus gateway where one side is Profibus-DP This script realized a script for every filedbus-fieldbus gateway where one side is fieldbus init 2. RS interface (fieldbus) This script realized the Mod