to the EtherCAT I/O Mapping [...] to the EtherCAT I/O Mapping [...] the process data (PDO
to the data type of the I/O [...] in the I/O mapping. Name [...] of the I/O mapping
CODESYS Development System
should be mapped to the I/O [...] , data type) and has the {attribute 'io_function_block_mapping
requested state change 16 [...] , for example, data [...] sync manager types
CODESYS Development System
DeviceObject IoConfig_Globals_Mapping [...] from the persistent list to mapped [...] of visualizations with data
CODESYS Development System
<data type> ( := [...] Devices and I/O Mapping [...] type> Data Type
CommunicationSettings export_io_mappings [...] Export the io mappings [...] . import_io_mappings
on Existing” (mapping I/Os [...] . Changing the names [...] Changing the names
the object types and data [...] : 'opcua.mapping.type' , [...] of the data type. The user
AXIS_REF_MAPPING [...] _BLOCK AXIS_REF_MAPPING [...] Type Initial Comment