Designing a 300-Node PROFIBUS Network with S7-300 and CP 342-5

Designing a 300-Node PROFIBUS Network with S7-300 and CP 342-5

A single PROFIBUS-DP segment is electrically limited to 32 nodes and the PROFIBUS standard caps any single bus at a maximum of 126 stations (address 0–125, with one slot reserved for the master). Hitting 300 slaves on one cable is therefore not a configuration problem you can solve by adding a different master — it is a topology problem you solve with multiple DP networks tied to a single S7-300 station. This reference walks through the architecture, hardware, segment math, TIA Portal configuration, and DP_SEND/DP_RECV programming required to build a 300-node PROFIBUS installation.

1. PROFIBUS Node Limits: Why 300 on One Cable Is Impossible

PROFIBUS-DP is built on RS-485. The physical layer of RS-485 places hard ceilings on every segment, and the PROFIBUS specification inherits those ceilings without exception.

Address 126 is reserved as the global broadcast address; in practice that means a single DP network tops out at 125 usable slaves. To reach 300 slaves you must split the installation into a minimum of three logical PROFIBUS networks, each terminating at its own DP master. The good news: a single S7-300 CPU can host all three masters if you bolt on the right communication processors.

2. System Architecture for 300 Slaves

The recommended partition for 300 DP slaves is three DP networks, each carrying 100 slaves. This keeps every network under 125 stations, gives the operator meaningful engineering granularity (one production cell = one DP subnet), and minimizes the blast radius of a single cable fault.

Each network uses 4 repeaters to break the 100 slaves into 4 segments of 25 slaves (well under the 32-node electrical limit). The terminating repeater on the last segment also serves as the active bus terminator, eliminating the need for a separate termination resistor block at the very end of the cable.

2.1 Address Space Layout

PROFIBUS addresses are unique per network — not globally across the plant. You can therefore reuse address 3 in all three networks without collision, as long as the GSD file and slot configuration for that slave are identical.

Note that for the CP 342-5, address 2 is the recommended master default; the integrated CPU 315-2DP port also defaults to 2. Keeping the master address identical across all three subnets simplifies the GSD library and the operator HMI diagnostics.

3. Hardware Selection and Bill of Materials

4. TIA Portal Network Configuration

Configure all three subnets in the Devices & Networks editor of TIA Portal V17 (or V18/V19/V20 — the steps are identical). Start with the CPU 315-2DP integrated port, then add the two CP 342-5 modules.

4.1 Subnet Properties

1. Open the project, then double-click Devices & Networks.
2. Select the CPU 315-2DP port DP (X2) and choose Add new subnet → name it DP-Network_1.
3. For each CP 342-5 in slot 4 and slot 5, select its DP port and create DP-Network_2 and DP-Network_3. The CPs and the CPU port must NOT share a single subnet.
4. Open Properties > PROFIBUS interface > Address on every master:
   • Address: 2
   • Highest station address (HSA): 125
   • Transmission speed: 1.5 Mbps
   • Profile: DP

Per Siemens' TIA Portal V20 PROFIBUS line configuration guide, a maximum of 125 nodes are possible on the bus (No. 0 to 124). If the HSA is set to a value less than or equal to 125, addresses equal to or greater than the HSA are not used during the token rotation; the bus master skips them entirely. Always set HSA to the highest address you will ever use, then leave a safety gap.

4.2 Importing Slave GSD Files

1. Download the GSD file for every slave type (ET200S, ET200MP, frequency inverter, valve island, etc.) from the manufacturer site.
2. In TIA Portal: Options > Manage general station description files (GSD) → install the GSD.
3. Drag the slave from the hardware catalog into the subnet, then assign it a unique address in the range 3–102 (100 slaves per subnet).
4. Configure the slot-level I/O on each slave (input bytes, output bytes, diagnostic slot).

5. Programming the CP 342-5 as a DP Master

The integrated DP port of a CPU 315-2DP exposes its peripheral I/O directly in the process image — you read inputs with IW x and write outputs with QW x. The CP 342-5 does not. Data between the CPU user program and the CP 342-5 is exchanged over the S7-300 backplane using two function blocks: DP_SEND (CPU → CP → slaves) and DP_RECV (slaves → CP → CPU). The official Siemens reference for the integrated DP port vs. CP 342-5 DP port is Entry ID 21628388.

5.1 FC Declarations

5.2 OB1 Cyclic Block (SCL / Structured Text)

// OB1 - Cyclic main
// CP 342-5 in slot 4 = DP-Network_2 (100 slaves)

// 1. Always call DP_RECV first to refresh RECV_DATA_CP2
DP_RECV(
    CPLADDR     := 256,                  // Base address of CP 342-5 in slot 4 (typical W#16#100)
    RECV        := RECV_DATA_CP2,        // 256-byte input buffer
    NDR         := DP_RECV_OK_CP2,       // New data received
    ERROR       := DP_ERROR_CP2,         // 16-bit error word
    STATUS      := DP_STATUS_CP2         // 16-bit status word
);

