IOCOMM User and
Administration Guide

  Introduction | Set-up | Configuration | Bootstrap | Indicators | Troubleshooting | Event Logging (syslog) | Exception Display | iocommd | Command Line Interface | Connectors and Cabling | Technical Specification | Glossary of Terms | Accessories


Exception Display

IOCOMM Exception Display

Re-occuring Exception

 

The IOCOMM Exception display provides details of critical errors which in most cases will cause the unit to halt operation and then perform an automatic re-boot. The only time when automatic re-boot does not happen is when an exception occurs during initial boot-up. In this case, the re-boot will be delayed for approximately 30 minutes. This is to prevent the unit from entering a continuous cycle of exception, re-boot, initialisation, exception, etc.

Should an exception occur on your IOCOMM unit, wait until the automatic reboot has been performed and check the status. If the exception re-occurs, make a note of the exception number together with details of what operation was being performed.

IOCOMM Exception Display

The most recent exception can be viewed from the web browser interface. From the IOCOMM Main Menu, select Status and statistics, Event logging, then Exception display. An example is given below:

Hardware detected exception

Exception 7

TRAP Bus Error

Location 0000c008 0000002c 00000000 00000000

D0-7 0000001c 00000001 0050c982 00000000
00000001 005b6dfe 005b6e36 005b6df2
A0-7 0073ca34 00649aa4 00000000 0073ca34
00740064 00649aa4 005b6de7 00678a0c
PC 0054666a
SR 00002600

Stack 0050c982 00000001 00000002 005b6d95
0054f26a 0054f2a0 0050c982 00000001
00000010 00554f8a 00000001 0073ca34
00740064 0050a182 005b6d90 005b6dc0

All of the information contained in the Exception display is important for fault diagnosis. The complete contents of the frame, together with details of the firmware version, should be passed to your supplier or Technical Support contact.

Re-occuring Exception

If the exception reoccurs, there are several options which can be tried to remove the fault.

Hardware reboot

Perform a hardware reboot / power cycle the unit. This may overcome a hardware problem not cleared by the automatic software reboot.

Factory reset

If a hardware reboot does not correct the problem, perform a factory reset. With the IOCOMM powered off, press and hold the TEST switch, then power-on the unit, holding in the TEST switch until the bootstrap diagnostic menu appears (as shown below).

Operations menu
1. Hardware diagnostics
2. Display exception information
3. Factory reset
4. Request password reset
5. Clear request flags
6. Download to RAM and run
7. Download to FLASH and run
q. Quit. Unpack FLASH and run
: q

From the menu, select option 3. Factory reset, then q to Quit. Unpack FLASH and run. If this is successful, upload the faulty configuration to a network host for analysis.

Check for FLASH / firmware corruption

Check for FLASH corruption, by following the instructions given in Troubleshooting. If you have recently changed to a new version of firmware, revert back to the previous version to check if the problem persists.

000127


Links to Other Chapters 

  Introduction | Set-up | Configuration | Bootstrap | Indicators | Troubleshooting | Event Logging (syslog) | Exception Display | iocommd | Command Line Interface | Connectors and Cabling | Technical Specification | Glossary of Terms | Accessories