top of page
< Back
Daviteq Compact RS485 Converter
LoRaWAN
Sigfox
Sub-GHz
NB-IoT

Daviteq Compact RS485 Converter

C-RS485

New replacement products

Replaced SKU

Satellite IoT

Gallery

1. Introduction

Overview

Daviteq Compact RS485 Converter is to connect to RS485 Modbus RTU port of field slave device such as power meter, water meter, flow meters, PLC, controller, analyzers... The converter can be integrated into the wireless transmitter from Daviteq, such as Sub-GHz WS433, LoRaWAN WSLRW, and Sigfox WSSFC, to build the complete Wireless RS485 master node. The converter is powered by external power.


Specification

Input port;1 x RS485 master port

Protocol;Modbus RTU

Fault protected RS-485 bus pins;up to ±40V

HBM ESD protection on RS-485 bus pins;±15kV

Extened common mode range;±15V (larger than required for RS-485)

High transient over voltage tolerance;±60V

Full fail-safe RS-485 receivers;open, short, terminated

2. Principle of Operation

The converter with RS485 Modbus RTU protocol is widely used in industrial automation and control systems. Here's a brief overview of its principal operation:


RS485 Communication Protocol

- Differential Signaling: RS485 uses differential signaling to transmit data, which helps in reducing noise and allows communication over long distances (up to 1200 meters).

- Multi-Drop Network: It supports a multi-drop network, meaning multiple devices (up to 32) can be connected on the same bus.

- Half-Duplex and Full-Duplex Modes: RS485 can operate in both half-duplex (one-way communication at a time) and full-duplex (simultaneous two-way communication) modes.


Modbus RTU Protocol

- Master-Slave Architecture: Modbus RTU operates on a master-slave architecture where the master device initiates communication and the slave devices respond.

- Message Structure: Each Modbus RTU message consists of:

- Slave Address: Identifies the slave device.

- Function Code: Specifies the action to be performed (e.g., read or write data).

- Data: Contains the actual data or parameters for the function.

- CRC Checksum: Ensures data integrity by detecting errors in transmission

- Registers and Coils: Data in Modbus RTU is organized into registers and coils, which can be read from or written to by the master device.

3. Calibration

No calibration is required for RS485 Modbus converter

4. Application Notes

5. Installation Notes

Key installation notes for an RS485 converter:


1. Wiring:

- Twisted Pair Cables: Use twisted pair cables to minimize electromagnetic interference (EMI).

- Termination Resistors: Install termination resistors (typically 120 ohms) at both ends of the RS485 bus to prevent signal reflections.


2. Grounding:

- Proper Grounding: Ensure proper grounding of the RS485 network to avoid ground loops and reduce noise.


3. Network Topology:

- Daisy-Chain Configuration: Use a daisy-chain (bus) configuration for connecting devices. Avoid star or ring topologies.


4. Device Addressing:

- Unique Addresses: Assign unique addresses to each device on the RS485 network to prevent communication conflicts.


5. Power Supply:

- Stable Power Supply: Ensure a stable power supply to the RS485 transmitter to maintain reliable communication.


6. Environmental Considerations:

- Temperature and Humidity: Install the transmitter in an environment within its specified temperature and humidity range.


6. Other Considerations:


- Check Compatibility: Verify that the RS485 transmitter is compatible with the other devices and the overall system.

- Follow Manufacturer Guidelines: Always follow the manufacturer's installation guidelines and safety instructions.

6. Troubleshooting

Important troubleshooting tips for an RS485 converter:


  1. Check Wiring and Connections:

    • Ensure all connections are secure and that A+ and B- communication cables are correctly connected throughout the network.


  2. Verify Termination Resistors:

    • Confirm that termination resistors (typically 120 ohms) are installed at both ends of the RS485 bus to prevent signal reflections.


  3. Inspect Grounding:

    • Proper grounding is essential to avoid ground loops and reduce noise. Check that the network is properly grounded.


  4. Check Communication Parameters:

    • Verify that all devices on the network are configured with the same baud rate, parity, stop bits, and data bits.


  5. Monitor for Noise and Interference:

    • Use twisted pair cables to minimize electromagnetic interference (EMI). Check for sources of electrical noise that could affect communication.


  6. Test with Known Good Devices:

    • Replace the RS485 transmitter with a known good device to determine if the issue is with the transmitter or another part of the network.


  7. Check for Biasing Resistors:

    • Ensure that biasing resistors are correctly installed if required by your network configuration.


  8. Review Device Configuration:

    • Confirm that each device has a unique address and that there are no address conflicts on the network.

7. Maintenance

Maintenance guidelines for an RS485 converter:


1. Regularly inspect wiring and connections to ensure they are secure and free from damage.


2. Check termination resistors at both ends of the RS485 bus to prevent signal reflections.


3. Verify proper grounding to avoid ground loops and reduce noise.


4. Periodically review communication parameters (baud rate, parity, stop bits, data bits) to ensure consistency across all devices.


5. Monitor for sources of electrical noise and use twisted pair cables to minimize interference.


6. Test the transmitter with known good devices to identify potential issues.


7. Ensure biasing resistors are correctly installed if required by your network configuration.


8. Keep the transmitter in an environment within its specified temperature and humidity range.

8. Default Configuration

This RS485 converter has the default configuration, however, those parameters can be changed. The user can change the configuration on the wireless transmitter so that the complete node(converter+ wireless) delivers the proper output value. Please check the Payload document for more information.

bottom of page