Can Mercury 23x Meters Share a Single RS-485 Branch?

Mercury 230, 234, and 236 meters can share one RS-485 branch when every meter has a unique address and the branch remains electrically sound. Treat the installation as one multidrop transmission line, not as several independent point-to-point links. The number that matters is not merely the device count: it is the electrical load, signal quality, and response timing measured at the least reliable meter.

Direct Multidrop Versus Repeater Segmentation

Two arrangements fit this equipment class. A direct multidrop branch is the simplest choice for six meters when cable routing, addressing, and signal quality are controlled. Segmentation adds an interface repeater when distance, loading, topology, or noise leaves insufficient communication margin.

Start with the direct branch for the six-meter case. Add a repeater only after measurements or repeatable communication failures show that the single segment lacks margin. A reported manufacturer claim allows more meters than the commonly cited 31-device Modbus network figure, but that claim is not a design limit for this installation. Read the supported node count and transceiver loading from the exact meter and interface documentation before expanding the branch.

Current, Thermal Load, and Timing

RS-485 communicates by producing a differential voltage across the line. Termination and connected transceivers draw current from the active driver. Excess termination, unintended parallel resistance, cable faults, or too many electrical loads reduce the effective impedance, increase driver current, and can heat or current-limit the interface. This is heat, not logic: changing an address cannot repair an overloaded physical segment.

Timing becomes the next limit after the waveform reaches every node. The SCADA driver sends a request to one address, waits for that meter, and then processes the reply. Duplicate addresses cause overlapping replies. Mismatched serial settings produce unreadable replies or silence. A response timeout that is shorter than the meter and network transaction time produces intermittent failures even when the wiring is acceptable.

Branch Diagnostic Checks

Test the physical branch before changing application data or transformer scaling. A stable link must survive repeated reads from every address, including the farthest or least reliable meter.

1. Record each meter model, address, and communication setting. The adapted DrvMercury23x driver covers Mercury 230, 234, and 236 meters for SCADA Version 6, but each configured device must match the installed meter and its address.
2. Inspect the cable as a trunk. Long branches or star connections create discontinuities that reflect signal energy and narrow the timing margin.
3. Locate termination and bias components. Termination belongs at the electrical ends of the segment; several enabled terminators can overload the active driver.
4. With power isolated, measure the line for shorts, opens, and unexpected resistance. Compare the measurement with the actual termination arrangement rather than applying an assumed resistance value.
5. Connect one meter and prove repeated reads. Add meters individually while tracking retries, timeouts, corrupted responses, and the first address that becomes unstable.
6. Poll each address separately, then run the intended scan sequence. Per-device success with full-scan failure points toward aggregate timing, duplicate addressing, or loading rather than a missing meter.
7. If communication is stable but transformer-connected values are wrong, compare the raw meter value with the driver’s transformation or scaling setup. Transport errors and ratio errors require different fixes.

Recommended Configuration Procedure

1. Assign a different address to every Mercury meter before joining the devices on one branch. Maintain an address schedule that links the physical meter, installed location, model, and SCADA entry.
2. Configure one serial rate and frame format across the meters, interface converter, and DrvMercury23x. Read the required values from the installed equipment; no universal setting is established here.
3. Wire the meters along one RS-485 trunk with consistent conductor polarity. Keep individual device connections short relative to the trunk.
4. Apply termination only according to the actual segment endpoints and equipment documentation. Remove unintended termination that places excessive parallel load on the driver.
5. Create one driver device entry per meter address. Configure only the parameters needed for the initial test, then add the remaining points after basic reads are stable.
6. In the Version 6 graphical interface, select a main parameter cell to load its additional parameters. Move or delete only main parameters with the interface controls. Within commands, the documented deletion method is the Del key, and command movement is not available.
7. Run a controlled poll of one meter at a time, followed by all six meters. If failures appear as the branch grows, correct topology, termination, and timing before installing a repeater.
8. Segment the line with a suitable interface repeater when the direct branch remains marginal after wiring corrections or when the documented loading limit would be exceeded.

Operational Verification

Verify communication and measurement accuracy separately. For communication, run repeated reads from every configured address and inspect the driver diagnostics for timeouts, retries, invalid frames, or replies attributed to the wrong device. Disconnect one meter at a time and confirm that only its configured address fails; multiple lost addresses indicate a shared wiring or segment problem.

For measurement verification, compare the displayed SCADA values with the values available directly from the meter. Where current or voltage transformers are used, check whether ratios are applied in the meter, in DrvMercury23x, or elsewhere in SCADA. Applying a ratio twice creates a stable but incorrect value; omitting it creates a different stable scaling error. Intermittent missing data still points toward transport or timing rather than transformer scaling.

Recheck the full branch after adding parameters because a larger scan increases transaction time. Record the working address map, serial settings, termination locations, measured line condition, scan behavior, and any repeater boundaries.

Recurring Failure Modes

Frequently Asked Questions