Rockwell Automation T80020 User Manual

Trusted

AN-T80020

Application Note

Diagnostics Procedure

This document provides:

• A procedure for first-line diagnostics

This explains how to gather the appropriate data for each situation. It is easy to lose evidence after a module or system failure. This procedure explains how to collect the evidence to give to a support engineer, who can use the rest of this document to diagnose the problem.

• Details of all error codes produced by the I/O modules

For I/O module faults, the first-line diagnostics will usually provide a fault code. This section explains the fault that has been found and advises on a course of action.

• A guide to the Analysis Tool

The Analysis Tool is a program which helps with the collection and analysis of diagnostic data from the system. It includes advice on all the error codes and will warn about problems found on the system.

For technical support email: support@icstriplex.com

Issue Record

Issue Number

6 March

7 May 09 Nick Owens Pete Stock Gerry Creech Added action on processor

8 July 09 Nick Owens Andy Holgate Pete Stock Revised Analysis Tool manual

9 Jan 10 Nick Owens Andy Holgate Pete Stock Revised Analysis Tool manual

10 May 10 Nick Owens Andy Holgate Pete Stock Analysis Tool v3.6 manual

11 Oct 10 Nick Owens Andy Holgate Pete Stock Analysis Tool v4.0 manual

12 Feb 11 Nick Owens Andy Holgate Pete Stock Analysis Tool v4.1 manual

Date Revised by Technical

Check

Nick Owens Pete Stock Gerry Creech Derived from 552936 rev 05.

Authorised by

Modification

Fault codes revised, converted to AN, advice rewritten.

shutdown

Issue 12 Feb 11 AN-T80020 1

Trusted

AN-T80020 Diagnostics Procedure

Diagnostics Procedure

Diagnostics Procedure..............................................................................................................................2

Table of Contents...................................................................................................................................2

First-line Diagnostics ................................................................................................................................4

Toolset Diagnostics ..................................................................................................................................7

Other data on Equipment Definitions ...................................................................................................11

Analysis Tool ..........................................................................................................................................12

Online...................................................................................................................................................13

Online Options...................................................................................................................................15

‘Set the time/date’..............................................................................................................................15

‘Auto set time/date’ ............................................................................................................................16

‘I/O Module Options’ ..........................................................................................................................16

‘Analyse Data’....................................................................................................................................17

System Graphic / Online Tree Window .............................................................................................18

Manual Command Entry....................................................................................................................19

Offline...................................................................................................................................................20

File Menu...........................................................................................................................................21

View Menu.........................................................................................................................................21

Log View............................................................................................................................................21

Log View............................................................................................................................................22

Find Menu..........................................................................................................................................22

Analysis View.....................................................................................................................................22

Bookmarks ........................................................................................................................................25

Module Versions................................................................................................................................29

System Health ...................................................................................................................................30

Bookmarks ........................................................................................................................................31

Main Processor System Logs .................................................................................................................32

Clearing the MP Non-Volatile RAM (NVRAM) Memory ..........................................................................35

GALPAT errors (TN20014)................................................................................................................35

Processor build 122 and System.INI changes (TN20061) ................................................................35

Clearing the non-volatile RAM...........................................................................................................35

Action on Processor Shutdown...............................................................................................................36

Normal Shutdown Action ...................................................................................................................36

Processor LED States..........................................................................................................................36

Toolset Debugger Messages ...............................................................................................................36

Processor System Event Logs .............................................................................................................37

Issue 12 Feb 11 AN-T80020 2

Trusted

AN-T80020 Diagnostics Procedure

Please do NOT send:...........................................................................................................................37

APPENDIX A. ERROR CODE DESCRIPTIONS....................................................................................38

Glossary...............................................................................................................................................39

0x0000 Series Codes (Firmware and System) ....................................................................................41

0x1000 Series Codes (Host Interface Unit) .........................................................................................43

0x2000 Series Codes (Host Interface ASIC) .......................................................................................46

0x3000 Series Codes (Field Interface ASIC) .......................................................................................48

0x4000 Series Codes (Module firmware operation).............................................................................49

0x5000 Series Codes (Input Field Interface Unit) ................................................................................50

0x6000 Series Codes (Output Field Interface Unit) .............................................................................55

