WAGO-I/O-SYSTEM 750 CoDeSys 2.3 Runtime Environment 97758-874/000-131 WAGO-I/O-IPC-C6ManualVersion 1.0.0Table 50: Addressing exampleI/O Module Input Data Output Data DescriptionType C* FC3,FC4FC1,FC2FC6 FC5750-600End moduleThe passive 750-600 End Module does nottransmit any data.Analog input/output modulesDigital input/output modules*C: Number of the input/outputPos: 46.6 /Serie 758 (Funk, IPC und PFC)/Feldbuskommunikation/CoDeSys 758-87x - Überschrift 1 @ 10\mod_1313151338247_21.doc @ 76730 @ 1 @ 111 CoDeSys 2.3 Runtime EnvironmentPos: 46.7 /Serie 758 (Funk, IPC und PFC)/Feldbuskommunikation/CoDeSys 758-87x allgemein nur Prozessabbilder @ 10\mod_1313151036978_21.doc @ 76726 @ 233 @ 111.1 Process ImagesA process image is a memory area in which the process data is stored in a definedsequence. The process image consists of the I/O modules attached to the internalbus, the PFC variables, the bit memory address area and the slaves attached to thefieldbus.Access to the process images is different with MODBUS and CoDeSys. Forinformation about access to the process data of the I/O modules connected to theI/O-IPC and slaves, please see sections “Accessing the Process Image viaMODBUS/TCP Functions” and “Access to the Process Images of the Input andOutput Data via CoDeSys 2.3”.11.1.1 Process Image for the I/O Modules Connected to the I/O-IPCAfter the I/O-IPC is started up, it automatically detects all connected I/O modules.The I/O-IPC generates a process image from this, which is divided into an inputdata and output data area with a maximum of 500 bytes.The analog input and output data is stored first word by word in the processimage. Next, the bits of the digital input and output data are combined into wordsand stored behind the analog data in the process image.Data width of an I/O moduleThe data width of an I/O module is between 0 and 48 bytes. For detailedinformation about the respective process data width of individual I/O modules,see section "Process Data Architecture for MODBUS/TCP".
