Troubleshooting DP Slave Not Ready on Hilscher NT100-DP Profibus Gateways

Problem Overview

A DP slave "not ready" condition on a Profibus DP network prevents the slave from exchanging process data with the DP master. When this fault occurs with a Hilscher NT100-DP gateway acting as a Modbus RTU to Profibus DP slave, the master CPU reports the gateway as a non-participating node on the bus. The slave diagnostic indication "not ready for parameter assignment and data exchange" appears in the diagnostic buffer of the S7 master and in the DP slave diagnostics view of STEP 7 or TIA Portal.

The reported configuration in this case:

• Master CPU MLFB: 6ES7 314-6CG03-0AB0 (SIMATIC S7-314C-2 DP compact CPU)
• Slave: Hilscher NT100-DP gateway (Modbus RTU to Profibus DP)
• DP station address: 44
• Baud rate: 1.5 Mbps
• Application: Modbus RTU to Profibus DP conversion
• SCADA: SIMATIC WinCC on the S7-300 process image

The slave address of 44 is above the per-segment electrical limit of 32 nodes defined by RS-485 driver loading, the baud rate of 1.5 Mbps is within the Profibus DP specification but at the upper edge of practical reliability, and the combination demands a fault-tolerant topology with proper termination, shielding, and at least one Profibus repeater between master and slave.

DP Slave Diagnostic States Reference

The Profibus DP standard defines a finite state machine for each slave. STEP 7 surfaces these states in the DP slave diagnostics view. The relevant transitions and their meanings are summarized below.

The "DP slave is not yet ready for parameter assignment and data exchange" indication corresponds to a slave that has just powered on or has been reset by the master. If the state persists beyond the standard initialization window of approximately 5-10 seconds, it indicates a bus communication fault rather than a transient startup condition.

Siemens documentation describes the state as follows: the slave is in startup and temporarily displays "not ready" before transitioning to parameterization. Persistent display of this state requires intervention on the physical layer, addressing, or GSD configuration. Reference: Siemens TIA Portal V21 - DP slave diagnostics (S7-300, S7-400).

Station Status Byte Decoding

When the slave is in Not_Ready, decode the Station Status 1 byte from the slave diagnostic frame to isolate the precise cause:

Station Status 2 indicates the master address and the slave's relationship to other masters. Station Status 3 contains the Ident number high/low, allowing the master to confirm the GSD assignment matches the physical slave.

Root Cause Analysis

A persistent DP slave "not ready" condition at address 44 with 1.5 Mbps baud rate typically traces to one of the following causes, listed in order of probability for this configuration:

1. DP station address outside master segment electrical limit — The CPU 314C-2 DP does not enforce a hard limit of 32 slaves per logical DP master system; the Profibus standard allows addresses 0-125. However, address 44 exceeds the per-segment electrical limit of 32 nodes (address 0 is reserved for masters/service, address 1-31 for slaves in a single segment per RS-485 driver loading). The slave at address 44 requires a multi-segment topology with at least one repeater between the master segment and the gateway segment. A missing or misconfigured repeater will leave address 44 unreachable.
2. Baud rate mismatch or signal integrity at 1.5 Mbps — 1.5 Mbps is within the Profibus DP specification (9.6 kbps to 12 Mbps) but is at the upper edge where cable quality, shielding, and termination become critical. A 1.5 Mbps segment cannot exceed 200 m of Type A cable without repeaters, and any sub-standard cable will cause intermittent loss of telegrams, which the slave interprets as a Not_Ready condition.
3. Incorrect or missing GSD file — The Hilscher NT100-DP requires its manufacturer-supplied GSD file to be installed in the STEP 7 GSD repository and selected during DP slave configuration. A generic PROFIBUS GSD or a wrong revision will cause the slave to reject the parameterization telegram and remain in Wait_Prm.
4. Cable termination or shielding defect — The first and last device on each segment must have termination enabled. A segment with only one termination or with termination at a middle device produces reflections that corrupt the telegram at 1.5 Mbps.
5. Gateway power or configuration fault — The NT100-DP gateway requires correct Modbus RTU side configuration (baud rate, parity, slave ID, register map) and correct DP side configuration (slave address, baud rate auto-detect). If the gateway is not in "Data Exchange" state on its own diagnostic LEDs, the slave will never reach Data_Exch with the master.

Hardware and Cabling Verification

The Profibus DP cable must meet IEC 61158-2 Type A specification. For 1.5 Mbps, the maximum segment length is 200 m without repeaters, with bus termination at both ends of every segment.

Cable Specification

Verification Procedure

1. Power off all DP nodes including the S7-300 CPU and the Hilscher NT100-DP gateway.
2. Inspect the Profibus connector at the gateway and at every neighboring node. Confirm that the termination switch is ON only at the two physical ends of each segment.
3. Measure the resistance between pins 3 and 8 of a Profibus connector with the connector disconnected from the device. Reading should be infinity (open) at middle nodes and approximately 220 Ω (two 390 Ω termination resistors in parallel plus network impedance) at the two end nodes.
4. Connect a PG/PC with STEP 7 installed to the Profibus segment. Open "Accessible Nodes" from the STEP 7 interface. Verify whether the Hilscher gateway at address 44 appears.
5. If the gateway does not appear, isolate the segment by disconnecting other nodes and reconnecting one at a time to locate a defective terminator or cable.