0x7000 Series Codes (Processor generated) ......................................................................................65

0x8000 Series Codes (General non-resettable) ..................................................................................68

0x9000 Series Codes (Host Interface Unit non-resettable) .................................................................69

0xC000 Series Codes (Module firmware non-resettable) ....................................................................69

Self Test Cycle Times.............................................................................................................................70

Issue 12 Feb 11 AN-T80020 3

Trusted

AN-T80020 Diagnostics Procedure

First-line Diagnostics

Every day, check the processor’s System Healthy LED. If this is green, there are no system faults. There may still be communications problems and field wiring problems.

If the System Healthy LED is flashing red, there is a system fault. Look at the other diagnostic LEDs in the table on the next few pages.

Each module has ‘Healthy’ LEDs, one for each slice of the module’s circuitry. The Communications Interfaces (8151 or 8151B) are not triplicated and so only have one LED.

Do not press the main processor reset pushbutton or remove and reinsert a module unless specifically advised to do so in the procedures below. Pressing the reset pushbutton may clear important diagnostic information. Removing and reinserting a module may cause shutdowns and will also clear some fault information.

Keep a logbook for recording error codes from I/O modules. Record the error code, module position (chassis and slot or reference number), date and time. If the advice in this document for that error code is to act only if it is persistent (returns later after pressing Reset), use the logbook to look for earlier records of the same fault.

LED colour Reason Procedure

Processor 'Healthy' LEDs are red

Processor 'Educated' LED is not steady green

Active Processor 'Run' light is not flashing green

Processor 'Inhibit' LED is flashing green

Processor module fault.

No application The Standby Processor takes a few minutes to synchronise with the

Application not running

The processor cannot be hot swapped

Collect the processor’s current system log. The procedure is described in a section below.

Obtain a replacement processor module of the same or later build. Swap to the replacement module.

If the fault appeared after the processor was restarted, it is likely that a memory corruption has occurred because the education process had not completed. Refer to TN20014.

Active Processor. It should not be removed during this time. If it has, memory corruption may occur. Refer to TN20014.

The Active Processor may have no application loaded.

The Standby Processor may not have started or completed its education from the Active processor.

The 'Run' light is always steady green on the Standby processor.

The Active processor should show a flashing green 'Run' LED.

The 'Run' LED is off when the application in the Active processor is stopped.

If the ‘Run’ LED has stopped when it should not have, then the system has detected a fault of some kind. This should be reported to ICS Triplex Technology. Refer to the section below describing Action on Processor Shutdown. This describes how to collect diagnostic information which may be lost during attempts to restart.

The 'Inhibit' LED flashes green when any input or output is locked, as a warning. This LED also flashes green when the current Standby Processor has an incompatible system configuration. A changeover from the Active to the Standby processor will not work if the Inhibit LED is flashing. To enable a swap in this second case, remove and reinsert the Standby processor to load the system configuration.

Issue 12 Feb 11 AN-T80020 4

Trusted

AN-T80020 Diagnostics Procedure

LED colour Reason Procedure

rocessor

P 'System Healthy' LED is not steady green

Processor ‘Healthy’ LEDs all steady green, System Healthy LED flashing red, all other LEDs off

Comms Interface 'Healthy' LED is not steady green

System shut down when it should not have done

here is a

T system fault

Processor kernel fault

Communications interface fault

Further investigation needed

he 'System Healthy' LED is steady green when the complete system

T is healthy. The LED flashes red when there is a fault in the system, or the processor is not yet initialised.

A fault in the system may be any of a long list of possibilities, but the processor current log will always show the reason.

Collect the processor’s current system log. The procedure is described in a section below.

Note that some faults may not show any other LED indication.

The processor’s foundation operating system has stopped the processor because of a firmware error. The processor is no longer running and will not communicate until it is restarted.

If you have just swapped processors, the old processor will always be stopped using a watchdog timeout kernel fault; in this case remove the old processor and do not worry.

If you had not swapped processors, this is a serious error and should be reported to ICS Triplex Technology. Refer to the section below describing Action on Processor Shutdown. This describes how to collect diagnostic information which may be lost during attempts to restart.

