IMDHMIControls LibraryShop main store

How-to

Connecting an S7-1200 to a PROFIBUS slave through a CM 1243-5

Industrial networks Published 6 min read

Short answer

An S7-1200 cannot speak PROFIBUS from any built-in port: its onboard Ethernet is PROFINET. PROFIBUS DP-V1 master duty needs the CM 1243-5 communications module in the S7-1200 rack. Confirm the remote device is a PROFIBUS slave, import its GSD into TIA Portal, give it a bus address no other station uses, and terminate the segment at both ends.

On this page
  1. Why the CPU's own port cannot carry PROFIBUS
  2. Confirm the remote device is a PROFIBUS slave
  3. What you need
  4. Configure the master system and the slave
  5. Worked example: bus addresses for one master and one slave
  6. Commissioning checks that prove the link
  7. The decision for each case
  8. Questions asked

An S7-1200 cannot talk PROFIBUS by itself: the port on the CPU is PROFINET Ethernet, and PROFIBUS is a separate network on its own physical interface. To connect PROFIBUS slave devices, fit a CM 1243-5 communications module in the S7-1200 rack — Siemens documents it as the module that connects an S7-1200 to PROFIBUS as a DP-V1 master — then configure the remote device as a DP slave from its GSD device description, give it a bus address nothing else on the segment holds, and terminate the segment at both ends. Check the remote device before you order the module: it needs a PROFIBUS DP slave interface, not just a socket the cable fits.

Why the CPU's own port cannot carry PROFIBUS #

What the S7-1200 has on board is an Ethernet interface running PROFINET. PROFIBUS is a separate fieldbus with its own signaling, frames and connector, and nothing in the CPU creates a path between them — that is why the answer to an S7-1200 PROFIBUS job is a communications module, not a cable.

The CM 1243-5 is the module documented for exactly this duty, and its technical specification gives the bus connection as a 9-pin D-sub female connector. It mounts on the S7-1200 rack beside the CPU like any other S7-1200 module.

Controllers that carry PROFIBUS on board need none of this — an S7-300 driving a PROFIBUS drive from the CPU's DP port is that arrangement. The S7-1200 has no DP port, so the module is the path.

Confirm the remote device is a PROFIBUS slave #

A connector that fits proves nothing. Read the device nameplate and manual for two facts before wiring:

  • Does the device have a PROFIBUS DP interface at all?
  • Is it configured as a DP slave?

The CM 1243-5 arrangement makes the S7-1200 the master, so the remote device must be the slave. If the device only ever works as a PROFIBUS master, no direct master-to-slave link exists between the two, and no wiring changes that — the architecture has to change.

If the device turns out to be Ethernet-only, leave it on Ethernet: connect it through a switch to the S7-1200's PROFINET port, or bridge the two sides with a gateway documented for both protocols — the same idea as a PLC bridging Modbus RTU devices onto PROFIBUS.

If it is a genuine DP slave, collect three things from its documentation: the GSD device description file, its parameter set, and the method for setting its bus address.

What you need #

  • A CM 1243-5 module, checked in Siemens' documentation against your CPU for module support.
  • PROFIBUS cable, shielded twisted pair, as specified in the device manuals.
  • A 9-pin D-sub PROFIBUS connector at every station, each with a terminating-resistor switch.
  • The slave's GSD file and manual.
  • TIA Portal with support for your CPU and the module.

De-energize the rack before fitting the module and make sure the machine cannot start while you work — the PROFIBUS job never justifies skipping the lockout.

Configure the master system and the slave #

  1. Fit the module. Rack power off, mount the CM 1243-5 beside the CPU per its installation instructions, power up, and confirm in the CPU diagnostics that it is recognized without a hardware fault.
  2. Wire the segment. Run the PROFIBUS cable to every station on its own connector, shield landed per the connector design. Switch terminating resistors ON at exactly the two end connectors and OFF everywhere else. In the standard terminating connector the resistors are fed through the connector from the station, so a powered-down end station loses termination — keep both end stations powered or fit an active terminating element.
  3. Set the slave's address at the device, using the method its manual documents, and write it on the drawing.
  4. Add the master. In the TIA Portal device configuration, add the CM 1243-5 to the S7-1200 and create the DP master system on its PROFIBUS interface.
  5. Import the GSD. Bring the slave's GSD in through the device catalog's device-description import so the slave appears in the catalog.
  6. Place the slave. Drag it onto the DP master system, set its bus address to the number from step 3, and build its slot configuration and parameters exactly as its GSD and manual define.
  7. Compile and download the hardware configuration to the CPU.
  8. Go online and read bus diagnostics from the master and the slave.

The master and slave must also agree on the bus baud rate. Both sides on a PROFIBUS segment auto-negotiate the signaling rate, which the standard defines from 9.6 kbps up to 12 Mbit/s, so you normally leave the rate at its default — but note it on the drawing if your segment runs at the top rate, because cable length limits shrink as the rate rises.

Worked example: bus addresses for one master and one slave #