If the gateway appears with a bus fault icon, the physical layer is functional but the slave is rejecting parameterization; proceed to GSD verification. Reference: Beckhoff DP slave diagnostics - State of the Slaves.

GSD File Configuration Check

The GSD (General Station Description) file defines the slave's identity, supported baud rates, diagnostic message format, and I/O module configuration to the DP master. For the Hilscher NT100-DP, the manufacturer GSD file is distributed via the Hilscher support package on the official Hilscher website under Support → Software → NT100-DP. The file name typically follows the pattern HIL_xxxx.GSD matching the gateway's Ident number.

Installation Steps

1. Download the GSD package from the official Hilscher support portal.
2. Extract the archive. Locate the GSD file matching the gateway's article number and firmware version.
3. In STEP 7 (V5.x) or TIA Portal, install the GSD via:
   • STEP 7 V5.x: Options → Install GSD File → Browse to folder → Select GSD → Install.
   • TIA Portal: Options → Manage device description files (GSD) → Install.
4. Restart the engineering software to refresh the device catalog.
5. Open HW Config / Device View. The Hilscher NT100-DP should now appear under PROFIBUS DP → Additional Field Devices → Gateways.

Verification Points

• GSD revision must match the firmware on the gateway. Mismatched revisions cause the parameterization check to fail and the slave remains in Wait_Prm.
• Baud rate entries in the GSD must include 1.5 Mbps. Older GSD revisions for some Hilscher gateways only support up to 500 kbps; verify the support matrix on the product page.
• Ident number of the slave in HW Config must match the Ident number printed on the gateway label.
• Module configuration in the slot assignment must reflect the Modbus register map. Typical NT100-DP configurations use 4 or 8 words of input and output.

DP Address and Baud Rate Requirements

The Profibus DP standard reserves addresses 0-125. Address 0 is reserved for service devices (PG/PC). Addresses 1-125 are available for slaves. The electrical segment limit is 32 nodes per segment (including master and repeaters) per RS-485 driver loading.

Address Space and Segment Limits

A slave at address 44 is permitted by the Profibus DP protocol but requires the segment to be extended by at least one repeater between master segment (addresses 1-31) and the gateway. Without the repeater, the master's DP interface cannot drive the bus to the gateway and the slave is reported as not reachable.

Baud Rate Reference

At 1.5 Mbps the bit time is 667 ns. Cable reflection, improper termination, or stubs longer than the specified maximum will cause telegram corruption. Reduce the baud rate to 187.5 kbps or 500 kbps as a fault isolation step. If the slave comes online at lower baud rate, the physical layer is marginal at 1.5 Mbps and requires cable repair or topology changes.

CPU 314C-2 DP Capability Constraints

The reported MLFB 6ES7 314-6CG03-0AB0 identifies a SIMATIC S7-314C-2 DP compact CPU. This CPU has two Profibus interfaces:

• Interface 1 (MPI/DP): MPI default, configurable as DP master or DP slave via HW Config.
• Interface 2 (DP): Dedicated DP master/slave interface.

S7-314C-2 DP Key Specifications

The CPU 314C-2 DP supports a maximum of 32 DP slaves per DP master system. If the project contains more than 32 slaves, additional DP master systems must be created (one per interface). For a single gateway at address 44 with one DP master system, the address itself is valid but the segment topology must support it. For full hardware specifications consult the Siemens Industry Online Support portal at support.industry.siemens.com and search for the MLFB.

STEP 7 / TIA Portal Diagnostic Procedure

The following procedure extracts the actual DP slave state from the CPU and isolates the fault.

Procedure in STEP 7 V5.x

1. Connect the PG to the MPI/DP interface of the CPU 314C-2 DP.
2. Go online (PLC → Online → Accessible Nodes).
3. Open HW Config. Right-click the DP master system → "DP Slave Diagnostics".
4. Locate the Hilscher NT100-DP entry. The status column displays the slave's current state from the table above.
5. Click on the slave. The "Slave Diagnostics" window displays Station status 1, 2, 3 (bytes per Profibus standard), master address, Ident number, and diagnostic bytes (manufacturer-specific).
6. Interpret Station Status 1 byte per the bit assignment table above.
7. Read the CPU diagnostic buffer (PLC → Diagnostic Buffer). Entries of type "DP slave failure" or "DP slave not reachable" provide the timestamp and the affected slave address.

Procedure in TIA Portal V21

1. Go online with the CPU.
2. Open "Diagnostics" from the project tree.
3. Select "PROFIBUS Diagnostics".
4. View the slave list. Each slave's status (green = Data_Exch, yellow = Not_Ready, red = Failure) is color-coded.
5. Click on the Hilscher gateway entry to view detailed diagnostic information, including last telegram timestamp and Ident number verification.

