How-to
Installing a robust PROFIBUS DP network inside an MCC
Short answer
Run the bus at or below 1.5 Mbit/s, keep the cable against the bonded backplane, clamp the shield to bonded metalwork at every MCC entry, and terminate only the two electrical ends of the segment: a slower rate widens timing margins but cannot fix poor bonding or missing termination.
On this page
A robust PROFIBUS DP segment inside a retrofit MCC is won by installation, not by slowing the bus. Cap the transmission rate at 1.5 Mbit/s, hold the cable against bonded metal with the greatest separation from power conductors the gutter allows, clamp the shield to bonded metalwork at every MCC entry rather than pigtail-landing it, and switch termination on at exactly the two electrical ends of the segment. Ground every node; terminate two. A slower rate widens timing margins, but it never repairs a bad bond or a missing terminator. What replaces the bucket hardware — a contactor and overload versus an intelligent starter — is a separate selection; settle motor starter vs contactor first, then build the network to survive the gutter it must share.
What the rate allows: segment length first #
PROFIBUS DP is a profile of the IEC 61158 fieldbus standard running an RS-485 physical layer, so the segment obeys transmission-line rules: one cable, daisy-chained from node to node, terminated at both ends, and inside the length the chosen rate allows. The segment table in the PROFIBUS installation guideline, for the cable type it specifies:
| Transmission rate | Maximum segment length |
|---|---|
| 9.6 to 187.5 kbit/s | 1000 m |
| 500 kbit/s | 400 m |
| 1.5 Mbit/s | 200 m |
| 3 to 12 Mbit/s | 100 m |
At the 1.5 Mbit/s ceiling, one segment may carry 200 m of cable — several times the route of any single MCC lineup, which is why length is rarely the constraint in a bucket retrofit; coupling and shield treatment are. 12 Mbit/s halves the allowance to 100 m and leaves the least margin for reflections and stubs, which makes it the wrong rate for a shared gutter. Confirm the table values against your network documentation before locking the rate.
Route the bus through the shared gutter #
This work opens buckets that share a gutter with live power wiring: lock out, then test for absence of voltage with a rated instrument before routing any cable, as NFPA 70E, 2024 edition — the US standard for electrical safe work practices — requires; confirm the procedure with your plant's safety program, the local authority having jurisdiction, and the MCC documentation.
- Walk the full route and mark it: every bucket the bus enters, each vertical gutter run, and the crossing into the master's cabinet. Note where the power conductors, contactor coils, and any drive output cables actually run.
- Identify the loudest neighbors. Drive output cables couple the most into a communications cable; where a bucket feeds a drive, its power-side decisions belong to the same retrofit — see choosing a line or motor reactor for a VFD.
- Take the far side of the gutter from the power conductors and keep it: greatest separation the space allows, shortest parallel exposure you can mark.
- Hold the cable flat against bonded metal — backplane, gutter wall, structural steel — for as much of the route as the construction permits; a cable lying on bonded steel picks up far less than one floating in mid-gutter.
- Cross power wiring at right angles where a crossing is unavoidable, and never lengthen a parallel run to dodge one.
- Support the cable without crushing it, inside the bend radius the cable datasheet gives, and clear of removable-bucket travel and anywhere maintenance will pull.
- Compare the installed route against the marked one before the gutters close. If the marked route cannot be held, change the containment or the network architecture — not the baud rate.
Bond the shield at every MCC entry #
The installation guideline is explicit for segments that are not intrinsically safe: earth the shield at both ends and at multiple points along the segment. Inside one MCC, that means every entry and every node.
- Use the cable and bus connectors the device documentation specifies, and land the bus only on those connectors — never break it onto terminal strips.
- At each entry, strip only the few centimetres of jacket the clamp needs, and keep the braid continuous under the jacket for the whole run.
- Clamp the exposed shield 360 degrees to grounded backplane metal. A broad clamp is a high-frequency bond; a pigtail is an inductor, and a long one rejects almost nothing.
- Verify the clamp lands on metal that is actually bonded: backplane to section frame, section to section, and the lineup to the protective-conductor and equipotential system. Both-end earthing presumes that bonding; where a run leaves the MCC to a structure you cannot bond to, earth one end directly and treat the far end as the guideline directs for missing equipotential bonding.
- Inspect every clamp for shield contact rather than jacket contact, then continuity-check the bonding path. Continuity finds gross defects; the high-frequency proof is the diagnostic counters under load, in commissioning.
Terminate only the two electrical ends #
Grounding and termination are different jobs, and confusing them is the most common wiring error on these retrofits.
- Build one daisy chain: bus in and bus out at each connector, node to node, with no branches and no improvised transitions.
- Find the two electrical ends from the actual cable path, which can differ from the physical order of the buckets, and switch termination ON at those two connectors only.
- Switch termination OFF on every intermediate connector, and re-check the switches after any bucket has been withdrawn and reinserted.
- Keep the termination powered in every operating state. During commissioning, power down the end device and withdraw the end bucket: if the segment dies with them, the terminator lost its supply — fit a connector with its own power feed, as its instructions allow.
Commission at 1.5 Mbit/s and prove it #
- Set 1.5 Mbit/s with the segment at or under its 200 m allowance, and configure every node from its GSD file at the addresses you assigned.
- Read the physical layer with a PROFIBUS diagnostic tester or the master's counters: frame errors, retries, station dropouts.
- Exercise the MCC while watching those counters — start and stop the largest motors and let the contactor bank switch. Errors that track motor switching are coupling: fix separation and bonding, not the baud rate.
- Confirm the segment survives its maintenance states: withdraw a middle bucket, then repeat the end-device power-down that checked termination supply.
- Step down to 500 kbit/s or 187.5 kbit/s only after bonding and termination pass and the counters still move, then re-verify the process update time the slower scan imposes. A rate drop is the last knob, not the first.
- When a node answers on the bus but returns no data, suspect addressing and configuration before EMI; diagnosing an S7-300 PROFIBUS gateway that enumerates but reads no I/O works through that class of fault.
Worked example: a 1.5 Mbit/s segment across 12 buckets #
Inputs, each with its source:
- Transmission rate: 1.5 Mbit/s — the project ceiling.
- Maximum segment length at that rate: 200 m, from the guideline table above.
- Installed cable: 45 m, measured along the marked route from the master's connector, through the gutter, and daisy-chained across 12 buckets to the last connector. This is the input you measure at layout; the value here is illustrative.
- Nodes: 12 starters plus the master, so 13 connectors on the segment.
Rule in words: the installed length on one segment must stay at or below the table value for the chosen rate, and a segment carries exactly two terminations whatever its node count.
Arithmetic: 45 m ÷ 200 m = 0.225, so the route uses 22.5% of the allowed length, leaving 200 m − 45 m = 155 m of margin. Terminations: 2 of the 13 connectors switched ON — the master's and the last bucket's — and 11 OFF.
Decision: at 22.5% of the length budget, rate is not the constraint; commission at 1.5 Mbit/s and spend the commissioning hours on clamps and termination checks. The threshold: the moment this segment crosses 200 m of installed cable, 1.5 Mbit/s is off the table — drop to 500 kbit/s at up to 400 m or 187.5 kbit/s at up to 1000 m, or split the segment.
Questions asked
Does PROFIBUS error checking make a rough installation acceptable?
No. PROFIBUS detects damaged frames and retries them; retries consume bus time, and persistent errors eventually drop the station from the master's scan. A retry counter that climbs while motors switch is an installation defect with a name, not a condition to absorb.
Should the shield be earthed at one end to prevent ground loops?
Not here. For segments that are not intrinsically safe, the installation guideline earths the shield at both ends and at multiple points, with equipotential bonding between the structures verified first. Single-ended treatment is the guideline's answer for a run whose bonding cannot be secured, not a default for an MCC lineup.
Why not run 12 Mbit/s since the cable is shielded anyway?
Because 12 Mbit/s caps the segment at 100 m and leaves the least margin for reflections and stubs, while shielding only limits coupling. One MCC lineup does not need the throughput; 1.5 Mbit/s with 200 m of allowance and wide timing margin is the retrofit choice.
Can the bus be landed on terminal strips like conventional control wiring?
No. The bus runs connector to connector in one daisy chain. Every terminal-strip break or improvised branch changes the transmission line and reflects energy back along it, producing faults that look like interference but are geometry.