Map settings
Select the To Controller tab or the From Controller tab.
Select Add.
The Create signal configuration dialog window opens.
Select the item name in the list to select the item.
Set the item starting position by typing the Byte number in which the least significant Bit should be located.
Set the item starting position by typing the Bit in which the least significant Bit should be located.
Set the Length of the item, expressed in number of bits.
Select Add.
Repeat the above steps for every item to be added.
Opening parameter configuration
Double click a parameter to open the configuration. Or select the check box 
for the item and then select OPEN.
Deleting parameter configuration
Select the check box
for the item.To select multi items, press Ctrl on your keyboard and select.
Select DELETE or press Delete on your keyboard.
Moving parameters
It is possible to move parameters by using drag-and-drop in the fieldbus map. The place where the parameter is dropped to indicates the starting position of the parameter.
If a parameter is 1 (or more) bytes then regardless of in which bit position the parameter is dropped it will adjust the starting position to bit 0.
If parameters are overlapped, the parameters will be marked red in both tables.
If an error in the parameter list happened, that error must be solved before being able to save. It is not possible to generate more errors if an error already is in place. That conflict must first be solved.
Data format
General data format description for parameters used in map settings.
Data type (ToolsTalk MT) | Data length (bits) | Data representation | Byte order |
|---|---|---|---|
Boolean | 1 | EtherCAT: 1 BIT PROFINET: 1 bit within an UNSIGNED8 (Generic data module) EtherNet/IP: 1 bit within a BYTE | - |
Boolean | 8 | Array of 8 Booleans EtherCAT: BITARR8 PROFINET: UNSIGNED8 EtherNet/IP: BYTE | - |
Unsigned | 8 | Unsigned Integer, 8 bits (UNSIGNED8, USINT) | - |
Unsigned | 16 | Unsigned Integer, 16 bits (UNSIGNED16, UINT) | EtherCAT/EtherNet/IP: Little-endian (LSB first) PROFINET: Big-endian (MSB first) |
Unsigned | 32 | Unsigned Integer, 32 bits (UNSIGNED32, UDINT) | EtherCAT/EtherNet/IP: Little-endian (LSB first) PROFINET: Big-endian (MSB first) |
Integer | 8 | Signed Integer, 8 bits (INTEGER8, SINT) | - |
Integer | 16 | Signed Integer, 16 bits (INTEGER16, INT) | EtherCAT/EtherNet/IP: Little-endian (LSB first) PROFINET: Big-endian (MSB first) |
Integer | 32 | Signed Integer, 32 bits (INTEGER32, DINT) | EtherCAT/EtherNet/IP: Little-endian (LSB first) PROFINET: Big-endian (MSB first) |
Float | 32 | Floating point number, 32 bits (FLOAT32, REAL) IEEE 754 single precision binary floating point format; 1 sign bit, 8 exponent bits, 23 fractional bits, s eeeeeeee fffffff ffffffff fffffffff | EtherCAT/EtherNet/IP: Little-endian (LSB first) PROFINET: Big-endian (MSB first) |
String | 1..n | UTF-8 encoded string within an array of predefined size (nr of bytes). EtherCAT: UNSIGNED8 array PROFINET: UNSIGNED8 array EtherNet/IP: BYTE array | - |
See Fieldbus Parameter Specification in References for detailed description of available parameters.
PLC configuration (PROFINET)
The module configuration in PLC must match the MTF6000 parameter configuration. Consider the following if the module configuration is done manually in PLC:
All To controller parameters (Output on PLC) must be configured before any From controller parameters (Input on PLC).
Any byte consisting of single bit parameter(s) (Length = 1) must be configured with Generic data module on the PLC. Single bit modules are not supported by the PROFINET protocol whereas the user must keep track of the content of any Generic data modules. Preferable use modules consisting of bit parameter groups (for example, IF 1 – IF 8) instead of single bit parameters (all single bit parameters exists also in a group parameter).
Any byte(s) that are empty in MTF6000 configuration must have Empty data module(s) in the PLC configuration. There are Empty data modules consisting of 1/2/4/8/16/32/64/128 bytes, fill the empty space with modules with as many bytes as possible first and then in decreasing size until the empty space is filled with Empty data modules. Avoid having any empty spaces within the configuration if not needed since it will decrease performance.