Inputs:

  • Master: the CM 1243-5 in the S7-1200 rack, planned at address 2 — a free number of your choosing; low numbers for masters are convention, not a rule.
  • Slave: the remote DP device, whose address selector reads 3 — set and read at the device per its manual.
  • Range: PROFIBUS station addresses run from 0 to 126.

The rule: every station on the segment holds exactly one address, unique on that segment, within 0 to 126, and the address entered for the slave in TIA Portal must equal the address set at the device.

Arithmetic:

  • Used addresses: {2, 3}.
  • Duplicate check: 2 ≠ 3 and the segment holds two stations, so no duplicate.
  • Range check: 0 ≤ 2 ≤ 126 and 0 ≤ 3 ≤ 126, so both addresses are valid.
  • Next free address: 3 + 1 = 4.

Result: the plan is valid — compile, download, commission.

Decision: commission when the two addresses differ, both sit inside 0 to 126, and the project entry matches the selector. Had the selector read 2, the slave would have duplicated the master and the master's diagnostics would show it faulted or missing — fix that at the device, never in the project. Note "master 2, slave 3, next free 4" on the panel drawing so the next device takes 4.

  • Module online: the CM 1243-5 appears in the online hardware with no module or configuration fault.
  • Slave online: in the DP master system's online view the slave sits at its configured address in data exchange — not missing, not in a parameterization error.
  • Data moves: write a known, safe value from the PLC to a slave output and watch a slave input the manual documents as changing; both must land in the PLC tags.
  • Slave diagnostics: the slave's own diagnostic buffer reports no configuration or parameter fault.

Once the bus runs, make its loss loud: the SCADA alarm that fires when PLC communication drops turns a broken segment into an alarm at the operator station instead of stale values on screen.

The decision for each case #

  • Remote device with a PROFIBUS DP slave interface: fit the CM 1243-5, import its GSD, assign the unique address, terminate both ends — the route in this article.
  • Remote device with Ethernet only: no PROFIBUS module; connect it on the Ethernet side through the S7-1200's PROFINET port, or use a gateway documented for both protocols.
  • Remote device that only works as a PROFIBUS master: no direct link into this arrangement; configure it as a slave if its manual allows, or move the connection to a gateway or the Ethernet side.
  • Addresses unique, in 0 to 126, project matching the device: download and commission. Anything duplicated or out of range stops the bus until it is fixed at the device.

Questions asked

Can an adapter turn the S7-1200 Ethernet port into PROFIBUS?

No. PROFIBUS runs RS-485 signaling on a 9-pin D-sub connector; the S7-1200 port is Ethernet on an RJ45 jack. An adapter only joins two incompatible physical layers, and neither protocol stack recognizes the other's frames, so no communication results. PROFIBUS reaches the S7-1200 through the CM 1243-5 module, and the Ethernet port stays with PROFINET, HMI and SCADA traffic.

Where is the slave's PROFIBUS address set?

At the slave device, by whatever its manual documents: rotary or DIP selectors, a display menu, or its own configuration software. Set it before wiring, note it on the drawing, and enter the same number for that slave in TIA Portal. An address typed only into the master project never reaches the device, and a mismatch leaves the slave unreachable after the download.

Does the CM 1243-5 do anything besides cyclic I/O exchange?

Yes. It is a DP-V1 master, so alongside the cyclic input and output data in the PLC process image it supports acyclic reads and writes, which is the path engineering and diagnostic access uses to reach slave parameters and diagnostic records. Which records a particular slave exposes comes from its GSD and manual, not from the master module.

What happens if an Ethernet-only device is wired into the PROFIBUS segment anyway?

It never answers. The device has no PROFIBUS stack, so the DP master system reports that slave as missing at its configured address and the segment stays faulted. The fix is architectural, not electrical: connect the device on the Ethernet side through the S7-1200's PROFINET port or a documented gateway, and keep it off the PROFIBUS cable.

Keep reading

  • How-to

    CompactLogix MSG to SLC 5/04 through a DH+ gateway

    The CIP path in the CompactLogix MSG ends at the 1756-DHRIO module in the remote chassis. On the MSG configuration tab, change the communication method from CIP to DH+, then enter Channel A and the SLC 5/04 node address in the DH+ fields; the SLC is never part of the path itself.

    Industrial networks

  • How-to

    How to route a ControlLogix MSG to a PLC-5 over DH+

    The CIP path is 1,5,2,10.60.28.60,1,2 and it ends at the 1756-DHRIO: out the local backplane to the ENBT/A in slot 5, over Ethernet to the bridge ENBT/A at 10.60.28.60, then across the bridge backplane to the DHRIO in slot 2. DH+ carries no CIP, so Channel A and DH+ node 67 are set on the message's communication tab, never appended to the path.

    Industrial networks

  • Troubleshooting

    Troubleshooting ControlNet scanning of legacy 1771 specialty I/O

    When a legacy 1771 specialty module will not scan over ControlNet, separate three layers before touching hardware: the chassis backplane allows two master/slave connections and each expander-class module takes one, the TIC-chip ASIC conflict applies to specific pairs only, and RSLogix 5000 gives you no configuration wizards for 1771 block transfer. Bench-test the exact module-and-chassis combination before go-live.

    Industrial networks