VM600 networking manual MAVM600-NET/E C - 7
Edition 9 - February 2018
APPENDIX C: MPC4 PROFINET SLOT DEFINITIONS
As shown above, in the extract for an MPC4 card in slot 3:
• PROFINET is enabled in the [GLOBAL] section using the IS_PROFINET_ACTIVED tag.
• MPC4 outputs are defined and organised in the [MAPPING] section, on a slot by slot
(card) basis, using $MPC4... tags.
NOTE: $MPC4... tags can use logical operators to combine status flags (bits).
• MPC4 Modbus register mapping is defined in the [MAPPING] section, on a slot by slot
(card) basis, using the Modbus register mapping syntax.
For example: 00000:3:U = Slot3:MPC4:C1:O1:V
See 9.2.4 The MAPPING section for further information.
NOTE: Modbus register mapping can use the pack command (Pack(...)) to
combine $MPC4... tags.
• PROFINET slots are defined in the [MAPPING] section, at the end of the configuration
file, using PROFINET_CREATE tags.
For example: PROFINET_CREATE SLOT3 0 36, where
• SLOT3 is the PROFINET slot ID.
The PROFINET slot ID number can correspond to the VM600 rack slot number or a
different numbering scheme can be used.
• 0 is the first Modbus register address to map to this PROFINET slot.
• 36 is the last Modbus register address to map to this PROFINET slot.
The first and last Modbus register addresses mapped to a PROFINET slot must
contain a contiguous data block.
The underlying PROFINET slot data structures are defined in a GSDML file
(see 10.5 GSDML files). The MPC4 Modbus register mapping and the PROFINET slot
definitions configured in the [MAPPING] section of the configuration file must match the data
structures defined in the GSDML file.
To Next Page
Loading...
Need help?
General
