A General Guide for RS-485 Communication

Problem (Issue) Statement

A General Guide For RS-485 Communication.

Description:

A general guide for RS-485 communication networks.

The RS-485 standard allows for very robust communications over distances of up to 4000 feet on networks wired with relatively inexpensive cable types.

Related Software:

NIL

Related Hardware:

NIL

System Application:

NIL

Symptom and Finding:

NIL

Cause:

A general guide for RS-485 networks.

Solution:

Summary:


Step-by-step Guide:

  • Network Topology:

Step 1: To avoid signal reflections which can cause communication errors, the Daisy Chain topology is highly recommended. The Daisy Chain topology is designed as one continuous line with multiple drops instead of similar to a star.
Daisy Chain Topology in Detail
Figure 1: Daisy Chain Topology in Detail


Step 2: The picture below shows several typical wiring configurations observed from site, with Daisy Chain's topology being the only acceptable configuration.
Frequently Observed Wiring Connection, with Daisy Chain Being the Only Acceptable Configuration
Figure 2: Frequently Observed Wiring Connection, with Daisy Chain being the Only Acceptable Configuration


Tip

The best way to ensure a robust and reliable RS-485 network is to build it around a daisy chain configuration.



  • Cable Distance:

Step 1: RS-485 standards allow communications of up to a maximum of 1km cable length for a network segment. This length is the total cable length between the first controller in the network and the last controller in the network. It is not the length between one controller to the next successive controller. Refer to the following picture for further information
1km Maximum Cable Length Requirement Between First and Last Controller in the Network
Figure 3: 1km Maximum Cable Length Requirement Between First and Last Controller in the Network


  • Cable Type:

Step 1: RS-485 specification recommends shielded twisted pair cable to reduce two major sources of problems for external noise: radiated EMI and received EMI.


Step 2: The recommended cable specifications are as follows:


Example of the shielded twisted pair cable:
Shielded Twisted Pair Cable Illustration
Figure 4: Shielded Twisted Pair Cable Illustration


Common Issue

  • Hardware devices connected using star topology, which resulted in hardware status down. 
  • Project deployment using incorrect cable type, noise induced by the environment can also cause hardware status to be down.

Date Documentation:

5/11/2018 (Rev 1.0)

PROOF-READ

.

.


.

© MicroEngine Technology Sdn Bhd (535550-U). All rights reserved.