If the 'Healthy' LED is flashing red, the module has halted. Remove and refit the module. The module may have shut down when unable to cope with a communications situation and may work properly next time.

If it still fails, obtain a replacement module. Remove the existing module and insert the replacement (they do not hot swap). The replacement will automatically load its configuration. Return the faulty module for repair.

Communications modules from hardware build C will store their current event log on power loss as the backup log. The backup log can be collected on the first restart (the procedure is described below). This will explain the reason for the fault.

If the ‘Run’ LED is still flashing and there was no recent intervention, check if the system has performed a shutdown that it was programmed to do.

If an online update had just been loaded, and outputs were deenergised unexpectedly, refer to AN-80009 section 1.12. This describes a problem with intelligent online updates with Toolset versions up to and including build 103 (TUV release 3.5).

Issue 12 Feb 11 AN-T80020 5

Trusted

AN-T80020 Diagnostics Procedure

LED colour Reason Procedure

comms

A interface port is not showing LED activity

Expander Interface module 'Healthy' LED not steady green

Expander Processor module 'Healthy' LED not steady green

o comms Serial ports should be flickering red/green or yellow if active.

Ethernet ports should be flickering red/green or yellow if active and steady green or off when inactive.

Flickering red or green only indicates one way communications. Red is transmit, green is receive.

If communications has previously been successfully commissioned, check the communications path for cable faults etc. Refer to the 8151B Communications Module PD for information on communications module settings.

Module fault Obtain a replacement module. Swap to the replacement module.

Return the faulty module for repair.

A table of further diagnostics is given in PD-8311.

Module fault Obtain a replacement module. Swap to the replacement module.

Return the faulty module for repair.

A table of further diagnostics is given in PD-8310.

Expander Processor Tx/Rx LEDs not flickering yellow

I/O module 'Healthy' LED flashing red

I/O module 'Healthy' LED steady red

I/O module Channel LEDs are not off or steady green

No comms These three LEDs monitor the communications on the three cables

from the Expander Interface. Note that no communications will be shown whilst the Expander Processor is in Standby, the Expander Interface is not operating or the system is starting up. If one communications link LED is off, check the cable and connections for that link.

A fault has been detected on the slice but the slice is still operating

A slice of the triplicated module has been set offline and has been disconnected.

Field fault Channel LED settings are system specific and may be configured in

Collect the error code using the Toolset debugger, as described in a section below. Look up the advice in the Error Code Descriptions below. Note the fault code, module reference, date and time in a log book and press Reset.

You cannot clear these faults or restart the slice by pressing Reset. You cannot get any logs from this slice without restarting it.

Obtain a replacement module of the same or later build. Swap to the replacement module. Remove the faulted module.

Insert the faulted module into an unused slot (one for which scanning is not disabled in the system configuration, but which is not connected to an I/O cable or hot-swap cable).

If the slice fails to start, return the faulty module for repair.

If the faulted slice starts, collect the I/O module log from that slice (described in a section below). Read the end of the log for error codes. Look up the advice in the Error Code Descriptions below.

the System Configuration. Check the meaning of the LED colour and investigate the channel wiring.

Issue 12 Feb 11 AN-T80020 6

Trusted

AN-T80020 Diagnostics Procedure

Toolset Diagnostics

If you need to find an I/O module fault code, use the Toolset to access the data in the system. The data also includes further data on the system, e.g. temperature, voltages, currents etc.

Open the Toolset, using either your desktop shortcut or the Start menu ( Start | All Programs | Trusted | Toolset ).

Open the application running in the system by double-clicking on its name.

It is possible to connect to the system using either the processor’s front panel serial port or over Ethernet via a communications interface. Before connecting to the system, check that the communications port settings are correct. Select Debug | Link Setup.

If you are using a TC-304 maintenance cable to connect to the processor’s front panel serial port, check that ‘Communication port:’ is set to COM1 (or whichever serial port you are using on the PC). Check that the maintenance cable is plugged into the PC serial port and the processor’s front panel port.

If you are using Ethernet, check that TMR System is selected. This option is at the bottom of the list and you need to scroll down to see it. Click on Setup and check the IP address is set. Hopefully for existing site systems, the communications settings will already be set up. Check that the system and PC are connected to the Ethernet network with addresses on the same subnet.

