XCell Troubleshooting Manual

TROUBLESHOOTING MANUAL
VERSION 1.07
Troubleshooting M anual Version 1.07
© Microsol Limited 2000
This document contains proprietary information of

Microsol Limited. The information and designs in the
document are covered by international copyright and a
number of international patents existing and pending.
Microsol, and its legally appointed licensees, reserve the
right to seek full redress in the case of any infringement.
The information in this document is subject to change

without prior notice. Microsol does not assume
responsibility for any errors in fact or design in this
publication. Specifications can and do vary in different
applications. The publication is provided for general
information only and shall not form part of any contact.
Microsol Contact Information

Address: Microsol Limited,
The Centre for Monitoring and Control,
Enterprise Complex,
Pearse Street,
Dublin 2,
Ireland.
Phone: +353-1-415 3700
Fax: +353-1-671 6343
email: info@microsol.com
web: www.microsol.com
Page ii
Troubleshooting Manual Version
1.06
Table of contents
1. INTRODUCTION .................................................................................................1
2. Direct Product Support and Assistance .............................................................3
3. Basic Definitions and Abbreviations..................................................................5
4. Diagnostic Facilities..........................................................................................7
5. Reference Documentation ................................................................................9
6. Table of Potential Problems........................................................................... 11

XCell Fault Finding Guide ................................................................................... 12
Accumulator Fault Finding Guide ........................................................................ 13
Sequence Of Events Fault Finding Guide............................................................. 15
7. PROBLEM SOLVING STRATEGY...................................................................... 18
OPERATOR W ORKSTATION FAULT FINDING GUIDE ............................................... 20
XCELL FAULT FINDING GUIDE ............................................................................. 45
ACCUMULATOR FAULT FINDING GUIDE................................................................. 59
AC ANALOGUE INPUT FAULT FINDING GUIDE ....................................................... 65
DIGITAL INPUT FAULT FINDING GUIDE .................................................................. 69
ANALOGUE OUTPUT FAULT FINDING GUIDE ......................................................... 75
DIGITAL OUTPUT FAULT FINDING GUIDE .............................................................. 81
ANALOGUE INPUT FAULT FINDING GUIDE ............................................................. 85
SERIAL COMMUNICATIONS FAULT FINDING GUIDE ................................................ 93
XCELL FIELDNET LAN FAULT FINDING GUIDE...................................................... 99
TIME SYNCHRONISATION FAULT FINDING GUIDE................................................. 105
SEQUENCE OF EVENTS FAULT FINDING GUIDE................................................... 109
IED FAULT FINDING GUIDE................................................................................ 111
Page iii
EXPRESS FAULT FINDING GUIDE ....................................................................... 115

EXPERT FAULT FINDING GUIDE.......................................................................... 121
EXPLORE FAULT FINDING GUIDE ....................................................................... 130
8. APPENDIX ONE ............................................................................................. 134

SYSTEM INITIALISATION DIAGNOSTICS ................................................................. 134
FIRMWARE AND OPERATING SYSTEM DIAGNOSTICS ............................................ 135
APPLICATIONS INITIALISATION DIAGNOSTICS ....................................................... 135
SYSTEM RUNTIME DIAGNOSTICS ........................................................................ 143
SYSTEM MODULES ............................................................................................ 144
I/O SERVER MODULES ...................................................................................... 144
HIGH LEVEL POINT TYPE MODULES.................................................................... 144
AC MEASUREMENT INFORMATION MESSAGES ..................................................... 144
IEC – 063 ....................................................................................................... 174
IEC – 110 ....................................................................................................... 176
NET – 187 ...................................................................................................... 180
Page iv
1.06
1. INTRODUCTION
This document provides support knowledge for customers installing and operating XCell
hardware and software in the field.
The manual is subdivided into different sections corresponding to the major components of a
typical XCell system. This approach helps to focus on the specific area requiring attention,
thus allowing a more efficient isolation of the problem leading to clearer diagnosis and
resolution.
The problem solving sections contain a list of potential problems along with likely causes
and corrective actions.
Page 1
Page 2
1.06
2. Direct Product Support and Assistance

Any problem that cannot be resolved using this documentation should be
referred directly to your system supplier.
Where an XCell product is installed under a support agreement with Microsol,

all queries should be communicated to Microsol directly. Support is also
available through email at support@microsol.ie
Page 3
Page 4
1.06
3. Basic Definitions and Abbreviations
AC Alternating Current
AI Analogue Input
AO Analogue Output
BRAM Battery Backed RAM
CPU module XCell processor module
CT/VT array Current Transformer / Voltage Transformer array
DDI Double Digital Input
DDE Dynamic Data Exchange
DI Digital Input
DO Digital Output
Dongle Software protection key on the PC parallel port
DSP Digital Signal Processing
EPROM Erasable Programmable Read Only Memory
FO Fibre Optic
FSD Field Service Diagnostics
IED Intelligent Electronic Device
IOA Information Object Address
LAN Local Area Network.
LED Light Emitting Diode
HMI Human Machine Interface
OLU On Line Unit
PC Personal Computer
PSU Power Supply Unit
RAM Random Access Memory
RMS Root Mean Square
RS-232 IEEE Serial communications standard
RS-485 IEEE Serial communications standard
RTU Remote Terminal Unit
SAV Save hardware configuration
SHC Show Hardware Configuration
SOE Sequence Of Events
Page 5
Page 6
1.06
4. Diagnostic Facilities
A range of diagnostic facilities is provided with the XCell product. These should be used
in conjunction with this manual to isolate and diagnose any problems. These facilities
include:
• Data quality information on each data point. This is generally available at the Master
Station / Control Centre display (providing the installed protocol supports it).
• XCell unit status and I/O module status which is available as digital status points at
the Master Station / Control Centre display.
• Local Front Panel diagnostics to assist fault finding. For further information refer to
the XCell User Manual and Appendix One of this manual.
• eXplore diagnostic software which runs on a PC and can assist fault finding. For
further information please refer to the eXplore User Manual.
• Vision diagnostic screens where the Vision HMI product is used.
Page 7
Page 8
1.06
5. Reference Documentation
Problem Involving Please Refer To
Operator Workstation Problems
PC problems. PC User Documentation
Printers Printer User Documentation
Printer Server Printer server User Documentation

Tapes backup units Tape Backup Unit User Documentation
Disks Units Disk Unit User Documentation
Cables Cable Documentation
Modems Modem Documentation
Vision software Vision Manual and Online Help Facility
XCell Hardware Problems XCell User Manual
Power up sequence XCell User Manual
Connection problems XCell User Manual
XCell FieldNet LAN problems XCell FieldNet Lan Fault Finding Guide
section of this document.
I/O Card Problems
Analogue Output Modules XCell User Manual
Analogue Input Modules XCell User Manual
Digital Input Modules XCell User Manual
Digital Output Modules XCell User Manual
IED Problems
Relay address numbers Changing Manufacturer supplied IED User Documentation
Communication Problems Manufacturer supplied IED User Documentation
Communication Problems
Cables XCell User Manual
Connectors XCell User Manual
Network termination XCell User Manual
Configuration Problems
Setting parameters eXpert User Manual
Downloading Configurations eXpert User Manual
eXpress software eXpress User Manual
Page 9
Page 10
1.06
6. Table of Potential Problems

Potential Problem Page
Operator Workstation
The Operator Workstation is not powering ON. Page 21
The Operator Workstation is powered ON but is not starting up properly. Page 21
Message on booting the PC indicating that a “Non system disc is installed in the drive”. Page 21
Operator Workstation not running Vision application. Page 22
PC monitor problems Page 22
Message displayed indicating that the Vision Tag Count is limited to a certain number. Page 23
Printer not powered ON. Page 23
Printer not printing. Page 23
“Print Screen” software menu item in Vision is not responding. Page 24
Vision system stops and is unresponsive to all operator actions. Page 25
No response from the field when attempting to carry out a routine action previously carried out Page 25
through Vision.
Unable to retrieve logged data. Page 26
Communications alarm is reported in the Alarm Log. Page 26
Plant status changes not being reported to the Event Log. Page 29
Incorrect analogue values displayed for long periods but correct themselves again for long Page 29
periods.
Incorrect analogue values displayed on the HMI. Page 31
A single point is reported as a red box with three question marks ??? on the Vision HMI screen. Page 32
Vision displays one or more points as a red box with three question marks ???. Page 33
Page 11

PC LAN fault Page 35
Each point is displayed on the Vision HMI screen as a red box with three question marks ???. Page 36
Multiple I/O Bad alarms reported in the Alarm Log. Page 37
Unable to drive an XCell output from Vision. Page 38
XCell I/O module failure is reported in the Alarm Log. Page 40
XCell processor module failure is reported in the Alarm Log. Page 41
Vision system reports fleeting alarms. Page 42
Cell processor module is repeatedly reported OK and then Failed. Page 42
Data points are toggling between good values and values that are clearly in error i.e. points Page 42
toggle between normal Vision colours and red with three question marks ???.
Problem logging on to Vision, password rejected as invalid. Page 43
Password known to be correct however, access is denied. Page 43
Unable to access certain aspects of the Vision system. Page 43
XCell Fault Finding Guide

No power on any XCell processor module in a rack. Power LEDs are not illuminated. Page 48
No power to a single XCell processor module in a rack. Power LED is not illuminated. Page 49
XCell processor module does not cycle through its boot up sequence Page 50
XCell processor module does not cycle through its boot up sequence following a firmware Page 52
upgrade.
XCell processor module rebooting continuously. Page 54
XCell processor module rebooting while running an eXpress logic sequences. Page 56
Non-volatile memory fault. Page 56
Page 12
1.06

Online unit status changing at random (as observed on the front panel FSD display). Page 57
Online LED is not illuminated on the front panel of the XCell Processor module. Page 57
Accumulator Fault Finding Guide

High Speed Counter (HSC) module not being scanned on the Front Panel LED matrix. Page 60
Accumulator values are not being produced by the source XCell processor module. Page 62
Accumulator values not available in another XCell processor module. Page 63
Accumulator values are not received through a communications interface. Page 63
AC Analogue Input Fault Finding Guide

ACI front panel LED matrix does not reflect the expected display. Page 67
Inaccurate AC measurements. Page 68
Digital Input Fault Finding Guide

Digital Input LED matrix not reflecting the plant status. Page 70
XCell Processed Digital Input (SDI, DDI etc) is not functioning in the XCell processor module. Page 71
XCell Raw Digital Input is not available in another XCell processor module. Page 72
XCell Processed Digital Input value (SDI, DDI etc) is not available in another XCell processor Page 72
module.
Processed Digital Input value (SDI, DDI etc) not received across a protocol interface. Page 73
Raw Digital Input not received across a protocol interface. Page 73
I/O not transferred by the XCell protocol interface unit. Page 74
Analogue Output (AO) Fault Finding Guide

Unable to drive an Analogue Output from eXplore on the local XCell processor module. Page 77
Unable to drive an Analogue Output from eXplore on another unit. Page 79
Unable to drive an Analogue Output through a protocol interface module. Page 79
Page 13

Digital Output (DO) Fault Finding Guide
Unable to drive a Digital Output from eXplore on the local unit. Page 82
Unable to drive a Digital Output from eXplore connected to another XCell processor module. Page 83
Unable to drive a Digital Output through a protocol interface. Page 84
Multiple control outputs cannot be driven on the same XCell processor module. Page 84
Analogue Input (AI) Fault Finding Guide

Analogue Input not scanning on the front panel LED matrix. Page 87
Analogue Input values not changing in the source I/O unit – verified using eXplore. Page 88
Analogue Input values are not correct when viewed within the source XCell processor module Page 90
– verified with eXplore in the source XCell processor module; (Analogue Input values should be
displayed as a percentage of the configured range).
Analogue Input values not received across an XCell protocol interface Page 92
Analogue Input values are not correct when viewed in another XCell processor module – Page 92
verified with eXplore.
Serial Communications Fault Finding Guide

XCell serial communications not working. Page 95
XCell not communicating, -RXD LED is flickering but TXD indicator LED not lighting. Page 98
Communication LEDs not illuminating as expected. Page 98
Communications not working after the unit was powered OFF for some time. Page 98
XCell appears to have lost its configuration data. Page 98
XCell FieldNet LAN Fault Finding Guide

General XCell FieldNet network Fault Page 101
XCell processor module cannot be seen by another XCell processor module. Page 103
Fibre Ring Monitoring module (OPB) displays ”CLS” on the Front Panel. Page 104
Time Synchronisation Fault Finding Guide
Page 14
1.06

Master station events time-stamped as 01 January 1970. Page 106
Sequence Of Events Fault Finding Guide

Unable to upload Sequence Of Events (SOE) file via IEC870. Page 110
IED Fault Finding Guide

No data values being displayed from IED Page 112
IED failed or communications fault. Page 113
IED device status is "Failed". Page 113
eXpress Fault Finding Guide

Unable to connect to XCell target processor module for Debugging. Page 116
Communications lost while debugging XCell target on a regular basis Page 117
eXpress program is not responding to I/O. Page 117
eXpress application is not activating outputs Page 118
eXpress unit is constantly rebooting. Page 118
eXpress application is not operating Page 118
eXpress application is not activating outputs. Page 119
I/O connection error generated in eXpress compiler. Page 119
eXpert Fault Finding Guide

Unable to enter a new value in a field. Page 124
Newly entered value not stored in the field. Page 124
Failed to download to the XCell target XCell processor module. Page 124
Test function failed in the FieldNet Tab Dialogue from the Comms menu. Page 125
CFG 027 message returned on the PC. Page 126
Error message “Exception in Delete Object errno = 2” Page 126
Page 15

“Protocol Instantation Failure” message encountered when trying to download a DDI, SDI Page 126
or DO configuration from eXpert.
Error encountered when trying to configure Analogue or digital I/O modules. Page 127
Error encountered when trying to configure an XCell processor module too soon after Page 128
powering on.
eXplore Fault Finding Guide

Raw Digital Input is not displayed correctly in eXplore connected directly to the input unit. Page 131
Raw Digital Input is not displayed correctly in eXplore connected to another XCell processor Page 131
module.
Processed Input (SDI, DDI etc) is not displayed correctly in eXplore connected directly to the Page 131
input unit.
Processed Input (SDI, DDI etc) is not displayed correctly in eXplore connected to another XCell Page 132
processor module.
Analogue Input is not displayed correctly in eXplore. Page 132
Page 16
1.06
Page 17
7. PROBLEM SOLVING STRATEGY
Page 18
Operator Workstation Fault Finding Guide
Troubleshooting
Manual Version 1.06
Page 19

The HMI comprises the operator workstations (Personal
Computers) their peripheral devices, cables, connectors
and software controlling the system. Further information
is to be found in the various elements of documentation
supplied with the system.
Page 20
Troubleshooting
Manual Version 1.06
Problem Possible Causes Actions

The Operator • The PC or monitor may not be • Ensure that the PC and
Workstation is not switched ON. monitor are plugged in and
powering ON. switched ON.
• The PC or monitor may not be • Ensure that the PC and
connected to a power source. monitor are connected to
an adequate power
source.
• PC or monitor may be powered • Ensure that the PC and

from an incorrect supply monitor are configured to
voltage. operate from the available
supply voltage.
• A power fuse may be blown. • Check the plug fuses on

both the PC and monitor.
The Operator • Operator Workstation not • Check previous fault

Workstation is powered powered ON. descriptions.
ON but is not starting
up properly.
• PC keyboard is disconnected. • Ensure that the keyboard

is connected to the PC.
• Floppy disc inserted in the • Remove any floppy disc

Floppy Disc Drive. from the Floppy Disc Drive
and start again.
• PC configuration fault. • Refer to the PC manual for

specific PC faults.
Message on booting • Floppy disc installed in the • Remove the floppy disc
the PC indicating that a Floppy Disc Drive during boot- from the Floppy Disc Drive
“Non system disc is up. and start again.
installed in the drive”.
Page 21

Operator Workstation • Operator Workstation not • Refer to the actions for
not running Vision powering ON. “The Operator
application. Workstation is not
powering ON ”. Page21.
• Vision application may not be • Verify that Apps are open

starting. using Alt+Tab
• Operator Workstation not • Refer to the actions for

starting up properly. “The Operator
Workstation is powered
ON but is not starting up
properly” page 21.
• Software licence may not be • Ensure the correct

installed or may have expired. software licence has been
installed.
PC monitor problems • No Power to the monitor. • Ensure that the monitor is
plugged in to an active
power socket.
• Ensure that all power

fuses are intact.
• No proper images are • Ensure that the PC-

displayed on the monitor. monitor cable is properly
installed at both ends.
• Faulty PC graphics card or • Test the monitor on

cable. another PC to confirm the
problem, (contact the
system supplier for further
instructions).
Page 22
Troubleshooting
Manual Version 1.06

Message displayed • The software licence installed • Acquire a new software
indicating that the allows maximum number of licence supporting a
Vision Tag Count is Tag points to be defined and higher Tag count.
limited to a certain this limit is now reached or
number. exceeded.
• A Dongle is not installed, but • Install a Vision dongle on

may be required on the PC. the parallel port of the PC
(if required).
Printer not powered • The printer may not be • Ensure that the printer is
ON. switched ON. switched ON.
• The printer may not be • Ensure that the printer is

connected to a power source. connected to the power
source.
• Printer powered from incorrect • Ensure that the printer is

supply voltage. configured to operate from
the available supply
voltage.
• Power fuse may be blown. • Check both plug and

printer fuses.
Printer not printing. • Printer not powered ON. • Check previous fault
description.
• No paper. • Insert the correct type of

paper. Refer to the
supplied printer
documentation.
Page 23

• No Ink. • Replace ink cartridge(s)
with appropriate
replacements. Refer to the
supplied printer
documentation.
• The printer is not connected to • Ensure that the printer is

the printer server. correctly connected to the
PC or to the LAN server
device as appropriate.
• The printer is not networked to • Verify the LAN connection

the specific operator between the operator
workstation. workstation and the printer
server (see the printer
server documentation).
• PC LAN fault • Refer to the actions for

“PC LAN fault”. Page 35.
• Other printer fault(s). • Refer to the printer

documentation for specific
printer faults.
“Print Screen” software • No power to the printer. • Ensure that printers are
menu item in Vision is powered ON at all times.
not responding
• Printer not printing. • Refer to the actions for
“Printer not Printing”.
Page 23.
Page 24
Troubleshooting
Manual Version 1.06

Vision system stops • The password being used may • Ensure the password is
and is unresponsive to be incorrect or it may have correct for the level of
all operator actions. timed out access required.
• Check that the password

has not timed out. Enter
the password again if
necessary.
No response from the • Communications links are • Check communications

field when attempting to faulty or broken. There may be between the operator
carry out a routine communications problem workstation and the field.
action previously involving the XCell FieldNet Refer to the “XCell
carried out through LAN. FieldNet LAN Fault
Vision. Finding Guide” section of
this manual for further
details. Page 99.
• XCell processor modules may • Examine local Vision

be off-line. diagnostic screens, check
XCell processor module
status, check I/O modules
connected to each XCell
processor module. Refer
to the Vision Manual and
Online Help Facility also
the XCell User Manual
for further information.
• Refer to the actions for

“Vision system stops
and is unresponsive to
all operator actions”.
Page 25.
Page 25

• There may be a faulty Digital • Refer to the “Digital Input
Input module. Fault Finding Guide”
section of this manual for
further details. Page 69.
• There may be a faulty Digital • Refer to the “Digital

Output module. Output fault Finding
Guide” section of this
manual for further details.
Page 81.
• Incorrect or faulty configuration • Refer to the “eXpert Fault

has been downloaded to an Finding Guide” section of
XCell unit. this manual for further
details. Page 121.
• There may be a problem with • Refer to the “Serial
the cabling between the HMI Communications Fault
and the XCell units in the field. Finding Guide” section of
this manual for further
details. Page 93.
• One or more XCell modules in • Refer to the “XCell Fault

the field may have developed a Finding Guide” section of
fault. this manual for further
details. Page 45.
Unable to retrieve • Stored data has been • Verify that the date of the
logged data. automatically deleted by required data does not
Vision archiving system. exceed the configured
archive period.
• No data exists because • Ensure that data exists for

nothing happened during the that period.
period under review.
Page 26
Troubleshooting
Manual Version 1.06

• No filter has been set to hide • Turn off all filters to view
some of the required data. all data. See the Vision
Online Help Facility for
further information.
Communications alarm • PC-XCell communications link • Check PC-XCell

is reported in the Alarm may be disconnected. communications link
Log. (cables, modems, etc
where applicable).
• PC-XCell Ethernet LAN not • When connected via
properly terminated. Ethernet, ensure that the
BNC terminations are
securely fastened at both
ends of the PC-XCell LAN
cable.
• XCell processor module acting • Verify that the XCell

