Direct Answer
The gateway is online but devices connect intermittently; you keep going on site and finally find it is a wiring problem. Eight out of ten RS485 faults are wiring-related: daisy-chain bus topology, A/B not reversed, a 120Ω termination resistor at each end, shield grounded at one end only, and bus length and node count controlled; follow these five rules and stability improves dramatically. The ESX/CW/CX series RS485 downlinks are wired by these five rules, and the site works first time.
A scene: a project's gateway was online but meters connected intermittently — three site visits found nothing — finally it turned out the star branches were too long and there was no termination resistor at the end — after changing to daisy-chain topology and adding a 120Ω resistor, it stabilized. Ten of ten RS485 pits are in the wiring — follow the five rules and intermittent connections become stable.
1. Bus Topology: Daisy Chain, Short Branches
Standard topology — daisy chain: from gateway to device, one after another in series — one device at each end, no break in the middle; Branch limit — branches (T-taps) should be as short as possible: ≤1 m recommended — long branches reflect signals and distort waveforms; Star mistake — many long wires fanning out from one point (star) — signal reflections stack up, and beyond a distance it connects intermittently; Retrofit principle — if the site is already star: change to daisy chain where possible; otherwise shorten branches and add termination compensation.
In one sentence: RS485 is "one bus strung end to end" — daisy-chain topology with branches ≤1 m — a long star branch is the number-one cause of intermittent connections.
A topology example: 8 meters in a switch room wired as a star with branches up to 15 m — the meters at the ends connected intermittently — changed to daisy-chain series with branches shortened to under 1 m — all stable. Set the topology first: daisy chain is the default answer for RS485; star is the most common site mistake.
2. A/B Polarity: Reversal Is the Most Hidden Mistake
Polarity definition — RS485 uses A/B two wires (also D+/D-): A to A, B to B — different vendors label differently (A+/B- or D+/D-); Reversal symptom — A/B reversed: device completely offline or occasional communication errors — no fault code, the most hidden; Quick check — one device offline: swap A/B first and test — if it works, it was reversed; several offline: check the gateway-side polarity; Unified labeling — standardize the "A/B" labeling before construction to avoid "A+/B-" mixed labels — unified labels halve the troubleshooting.
In one sentence: A/B reversed does not report an error, it just fails — "swap and test first" is the first troubleshooting move — unified labels prevent it at the source.
A reversal example: 3 meters totally offline in a project — gateway fine, baud rate fine, addresses fine — after swapping A/B, all connected — polarity reversal is the most hidden mistake, and the first troubleshooting move is the swap. A polarity error reports no fault code — a reversed meter stays "completely silent"; swapping A/B tells you in one test.
3. The 120Ω Termination Resistor: Position Matters More Than Presence
Purpose — the 120Ω termination resistor absorbs end reflections: the signal at the line end no longer bounces — clean waveform, stable communication; Position — one at each of the two far ends only: one at the head (gateway side), one at the farthest device — no resistor in the middle; Common mistake — the resistor added at a middle device: reflections not eliminated, signal wasted — as good as not added; Count — two buses, two sets of termination resistors: each bus has one at each end — do not share across buses.
In one sentence: the 120Ω termination resistor is "one at each end, none in the middle" — the wrong position equals not having it — absorb the end reflection and the waveform is clean.
A resistor example: intermittent communication errors on a project — all configuration checked and correct — the inspection found the termination resistor on the 4th device in the middle — moved to the two ends and it stabilized. The termination resistor is not a "did you add it" question, it is a "did you add it in the right place" question — both ends, and a misplaced one is useless.
4. Shield Grounded at One End: One End Is Right
Shield purpose — the shield blocks external interference (especially near motors and VFDs) — but grounded the wrong way it becomes an interference source; Single-ended grounding — ground the shield at one end only (usually the gateway side) — grounding both ends forms a ground loop and loop current interference; Common-ground handling — devices and the gateway share ground: ground potentials align, and the A/B differential stays stable — add isolation when not sharing ground; Check method — are both shield ends grounded? Change to single-ended — if it is intermittent and VFDs are nearby, check the shield grounding first.
In one sentence: the shield is "grounded at one end" — both ends cause loop current backlash — if it is intermittent near a VFD, check the shield wiring first.
A grounding example: VFDs ran alongside the cable tray in a plant — communication intermittently failed — both shield ends grounded formed a ground loop — after changing to single-ended grounding it stabilized. Grounding the shield at both ends creates interference of your own — single-ended is the standard answer; once the loop is gone, communication is stable.
5. Length, Node Count and Baud Rate: The Triangular Trade-off
Length limit — RS485 conventionally runs 1200 m (at 9600 bps) — the longer the distance, the lower the baud rate, and vice versa; Node limit — ≤32 nodes per bus (standard load) — more devices need grouping across multiple buses; Baud-rate trade-off — 9600 bps is stable (long distance), 115200 bps is fast (short distance) — choose between speed and stability; Field experience — a switch room is usually under 300 m with ≤32 nodes: 9600–19200 bps is the most stable — do not chase high speed.
In one sentence: length × node count × baud rate form a triangular relationship — in a switch room, 300 m, ≤32 nodes and 9600 bps is the most stable — choose stability over speed.
A trade-off example: a project set 115200 bps for speed — fine within 80 m, packet loss beyond 120 m — after lowering to 19200 bps, it was stable within 200 m. Baud rate is not "the faster the better" — distance and stability are computed first, and the rate follows the site.
6. Common Misconceptions: Three "Of Course" Assumptions in RS485 Wiring
Misconception one: no shield grounding is fine — fine without interference on site, exposed the moment a VFD appears — shield grounding is standard, not optional; Misconception two: add termination resistors anywhere — a resistor at a middle device leaves the reflection and worsens the signal — position matters more than count; Misconception three: more devices means raise the baud rate — more devices slow polling, and a higher rate is even less stable — group nodes, do not raise the rate.
In one sentence: three "of course" assumptions map to three rules — ground the shield, resistors at both ends, group nodes — do not replace wiring standards with assumptions.
A misconception example: 40 devices on one bus at 57600 bps — polling timeouts and constant packet loss — the review: nodes exceeded without grouping, and the rate was too high without lowering. The five wiring rules are not a multiple-choice — topology, polarity, resistor, grounding and rate, not one can be skipped.
7. Back to FEXLINK: How RS485 Wiring Lands
To land the wiring logic on products: the ESX/CW/CX series RS485 downlinks are constructed by five rules — "daisy-chain topology + A/B not reversed + 120Ω at each end + shield grounded at one end + length/node/rate controlled" — the gateway side reserves termination positions and shield ground points, and the site is built against the five rules. Five wiring steps: ① daisy-chain topology → ② unified A/B labels → ③ resistors at both ends → ④ single-ended shield ground → ⑤ rate by distance — five steps done, RS485 is stable.
One summary: eight of ten RS485 faults are in the wiring — daisy-chain topology, A/B not reversed, 120Ω at each end, shield grounded at one end, length/node/rate controlled — follow the five rules and intermittent connections become stable. Wiring is both a construction job and a technical job — each of the five rules answers one "most common site mistake"; follow the standards and you avoid them.
One reminder: do not rush to replace devices when connections are intermittent — check the five wiring rules first: is the topology star, is A/B reversed, is the resistor position right, is the shield grounded at both ends, is the rate too high — after five checks, eight of ten problems are in the wiring. Troubleshoot wiring first and devices second — the five rules are the on-site checklist.
Scope and Limitations
- The conclusions in this article are intended for LV distribution and electrical-safety sites. Criteria are compiled from public codes and FEXLINK product documentation, and product parameters follow the latest selection handbook and product knowledge base.
- Quantitative criteria (protection zone, discharge and residual voltage, earth resistance, thresholds and grading) hold under the preconditions stated in this article. Where the site voltage level, earthing arrangement, environmental category or load profile differs, the figures must be recalculated. Specific configurations involving ESX/CW/CX series(RS485 downstream) should be verified against actual circuit parameters.
- Specific product models and parameters are subject to the latest selection handbook and product knowledge base; this article does not constitute selection or procurement advice.
- Standard numbers cited here refer to the currently effective editions; when a standard is revised, the related quantitative conclusions must be re-checked.
- Deployment and implementation for specific projects must be carried out by qualified engineers based on site survey and design drawings.
Frequently Asked Questions
Five RS485 Wiring Mistakes That Cause Flaky IoT Networks
The gateway is online but devices connect intermittently; you keep going on site and finally find it is a wiring problem