Ensure the processor keyswitch is turned to ‘Maintain’ if using a Toolset before build 103. Toolsets before build 103 will not communicate with the system if the keyswitch is in the ‘Run’ position. Toolsets from build 103 will communicate read-only if the keyswitch is in the ‘Run’ position.

Issue 12 Feb 11 AN-T80020 7

Trusted

AN-T80020 Diagnostics Procedure

Select Debug | Debug. A long thin window entitled IEC1131 TOOLSET – (application) – Debugger should appear. This will have a bold black line of text giving the state of the application. This window is called the Debugger window and it is the key to all online controls. To disconnect from the system, close this window and all other online windows will also close.

If the black line of text says RUN, you are connected to the system. Go on to the next page.

If the black line of text does not say RUN, and the system is clearly running (flashing ‘Run’ LED on the processor), then there is likely to be a communications problem.

Using a serial port, you will see ‘Disconnected’. Check that the keyswitch is set to Maintain and the maintenance cable is connected. Then try to connect again. Using Ethernet, the online session will abort with the message ‘Cannot install the communication’. You will need to close down all Toolset windows to reset this error.

Check the keyswitch position. Check that the Ethernet network is connected by sending a ‘ping’ command to the communications interface port using the following command (with the appropriate IP address) in a command window. Then try to connect again.

Issue 12 Feb 11 AN-T80020 8

Trusted

AN-T80020 Diagnostics Procedure

You will see a window similar to the ‘Programs’ window, now called the ‘Debug Programs’ window. This gives access to online diagnostics. You cannot close this window. To end an online session, close the Debugger window.

Open the I/O connection table by clicking on the icon shown above or menu Project | I/O connection.

Each module in the system has an equipment definition. Imagine this as a marshalling terminal rail, with several blocks of terminals. These terminals are shown as icons appearing like screws, in several different terminal blocks called boards. Each board is used to send data to or from the module, and some of it is useful for diagnostics.

Each equipment definition is described in the product description for the module. Note that equipment definition ttmrp is the processor (see PD-T8110B) and tci is the communications interface (but there is no data on the tci boards).

Each equipment definition is allocated to a chassis and slot position where the module is. Click on the first board in the definition (for the 8403 shown, click on DI). At the top of the data on the right is the chassis and slot position.

If you are looking for an error code, find the definition with the same chassis and slot number as the faulty module. Then click on the HKEEPING board and scroll down to the last three channels. In the example above, the module is healthy. All three slices are reporting a zero error code.

If any of the last three channels is not zero, note the number.

Issue 12 Feb 11 AN-T80020 9

Trusted

AN-T80020 Diagnostics Procedure

The error code number is shown in decimal (base 10). However, the codes are defined in hexadecimal (base 16) and the number needs to be converted.

Open the Windows Calculator. Select the Scientific view (View | Scientific).

Select ‘Dec’ (decimal) as shown above. Type the error code number. Select ‘Hex’ (hexadecimal). The calculator will convert the number.

Look up the hexadecimal number in the table in this manual. The error codes are listed in hexadecimal number order, which is like decimal but has six extra digits: 0,1,2,3,4,5,6,7,8,9,A,B,C,D,E,F,10,11,...

In this case, 52?? Indicates an input channel fault. It is on channel 16, because 10 in hexadecimal is 16 in decimal.

Follow the advice given for the error code.

You can avoid having to convert the error code if an integer variable is wired to each channel, and its format is set to 1A2B (four digit hexadecimal). The toolset will convert the value into hexadecimal for you.

It is important to check for error codes before pressing the main processor reset pushbutton, because pressing reset will clear all fault indications and fault filter counters. It is possible that a rare or slow fault has occurred, due to a genuine problem, which may not occur again for some time.

Once you have collected all fault codes and noted them, you may press the processor Reset pushbutton to clear them.

Issue 12 Feb 11 AN-T80020 10

Trusted

AN-T80020 Diagnostics Procedure

Other data on Equipment Definitions

All modules provide information on temperature, in many cases at several points throughout the module. Note that these temperatures are ranged differently, e.g. on the processor 1°C = 10 counts, but on the I/O modules, 1°C = 256 counts. The operating range of all native 8000 series modules