as the HMI interface unit is not interface processor
operational or is not properly module is operational and
configured. correctly configured using
eXpert. (For further details
refer to the XCell fault
Finding Guide section of
this manual (page 45), the
XCell User Manual and
the eXpert Manual.
Page 27

• Vision may not be connected • Ensure that the XCell
to the XCell processor module processor module
configured for communications. configured for
communications is visible
to the Vision system i.e.
that Vision is connected
to the correct unit. (Refer
to the XCell Fault
Finding guide and the
Serial Communications
Fault Finding Guide
sections of this manual
(pages 45 and 93
respectively).
• Communications XCell • Ensure that the XCell

processor module is powered system is powered ON.
OFF.
• XCell FieldNet LAN is faulty. • Refer to the actions for
“XCell FieldNet LAN
fault”. Page 101.
• XCell processor module • Refer to the XCell Fault

problem. Finding Guide section of
this manual (page 45) and
for further details.
• Configuration not downloaded • Ensure that all relevant

to the XCell interface module. communications tables
have been downloaded to
the XCell interface
processor module. (See
and eXpert User Manual
for further details).
Page 28
Troubleshooting
Manual Version 1.06

Plant status changes • Communications problem. • Refer to the problem
not being reported to “Communications alarm
the Event Log. is reported in the alarm
log” for actions on this
item. Page 27.
• Vision communications server • Verify other points are

is halted. operational through the
same communications
server. If not shutdown the
operator workstation with
the communications
server and restart it again.
(Refer to the Vision
Manual and Vision
Online Help facility for
further information).
• Vision application is halted. • If none of the operator

facilities are functional
then shutdown the
Operator Workstation and
restart it again. (Refer to
the Vision Manual and
Vision Online Help
facility for further
information).
• XCell module fault involving • Refer to the actions for

processed digital data “Processed Digital Input
value (SDI, DDI etc) not
received through a
protocol interface.” Page
73.
Page 29

• The IEC-870 Dynamic Data • Check that the DDE
Exchange (DDE) Server may Server is running using
not be running on the Vision Alt-Tab. Refer to the IEC-
workstation. 870 DDE Server Manual
for further information).
• Plant device (IED) may be • Ensure that the IED is

powered OFF, offline or correctly configured and
defective. communicating. (Refer to
the manufacturer-supplied
documentation for the
device).
• Ensure that the correct

binary inputs are
marshalled for the device.
(Refer to the
manufacturer-supplied
documentation for the
device).
• Ensure that the correct

address for the point
within the device has been
configured in the XCell
communications
processor module. (Refer
to the manufacturer-
supplied documentation
for the device and the
eXpert User Manual).
Page 30
Troubleshooting
Manual Version 1.06

Incorrect analogue • Incorrect settings on one • While the problem exists
values displayed for XCell interface of a redundant note the active XCell
long periods but correct pair. The problem only exhibits interface processor. Using
themselves again for itself when that link is active. the configuration tool for
long periods. the appropriate interface
unit, ensure that the
correct analogue points
are mapped to the correct
protocol addresses.
Alternatively verify the
mapping on both interface
units. Download the
protocol maps to the XCell
interface processors.
• Incorrect settings on one PC • While the problem exists

communications server of a note the active PC
redundant pair. The problem communications server. In
only exhibits itself when that the configuration of this
link is active. server ensure that the
correct analogue points
are mapped to the correct
protocol addresses.
Alternatively verify the
mapping on both PC
communication servers.
Restart the
communications servers.
Page 31

Incorrect analogue • Analogue Input is not being • Refer to the actions for
values displayed on the read correctly by the I/O unit. ”Analogue values not
HMI. changing in the source
I/O unit – verified using
eXplore”. Page 88.

“Analogue values are
not correct when viewed
on the source XCell
processor module -
verified using eXplore-
etc ”. Page 90.
• I/O cannot be seen by the • Refer to the actions for

XCell communications “XCell processor module
interface unit. cannot be seen by
another XCell processor
module“. Page 103.
• I/O not transferred by the XCell • Refer to the actions for

protocol interface module. “I/O not transferred by
the XCell protocol
interface unit”. Page 74.
• Communications problem. • Refer to the actions for

“Communications alarm
is reported on the alarm
log”. Page 27.
A single point is • The associated XCell • Refer to the actions for

reported as a red box processor module is powered “XCell processor module
with three question OFF or has failed. failure is reported in the
marks ??? on the Alarm Log”. Page 40.
Vision HMI screen.
Page 32
Troubleshooting
Manual Version 1.06

• The associated XCell I/O • Refer to the actions for
module is removed or failed. “XCell I/O module failure
is reported in the Alarm
Log”. Page 41.
• Incorrect mapping in the XCell • Ensure that the correct

interface processor module. points are mapped to the
correct protocol
addresses. Download the
protocol map to the XCell
interface processor
module.
• Configuration not downloaded • Download the protocol

to the XCell interface processor mapping configuration to
module. the XCell interface
processor module.
• Other causes. • Refer to the actions for

“Vision displays one or
more points as a red box
with three question
marks ???”. Page 33.
Vision displays one or • The appearance of a red box • Check the Alarm Log for
more points as a red with three question marks ??? any recent alarms that
box with three question indicates that the data is might identify the problem.
marks ???. unavailable to Vision.
• Check Vision diagnostic
screens to identify any
faulty modules, units or
communications links.
• PC-XCell communications link • Refer to the actions for

failure. “Communications alarm
Log”. Page 27.
Page 33

• PC communications server • Refer to the actions for
Log”. Page 27.
• PC LAN fault. • Refer to the actions for

“PC LAN fault”. Page 35.
• The associated XCell • Refer to the actions for

processor module is powered “XCell processor
OFF or failed. module failure is
reported in the Alarm
Log”. Page 41.

Log”. Page 40.

correct protocol
interface processor
module.

processor module.
Page 34
Troubleshooting
Manual Version 1.06

• Vision communications server • Verify other points are
is halted. operational through the
same communications
server. If not shutdown the
operator workstation with
the communications
server and restart it again.
• Vision application is halted. • If none of the operator

facilities are functional
then shutdown the
operator workstation and
restart it again.
• XCell FieldNet LAN is faulty. • Refer to the “XCell

FieldNet LAN Fault
Finding Guide section of
this manual (page 99) and
PC LAN fault • LAN interconnecting network • Ensure that all LAN

cables are not connected or cables are correct and
incorrectly connected securely connected to the
proper interface points.
• 10Base2 LAN is not • Ensure that any 10Base2

terminated at both ends. cable is correctly
terminated at both ends of
the network.
Page 35

Each point is displayed • The appearance of a red box • Check the Alarm Log for
on the Vision HMI with three question marks ??? any recent alarms that
screen as a red box indicates that the data is might identify the problem.
with three question unavailable to Vision.
marks ???. • Check Vision diagnostic
screens to identify any
faulty modules, units or
communications links.

Log”. Page 27.

Log”. Page 27.

“PC LAN Faulty”. Page
35.

Fault”. Page 101.
Page 36
Troubleshooting
Manual Version 1.06

correct protocol
interface processor
module.

processor module.
Multiple I/O Bad alarms • The associated XCell • Refer to the actions for
reported in the Alarm processor module is powered “XCell processor
Log. OFF or failed. module failure is
reported in the Alarm
Log”. Page 41.
Log”. Page 40.

Fault”. Page 101.
• PC-XCell FieldNet LAN • Refer to the actions for

configuration problem. “XCell FieldNet LAN
Fault”. Page 101.
Page 37

• Other cases. • Refer to the actions for
“Vision displays one or
more points as red with
three question marks
??? ”. Page 33.
Unable to drive an XCell • Interlocking conditions prevent • Ensure that the plant
output from Vision. the command from being sent conditions are suitable for
to the XCell system. driving the required output.
• XCell system fault. • Refer to the actions for

“Unable to drive a Digital
Output through a
protocol interface”. Page
84.
• The XCell processor module • Check the modules OLU

hosting the protocol is faulty or
powered OFF. • Check for front panel
messages on the relevant
XCell processor module.
Refer to Appendix One
“Front Panel Diagnostic
Messages” (page 132) for
• The XCell processor module • Check the modules OLU

controlling the Digital Output
modules is faulty or powered • Check for front panel
OFF. messages on the relevant
Page 38
Troubleshooting
Manual Version 1.06

• Digital Output module is faulty • Check XCell processor
or powered OFF. module to which the
Digital Outputs are
connected. Use the SHC
front panel menu item.
• Check for front panel

messages on the relevant
• There is nothing connected to • Check for front panel

the Digital Output module. messages on the relevant
• Digital Output module is not • Check for power to the

being powered correctly. Digital Output module;
replace if faulty.
Log”. Page 27.

Log”. Page 27.
Page 39

“PC LAN Faulty”. Page
35.
XCell I/O module failure • I/O module has been removed. • Replace the module and
is reported in the Alarm verify that it is no longer
Log. reported as failed.
• Mismatch between the I/O • Either replace the module

module type inserted and that if incorrect or save the
saved in the XCell processor correct configuration using
module configuration. the front panel function
button. Refer to the XCell
User Manual for further
information.
• Check that the module

occupies the correct slot
position.
• Check the onboard

jumpers on the module.
• I/O module is not secured • Re-insert the module

properly in the rack and is not correctly and secure
making proper electrical properly.
contact with the backplane.
• Faulty XCell unit. • Replace the unit and test

again.
• Fault on the associated XCell • Verify the XCell processor

processor module. with a replacement
module.
Page 40
Troubleshooting
Manual Version 1.06

• Fault on the particular XCell • Verify the backplane with
backplane. a replacement module.
XCell processor module • XCell processor module is • Switch on the unit using
failure is reported in the powered OFF or removed. the switch on the front of
Alarm Log. the XCell processor
module.
• Power is lost to the XCell • Refer to the actions for

processor module or rack. “No power to any XCell
processor module in a
rack”. Page 48.

“No power to a single
XCell processor module
in a rack”. Page 49.
• XCell processor module is not • Re-insert the module

secured properly in the rack correctly and secure
and is not making proper properly.
electrical contact with the
backplane.
• XCell processor module is • Replace the XCell

failed. processor module and
verify that the unit is no
longer reported as failed.
• XCell processor module is • Refer to the actions for

constantly rebooting. “XCell processor module
rebooting continuously
”. Page 54.
Page 41

Fault Finding Guide”.
See Page 99
Vision system reports • Spurious field events can give • Check the plant device.
fleeting alarms. rise to alarms at the operator
Workstation. • Ensure that the XCell
processor modules
interfacing with the field
are configured properly.
• Ensure that the

communications port
address of the device is
known and correct.
• Intermittent wiring connection. • Check that the field wiring

connections are fully
secured and that the
wiring is intact.
XCell processor module • XCell processor module is • Refer to the actions for
is repeatedly reported constantly rebooting. “XCell processor module
OK and then Failed. rebooting continuously”.
Page 54.
• XCell FieldNet LAN fault. • Refer to the actions for
fault”. Page 101.

correct protocol
interface processor
module.
Page 42
Troubleshooting
Manual Version 1.06

processor module.
Data points are toggling • XCell processor module is • Refer to the actions for
between good values constantly rebooting. “XCell processor module
and values that are rebooting continuously”.
clearly in error i.e. Page 54.
points toggle between
normal Vision colours
and red with three
question marks ???.
• XCell LAN fault. • Refer to the actions for
fault”. Page 101.

correct protocol
interface processor
module.

processor module.
Problem logging on to • Password typed incorrectly. • Retype the password.

Vision, password Ensure any case specific
rejected as invalid. information is included.
Password is known to • Password may have been • Contact your system

be correct however, changed. administrator.
access is denied.
Page 43

Unable to access • The supplied password may • Ensure that the correct
certain aspects of the not permit access to the level password is used for the
Vision system. required. level of security required.
• Contact your system

administrator.
• The user may have been • Automatic log-off occurs

logged off by the system. at certain security levels
following a time-out
period. Log-on again.
• Contact your system

administrator.
Page 44
Troubleshooting
Manual Version 1.06

This section deals with troubleshooting XCell hardware during
installation and start-up. The following list of points contains general
safeguards and precautions which should be observed when
installing or rebooting XCell processor and I/O modules. Further
information may be found in the XCell User Manual.
• Electrostatic precautions should be followed when

handling XCell hardware.
• Power must be disconnected from the unit (front

panel power switch) when removing or installing any
module (including the XCell Processor module
itself). The swapping of cards with power ON can
cause damage and invalidates any warranty.
• Always use the SHC front panel option or eXplore

to check for the correct hardware, refer to the XCell
User Manual.
• Connecting the wrong field connector to the wrong

I/O module can damage the I/O module and
invalidate any warranty.
• When changing modules always ensure that the

appropriate connectors are inserted into the correct
I/O module.
• Do not plug power leads into the network

connection.
• For correct operation boards should be secured in

racks with screws provided.
• Ensure correct polarity of the DC power supply.
Page 45
• When replacing modules always ensure that

jumper positions are correct, refer to the XCell
User Manual.
• Check network termination resistors are properly

installed, refer to the XCell User Manual.
• It is important to ensure that the XCell processor

module cycles through the correct boot-up
sequence
1. Power, Active, fail and Online LEDs

light. The I/O matrix LEDs are scanned
four times. The message display
indicates 888
2. Active, Fail and Online LEDs turn off

and the message display will cycle
through the 10,20,…100, Bra,….210,
RCL….340 sequence
3. I/O LED matrix scans vertically four

times.
4. Message display indicates the XCell

processor module unit number. Power
LED is steady ON. Active LED is
flashing. If the module forms part of a
network the Online LED is steady ON.
(See the XCell User Manual for more
detailed information).
Page 46
Troubleshooting
Manual Version 1.06
• It is sometimes necessary to clear all stored

configurations from an XCell processor module, this
can be done by holding the front panel function
button pressed, immediately following power-on of
the unit, until “bra” appears on the front panel
display. (base 404 or later)
• Ensure the correct communications ports are used

on both the PC and the XCell processor module.
Page 47

No power on any • XCell processor modules are • Ensure that the associated
XCell processor powered OFF. XCell processor modules are
module in a rack. switched ON using the front
Power LEDs are not panel power switch.
illuminated.
• Faulty module or backplane • Remove all modules and
check the backplane supply
voltage to determine if the
problem is caused by faulty
modules or a faulty backplane.
• If the backplane supply is OK,

re-insert modules individually
to identify any faulty modules.
• No power to the XCell rack. • Verify power to the rack using

a DC voltmeter.
• DC power cable is • Ensure the dc power

disconnected from the rack. connection is correctly
installed.
• DC power is connected to the • Ensure that the DC power is

wrong backplane connections. connected to the correct
terminals on the XCell
backplane.
• Polarity of the dc power supply • Ensure that the dc power is

is incorrect. connected to the rack with the
correct polarity.
Page 48
Troubleshooting
Manual Version 1.06

• Power source is under rated for • Ensure that the power source
the connected load. is correctly sized for the load it
is driving.
• Power source is producing the • Verify the power source is

wrong output voltage. producing the correct output
voltage.
• XCell processor modules are • Re-insert the modules

not secured properly in the correctly and secure them
rack and are not making proper properly.
backplane.
• There may be a conflict • Ensure dual power sources are

between dual power supplies. connected correctly. (See the
XCell User Manual for further
information).
No power to a single • The XCell I/O unit is powered • Ensure that the XCell I/O unit
XCell processor OFF. is switched ON using the front
module in a rack. panel power switch.
Power LED is not
illuminated.
• XCell processor module is not • Re-insert the module correctly
secured properly in the rack and secure properly
and is not making proper
backplane.
• XCell processor module is • Replace the XCell processor

faulty. module and verify that the
power LED is illuminated in the
new unit.
Page 49

• The XCell processor module is • Ensure that the back of the
shorting off a neighbouring processor module is not
module. shorting against the
neighbouring metalwork.
• The XCell I/O module is faulty. • Remove all I/O modules

associated with the unit
(following the recommended
power OFF procedure) to
identify if the problem is the
result of a faulty I/O module.
• If the processor module is now

operating then replace each of
the I/O modules individually to
identify the faulty module.
• The power source is producing • Verify that the power source is

the wrong output voltage producing the correct output
voltage.
• The power source is under • Ensure that the power source

rated for the connected load. is correctly sized for the load
that it is driving.
XCell processor • Memory is held in some • Clear memory by temporarily

module does not intermediate state. moving the appropriate link on
cycle through its boot the processor module or using
up sequence. the front panel function button
at start-up, (refer to the XCell
User Manual for details).
• The RAM Clear link on the • Ensure that the RAM Clear
processor module is set to the link on the XCell processor
wrong position module is not set to the Clear
position.
Page 50
Troubleshooting
Manual Version 1.06

• Expansion memory is required • Ensure that the memory
but not fitted. expansion module is installed
where required and that it is
populated with the required
compliment of memory chips.
• XCell I/O module is faulty. • Remove all I/O modules

associated with the unit
identify if the problem arises
from a faulty I/O module.
• If the XCell processor module

is now operating then replace
each of the I/O modules
individually to identify the faulty
module.
• Memory is not installed / • Ensure that all memory is

inserted correctly. installed / inserted correctly
with no pins bent on the
memory devices.
• Memory links incorrectly set. • Ensure that the memory links

on the processor module are
correctly set for the installed
memory.
• Protocol firmware not installed • Ensure that any additional

correctly. firmware (e.g. appropriate
protocol and eXpress support,
etc.) is correctly installed with
the chips in the correct
sockets.
Page 51

• Some necessary hardware is • Ensure that all the necessary
not present in the unit. hardware is installed for the
application software, e.g.
Ethernet module.
• Other causes. • The last number displayed on

the 7-segment display during
the boot-up sequence should
assist in the identification of
the problem. Refer to the
appendix on “Front Panel
Diagnostic Messages” (page
132) during the boot cycle for
further assistance.
XCell processor • Memory is held in some • Clear memory by temporarily

module does not intermediate state. moving the appropriate link on
cycle through its boot the processor module or using
up sequence the front panel function button
following a firmware at start-up, (refer to the XCell
upgrade. User Manual for details).
• The RAM Clear link on the • Ensure that the RAM Clear
processor module is set to the link on the processor module
wrong position. is not set to the Clear position.
• Expansion memory is required • Ensure that the memory

but not fitted. expansion module is installed
where required and that it is
populated with the required
compliment of memory.
• There are no software chips • Ensure that labelled firmware

installed on the XCell chips are installed on the XCell
processor module board. processor module.
Page 52
Troubleshooting
Manual Version 1.06

• The software chips are • Ensure that the software chips
installed incorrectly or in the are installed in the correct
wrong positions on the XCell sockets on the XCell
processor module board. processor module circuit board
and that the orientation of the
chips is correct.
• There are no RAM chips • Ensure that RAM chips are
installed on the XCell installed on the XCell
processor module board. processor module circuit
board.
• The RAM chips are installed • Ensure that the RAM chips are
incorrectly or in the wrong installed in the correct sockets
positions on the XCell on the XCell processor module
processor module board. circuit board and that the
orientation of the chips is
correct.
• Onboard jumper settings are • Ensure that all relevant

wrong for the size of EPROM EPROM jumpers are in the
used. correct positions. (Refer to the
XCell User Manual for more
information).
• Onboard jumper settings are • Ensure that all relevant RAM

wrong for the size of RAM chip jumpers are in the correct
used. positions. (Refer to the XCell
details).
• Some pins from the RAM or • Ensure that all the RAM and
EPROM chips are bent and not EPROM pins are correctly
inserted properly in their inserted into their respective
sockets. sockets.
Page 53

• The wrong version of firmware • Ensure that the correct version
is installed on the XCell of firmware is installed on the
processor module circuit processor module.
board.
• Ensure that the EPROMs have
been programmed correctly
with the correct version of
software.
• Verify the EPROMs against

the master software.
• One or more XCell I/O modules • Remove all I/O modules

are faulty. associated with the unit
identify if the problem is
caused by a faulty I/O module.
• If the processor module is now

operating replace each I/O
module individually to identify
the faulty unit.
XCell processor • Another XCell processor • Ensure that no two XCell

module rebooting module on the network has the processor modules have the
continuously. same unit number. same unit number on the XCell
network.
• XCell processor module not • Refer to the actions listed for

initialising properly. “XCell processor does not
cycle through its boot up
sequence”. Page 50.
Page 54
Troubleshooting
Manual Version 1.06

• eXpress logic sequence is • Ensure that the eXpress cycle
overloading the XCell processor time allows sufficient time for
module. the eXpress sequence and all
other XCell processing
activities. No eXpress logic
sequence should have a cycle
time of zero.
• Memory expansion not fitted • Ensure that memory

where necessary. expansion is fitted where
required.
• Excessive data changes on a • Verify the network traffic using

continuous basis may result in a network event logger (part of
the depletion of XCell eXplore) and identify any
resources and cause the units frequently changing inputs.
to stop or be rebooted by their
watchdogs.
• Disconnect any frequently
changing inputs.
• The power source used is • Ensure that the power supply

under-rated for the connected used is capable of supplying
load. the needs of the system.
• XCell network Fault • Refer to the actions listed for

“XCell FieldNet LAN Fault”.
Page 101.
• Insufficient memory in XCell • If the system is large and has

processor modules to handle frequently changing inputs
continuous network traffic. then the system firmware
should be upgraded for a large
system and additional RAM
fitted to the units.
Page 55

XCell processor • eXpress application problem. • Refer to the actions for
module rebooting “eXpress unit is continuously
while running an rebooting”. Page 118.
eXpress logic
sequences.
Non-volatile memory • Memory links not configured • Ensure that the jumpers are
fault. properly for non-volatile set correctly on the XCell
retention. processor module to ensure
that the memory is retained
during power OFF.
• Battery not charged initially to • Leave the XCell processor

retain the memory during module powered ON for at
power OFF. least 72 hours to charge the
battery and check its retention
during power OFF again.
• Powered OFF for a period • Ensure that the XCell

greater than the memory processor module was not left
retention period. powered OFF for a period
greater than the memory
retention period.
• Fault on the XCell processor • Replace the XCell processor

module. module with a different XCell
processor module known to be
working and verify its correct
operation.
• Memory cleared manually. • Ensure that the memory has

not been manually cleared,
either using the RAM Clear
link on the XCell processor
module or using the Front
Panel memory clear option
during power-ON.
Page 56
Troubleshooting
Manual Version 1.06

Online unit status • Some XCell processor module • Check the system for any unit
changing at random is rebooting and constantly rebooting and power it OFF in
(as observed on the causing the others to swap to an attempt to isolate the fault.
front panel FSD try to recover it. Once the system is stable
display). again refer to the actions for
“XCell processor module
rebooting continuously”
(page 54) to resolve the
problem.
• XCell network Fault. • Refer to the actions listed for

“XCell FieldNet LAN Fault”.
Page 101.
Online LED is not • XCell processor module not • Refer to the actions for “XCell
illuminated on the booting properly. processor module does not
front panel of the cycle through its boot-up
XCell Processor sequence”. Page 50.
module.
• Front panel online LED faulty. • Verify the LED during the XCell
processor module boot up
sequence when all front panel
LEDs are exercised.
• XCell FieldNet network fault. • Refer to the actions for “XCell

FieldNet LAN fault”. Page
101.
Page 57
Page 58
Troubleshooting Manual
Version 1.06

This section deals with troubleshooting XCell Accumulators during
installation and start-up. The following list of points contains general
safeguards and precautions which should be observed when
installing or rebooting XCell Accumulator HSC (High Speed
Counter) or Digital Input (DI) modules. Further information may be
found in the XCell User Manual.

handling XCell High Speed Counter (HSC)
modules or Digital Input (DI) modules.

panel power switch) when removing or installing
any module (including the XCell Processor module

to check for the correct hardware, refer to the
XCell User Manual.


appropriate connectors are inserted into the
correct I/O module.
• For correct operation all modules should be

secured in racks with screws provided.

jumper positions are correct, refer to the XCell
User Manual.
Page 59

High Speed Counter • XCell I/O is powered OFF. • Ensure that the XCell I/O unit
(HSC) module not is powered ON using the front
being scanned on the panel power switch.
Front Panel LED
matrix.
• The LED matrix is displaying • Ensure that the LED matrix is
the wrong I/O channels. set-up to display the relevant
I/O indications.
• Faulty LED or LED matrix. • Verify the I/O status using

eXplore diagnostic Tool. If it
displays the inputs correctly
then the LED / LED matrix is
faulty.
• HSC Input module is not • Ensure that the HSC Input

installed. module is correctly installed.
• HSC Input module is not • Ensure that all I/O modules

seen by the XCell processor are installed and visible using
module. the SHC menu option on the
XCell front panel.
• Ensure that the hardware

configuration is saved using
the front panel SHC option.
• Ensure that the links are

correctly set on all I/O
modules adjacent to the XCell
processor module.
Page 60
Version 1.06

• HSC Input module faulty. • Disconnect the module from
the plant by removing the
connectors at the front of the
module. Simulate HSC inputs
using an I/O simulator and
verify the operation of the
module. Replace the HSC
Input module with a new
module (if possible) and verify
its correct operation.
• Unit is halted or in the • Ensure that the active LED is

process of rebooting. toggling. If not, refer to the
actions for “XCell processor
module(s) rebooting
continuously”. Page 54. Or
“XCell processor module
does not cycle through its
boot-up sequence”. Page
50.
• User codes displayed on the • Refer to the appendix on

7-segment display on the “Front Panel Diagnostic
XCell front panel. Messages” (page 132) for
further details.
Page 61

Accumulator values are • Field input is not correct. • Ensure that the correct field
not being produced by connector is connected to the
the source XCell I/O module.
processor module.
• Disconnect the module from
the plant by removing the
module. Simulate inputs
module. If the module is
operational then check the
field wiring and the input
voltage level.
• High Speed Counter modules • Refer to the actions for “High

not being scanned. Speed Counter (HSC)
module not being scanned
on the Front Panel LED
matrix”. Page 60.
• Fault on Digital Input • Refer to the actions for

channel(s) used for “Digital Input LED matrix
accumulators. not reflecting the plant
status”. Page 70.
• Incorrect configuration for the • Check the configuration

Accumulator point in the parameters for the processed
XCell processor module. point in the eXpert
configuration tool, particularly
the input type and channel
number. Download the
configuration to the XCell
processor module again and
once more, verify the
processed value using
eXplore.
Page 62
Version 1.06

• Configuration not downloaded • Download the configuration to
to the XCell I/O unit . the XCell I/O unit
Accumulator values not • High Speed Counter module • Refer to the actions for “High
available in another is not being scanned (if HSC Speed Counter (HSC)
XCell processor being used). module is not being
module. scanned on the front panel
LED matrix”. Page 60.
• Fault on Digital Input • Refer to the actions for

channel(s) used for “Digital Input LED matrix
accumulators. not reflecting the plant
status”. Page 70.
• Accumulator values not • Refer to the actions for

being produced by the “Accumulator values not
source XCell processor being produced by the
module. source XCell processor
module”. Page 62.
• I/O unit cannot be seen by • Refer to the actions for “XCell

the other XCell processor processor module cannot
module. be seen by another XCell
processor module”. Page
103.
Accumulator values are • Accumulator values are not • Refer to the actions for
not received through a being produced by the “Accumulator values not
communications source XCell processor being produced by the
interface. module. source XCell processor
module”. Page 62.
Page 63

• Accumulator values not • Refer to the actions for
available in the “Accumulator values not
communications XCell available in another XCell
processor module. processor module”. Page
63.
• I/O not transferred by the • Refer to the actions for “I/O

XCell protocol interface . not transferred by the XCell
protocol interface unit”.
Page 74.
Page 64
Troubleshooting
Manual Version 1.06

This section deals with troubleshooting the XCell AC Analogue Input
module. The following list of points contains general safeguards and
precautions which should be observed when working with XCell AC
Analogue Input modules. Further information may be found in the
XCell User Manual and in the eXpert Manual


module (including the XCell Processor module
• Always use the SHC front panel option or eXplore to

check for the correct hardware, refer to the XCell
User Manual.


I/O module.
• For correct operation all modules should be secured

in racks with screws provided.
• When replacing modules always ensure that jumper

positions are correct, refer to the XCell User
Manual.
Page 65
• If ACI modules are installed, the sixteenth LED of

column A,B,C or D will flash (depending on which
slot contains the card). If ACI modules are installed
and no LEDs light then check the configuration
using the SHC front panel menu item.
• For ACI-021 no more than one frequency

measurement should be configured in the eXpert
tables.
• For ACI-022 only a single frequency should be

configured.
• For a fully configured ACI-022 module the following

measurement limitations apply, eight RMS
measurements, one frequency measurement, all
measurements for two 3-phase feeders and two
single phase feeders.
Page 66
Troubleshooting
Manual Version 1.06

ACI front panel LED • LED matrix displaying the • Ensure that the LED matrix is
matrix does not wrong I/O channels. set-up to display the relevant
produce the expected I/O indications.
display.
• Faulty LED / LED matrix. • Use OLU display or alternate

LED group to test the
operation of the LED matrix.
• ACI module is not installed. • Ensure that the ACI module is

correctly installed.
• ACI module is not seen by the • Ensure that all I/O modules
XCell processor module. are installed and visible using
the SHC menu option on the
front panel of the XCell
processor module.

the front panel SHC menu
option.

modules and the XCell
processor module.
Page 67

• ACI module faulty. • Disconnect the module from
plant by removing the
module. Simulate ac inputs
module. Replace the ACI
module with a new module and
verify its correct operation.
• User codes displayed on the 7- • Refer to the section on Front

segment display on the XCell Panel Diagnostic messages
front panel. (page 132) for further details.
Inaccurate AC • ACI module not calibrated. • Ensure that the ACI module
measurements has been calibrated with the
matching CTs and VTs.
• CTs and VTs not matched to • Ensure that the ACI module
the ACI module. has been calibrated with the
matching CTs and VTs.
• RMS phase measurement not • Frequency channel zero and

configured for frequency RMS phase measurement
channel zero. A valid RMS should be configured for a VT
value must be present before a input if possible.
frequency measurement will
run.
• Exceeding the computational • Do not exceed the

load on the ACI module computational specifications
processor. for the ACI module being used.
Adjust the configuration tables
and re-download the
configuration. See the eXpert
Manual for further details.
Page 68
Troubleshooting
Manual Version 1.06

This section deals with troubleshooting XCell Digital Input modules.
The following list of points contains general safeguards and
precautions which should be observed when working with XCell Digital
Input modules. Further information may be found in the XCell User
Manual.
• Note that Double Digital Inputs (DDIs) require two

consecutive channels on a Digital Input module
• Ensure that Digital Input wiring is not connected to

Analogue Input modules.


module (including the XCell Processor module itself).
The swapping of cards with power ON can cause
damage and invalidates any warranty.

User Manual.
• Connecting the wrong field connector to the wrong I/O

module can damage the I/O module and invalidate
any warranty.

I/O module.

Page 69

positions are correct, refer to the XCell User Manual.
Digital Input LED • XCell I/O unit is powered OFF. • Ensure that the XCell I/O unit is
matrix not reflecting switched ON using the front
the plant status. panel power switch.
• LED matrix displaying the • Ensure that the LED matrix is
wrong I/O channels. set-up to display the relevant I/O
indications.
• Faulty LED or LED matrix. • Verify the I/O status using

eXplore diagnostic Tool. If it
displays the inputs correctly
then the LED or LED matrix is
faulty.
• Digital Input module is not • Ensure that the Digital Input

installed. module is correctly installed and
module jumpers are set for the
correct slot position.
• Digital Input module is not • Ensure that all I/O modules are
seen by the XCell processor installed and visible using the
module. SHC menu option on the XCell
processor module front panel.

configuration is saved using the
front panel SHC option.

correctly set on all I/O modules
in the XCell processor module.
Page 70
Troubleshooting
Manual Version 1.06

• Field input is not correct. • Ensure that the correct field
connector is connected to the
I/O module.
• Disconnect the module from the

plant by removing the
module. Simulate Digital Inputs
using an I/O simulator and verify
the operation of the module. If
the module is operational then
check the field wiring and the
input voltage level.
• Digital Input module faulty. • Replace the Digital Input module

with a new module and verify its
correct operation.
• User codes displayed on the 7 • Refer to the appendix on Front

–segment display on the XCell Panel Diagnostic messages
front panel. (page 132) for further details.
XCell Processed • Raw digital point may not be • Using eXplore check the
Digital Input (SDI, functional. operation of the Raw Digital
DDI etc) is not points. If these are not
functioning in the operational refer to the actions
XCell processor for “Digital Input LED matrix
module. not reflecting the plant status“ .
Page 70.
Page 71

• Incorrect configuration for the • Check the configuration
processed point in the XCell parameters for the processed
processor module. point with the eXpert
configuration tool.
• Ensure that the configuration

has been compiled prior to
downloading.
• Re-download the configuration to

the XCell processor module and
again verify the processed value
using eXplore.
• Configuration not downloaded • Download the configuration to

to the XCell I/O processor the XCell I/O processor module.
module.
XCell Raw Digital • XCell unit is powered OFF. • Ensure that both XCell units are
Input is not available switched ON using the front
in another XCell panel power switch.
processor module.
• Fault on the XCell I/O unit. . • Refer to the actions for “Digital
Input LED matrix is not
reflecting the plant status” .
Page 70.

another XCell processor processor module cannot be
module. seen by another XCell
processor module”. Page 103.
XCell Processed • XCell processor module is • Ensure that both XCell processor
Digital Input value powered OFF. modules are switched ON using
(SDI, DDI etc) is not the front panel power switch.
available in another
XCell processor
module.
Page 72
Troubleshooting
Manual Version 1.06

• Fault on the XCell I/O unit. . • Refer to the actions for “XCell
Processed Digital Input (SDI,
DDI etc) is not functioning in
the XCell processor module”.
Page 71.

another XCell processor processor module cannot be
Processed Digital • XCell processed Digital Input • Refer to the actions for “XCell
Input value (SDI, DDI (SDI, DDI etc) is not processed Digital Input (SDI,
etc) not received functioning in the XCell DDI etc) is not functioning in
across a protocol processor module. the XCell processor module”.
interface. Page 71.
• XCell Processed Digital Input • Refer to the actions for “XCell

value (SDI, DDI etc) is not Processed Digital Input value
available in another XCell (SDI, DDI etc) is not available
processor module. in another XCell processor
module”. Page 72.
• I/O not transferred by the XCell • Refer to the actions for “I/O not
protocol Interface unit. transferred by the XCell
protocol Interface unit”. Page
74.
Raw Digital Input not • Digital Input is not read • Refer to the actions for “Digital
received across a correctly by the I/O processor Input LED matrix not reflecting
protocol interface. module. the plant status”. Page 70.
• I/O unit cannot be seen by the • Refer to the actions for “XCell
protocol XCell processor processor module cannot be
Page 73

• The protocol being employed • Ensure the installed protocol
does not support raw Digital supports raw Digital Inputs.
Inputs.
protocol interface unit. . transferred by the XCell
protocol interface unit”. Page
74.
I/O not transferred by • The protocol interface XCell • Ensure that the protocol
the XCell protocol processor module is powered interface unit is switched ON
interface unit. OFF or failed. using the front panel power
switch.
• Incorrect mapping in the XCell • Ensure that the correct points

interface processor module. are mapped to the correct
protocol addresses. Download
the protocol map to the XCell
interface processor module.
• Configuration not downloaded • Download the protocol mapping

to the XCell interface processor configuration to the XCell
module. interface processor module.
• Fault on the communications • Replace the processor module

XCell processor module. with a new module (if possible)
and verify its correct operation.
• Cable fault between the XCell • Ensure the cable is wired

protocol interface module and correctly according to the
its communication partner. requirements and that the cable
is not damaged.
• Ensure that the cable is

correctly secured at both ends.
Page 74
Analogue Output Fault Finding Guide
Troubleshooting
Manual Version 1.06

This section deals with troubleshooting XCell Analogue Output
module. The following list of points contains general safeguards and
precautions, which should be observed when working with XCell
Analogue Output modules. Further information may be found in the
XCell User Manual.


panel power switch) when removing or installing
any module (including the XCell Processor module

to check for the correct hardware, refer to the
XCell User Manual.


appropriate connectors are inserted into the
correct I/O module.
• For correct operation all modules should be

secured in racks with screws provided.

jumper positions are correct; refer to the XCell
User Manual.
Page 75
• Analogue Output modules cannot be configured

directly using eXpert. They can only be configured
as raw point types.
• Analogue Output channel numbers start at zero in

slot one (next to the XCell processor module) and
increment sequentially to a maximum of 127
channels over the four slots.
Page 76
Troubleshooting
Manual Version 1.06

Unable to drive an • XCell processor module is • Ensure that the XCell
Analogue Output powered OFF. processor module is switched
from eXplore on the ON using the front panel power
local XCell processor switch.
module.
• Analogue Output module is not • Ensure that the Analogue
installed. Output module is correctly
installed.
• Analogue Output module is not • Ensure that all I/O modules

seen by the XCell processor are installed and visible using
module. the SHC menu option on the
XCell front panel.

the front panel SHC menu
option.

modules on the XCell
processor module.
Page 77

• Incorrect Analogue Output • Ensure that the channel
channel number is being used. number being used in a
configuration table allows for
the number of channels on
each I/O module. Channel
numbers increment
sequentially starting at zero in
the slot adjacent to the
processor module, e.g. a
sixteen-channel module will
have channel numbers 0-15 if
it is located in slot one. See
the XCell User Manual for
further details.
• Analogue Output module • Replace the Analogue Output

faulty. module with a new module and
verify its correct operation.
• User codes displayed on the 7- • Refer to the appendix on

segment display on the XCell “Front Panel Diagnostic
front panel. Messages“ (page 132) for
further details.
Unable to drive an • Local XCell processor module • Ensure that the local XCell
Analogue Output is powered OFF. processor module is switched
from eXplore on ON using the front panel power
another XCell unit. switch.
• Fault on the XCell output unit. . • Refer to the actions for

“Unable to drive an
Analogue Output from
eXplore on the local XCell
Page 78
Troubleshooting
Manual Version 1.06

eXplore interface unit. processor module cannot be
seen by another XCell
processor module”. Page
103.
Unable to drive an • Fault on the XCell system. • Check if the output can be
Analogue Output driven from eXplore on the
through a protocol protocol interface module and
interface module. if not then refer to the actions
for “Unable to drive an
Analogue Output from
eXplore on another XCell
unit”. Page Error! Bookmark
not defined..
• Command not transferred by • Refer to the actions for “I/O

the XCell protocol interface unit not transferred by the XCell
. protocol interface unit”.
Page 74.
Page 79
Page 80
Digital Output Fault Finding Guide
Troubleshooting
Manual Version 1.06

This section deals with troubleshooting a XCell Digital Output module.
The following points contain general safeguards and precautions which
should be observed when working with XCell Digital Output modules.
Further information may be found in the XCell User Manual.

• Power must be disconnected from the unit (front panel

power switch) when removing or installing any module
(including the XCell Processor module itself). The
swapping of cards with power ON can cause damage
and invalidates any warranty.

check for the correct hardware, refer to the XCell User
Manual.

module can damage the I/O module and invalidate any
warranty.

appropriate connectors are inserted into the correct I/O
module.

• Digital Output channel numbers start at zero in slot

one (next to the XCell processor module and
increment sequentially to a maximum of 127 channels
over the four slots
Page 81

Unable to drive a • XCell processor module is • Ensure that the XCell processor
Digital Output from powered OFF. module is switched ON using the
eXplore on the local front panel power switch.
XCell unit.
• Digital Output module is not • Ensure that the Digital Output

installed. module is correctly installed.
• Digital Output module is not • Ensure that all I/O modules are
seen by the XCell processor installed and vi sible using the
module. SHC menu option on the XCell
processor module front panel.

front panel SHC option.
• Ensure that the links are correctly

set on all I/O modules and on the
• Incorrect Digital Output • Ensure that the channel number

channel number is being used. being used allows for the number
of channels on each of the I/O
modules. Channel numbers
increment sequentially starting at
zero in the slot adjacent to the
processor module. e.g.: a thirty-
two channel module will have
channel numbers 0-31 if it is
located in slot one. See the XCell
User Manual for further details.
.
Page 82
Troubleshooting
Manual Version 1.06

• No power connected to the • Ensure that power is connected
Digital Output module. to the front of any High Density
Digital Output modules. Refer to
the XCell User Manual for further
information.
• Incorrect parameterisation for • Check the configuration

the Digital Outputs on the XCell parameters for the Digital
processor module. Outputs. Compile and re-
download the configuration to the
output unit. Refer to the XCell
User Manual and the eXpert
information.
• Digital Output parameters may • Download the Digital Output

not have been downloaded to parameters to the XCell processor
the XCell processor module. module. Refer to the eXpert User
Manual for further information.
• Digital Output module faulty. • Replace the Digital Output

module with a new (if possible)
module and verify its correct
operation.
• User codes displayed on the 7- • Refer to the appendix on “Front

segment display of the XCell Panel Diagnostic Messages”
processor module front panel. (page 132) for further details.
Unable to drive a • Local XCell processor module • Ensure that the local XCell
Digital Output from is powered OFF. processor module is switched ON
eXplore connected to using the front panel power
another XCell switch.
processor module.
Page 83

• Fault on the XCell output unit. • Refer to the actions for “Unable
to drive a Digital Output from
eXplore on the local XCell
unit”. Page 82.
XCell processor module to processor module cannot be
which eXplore is connected. seen by another XCell
Unable to drive a • Fault on the XCell system. • Check if the output can be driven
Digital Output from eXplore on the protocol
through a protocol interface unit and if not then refer
interface to the actions for “Unable to
drive a Digital Output from
eXplore connected to another
XCell processor module”. Page
83.
protocol interface module. transferred by the XCell
protocol interface module”.
Page 74.
Multiple control • Jumper on Digital Output card • Ensure that the jumper is set for
outputs cannot be for 2-up inhibit is incorrectly 2-up inhibit if only one output at a
driven on the same set. time is required on the Digital
XCell processor Output module. If jumper
module. positions are changed on I/O
boards the configuration must be
saved using the SHC option on
the front panel menu.
Page 84
Analogue Input Fault Finding Guide
Troubleshooting
Manual Version 1.06

This section deals with troubleshooting XCell Analogue Input module.
The following list of points contains general safeguards and precautions
to be followed when working with XCell Analogue Input modules. Further
information may be found in the XCell User Manual.

• Power must be disconnected from the unit (front panel

power switch) when removing or installing any module
(including the XCell Processor module itself). The
swapping of cards with power ON can cause damage
and invalidates any warranty.

check for the correct hardware, refer to the XCell User
Manual.

module can damage the I/O module and invalidate any
warranty.

appropriate connectors are inserted into the correct I/O
module.
• For correct operation all modules should be secured in

racks with screws provided.

• For Analogue Inputs, configuration options are available

from the XCell processor module front panel as well as
from eXpert. Delta Scaling and Over-Range can be set
from the function button. However, it is preferable to
leave Delta and Scaling as defaults and use eXpert to
Page 85
configure them as required. The eXpert configuration will

override any Delta or Scaling values set from the front
panel.
• When configuring the Delta value in eXpert be aware

that the Delta value displayed is % multiplied by 100
e.g. a value of 800 in the Delta column converts to a
Delta value of 8%
• In using Analogue Input modules it is important to note

that eXpress uses raw counts while the HMI employs
scaled values, there may be a difference between raw
and scaled values depending on the protocol used.
Page 86
Troubleshooting
Manual Version 1.06

Analogue Input not • XCell I/O processor module is • Ensure that the XCell I/O processor
scanning on the front powered OFF. module is switched ON using the
panel LED matrix. front panel power switch.
• LED matrix displaying the • Ensure that the LED matrix is set-
wrong I/O channels. up to display the relevant I/O
indications. (Refer to the XCell User
• Faulty LED matrix element or • Verify the I/O status using the
LED matrix. eXplore diagnostic tool. If it displays
the inputs correctly then the LED /
LED matrix is faulty. Refer to the
XCell User Manual and the
eXplore User Manual for further
information.
• Analogue Input module is not • Ensure that the Analogue Input

installed. module is correctly installed in the
rack. Refer to the XCell User
Page 87

• Analogue Input module is not • Ensure that all I/O modules are
seen by the XCell processor installed and visible using the SHC
module. menu option on the XCell front
panel.

front panel SHC menu option.
• Ensure that the links are correctly

set on all I/O modules and on the
XCell processor module. Refer to
the XCell User Manual for further
information.
• Analogue Input module faulty. • Replace the Analogue Input module

correct operation.
• User codes displayed on the 7- • Refer to the section on Front Panel

segment display on the XCell Diagnostic messages for further
processor module front panel. details.
Analogue Input • Module not scanning properly. • Refer to the actions for “Analogue
values not changing Input not scanning on the front
in the source I/O unit panel LED matrix”. Page 87.
– verified using
eXplore.
Page 88
Troubleshooting
Manual Version 1.06

• Field input is not correct. • Ensure that the correct field
connector is connected to the I/O
module.
• Disconnect the module from the

plant by removing the connectors at
the front of the module. Simulate
Analogue Inputs using an I/O
simulator and verify the operation of
the module. If the module is
operational then check the field
wiring and the input voltage level.
• Incorrect module range. • Ensure that the range of the

Analogue Input module is suitable
for the inputs.
• Incorrect analogue • Check the analogue configuration

configuration in the XCell parameters in the configuration tool
processor module. Refer to the eXpert User Manual

again verify the values using
eXplore.
• Configuration not downloaded • Download the configuration to the

to the XCell I/O unit. XCell I/O processor module.
• Incorrect over-ranges • Ensure the over-range value

configured on the analogue configured on the analogue XCell
XCell processor module. processor module (using the front
panel function button after start-up)
matches the hardware calibration on
the analogue module.
Page 89

• Delta value set too high. • Ensure that the reporting delta value
configured in the configuration tool
is not set so high as to prevent
current changes being reported.
Ensure that the configuration is
downloaded to the XCell I/O
processor module.
• If no channel configuration is
required then ensure that the delta
value set via the front panel after
start-up is not set so high as to
prevent current changes being
reported.
• User codes displayed on the • Refer to the appendix on “Front

seven-segment display on the Panel Diagnostic Messages” (page
XCell front panel. 132) for further details.
Analogue Input • Incorrect module range. • Ensure that the range of the
values are not correct Analogue Input module is suitable
when viewed within for the inputs.
the source XCell
processor module –
verified with eXplore
in the source XCell
processor module;
(Analogue Input
values should be
displayed as a
percentage of the
configured range).
Page 90
Troubleshooting
Manual Version 1.06

• Incorrect analogue • Check the analogue configuration
configuration in the XCell parameters in the configuration tool.
processor module.
again verify the values using
eXplore.
• Configuration not downloaded • Download the configuration to the

to the XCell I/O unit. XCell I/O processor module.
• Incorrect over-ranges • Ensure the over-range value

configured on the analogue configured on the analogue XCell
XCell processor module. processor module (using the front
panel function button after start-up)
matches the hardware calibration on
the Analogue Input module.
• Faulty plant measurement. • Verify voltage or current input from

the plant to the XCell terminals. If
necessary use an oscilloscope to
verify the stability of the inputs.
• Test the module using an accurate

input source.
• Analogue Input not reporting • Refer to the actions for “Analogue

value changes. Input values not received across
an XCell protocol interface”. Page
92.
• Faulty analogue module. • Replace the analogue module and

repeat the tests.
Page 91

• User codes displayed on the • Refer to the section on “Front
seven-segment display on the Panel Diagnostic Messages” (page
XCell processor module front 132) for further details.
panel.
Analogue Input • Analogue Input is not read • Refer to the actions for “Analogue
values not received correctly by the I/O processor Input not changing in the source
across an XCell module. I/O processor module – verified
protocol interface. using eXplore”. Page 88.
XCell protocol unit. processor module cannot be seen
by another XCell processor
module”. Page 104.
protocol interface unit. transferred by the XCell protocol
interface module”. Page 74.
Analogue Input • Analogue Input values are • Refer to the actions for “Analogue
values are not correct transmitted with incorrect Input values are not correct when
when viewed in values from the source XCell viewed within the source XCell
another XCell processor module. processor module - ”. Page 90.
processor module –
verified with eXplore.
• The unit is not communicating • Refer to the actions for “XCell
properly with the source XCell processor module cannot be seen
processor module. by another XCell processor
Page 92
Troubleshooting
Manual Version 1.06

This section deals with troubleshooting XCell serial communications.
The following list of points contains general safeguards and
precautions which should be observed when working with XCell serial
communications. Further information may be found in the XCell User
Manual:


module (including the XCell Processor module itself).
The swapping of cards with power ON can cause
damage and invalidates any warranty.

User Manual.

module can damage the I/O module and invalidate
any warranty.

I/O module.


Page 93
• Ensure that the correct port is selected on both the

PC and the XCell processor module for the type of
serial communications to be carried out.
• Use the XCell processor module port LEDs to assist in serial

communications diagnostics and fault finding.
Page 94
Troubleshooting
Manual Version 1.06

XCell serial • No Rx data. • Check the RXD LED for RX data.
communications not
working. • Ensure the cables are wired
correctly and connected correctly.
• Ensure that data is being

transmitted to the XCell processor
module.
• No Tx data. • In the case of a slave protocol,

ensure that data is received by
watching the RXD LED. If not, refer
to the actions for “No RX data”
above.
• Check the TXD LED for transmit

data.
• Ensure the communications cable

is connected to the correct port.
• Ensure that the protocol firmware

is installed in the XCell processor
module.
• Ensure that all the protocol

configuration parameters are
correct and have been downloaded
to the XCell processor module.
Page 95

• Protocol firmware may not be • Ensure the required protocol
installed on the XCell firmware is installed and running
processor module. correctly on the XCell processor
module. Some protocols use the
front panel LED matrix to display
the current status of the protocol.
Refer to the relevant protocol
documentation for further details.
• Interface cable is incorrectly • Ensure that the interface cable is

wired. correctly wired. If possible replace
the cable with a known good cable
and verify the operation.
• Check the RXD and TXD LEDs to

verify the RX cable and the TX from
the XCell processor module.
• Interface cable is connected • Ensure that the interface cable is

to the wrong XCell processor connected to the correct port on
module communications the XCell processor module.
port.
• Interface cable is not • Ensure that the interface cable is
connected properly. properly connected at both ends.
• Ensure that any cable terminators

are of the correct value (where
appropriate).

Page 96
Troubleshooting
Manual Version 1.06

• Interface cable is damaged. • Ensure that the interface cable is
not damaged.

• The protocol interface • Ensure that the protocol interface

parameters are not set parameters are correctly set at
correctly at both ends. both ends, e.g. speed, data
length, parity etc.
• The data to be transferred • Ensure that the data to be

over the protocol is not transferred is defined correctly at
defined correctly. both ends.
• Protocol configuration data • Ensure that all protocol

has not been downloaded to configuration data has been
the XCell interface processor downloaded to the XCell interface
module. processor module.
• Hardware settings incorrect • Ensure that the hardware links are

at one or both ends. set correctly at both ends for the
required communications
interface.
• Fibre Optic leads connected • Refer to section on "Fibre Optic

incorrectly. connections" in the XCell User
Manual and among the actions for
“XCell FieldNet LAN fault”. Page
101.
• Communications port fault. • Replace the processor module

correct operation.
Page 97

XCell not • XCell serial communications • Refer to the actions for “XCell
communicating, -RXD not working. serial communications not
LED is flickering but working”. Page 95.
TXD indicator LED
not lighting.
Communication • LED Fault. • Replace the processor module

LEDs not illuminating with a new module (if practicable)
as expected. and verify its correct operation.
• XCell serial communications • Refer to the actions for “XCell

not working. serial communications not
working”. Page 95.
Communications not • Fault with non-volatile • Refer to the actions for “Non-
working after the unit memory. volatile memory fault”. Page 56.
was powered OFF for
some time.
XCell appears to have • Unit powered OFF and lost • Refer to the actions for “Non-
lost its configuration its memory, volatile memory fault”. Page 56.
data.
Page 98
Troubleshooting
Manual Version 1.06

This section deals with troubleshooting the XCell FieldNet LAN. The
following section divides into General Guide to Network Troubleshooting
followed by a list of potential network problems. The General Guide
contains a list of points, general safeguards and guidelines which
should be observed when working with XCell processor modules
connected together over the FieldNet LAN. Further information may be
found in the XCell User Manual.
General Guide to Network Troubleshooting
Network troubleshooting can be difficult in a distributed system with

redundant networks. This section provides some general guidelines for
network troubleshooting:
• Ensure that the “online” LED is illuminated on all units.
• Under normal operating conditions all XCell processor modules on

the FieldNet network should have “Power” and “Online” LEDs ON; the
“Active” LED should flash. If the “Active” LED fails to light or remains
steady ON the module is not in an operational state.
• Ensure that all XCell processor modules on the network are fitted
with the same version of BASE software.
• Use the front panel OLU display to verify that each XCell processor
module can see all other units on the network. If this is not the case,
then identify a dividing point in the network and check all connections
and modules at this point.
• Use the front panel PRI display to establish which network of the
redundant pair each unit is using for its communications, (all units
should be on the same network).
• Powering off one XCell processor module on the network should

cause all others to swap to the other network and remain on that
Page 99
network. If they fail to remain there it indicates a problem with that

network.
• Remove any fibre optic ring monitoring modules from the network to
simplify troubleshooting.
• Disconnect field I/O and communication links to eliminate these as

the cause of the problem.
• Try to identify if the problem is associated with a particular unit or range

of units. If so, remove them from the system temporarily and verify the
operation of the network without them. It is better to completely
disconnect the particular units (including patching out entire locations
at the fibre optic patch panels) rather than simply powering OFF XCell
processor modules.
• Ensure that cables used for interconnecting XCell processor

module racks are of the right type and wired correctly.
• Ensure the copper network segments are properly terminated.

Incorrect network termination may give rise to both network and swap-
over problems, refer to the XCell User Manual for correct network
termination procedure.
• Ensure fibre optic cables connect the transmitter on one card to the
receiver on another.
• Ensure that fibre optic cables do not exceed their maximum bend
radius.
• Powering OFF a fibre optic module disconnects the network at that

point, as the network signal is not retransmitted to the next point if the
card is powered OFF.
• Ensure that the maximum number of XCell processor modules

sharing a copper network does not exceed 32. If more than 32 units are
to be networked together a fibre optic connection must be used.
Page 100
Troubleshooting
Manual Version 1.06
• Ensure that the maximum FieldNet operating distance without fibre-

optic connections does not exceed sixty metres (60m).

XCell FieldNet LAN • Multiple XCell processor • Ensure that no two XCell processor
fault modules with the same modules on the LAN have the same
address. unit address set on the front panel.
• Unterminated copper LAN • Ensure that all copper segments of

problems. the LAN are correctly terminated at
both extremities, i.e. each copper
section separated by fibre optic links
must be terminated at both ends.
• Use the “General guide to network

troubleshooting” above to narrow the
source of the problem.
• XCell processor module • Power OFF any failed units on the

failed with watchdog FieldNet LAN, attempt to power them
disabled. i.e. Failed LED is ON again only after the FieldNet LAN
ON or Activity LED is not is stable.
Blinking.
• Incorrect fibre optic • Ensure that all fibre optic leads are
connections. connected to the correct points, i.e.
upstream to down-stream, on the
next node, down-stream to upstream
on the next node, LAN A to LAN A
and LAN B to LAN B.
• Badly connected fibre • Ensure that all fibre cables are

links. securely connected.
Page 101

• Badly connected copper • Ensure that all copper cables are
cables. securely connected particularly
between racks.
• Multiple racks incorrectly • Ensure that all racks connected on

connected. copper are connected in series with
network terminations at both
extremities of the copper FieldNet
LAN.
• Un-screened copper • Ensure that all interconnecting

cables. copper cables are screened with one
end securely connected to earth.
• Ensure that only specified cable

types are used.
• Faulty or disconnected • Ensure that all network cables

network cabling. (copper and fibre optic) are good and
properly connected.
• Fibre Optic module used in • Ensure that all Fibre Optic modules
the network is powered are powered ON and appear to be
OFF. functioning correctly.
• Fibre optic patch lead is • Ensure that no fibre optic cables are
bent severely and damaged bent to exceed their minimum bend
as a consequence. radius or it can be assumed that they
are permanently damaged.
• Replace any suspect fibre optic

leads.
• Fractured or damaged fibre • Replace any fractured fibre optic

optic cables. cables ensuring not to exceed the
maximum bend radius on the fibre.
Page 102
Troubleshooting
Manual Version 1.06

• XCell processor modules • Power OFF any XCell processor
stopped or constantly modules that are stopped or regularly
rebooting. rebooting. When the network
stabilises (i.e. when no further
diagnostic messages are displayed
on the front panels of the XCell
processor modules) the units may be
powered ON again one at a time
ensuring that no unit has an adverse
affect on the FieldNet LAN.
• Refer to the actions listed for “XCell

processor module rebooting
continuously”. Page 54.
• Excessive network traffic • Disconnect any constantly changing

for a prolonged period of I/O to identify the problem. Increase
time. downloads on analogues to reduce
analogue traffic. Configure auto
suppression on digitals to eliminate
chattering inputs.
XCell processor • XCell processor module is • Ensure that both XCell processor
module cannot be powered OFF. modules are switched ON using the
seen by another front panel power switch.
XCell processor
module.
Page 103

• XCell processor modules • Verify using the front panel OLU
may be communicating on display that the other unit is visible
different networks (A and (online). One unit may be on the
B) in a dual redundant pair. network A and the other on network B
Verify using the front panel of a dual network system.
OLU display.
• If the other unit is not visible then
power it off and power it back on
again. Wait for one minute and verify
the OLU display again. If it remains
unseen, power OFF the local XCell
processor module and power it ON
again. Verify the OLU display.
• XCell FieldNet LAN is • Refer to the actions for “XCell

faulty. FieldNet LAN fault”. Page 101.
Fibre Ring Monitoring • Indicates that a fault was • Refer to the actions listed for “XCell
module (OPB) detected elsewhere in the FieldNet LAN Fault”. Page 101.
displays ”CLS” on the F.O. Ring and the Ring
Front Panel. monitor had to close to
compensate for the fault.
Page 104
Troubleshooting
Manual Version 1.06

This section deals with troubleshooting time synchronisation in XCell
systems. The following list of points contains general information
useful when implementing time synchronisation in XCell systems.
Further information may be found in the XCell User Manual and
specific clock documentation.
• Ensure that the clock antenna is always positioned in such a

way that it receives a clear signal.
• Different clocks have different methods of informing the user that

no signal has been received, For further information refer to the
specific clock documentation.
Page 105

Master station events • The source XCell I/O processor • Ensure that the XCell
time-stamped as 01 module has restarted at some processor module is not
January 1970. stage and generated events rebooting due to some fault.
before it had its clock re-
synchronised.
• Clock source (GPS or Master • Ensure that the clock source

Station) has failed. is operational and regularly
sending time update to the
XCell system.
• Clock source (GPS or Master • Ensure GPS antenna is

Station) has an incorrect time. correctly positioned to receive
the clock signal.
• Ensure that the clock source

has correct time and
maintains it on an ongoing
basis.
• XCell processor module • Ensure that XCell clock

connected to the clock source interface unit is fully
is powered OFF or has a fault. operational and no diagnostic
messages are displayed on
the Front Panel.
• Clock source connection fault. • Ensure that the interface cable

is correctly wired and properly
connected at both ends. The
wiring of the interface cable is
manufacturer specific and
depends on the type of clock
used, refer to the
documentation supplied with
the clock being used.
Page 106
Troubleshooting
Manual Version 1.06

• The clock source may be • Ensure that the clock source
connected to the wrong XCell is connected to the correct
processor module or to the port on the correct XCell
wrong port. processor module.
• Ensure that the XCell

processor module has the
correct clock protocol firmware
fitted.
• GPS Clock is not receiving • Ensure that the antenna is

time correctly. always positioned in such a
way that it receives a clear
signal.
Page 107
Page 108
Sequence Of Events Fault Finding Guide
Version 1.06
Sequence of Events Fault Finding Guide.

This section deals with troubleshooting potential problems which
may arise when attempting to retrieve a Sequence Of Events file
from the IEC-870 XCell processor module. Further information may
be found in the XCell User Manual.
Page 109

Unable to upload • No events marked for SOE • Ensure that required points are
Sequence Of Events storage occurred. configured in IEC mapping with an
(SOE) file via IEC870. indication that they are to be logged
in SOE file.
• IEC-870 not configured to • Ensure that IEC-870 is configured to
maintain an SOE file. maintain an SOE file.
• The SOE may be empty at the • Ensure that some SOE points have
time of request. changed before uploading the file.
• Ensure that the SOE file has not

been previously uploaded and is
therefore empty at the time of the
new request.
Page 110
Troubleshooting
Manual Version 1.06

This section deals with troubleshooting IEDs which are third party
Intelligent Electronic Devices used to gather data from the field.
Refer to the specific equipment manual for configuration and fault-
finding details relating to a particular device. The following list of
points contains general safeguards and precautions which should be
observed when connecting IEDs to XCell hardware.
• Always read the IED manufacturer-supplied

documentation before connecting IEDs to XCell
hardware.
• Always ensure that correct, manufacturer specified,

cables and connectors are used with IED devices, (for
example, is RTS/CTS specified or required).
• Some devices require specific manufacturer supplied

cabling in order to perform specific tasks, e.g. convert
TTL to RS232. Ensure that such cabling is in place if
required.
• Ensure that each device is correctly set up for

communications. i.e. correct baud rate, communications
port, parity and any other necessary parameter, (refer to
the user documentation for the specific device for further
details).
Page 111

No data values being • IED failed or communications • Refer to the actions for "IED
displayed from IED. fault. failed or communications
fault”. Page 113.
• IED data not being retrieved • Ensure that the IED is

from IED configured with the correct data
points (use the manufacturer's
software to verify if appropriate).
• Ensure that the XCell processor

module is configured to retrieve
the points from the appropriate
IED address. Refer to the
eXpert User Manual for further
information.
• Conflict between IED data and • Ensure that there is no conflict

XCell I/O modules. between the XCell and / or I/O
modules and the data being
returned from the IED by
removing the XCell I/O modules
and verifying the situation
again.
• XCell processor module • Refer to the actions for “XCell

connected to the IED cannot processor module cannot be
be seen by the processor seen by another XCell
module transferring the data for processor module”. Page 103.
display.
• IED data not transferred by • Refer to the actions for “I/O not
XCell to the display system. transferred by the XCell
protocol Interface unit”. Page
74.
Page 112
Troubleshooting
Manual Version 1.06

• Problem with the HMI interface. • Refer to the section on
"Operator Workstation Fault
Finding Guide” of this
document (page 20) for further
information.
IED failed or • Device Failure. • Ensure that the device is

communications powered ON and functioning
fault. correctly, (refer to device user
manual).
• Unable to communicate with • Refer to the section on "XCell

the device. serial communications not
working". Page 95.
• Ensure that the IED device is

configured with the correct unit
address.
• Ensure that no two IED devices

have the same unit address.
• Verify cables, cable

connections, cable terminators,
IED communications settings
and any other relevant device
parameter against the IED
manufacturer specifications.
IED device status is • IED failed or communications • Refer to the actions for "IED
"Failed". fault. failed or communications
fault". Page 113.
Page 113
Page 114
Troubleshooting
Manual Version 1.06

This section deals with troubleshooting potential problems involving the
eXpress software package. The following list of points contains general
safeguards and precautions which should be observed when working
with eXpress. Further more detailed information may be found in the
eXpress User Manual and Language Reference
• Before a tag is exported to eXpress from eXpert, ensure

the eXpert database has been compiled.
• Ensure different channel numbers are selected for each

eXpress tag (of the same type) within an eXpress unit.
• eXpress will only scan inputs and drive outputs; real

outputs will not be read by eXpress.
• Inputs / Outputs in eXpress are defined from the view-point

of the master station.
• If real Analogue Outputs (e.g. set-points) need to be taken

into an eXpress program through IEC to be used in driving
other outputs they will need to be mapped to virtual
eXpress Analogue Outputs.
• When defining virtual eXpress Inputs / Outputs, it is

necessary to define them in the same XCell unit running
the eXpress program.
Page 115

Unable to connect to • The Cell target processor • Power OFF the XCell processor
XCell target processor module does not have eXpress module and check the eXpress
module for firmware installed. PROMs. Ensure they are present
Debugging. and correctly installed.
• Check memory jumpers on the

XCell processor module board.
(Refer to jumper section of the
XCell User Manual).
• The connection to the XCell • Ensure that the eXpress PC is

processor module is via a port connected to an XCell
that does not allow an eXpress communications port that
download. supports configuration.
• The communication port should be

defined in the PC-PLC link set-up.
(Refer to the eXpress User
Manual and Language
Reference for further details).
• LED activity seen on the • Ensure that eXpress firmware is

bottom port of the target XCell installed on the target XCell unit.
processor module while trying
to establish communications to • Ensure that the PROM jumper
the target. (eXpress comms settings are correct for the
task not running). firmware installed.
• Get a new set of eXpress firmware

and re-install it in the XCell
processor module.
• Verify that the correct slave

number is used in the “Link Set-
up,” this should be equal to one.
Page 116
Troubleshooting
Manual Version 1.06

• Incorrect communications • Check that the communications
parameters may be set up. cable is correctly wired and
functioning (see the XCell User
Manual). Ensure the correct baud
rate is used and that the target
XCell Processor module unit-
number is correct.
Communications lost • Parameters missing from • Check the .INI file against the set-
on a regular basis eXpress .INI file. up specified in the eXpress User
while debugging an Manual and Language
application on the Reference .
target XCell unit.
eXpress program is • eXpress program not • Ensure that the eXpert

not responding to I/O. downloaded. configuration was compiled before
exporting tags to eXpress.
• Ensure that the correct compiler

options were selected (in
eXpress) prior to downloading.
• I/O configuration not • Make sure the hardware

downloaded or downloaded configuration is saved at the front
incorrectly. panel of the XCell processor
module using the ‘SHC’ menu
item.
• Re-compile any relevant eXpert

configurations and re-download
them to all relevant I/O units.
• eXpress program not running. • Check the DBG LED matrix on

the front panel of the target XCell
processor module to establish if
eXpress is running.
Page 117

eXpress application is • eXpress program not running. • Refer to the actions for “eXpress
not activating outputs application is not operating”.
Page 118.
eXpress unit is • eXpress cycle time is too short • Ensure that the eXpress cycle
constantly rebooting. for the eXpress logic and all time allows sufficient time for the
other XCell activities. eXpress sequence and all other
XCell processing activities. No
eXpress logic sequence should
have a cycle time of zero.
• Other possible causes for an • Refer to the actions listed for

XCell processor module to “XCell processor module
reboot. rebooting continuously”. Page
54.
eXpress application is • The application is not • Ensure that the correct compiler
not operating programmed correctly. options were selected prior to
verifying and downloading.
• Use the eXpress debugger to

evaluate the problem.
• The eXpress application was • Check the communications

not downloaded to the target. hardware set-up is functioning and
that the correct parameters have
been selected. Re-download the
configuration.
• LED 1a on the XCell processor

module front panel LED matrix
should be active if an application
is downloaded.
Page 118
Troubleshooting
Manual Version 1.06

• The eXpress manager process • Select ‘DGB’ from the Field
is not running in the target Service Debug (FSD) menu on the
XCell processor module. front panel display of the target
XCell processor module and
check if eXpress is running. LED
a4 should be pulsing if the
eXpress kernel is working in the
XCell processor module. LED a16
should be on when the application
starts.
• The application was deleted • Download a new version of the

due to clearing BRAM, the application.
non-volatile storage.
• The XCell configuration for the • Download the configuration again.

I/O points was not downloaded
to the various XCell processor
modules.
• XCell hardware does not • Ensure that the target XCell

support the application processor module has eXpress
firmware and sufficient RAM
installed.
eXpress application is • eXpress program not running. • Refer to the actions for “eXpress
not activating outputs. application is not operating”.
Page 118.
I/O connection error • Multiple eXpress tags were • Ensure each eXpress point has a
generated in eXpress generated with the same unit unique combination of unit and
compiler. and channel number. channel.
Page 119
Page 120
Version 1.06

This section deals with troubleshooting the eXpert software package.
eXpert is a configuration software package supplied for use with
Microsol hardware. The following list of points contains general
safeguards and precautions which should be observed when using
the eXpert package. For a full description of this software’s
functionality and capabilities see the eXpert User Manual.
• It is essential that Microsoft Access be installed on your

computer before attempting to use eXpert.
• eXpert does not work in 256-colour mode, ensure an

alternative higher resolution graphics mode is employed.
• Ensure that the correct serial cable is used and that it is

connected to the correct port on the XCell processor
module, (see the eXpert User Manual for further
information).
• Remember that the number of the physical channel is

not the same as the record number in the eXpert
database.
• Ensure that the eXpert configuration for point types

CANNOT have duplicated channel numbers. Use the first
channel number when configuring DDI (Double Digital
Input) values
• Ensure to always maintain a backup of the eXpert

database.
• Ensure the actual hardware installed in the XCell rack

matches the intended configuration to be downloaded
from eXpert.
Page 121
• Ensure that eXpert configurations are compiled prior to

downloading. If a change is made in a configuration it
must be compiled in order for the change to take effect.
• Ensure that the configuration downloaded from eXpert

matches the hardware present.
• Analogue Output modules cannot be configured directly

using eXpert. They can only be configured as raw point
types
• Always use the correct downloading sequence. For

example, when downloading IEC tables, the IECGEN
table should be downloaded last.
• Ensure that the XCell hardware configuration has been

saved using the ‘SAV’ option on the ‘SHC’ front panel
menu item, otherwise downloads may not work as
intended
• Ensure that the proper values have been downloaded

from eXpert and in the correct order, for example ensure
that the IECMAP table precedes the IECGEN table.
(Refer to the eXpert Manual for further information.
• Ensure that the XCell communications processor module is

communicating, check the Tx and Rx front panel LEDs.
• When using eXpert ensure that the unit number you are
trying to connect to is the same unit number set in the
eXpert dialog box.
• eXpert is not designed to have multiple instances run on

the same computer at once.
• When editing, using eXpert, users should not have

multiple spreadsheet editors open simultaneously.
Page 122
Version 1.06
• If an “Abort Script Error” message occurs when using

eXpert, the user should shut down the eXpert application
and also kill the NTVDM (NT Virtual Dos Machine).
1. Run Task Manager in Windows NT
2. Select the process tab.
3. Select the process NTVDM
4. Select the end process button.
5. Press OK on the warning dialog-box
that is raised.
Page 123

Unable to enter a new • Data entry mode is not • Double click on the right hand
value in a field. selected. mouse button to select data
entry mode.
Newly entered value • Data entry not completed with • Ensure that all data entry is
not stored in the field. the “Enter” key. Possibly used completed with the “Enter”
the mouse to select another key.
field.
Failed to download to • Link failure or communications • Verify the communications link

the target XCell failure. using the Test function in the
processor module. FieldNet Tab Dialogue from the
Comms menu.
• Check that the

communications cable is
connected properly to the
correct XCell processor module
port and is functioning
normally.
• The target XCell processor • Refer to the sections on

module is powered OFF or not troubleshooting XCell hardware
functioning properly. (page 45) in this document.
Page 124
Version 1.06

• XCell hardware does not match • Ensure that the target XCell
the configuration requirements. processor module has the
required hardware for the
configuration being
downloaded.
• Ensure that the hardware set-

up has been saved on the
target XCell processor module
using the SAV option on the
SHC menu of the XCell front
panel.
• Diagnostic message displayed • Refer to the appendix on “Front

on the front seven-segment Panel Diagnostic Messages”
display of the gateway XCell (page 132) for further
processor module. information.
• Diagnostic message displayed • Refer to the appendix on “Front

on the front panel seven- Panel Diagnostic Messages”
segment display of the target (page 132) for further
XCell processor module. information.
• eXplore is also connected into • Exit the eXplore package

the same XCell system and properly and run eXpert.
both packages conflict with the
same interface address.
Test function failed in • PC not connected to the XCell • Ensure that the interface cable
the FieldNet Tab FieldNet network. is connected to the correct
Dialogue from the serial port on the PC and to the
Comms menu. correct port on the XCell
processor module.
Page 125

• Incorrect gateway XCell unit • Ensure that the gateway XCell
number is configured in the PC unit number is set to that XCell
comms Tab Dialogue. unit number to which the PC is
connected.
• The gateway XCell processor • Refer to the “XCell Fault

module is powered OFF or not Finding” section of this
functioning properly. document (page 45) for
information on troubleshooting
XCell units.
• Incorrectly wired interface • Ensure that the interface cable

cable. between the PC and the XCell
system is correctly wired.
Refer to the eXpert User
CFG- 027 message • Download failed because the • Wait for approximately one
returned on the PC. XCell processor module had minute to allow the previous
not terminated the previous download session to timeout in
configuration session. the XCell target and try to
download again.
Error message • eXpert requires more than 256 • Ensure the display is set in a
“Exception in Delete colours in its set-up graphics mode with more than
Object errno = 2” 256 colours.
“Protocol • Failing to communicate with • Check settings in eXpert.

Instantation Failure” the relevant XCell processor
message module. • Be sure to compile the
encountered when configuration properly.
trying to download a
DDI, SDI or DO • Ensure the PC serial cable is
configuration from connected to the upper port on
eXpert. the XCell processor module.
Page 126
Version 1.06

• The XCell hardware • Ensure that all I/O modules are
configuration may not see the installed and visible using the
I/O modules in question. SHC menu option on the XCell
front panel.
• The XCell hardware • Ensure that the hardware

configuration may not have configuration is saved using
been properly saved. the front panel SHC option.
• The wrong XCell processor • Ensure that the unit number

module number may have been you are trying to connect to is
given in the eXpert the same unit number set in
configuration. the eXpert dialog box.
• Trying to communicate with an • Always allow a little time

XCell processor module too (40sec) before attempting
soon after powering it ON. communications with a newly
installed XCell processor
module.
Error encountered • Attempting to configure non- • Check the front panel message
when trying to existent hardware. For generated on the target XCell
configure Analogue or example, trying to configure 64 processor module. Refer to the
digital I/O modules. channels when only one card appendix on “Front Panel
is installed. Diagnostic Messages” (page
132) for an interpretation of all
relevant front panel user
messages.
• Install additional hardware, as

required, to match the eXpert
configuration.
• Adjust the eXpert configuration

to match the hardware present.
Page 127

• The XCell hardware • Ensure that the hardware
configuration may not have configuration is saved using the
been properly saved. front panel SHC menu option.
Error encountered • An XCell processor module • Allow at least forty seconds

when trying to needs a short time to stabilise after power ON for the XCell
configure an XCell on the network immediately processor module to rejoin the
processor module too following power-ON. network.
soon after powering
on.
Page 128
Version 1.06
Page 129

This section deals with troubleshooting the eXplore
software package. eXplore is a diagnostic tool for use with
XCell hardware. For a full description of this software’s
functionality and capabilities see the eXplore User
Manual.
Page 130
Version 1.06

Raw Digital Input is • XCell processor module is • Ensure that the associated XCell
not displayed powered OFF. processor module is switched ON
correctly in eXplore using the front panel power switch.
connected directly to Wait one minute for the unit to
the input unit. power ON fully. Exit eXplore and
restart the package.
• Fault on the XCell I/O unit. • Refer to the actions for “Digital
Input LED matrix not reflecting
the plant status”. Page 70.
Raw Digital Input is • XCell I/O unit is powered OFF. • Ensure that the XCell I/O unit is
not displayed switched ON using the front panel
correctly in eXplore power switch. Wait one minute for
connected to another the unit to power ON fully. Exit
XCell processor eXplore and restart the package.
module.
• Fault on the XCell I/O • Refer to the actions for “Digital
processor module. Input LED matrix not reflecting
the plant status”. Page 70.
eXplore interface unit. processor module cannot be
seen by another XCell processor
Processed Input • XCell Processed Digital Input • Refer to the actions for “XCell
(SDI, DDI etc) is not (SDI, DDI etc) is not Processed Digital Input (SDI, DDI
displayed correctly in functioning in the XCell etc) is not functioning in the
eXplore connected processor module. XCell processor module”. Page
directly to the input 71.
unit.
Page 131

Processed Input • XCell Processed Digital Input • Refer to the actions for “XCell
(SDI, DDI etc) is not (SDI, DDI etc) is not available Processed Digital Input (SDI, DDI
displayed correctly in in another XCell processor etc) is not available in another
eXplore connected to module. XCell processor module”. Page
another XCell 72.
processor module.
Analogue Input is not • XCell processor module is • Ensure that the associated XCell
displayed correctly in powered OFF. processor module is switched ON
eXplore. using the front panel power switch.
Wait one minute for the unit to
power ON fully. Exit eXplore and
restart the package.
• Fault on the XCell I/O unit. • Refer to the actions for “Analogue
Input not changing in the
source I/O unit – verified using
eXplore”. Page 88.
Page 132
Front Panel Diagnostic Messages
Version 1.06
Page 133
8. APPENDIX ONE
This appendix lists diagnostic messages that may be encountered on the
front panel seven segment display of an XCell processor module. The
message display combines a three-character string followed by a three-digit
number.
Individual messages may appear as a result of many factors and the

particular message observed is, in many cases, dependent on prevailing
operational conditions.
Each message and any corrective actions are described in the following
tables.
Diagnostic messages are divided into two categories: 1) those that appear
during XCell system initialisation and 2) those that appear when the XCell is
actually running.
System Initialisation Diagnostics

System initialisation is broken into two main sections.
a) Firmware and Operating System initialisation

b) Application level initialisation
An incrementing number displays on the front panel as individual parts of the

system initialise. If initialisation fails at some point the last number remains
visible until the unit is reset (either manually or by the Watchdog).
Page 134
Version 1.06
Firmware and Operating System Diagnostics

Firmware and operating system initialisation is covered by step numbers
between 0 and 140 as follows :
000 - Clear Operating System configuration tables.

010 - Initialise Vector Table.
020 - Build System Memory Map.
030 - Initialise pSOS Configuration Table with defaults.
040 - Register the default I/O card ID.
050 - Register device driver 0.
060 - Register clock device.
070 - Register EEPROM device
080 - Register default number of OS Resources.
090 - Search for memory map for Named Blocks.
100 - Run cold initialisation for Microsol library.
110 - Run cold initialisation for all Named Blocks.
120 - Initialise pSOS configuration table with system
requirements.
130 - Initialise the hardware timer.
140 - Start pSOS.
During firmware initialisation, a hardware clock missing status message

(HCL on the front panel for approximately 2 seconds between steps 130 and
140) may appear informing you that the hardware clock chip was not found.
Unless otherwise specified the hardware clock chip must be present on the
XCell processor module card.
Applications Initialisation Diagnostics

Application initialisation is covered by step numbers between 200 and 350
as follows:
200 - Initialise system variables to default values.

210 - Initialise hardware timer and system time.
220 - Initialise memory allocation control block.
Page 135
225 - Initialise the Battery Backed RAM region.

230 - Create system heap region.
240 - Create message control block partition.
250 - Resolve the run-time database server public symbol.
260 - Initialise the run-time database.
270 - Create applications group registration group.
280 - Create the I/O configuration group.
285 - Initialise system configuration group.
290 - Initialise system device drivers.
300 - Retrieve system variables from EEPROM.
310 - Runtime link the system variables.
320 - Initialise application device drivers.
330 - Run warm initialisation for all Named Blocks.
335 - Refresh all GSR addresses in BRAM.
340 - Run hot initialisation for all Named Blocks.
350 - Initialise the front panel display.
During application initialisation a Real Time Clock missing status message

(RCL on the front panel for approximately 2 seconds between steps 210 and
220) may appear informing you that the Real Time Clock chip was not found.
Unless otherwise specified the hardware clock chip is optional.
Page 136
Version 1.06
TABLE ONE
Message Cause Action

000 General XCell processor module Ensure the EEPROM chip is correctly inserted on the XCell
hardware failure. processor module. Ensure all RAM chips correctly inserted
on the XCell processor module. Ensure that all jumpers on
the XCell processor module are in the correct positions.
Refer to the XCell User Manual for further information on
jumper settings.
010 General XCell processor module Ensure all RAM chips correctly inserted on XCell processor
hardware failure. module. Ensure all jumpers on the XCell processor module
are in the correct positions. Refer to the XCell User
Manual for further information on jumper settings.
hardware failure. module. Ensure all jumpers on the XCell processor module
are in the correct positions. Refer to the XCell User
030 General XCell processor module Ensure the EEPROM chip is correctly inserted XCell
hardware failure. processor module. Ensure RAM chips correctly inserted on
the XCell processor module. Ensure all jumpers on the XCell
processor module card are in the correct positions. Refer to
the XCell User Manual for further information on jumper
settings.
040 General XCell processor module Ensure all RAM chips correctly inserted on the XCell
hardware failure. processor module. Ensure all jumpers on the XCell
processor module are in the correct positions. Refer to the
XCell User Manual for further information on jumper
settings.
hardware failure. module. Ensure all jumpers on XCell processor module are in
the correct positions. Refer to the XCell User Manual for
further information on jumper settings.
Page 137

060 General XCell processor module Ensure that the hardware timer chip is correctly inserted on
hardware failure. the XCell processor module. Ensure all jumpers on the XCell
settings.
070 General XCell processor module Ensure the EEPROM chip is correctly inserted on the XCell
settings.
080 General XCell processor module Ensure all RAM chips are correctly inserted on the XCell
settings.
090 Invalid or conflicting Named Blocks Ensure that correct versions of PROMs are installed on the
found in memory. XCell processor module. Ensure all PROM chips are
correctly inserted on the XCell processor module and not
corrupted. Ensure that code and data sections of Named
Blocks in PROM do not overlap.
100 The XCell processor module is Check that RAM and PROM jumpers on the XCell processor
reporting data corruption. module are correctly set. Ensure all PROM chips correctly
inserted on the XCell processor module card and are not
corrupted. Refer to the XCell User Manual for further
information on jumper settings.
110 Data corruption or invalid Named Check that RAM and PROM jumpers on the XCell processor
Block. module are correctly set. Ensure that correct versions of
PROMs are installed on the XCell processor module. Ensure
all PROM chips are correctly inserted on the XCell processor
module card and are not corrupted. Refer to the XCell User
Page 138
Version 1.06

120 General XCell processor module Ensure that RAM chips are correctly inserted on the XCell
hardware failure. processor module card. Ensure that all jumpers on the XCell
processor module card in the correct positions. Refer to the
settings.
130 General XCell processor module Ensure the hardware timer chip is correctly inserted on
hardware failure. XCell processor module card. Ensure that RAM chips are
correctly inserted on XCell processor module. Make sure all
jumpers on XCell processor module card are in the correct
positions. Refer to the XCell User Manual for further
140 Invalid or corrupted PROM chips. Ensure correct versions of PROMs are installed on the XCell
processor module card. Ensure that all PROM chips are
correctly inserted on the XCell processor module and are
not corrupted. Ensure that all jumpers on the XCell
processor module card in the correct positions. Refer to the
settings.
200 General XCell processor module Ensure all RAM chips are correctly inserted on the XCell
hardware failure. processor module Card. Ensure that all jumpers on the XCell
settings.
210 General XCell processor module Ensure the Hardware Timer Chip is correctly inserted on the
hardware failure. XCell processor module card
220 Data corruption or invalid Named Check that RAM and PROM jumpers on the XCell processor
Block. module card are correctly set. Ensure that correct versions
of PROMs are installed on the XCell processor module.
Ensure that all PROM chips are correctly inserted on the
XCell processor module card and not corrupted. Ensure that
Code and Data sections of Named Blocks in PROM do not
overlap. Refer to the XCell User Manual for further
Page 139

225 The XCell processor module is Check that RAM jumpers on the XCell processor module
reporting that it has insufficient card are correctly set. Ensure that correct versions of
memory. PROMs are installed on the XCell processor module card.
jumper settings.
memory. PROMs are installed on the XCell processor module card.
jumper settings.
memory. PROMs are installed on the XCell processor module. Refer to
settings.
250 General XCell processor module Check that RAM jumpers on the XCell processor module
hardware failure. card are correctly set. Ensure that correct versions of
PROMs are installed on the XCell processor module. Refer to
settings.
settings.
settings.
settings.
Page 140
Version 1.06

settings.
290 General XCell processor module Ensure all input/output boards are correctly inserted in the
hardware failure. rack. Ensure the correct versions of EPROMS are installed.
295 General XCell processor module Ensure all input/output boards are correctly inserted in the
hardware failure. rack. Ensure the correct versions of EPROMS are installed.
Make sure that each additional board in the rack is correctly
connected to the power supply.
300 General XCell processor module Ensure the EEPROM chip correctly inserted on the XCell
hardware failure. processor module card. Ensure all RAM chips are correctly
inserted on the XCell processor module card. Ensure all
jumpers on the XCell processor module are in the correct
positions. Refer to the XCell User Manual for further
settings.
320 An application running on the Ensure that the correct versions of PROMs are installed on
XCell processor module has the XCell processor module card.
caused an error.
caused an error.
settings.
Page 141

caused an error.
settings.
Page 142
Version 1.06
System Runtime Diagnostics

The string specifies which application or system module generated the message. The
number specifies which error occurred in that module. The number identifies the specific
diagnostic message within the module. The message strings are divided into three groups
as follows:
1) System Modules:
SYS System interface
bRA Battery Backed RAM driver
DB Runtime database
DD Distributed database manager
CFG Configurator
NET FieldNet network
2) I/O Server :
AIR Standard AI driver
AO Raw Analogue Output Point Type
AOI Standard AO driver
DI Standard DI driver
HAI High density AI driver
RAI Raw Analogue Input Point Type
RDI Raw Digital Input Point Type
RDO Raw Digital Output Point Type
RHS Raw HSC Point Type
SIO I/O Scheduler
3) High Level Point Types :

