Skip to content
English
Contact us
  • There are no suggestions because the search field is empty.

Serial (RS-485) Wiring, Polarity, and Node Addressing

Learn how to wire RS-485 devices to Enbase, verify A/B polarity, apply termination and shielding, assign unique node addresses, and troubleshoot common communication issues.

RS-485 is commonly used to connect controllers, annunciators, and other field devices to the Enbase Hub using Modbus RTU. Reliable communication depends on correct wiring polarity, cable practices, termination, communication settings, and unique device addresses.

IMPORTANT: Safety: Wiring changes should be completed only by qualified personnel. Follow your site electrical safety and lockout/tagout procedures, de-energize equipment before changing conductors, and verify the applicable device and panel documentation before making wiring changes.

RS-485 Wiring and Polarity

Detechtion follows the EIA-485 convention described in the referenced technical material: A is the inverting signal (TxD-/RxD-, commonly D-) and B is the non-inverting signal (TxD+/RxD+, commonly D+).

Vendor naming is not always consistent. A terminal labeled A on one device may not correspond to the same polarity labeling used by another vendor. Always verify the device documentation before landing conductors.

For a correctly identified pair, maintain the same polarity through the network:

  • B (+) to B (+)
  • A (-) to A (-)

If a device does not communicate, first verify the manufacturer's A/B or +/- definitions, the actual terminal numbers, and the Enbase panel drawings before changing wiring.

Common Panel-Specific Wiring Examples

The source set referenced for this article includes the following panel-specific examples. Because vendor terminal labeling can differ, confirm the current panel drawing and controller manual before wiring:

  • Centurion C5: TB94 (A) to RS485-1B, and TB95 (B) to RS485-1A.
  • Murphy panels using the referenced Modbus RTU convention: A to RS485-1B, and B to RS485-1A.
  • RemVue 500: terminal 10 (A) to RS485-1B, and terminal 11 (B) to RS485-1A.

Shielding

For the shielded RS-485 cable referenced in the source material, connect the cable shield at one end only, at the Hub/RTU-1003 end. Grounding the shield at both ends can create a ground loop and introduce electrical noise.

 Cable and Network Topology

  • Use Belden 9841 or an equivalent cable rated for RS-485.
  • Use a daisy-chain topology whenever possible.
  • Avoid star wiring and long spurs because they can introduce reflections and communication instability.

 RS-485 Termination

RS-485 networks may require termination at the physical ends of the bus to reduce signal reflections.

  • The referenced Enbase Hub/RTU-1003 configuration includes a built-in 120-ohm termination resistor on RS-485 that is enabled by default and configurable in the Hub Control Panel.
  • The Hub/RTU-1003 should be located at one end of the RS-485 network when its termination is enabled.
  • For long runs, including runs of approximately 500 ft or more in the referenced guidance, terminate the opposite physical end of the network with a 120-ohm resistor between A and B.
  • Do not add termination devices in the middle of the RS-485 bus.

 Centurion C5 Termination and Biasing

The referenced Centurion C5 material indicates that termination and fail-safe bias can be switched independently by port.

  • TERM controls the termination resistor for the port.
  • PU/PD controls fail-safe pull-up and pull-down biasing.
  • Fail-safe bias should be enabled only once on the RS-485 bus.
  • The device at the far end of the network should have termination enabled when required by the network design.

Node or Slave Addressing

Each Modbus device on the same RS-485 network must have a unique node or slave address. Duplicate addresses can cause communication failures or incorrect data when more than one device responds to the same request.

Altronic DD40 and DSM

The referenced DD40 and DSM material uses node numbers from 1 through 99, configured at the device.

Centurion C5

  • RS485-1 slave address is configured through the display/software.
  • RS485-2 slave address is configured using DIP switches 1 through 8.
  • The referenced firmware 50333921 behavior uses two consecutive addresses for the C5. If this firmware applies to your controller, reserve the configured address and the next address for the C5.

Address range varies by controller and port. Confirm the supported range in the controller's current Modbus documentation before assigning an address.

Enbase Hub as a Modbus RTU Slave

When the Enbase Hub is configured as a Modbus RTU Slave, the Slave ID is the node address that the Hub responds to. The referenced Auto Mapping configuration defaults the Slave ID to 1, but the value is configurable in the Modbus RTU Slave task.

Communication Settings Must Match

Correct wiring and addressing are not enough by themselves. The Hub and the connected device must also use matching serial communication settings, including baud rate and parity. Verify the device documentation and the corresponding Enbase configuration.

Quick Troubleshooting Checklist 

No Data or No Communication

  • Verify A/B polarity against the device manufacturer's documentation.
  • Verify the device is landed on the intended RS-485 port.
  • Confirm baud rate and parity match between Enbase and the field device.
  • Confirm the configured slave/node ID matches the address set on the device.
  • Check termination and bias settings for the network.
  • In the Enbase Hub Grid View, review Scan Status and scan error counts. The Hub Control Panel documentation confirms that Grid View exposes scan status, successful scan counts, scan errors, and consecutive scan errors for each Tag.

Incorrect, Maxed, or Unexpected Readings Across Multiple Devices

  • Check for duplicate slave or node addresses.
  • Verify every device on the same RS-485 bus has a unique address.
  • Confirm register mapping and data type configuration for the affected tags.

Before Contacting Support

If the RS-485 device is still not communicating, provide the following information to Detechtion Support when available:

  • Asset or unit number
  • Enbase Hub serial number
  • Connected device manufacturer and model
  • RS-485 port being used
  • Device node/slave address
  • Baud rate and parity
  • Photo of the wiring terminals and device label
  • Screenshot of the Enbase Grid View showing Scan Status or scan errors
  • Description of what changed before communication stopped, if applicable