Configuring Siemens CP50M0 PROFIBUS DP Master on SIMATIC TDC
The Siemens CP50M0 is the PROFIBUS DP master interface module used in SIMATIC TDC (Technology and Drive Control) racks and in its predecessor platform, SIMADYN D. Despite the modern migration of fieldbus engineering to TIA Portal, hundreds of TDC installations are still in service worldwide and depend on the legacy COMProfibus V5.1 tool, a CP5611 PCI card, and a proprietary Siemens service cable for commissioning and maintenance. This reference explains how the CP50M0 is parameterized, why the COMProfibus Import command does not work for this station type, and the correct Export-DP Master procedure that downloads the configuration into the module over CP5611.
.pdb / .cpt project file is lost, the configuration must be re-entered manually against the wiring documentation.1. CP50M0 PROFIBUS Master Overview in SIMATIC TDC
The CP50M0 is a communications processor module that occupies one slot in the SIMATIC TDC subrack. It provides a single PROFIBUS DP master channel at RS-485, 9.6 kbit/s up to 12 Mbit/s, conforming to EN 50170 Volume 2 (PROFIBUS DP). It communicates with the TDC CPU module (SS52 family) over the backplane and exchanges process data with the application memory in deterministic cycle times.
| Parameter | Value |
|---|---|
| Module family | SIMATIC TDC communications processor |
| PROFIBUS role | DP master class 1 |
| Bus interface | 9-pin sub-D female (RS-485), isolated |
| Baud rates | 9.6 / 19.2 / 45.45 / 93.75 / 187.5 / 500 / 1500 kbit/s; 3 / 6 / 12 Mbit/s |
| Max. DP slaves | 32 per segment (124 with repeaters, segment design rules apply) |
| Cyclic I/O per slave | Up to 244 bytes input / 244 bytes output |
| Configuration host | COMProfibus V5.1 over CP5611 / CP5613 / CP5511 / CP5512 |
| Parameter port | Service cable from CP5611 to TDC rack (proprietary, see TDC Hardware Manual) |
| Slot width | 1 slot, double-height front connector |
| Status indication | Front-panel LEDs: RUN, STOP, BF (bus fault), SF (system fault), DP |
Inside COMProfibus, the CP50M0 is registered under the master station type Simadyn D SS52 because the firmware image, the bus parameter record layout, and the configuration download protocol were inherited from the SIMADYN D platform. Choosing any other station type (IM308-C, IM180-V3, S5-95U DP/Master) will produce a project that the module rejects.
2. Prerequisites and Required Components
Before attempting any configuration exchange with a CP50M0, the following items must be available.
| Item | Specification |
|---|---|
| Engineering PC | PC with PCI slot for CP5611 (or PCMCIA / ExpressCard slot for CP5511 / CP5512) |
| PROFIBUS interface | Siemens CP5611 (6GK1561-1AA01), or CP5613 / CP5614 for higher baud rates |
| Driver | SIMATIC NET PC software, version matching COMProfibus (V6.x or V7.x for legacy PG) |
| Configuration tool | COMProfibus V5.1 (latest released build) |
| Service cable | Siemens cable between CP5611 and the TDC parameterization port (ordered against the TDC Hardware Manual) |
| Operating system | Windows XP SP3 / Windows 2000 (officially supported); Windows 7 (with restrictions, see §7) |
| Project archive | Existing .pdb / .cpt COMProfibus database, if available |
SIMATIC NET Diagnostics > CP5611 > Firmware Version. CP5611 hardware revisions A02 and later are required for stable 12 Mbit/s operation with COMProfibus V5.1.3. Why CP50M0 Import Fails in COMProfibus
The CP50M0 firmware does not implement the upload protocol expected by COMProfibus for the Import menu path. When the operator opens COMProfibus and selects File → Import..., the tool enumerates the three master types it can read from a live module:
- IM308-C (for S5-135U/155H racks)
- IM180-V3 Master (S7-400 stand-alone DP master)
- S5-95U DP/Master (S5-95U PLC)
CP50M0 is not in this list because the upload protocol used by SIMADYN D SS52 does not expose the binary parameter set in a form that COMProfibus can re-parse. The tool will display the dialog, but selecting any of the three stations produces no response from the module even when the CP5611 is logically linked and the LEDs indicate a healthy parameterization link.
Implications for the field engineer
- If the original COMProfibus project file exists on a backup medium, restore it and edit that file.
- If the project file is lost, reconstruct the configuration from the wiring diagram and the I/O address list of the TDC application. The CP50M0 does not retain human-readable documentation of its slaves.
- Treat any clone or spare module as blank and always download a fresh project before commissioning.
4. Correct Configuration Workflow: Simadyn D SS52
The supported workflow assumes the engineer is creating or editing the project offline and pushing the result into the module.
- Launch COMProfibus V5.1.
- From File → New, create a project and select the master station type Simadyn D SS52. The dialog will not offer CP50M0 by name; SS52 is the correct logical target.
- Open Master → Parameters and set:
- Bus profile (Standard / User-defined)
- Baud rate matching the installed slaves
- Slot time, quiet time, setup time, target rotation time (TTR)
- Watchdog and group assignment
- Add slaves from the GSD catalog (Slave → Insert) and assign I/O bytes per the TDC application interface definition.
- Save the project as a
.pdbfile in a versioned folder structure (e.g.\\plant\t-dc\unit-01\cp50m0\pdb\rev07\).
Bus parameter reference
| Parameter | Typical value | Notes |
|---|---|---|
| Baud rate | 12 000 kbit/s | Must be identical on every slave GSD |
| Slot time (TSL) | 1 000 bit-times | Derived from GSD of slowest slave |
| Min. station delay (min TSDR) | 11 bit-times | Per EN 50 170 |
| Max. station delay (max TSDR) | 150 bit-times | Calculate from longest telegram |
| Quiet time (TQUI) | 0 (auto) | |
| Setup time (TSET) | 1 bit-time | |
| Target rotation time (TTR) | 3 000 000 μs | Lower bound = sum of all slave cycle times |
| GAP factor | 10 | |
| Highest station address (HSA) | 126 | Unless reduced deliberately |
| Retry limit | 3 |
5. Export-DP Master Download Procedure
Once the project compiles cleanly, the configuration is pushed to the CP50M0 by the Export-DP Master command. The dialog wording is historical and does not perform a file export; it initiates a parameter download to the module.
- In COMProfibus, with the project open, right-click the Simadyn D SS52 master icon in the tree view.
- Select Export-DP Master.... The download dialog opens.
- Confirm the CP5611 is selected as the access point (PG/PC interface = CP5611(PROFIBUS)).
- Connect the service cable between the CP5611 9-pin sub-D and the TDC parameterization port (front X1 of the rack).
- Switch the CP50M0 to STOP using the toggle switch on the front panel or via the TDC operator panel.
- Click Start in the Export-DP Master dialog. The progress bar indicates parameter block transfer.
- Watch the CP50M0 front-panel LEDs:
-
STOPLED solid during transfer -
SFLED flashing during parameterization - Successful end:
STOPLED off,RUNLED green
-
- When the dialog reports Transfer OK, switch the module back to RUN and verify DP slaves come online.
Failed-transfer matrix
| Symptom in COMProfibus | CP50M0 LED pattern | Root cause | Corrective action |
|---|---|---|---|
| Connection timeout | All LEDs off | Service cable not seated or CP5611 driver not loaded | Re-seat cable, restart SIMATIC NET service |
| Slave rejection on first poll | BF flashing 1 Hz, RUN off | Wrong baud rate or wrong station address on a slave | Compare GSD settings with physical DIP switches |
| CRC error in parameter block | SF solid red | Service cable too long or near VFD cable | Route cable > 200 mm from power conductors |
| Station does not respond | STOP solid, SF solid | Module in wrong firmware state | Power-cycle the TDC subrack, retry |
6. CP5611 Interface Installation and Driver Setup
The CP5611 (Siemens part number 6GK1561-1AA01) is a PCI card that provides both MPI and PROFIBUS interfaces to the engineering PC. COMProfibus V5.1 cannot operate without a properly installed CP5611 driver layer.
- Insert the CP5611 in a free PCI slot and boot Windows.
- Install SIMATIC NET PC Software V6.4 SP4 or V7.1 (matching COMProfibus V5.1 compatibility matrix).
- In Set PG/PC Interface, choose
CP5611(PROFIBUS)as the access point of the application COMProfibus. - Open SIMATIC NET Diagnostics, select the CP5611, and verify:
- Firmware version is visible
- Bus status shows Online when connected to an active bus
- Node address is set (default 0; for point-to-point service cable set to 0 or 1 depending on TDC rack)
- If the CP5611 is used in diagnostic mode (read-only), set PG is the only master on the bus in the access point properties to avoid bus parameter conflicts with the CP50M0 acting as DP master.
7. COMProfibus V5.1 on Windows 7 Compatibility
COMProfibus V5.1 was developed before Windows 7 existed and is not officially certified by Siemens for that operating system. Field experience shows mixed results:
| Scenario | Behavior | Mitigation |
|---|---|---|
| Installation on Windows 7 32-bit | Installs with compatibility warning; SETUP.EXE must be run as administrator |
Right-click → Run as administrator; set compatibility to Windows XP SP3 |
| Installation on Windows 7 64-bit | Not supported natively | Use a Windows XP Mode VM or replace PG with Windows XP |
| COMProfibus launch | COM port enumeration fails on first run | Run as administrator; reinstall SIMATIC NET CP5611 driver |
| Export-DP Master | Works once driver is functional, but unstable on USB-connected CP5511 / CP5512 | Prefer CP5611 (PCI) over CP5511/CP5512 |
| UAC prompts | Block writes to ProgramData and Users folders |
Disable UAC for the COMProfibus shortcut, or store projects outside Program Files
|
| Sleep / hibernate | CP5611 driver crashes on resume | Disable sleep on the engineering PG; reboot before each session |
For long-term reliability on a Windows 7 PG, install COMProfibus V5.1 inside a virtualized Windows XP environment (VMware, VirtualBox) and present the CP5611 as a passthrough or use a USB-to-PROFIBUS adapter (CP5711) bridged into the VM. The native Windows 7 path is workable for occasional parameter downloads but should not be used for factory acceptance tests.
8. Cable Connection: CP5611 to TDC Rack
The service cable referenced in the TDC Hardware Manual is not a stock PROFIBUS cable. It carries the DP signals plus the parameterization handshake on a separate pin pair that the CP50M0 exposes for engineering access. The cable must be ordered as a spare part from Siemens; field-built substitutes risk damaging the parameterization port.
| CP5611 sub-D pin | Signal | TDC front connector pin | Function |
|---|---|---|---|
| 3 | RxD/TxD-P (B) | A1 | PROFIBUS data P |
| 5 | DGND | A2 | Data ground |
| 6 | VP (+5 V) | A3 | Bus termination supply (not used on service cable) |
| 8 | RxD/TxD-N (A) | A4 | PROFIBUS data N |
| 4 | RTS | B1 | Parameterization handshake (PG-to-TDC direction) |
| 1 | Shield | Shell | Cable shield, bonded at both ends |
9. Modernization Path: Migrating to TIA Portal
For new TIA Portal-based controllers (S7-1200, S7-1500, ET 200SP) that need to communicate with the existing CP50M0 / TDC bus segment, the CP50M0 remains the PROFIBUS DP master. The S7-1200 / S7-1500 stations are configured as DP slaves and integrated as PROFIBUS devices in the TIA Portal project. See the official Siemens configuration guide:
When a TDC rack is being decommissioned in favor of an S7-1500 + PROFIBUS master, the workflow is:
- Read the existing COMProfibus project, or rebuild from the wiring documentation.
- Create a TIA Portal project, add the S7-1500 CPU and the CP 1542SP-1 / CM 1542-1 PROFIBUS master module.
- Insert each DP slave from the GSD library using the same addresses as the legacy CP50M0 configuration.
- Map the cyclic I/O to the S7-1500 process image; mirror the data-block offsets used by the TDC application.
- Perform a side-by-side cutover with the COMProfibus project archived for fallback.
Conversely, if the S7-1200 / S7-1500 is the DP master and the TDC remains as a slave station, it is rarely practical: the CP50M0 firmware does not expose a DP slave mode. Migration scenarios therefore favor replacing the CP50M0 + TDC with a SIMOTION or S7-1500 + CP 1542 combination.
10. Diagnostic Reading and Troubleshooting
Live diagnostic data from a DP slave can be read from a STEP 7 / TIA Portal CPU using the DPNRM_DG instruction (read diagnostic data from a PROFIBUS DP slave). The function returns the standardized diagnostic buffer defined by EN 50 170 Volume 2, which includes station status, manufacturer-specific diagnostic bytes, and module status. Reference: DPNRM_DG instruction - S7-1200 manual collection, TIA Portal V20.
Although DPNRM_DG runs on an S7-1200 / S7-1500, the same diagnostic frame structure is broadcast by the CP50M0 on the bus and can be captured by COMProfibus online diagnostics:
- In COMProfibus, choose Online → DP Diagnostics.
- The tool polls every active slave and displays station status byte 1 and 2.
- For extended manufacturer-specific diagnostics, double-click the affected slave — COMProfibus parses the GSD-declared diagnostic blocks.
CP50M0 LED state decoding
| RUN | STOP | BF | SF | Meaning |
|---|---|---|---|---|
| Green | Off | Off | Off | Master cyclic, all slaves in data exchange |
| Green | Off | 1 Hz flash | Off | One or more slaves missing or failed |
| Off | Yellow | Off | Off | Module stopped by operator, bus parameterization retained |
| Off | Yellow | Off | Red 2 Hz | Project download in progress |
| Off | Off | Red solid | Red solid | Hardware fault or wrong master station type downloaded |
| Green 0.5 Hz | Off | Off | Off | Master in cold-restart, waiting for application handshake |
11. Verification, Commissioning, and Acceptance Test
After a successful Export-DP Master, execute the following acceptance sequence before handing the TDC rack back to operations.
- Power-cycle the CP50M0 to confirm the project survives a cold restart.
- Compare the cyclic I/O image in the TDC application against the COMProfibus project — every configured slot must show the expected byte count.
- Disconnect one slave and verify the BF LED changes state within one bus cycle (TTR).
- Reconnect the slave and confirm automatic recovery without operator action.
- Capture the COMProfibus online diagnostic buffer and archive it in the project folder
acceptance/<date>/. - Update the wiring diagram revision number and store the new
.pdbin the same folder, renamed with the date.
.pdb project file and the COMProfibus Protocol printout (PDF). The PDF records the exact bus parameters that were downloaded and is the only document that survives a future COMProfibus version migration.Troubleshooting Matrix
| Symptom | Likely cause | Diagnostic step | Fix |
|---|---|---|---|
| Import command does nothing | CP50M0 firmware does not support upload | Stop attempting import; reconstruct project | Edit .pdb offline, then Export-DP Master |
| Export-DP Master times out | CP5611 driver not running | SIMATIC NET Diagnostics → CP5611 status | Restart S7DpComm service |
| Slave fails to enter data exchange | GSD version mismatch | Compare GSD revision with slave firmware sticker | Update GSD in COMProfibus catalog |
| Random bus errors after switch-on | Missing shield bond on service cable | Measure shield continuity at both ends | Replace cable; verify 360° shield termination |
| BF LED solid after firmware change | Wrong master station type downloaded | Inspect downloaded bus profile | Re-export with Simadyn D SS52 selected |
| CP50M0 will not enter RUN | Application handshake missing | Check TDC CPU program for CP50M0 slot enable | Restore TDC application from project archive |
Frequently Asked Questions
Can I import a CP50M0 configuration back into COMProfibus?
No. The CP50M0 firmware, configured as Simadyn D SS52, does not implement an upload protocol that COMProfibus V5.1 can parse. The Import command in COMProfibus will only respond to IM308-C, IM180-V3, and S5-95U DP/Master stations. Always archive the original .pdb project file and a printed parameter protocol.
What station type must I select for the CP50M0 in COMProfibus?
Select Simadyn D SS52 as the master station type when creating the COMProfibus project. The CP50M0 is the TDC-platform module that shares its PROFIBUS stack with the SIMADYN D SS52 CPU, and any other choice will produce a project the module rejects with the SF LED solid red.
Is COMProfibus V5.1 supported on Windows 7?
Officially no. Windows 7 32-bit will run COMProfibus with administrator rights and Windows XP SP3 compatibility, but the SIMATIC NET CP5611 driver can crash on resume from sleep. For reliable operation use Windows XP, or run COMProfibus inside a Windows XP virtual machine with the CP5611 or CP5711 presented as passthrough.
Which Siemens interface card do I need to download the configuration?
Use a CP5611 (PCI), CP5613, CP5614, or the PCMCIA / ExpressCard variants CP5511 / CP5512. The CP5611 is the most common choice for TDC service work and requires the SIMATIC NET PC software V6.4 or V7.1 driver set selected under Set PG/PC Interface → CP5611(PROFIBUS).
Can a CP50M0 act as a DP slave to an S7-1500 master?
No. The CP50M0 is a DP master class 1 module and does not support slave mode. To replace a TDC station with an S7-1500 system, use a CP 1542SP-1 or CM 1542-1 PROFIBUS master module in the S7-1500 station and migrate the existing DP slaves into the TIA Portal project as documented in the TIA Portal V20 PROFIBUS DP configuration guide.