Reference: Siemens TIA Portal V21 - DP slave diagnostics documentation.

Configuring the Hilscher NT100-DP Gateway

The NT100-DP gateway is configured via the Hilscher SYCON.net configuration tool or via the on-board DIP switches for the DP address.

DP Address Configuration (DIP Switches)

The slave address is set via binary-coded DIP switches on the gateway. Address 44 (decimal) equals 0x2C (binary 00101100). Bits 2, 3, and 5 must be ON:

A change to the DIP switches takes effect only after a gateway power cycle. Always power cycle after adjusting the address.

SYCON.net Configuration

1. Connect the PG to the diagnostic port (USB or RS-232) of the NT100-DP.
2. Launch SYCON.net. Scan for the gateway.
3. Configure the DP slave side: address 44, baud rate auto-detect (recommended for verification).
4. Configure the Modbus RTU master side: baud rate, parity, stop bits, slave ID, polling interval.
5. Map the Modbus registers to the DP I/O areas:
   • Input area (slave → master): Modbus registers 40001-40016 mapped to PIW 0-31 (16 words).
   • Output area (master → slave): PQW 0-15 mapped to Modbus registers 40001-40008.
6. Download the configuration to the gateway.
7. Verify the gateway's status LEDs:
   • RUN (green) solid: Gateway running.
   • ERR (red) off: No internal error.
   • DP (yellow) flashing: Data exchange active.
   • COM (green) flashing: Modbus RTU communication active.

If the DP LED is solid on and not flashing, the gateway is not in data exchange with the master; return to the master diagnostics. A solid DP LED typically indicates a parameterization or configuration fault rather than a physical layer fault.

Commissioning and Verification Procedure

Execute the following verification sequence after applying configuration changes.

1. Physical verification — Confirm termination is active at exactly two nodes per segment. Confirm cable lengths match baud rate per the segment length table.
2. PG visibility — From STEP 7 / TIA Portal, verify the gateway appears in "Accessible Nodes" at address 44.
3. Master configuration — Confirm the Hilscher gateway is in HW Config at address 44, with the correct GSD module selected.
4. Download configuration — Download HW Config to the CPU. The CPU performs a DP master restart, re-parameterizes all slaves.
5. Check diagnostic buffer — After 30 seconds, read the CPU diagnostic buffer. No DP slave failure entries should appear.
6. Check DP slave diagnostics — Open DP Slave Diagnostics. The slave state should be Data_Exch (green).
7. I/O test — In a watch table or with the PG online monitor, force an output value at PQW x and verify the corresponding Modbus register changes on the Modbus side. Read the corresponding PIW and verify the Modbus input register value appears.
8. Long-term stability — Leave the system running for 24 hours and re-check the diagnostic buffer. Intermittent failures will appear as "DP slave failure" with timestamps.

WinCC Tag Integration for PIW Monitoring

WinCC reads tags from the S7-300 process image. The DP slave's input words appear at offsets defined in HW Config. For example, if the Hilscher NT100-DP is configured with module slot 1 as "4 words input" at address base 0, the inputs are at PIW 0-7.

WinCC Tag Configuration

1. Open WinCC Explorer. Add a new connection to the S7-300 CPU with the WinCC channel "SIMATIC S7-300/400".
2. Add tags. For each Modbus register to be monitored:
   • Tag name: e.g., Modbus_Register_40001
   • Address: DB0,WORD0 or direct peripheral address IW0
   • Data type: WORD or INT
   • Length: 1 word per register
3. For a window of 1000 Modbus registers, structure the configuration as 1000 tags or use a script-based approach with a single tag area and pointer-based access.

Bulk Tag Scripting Example (C-Script)

// Read 1000 Modbus words from PIW 0-999 and log to WinCC archive
#include "apdefap.h"
BOOL LogModbusRegisters()
{
    DWORD dwError;
    WORD wValue;
    for (int i = 0; i < 1000; i++)
    {
        char szTagName[64];
        sprintf(szTagName, "Modbus_Register_%d", i);
        dwError = GetTagWord(szTagName, &wValue);
        if (!dwError)
        {
            printf("Register %d = %d\n", i, wValue);
        }
    }
    return TRUE;
}

WinCC Tag Licensing

Each tag in WinCC requires a runtime license per the WinCC licensing model. The WinCC base license includes 128 tags by default; additional power tags are licensed in 256-tag packages. For 1000 Modbus registers, ensure adequate power tags are licensed.

Troubleshooting Matrix

CPU 314C-2 DP vs CPU 414-3 DP Comparison

Confirm the actual CPU MLFB on the hardware before assuming the configuration. The MLFB on the front panel of the CPU starts with "6ES7 414" for a CPU 414-3 DP. Mismatched CPU identification is a common cause of "module configured but not available" diagnostic entries.

Safety Notes

FAQ