Troubleshooting Profibus DP on Hach SC1000 in TIA Portal V15

A Siemens CPU 1512SP-1 PN controlling a Hach Lange SC1000 multi-channel digital controller over Profibus DP through a CM 1542-5 master module is a typical water/wastewater analyser network. Field engineers frequently report that the SC1000 stays "not reachable" after GSD installation and address configuration. The root cause is almost always a mismatch between the SC1000 keypad-configured Profibus telegram and the slot configuration downloaded into the S7-1500, compounded by an incomplete project download. This reference walks through architecture, GSD handling, telegram alignment, hardware download, and the data-exchange program required to bring the link up.

1. System Architecture

The network is a classic Profibus DP master/slave link with a hybrid ET 200SP station acting as the head-end controller.

The CM 1542-5 (6ES7 545-5DA00-0AB0) is a Profibus DP master/slave module for the SIMATIC ET 200SP distributed I/O system. It supports DPV0 and DPV1, up to 32 slaves per segment, and diagnostic interrupts to the host CPU. The module must be inserted into a Type A0 or Type A1 base unit (BU15-P16+A0+2B or similar). Without a base unit the module will not be detected during hardware detection in TIA Portal.

2. Profibus Cabling and Termination

Before touching software, validate the physical layer. A Profibus DP link at the standard 1.5 Mbaud baud rate tolerates only the segment limits defined by IEC 61158 / EN 50170:

• Max segment length at 1.5 Mbaud: 200 m
• Max segment length at 12 Mbaud: 100 m
• Termination: active at both segment ends, ON at the connector (typically Siemens 6GK1 500-0FC10 or 6ES7 972-0BA12-0XA0)
• Shield continuity: 360° bonding at every connector
• Shield grounded at cabinet entry, not on both ends if the segment runs between buildings (avoid ground loops)

With only two nodes (master at address 2, slave at address 4), the terminators at the two end connectors are sufficient. A common field failure is leaving terminators OFF at both ends because both connectors ship with the switch in the OFF position. Verify with a continuity check across the A and B cores between the two end connectors; termination creates a defined DC bias.

3. GSD File Installation

The SC1000 Profibus option card requires a vendor GSD file (Hach Lange part of the SC1000 Profibus option kit). The GSD defines the device's slave capabilities: supported baud rates, module identifiers, and the I/O data layout.

3.1 Install the GSD in TIA Portal V15

1. Copy the GSD file (e.g., HACHA044.GSD or HACH0F6C.GSD) and matching bitmap .bmp to a local folder.
2. Open TIA Portal > Options > Manage general station description files (GSD).
3. Browse to the folder, select the .gsd file, click Install.
4. Confirm the device appears under Other field devices > PROFIBUS DP > Sensors > ... > HACH LANGE > SC1000.

4. Profibus Address Allocation

Profibus DP uses station addresses 0 to 127, with 0 and 1 reserved for masters in most implementations. The reported network uses:

Both addresses must match. Mismatched addresses are the number one reason the SC1000 stays "not reachable" even though the cable checks out.

5. SC1000 Profibus Telegram Configuration (Key Step)

The SC1000 is a pure DP slave. There are no DIP switches on the controller to set the address or telegram; every parameter is configured through the SC1000 keypad. The Profibus menu structure and the supported telegram data widths are described in the SC1000 controller manual, section 5.12.

5.1 Setting the Slave Address on the SC1000

1. On the SC1000 front panel, press Menu.
2. Navigate to System Setup > Communication > Profibus.
3. Set Profibus Address to 4.
4. Save and back out to confirm the value persists after a power cycle.

5.2 Choosing the Telegram Length

The SC1000 Profibus option card supports several fixed telegram widths. The most commonly used data layouts for the SC1000 are:

Whatever width is selected in the SC1000 menu MUST match the slot configuration that is downloaded into the CM 1542-5 in TIA Portal. If the widths differ, the master either reports a parameterisation fault or, more commonly, the slave appears online but no process data is exchanged and the SC1000 stays "not reachable" in the user's mind because no values update.

6. TIA Portal Hardware Configuration

Open the device view of the CM 1542-5 in the project tree. The configuration must mirror the SC1000 telegram chosen in section 5.

6.1 Add the SC1000 to the Profibus Subnet

1. Open Devices & Networks.
2. Select the CM 1542-5 and the existing PROFIBUS_1 subnet (or create a new one with the desired baud rate; Auto is acceptable for a homogeneous segment).
3. In the hardware catalog, navigate to Other field devices > PROFIBUS DP > Sensors > HACH LANGE > SC1000.
4. Drag the SC1000 onto the subnet. The system will assign a default Profibus address; change it to 4 in the inspector.
5. Open the SC1000 device view. Add a slot module matching the SC1000 telegram width (e.g., 16 bytes I / 16 bytes O).

6.2 Slot and I/O Address Map

TIA Portal assigns I and Q addresses in the process image. The base addresses for the SC1000 slot appear in the inspector under I/O addresses:

Note these addresses. The LADDR input of DPRD_DAT and DPWR_DAT expects the logical base address from the I/O addresses table. Using the diagnostic address instead of the process image base is a common error.

7. Project Download — The Single Most Common Field Mistake

Configuring the hardware is not enough. The configuration must be compiled and downloaded to the S7-1500 station. Field engineers frequently use the top-bar Download button in TIA Portal, which downloads the software (the program blocks) but not the hardware configuration. The result is a project with a program but with the original PLC hardware configuration still in the CPU — and therefore no Profibus master at all, or a Profibus master with the old slot list.

1. Right-click the CPU_1 [CPU 1512SP-1 PN] node.
2. Choose Download to device > Hardware configuration.
3. If a PG/PC interface dialog appears, select the PROFINET interface used for engineering.
4. In the download preview, verify the following are selected:
   • Software (blocks)
   • Hardware configuration
   • All Profibus devices (CM 1542-5 and SC1000)
5. Click Load. Accept the prompt to overwrite online/offline differences.
6. After download, perform a CPU restart (Run > Restart) so the CM 1542-5 reinitialises and the SC1000 is parameterised.

8. Data Exchange Programming (DPRD_DAT / DPWR_DAT)

For DPV0 slaves the standard SIMATIC system blocks are DPRD_DAT (read) and DPWR_DAT (write). Both blocks come from the SIMATIC system library and are available in TIA Portal as part of the standard S7-1500 instruction set.

8.1 Block Interfaces

The LADDR must be the input base for DPRD_DAT and the output base for DPWR_DAT. Some engineers mistakenly use the same value for both. The two addresses are usually adjacent but not always; check the device view.

8.2 Structured Text Sample (SCL)

// FB_SC1000_DataExchange
// Inputs : bEnable : BOOL, hwInputBase : WORD, hwOutputBase : WORD
// Outputs: bBusy : BOOL, bError : BOOL, wStatus : WORD
// InOuts : iqData : ARRAY[0..31] of BYTE

IF bEnable THEN
    // Read 16 bytes from SC1000 into iqData[0..15]
    #iStatusRead := DPRD_DAT(
        LADDR  := #hwInputBase,
        RET_VAL:= #wStatusRead);
    // wStatusRead = 0 means success

    // Write 16 bytes from iqData[16..31] to SC1000
    #iStatusWrite := DPWR_DAT(
        LADDR  := #hwOutputBase,
        RECORD := #iqData[16],
        RET_VAL:= #wStatusWrite);
END_IF;

8.3 Ladder Logic Sample

Network 1 — Read SC1000 input data
|--[ bEnable ]--[CALL DPRD_DAT
|                 LADDR := W#16#100
|                 RECORD := P#DB100.DBX0.0 BYTE 16
|                 RET_VAL := MW200 ]--|

Network 2 — Write SC1000 output data
|--[ bEnable ]--[CALL DPWR_DAT
|                 LADDR := W#16#100
|                 RECORD := P#DB100.DBX16.0 BYTE 16
|                 RET_VAL := MW202 ]--|

For DPV1 services (acyclic read/write of diagnostic data), the standard blocks RDREC and WRREC are used. The SC1000 GSD may not expose DPV1 slots; check the GSD revision.

9. Diagnostics and LED Behaviour

Read the LED status of the CM 1542-5 and the Profibus connector to isolate the fault layer:

10. TIA Portal Online Diagnostics

1. Go online with the CPU.
2. Open Devices & Networks, then Online & diagnostics on the CM 1542-5.
3. Open the Diagnostics buffer. Look for entries such as:
   • Parameterisation error at slave address 4 — telegram mismatch or wrong GSD revision
   • Slave not found — address or wiring problem
   • Configuration error at slave address 4 — slot count differs from GSD
4. Click the slave in the Profibus topology view. The status panel shows:
   • OK: slave in cyclic data exchange
   • Not reachable: no response to parameterisation
   • Fault: parameterisation failed

11. SC1000 Front-Panel Diagnostics

On the SC1000 keypad, navigate to System Setup > Communication > Profibus > Status. Typical status displays:

12. Step-by-Step Recovery Procedure

If the SC1000 is still "not reachable" after the steps above, perform a clean recovery:

1. On the SC1000 keypad, perform a Factory Defaults on the Profibus option card (System Setup > Communication > Profibus > Reset).
2. Re-enter the Profibus address 4 and select the desired telegram width (e.g., 16/16).
3. In TIA Portal, delete the SC1000 from the Profibus subnet.
4. Re-drag the SC1000 from the catalog onto the subnet.
5. Re-add the matching slot module in the SC1000 device view.
6. Right-click the CPU and choose Download to device > Hardware configuration (NOT the top-bar download button).
7. Wait for the CPU to restart. Watch the CM 1542-5 BF LED transition to off.
8. Check the SC1000 Profibus status: should read "OK".
9. Monitor the relevant DB with a VAT table to confirm process values update.

13. Troubleshooting Matrix

14. Performance and Timing Notes

Profibus DP cycle time on a small two-node segment at 1.5 Mbaud is typically in the 1–5 ms range. With the SC1000 polling at 16/16 the cyclic data is updated in the S7-1500 process image at the OB1 cycle boundary. For better determinism move the SC1000 I/O into a process image partition (PIP) and use OB 6x synchronised to a constant bus cycle. Hach documentation does not specify a minimum OB1 cycle time, but Profibus DP guarantees token rotation and slave polling within configured slot time (Tsl) and watchdog.

15. Related Standards and References

The Profibus DP protocol is standardised in IEC 61158 and IEC 61784. The CM 1542-5 conforms to the PROFIBUS profile for DP master class 1/2. The SC1000 Profibus option is registered in the PI (PROFIBUS & PROFINET International) product guide as a vendor-registered slave device.