ACU High level Accumulator Point Type
AIP High level Analogue Input Point Type
AOP High level Analogue Output Point Type
bCD High level BCD Point Type
DIP High level Digital Input Point Type
DOP High level Digital Output Point Type
IEC IEC 870-5 protocol
PTE High level Point Type engine
Page 143
SPT High level Point Type scheduler
System Modules
System Modules are software components managing system resources (i.e. memory,
database etc).
Problems sometimes arise in system modules due to erroneous actions taken by an
application attempting to access a system resource.
I/O Server Modules

I/O server modules are software components interfacing to I/O hardware. The I/O Server
consists of drivers for each I/O board type, a raw Point Type for storing the I/O data and a
scheduler, which calls the I/O drivers to scan the hardware.
High Level Point Type Modules

The high level Point Type modules are software components that perform high level
processing of raw Point Type values and storage of the processed values.
AC Measurement Information Messages

ACI cards generate many Front Panel Diagnostic Messages as described below.
ACI - 001 to ACI - 099 inclusive are internal XCell system messages and are not
user-serviceable. When these messages are seen and the XCell does not recover, the
unit should be powered OFF then on again. If the message persists the user should
power OFF the XCell and clear BRAM then reconfigure the unit from eXpert. If the
difficulty remains, your equipment vendor should be notified.
ACI - 100 to ACI - 199 inclusive are XCell ACI configuration messages.
Most of these messages point to problems in the user’s eXpert configuration.
When these messages are seen the AC measurement configuration causing the
message is rejected and any previously valid AC measurement configuration running on
the XCell continues to run. (Other Point Types on the local unit are not affected).
Page 144
Version 1.06
ACI-200 to ACI-229 inclusive are ACI card failure messages. These messages indicate a
problem with the ACI module. Indicating a DSP not performing within expected bounds
that may have ceased to update its heartbeat register leading the XCell to conclude the
DSP has failed. These messages are usually cleared by re-booting the XCell processor
module. If this action fails to resolve the problem the card may need to be replaced.
ACI-230 to ACI-250 inclusive are ACI card non-fatal warnings of no concern to the
customer.
NOTE: Messages not listed below should be communicated to your system supplier.
Page 145
TABLE TWO.

