Mapping Cyclic IO Words Between SIMOCODE pro V and PCS 7 Driver Blocks
In SIMATIC PCS 7, cyclic data exchange between SIMOCODE pro V and driver blocks (such as FbSwt or the dedicated SIMOCODE PCS 7 Library blocks) maps directly to the process data (PZD) words configured in HW Config. PZDIN1 connects to the starting peripheral input word (e.g., IW 512), transmitting SIMOCODE Status Word 1 (STW1), while PZDIN2 receives motor current (% of Is) or Status Word 2. PZDOUT1 connects to the starting peripheral output word (e.g., QW 512), transmitting Control Word 1 (CTW1) for start, stop, and reset commands.
Table of Contents
- Cyclic Telegram Structure of SIMOCODE pro V
- Interconnection Architecture with PCS 7 Driver Blocks
- Verification
- Limitations and Operational Precautions
- Engineer FAQ
- Technical References
- Related Articles
- Related Tags
Cyclic Telegram Structure of SIMOCODE pro V
SIMOCODE pro V motor management devices communicate with SIMATIC S7-400 and S7-410 controllers over PROFIBUS DP or PROFINET IO using cyclic Process Data (PZD) words.
In the SIMOCODE ES hardware parameterization, the cyclic send and receive buffers are structured as follows:
* Cyclic Send (Device to AS / Inputs):
* Send Byte 0 & 1 (PZDIN1 / Word 1): Status Word 1 (STW1). Transmits fundamental operating states: Ready, Running Forward, Running Reverse, Overload Warning, Fault Summary, and Local/Remote status.
* Send Byte 2 & 3 (PZDIN2 / Word 2): Analog Process Value. By default, maps to motor current expressed as a percentage of nominal motor current (0 to 1000% of Is), or Status Word 2.
* Cyclic Receive (AS to Device / Outputs):
* Receive Byte 0 & 1 (PZDOUT1 / Word 1): Control Word 1 (CTW1). Receives command bits from the automation program: Start Forward, Start Reverse, Stop, and Fault Reset.
* Receive Byte 2 & 3 (PZDOUT2 / Word 2): Secondary control parameters or analog setpoints (e.g., soft starter ramp times).
Interconnection Architecture with PCS 7 Driver Blocks
In SIMATIC PCS 7 CFC charts, communication drivers (such as FbSwt or MMStat / MMDrv from the official SIMOCODE PCS 7 Library) bridge hardware I/O addresses to technological motor blocks (MotL, MotRevL):
- HW Config Peripheral Base Address:
* When inserting the SIMOCODE pro V object on the DP or PN bus in HW Config, Step 7 assigns a starting address (for example, InputIW 512and OutputQW 512). - CFC Pin Interconnections:
*PZDIN1: Must be interconnected directly to the starting input addressIW 512. This supplies Status Word 1 directly to the block algorithm.
*PZDIN2: Connects to the second input wordIW 514. This supplies the motor current to the channel driver, which scales it into engineering amperes for faceplate display.
*PZDOUT1: Connects to the starting peripheral output wordQW 512, writingCTW1commands to the SIMOCODE field unit. - Module Driver Generator Integration:
* When compiling CFC with Generate module drivers, the compiler links diagnostic outputs (oMode_xx,DataXchg) to upstream diagnostic blocks (MOD_SWT), automating health tracking.
Verification
- In SIMATIC CFC, open the chart containing the driver block in dynamic test mode.
- Verify that
PZDIN1reflects active hex bitmasks (e.g.,16#0001for Ready). - In SIMOCODE ES, trigger a local motor jog. Verify that
PZDIN2dynamically registers current flow and displays motor load on the PCS 7 faceplate. - Issue a Start command from the PCS 7 OS motor faceplate. Verify that
PZDOUT1transmits the start bit and the physical SIMOCODE contactor pulls in immediately.
Limitations and Operational Precautions
- If customized cyclic send/receive tables are defined in SIMOCODE ES, the bit definitions must strictly match the expectations of the PCS 7 driver block; altering default PZD mappings without modifying driver block types causes command inversions.
- Ensure that the SIMOCODE device parameter "Control Stations" is configured to accept PLC commands (Remote Mode) when commanded by
PZDOUT1. - When using PROFINET SIMOCODE devices, configure PROFINET device names and IP addresses correctly before attempting cyclic PZD communication.
Engineer FAQ
- Can I use standard APL blocks with SIMOCODE pro V?
Yes. Standard APLMotLcan control SIMOCODE using standard channel drivers (Pcs7DiIn,Pcs7DiOu,Pcs7AnIn) or through the dedicated Siemens SIMOCODE pro PCS 7 Library. - Why does PZDIN2 show 1000 when the motor is running?
SIMOCODE transmits current as a permille value (0.1% per count). A raw value of1000indicates exactly 100.0% of nominal motor current (Is). - What happens if PZDIN1 is connected to IW 514 instead of IW 512?
The driver block will interpret raw motor current as status bitflags, resulting in random, erratic tripping and false status indications on the OS.
Technical References
- SIMOCODE pro PCS 7 Function Block Library Manual (A5E41356295-AA).
- SIMOCODE pro System Manual: Parameterization and Cyclic Communication.
- Siemens Industry Online Support Entry ID 109801081: Integrating SIMOCODE pro V into SIMATIC PCS 7.
Related Articles
- Configuring SIMOCODE pro V with PROFINET System Redundancy (S2) in PCS 7.
- Handling Thermal Overload and Thermistor Faults in SIMOCODE Motor Management.
Related Tags
PCS 7, SIMOCODE, PROFIBUS, PROFINET, Motor Management, PZD, Hardware Config, Driver Blocks