Udp Multicast; Ppp; Df1/Eip; Modbus/Tcp - GE MDS iNET Series Reference Manual

When the unit is configured as both TCP Client and Server, the transceiver will operate in either client or
server mode, depending on which event occurs first, either receiving data on the serial port, or receiving a
request to open a TCP connection from a remote client.
The transceiver keeps a TCP session open until internal timers that monitor traffic expire. Once a TCP ses-
sion is closed, it must be opened again before traffic can flow.

UDP Multicast

IP provides a mechanism to do a limited broadcast to a specific group of devices. This is known as "multi-
cast addressing." Many IP routers, hubs and switches support this functionality.
Multicast addressing requires the use of a specific branch of IP addresses set apart by the Internet Assigned
Numbers Authority (IANA) for this purpose.
UDP multicast is generally used to transport polling protocols typically used in SCADA applications where
multiple remote devices will receive and process the same poll message.
As part of the Multicast implementation, the radio sends IGMP membership reports and IGMP queries, and
responds to membership queries. It defaults to V2 membership reports, but responds to both V1 and V2 que-
ries.
You must configure the multicasted serial port as the target for the multicast data (for example, multi-
point-to-multipoint mode, or point-to-multipoint mode where the inbound data is multicast). This restriction
is because a host that only sends data to a multicast address (for example, point-to-multipoint mode where
the iNET acts as a point) will not join the group to receive multicast data because the host's inbound data is
directed unicast data.
The serial-to-serial example which follows shows how to provide multicast services. (See "Point-to-Multi-
point IP-to-Serial Application Example" on Page 59.)

PPP

External devices can connect to the transceiver using PPP (Point-to-Point Protocol). The transceiver works
as a server and assigns an IP address to the device that connects through this interface.
To gain access to the transceiver from a PC even if the network is down, a modem may be connected to one
of the transceiver's COM ports that has been configured with PPP.

DF1/EIP

NOTE:
DF1/EIP is only supported on MDS iNET 900 ENI and MDS iNET-II 900 radios. Refer to your
product to determine the radio's capabilities.
The MDS iNET/ENI embeds the Ethernet/IP networking functionality of Rockwell's ENI adapter into the
iNET 900 transceiver. With some minor exceptions, the iNET/ENI duplicates the functionality of the
1761-NET-ENI, providing Ethernet/IP connectivity to any device using the full-duplex DF1 protocol. More
information can be found in Appendix A, MDS iNET/ENI Protocols (beginning on Page 132).

MODBUS/TCP

NOTE:
MODBUS/TCP is only supported on MDS iNET 900 ENI and MDS iNET-II 900 radios. Refer
to your product to determine the radio's capabilities.
The transceiver implements a MODBUS/TCP server that bridges MODBUS/TCP to either
. It does not function as a MODBUS/TCP client.
Modbus/ASCII
50 MDS iNET Series Reference Manual
or
Modbus RTU
05-2806A01, Rev. L