ACI-100 The ACI DSP rejects eXpert configuration. Ensure that correct software versions are
installed in the XCell processor modules.
ACI-101 ACI card is not present or has failed. Ensure that ACI cards are installed in the
correct slot positions. Refer to XCell User
Manual.
ACI-102 Attempting to configure more than eight AC Make sure the cards installed in the XCell
channels for AC RMS Phase measurement. processor module match the configuration
established in eXpert. Check configuration
tables.
ACI-103 Attempting to configure more than eight AC Ensure the eXpert configuration matches the
channels for AC frequency measurement. installed hardware. Check configuration
tables.
ACI-104 The DC Analogue channel is out of range. Compare the installed hardware list with the
eXpert configurations and correct as
appropriate. Check number of channels in the
ACM16 configuration table.
ACI-105 Attempted to configure an AC frequency Ensure the eXpert configuration matches the
over DC Analogue. installed hardware. Check frequency settings
in the ACM16 configuration table.
ACI-106 ACI Card number out of range. Compare the installed hardware list with the
appropriate. Check the card number in the
ACICARD configuration table; ensure card
number is within the allowed range.
ACI-107 Attempted to configure AC RMS Phase over Compare the installed hardware list with the
DC Analogue. eXpert configurations and correct as
appropriate. Check number of channels in the
ACM16 configuration table.
ACI-108 Type of AC Channel has different settings in Ensure the eXpert configuration matches the
different feeders. installed hardware. Check the feeder settings
in the ACIFDR configuration table.
Page 146
Version 1.06

