used or the UDP port can be set manually. If the destination IP address belongs to a Unit and
the UDP port is not assigned to COM (COM1(2) or to a Terminal server in case of RipEX) or
to any special daemon running in the destination address, the packet is discarded.
Note
M!DGE use UDP port 8882 for its COM port.
■
Table
The Address translation is defined in a table. There are no limitations such as when the Mask
translation is used. If there are more SCADA units on the RS485 (e.g. with RipEX COM2) their
interface, their “Protocol addresses” should be translated to the same IP address and UDP port
pair, where the multiple SCADA units are connected. There are 3 possibilities how to fill in the
line in the table:
− One "Protocol address" to one "IP address" (e.g.: 56 −−> 192.168.20.20)
− Range of "Protocol addresses" to one "IP address" (e.g.: 56 – 62 ===> 192.168.20.20)
− Range of "Protocol addresses" to range of "IP addresses" (e.g.: 56 – 62 ===> 192.168.20.20
– 26). One option is to write only the start IP and a dash, the system will add the end address
itself.
•
Protocol address
This is the address which is used by the SCADA protocol. It may be set either in Hexadecimal
or Decimal format according to the List box value.
Protocol address length can be 1 byte, but for the DNP3 and UNI protocols support 2 bytes
addresses.
•
IP
The IP address to which Protocol address will be translated. This IP address is used as the
destination IP address in the UDP datagram in which serial SCADA packet received from
COM is encapsulated.
•
UDP port (Interface)
This is the UDP port number which is used as the destination UDP port in the UDP datagram
in which the serial SCADA message, received from COM, is encapsulated.
•
Note
You may add a note to each address up to 16 characters long for your convenience. (E.g.
“Remote unit #1”).
•
Active
You may tick/un-tick each translation line in order to make it active/not active.
•
Modify
Edit, Delete Add buttons allow to edit or to add or to delete a line. The lines can be sorted
using up and down arrows.
•
Slave
The SCADA Slave typically only responds to Master requests, however in some SCADA protocols
it can communicate spontaneously.
Messages from the serial interface are processed in a similar way as the Master site, i.e. they are
encapsulated in UDP datagrams, processed by the router inside the M!DGE unit and forwarded to
the respective interface, typically to the mobile network.
○
Broadcast accept
List box: On, Off
Default = Off
If
On
, broadcast messages from the Master SCADA device to all Slave units are accepted and
sent to connected Slave SCADA unit.
55
© RACOM s.r.o. – M!DGE2 GPRS/UMTS/HSPA+/LTE router
Web Configuration
Содержание M!DGE2
Страница 2: ......
Страница 159: ...7 8 LOGOUT Log out from Web Manager 159 RACOM s r o M DGE2 GPRS UMTS HSPA LTE router Web Configuration ...
Страница 188: ...188 ...