Programming SIMODRIVE 611U on S7-315 PROFIBUS DP with SFC14 and SFC15

This field-procedure reference covers the full commissioning path for a Siemens SIMODRIVE 611 universal (611U) inverter controlled by a SIMATIC S7-315 (CPU 315-2 DP, order code 6ES7 315-2AFxx-0AB0) over PROFIBUS DP using the standard SFCs 14 (DPRD_DAT) and 15 (DPWR_DAT). The intended mode is positioning. Sample FBD and LAD code is provided with full LADDR, RECORD, and RET_VAL parameterization, plus the SIMOCOMU parameterization steps required to bring the drive online. All control word transitions (047E_h reset, 047F_h enable) are mapped, and a fault code matrix is included for commissioning troubleshooting.

1. Reference Architecture and Signal Topology

The S7-315-2 DP master communicates with the SIMODRIVE 611U control unit (typically a 6SN1118-x-x-x-x-x) over a PROFIBUS DP cable terminated per EN 50170. The 611U exposes a PROFIdrive-compliant slave interface and supports PPO types 1, 2, 3, 4, and 5. For positioning, PPO4 is the standard selection because it provides 6 process data words (PZD) in both directions plus the 4-word PKW parameter channel.

1.1 Hardware Bill of Materials

2. Prerequisites

1. STEP 7 V5.5 (or higher) with S7-300 component support installed.
2. SIMOCOMU commissioning software matching the 611U firmware (check Help > About for the supported GSD-compatible parameter set).
3. PROFIBUS cable pre-wired, shields grounded at both ends, terminator ON at the two end nodes only.
4. 611U control unit node address set on the rotary DIP switch (DIP switch S1 / address 0...127; standard for 611U is 4).
5. 24 V control section powered (X124 connector) and pre-charge/line contactor hardware interlock wired per the manual.
6. GSD file for the 611U installed in STEP 7 (the file is shipped with SIMOCOMU and is named SIEM8110.GSD or similar, depending on firmware release).

3. SIMOCOMU Drive Configuration

Open SIMOCOMU, establish a serial or PROFIBUS connection to the 611U, and configure the drive for positioning mode. The 611U exposes hundreds of parameters; the minimum set required for a positioning application is shown below.

3.1 Minimum Parameter Set for Positioning

Save the parameter set to the EEPROM (P999 = 1 in SIMOCOMU to commit non-volatile). Cycle 24 V control power to activate.

4. SIMATIC Manager Hardware Configuration

1. Open STEP 7 / SIMATIC Manager and create a new project with the S7-315-2 DP as the station.
2. Open HW Config and place the S7-315-2 DP on rail 0.
3. Open the DP master system properties. Set baud rate (1.5 Mbps recommended) and the master address (default 1).
4. From the PROFIBUS DP catalog, open SIMODRIVE → SIMODRIVE 611 universal → drag the 611U to the master system.
5. Assign DP slave address 4 (or whatever matches the DIP switch on the control unit).
6. Open the 611U slot properties and select PPO type 4. PPO4 occupies 10 input words (4 PKW + 6 PZD) and 10 output words (4 PKW + 6 PZD) of the I/O image.
7. STEP 7 proposes a starting I/O address. The convention is to use multiples of 16. For this article, the inputs start at IW 280 (10 words: 280..289) and the outputs start at QW 280 (10 words: 280..289). This is the LADDR you pass to SFC14 and SFC15.
8. Compile and download the HW Config to the CPU. The CPU will perform a DP reconfiguration and the 611U will appear in the online DP slave list.

5. PPO4 Frame Structure

PPO4 is a 20-byte (10-word) telegram in each direction, divided into the parameter channel (PKW) and the process data (PZD).

6. Control Word (STW1) and Status Word (ZSW1) Map

The control word and status word definitions below are the standard PROFIdrive v2 values that the SIMODRIVE 611U publishes. Cross-check against the manual that ships with your specific 611U firmware (the original Configuration Manual is part number PJU_0613_en.pdf, "Configuration Manual SIMODRIVE 611 digital").