ACI-109 Feeder out of range for AC RMS Line Ensure the eXpert configuration matches the
Voltage. installed hardware. Check the feeder settings
in the ACM16 configuration table.
ACI-110 Maximum CT or VT input for a feeder is set to Ensure the eXpert configuration matches the
zero. installed hardware. Check the CT and VT
settings in the ACIFDR configuration table are
nonzero.
ACI-111 Attempt to configure DC Analogues on a non- Make sure the cards installed in the XCell
DC Analogue ACI card. processor module match the configuration
established in eXpert. Check the DC analogue
settings in the ACM16 configuration table.
ACI-112 Attempt to configure a 16-bit AC Compare the installed hardware list with the
measurement twice. eXpert configurations and correct as
appropriate. Check for AC measurement
conflicts in the ACM16 configuration table.
ACI-113 Attempt to configure a 32-bit AC Compare the installed hardware list with the
measurement twice. eXpert configurations and correct as
appropriate. Check for AC measurement
conflicts in the ACM32 configuration table.
ACI-114 Unable to configure one or more busy ACI Allow the busy ACI card to complete its time-
cards. critical task before attempting to download the
configuration.
ACI-115 Feeder out of range for derived power Ensure the eXpert configuration matches the
measurement. installed hardware. Check the feeder number
in the ACM16 configuration table. Ensure the
feeder number is within the allowed range.
ACI-116 Less than three current inputs defined for Ensure the eXpert configuration matches the
three-phase feeder. installed hardware. Ensure the correct three-
phase feeder settings in the ACICARD
configuration table.
Page 147

