GE RX3i - Chapter 12 Diagnostics; 12.1 What to Do if You Cannot Solve the Problem

GFK-2224Q January 2017 207
Chapter 12 Diagnostics
This chapter describes diagnostic techniques for a PACSystems Ethernet Interface.
▪ What to do if You Cannot Solve the Problem
▪ Diagnostic Tools Available for Troubleshooting
▪ States of the Ethernet Interface
▪ EOK Blink Codes for Hardware Failures
▪ Controller Fault Table
▪ Monitoring the Ethernet Interface Status Bits
▪ Monitoring the FT Output of the COMMREQ Function Block
▪ Monitoring the COMMREQ Status Word (CSW)
▪ Using the EGD Management Tool
▪ Troubleshooting Common Ethernet Difficulties
12.1 What to do if You Cannot Solve the Problem
If you cannot solve the problem, contact Technical Support. Please have the following information ready:
▪ The Name and Catalog Number marked on the product.
- PLC CPU version number from CME Status screen
- Ethernet Interface CPU Embedded or standalone
▪ Description of symptoms of problem. Depending on the problem, you may also be asked for the following
information:
- The ladder logic application program and the PLC sweep time at the time the problem occurred.
- A listing of the configuration parameters for the Ethernet Interface that failed.
- A description of the network configuration. This should include the number of PLCs and host
computers accessing the network, the type of network cable used (e.g. twisted pair, fiber optic, etc.),
length of network cable, and the number and manufacturer of transceivers, hubs, and network
switches used.
- Description of all Ethernet communication activity for the PLC.
- Versions of all software communicating with the PACSystems controller via Ethernet.
This includes Proficy Logic Developer, CIMPLICITY PE, IFIX, etc.
- Be prepared to provide the Controller Fault Table showing Fault Extra Data
- Be prepared to provide Station Manager Log showing Ethernet Events