Troubleshooting Siemens TDC CP50M0 PROFIBUS ECO 4 Error

Problem Details

A Siemens TDC rack equipped with a CPU550 controller and a CP50M0 communication processor reports a non-zero ECO output at the @PRODP block together with a blinking H6 LED on the CPU module the moment a PROFIBUS DP slave (for example a Balluff encoder) is included in the project download. With the CPU configuration only — no slave — ECO = 0 and the H6 LED is steady, indicating a healthy bus master. The instant the slave GSD/database entry is added and the project is downloaded through ComProfibus, ECO transitions to 4 and H6 begins to blink, signalling that the CP50M0 has rejected the bus configuration.

This is one of the most frequent first-day issues on a TDC commissioning. The TDC PROFIBUS stack is intentionally split between three engineering artefacts:

1. The HWConfig rack (interface type and MPI/PROFIBUS address assignment on X1/X2).
2. The ComProfibus master database (slave list, slave addresses, I/O lengths, baud rate).
3. The CFC chart that contains the in/out telegram wiring for every slave.

All three artefacts must be consistent before @PRODP will leave state 0. A discrepancy between any pair — for example a slave declared in ComProfibus but not yet wired in CFC, or a CFC telegram whose length does not match the ComProfibus slave configuration — will surface as the ECO = 4 / H6-blinking signature documented in the TDC manual chapter 3.8 (PROFIBUS DP coupling CP50M0).

Affected Hardware and Engineering Tools

The failure pattern is specific to the SIMATIC TDC (Technology and Drive Control) platform, where the PROFIBUS master is hosted on a dedicated communication module rather than on the CPU itself. The minimum hardware set is:

• CPU550 — the TDC central processing unit. It runs the user project, hosts the CFC charts, and starts the bus via the @PRODP system block.
• CP50M0 — the PROFIBUS DP master communication module. It carries two physical interfaces:
  • X1 — typically configured as MPI (address 2 in the reported case) for engineering station access.
  • X2 — the PROFIBUS DP master port, which is the source of the ECO 4 error in this scenario.
• Engineering PC with STEP 7 / SIMATIC Manager for HWConfig and the legacy ComProfibus tool for the master database, plus the CFC editor for the application charts.

The TDC PROFIBUS coupling described in chapter 3.8 of the CP50M0 manual requires that ComProfibus generate a binary base configuration that is then downloaded into the CP50M0 independently of the STEP 7 / CFC download. Forgetting this separate download step is a common cause of the symptoms reported here, even when the CFC side is correct.

Root Cause Analysis

The ECO = 4 value with a blinking H6 LED indicates that the CP50M0 has either not received a valid master configuration, has received one that does not match the CFC side, or has detected a slave whose telegram the CFC has not declared. From the original report the most likely causes, in descending order of probability, are:

1. Missing in/out telegram wiring in CFC. The @PRODP block was instantiated and the bus started, but no CFC chart contains the receive/transmit blocks for the Balluff slave. Chapter 3.8 of the CP50M0 manual is explicit: in addition to @PRODP, every slave requires in/out telegrams in the CFC program.
2. ComProfibus base configuration not loaded to CP50M0. The slave was added to the ComProfibus project on the engineering station, but the binary master configuration was not downloaded to the CP50M0 flash/online memory. The CPU therefore sees the slave in CFC but the CP50M0 does not know about it.
3. Telegram length / I/O count mismatch. The number of input words and output words defined in the ComProfibus slave record does not match the telegram block parameters in CFC. The CP50M0 rejects the configuration because the projected bus shape is inconsistent.
4. Slave address / baud rate mismatch. The slave's physical address (e.g. 63) or its set baud rate does not match the ComProfibus master record. This is independent of ECO 4 — it usually surfaces as a slave diagnostic — but it should be ruled out during the same check pass.

Pre-Commissioning Checklist

Before touching @PRODP, walk through the following list. Each item has been a contributor to the reported symptom on real TDC racks:

1. Physical layer
   • PROFIBUS connector on CP50M0 X2 is wired to the incoming segment, terminating resistor is ON at both cable ends only.
   • Shield continuity checked end-to-end; shield grounded at one end only to avoid ground loops.
   • Slave PROFIBUS address set on the device (e.g. address 63 on a rotary selector).
   • Baud rate selector on the slave matches the ComProfibus master record.
2. HWConfig (STEP 7 / SIMATIC Manager)
   • CP50M0 inserted in the correct slot.
   • X1 interface type = MPI, address = 2 (or as required by site convention).
   • X2 interface type = PROFIBUS, master role assigned, address = 1 (matches @PRODP master address parameter).
   • HWConfig compiled and downloaded to the rack.