ACI-117 Feeder out of range for cumulative energy. Compare the installed hardware list with the
appropriate. Ensure the Cumulative Energy
function settings correspond to the correct
feeder numbers in the ACM32 configuration
table.
ACI-118 Attempt to configure AC RMS Line voltage on Ensure the eXpert configuration matches the
a single-phase feeder. installed hardware. Ensure the correct single-
phase and three-phase feeder settings in the
ACM16 and ACICARD configuration tables.
ACI-119 Less than three voltage inputs defined for a Ensure the eXpert configuration matches the
three-phase feeder. installed hardware. Ensure the three-phase
feeders are configured with three current
inputs and three voltage inputs in the ACIFDR
configuration tables.
ACI-120 Attempting to access more than 16 AC Ensure the channel number settings in the
channels for AC RMS phase measurements. ACM16 table are correct for AC RMS phase
measurement; the maximum channel number is
fifteen.
ACI-122 CT or VT type for an AC channel is Ensure the correct eXpert configuration is

inconsistent across feeder alliances. downloaded. Check the ACIFDR table for
multiple instances of CTs VTs and
inconsistencies across feeders.
ACI-124 Attempt to configure more than four Maximum Ensure the eXpert configuration matches the
four ACI cards in a single XCell. installed hardware. Ensure that no more than
four ACI cards are configured in the ACICARD
configuration tables.
ACI-125 ACI Card Numbers not configured in When configuring ACI cards in the ACICARD
ascending order. table.
Compare the installed hardware list with the
appropriate. Ensure ACI cards are configured
in ascending order in the ACICARD
configuration table.
Page 148
Version 1.06

ACI-126 No feeder configuration table exists. Ensure the eXpert configuration matches the
installed hardware. Ensure all ACI related
tables are downloaded in the configuration.
Note that the ACIFDR table is mandatory.
ACI-127 No feeders configured for at least one ACI Ensure the eXpert configuration matches the
card. installed hardware. Ensure each ACI card
have at least one associated feeder
configured in the ACIFDR table.
ACI-128 Feeder numbers for an ACI card do not start Ensure the eXpert configuration matches the
at zero. installed hardware. Ensure the first feeder
configured for each ACI card, in the ACIFDR
table is numbered zero.
ACI-129 Not enough configured feeders for AC RMS Compare the installed hardware list with the
Line Voltage. eXpert configurations and correct as
appropriate. Ensure there are sufficient
configured feeders for AC RMS line voltage
measurements in the ACM16 table.
ACI-130 Not enough configured feeders for derived Ensure the eXpert configuration matches the
power. installed hardware. Ensure there are sufficient
configured feeders for derived power AC
ACI-131 AC channel in a feeder does not exist. Compare the installed hardware list with the
appropriate. Ensure the assigned channel
exists in the ACIFDR table; eight channel cards
support from zero to seven, sixteen channel
cards support from zero to fifteen.
ACI-132 Feeder numbers for an ACI card are not Ensure the eXpert configuration matches the
contiguous. installed hardware. Ensure the feeder
numbers in the ACIFRD table are configured in
ascending order with the first feeder being
zero.
Page 149

ACI-133 Too many feeders configured on an ACI Ensure the eXpert configuration matches the
card. installed hardware. Ensure that no more than
seven feeders are configured for a specific
ACI card in the ACIFDR table.
ACI-134 Attempting to access more than sixteen AC Compare the installed hardware list with the
channels for AC frequency measurement. eXpert configurations and correct as
appropriate. Ensure that no channel is
configured beyond fifteen when configuring
an AC frequency measurement in the ACM16
table.
ACI-135 Not all ACI cards received a feeder Compare the installed hardware list with the
configuration. eXpert configurations and correct as
appropriate. Ensure all installed ACI cards
have at least one associated feeder
configured in the ACIFDR table.
ACI-136 Feeder configuration contains extraneous Check for inconsistencies between the eXpert
records. configuration and the installed hardware.
Ensure the ACIFDR table contains the correct
number of records. Ensure the correct number
of ACI cards are installed and functioning for
the intended configuration download.
ACI-137 Maximum system frequency is lower than the Ensure the eXpert configuration matches the
nominal system frequency. installed hardware. Ensure the maximum
system frequency is set greater than the
nominal system frequency in ACICARD table.
ACI-138 Reporting period is too short. Make sure the cards installed in the XCell
processor module match the configuration
established in eXpert. Ensure the AC
measurement reporting period is not less than
the reciprocal of the nominal system
frequency in the ACICARD table.
Page 150
Version 1.06

ACI-139 Attempt to use an un-configured AC channel. Ensure the eXpert configuration matches the
installed hardware. Ensure all channels are
configured without conflict for AC RMS, phase
and DC analogue measurements in the ACM16
table.
ACI-140 An AC measurement has been configured for Check the feeder table; ensure the channel
a channel that is not in the feeder table. exists in the table. Download the configuration
again.
ACI-141 Current and voltage AC Channels are Check for inconsistencies between the eXpert
identical within a feeder. configuration and the installed hardware.
Ensure AC channels are not configured to
provide both current and voltage inputs in the
ACIFDR table.
ACI-142 Current and voltage phases differ within a Ensure the correct eXpert configuration is
feeder. downloaded. Check the ACIFDR table for
multiple instances of CTs VTs and
inconsistencies across feeders. Ensure
voltage and current channels have the same
phase in the ACIFDR table.
ACI-143 Not enough configured feeders for Ensure the correct eXpert configuration is
cumulative energy. downloaded. Ensure the three-phase feeder
number is properly specified when configuring
a cumulative energy AC measurement in the
ACM32 table.
ACI-144 Delta for sixteen-bit AC measurement Ensure the delta value does not exceed 100%
exceeds 100%. when configuring sixteen-bit AC
ACI-145 Delta for thirty-t w o-bit AC measurement is Ensure the delta value does not exceed 100%
exceeds 100%. when configuring thirty-t w o-bit AC
ACI-146 Attempt to configure sixteen-bit AC Check for inconsistencies between the eXpert
measurement on non-existent ACI card. configuration and the installed hardware.
Check for failed or missing sixteen-bit ACI
cards.
Page 151

ACI-147 Attempt to configure thirty-t w o-bit AC Check for inconsistencies between the eXpert
measurement on non-existent ACI card. configuration tables and the installed
hardware. Check for failed or missing thirty-
t w o-bit ACI cards.
ACI-148 Attempt to configure a failed ACI card. Check for inconsistencies between the eXpert
configuration and the installed hardware.
Check for failed or missing ACI cards.
ACI-149 Attempting to access more than seven three- Check for inconsistencies between the eXpert
phase feeders on one ACI card. configuration and the installed hardware.
Ensure that no more than seven three-phase
feeders, numbered from zero to six, are
configured in the ACIFDR table; additional
feeders must be single-phase.
ACI-150 Single-phase feeders and three-phase Make sure the cards installed in the XCell
feeders are mixed on an ACI card. processor module match the configuration
established in eXpert. Ensure that all three-
phase feeders are configured before single-
phase feeders on the same card in the
ACIFDR table.
ACI-151 Max Current or Voltage input for an AC Check for inconsistencies between the eXpert
Channel is inconsistent across feeders. configuration and the installed hardware.
Ensure that all feeders are properly configured
in the ACIFDR table. Check maximum voltage
and current input settings.
ACI-152 Attempting to configure an incorrect number Check the software version number. Ensure
of feeders for the software installed. that the correct software is installed in the
XCell processor module for the intended
number of feeders. Some software versions
restrict feeder numbers.
ACI-154 Attempting to configure a feeder with no Check for inconsistencies between the eXpert
input AC channels. configuration and the installed hardware.
Ensure that all three-phase and single-phase
feeders are configured with voltage and
current inputs in the ACIFDR table.
Page 152
Version 1.06

ACI-155 Attempting to configure a single-phase Check for inconsistencies between the eXpert
feeder with a neutral current input. configuration and the installed hardware.
Ensure that all single-phase feeders are
configured without neutral current inputs in the
ACIFDR table.
ACI-156 Attempting to configure more than one Make sure the cards installed in the XCell
voltage input on a single-phase feeder. processor module match the configuration
established in eXpert. Ensure that all single-
phase feeders are configured with no more
than one voltage input in the ACIFDR table.
ACI-157 Attempting to configure more than one Check for inconsistencies between the eXpert
current input on a single-phase feeder. configuration and the installed hardware.
Ensure that all single-phase feeders are
configured with no more than one current
input in the ACIFDR table.
ACI-158 No neutral current input for three-wire three- Check for inconsistencies between the eXpert
phase feeder has been defined. configuration and the installed hardware.
Ensure that all three-phase feeders are
configured with the correct neutral current
source settings in the ACIFDR table.
ACI-159 Three-phase derived power measurement Check for inconsistencies between the eXpert
configured on single-phase feeders. configuration and the installed hardware.
Ensure that when configuring a derived power
AC measurement all relevant settings are
correct in the ACM16 table.
ACI-160 Use of neutral current input inconsistent Ensure the correct eXpert configuration is
across feeders. downloaded. Ensure that neutral current input
settings are consistent with three-phase
feeder settings in the ACIFDR table.
ACI-161 There is a mismatch between the allowed Check the software version number. Ensure
number of feeders and the software version that the correct software is installed in the
installed. XCell processor module for the intended
number of feeders. Some software versions
restrict feeder numbers.
Page 153

ACI-162 Three-phase feeder with derived neutral Ensure the correct eXpert configuration is
cannot have a Neutral Current input. downloaded. Ensure that neutral current input
settings are consistent with three-phase
feeder settings in the ACIFDR table. Ensure
that any three-phase feeder with a derived
neutral current input is set to Not Used in the
ACIFDR table.
ACI-167 Attempting to configure an incorrect number Check the software version number. Ensure
of DC analogue measurements for the that the correct software is installed in the
software installed. XCell processor module for the intended DC
analogue measurements. Some software
versions do not support certain
measurements.
ACI-169 The phase of an AC Channel is inconsistent Check for inconsistencies between the eXpert
across feeders. configuration and the installed hardware.
Ensure there are no phase conflicts for AC
channels across feeders in the ACIFDR table.
ACI-170 Attempting direct memory access to a non- Make sure the cards installed in the XCell
existent ACI card. processor module match the configuration
established in eXpert. Ensure a working ACI
card is connected to the XCell processor
module.
ACI-171 Attempting direct memory write outside the Check for inconsistencies between the eXpert
ACI card's memory range. configuration and the installed hardware.
Ensure an installed protocol is not trying to
write to a non-existent memory location on the
ACI card.
ACI-172 Attempting direct memory read outside the Check for inconsistencies between the eXpert
ACI card's memory range. configuration and the installed hardware.
Ensure an installed protocol is not trying to
read from a non-existent memory location on
the ACI card.
Page 154
Version 1.06

ACI-203 Bad memory location found on the ACI card. Check for inconsistencies between the eXpert
configuration and the installed hardware.
Power the XCell OFF then ON again, if
possible. If the message persists, replace the
ACI card.
ACI-204 The ACI card has been removed or has Make sure the cards installed in the XCell
failed. processor module match the configuration
established in eXpert. Pow er-OFF the XCell
processor module Ensure an ACI card is
present and working with the XCell processor
module. If an ACI card is present and the
message persists the card may be faulty.
ACI-205 The ACI card has failed to enter its start-up Check for inconsistencies between the eXpert
sequence. configuration and the installed hardware.
Power the XCell OFF then ON again. Ensure an
ACI card is present and working with the XCell
processor module. If an ACI card is present
and the message persists the card may be
faulty and need to be replaced.
ACI-206 The ACI card heartbeat has failed to start, the Check for inconsistencies between the eXpert
XCell has set the card as failed. configuration and the installed hardware.
Power the XCell OFF then ON again, if
possible. Ensure an ACI card is present and
working with the XCell processor module. If an
ACI card is present and the message
persistent the card may be faulty and need
replacement.
ACI-207 ACI card hardware version is unsupported. At power ON there is a hardware version
mismatch between the XCell processor module
and the ACI card. Reboot the XCell processor
module and ensure it supports the particular
ACI hardware version installed.
Page 155

ACI-208 ACI card software version is unsupported. At power ON there is a software version
mismatch between the XCell processor module
and the ACI card. Reboot the XCell processor
module and ensure the XCell firmware
supports the particular ACI software version
installed.
ACI-209 ACI card failed to exit start-up sequence. At power ON, the DSP processor on an ACI
card failed to complete its start-up sequence.
ACI-209 may also appear at run-time if the
XCell processor module resets an ACI card
and the DSP fails to restart properly. The ACI
card is marked as failed, eXpert configurations
are rejected. Reboot the XCell, repeatedly if
required.
ACI-210 ACI card was unsuccessfully reset after The ACI card has failed to acknowledge
failing to accept a time update. receipt of current time from the XCell
processor module and did not restart when
the XCell reset it. The ACI card is marked as
failed, eXpert configurations are rejected.
Reboot the XCell, repeatedly as required and
check eXpert configuration tables.
ACI-230 Information message announcing that the ACI ACI card processor lost its heartbeat but the
card heartbeat has been restored. XCell processor module successfully reset the
card. This message is only of significance if it
recurs very frequently in which case a faulty
card may be in place.
ACI-231 ACI card has ignored XCell for more than 10 The ACI card is engaged in a critical operation,
minutes. for example, opening or closing a relay, and
cannot be interrupted by the XCell processor
module. No user action is required unless the
XCell displays ACI -231 every ten minutes in
which case the ACI card may have failed
while carrying out a critical operation.
Page 156
Version 1.06

ACI-233 ACI card was successfully reset after failing The ACI card has failed to acknowledge
to accept a time update. receipt of current time from the XCell
processor module and did not restart when
the XCell reset it. The ACI card is marked as
failed, eXpert configurations are rejected.
Reboot the XCell, repeatedly as required and
check eXpert configuration tables.
ACI-234 ACI card reset due to sixteen-bit AC The ACI card has reported a 16-bit AC
measurement out of range. measurement outside of the predetermined
range. The XCell processor module
automatically resets the ACI card when this
occurs and corrects the problem. The
message is of significance only if it occurs
very frequently. Check the eXpert
configuration.
ACI –235 ACI card reset due to 32-bit AC measurement The ACI card has reported a 32-bit AC
out of range. measurement outside of the predetermined
range. The XCell processor module
automatically resets the ACI card when this
occurs and corrects the problem. The
message is of significance only if it occurs
very frequently. Check the eXpert
configuration.
ACU - 002 Operating System error. Re-boot the XCell processor module. If the
message persists, carefully note the
conditions under which the message occurred
and consult your system supplier or equipment
vendor.
ACU - 003 There is an error in the configuration Examine the configuration carefully in eXpert,
downloaded to the XCell processor module. make changes as required, re-compile and
download the configuration again.
Page 157