except the Gateway module which contains a PC104 computer) is –5 to 60°C. Since there is no fan

( fail monitoring, there should be alarms set on overtemperature in the application.

There is also detailed information on internal voltages and currents at many points in each module, measured in millivolts and milliamps. This covers both internal measurements and field I/O condition. These should approximate to the stated voltage (e.g. 24V or 8V) or show that currents are shared evenly and not overloaded.

There are channels left spare for condensation monitors. These are not used. The main processor definition (TTMRP) gives some digital system status information including the number of locked variables in the application, a variety of digital system alarms including the System Healthy LED state, and the health of the active and standby processors.

Each I/O module definition provides details of the state and condition of each channel, with discrepancy alarms for where the triplicated slices disagree on the state of an I/O point.

All of the above data may be connected to in the application and used for diagnostic alarms and actions. The data is described in the Product Descriptions for each module.

Issue 12 Feb 11 AN-T80020 11

Trusted

AN-T80020 Diagnostics Procedure

Analysis Tool

This application can collect command line diagnostics online from a live system. It can analyse the collected data and provide advice and reports. It can also analyse logs taken by the macro program Dumptrux in the same way. It can erase the system logs.

The program installs itself by default into the same directory as the Toolset and other 8000 series software. It also provides the option of a desktop icon and a Quick Launch icon.

On opening, you can either go online (Online | Comms Setup ...) or choose an existing file to analyse (File | Open log file). At each point, the bottom banner shows the options available to you.

Open Analysed Data will open a file that this program has created, which has the log and all reports in it. After opening a log file, you can save the analysed data. Analysed data can be opened quicker than a log file because the analysis work has already been done.

Issue 12 Feb 11 AN-T80020 12

Trusted

AN-T80020 Diagnostics Procedure

Online

The online comms setup allows Ethernet or serial connection. Choose the Ethernet IP address or serial port number as appropriate.

Choose the automatic diagnostic collection option:

1) None

This just makes a connection and opens the terminal.

2) Choose

This collects enough data to discover the modules fitted in the system and takes only a few seconds. It then provides a picture or tree of the system which can be clicked on to get data from each module.

2) Not I/O

This collects all diagnostic data from the processor(s), communication interfaces, expander modules and chassis, which will only take one or two minutes. This information is often the most important, and is necessary even if the fault is in an I/O module. It also provides a picture or tree of the system, so that data can be gathered from any I/O module.

3) All

This collects all the above data, but also collects from all the I/O modules. This will take some time, especially if the I/O module logs are collected. It may be appropriate to ask a user to collect all data, to avoid needing to explain which data is required.

For a serial connection, use a TC-304 maintenance cable. Check that the maintenance cable is plugged into the PC serial port and the processor’s front panel port. Ensure the processor keyswitch is turned to ‘Run’. The Analysis Tool cannot communicate if the keyswitch is in the ‘Maintain’ position. If the processor front panel port does not seem to work, the Analysis Tool can also be connected to a communication interface front panel port.

If you are using Ethernet, check that the system and PC are connected to the Ethernet network with addresses on the same subnet. The keyswitch can be in either position.

On clicking OK, you should see a title line (which assists the analysing code) and a prompt (ci:? for Ethernet and mp:? for serial). If you only see an empty window or the program reports it cannot make a connection, there is no communications. For a serial connection, check the cable and the keyswitch position, then press Enter to request a prompt. For an Ethernet connection, check that the Ethernet network is connected by sending a ‘ping’ command to the communications interface port using the ‘ping’ command (with the appropriate IP address) in a command window as shown in the Toolset diagnostics section above. Then try Online | Comms Setup again.

Issue 12 Feb 11 AN-T80020 13

Trusted

AN-T80020 Diagnostics Procedure

Once the program has a connection, it will start the automatic collection option that was chosen. Leave the collection to run. It will report its progress in the bottom banner.

Issue 12 Feb 11 AN-T80020 14

Trusted

AN-T80020 Diagnostics Procedure

Online Options

Once the online collection has finished, more options are available on the Online menu.

‘Set the time/date’ allows you to set the clock in the system.

