How To Troubleshoot a PLC crash with Concept or ProWORX 32

Issue
How to troubleshoot a Quantum 984 PLC crash using either 'ProWORX 32' or 'Concept'

Prosuct Line
All Quantum 984 PLC's

Environment
ProWORX 32

Resolution
If the PLC has crashed, you can try power cycling it to recover. If the crash still occurs after a power
cycle, the following procedure can be used to help diagnose and troubleshoot the cause of the crash.

When the Quantum PLC crashes, it is possible to determine the cause of the crash from the
provided hexadecimal stop code. Using the stop code and associated information in the online help,
it may also be possible to recover from the crash.

If the Quantum PLC application is using 'ProWORX 32':

• Connect to the PLC in the 'Online' mode.
• Click on 'PLC Status' in the project navigation tree.

• Click on 'Stopcode' in the 'PLC Status' window..
• Compare the 'Stopcode' word bits with the help description to determine the cause of the crash.
• Record the stop code hex value.

If the Quantum PLC application is using 'ProWORX NxT':

• Connect to the PLC in the online mode.

• Click on 'Tools\PLC Status...'.

• Click on 'Stop Code' in the 'PLC Status' window..

• Compare the 'Stopcode' word bits with the help description to determine the cause of the crash.
• Record the stop code hex value.

If the Quantum PLC application is using 'Concept':

• Connect to the PLC
• Click on 'Online\Controller status'.

• Scroll through the 'STAT:Read Controller Status Table' pages by clicking on the >> arrow for more
• information to help determine why the crash occurred.

• The 'Stopcode' can be found on page 5 of the 'STAT:Read Controller Status Table'. The value of

the 'Stopcode' is shown in decimal format.

If powering cycling the PLC fails to help recover it, you can try the following:

• Reload the exec firmware using 'ExecLoader'.
• Download the PLC application using the applicable PLC programming software.
• Start the PLC.

If the PLC still fails to start or the crash still occurs, try swapping out the PLC with another one. If
swapping out the PLC corrects the problem, you can contact the local 'Schneider Electric Customer
Support Help Desk to send the defective PLC back for repair or exchange.

If the crash still occurs after swapping the PLC, contact the local 'Schneider Electric Customer Support
Help Desk' to open a support case. Provide the following information with the case:

• A 30 second video capture (If possible) of the local rack showing all of the LED activity on the CPU

and IO cards including any '140NOE7xxxx' Ethernet adapter cards (if applicable), during the crash.

• Record of the LED blink patterns including the number of blinks on each LED.
• Record of how long the PLC was in service before the crash occurred.
• Record of any changes made to the PLC between the time that it was placed in service and the time

the crash occurred.

• Record of the stop code:
  • If using 'ProWORX 32' or 'ProWORX NxT', provide a screen capture of the 'Stopcode'
  window. .
  • If using Concept, provide a screen capture of pages 1 through 7 for the
  'STAT: Read Controller Status Table'

If the crash occurs after downloading a new or modified application where a loadable has been added,
you can try the following:

• Remove the loadable
• Downlaod the application to the PLC.
• Try starting the PLC.

If the PLC starts, then the cause is due to either the loadable is not compatible with the PLC or there is a
conflicting opcode. You can try changing the opcode assignment and retesting.

---

Legacy KB System (APS) Data: RESL212198 V1.0, Originally authored by AlCh on 07/30/2013, Last Edited by AlCh on 07/30/2013
Related ranges: ProWORX