Configuring Remote Airlink Gateways For Modbus With Udp - Sierra Wireless AirLink RV50 Series User Manual

Hide thumbs Also See for AirLink RV50 Series:
Table of Contents

Advertisement

ALEOS 4.9.0 Software Configuration User Guide for AirLink RV50 Series
Note: With a name instead
of IPs for the host device,
the remote devices query
the DNS server for the
current IP assigned to the
host device before sending
data back to the host.
Rev 1 Dec. 17
Configuring Remote AirLink gateways for
Modbus with UDP
This section covers standard Modbus settings for the AirLink gateway at the
remote unit; variations may need additional commands.
1. Configure the ports
In ACEmanager, select Port Configuration in the side menu.
The destination port for the device at the host needs to match the device port in
use on all the devices at the remote sites. For example, if the remote device's
device port (see below) is "12345", then the Modbus host device's S53
destination port should be set to "12345".
Set the destination port (S53) to match the device port of the host device
(*DPORT). Make sure the device port of the remote device (*DPORT) matches
the destination port of the host device (S53).
Configure IP Addresses for the Host
If the Host device has a static IP address, enter it in the Destination Address for
S53.
If the device at the host has a dynamic IP and is using Dynamic DNS, instead of
an IP address for S53, specify the name of the host device (**). If the remote
devices are using a different DDNS than the host device, you need to specify the
fully qualified domain name (**+*DOMAIN).
Note: Setting the Host device IP address as the S53 Destination Address provides a low
level security. The device does not forward UDP traffic unless the source IP/port matches
what is in S53. However, if you set *AIP=1, the device forwards UDP traffic from any
source IP address as long as it is accessing the device on the configured *DPORT.
1. Configure the default mode for start-up.
Each device at the remote locations needs to be configured to communicate with
the device at the host. In ACEmanager, select UDP in the side menu.
a. Enable S82, UDP answer.
b. Set S83 to the idle time-out applicable to your application, commonly 20.
2. Configure other RTU settings.
Other parameters may need to be changed, but this is dependent on the RTU
type being used. At a minimum, this typically involves setting the proper serial
settings to match your RTU.
3. Optional: Dynamic IP Address
If you do not have a static IP, the host device should be configured to report its
current IP to a Dynamic DNS (DDNS) server with Dynamic DNS.
Match the name of the device to the names specified in the host device's MLIST
or MLISTX for the connected RTU.
352
41111088

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents