You are on page 1of 6

PROPRIETARY RIGHTS NOTICE This document and information that it contains are the property of Instron.

Rights to duplicate or otherwise copy this document and rights to disclose the document and such information to others and the right to use the information contained therein may be acquired by written permission signed by a duly authorized officer of Instron.

ETHERNET FRAME INTERFACE (EFI) INSTALLATION INSTRUCTIONS

1. INTRODUCTION This document describes how to install the Ethernet Frame Interface (EFI). The EFI is a device that allows Instron frames that currently/previously utilized the Digilink to connect to PCs. Prior to starting this procedure Install the Bluehill or Partner software, Bluehill software must be version 2.15 or higher and the Partner software must be version 8.2a or higher. 2. INSTALLATION PROCEDURE 2.1 Hardware Verify that the load frame is installed properly. If the computer controlling the frame is to be connected to a network install a network Interface Card (NIC) and drivers for communication with the testing machine. Connect Ethernet crossover cable (144-1-1052) to the EFI and to the dedicated Ethernet card on the PC, a standard Category 5 (Network Cable) will not work you must use the crossover cable as two of the pins in the cable cross. Connect the Digilink cable (144-1-1053) to the EFI and frame, you must use the new Digilink cable as it is a fully populated cable and in future DSP board revisions the DSP will power the EFI. Discard the Digilink cable. If the EFI is being fitted to an existing frame you must provide power the EFI, connect the DC wall transformer (111-1-1019) to the EFI. The transformer comes with a kit of universal plugs (111-1020), use the proper one for the location. If this is being shipped with a new frame, the new version of the DSP Board will provide the necessary power to the EFI through the Digilink Cable. Once the EFI is powered, verify that after 20 seconds the EFI LED (light emitting diode) is blinking RED. See below. Turn frame ON. After the frame is powered, the seven segment display will count down to 2. Once it reaches this point and initiates communications the EFI LED will blink YELLOW (GREEN/RED)

LED

RESET

POWER

WORK INSTRUCTIONS TO INSTALL THE ETHERNET FRAME INTERFACE (2424-400) A


REV

Mar 28, 2008


B

INSTRON
SHEET 1 OF 6

2.2 Network Setup In Windows choose the Network Connections tool (in Win XP it is found under Start/Control Panel): Select the Network Card associated with the EFI, right click on it and select Properties. The properties window will come up. Select the Internet Protocol (TCP/IP) and press Properties.

On the Internet Protocol Properties page you must manually assign an IP address to the NIC card installed in the PC. The EFI has a default address of 169.254.1.1, in order to communicate properly you must manually assign the IP address to 169.254.1.2 to the NIC Card. This is done by selecting Use the Following IP address: radio button. Once this is done you must populate the Subnet Mask with 255.255.255.0. Verify the entries are as follows: IP address: 169.254.1.2 Subnet mask: 255.255.255.0 Default gateway: BLANK

Press OK and press Close to exit the Network Properties window

Mar 28, 2008

INSTRON

REV

SHEET 2 OF 6

2.3 Software Setup 2.3.1 Bluehill Software Start Bluehill. Once Bluehill is running you must configure the frame to communicate via the Ethernet (the default setting is Digilink communications). Select the Admin Button. On the Admin Page select Configuration. Select Frame in the navigation bar. Then follow these steps: 1. Ensure the correct Controller Type is selected. 2. Select the Ethernet option for the Interface Type.

In addition to an IP address the EFI uses a MAC address, every EFI will have a unique MAC address which can be found on the label affixed to the EFI. The first 6 digits, 00-90-c2, will be used on every EFI and indicate that the device is an Instron device. The last 6 digits will be unique to the specific EFI. This is to ensure that the Bluehill Software only communicates with this specific EFI. 3. Enter the MAC Address; the MAC Address is case-sensitive. 4. Ensure that the Correct Frame Model and Frame Serial Number are selected.

As stated on the top of the Bluehill screen you must restart the software for the changes to take affect. Exit Bluehill. Launch the Bluehill software again and the software should be communicating with the EFI and frame. This can be verified by looking at the EFI LED, it should be blinking GREEN.

Mar 28, 2008

INSTRON

REV

SHEET 3 OF 6

2.3.2 Partner Software Start Partner. Once Partner is running you must configure the controller to communicate via the Ethernet (the default setting is Digilink communications). From the Home screen select Tools in the Menu. Select Configure from the drop down menu. Select Controller to view the controller setup window. On the General Tab verify the correct controller is selected.

Select the Interface type Ethernet.

Enter the MAC Address; the MAC Address is case-sensitive.

In addition to an IP address the EFI uses a MAC address, every EFI will have a unique MAC address which can be found on the label affixed to the EFI. The first 6 digits, 00-90-c2, will be used on every EFI and indicate that the device is an Instron device. The last 6 digits will be unique to the specific EFI. This is to ensure that the Partner Software only communicates with this specific EFI. You must restart the Partner software for the changes to take affect. Exit Partner Launch the Partner software again and the software should be communicating with the EFI and frame. This can be verified by looking at the EFI LED, it should be blinking GREEN

Mar 28, 2008

INSTRON

REV

SHEET 4 OF 6

3. COMMUNICATION FAILURES 3.1 TROUBLESHOOTING If upon starting the software the PC cannot communicate with the frame, you may get one of the following error messages. Bluehill:

Partner:

Follow the suggestions on the dialog box. Also: Verify the State of the EFI LED: o SOLID indicates that the EFI could be damaged, disconnect all the cables and try again. o Blinking RED Problems with the frame communications. Check the controller and the Digilink cable. o Blinking YELLOW Problems with Bluehill/Partner communications, check IP settings and Ethernet. o Blinking GREEN Everything seems to be OK. Verify that the Bluehill installation is 2.15 or above and for Partner 8.2a or above.

Mar 28, 2008

INSTRON

REV

SHEET 5 OF 6

3.2 Network Conflicts If all the network settings are correct, you can verify that the PC can communicate with the NIC Card and the EFI by Pinging the devices. Ping is a command used to test connections e.g. ping 169.254.1.1 will test the computers connection with the EFI. It will report if any packets are dropped and how fast the connection is, there should be no packets dropped and the time should be about 1ms (Based upon my experience so far). 3.2.1 Firewall Conflicts There should not be issues with firewalls unless someone decides to block outgoing traffic on their computer in which case they need to allow port 48362 for both TCP and UDP access. 3.2.2 TCP/IP Conflicts In the event the IP address is already being used by the customers network, highly unlikely but possible, you can change the default IP address used by the EFI. This should only be done if the IP address is already used, Do not change the default IP address as a troubleshooting tool. Once the reconfiguration has been performed the EFI is no longer accessible by the EFI configuration tool. If communications is lost due to IP conflict with the new address, the user must hold and reset the EFI until it reverts to the default address settings again (169.254.1.1) Run the I_EFIConfig.exe tool (found under Program Files/ Bluehill/Bin) this tool allows the user to enter a new EFI address, example: 192.168.1.1. See below:

Click the Save button and it will reconfigure the EFI and write the new target address into the computer registry.

At this point the local computer must be reconfigured to use the same domain but with a unique address, based on the above example 192.168.1.2 (see above for IP configuration). This should then allow the computer to connect with the EFI at the new address. In systems where there is a Bluehill and Partner installation, modifications to one regarding the communications method will affect the other because they share the same DigiServ resource.

Mar 28, 2008

INSTRON

REV

SHEET 6 OF 6