// 2. User logic writes the output image
SEND_DATA_CP2[0]  := SHL(BYTE#16#01, motor_run_cmd_bit);   // example
// ... (rest of your 256 bytes of output image)

// 3. Push output image to CP, which then broadcasts on DP
DP_SEND(
    CPLADDR     := 256,
    SEND        := SEND_DATA_CP2,
    DONE        := DP_SEND_OK_CP2,
    ERROR       := DP_ERROR_CP2,
    STATUS      := DP_STATUS_CP2
);

The second CP 342-5 in slot 5 uses its own base address (e.g. W#16#108) and its own SEND/RECV buffers. The same two FBs are called twice per OB1 cycle. Detailed configuration steps for the CP 342-5 as a DP master are in Siemens Entry ID 109744374.

5.3 DP_SEND/DP_RECV Error Code Reference

6. Segment Length and Repeater Math

PROFIBUS segment length is baud-rate dependent. Use the table below to size your violet cable runs.

For a 100-slave, 4-segment network at 1.5 Mbps, the maximum trunk distance is 4 × 200 m = 800 m from master to last slave, plus the drop-cable length per slave (typically < 0.5 m, must be kept short at >1.5 Mbps). If your plant exceeds 800 m total, drop one or more segments to 500 kbps (1600 m) or add a second-tier repeatered branch.

You may cascade up to 9 repeaters between any two stations. With 4 repeaters per network, 100 slaves, and 1.5 Mbps, you stay comfortably inside the token rotation timing budget (Ttr = 10,000 bit times at 1.5 Mbps ≈ 6.7 ms; a 100-slave token round fits in < 2 ms in practice).

7. Diagnostics and Verification

Once the system is wired and programmed, follow this verification sequence before handing the line to operations.

7.1 Power-Up Verification (per network)

1. Power on repeaters in order from master outward; verify green PWR LED on each.
2. Set the bus terminator ON at the first and last node only. Use a 9 V battery test: voltage between pins 5 and 6 of the first PROFIBUS connector should read ~5 V if termination is active.
3. Switch CPU to RUN. SF (red) and BF (red, bus fault) LEDs on the master should extinguish within 5 seconds.
4. Open TIA Portal Online & Diagnostics > PROFIBUS > Station Status — all 100 slaves should report Data Exchange.

7.2 Token Rotation Time Check

Use the master diagnostic buffer to read Trdy_actual (real token rotation time). For 100 slaves at 1.5 Mbps, Trdy_actual should be < 5 ms; values approaching 10 ms indicate an address gap (HSA too high) or a faulty repeater. Tighten HSA from 125 down to 110 to recover margin.

7.3 Cycle Time Test

Insert a TON timer in OB1 around the DP_SEND call. A healthy 100-slave network at 1.5 Mbps typically completes one full DP cycle in 3–8 ms. Sustained values > 15 ms require either a baud-rate drop (to 500 kbps) or network partition.

8. Troubleshooting Matrix

9. Practical Commissioning Checklist

1. Build one subnet at a time: commission DP-Network_1 with the integrated port first, then add DP-Network_2, then DP-Network_3.
2. Lock the addresses physically: write the PROFIBUS address on the housing of every slave (vinyl label or paint pen). Address re-numbering during a hot fault is the #1 cause of 4 a.m. callbacks.
3. Document the GSD file version used per slave type in the project comments. GSD drift is the second-biggest source of late-stage surprises.
4. Configure DP cycle synchronization in the CPU properties to lock the DP cycle to the OB1 cycle — eliminates jitter when the OB1 time slice and the DP token pass overlap.
5. Use a PROFIBUS diagnostic repeater (6GK1 500-0AB10) on at least one segment — it stores the last 100 bus events and identifies the segment at fault, which is invaluable when 300 nodes are spread across the plant.
6. Train the maintenance crew on address-based diagnostic: teach them that a slave on DP-Network_2 address 17 is the same physical sensor as the one previously on DP-Network_1 address 17 only if the GSD matches — a network swap can mask itself as a hardware fault.
7. Validate spare-parts strategy: keep one of every slave SKU on the shelf pre-addressed to its spare address (e.g. 110, 111, 112, 113, 114, 115 in every network) so a hot swap doesn't require a PG.

10. When to Use a Different Architecture

300 nodes is also a tipping point. Once the panel build exceeds 6 repeaters per network, consider:

• PROFINET: replace DP entirely. A single S7-300 with CP 343-1 handles hundreds of PROFINET devices with no segment math, no termination, and standard Ethernet cabling. Migration path: keep the same PLC, swap the CPs.
• PROFIBUS over fiber (OLM): use 6GK1 502-1/3/4 OLM modules to convert DP copper to fiber for plant-spanning runs > 800 m. Each OLM counts as a repeater in the cascaded chain (max 9 between any two stations).
• Distributed intelligence: drop an ET200S with IM151-8 PN/DP coupler as a sub-master — it aggregates 12 PROFIBUS slaves onto one PROFINET node, flattening the topology and reducing the number of DP masters you need to host in the S7-300.

FAQ