Many Galil controllers use Ethernet as a high performance communication bus. This chapter discusses the possible Ethernet network configurations that come up when installing Galil controllers. The first section shows a block diagram of connecting a static network versus a dynamic network. The second section shows examples of typical network configurations.
|
| Bock diagram that walks the user through connecting to a controller via a static versus a dynamic network |
The instructions above reference the GalilTools Connections dialog and the No IP tab.
The following are examples of possible network configurations when using a Galil controller. The IP addresses shown are for example purposes only and can/will be different for actual installations. In all cases where there are two Network interfaces such as a static NIC and a wireless NIC - make sure that the two NIC interfaces are using IP addresses that are on different subnets. For example, a static network card cannot have the IP address of 192.168.1.5 if the wireless NIC has an IP address of 192.168.1.4. Instead, the static NIC should have something like 10.10.10.1 in order to make sure it is on a different subnet*.
This first network configuration is Galil�s recommended way of having a computer connected to both the outside world (Internet or company network) at the same time as connecting to an internal controller network. In the diagram, it shows that the first network card labeled NIC1 has an IP address of 192.168.1.2 and is dynamically assigned an IP address from the Router (via DHCP). The second network card is labeled NIC2 and should be set up as a static IP address via the computers Network card settings. In this scenario, the two controllers on the network must be assigned an IP address via Ethernet using Galil software such as GalilTools, SmartTerm or WSDK or via an RS-232 serial connection (not shown) using the IA command and then using BN to burn it in to non-volatile memory. (When using the Galil software to assign the controller IP over Ethernet, the BN command is automatically issued after the IP assignment.) If Internet is not needed, then this same configuration is valid by removing NIC1 from the diagram.
 |
| Network Configuration #1 |
The third configuration is for users that would like to attach an auxiliary device to the controller via Ethernet such as an RIO to get more I/O points but who do not want to use a Hub/Switch to connect them. A Crossover Ethernet cable can be used to connect from the controller to the RIO. In the case of the DMC-40�0, a crossover Ethernet cable is not necessary as it will automatically configure itself based on the cable being used. For more information on connecting a RIO-47xxx as external I/O, go to: http://wwgalilmc.com/support/appnotes/accelera/note2512.pdf
 |
| Network Configuration #2 |
*Subnet - a subnet is a group of IP addresses that are grouped together as a �sub-network� in order to be used for a specific purpose. IP addresses outside of the �subnet mask� are not allowed to communicate to IP addresses inside the subnet. A subnet mask is generally specified by using a value of 255 designating which parts of the IP address are common to that subnet. For example, a subnet mask of 255.255.0.0 specifies that the first two bytes of the IP address are restricted to communication to other devices with the same values for those first two bytes (ie: a device with an IP address of 192.168.x.x can communicate to any other device with an IP address of 192.168.x.x)