You can enter a time/date using the middle ‘Time to set’ options, and click ‘Set this time’. Clicking ‘Copy and Set’ does both actions.

‘Copy computer time’ will put the current PC time and date into the ‘Time to set’ options. ‘Copy system time’ will put the current system time and date into the options; you can then correct this, e.g. for time zone changes.

At the moment the ‘Time to set’ is correct, click ‘Set this time’. This is most reliable on a serial cable to the processor front panel, because there is a delay in connection from a communication interface which can cause the request to be missed.

Issue 12 Feb 11 AN-T80020 15

Trusted

AN-T80020 Diagnostics Procedure

‘Auto set time/date’ sets the time automatically from the computer’s clock. It firstly measures the

delay between sending a new line and receiving a prompt, and then plans a moment to set the time every ten seconds. On setting the time, the new line is sent at a calculated moment before the second to attempt the most accurate time synchronization. Serial is the fastest medium with latencies of a few milliseconds; Ethernet latencies are at least twenty times longer. This still cannot be accurate to the

illisecond, and only IRIG can provide true millisecond timestamping.

‘I/O Module Options’ provides the diagnostic privileged access password and chooses the data to

be collected from I/O modules. The Analysis Tool must have the diagnostic password entered before collecting data from I/O modules. The options dialog will appear if you try collecting or erasing I/O modules without having entered the password.

Enter the diagnostic password. The password may be changed using the System.INI configuration file; if in doubt, contact support@icstriplex.com.

You can also choose:

Collect logs: whether to get the event logs from the I/O modules plus general data, or just the general data. This can be used to speed up collection if you aren't interested in the logs; they can take a long time to collect and can be very large.

Collect from slice: you can speed up diagnostics by just collecting from faulty slices. Choose the slice you want; the default is all three.

Issue 12 Feb 11 AN-T80020 16

Trusted

AN-T80020 Diagnostics Procedure

‘Erase Logs’ deletes all system event logs.

Do not erase any logs unless you are sure they are no longer necessary. For example:

• The logs are too big to collect. Erase the logs, leave the system to run its diagnostic routines (24 hours), then collect the logs to inspect current problems.

• Collect the logs once a month for an archive, and erase the logs after each collection to keep them small.

The default option is to erase all logs in the system. This includes the main processor current and backup logs (in both processors if two are fitted), all communication interface logs, and all I/O module logs.

If you de-select ‘Erase all logs in system’, you can choose which module logs to erase. You can select one I/O module from a drop-down list.

The Analysis Tool will collect the first 90 lines of each I/O module log before erasing it. It checks these lines for manufacturing test entries, and puts these test entries back into the log after erasing it. This assists with module diagnosis and repair. Note that Dumptrux does not preserve these test entries and should no longer be used for erasing logs.

‘Analyse Data’ passes the collected data to the analysing side of the program, which will prepare

reports. Choose this option when you have collected all the data you want, and you want to analyse it. After this, the program behaves exactly as if you had opened an existing file through File | Open. You can still go back online however, using menu option Online | Terminal. The analysis side of the tool is described later.

Issue 12 Feb 11 AN-T80020 17

Trusted

AN-T80020 Diagnostics Procedure

System Graphic / Online Tree Window

When you connect, the Analysis Tool will interrogate the system and make a clickable window of the system shape.

If you hover over a module, the window title shows the module type and a pop-up ‘Tool Tip’ shows whether you have already collected from that module. A grey module has not been collected, a light blue module is being collected, and a dark blue module has been collected. If you click on a module or chassis end, the Analysis Tool will collect all useful data from that part of the system.

If there are two processors, the left-hand processor in the graphic is always the active processor (the Analysis Tool cannot distinguish left and right slots).

Issue 12 Feb 11 AN-T80020 18

Trusted

AN-T80020 Diagnostics Procedure

Manual Command Entry

You can type commands into the online window. This is recommended only if you are competent with the 8000 series systems and you know the command you need, or the first-line diagnostics specifically asks you to type these commands. The most useful commands are:

ls b Show backup log of events before the last power-down of the main processor

ls d Show current main processor log since last power-up (moved to backup log on power loss)

ls l Real-time monitor of processor log

