The following information can be used to help you detect system hardware problems with the DeltaV Explorer and correct them.
| Possible Cause | Corrective Action |
|---|---|
| Node is not connected to the switch. | Check the LEDs on the controller (see the LED Checklists). |
| Control network cable is not working correctly. | Test the cable between the controller and the switch. If the cable is not working correctly, repair or replace it. |
| Node is not connected correctly to the network. | Make sure cables are connected to the correct ports on the switch and the controller. |
| Connection on the carrier is not secure. | Remove the controller from its power/controller carrier for at least 15 seconds and replace it onto the carrier. |
| DeltaV Explorer is not connected to the active database, or the DeltaV Database Server (DvDbServer) is not running. | Exit the DeltaV Explorer and restart the connection to the active database. |
Problem: The controller has an
indicator.
appears for nodes that are not communicating. Typically, this
indicator occurs if there is a bad connection or the controller is not powered
up. To clear this indicator, go to the node and make sure it is connected, the
wiring is correct and sound, and the node is powered up. This indicator also
occurs for a few seconds after a controller is commissioned
| Possible Cause | Corrective Action |
|---|---|
| Node is not connected to the switch. | 1. Check the LEDs on the controller. |
| 2. Check the Control Network cables to make sure they are connected to the correct ports on the switch and controller. | |
| Control network cable is not working correctly. | Test the cable between the controller and the switch. If the cable is not working correctly, repair or replace it. |
| You are looking at the wrong controller. | Make sure you are looking at the correct controller by selecting . |
| Primary and secondary Control Network connections are crossed. | 1. Use DeltaV Explorer to flash the controller LEDs. If the LEDs flash, use the Check Node Integrity function in DeltaV Diagnostics and verify that a Not Connected status is returned. |
| 2. Verify that the primary Control Network cables are connected to the correct primary ports on the controller, workstation, and switch. | |
| 3. Verify that the secondary Control Network cables are connected to the correct secondary ports on the controller, workstation, and switch. |
Problem: The workstation has an
indicator.
appears for nodes that are not communicating. Typically, this
indicator occurs if there is a bad connection or if the workstation is not
powered up. To clear this indicator, go to the node and make sure it is
connected, the wiring is correct and sound, and the node is powered up.
| Possible Cause | Corrective Action |
|---|---|
| Workstation is not set up properly. | Make sure the workstation is powered up. Look in and verify that DeltaV Services are running. |
| Node is not connected to the switch. | Check the Control Network cables to make sure they are connected to the correct ports on the switch and workstation. |
| Control network cable is not working correctly. | Test the cable between the workstation and the switch. If the cable is not working correctly, repair or replace it. |
| Workstation address is set to a default value or an incorrect address. | 1. Look at the Internet Protocol (IP) address and verify that the address matches the DeltaV Explorer address for the node. If the address is not correct, run Workstation Configuration. |
| 2. Use the Utilities from the 3Com Install disk to verify that the Plug N Play feature is turned off for the workstation Control Network card. |
Problem: A node has an
indicator.
| Possible Cause | Corrective Action |
|---|---|
| Installing node (the workstation) does not have all the information on the node. | Click the node with the indicator, click the right mouse button, and then click Install Setup Data. This transfers setup data from the database to the physical node. It also updates the installing workstation node so that the workstation has all the information it needs to manage the new node. |
This indicator can appear on controllers that are physically connected to the network or on controller placeholders. Note that you cannot install setup data for a controller placeholder; the physical node must be connected first.
Problem: A node has a
indicator.
| Possible Cause | Corrective Action |
|---|---|
| Node is communicating but has an integrity problem. | Most integrity problems are due to hardware problems. Check the LEDs on the nodes (refer to the LED tables in this chapter) and correct the hardware problem. |
Occasionally, integrity problems occur if there is a mismatch between the I/O configuration and the installed I/O. In this case, compare the controller I/O configuration in the DeltaV Explorer with the actual I/O cards connected to the controller. This comparison can be accomplished by viewing either the I/O Auto-Sense dialog in DeltaV Explorer, or by examining the I/O hierarchy in Diagnostics.
Integrity problems can occur if the controller is configured for network redundancy but does not have the necessary connections to support it. Verify that the controller is configured to support network redundancy. If it is, make sure the controller is connected to the network correctly.
This indicator also occurs if workstations have Event Chronicle problems (configured for a directory that does not exist, for example), or if workstations are not communicating with the controller.
If the indicator persists, use DeltaV Diagnostics to pinpoint the problem.
indicator.