Siemens RS485 Noise: It Is an EMC Path, Not a USS Fault

Follow the packet. The PLC sends a request, the RS485 transceivers and cable carry the differential signal, the drive parses the USS frame, and the response returns over the same pair. Communication is stable before the motor runs and fails when the motor is energized. That transition points to an electromagnetic-coupling or reference-voltage problem in the physical path, not to a protocol change.

Power filters, magnetic rings, an isolation transformer, and an RS485 repeater produced little or only partial improvement in this installation. Layer one first: correct the cable geometry, protective bonding, termination, bias, and routing before changing protocol logic.

Where does the RS485 packet stop?

Path element	Check	Failure indication
PLC or master	Confirm transmitted frames and request counters	No request leaves the master
Master transceiver	Observe the differential waveform at its terminals	Local waveform is already distorted
Twisted-pair cable	Compare waveforms at both physical ends	Clean at the master but distorted at the drive
Drive transceiver	Check whether valid requests produce responses	Clean request arrives but no response leaves
USS processing	Compare address, baud rate, framing, and request content	Electrically clean frames are rejected

Run the same request sequence with the drive powered but the motor stopped, then repeat it while starting and running the motor. If errors begin only with motor output active, inspect the cable path and common-mode voltage before editing USS logic. The proof for this stage is a recorded point along the path where a clean request becomes corrupted or disappears.

How should the A/B cable be connected and routed?

Use the two conductors of one twisted pair for A and B. Both conductors must have the same construction and follow the same physical route. Splitting them across different pairs destroys the balanced geometry that gives RS485 its noise rejection. Keep the untwisted length at terminals as short as practical and avoid long branches from the trunk to individual devices.

Route the communication pair away from drive output conductors and motor cables. Crossing a power cable is less troublesome than running beside it for a long distance; cross at approximately a right angle where separation cannot be maintained. Do not use the cable shield as an RS485 signal conductor.

Apply the shield-bonding method specified by the installed drive, cable, and site EMC design. One-end and two-end shield practices address different combinations of low-frequency ground potential and high-frequency coupling. Inspect the equipotential bonding path before selecting either method; a two-end shield connection can carry unwanted current when the endpoints are poorly bonded.

The check is physical: trace one continuous twisted pair from master to final node, document every splice and branch, and compare communication with the drive stopped and running after correcting the route.

How do protective earth and reference voltage affect the link?

Bond the drive protective-earth terminal, motor enclosure, and grounded panel structure through the intended protective and equipotential paths. Mounting a drive enclosure on a grounded panel does not by itself prove a low-impedance bond through paint, hardware, cable glands, and motor connections. Protective earth must not serve as a normal load-current return path.

RS485 receivers respond to the voltage difference between A and B, but each receiver also has a permitted common-mode range. Motor switching can move both conductors together relative to a transceiver reference. The differential data may still look recognizable while the common-mode voltage pushes the receiver outside its operating range.

1. Inspect the drive PE conductor and the motor-frame bonding conductor at both ends.
2. Check panel bonding surfaces, shield clamps, and cable-entry hardware.
3. Measure the RS485 differential waveform and the common-mode movement during motor start with suitable isolated or differential instrumentation.
4. Correct the bonding path before using communication isolation as a substitute for it.

The check passes when motor operation no longer causes excessive reference movement at either RS485 endpoint and protective bonding remains intact.

How should termination and idle bias be applied?

Setting	Location	Purpose	Recurring error
Termination across A-B	Physical ends of the trunk	Reduce reflections from impedance discontinuities	Installing terminators at arbitrary intermediate nodes
Nominal 120 ohm resistor	Only where it matches the cable and device instructions	Approximate the cited cable termination value	Treating 120 ohms as correct without checking the installed cable
Idle bias	One engineered point on the segment	Hold a defined differential state when no driver is active	Adding pull-up and pull-down networks at many nodes

With power removed and both devices disconnected as required by their manuals, resistance measurements can reveal termination errors. Under the labeled assumption that the segment has exactly two 120 ohm terminators and no other loading, the resistance across A-B is approximately 120 || 120 = 60 ohms.

One proposed bias network was +5 V - 3.3 kohm - A - 180 ohm - B - 3.3 kohm - GND, with the 180-ohm resistor replacing the original 120-ohm resistor. Its ideal unloaded differential voltage calculates as 5 V × 180 / (3300 + 180 + 3300) = 0.133 V, not 0.2 V. Transceiver loading and other bus resistors change that result. Treat the network as a configuration to calculate and measure, not as a universal replacement for termination.

The check is an oscilloscope trace with a stable idle state, clean transitions, and no large ringing at both physical ends while the motor is running.

When should an isolated repeater or filter be added?

Add an isolated RS485 repeater when measurements show that segmenting the cable or breaking the communication-reference path removes common-mode stress. Place it at the boundary between the noisy drive segment and the control segment. Terminate and bias each resulting segment according to its own topology; a repeater creates two electrical buses, not one longer bus.

A repeater produced only partial improvement here. That result indicates that some coupling path remained, such as motor-cable proximity, incomplete PE bonding, incorrect termination, or noise entering both repeater segments. Optical or magnetic isolation can protect communication electronics and interrupt a reference-current path, but it cannot repair poor cable geometry or a missing motor-frame bond.

Input filters, isolation transformers, RC networks, and ferrites address particular frequency ranges and coupling modes. Select them from measurements and the drive installation requirements. Adding them without locating the coupling path can leave the RS485 failure unchanged. The check passes only when the added device produces a repeatable improvement under the same motor-start and load test.

How is the complete USS link verified?

Item	Installation value or decision
Siemens drive protocol	USS
Other cited drive protocol	Modbus
Problem installation baud rate	9600 bit/s
Reported Siemens MM4 examples	19200 bit/s with fewer drives; 57600 bit/s with more closely grouped drives
Node address and frame settings	Read from the master and installed drive; no parameter identifiers were specified

Baud rate changes alter bit timing but do not repair grounding, routing, or termination. Verify every layer in a controlled sequence:

1. Record request, response, retry, timeout, and checksum-error counts with the motor stopped.
2. Start the motor repeatedly and run it through the operating range while sending the same requests.
3. Observe A-B at the master and final drive, including idle periods and direction changes.
4. Confirm the configured USS address, baud rate, framing, and master polling sequence.
5. Run a sustained test longer than the previously observed time-to-failure. If communication later stops and returns only after drive power cycling, inspect drive diagnostics and master timeout state before declaring an EMC fix.

The end-to-end check passes when every transmitted request reaches the addressed drive, every expected response returns without rising error counts, and motor starting or running does not change that result.

FAQ