RadioLinx RLX-FHS modem

Problem Solution Overview

We performed testing between the subject device and our 3100-MCM and 3150-MCM product.

Solution Brief

Our testing generated the following results:

• We were able to successfully communicate through the modems. (see below for configuration parameters used during the testing)

The purpose of our testing is to assure a level of compatibility in the communications between the two products. Through this testing, we attempt to identify problem areas that may arise when implementing the interface in the field.

Configuration:

The product testing was performed with the following settings used:

Port 1:
- Baud: 9600
- Parity: None
- Stop: 1
- Mode: RTU Master Mode
- Physical Connection: RS-485 & RS-232

Port 2:
- Baud: 9600
- Parity: None
- Stop: 1
- Mode: RTU Slave Mode
- Physical Connection: RS-485 & RS-232

The Module Configuration used in our testing was as follows:

This configuration in combination with the example ladder logic referenced below generates the following memory map:

N10:0 to N10:129- Slave Data
N10:130 to N10:149- Slave Error Table (Contains revision level information also)
N10:150 to N10:199- Master Error Table (Contains status of commands for diagnostics)

Command List:

The following command list shows some of the commands, which were used to test the communications:

Cable Connection:

The physical connection that was used during testing was as follows:

Additional Comments and Observations:

1. Model tested: RLX-FHS Radio Modem
2. RTS / CTS must be jumpered.

Radio Setup Considerations: (Using RadioLinx ControlScape FH Software)

1) Configure the Network to use a Point-Multipoint Modbus Network Type.

2) Baud rate for each modem must mach the 31xx-MCM settings with no handshaking.

3) When downloading Radio configuration from PC, ensure that no data is transferring