Ethernet Configuration; Communication Protocols; Addressing - Galil Motion Control DMC-14 5 Series Manual

RTS line goes high for inhibit. This handshake procedure ensures proper communication especially at
higher baud rates.

Ethernet Configuration

Communication Protocols

The Ethernet is a local area network through which information is transferred in units known as
packets. Communication protocols are necessary to dictate how these packets are sent and received.
The DMC-14XX supports two industry standard protocols, TCP/IP and UDP/IP. The controller will
automatically respond in the format in which it is contacted.
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 acknowledgement 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 information is lost, the controller does not return a colon or question mark. Because the
protocol does not provide for lost information, the sender must re-send the packet.
Although UDP/IP is more efficient and simple, Galil recommends using the TCP/IP protocol. TCP/IP
insures that if a packet is lost or destroyed while in transit, it will be resent.
Ethernet communication transfers information in 'packets'. The packets must be limited to 470 data
bytes or less. Larger packets could cause the controller to lose communication.
NOTE: In order not to lose information in transit, Galil recommends that the user wait for an
acknowledgement of receipt of a packet before sending the next packet.

Addressing

There are three levels of addresses that define Ethernet devices. The first is the Ethernet or hardware
address. This is a unique and permanent 6 byte number. No other device will have the same Ethernet
address. The DMC-14XX Ethernet address is set by the factory and the last two bytes of the address
are the serial number of the controller.
The second level of addressing is the IP address. This is a 32-bit (or 4 byte) number. The IP address is
constrained by each local network and must be assigned locally. Assigning an IP address to the
controller can be done in a number of ways.
The first method is to use the BOOT-P utility via the Ethernet connection (the DMC-14XX must be
connected to network and powered). For a brief explanation of BOOT-P, see the section: Third Party
Software. Either a BOOT-P server on the internal network or the Galil terminal software may be used.
To use the Galil BOOT-P utility, select the registry in the terminal emulator. NOTE: Select the
DMC-1415 controller. Once the controller has been selected, enter the IP address and select either
TCP/IP or UDP/IP as the protocol. When done, click on the ASSIGN IP ADDRESS. The Galil
Terminal Software will respond with a list of all controllers on the network that do not currently have
IP addresses. The user selects the controller and the software will assign the controller the specified IP
address. Then enter the terminal and type in BN to save the IP address to the controller's non-volatile
memory.
CAUTION: Be sure that there is only one BOOT-P server running. If your network has DHCP or
BOOT-P running, it may automatically assign an IP address to the controller upon linking it to the
network. In order to ensure that the IP address is correct, please contact your system administrator
before connecting the controller to the Ethernet network.
40 Chapter 4 Communication
i
Artisan Technology Group - Quality Instrumentation ... Guaranteed | (888) 88-SOURCE | www.artisantg.com
DMC-14x5/6