6.1 STW1 Bit Map (Master → 611U, PZD word 1 = QW288)

6.2 Reset / Enable Control Word Values

Per the source documentation, the two control word values used to start the 611U from cold are:

• QW288 = W#16#047E (binary 0000 0100 0111 1110): drive in a defined reset / not-enabled state. Bit 10 = 1 (PLC control), bit 1 = 1 (no OFF2), but bit 0 = 0 (no ON), so the drive is parked.
• QW288 = W#16#047F (binary 0000 0100 0111 1111): bit 0 = 1 → ON, bit 1,2,3,4,6,7,10 = 1 → drive enabled and pulses released (subject to hardware enable on terminal X121).

6.3 ZSW1 Bit Map (611U → Master, PZD word 1 = IW288)

7. SFC14 and SFC15 Programming (LAD and FBD)

SFC14 (DPRD_DAT) reads a consistent block of data from a DP slave. SFC15 (DPWR_DAT) writes a consistent block of data to a DP slave. The 20-byte PPO4 must be transferred atomically (i.e. all 10 words in a single DP cycle) to avoid a torn read on multi-word values such as the 32-bit actual position Xist.

7.1 Data Block Layout (DB100)

Reserve a 40-byte data block for the cyclic image:

DATA_BLOCK DB100
  STRUCT
    RX_PPO : ARRAY[0..19] OF BYTE;   // Inputs (611U -> Master), filled by SFC14
    TX_PPO : ARRAY[0..19] OF BYTE;   // Outputs (Master -> 611U), source for SFC15
  END_STRUCT
END_DATA_BLOCK

Symbolic names simplify FBD and LAD coding. Define the following in the symbol table:

7.2 LAD Network — Read PPO4 from 611U

Network 1: Read PPO4 from slave 611U (LADDR 280) into DB100.PPO4_RX
  CALL "DPRD_DAT"           // SFC14
   LADDR    := W#16#0280    // configured I/O start address of the 611U
   RET_VAL  := MW100        // 0 = OK, see fault code table
   RECORD   := P#DB100.DBX0.0 BYTE 20

Equivalent graphic in LAD: a single SFC14 box with the three terminals connected as shown. LADDR is fixed at W#16#280; RET_VAL feeds a status word that OB1 can evaluate; RECORD is the symbolic pointer P#DB100.DBX0.0 BYTE 20.

7.3 LAD Network — Write PPO4 to 611U

Network 2: Write DB100.PPO4_TX to slave 611U (LADDR 280)
  CALL "DPWR_DAT"           // SFC15
   LADDR    := W#16#0280
   RECORD   := P#DB100.DBX20.0 BYTE 20
   RET_VAL  := MW102        // 0 = OK, see fault code table

7.4 FBD Variant (same logic, graphical form)

In FBD the two boxes appear as standard function blocks. The RECORD inputs accept the pointer P#DB100.DBX0.0 BYTE 20 and P#DB100.DBX20.0 BYTE 20 respectively. RET_VAL is a WORD output that should be tied to a status flag and ideally also passed to SF (set fault) for OB82-driven diagnostics.

7.5 STL Variant (compact, for reference)

// --- Read ---
CALL "DPRD_DAT"
     LADDR :=W#16#280
     RET_VAL:=MW100
     RECORD :=P#DB100.DBX0.0 BYTE 20
// --- Write ---
CALL "DPWR_DAT"
     LADDR :=W#16#280
     RECORD :=P#DB100.DBX20.0 BYTE 20
     RET_VAL:=MW102

7.6 SFC14 / SFC15 Return Code (RET_VAL) Matrix

8. State Machine for the 611U Control Word

Below is the recommended state sequence implemented in OB1. The transitions and the corresponding STW1 values are standard PROFIdrive v2 timing.

8.1 Sample FBD — Control Word Sequencer (Network 3)