3. ComProfibus
   • Master created with the correct CPU (CPU550) and PROFIBUS address 1.
   • Slave inserted with correct GSD, correct bus address, and correct I/O length.
   • Project saved and the binary master configuration generated.
   • Binary configuration downloaded into the CP50M0 (not just saved on the engineering PC).
4. CFC
   • Chart contains an instance of the @PRODP block with valid parameters.
   • For every slave declared in ComProfibus, an in-block and an out-block are placed in the chart and connected to the application's processing blocks.
   • CFC chart compiled and downloaded to the CPU550.

@PRODP Block Parameter Reference

The @PRODP block is the TDC system block that starts and supervises the PROFIBUS DP master on the CP50M0. The block exposes the parameters listed below. The two values reported in the original symptom (BAUD = 5 and MASTER = 1) are the minimum to bring the bus up; the remaining parameters govern supervision and recovery.

ComProfibus Master Database Configuration

ComProfibus is the legacy tool that owns the master-side PROFIBUS database for TDC. It is the only place where the GSD-derived I/O footprint of each slave is recorded. The workflow is:

1. Open ComProfibus and create a new project, or open the existing project associated with the rack.
2. Insert the master with type CPU550 and address 1 (must match the value passed to @PRODP and the HWConfig PROFIBUS address).
3. Insert the slave (Balluff encoder in the reported case) at the desired PROFIBUS address, e.g. 63. This is also the address the TDC will use to identify the slave in the in/out telegram wiring.
4. Confirm the I/O length and consistency. If the slave is a pure encoder, expect input words only; if it has parameter channel data, those words must be included in the input length.
5. Save the project. Generate the binary master configuration.
6. Download the binary configuration into the CP50M0. This is a separate step from the STEP 7 / CFC download — the configuration lives in the CP50M0's own memory, not in the CPU's project file.

CFC In/Out Telegram Wiring

The CP50M0 manual chapter 3.8 (PROFIBUS DP coupling CP50M0) is the authoritative source for the telegram wiring procedure. The general pattern is:

1. Open the CFC chart where the bus data is to be consumed (one chart per slave, or one shared chart with all slaves, depending on application convention).
2. Insert the slave's input block (e.g. @DP_IN or a vendor-specific receive block). Configure it with:
   • The slave's PROFIBUS address (the same address used in ComProfibus, e.g. 63).
   • The number of input words to receive, matching the ComProfibus I/O length for that slave.
3. Insert the slave's output block (e.g. @DP_OUT or a vendor-specific transmit block) with the same address and the matching number of output words, even if the slave has no outputs (use a length of 0 in that case, do not omit the block).
4. Wire the input block's outputs and the output block's inputs to the application logic.
5. Compile the chart and download to the CPU550.

When the CFC download is repeated with a previously-missing slave wiring, the symptom resolves: ECO returns to 0 and H6 stops blinking once the CP50M0 sees a consistent projected bus shape.

Error Code Reference

Only two ECO values are documented in the original symptom report. The standard CP50M0 manual contains additional states; the values most often encountered in commissioning are summarised below. The interpretation column is conditional on the values seen in the source unless otherwise noted.

Step-by-Step Resolution Procedure

1. Confirm the symptom baseline. With the project set to CPU only (no slave), download HWConfig and CFC. ECO should be 0 and H6 steady. If not, the problem is in HWConfig / rack, not in PROFIBUS.
2. Add the slave in ComProfibus. Insert the Balluff encoder at the desired address, verify I/O lengths, save, and generate the binary master configuration.
3. Download the binary master configuration to the CP50M0. Use the ComProfibus online functions. This step is independent of the STEP 7 / CFC download and is frequently skipped by first-time users.
4. Add the in/out telegram wiring in CFC for the new slave (one in-block, one out-block, matched to the slave's address and the I/O lengths from ComProfibus).
5. Compile and download the CFC chart to the CPU550.
6. Observe the CP50M0 and CPU indicators. H6 returns to steady, ECO returns to 0. If H6 still blinks, proceed to the extended diagnostics below.

Extended Diagnostics

If the symptom persists after the procedure above, walk this matrix in order. Each row contains a single, isolated check; resolve the first failure before re-testing.

Verification Procedure

Once the configuration is consistent, verify operation with the following checks:

1. Power-cycle the CP50M0 (or issue a controlled bus restart from the engineering station) and confirm that H6 returns to steady and ECO stays at 0 without operator intervention.
2. Force a known value on a slave input register from the slave's configuration tool and observe the corresponding CFC input pin updating at the configured PROFIBUS cycle.
3. Read the slave's diagnostic buffer through ComProfibus. It should show no configuration errors and no watchdog events.
4. Read the CP50M0's diagnostic buffer. The startup sequence should be visible with no error events.
5. Document the working configuration: master address, baud rate code, slave address(es), I/O lengths, and CP50M0 firmware revision. Store the ComProfibus binary and the CFC chart in the project archive.

FAQ