Issue
There is an error message on the LCD display of the old style Infinet controllers. What do these errors mean?
Product Line
Andover Continuum
Environment
Infinet Controller
Cause
Information on the error code received on the LCD display.
Resolution
Infinet controller is displaying error 1 on its LCD display.
This message indicates that the controller received a bad packet of data on the Infinet. If the problem persists follow troubleshooting instructions.
- Verify Infinet cable connections, approved twisted shielded pair cable, less than 4000 feet of network cable between Infilink repeaters, no more than 31 controllers between Infilink repeaters.
- Verify proper grounding at the Infinet controller on the AC power terminals, poor grounding can cause erratic operation and communication problems. Easiest method to verify ground is to connect a digital voltmeter between the earth ground terminal on the power strip of the controller and the shield of the Infinet. this method will only work if you have connected your shields all through the network back to the Infilink and CX controller.
- Check the baud rate switch on the Infilink repeater module, although the Infinet controllers auto baud, the Infilink baud rate must be manually switched.
- Break down the network in segments to identify the bad controller or network segment. A binary search is recommended. (i.e. break the network in half, if this resolves the problem add half of the deleted back on, if it does not resolve the problem cut the remaining network in half, etc.). Once the offending segment has been identified, troubleshoot to the cable segment or controller level
Infinet controller is displaying error 2 on its LCD display. This message means that it could not pass a token to another controller on the Infinet. If the problem persists follow troubleshooting instructions. (No response to the Infinet token pass)
- Verify Infinet cable connections, approved twisted shielded pair cable, less than 4000 feet of network cable between Infilink repeaters, no more than 31 controllers between Infilink repeaters.
- Verify proper grounding at the Infinet controller on the AC power terminals, poor grounding can cause erratic operation and communication problems. Easiest method to verify ground is to connect a digital voltmeter between the earth ground terminal on the power strip of the controller and the shield of the Infinet. this method will only work if you have connected your shields all through the network back to the Infilink and CX controller.
- Check the baud rate switch on the Infilink repeater module, although the Infinet controllers auto baud, the Infilink baud rate must be manually switched.
- Break down the network in segments to identify the bad controller or network segment. A binary search is recommended. (i.e. break the network in half, if this resolves the problem add half of the deleted back on, if it does not resolve the problem cut the remaining network in half, etc.). Once the offending segment has been identified, troubleshoot to the cable segment or controller level
Infinet controller is displaying an error 3 on its LCD display. This means that the input reference voltage is out of range on the analog inputs.
- Verify that inputs coming from external transducers are not exceeding the voltage input range, either 5 or 10 volts depending on model, if so use a voltage divider on the input.
- Verify that any input wiring is not run in the same conduit as high voltage cable, or is properly shielded and grounded. If there is voltage getting coupled into the input wiring, separate the input wiring from the interference, or shield the cables. If the interference is being caused by the end device such as an auxiliary contact form an high voltage device, a cap between .01 and 1 microfarads across the input terminal to earth ground may alleviate the problem.
- Remove field I/O wiring from the controller and recheck operation. If the problem goes away determine which I/O wire is the culprit and correct it.
- Power down the Infinet controller and restart while connected to network. This will eliminate this unit having a duplicate ID on the network and it will also run the power up diags.
- Verify proper grounding at the Infinet controller on the AC power terminals, poor grounding can cause erratic operation and communication problems. Easiest method to verify ground is to connect a digital voltmeter between the earth ground terminal on the power strip of the controller and the shield of the Infinet. this method will only work if you have connected your shields all through the network back to the Infilink and CX controller.
- Remove field I/O wiring from the controller and recheck operation. If the problem goes away determine which I/O wire is the culprit and correct it.
Infinet controller is displaying an error 4 on its LCD display. This means that the analog output reference voltage is out of range.
- Verify that inputs coming from external transducers are not exceeding the voltage input range, either 5 or 10 volts depending on model, if so use a voltage divider on the input.
- Verify that any input wiring is not run in the same conduit as high voltage cable, or is properly shielded and grounded. If there is voltage getting coupled into the input wiring, separate the input wiring from the interference, or shield the cables. If the interference is being caused by the end device such as an auxiliary contact form an high voltage device, a cap between .01 and 1 microfarads across the input terminal to earth ground may alleviate the problem.
- Remove field I/O wiring from the controller and recheck operation. If the problem goes away determine which I/O wire is the culprit and correct it.
- Power down the Infinet controller and restart while connected to network. This will eliminate this unit having a duplicate ID on the network and it will also run the power up diags.
- Verify proper grounding at the Infinet controller on the AC power terminals, poor grounding can cause erratic operation and communication problems. Easiest method to verify ground is to connect a digital voltmeter between the earth ground terminal on the power strip of the controller and the shield of the Infinet. this method will only work if you have connected your shields all through the network back to the Infilink and CX controller.
- Remove field I/O wiring from the controller and recheck operation. If the problem goes away determine which I/O wire is the culprit and correct it.
Infinet controller is displaying an error 5 on its LCD display. This indicates the controller underwent a reset of power down and retained memory ( warm start). If there is not reason for this to occur power outages etc., then troubleshoot the problem.
- Verify proper grounding at the Infinet controller on the AC power terminals, poor grounding can cause erratic operation and communication problems. Easiest method to verify ground is to connect a digital voltmeter between the earth ground terminal on the power strip of the controller and the shield of the Infinet. this method will only work if you have connected your shields all through the network back to the Infilink and CX controller.
- Measure the AC power at the controller, Verify it is within specification (nominal +/- 20%). Typically 24 VAC power that is daisy chained will drop the voltage along the connections leaving the power below the acceptable level even if the transformer is sized correctly.
- Verify that any outputs that are driving inductive loads such as relays, actuators, or valves, have a varistor across the coil n the field device.
- Verify that any input wiring is not run in the same conduit as high voltage cable, or is properly shielded and grounded. If there is voltage getting coupled into the input wiring, separate the input wiring from the interference, or shield the cables. If the interference is being caused by the end device such as an auxiliary contact form an high voltage device, a cap between .01 and 1 microfarads across the input terminal to earth ground may alleviate the problem.
- Remove field I/O wiring from the controller and recheck operation. If the problem goes away determine which I/O wire is the culprit and correct it.