// Step S0: STW1 := W#16#0     when start = FALSE
// Step S1: STW1 := W#16#047E  when start = TRUE AND ZSW1.0 = TRUE
// Step S2: STW1 := W#16#047F  when ZSW1.1 = TRUE
// Step S3: STW1 := W#16#047E  when ZSW1.3 = TRUE (fault), keep STW1.7 toggled

9. Traversing Blocks (Positioning Mode)

Once the drive is enabled, positioning is achieved by selecting a traversing block number in STW2 (PZD word 6, QW298). The 611U supports 64 traversing blocks in absolute or relative mode.

9.1 Traversing Block Header (in PPO4, written via PKW)

For continuous block streaming, write the block number into P1500 using the PKW channel while the 611U is in Block selection mode (P1250 = 1).

9.2 Override and Function Inhibit

• Override is written into PZD3 (QW292). The 611U scales the velocity in PZD2 by this factor; valid range is 0..16384 with 16384 = 100 %.
• Function inhibit (P1240) is a hardware-equivalent safety: when the corresponding bit in STW2 is set, the drive refuses new traversing tasks and decelerates the axis to standstill with the configured emergency ramp.

10. Homing and Referencing

Before any absolute positioning, the axis must be homed. The 611U supports multiple homing modes (P1400):

Confirm ZSW1 bit 10 (Reference point reached) is 1 before issuing any absolute traversing task.

11. Commissioning and Verification

1. Bring the system to a safe state. Open line contactor, ensure emergency stop chain is closed.
2. Connect STEP 7 to the S7-315 and go online. In HW Config right-click the 611U and select PROFIBUS diagnostics to confirm the slave is in cyclic data exchange (no red X).
3. Open a VAT table in STEP 7. Force DB100.DBW38 = W#16#047E and observe DB100.DBW28 for ZSW1.0 = 1.
4. Force DB100.DBW38 = W#16#047F. Check ZSW1.1 = 1 and ZSW1.2 = 1; the 611U should now be running. With the line contactor still open, no motion occurs but the drives internal state is armed.
5. Close the line contactor (in controlled order). Issue a small relative move via traversing block 1 (e.g. 1.0 mm at 1 mm/s) and monitor DB100.DBD34 for the actual position advancing toward the target.
6. Inspect the PROFIBUS diagnostics page periodically; it shows the last error counters, retry count, and bus statistics for the 611U segment.
7. Use the SIMOCOMU trace function to record the internal state machine, current, and speed for the next positioning run. Cross-check against the S7 VAT.

12. Troubleshooting Matrix

13. Common 611U Fault Codes (Subset)

The 611U has an eight-digit fault number space. The table below lists the most common ones encountered during PROFIBUS-driven commissioning; refer to the Configuration Manual for the full list.

14. Best Practices

• Always place the SFC14/15 calls in OB1 (or a single consistent-time OB such as OB35 if you need fixed 100 ms scheduling). Calling them from multiple OBs at different priorities leads to torn writes and bus collisions.
• For 32-bit values (Xist, NIST_B), never use direct I/O access. Go through SFC14/15 into a DB to guarantee consistency.
• Program the state machine in a separate FB (e.g. FB611) so the same block can be reused for multiple 611U axes. Pass LADDR, STW1, NIST, and the Xist actual position as VAR_IN_OUT of type STRUCT.
• Monitor the PROFIBUS diagnostics page after every parameter change in SIMOCOMU. The 611U sometimes re-initialises the DP interface after a non-volatile commit, which can cause a momentary 80A1 return code.
• Where possible, use a higher-priority OB (OB35) for the cyclic PZD write and a lower-priority OB (OB1) for the acyclic PKW writes. Insert a bit interlock to prevent a PKW write and a PZD write from clashing in the same cycle.

15. References to Official Documentation

The Configuration Manual for SIMODRIVE 611 digital (PJU_0613_en.pdf) is the master document for parameter numbers, telegram structures, and fault codes used in this article. The SFC14 / SFC15 semantics are documented in the SIMATIC S7-300/400 system and standard functions reference manual.