![Galil Motion Control RIO-47 series
RIO-47100 Скачать руководство пользователя страница 19](http://html1.mh-extra.com/html/galil-motion-control/rio-47-series-rio-47100/rio-47-series-rio-47100_user-manual_558776019.webp)
The RIO supports two industry standard protocols, TCP/IP and UDP/IP. The board will automatically
respond in the format in which it is contacted upon connection.
TCP/IP is a "connection" protocol. The master must be connected to the slave in order to begin
communicating. Each packet sent is acknowledged when received. If no acknowledgment is
received, the information is assumed lost and is resent.
Unlike TCP/IP, UDP/IP does not require a "connection". This protocol is similar to communicating via
RS232. If a cable is unplugged, the device sending the packet does not know that the information
was not received on the other side. Because the protocol does not provide for lost information, the
sender must re-send the packet.
Galil recommends using TCP/IP for standard communication to insure that if a packet is lost or
destroyed while in transit, it will be resent. However UDP is recommended in certain situations such
as launching Data Record information to a host for graphing or data collection.
Each packet must be limited to 470 data bytes or less. This is not an issue when using Galil software
as the Galil Ethernet driver will take care of the low level communication requirements.
The
command blocks the controller from receiving packets on Ethernet ports lower than 1000
except for ports 0, 23, 25, 68, 80 and 502. To receive packets on all ports, set
NOTE:
In order not to lose information in transit, Galil recommends that the user wait for an
acknowledgment of receipt of a packet before sending the next packet.
Ethernet Capabilities by Model
Model
Auto MDIX
Dual-Port 10/100 Mbits/s
RIO-47100
NO
NO
100 Mbits standard, 10 Mbits w/jumper installed
RIO-47102
YES
NO
Auto-negotiate
RIO-47120
NO
NO
100 Mbits standard, 10 Mbits w/jumper installed
RIO-47122
YES
NO
Auto-negotiate
RIO-47142
YES
YES
Auto-negotiate
RIO-47200
NO
NO
100 Mbits standard, 10 Mbits w/jumper installed
RIO-47202
YES
NO
Auto-negotiate
RIO-47300
YES
YES
Auto-negotiate
Table 3.1: Ethernet Capabilities by RIO Part Number
Addressing
There are three levels of addresses that define Ethernet devices. The first is the MAC or hardware
address. This is a unique and permanent 6 byte number. No other device will have the same MAC
address. The RIO MAC address is set by the factory and the last two bytes of the address are the
serial number of the board. To find the Ethernet MAC address for a RIO unit, use the
A sample is shown here with a unit that has a serial number of 3:
Sample MAC Ethernet Address: 00-50-4C-28-00-03
The second level of addressing is the IP address. This is a 32-bit (or 4 byte) number; an example of
such is: 192.168.15.1. The IP address is constrained by each local network and must be assigned
locally. Assigning an IP address to the RIO board can be done in 3 different ways.
1. The first method for setting the IP address is using a DHCP server. The
whether the RIO board will get an IP address from the DHCP server. If the unit is set to
(default) and there is a DHCP server on the network, the controller will be dynamically
assigned an IP address from the server. Setting the board to
will prevent the controller
from being assigned an IP address from the server.
Chapter 3 Communication ▫ 19 RIO-47xxx Rev 1.0r