ACU - 013 Bad channel configured for an accumulator Ensure that the correct card type (HSC or DI)
(HSC) or Digital Input (DI) module. exists in the rack and that the channel number
selected in eXpert exists and is operational.
ACU - 019 The XCell unit has experienced an operating Note the operational conditions under which
system fault. the message occurs and contact your system
supplier or equipment vendor.
download the configuration again. If the
vendor.
download the configuration again. If the
vendor.
ACU - 026 Accumulator Channel already configured Check the channels configured for SDI’s and
DDI’s, as an overlap exists between these
records and the configured Accumulator
Records.
Page 158
Version 1.06

AIP - 002 Invalid host Analogue Input configuration data Ensure that all Host Analogue Input Points are
or I/O hardware failure. configured with correct Analogue Input
channel numbers. Check using the Show
Hardware Configuration function on the front
panel menu that the correct I/O configuration is
displayed. Ensure all Analogue Input Cards are
correctly installed in the XCell processor
module. Ensure the XCell processor module
card is correctly installed in the backplane.
See The XCell User Manual for further
information.
AIP - 004 Invalid host Analogue Input configuration Ensure the host configuration for all Analogue
data. Input points is correct.
AIP - 006 Invalid host Analogue Input configuration Ensure that all Host Analogue Input Points are
data. configured with correct Analogue Input
information.
AIP - 007 Invalid host Analogue Input configuration Ensure that all Host Analogue Input Points are
data. configured with correct Analogue Input
information.
Page 159

AO - 016 Invalid host output configuration data or Ensure that all Host Analogue Output Points
general Input / Output hardware failure. are configured with correct Analogue Input
displayed. Ensure all Analogue Output Cards
are correctly installed in the XCell processor
information.
AO - 024 General Input / Output hardware failure. Ensure that all Host Analogue Output Points
are configured with correct Analogue Output
information.
AO - 028 Invalid host output configuration data or Ensure that all Host Analogue Output Points
general Input / Output Hardware failure. are configured with correct Analogue Output
information.
Page 160
Version 1.06

AOI - 001 The XCell unit is reporting a general Input / Check that the Show Hardware Configuration
Output hardware failure. menu item, activated using the front panel
function button, displays the correct I/O
configuration. Ensure that all Analogue Output
Cards are correctly installed in the XCell
processor module. Ensure that the XCell
processor module card correctly installed in
the backplane.
AOI - 003 The XCell unit is reporting a general Input / Check that the Show Hardware Configuration
Output hardware failure. menu item, activated using the front panel
configuration. Ensure that all Analogue Output
Cards are correctly installed in the XCell
processor module. Ensure that the XCell
the backplane.
AOI - 006 The XCell processor module reports an Ensure that all host Analogue Output Points
invalid host output configuration data or I/O are configured with correct Analogue Output
hardware failure. channel numbers. Check using the Show
information.
AOP - 004 The XCell processor module reports invalid Ensure host Configuration for all Analogue
host Analogue Output configuration data. Output Points is correct. Examine the
configuration carefully in eXpert, make
changes as required, re-compile and
AOP - 005 The XCell processor module reports invalid Ensure all host Analogue Output Points are
host Analogue Output configuration data. configured with valid conversion types.
Page 161

BAI - 015 Different Point Types are trying to chain to Check the eXpert Configuration for conflicts in
the same record. the assignment of Channel Numbers.
bCD - 003 Invalid software installed. Contact your system supplier or equipment
vendor.
bCD - 004 The XCell processor unit reports insufficient Ensure that the processor module has
memory available for the task being sufficient RAM installed to carry out the
performed. required tasks. Install additional RAM if
required.
bCD - 013 Invalid eXpert configuration. Check channel assignments in eXpert.
bCD - 015 The XCell processor unit reports an internal Re-boot the XCell unit, if the message persists,
software error. note the operational conditions under which
the message occurs and contact your system
bCD - 020 The XCell processor module reports an Note the operational conditions under which
internal database error. the message occurs and contact your system
bCD - 023 The XCell processor unit reports an internal Note the operational conditions under which
database error. the message occurs and contact your system
bCD - 034 There is insufficient memory installed on the Ensure that the processor module has
XCell processor unit. sufficient RAM installed to carry out the
required tasks. Install additional RAM if
required. Note the operational conditions under
which the message occurs and contact your
system supplier or equipment vendor.
bCD - 042 General Input / Output hardware error. Check all Input or Output modules installed
adjacent to the XCell unit; also check the
eXpert configuration.
bCD - 046 Invalid eXpert configuration downloaded to Check the locations of all boards adjacent to
the XCell processor module. the XCell unit against the intended eXpert
configuration.
Page 162
Version 1.06

bCD - 049 The XCell processor unit reports an internal Note the operational conditions under which
database error. the message occurs and contact your system
bCD - 071 The Digital Input module channel numbers do Ensure that the hardware configuration has
not match the eXpert configuration been saved, ensure that the eXpert
downloaded to the XCell processor module. configuration matches the installed hardware.
bCD - 074 An eXpert configuration was not Download the eXpert configuration again.
downloaded properly.
bCD - 078 Internal database problem. Note the operational conditions under which
the message occurs and contact your system
bCD - 081 Invalid configuration. Ensure that the hardware configuration has
been saved, ensure that the eXpert
configuration matches the installed hardware.
bCD - 082 Error in downloaded configuration. Verify the eXpert configuration and download
it again.
bRA - 001 Insufficient memory or memory corruption. Ensure that all RAM jumpers on XCell
processor module card are correctly set.
Ensure all RAM chips are correctly installed on
the XCell processor module. Refer to the
XCell User Manual for more information on
jumper settings.
bRA - 002 Insufficient BRAM memory or invalid Ensure that all RAM jumpers on XCell
allocation size specified by an application. processor module card are correctly set.
Ensure all RAM chips are correctly installed on
the XCell processor module. Refer to the
XCell User Manual for more information on
jumper settings.
CFG - 002 An operation has been attempted for an I/O Check that the target I/O card is recognised
channel not defined in a configuration, or the and is saved in the hardware configuration.
configuration has not been saved.
Page 163

CFG - 006 The XCell processor module reports a Check communications links. Restart eXpert
communications failure or an XCell processor configuration download.
module reset.
CFG - 007 The XCell processor module reports a Check the communications link. Reset the XCell
communications failure, the previous processor module and redo the eXpert
configuration did not terminate properly. configuration download.
CFG - 008 Configuration download in progress from Ensure no other host systems are
another host system. downloading.
CFG - 009 The XCell processor module has detected a Ensure that the version of the eXpert database
mismatch between the eXpert database field is compatible with the version of software
size and the XCell field size. running on the XCell unit.
CFG - 014 Database access is denied, database ‘in Reset the database lock. Wait approximately
use’ lock is set. Probably due to failure of a one minute for the previous download to
previous configuration download. session to time-out on the target XCell
processor module then download the
configuration again. If the problem recurs,
reset the XCell processor module.
CFG - 019 Unable to allocate memory. Verify that the downloaded configuration is as
expected.
Check RAM jumpers on XCell processor
module card correctly set. Ensure RAM chips
correctly installed. Possible network instability,
refer to the section on network
troubleshooting in this document.
CFG - 020 General configuration information message. Explanation depends upon the specific
configuration being attempted. Check the
configuration in eXpert.
CFG - 027 Unable to run software in EPROM. Check that Named Block is in memory. Ensure
download failed because the XCell processor it makes cold, warm and hot initialisations. Wait
module had not terminated the previous for approximately one minute to allow the
configuration session. previous download session to timeout on the
target XCell processor module and try to
Page 164
Version 1.06

CFG - 069 The eXpert configuration is not matching the Check eXpert configuration against physical
physical I/O (i.e. too many records). output.
CGC – 111 An inconsistency was discovered with some Clear BRAM and redownload configuration.
configuration data and any outputs in this unit
will be disabled..
CGC – 112 The number of configuration tables (Static Contact Microsol.
Groups) has exceeded the allowed maximum
COU - 042 A bad frame was received from a KBUS Check if the KBUS device is functioning
device. The data will be re-requested. correctly and is correctly connected on the
communications line. Check the terminating
resistors and the cable shielding.
COU – 045 The wrong conversion function is defined in Review the conversion functions against the
the KBUS Map Table for a piece of data just data being polled. Verify the data type of each
received from a device. cell returned from the specific KBUS devices.
COU – 100 A KBUS device has been marked Offline. Check if the KBUS device is functioning
correctly and is correctly connected on the
communications line. Check the terminating
resistors and the cable shielding.
DB - 016 Time-out during access to a particular group Decrease the load on the XCell unit by
in the database by multiple applications. spreading the points over large scan periods
or by reducing the number of points
processed. Increase the applications time-outs
for database access.
DD - 011 A general message indicating that the Of itself this message is not indicative of a
processor has difficulty processing a specific problem. However, the message
received message. immediately before or after this message
should be noted and normally provides the
exact explanation.
DD - 015 The XCell processor module reports Check that all RAM jumpers on the XCell
insufficient memory. processor module card are correctly set.
Ensure all RAM chips are correctly installed.
Refer to the XCell User Manual for further
DD - 030 Database locking during configuration. Reduce the number of points configured in a
single download.
Page 165

DDI - 016 Not able to create required fields for DDI Note the operational conditions under which
Group. the message occurs and contact your system
DDI - 028 A digital input channel or channels, used in Ensure the channel numbers used in the DDI
the Double Digital Input point type configuration are correct. Check that the digital
configuration, does not exist. input card is recognised and is saved in the
hardware configuration.
DDI - 041 The channel or record specified in the Check the eXpert configuration against the
configuration does not exist. installed hardware; replace any removed or
failed card.
DI - 007 General Input / Output hardware failure. Check that the Show Hardware Configuration
menu item, activated using the front panel
configuration. Ensure that all Digital Input Cards
module. Ensure that the XCell processor
module card correctly installed in the
backplane.
DI – 018 General Input / Output hardware failure. Check that the Show Hardware Configuration
configuration. Ensure that all High Density
Digital Input Cards are correctly installed in the
XCell processor module. Ensure that the XCell
the backplane.
DIP – 004 The XCell processor module reports an Ensure the host eXpert configuration is correct
invalid host Digital Input configuration. for all Digital Input points. Ensure that all host
Digital Input points are configured with correct
Digital Input channel numbers.
Page 166
Version 1.06

invalid host Digital Input configuration or for all Digital Input points. Check that the Show
general Input / Output hardware failure. Hardware Configuration menu item, activated
using the front panel function button, displays
the correct I/O configuration. Ensure that all
High Density Digital Input Cards are correctly
installed in the XCell processor module. Ensure
that the XCell processor module card correctly
installed in the backplane
Digital Input points are configured with
different Digital Input channel numbers.
DNT – 064 The XCell processor module is reporting a This message is normally seen soon after a
transitional network message. unit has been powered ON / OFF and can
usually be ignored. Allow the network to
stabilise for one minute after adding or
removing a unit.
removing a unit.
Page 167

removing a unit.
DOP – 004 Invalid host Digital Output configuration data. Ensure that the host eXpert configuration for
all Digital Output points is correct.
HAI – 002 General Input / Output hardware failure. Check that the Show Hardware Configuration
backplane.
backplane.
backplane.
Page 168
Version 1.06

HAI – 017 Faulty analogue channel. Faulty channel(s) may be identified from close
inspection of the front panel LED array. Ensure
all Analogue Input cards are correctly installed
in the XCell processor module. Ensure that the
XCell processor module card is correctly
installed in the backplane.
HDO – 002 The XCell processor module reports that it is Ensure that the Digital Output (HDO) card is
unable to power a Digital Output channel. correctly powered ON.
HDO – 005 The XCell unit is attempting to drive more than Ensure that the 2-up inhibit jumper on the
one Digital Output at the same time. Digital Output (HDO) card is set.
HDO – 070 The XCell is trying to send a zero value pulse Check the eXpert configuration is correct for
command i.e. trying to switch off a pulsed Digital Outputs; this message is usually just a
Digital Output. warning.
HDO – 073 The outputs have been disabled on this XCell Clear BRAM and redownload configuration.
because the periodic configuration validation
detected an inconsistency with some
configuration data..
IDI – 015 HDI card has failed. Replace or check the HDI module.
IDI – 025 The number of Digital Input signals received Do not connect or disconnect a SIM test box to
exceeds the capacity of the interrupt buffer. or from a live card.
This message can occur if a Microsol SIM Should this message occur in other
test box is disconnected and reconnected to circumstances please note the operational
a live card, generating spurious signals. conditions and contact your system supplier or
equipment vendor.
IE2 – 001 The XCell reports a difficulty in writing to its Check that the correct serial cable is being
serial port. used. Ensure that all relevant jumpers are set
correctly. Ensure that the correct serial port
settings have been included in the
downloaded eXpert configuration.
Page 169

IE2 – 002 The XCell reports a difficulty in reading Check that the correct serial cable is being
from its serial port. used. Ensure that all relevant jumpers are set
correctly. Ensure that the correct serial port
settings have been included in the
downloaded eXpert configuration.
IEC – 001 Hardware failure or insufficient memory. Ensure that all RAM chips correctly inserted.
Check that the memory expansion card is
correctly installed. Ensure that a correct
version of IEC firmware is installed..
IEC – 002 Hardware failure or port configuration Ensure RAM chips correctly inserted. Ensure
problem. port is not being used by another protocol.
IEC – 010 Incorrect firmware installed on the XCell Ensure correct versions of IEC and BASE are
processor module board. installed.
processor module board. Incorrect version of installed. Ensure correct version of eXpert.
eXpert.
IEC – 040 Hardware failure or insufficient memory. Ensure that all RAM chips correctly inserted.
Check that the memory expansion card is
correctly installed. Ensure that a correct
version of IEC and BASE firmware is installed.
IEC – 041 Unrecognised message type received from Ensure correct versions of IEC and BASE are
the Master Station. installed in the XCell processor module. Check
the IEC message type byte in the frame sent
by IEC.
Page 170
Version 1.06

IEC – 042 Internal software failure; error on writing to a Ensure correct versions of IEC and BASE
time buffer. General hardware failure. firmware are installed on the XCell processor
module board. Ensure a memory expansion
board is installed on the XCell processor unit
board.
IEC – 043 Error on reading from the internal time buffer, Ensure that correct versions of IEC and BASE
or general hardware failure. firmware are installed on the XCell processor
module card. Ensure that the memory
expansion card is installed.
IEC - 044 Error while processing internal IEC 870-5 Ensure correct versions of IEC and BASE are
protocol messages. Possible configuration installed on the XCell processor module board.
problem with the downloaded MAP table. Ensure a memory expansion card is installed.
Ensure that a correct configuration is
downloaded from eXpert.
IEC - 045 Error while accessing XCell database. Ensure correct versions of IEC and BASE are
Possible configuration problem with the installed. Ensure memory expansion card is
downloaded MAP table. installed. Ensure correct configuration is
downloaded from eXpert.
IEC - 046 Internal software problem. One of the This is a valid operational situation. Ensure that
following buffers has overflowed; Class 1 the host does not issue multiple simultaneous
buffer, Class 2 buffer or Command Response commands. Ensure a memory expansion card
buffer. is installed.
IEC – 047 Invalid protocol MAP table configuration. Ensure a valid eXpert protocol configuration
Attempt to access a non-existing IOA. was downloaded to the XCell unit. Ensure that
a memory expansion card is installed. In the
case of a General Interrogation or Counter
Interrogation command, ensure that the IOA is
zero.
IEC – 048 Attempt to perform a Single command failed. Ensure a valid protocol configuration was
downloaded to the XCell. Verify the host
database.
IEC – 049 The requested operation is neither a SELECT, Ensure a correct version of IEC firmware is
EXECUTE or BREAK. installed. Check the single command sent from
the master station.
Page 171

IEC – 050 Attempt to perform a Single command failed. Ensure a valid protocol configuration was
downloaded to the cell. Verify that the cell
containing the outputs has been correctly
configured. Ensure a correct version of IEC
firmware is installed. Check the single
command sent from the master station.
IEC – 051 The requested operation is neither a SELECT, Ensure a valid eXpert protocol configuration
EXECUTE or BREAK. was downloaded to the XCell processor unit.
Verify that the XCell containing the outputs has
been configured correctly. Ensure a correct
version of IEC firmware is installed. Check the
double command sent from the master station.
IEC – 052 Attempt to perform a Double command failed. Ensure a valid eXpert protocol configuration
was downloaded to the XCell processor unit.
double command sent from the master station.
IEC – 053 Attempt to perform a regulating step Ensure a valid eXpert protocol configuration
command failed. was downloaded to the XCell processor unit.
regulating step command sent from the master
station.
IEC – 054 Attempt to perform a regulating step Ensure a valid eXpert protocol configuration
command failed. was downloaded to the XCell processor unit.
regulating step command sent from the master
station.
Page 172
Version 1.06

IEC – 055 Attempt to perform a Set Point command Ensure a valid eXpert protocol configuration
failed. was downloaded to the XCell processor unit.
Set Point command sent from the master
station.
IEC – 056 Failure when constructing a reply to a Ensure that correct versions of IEC and BASE
command message. Insufficient memory for a firmware are installed in the XCell. Ensure a
reply. memory expansion card is installed.
IEC – 057 Problem encountered when processing Ensure a valid protocol configuration was
Counter Request. Either the COT or the VSQ downloaded to the cell. Check the interrogation
in the received frame is incorrect (i.e. not in command issued by the master station.
accordance with the IEC specifications).
IEC – 058 Error encountered when processing the QOI Ensure a valid protocol configuration was
parameter in a received message. downloaded to the cell. Check the interrogation
command issued by the master station.
IEC – 059 Error encountered when processing the Ensure a valid protocol configuration was
Parameter Loading command. downloaded to the cell. Check the measured
value issued by the master station.
IEC – 060 Error encountered when accessing Ensure a valid protocol configuration was
database. downloaded to the cell. Ensure a correct
version of IEC is installed in the XCell unit.
IEC – 061 Error encountered when processing time Ensure a valid protocol configuration was
functions within the IEC protocol. downloaded to the cell. Ensure correct
versions of IEC 870-5 protocol firmware is
installed in the XCell unit.
IEC – 062 Change message received is not a FULL- Ensure a valid protocol configuration was
UPDATE or a Normal Change message. downloaded to the XCell. Ensure correct
versions of IEC 870-5 protocol firmware is
installed in the XCell unit.
Page 173

IEC – 063 Unable to determine the Online / Offline status Ensure a correct version of IEC firmware is
of another unit. installed. Ensure that a memory expansion
card is installed.
IEC – 064 Error encountered when processing protocol Ensure a valid protocol configuration was
database, following a cell failure on the local downloaded to the cell. Ensure correct
network. IEC cannot pack unit status events. versions of IEC 870-5 protocol firmware.
Check the unit operational status. Check
network.
IEC – 065 Error encountered when constructing a 7- Ensure a correct version of IEC firmware is
byte time-stamp. installed. Ensure that a memory expansion
card is installed.
IEC – 066 Error encountered processing SELECT Ensure a valid protocol configuration was
operation for a Set Point command. downloaded to the cell. Ensure correct
versions of IEC 870-5 protocol firmware are
installed in the XCell processor unit.
IEC – 067 Error encountered processing EXECUTE Ensure a valid protocol configuration was
operation for a Set Point command. possible downloaded to the cell. Ensure correct
error in the eXpert configuration. versions of IEC 870-5 protocol firmware.
IEC – 068 Error encountered processing BREAK Ensure a valid protocol configuration was
operation for a Set Point command. downloaded to the cell. Ensure correct
versions of IEC 870-5 protocol firmware.
IEC – 069 Error encountered trying to select a single Ensure a valid protocol configuration was
t w o-stage output when another two-stage downloaded to the cell (only one active two /
output on the same card is already active. three-stage output may be selected per card.
This message is also encountered when A select should not be sent to a single-stage
trying to select a single two-stage output command. Enter the commands in the correct
when that output is already selected. sequence).
Also occurs if a select is sent to a single Ensure correct versions of IEC 870-5 protocol
stage output. firmware.
IEC – 070 An XCell unit containing a Digital Output card Ensure the target XCell unit is on-line.
has gone off-line.
operation for a Single command. downloaded to the cell. Ensure correct
versions of IEC 870-5 protocol firmware.
Page 174
Version 1.06

IEC – 072 Error encountered processing SELECT Ensure a valid protocol configuration was
operation for a Double command. downloaded to the cell. Ensure a correct
version of IEC 870-5 protocol firmware is
installed in the XCell.
IEC – 073 Error encountered processing EXECUTE Ensure a valid protocol configuration was
installed in the XCell processor unit.
installed in the XCell.
IEC – 075 Error encountered when processing Counter Ensure a valid protocol configuration was
Interrogation command. downloaded to the cell. Ensure a correct
installed in the XCell processor module.
IEC – 076 Bad internal data type. Contact your system supplier or equipment
vendor.
IEC – 077 The XCell unit is reporting an internal data Note the operational conditions under which
type error. the message was displayed and contact your
IEC – 080 Error encountered when formatting Ensure correct versions of IEC 870-5 protocol
messages for transmission to host. firmware. Check for Hardware failure. Ensure
the memory expansion card is correctly
installed.
IEC – 084 Invalid regulation step command. Check input message parameters.
IEC – 100 Error encountered when attempting to Ensure correct versions of IEC 870-5 protocol
allocate memory. firmware. Check for Hardware failure. Ensure
memory expansion card is correctly installed.
Page 175