The terminal is a simple implementation and will not refresh the screen until a new line is entered. This is most evident with ls l; type ctrl-c to exit and press Enter. Teraterm Pro is recommended for full manual command-line access.

The Main Processor log is available without privileged (password) access, and does therefore not invalidate any safety protection. A later section describes some of the possible entries in these logs.

Issue 12 Feb 11 AN-T80020 19

Trusted

AN-T80020 Diagnostics Procedure

Offline

You can either:

1) analyse some data you have collected online (see above) or

2) open an existing log file (collected using the Analysis Tool, Dumptrux or a terminal program) or

3) open a file of analysed data previously made by this program.

If you want to analyse your online data, use Online | Analyse Data.

If you want to analyse a saved file, use File | Open log file.

The analyser will read each log command and gather its data, then prepare the data for the reports. This process can take time on large logs. If it takes forever, you can cancel it by clicking the menu option Click here to stop. The reports will only contain information from the data analysed so far.

Sometimes the Analysis Tool will be unable to open the log. If it fails, it will give the message shown above. Some logs are corrupted due to communications noise, and sometimes the I/O modules will not store their logs properly (the logging process is not the highest priority task and it can be interrupted). In some cases, the system may contain modules which reply with message formats that have not been tested (or accounted for) with the Analysis Tool, causing the code to abort. There is little that can be done to cope with corrupted logs, but it may be possible to account for an unknown reply format. Please send the log to ICS Triplex as instructed.

Issue 12 Feb 11 AN-T80020 20

Trusted

AN-T80020 Diagnostics Procedure

Once open, you see the System Health view. This shows a summary of advice given by the program and it is described later.

File Menu

The File menu provides basic tools as follows, depending on which view is shown:

• Open log file: chooses a new file to open. (Ctrl-O will also work)

• Open analysed data: opens a file created by the Save analysed data option below. It will open

quickly because the analysis work is already done.

• Save analysed data: saves a file containing the log and all report data. This can be opened later by the Open analysed data option above. The file can be very large, but it will compress well. Please compress it if you want to email it. (Ctrl-S will also work)

• Save this report: saves the currently displayed report to a file.

• Copy selection: copies the selected text for pasting into other documents. (Ctrl-C will also

work)

• Print this view: sends the current view to the printer. (Ctrl-P will also work)

• Exit: closes the Analysis Tool.

View Menu

The View menu lets you choose the different reports and displays that the Analysis Tool provides. The contents of this menu will change depending on the report view you have chosen. The reports are described on the next pages.

Issue 12 Feb 11 AN-T80020 21

Trusted

AN-T80020 Diagnostics Procedure

Log View

This shows the initial view of the whole file, as if it was in a text editor. Experienced engineers can search through the data for details that may not be captured by the reports. Use the Find menu to help with searching.

Find Menu

The Find menu has the following options for manual searching through the log.

• Text … : simple text search as in Notepad, with similar options. (Ctrl-F will also work)

• Current Log: goes to next ls d command in the log (from the active processor, standby processor or communications interface)

• Backup Log: goes to next ls b command in the log

• Chassis/slot ... : goes to the next I/O module prompt for the given

chassis, slot and slice.

Analysis View

This view shows a representation of the system and provides detailed reports on parts of the system. It will show the active processor’s individual report when opened. A navigational window lets you choose a report.

This shows a simple picture of the system, and provides access to the reports described below.

Hovering the mouse over a module will show its description in the title, and an explanation of the colour.

Beige: no module fitted

Green: fitted module, either healthy or no data gathered

Amber: possible fault, needs further investigation

Orange: definite fault on that module (or its configuration).

Red: critical fault found which should be reported to ICS Triplex.

Blue border: upgrade recommended. Thicker borders are higher

priority.

Left-click a module to see its main report, as described below.

Right-click a module to see the other available reports in a screen menu.

This system has one processor. If it had a second processor, it would be shown in the right-hand slot. The left hand slot is always the active processor – it is not possible for the program to determine which physical slot the module is in.

Processors and communication interfaces have three reports. Left-clicking on the module provides the basic report. Right-clicking provides the current and backup logs. The contents of the processor log are described in a later section.

Issue 12 Feb 11 AN-T80020 22

+ 49 hidden pages