IEC – 101 Error encountered when attempting to free Ensure that correct versions of IEC 870-5
memory. protocol firmware are installed. Check for
hardware failure. Ensure the memory
expansion card is correctly installed.
IEC – 102 The XCell processor module is reporting a Check that the IEC Map table in the eXpert
Point Type problem during a general configuration has been completed properly.
integration.
IEC – 103 An error has been encountered when Note the operational conditions under which
packing events. the message was displayed and contact your
IEC – 104 A bad event buffer class was encountered Note the operational conditions under which
in the IEC firmware. the message was displayed and contact your
IEC – 105 Error encountered when a large number of The RTU should be polled to empty the buffers
events are generated and polling of the RTU
has not taken place. If more events are
generated without polling the oldest events
are deleted one by one to make room for the
newest events. A background scan will
occur after polling is resumed to restore the
correct status of all deleted events.
IEC – 110 The IEC clock has drifted since the last time Check IECGEN table in the eXpert configuration
synchronisation. Host did not send Time Sync for expected time period. Send a time
message within expected time period. synchronisation command to the unit.
IEC – 199 Error encountered when continuous In order for more commands to be accepted by
commands sent to the RTU and no polling for the RTU polling of the RTU needs to occur
responses takes place. The command continuously. This polling will retrieve previous
response buffer has overfilled. command responses and keep the buffer from
getting filled.
IEC – 200 High-priority output message buffer RTU polling should occur more frequently to
overflow. Ususlly occurs when multiple retrieve previous command responses and
digital output drives are sent but the RTU is keep the buffer from getting filled.
not polled for responses
Page 176
Version 1.06

IEC – 213 Not enough space for file download. The file system size can be specified in the
IECGEN table. Increase the file system size
parameter to match the actual requirement.
IEC – 217 Internal file system error. Check that PMR is mapped in IECFIL.
IEC – 219 Sequencing error during an IEC file transfer. Usually no action required. The transfer
mechanism recovers. If the problem persists,
note the operational conditions under which
the message was displayed and contact your
system supplier or equipment vendor
IEC – 221 File transmission error, or incorrect Check connections and try again. Check and,
configuration file or file number generated. if necessary, change the configuration file
number in IECFIL.
IEC – 223 Unable to overwrite a file because the file is Information message.
ready for upload.
IEC – 225 Bad redundancy, Configuration Unit Number. Check unit number in the eXpert configuration.
Note the operational conditions under which
IEC – 227 Error encountered when returning time Note the operational conditions under which
buffer. the message was displayed and contact your
IEC – 235 Error getting Sequence Of Events (SOE) time Upload the Sequence Of Events (SOE) file;
buffer, i.e there is no partition space left to though the contents may be lost. Note the
make a Sequence Of Events (SOE) time operational conditions under which the
entry. message was displayed and contact your
IEC – 247 Error in version number for PMR in IEC. Note the operational conditions under which
IEI – 132 Received an IOA that is not in the Master Map Check the Master and Slave IEC Map Tables.
Table and therefore cannot be processed.
Page 177

IEI – 152 Received only part of the response message Generally caused when disconnecting
to a Class 1 Poll. communications or with noisy communications.
Check the communication links.
IEI – 153 Received only part of the response message Generally caused when disconnecting
to a Class 2 Poll. communications or with noisy communications.
Check the communication links.
NET – 020 Insufficient memory. Check that all RAM jumpers on the XCell
Ensure an expanded memory board is installed
on the XCell processor card.
NET – 021 Internal software problem. Bad pointer to Check that all RAM jumpers on the XCell
data area or corrupt local data storage. processor module card are correctly set.
Ensure that correct versions of PROMs are
installed.
NET – 039 Internal software error. There are no more Possible network instability. Refer to the
Net-PB buffers available in the NPBP partition. section on network troubleshooting in this
This is a fatal error. A system limit has been document.
reached or there is incorrect operation of the
network, leading to a bottleneck.
NET- 085 Internal memory allocation problem Check that all RAM jumpers on XCell processor
module card are correctly set. Ensure that all
RAM chips correctly installed on the circuit
board. Ensure an expanded memory board is
installed on the XCell processor card.
NET- 087 Internal software error. The network layer is Ensure all expected XCell processor modules
attempting to transmit a message with either are online and operational. Check for possible
of the following conditions present: network instabilities.
• The address of the destination unit is the
local unit.
• The destination unit does not exist in the
Route Table.
Page 178
Version 1.06

NET – 089 Internal software error. The network layer is Ensure all expected XCell processor modules
attempting to process a datagram (received are online and operational. Check for possible
from a datalink layer and the destination network instabilities.
address does not exist in the Route Table.
NET – 095 The XCell processor reports insufficient Check that all RAM jumpers on XCell processor
internal memory. module card are correctly set. Ensure that all
NET – 152 Internal memory allocation problem. Check that all RAM jumpers on XCell processor
module card are correctly set. Ensure that all
NET - 184 Detected the loss of a number of messages Check the network connections and
on FieldNet network and initiating message terminations and unit addressing conflicts.
recovery Check the online LED and list of Online Units
(OLU) on the frfont panel.
Page 179

NET – 187 Internal XCell software problem. In attempting Check that all RAM jumpers on XCell processor
to transmit the highest priority buffered module card are correctly set. Ensure that all
message, an error occurred. This high level RAM chips correctly installed on the circuit
error may mask out lower level errors. board. Possible network instability, refer to the
section on network troubleshooting in this
document.
NET – 189 Internal XCell software problem. Datalink Check that all RAM jumpers on XCell processor
transmit task failed some initialisation. module card are correctly set. Ensure that all
board. Possible network instability, refer to the
document.
NET – 201 Excessive system load. Decrease the load on the XCell processor unit
by spreading points over large scan periods or
by reducing the number of points processed.
Possible network instability, refer to the
document.
NET – 225 Excessive system load. Decrease the load on the XCell processor unit
by spreading points over large scan periods or
by reducing the number of points processed.
Possible network instability, refer to the
document.
NET – 255 Message reserved for reporting errors in Debug code operating in the system software.
debug code. Note the operational conditions under which
PTE – 010 Invalid Host Output configuration data. Ensure that instrument limits for all host
Analogue Points using square root conversion
are correctly configured.
RAI – 003 Unsupported operation on analogue inputs. Check all I/O mapping in the RTU’s protocol
This may be due to an attempt to drive an interfaces to the MMI for analogue inputs
analogue input mapped as outputs.
.
Page 180
Version 1.06

RAI – 009 The XCell processor module is reporting a Check that the Show Hardware Configuration
general Input / Output hardware failure. function on front panel menu displays the
correct Input / Output configuration. Ensure
that all Input / Output Cards are correctly
installed in the rack adjacent to the XCell
processor module. Refer to the XCell User
RAI – 013 The XCell processor module is reporting a Check that the Show Hardware Configuration
general Input / Output hardware failure. function on the front panel menu displays the
RDI – 007 The XCell processor module is reporting a Check that the Show Hardware Configuration
RDI – 011 The XCell processor module is reporting a Check that the Show Hardware Configuration
RDI – 024 Internal XCell software problem; bad GSR Illegal action performed on an input; check the
call. eXpert configuration for inconsistencies.
RDI – 039 Digital input transitions have occurred which This is a valid operational condition but it is
are less than the debounce time. notified to the operator in case there is some
underlying problem with the input that needs to
be addressed.
Page 181

RDO – 002 Invalid host output configuration data or a Ensure all Host Output Points are configured
general Input / Output hardware failure. with the correct output channel numbers.
Check that Show Hardware Configuration
function on the front panel menu displays the
that all Digital Output Cards are correctly
processor module. Ensure the XCell processor
module card is correctly installed in the
backplane.
RDO – 020 Attempting to drive the channel incorrectly. A Check configuration to see if a channel is
bad response to the ACTIVATE command configured as 3 stage. Check that Show
was received. Hardware Configuration function on the front
panel menu displays the correct Input / Output
configuration. Ensure that all Digital Output
Cards are correctly installed in the rack
adjacent to the XCell processor module.
RDO – 021 Attempting to drive the channel incorrectly. A Check configuration to see if channel is
bad response to the REQUEST command configured as 3 stage. Check that Show
was received. Hardware Configuration function on the front
panel menu displays the correct Input / Output
configuration. Ensure that all Digital Output
Cards are correctly installed in the rack
adjacent to the XCell processor module.
RDO – 022 Attempting to drive a three-stage output with Check the DOT configuration to see if the
a single stage command channel configuration matches the issued
Or drive command.
A problem driving an output with a pulse
command
RDO – 027 Attempting to drive a channel for which there Check the DOT configuration and determine if
is no DOT configuration. the channel is configured, if not, configure the
channel.
RDO – 034 Attempting to drive a second 3-stage output Wait until the first output pulses OFF (if it is
when a 3-stage output is already activated in configured as pulse) or drive it OFF (if it is
the XCell processor unit. configured as steady) before driving the
second output ON.
Page 182
Version 1.06

RDO – 046 The XCell processor module reports an Note the operational conditions under which
internal database error. the message was displayed and contact your
RDO – 052 If the Enable signal is not in the correct state, Check that the Enable signal is in the correct
this error will occur when trying to drive the state before driving the corresponding output.
corresponding output.
RDO – 053 Attempting to drive an output as a single Ensure output is configured to the mode in
stage output when the output is configured which it will be driven. Check the DOT
as a three-stage output. configuration to determine if the channel is
configured as a 3 stage. If so, configure it as a
single stage channel.
RHS – 001 Invalid Configuration for HSC Point Type. Note the operational conditions under which
RHS – 002 Invalid Configuration for HSC Point Type. Note the operational conditions under which
RHS – 003 Incorrect software versions. Note the operational conditions under which
RHS – 004 Hardware I/O error. Note the operational conditions under which
RHS – 005 Hardware I/O error or memory failure. Note the operational conditions under which
RHS – 006 Insufficient memory. Note the operational conditions under which
Page 183

RHS – 007 System limit reached. Note the operational conditions under which
RHS – 010 General Input / Output hardware fault, failure Check that Show Hardware Configuration
to read a channel count. function on the front panel menu shows that a
HSC card is present. Ensure that all jumpers
are set for the correct slot position and that
the XCell processor module card is correctly
installed in the backplane.
RHS – 013 Internal software problem. Note the operational conditions under which
RHS– 014 Internal software problem. Note the operational conditions under which
Page 184
Version 1.06

RP5 – 001 Error encountered while trying to free Ensure that PROMS containing the correct
memory. version of RP570 protocol software are
installed. Check for general hardware failure.
If present, ensure that the memory expansion
card is fitted correctly.
RP5 – 008 Error encountered while trying to free Ensure that PROMS containing the correct
memory. version of RP570 protocol software are
installed. Check for general hardware failure.
If present, ensure that the memory expansion
card is fitted correctly.
RP5 – 009 Invalid protocol map table configuration table. Ensure that a valid eXpert protocol
Attempting to access a non existing object configuration was downloaded to the XCell
number. processor module. If present, ensure that the
memory expansion card is fitted correctly.
RP5 – 011 Invalid protocol map table configuration table. Ensure that a valid eXpert protocol
Attempting to access a non-existing or invalid configuration was downloaded to the XCell
UGFR. processor module. If present, ensure that the
RP5 – 012 Internal Software problem. Contact the system supplier or equipment
vendor.
RP5 – 013 Error encountered while trying to send a 1- If the selected output is not on a local XCell
stage drive command. unit, make sure the XCell unit with the selected
output Is powered ON and on-line. Otherwise
contact the system supplier or equipment
vendor.
RP5 – 015 Internal Software problem. Contact the system supplier or equipment
vendor.
RP5 – 016 Error encountered while processing a host Check that the frame sent by the host us a
command. valid RP570
Page 185

RP5 – 020 Error encountered while accessing the XCell Ensure that a valid eXpert protocol
database. Potential configuration problem configuration was downloaded to the XCell
involving the downloaded map table. processor module. Ensure that the memory
expansion card is fitted correctly.
RP5 – 021 Error encountered while accessing the XCell Ensure that correct versions of firmware are
database. installed. Ensure that a valid eXpert protocol
configuration was downloaded to the XCell
processor module. If present, ensure that the
RP5 – 022 Internal software problem. Contact the system supplier or equipment
vendor.
RP5 – 023 Device read error. Ensure that the communication parameters in
the general protocol configuration table and
the master/Host are the same, e.g. parity, baud
rate, stop and start bits etc.
RP5 – 024 Invalid protocol general configuration. Ensure that a valid eXpert protocol
configuration was downloaded to the XCell
processor module. If correct, contact the
vendor.
RP5 – 030 An incorrect range may be specified for a Check the range specified for each data type
data-type in the protocol map table or an in the protocol map table.
invalid protocol map table exists.
RP5 – 035 Invalid protocol map table for counters. Ensure that a valid eXpert protocol
configuration for counters is downloaded to
RP5 – 036 Invalid protocol map table for digital data Ensure that a valid eXpert protocol
types. configuration for digital data types is
downloaded to the XCell processor module.
Page 186
Version 1.06

RP5 – 037 Invalid protocol map table for analogue data Ensure that a valid eXpert protocol
types. configuration for analogue data types is
downloaded to the XCell processor module.
vendor.
vendor.
vendor.
SDI – 042 The message indicates that a channel record 1. A configuration for an SDI has been
is missing. This can be triggered by many downloaded but the corresponding
conditions. These are some of them: channel is faulty or the card is missing.
2. An attempt is being made to configure the

same channel as both an SDI and a DDI.
3. Too many interrupts (digital input

changes) are being generated, usually by
test equipment such as the SIM 010 box.
This causes the channel to be marked
bad. Other error messages would be
displayed to support this explanation.
This error is usually only seen when testing a

system in house or when commissioning a
new system. It is not expected to be observed
in a system that is fully operational.
SIO – 011 Insufficient memory. Note the operational conditions under which
Page 187

SIO – 019 Excessive load on the XCell processor Decrease the load on the XCell unit by
module. spreading points over large scan periods or by
reducing the number of points being
processed. Decrease amount of I/O in the unit.
If the problem persists note the operational
conditions under which the message was
displayed and contact your system supplier or
equipment vendor.
SPT – 028 Insufficient memory. Check that the RAM jumpers on the XCell
Ensure RAM chips are correctly installed.
SPT – 034 Excessive system load. Decrease the load on the XCell unit by
spreading points over large scan periods or by
reducing the number of points being
processed. Decrease amount of I/O in the unit.
If the problem persists note the operational
equipment vendor.
SYS – 036 Insufficient memory. Check that the RAM jumpers on the XCell
Ensure RAM chips are correctly installed.
SYS – 064 Insufficient memory. Note the operational conditions under which
SYS – 065 Attempting to release unallocated memory. Note the operational conditions under which
TCP – 022 The IPE-101 card is not present or not Restart the unit ensuring that the IPE 010 is
powered on. powered up at the same time or before the
XCel processor module.
TCP – 039 Unable to obtain semaphore within the time When this occurs the system already has a
period allocated, problem in the driver; the code is not
functioning correctly.
Page 188
Version 1.06

TCP – 040 Unable to release a semaphore after use. Restart the XCell unit. Note the operational
equipment vendor. Error 39 will follow this
error normally.
TCP – 041 It is not possible top bind an address to a System should self-recover from this error.
socket which has been created. Otherwise reboot the system.
TCP – 042 No space available to create a new socket This system only allows the user to open a
parameter block. certain number of sockets. If this number is
exceeded this message is given. To avoid this
problem, close some of the opened sockets.
TCP – 043 No space available for socket transmit and This error causes the system to reboot since
receive buffers the system cannot find any available space to
copy messages through the stack layers. This
may be due to incorrect closing of a previously
opened socket.
TCP – 044 Initialisation of pNA+ has failed Internal pSOS problem. Will only occur on start
up.
Reboot the system, if problem persists note
the operational conditions under which the
message was displayed and contact your
TCP – 047 Unable to create Read Ahead Buffer for use There is no space available in the HEAP or it is
w ith a newly created socket. too fragmented to create a RAB. Install more
RAM on the XCell processor module; a
temporary solution is to restart the system.
TCP – 048 Unable to create mirror buffer for Ethernet There is no space available in the HEAP or the
card. HEAP is too fragmented to create an RAB.
Install more RAM on the XCell processor
module temporary solution is to restart the
system.
Page 189

TCP – 049 Unable to close the required socket. If this problem persists, a situation arises
where it is not possible to open a new socket
as all available socket areas are already in
use.
TCP – 050 Connection of host and local socket has Perhaps the host has abandoned the
failed. connection. The system should resolve this
problem.
TCP – 051 Cannot read characters from socket receive Memory allocation problems. May need to
buffer reboot system if the problem is not resolved
internally.
TCP – 052 Incorrect system start up or power was Reset the IPE - 010 card by switching power
removed from IPE - 010 temporarily supply off and on before restarting the
system.
TCP – 053 Cannot return memory to Heap after closing This will eventually cause problems with
socket. memory leakage.
Restart the system at the first available
opportunity.
TCP – 054 Non recoverable error in system In this situation the unit reboots due to memory
allocation problems within the system.
UIP – 016 XCell message timed out. An XCell processor Check that eXpert or eXplore are still running.
module timed out while waiting for a Ensure that the communications link between
response from eXpert or eXplore. the PC running eXpert and the XCell processor
module is secure and functioning.
UIP – 017 Destination XCell not responding. eXpert or Ensure the destination XCell’s unit address is
eXplore is attempting communication from one correctly configured in eXpert.
XCell processor module to another XCell
processor module which is not responding.
UIP – 018 Destination XCell is not found. eXpert or Ensure the destination XCell is on the network
eXplore is attempting communication from one and is powered ON and functioning.
XCell processor module to another XCell
processor module which cannot be seen on
the network.
Page 190
Version 1.06
Page 191
Document Number 404001-104
Issue Date: 25 August 2000

XCell Troubleshooting Manual

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

XCell Troubleshooting Manual

Uploaded by

Copyright:

Available Formats

TROUBLESHOOTING MANUAL

© Microsol Limited 2000

This document contains proprietary information of

The information in this document is subject to change

Microsol Contact Information

Phone: +353-1-415 3700

Fax: +353-1-671 6343

2. Direct Product Support and Assistance .............................................................3

3. Basic Definitions and Abbreviations..................................................................5

5. Reference Documentation ................................................................................9

6. Table of Potential Problems........................................................................... 11

EXPRESS FAULT FINDING GUIDE ....................................................................... 115

8. APPENDIX ONE ............................................................................................. 134

2. Direct Product Support and Assistance

Where an XCell product is installed under a support agreement with Microsol,

3. Basic Definitions and Abbreviations

Printers Printer User Documentation

Printer Server Printer server User Documentation

6. Table of Potential Problems

The Operator Workstation is powered ON but is not starting up properly. Page 21

Operator Workstation not running Vision application. Page 22

PC monitor problems Page 22

Printer not powered ON. Page 23

Printer not printing. Page 23

“Print Screen” software menu item in Vision is not responding. Page 24

Vision system stops and is unresponsive to all operator actions. Page 25

Unable to retrieve logged data. Page 26

Communications alarm is reported in the Alarm Log. Page 26

Incorrect analogue values displayed on the HMI. Page 31

Potential Problem Page

Multiple I/O Bad alarms reported in the Alarm Log. Page 37

Unable to drive an XCell output from Vision. Page 38

XCell I/O module failure is reported in the Alarm Log. Page 40

XCell processor module failure is reported in the Alarm Log. Page 41

Vision system reports fleeting alarms. Page 42

Cell processor module is repeatedly reported OK and then Failed. Page 42

Problem logging on to Vision, password rejected as invalid. Page 43

Password known to be correct however, access is denied. Page 43

Unable to access certain aspects of the Vision system. Page 43

XCell Fault Finding Guide

XCell processor module rebooting continuously. Page 54

Non-volatile memory fault. Page 56

Potential Problem Page

Accumulator Fault Finding Guide

Accumulator values not available in another XCell processor module. Page 63

Accumulator values are not received through a communications interface. Page 63

AC Analogue Input Fault Finding Guide

Inaccurate AC measurements. Page 68

Digital Input Fault Finding Guide

Raw Digital Input not received across a protocol interface. Page 73

I/O not transferred by the XCell protocol interface unit. Page 74

Analogue Output (AO) Fault Finding Guide

Unable to drive an Analogue Output from eXplore on another unit. Page 79

Unable to drive an Analogue Output through a protocol interface module. Page 79

Potential Problem Page

Unable to drive a Digital Output through a protocol interface. Page 84

Analogue Input (AI) Fault Finding Guide

Serial Communications Fault Finding Guide

Communication LEDs not illuminating as expected. Page 98

XCell appears to have lost its configuration data. Page 98

XCell FieldNet LAN Fault Finding Guide

Time Synchronisation Fault Finding Guide

Potential Problem Page

Sequence Of Events Fault Finding Guide