Maintainance Data Types

Error Description Type

Fast W'Dog Error 0

Battery Failure 1
BBRAM Failure 2
Field Volt Fail 3
Bus Reset Error 4
Slow W'Dog Error 5
SRAM Failure Bus 6
SRAM Failure Blk 7
FLASH Failure 8
Code Verify Fail 9
BBRAM Failure 10
Battery Failure 11
Field Volt Fail 12
EEPROM Failure 13
Software Failure 14
H/W Verify Fail 15
Non Standard 16
Ana. Sample Fail 17
NIC Soft Error 18
Set.Commit Error 19
PSL Commit Error 20
Curve Commit Err 21

Platform Code Verify Fail (Maint Type 9) Error Codes (As detected in P443, P445, P446, P540, P540D, P84

Error Code Decimal Negative Error Module Sub Code

0x0080xxxx Inmon.c
0x00800000
to
0x00807FFF Inmon.c
0x00809A80
to
0x00809FBF Inmon.c

0x00Cxxxxx Inmon.c
0x00C00000
to
0x00C6FFFF Inmon.c
0x00C70000
to
0x00C7FFFF Inmon.c
0x00C036BE 12596926 Inmon.c

0x00C036CE 12596942 Inmon.c

Platform Software Failure / Non Standard (Maint Type 14 / 16) Error Codes (As detected in P443, P540, P
Type 14 unless specified

Error Code Decimal Negative Error Module Sub Code

0x01040006 dbmnvm.c
0x0B230136 186843446
0x0B230163 186843491

0x0C010000

0x0C020000 Inmon.c

0x0C020022 201457698 Inmon.c

0x0C0200E0 Inmon.c

0x0C0200F0 Inmon.c

0x0C030000

0x0C040000

0x0C050000
0x0C060000

0x0C070000

0x0C080000

0x0C090000

0x0C0A0000

0x0C0B0000

0x0C0C0000

0x0C0D0000 202178560

0x0C0DDB15 202234645 Inmon - Acquisition 219 (dec)

0x0C0DDB1C 202234652 Inmon - Acquisition 219 (dec)

0x0C0E0000 202244096
0x0C0ED919 202299673 Inmon - Acquisition 217 (dec)

0x0C0F0000

0x0C100000 202375168

0x0C100000

0x0C110000

0x0C120000

0x0C130000

0x0C140001 202637313

0x0C140002 202637314
0x0C140003 202637315

0x0C140004 202637316

0x0C140005 202637317

0x0C140006 202637318

0x0C140007 202637319

0x0C140008 202637320

0x0C140009 202637321

0x0C14000A 202637322

0x0C150000

0x0C160010 202768400

0x0C160011 202768401

0x0C160012 202768402

0x0C160013 202768403

0x0C160014 202768404

0x0C160015 202768405

0x0C1600A0 202768544

0x0C1600B0 202768560
0x0C1600C0 202768576

0x0C1600D0 202768592

0x0C170016 202833942

0x0C170017 202833943

0x0C170018 202833944

0x0C170019 202833945

0x0C17001A

0x0C180000 inmon.c
0x0C18xxxx
(where xxxx
is not 0000) inmon.c

0x0C190000

0x0C1A0000

0x0C1C0000

0x0C1E0000

0x0C220028 inmon.c

0x0C250028 inmon.c
0x0D080AE7 msf.c
0x0E020000 235012096
0x0E080000 235405312
0x0F010A16
(Type 16)

0x13240000 321126400

0x1905012d 419758381

0x190A0162 419758381

0x1C1200F5 470941941

0x1C1200F6 470941942

0x2D080215

0x351F03F5

0x352Dxxxx (e.g. 0x352D0411)

0x35350000
(Type 16)

0x39170000 dnpdrv.c

0x44000001 flashapihdlr.c

0x5E2C05DA
0x5E2CDFC1

Product Software Failure / Non Standard (Maint Type 14 / 16) Error Codes (As detected in P443, P445, P4

Additional Errorcodes e.g. Sigma Delta (as used in P34x relays) have been included.
Note that these error codes may be applicable to other Px40 Products which use the CAA (e.g. P14x, P34x, P6
These errorcodes are NOT APPLICABLE to other Px40 products (e.g. P24x, P441?, P442, P444, P741, P742,

Type 14 unless specified

Error Code Decimal Negative Error Module Sub Code

2172715008 -2122252288
to to
0x8181xxxx 2172780543 -2122186753
2172780544 -2122186752
to to
0x8182xxxx 2172846079 -2122121217
0x8381xxxx
(Type 16)
0x83820000
(Type 16)
0x83830000
(Type 16) 2206400512

0x8C0F0000 2349793280

0x8C810000 2357264384
0x8D840000
0x928C0000 2458648576
0x928C0100 2458648832
0x928C0200 2458649088
0x928C0300 2458649344

0x93830000 2474835968 -1820131328

0x93840000 2474901504 -1820065792
0x93850000 2474967040 -1820000256
0x93860000 2475032576 -1819934720

0x93870000 2475098112 -1819869184

0x93880000 2475163648 -1819803648

0x93890000 2475229184 -1819738112

0x938A0000 2475294720 -1819672576

0x938B0000 2475360256 -1819607040

0x96800237 2524971575

0x9681023E 2525037118

0x97800855 2541750357
0xAC810000 2894135296 -1400832000
0xB1820000
(Type 16)
0xBE820000
(Type 16) 3196190720 -1098776576
0xC1820000
(Type 16) 3246522368 -1048444928

0xC989xxxx

0xCC0100xx

0xCC0200xx

0xCF840000 3481534464 -813432832

0xCF850000 3481600000 -813367296

0xCF860000 3481665536 -813301760

0xD1810000
(Type 16) 3514892288 -780075008
0xD18100B9
(Type 16)
0xD5820000
(Type 16) 3582066688 -712900608
0xDD020000

0xDD0A0000

0xDD0F0000

0xDD810000

0xDD820000

0xDD830000

0xDD840000

0xDD850000

0xDD860000

0xE0000001

0xE0010001
0xE0010002
0xE0010004
0xE0010005

0xE0010006

0xE0050001
0xE0300001
0xE0300002
0xE0400001

FOLLOWING IS FOR LATTES PRODUCTS ONLY (e.g. P24x, P441?, P442, P444, P741, P742, P743).
Product Software Failure / Non Standard (Equivalent Maint Type 14 ? / 16 ?) Error Codes (As Reported b

These errorcodes MAY BE APPLICABLE to Px40 products (e.g. P24x, P441?, P442, P444, P741, P742, P743).

Type 14 ? or 16 ? unless specified - If only someone would tell us...

Error Code Decimal Negative Error Module Sub Code

0x8118xxxx
Note: The yellow blocks are the error codes which have not been
explained.
cted in P443, P445, P446, P540, P540D, P841)

Error sub-module(s) Feature Code Error Feature

Phase 2 Processor
(CPU2/XCPU2) Internal
sbs_atPerm.c, sbs_atinit.c RAM Failure
Phase 2 Processor
(XCPU2/CPU2) RAM2_3
sbs_atPerm.c, sbs_atinit.c Failure
Phase 2 Processor
(XCPU2/CPU2) RAM0_1
sbs_atPerm.c, sbs_atinit.c Failure
Phase 2 Processor
(CPU2/XCPU2) External
sbs_atPerm.c, sbs_atinit.c SRAM Failure
Phase 2 Processor
(XCPU2/CPU2) SRAM
sbs_atPerm.c, sbs_atinit.c Failure
Phase 2 Processor
(XCPU2/CPU2) SRAM2
sbs_atPerm.c, sbs_atinit.c Failure
 Phase 2 Processor
(CPU2/XCPU2) SRAM
sbs_atPerm.c, sbs_atinit.c Failure
Phase 2 Processor
(CPU2/XCPU2) SRAM
sbs_atPerm.c, sbs_atinit.c Failure

Error Codes (As detected in P443, P540, P540D)

Error sub-module(s) Feature Code Error Feature

EEPROM Access Failure

cs103stack.c
cs103stack.c
The Courier serial
communications service
could not be initialised.

The Flash memory service

could not be initialised.

The Flash memory service

see 50300L1\... smf_drv.h could not be initialised

The Flash memory service

could not be initialised.

The Flash memory service

could not be initialised.
Nucleus Plus could not
create the slow watchdog
timer

Nucleus Plus could not

allocate memory for the
stack and/or the queue for
the Monitor Task. Check
that there is sufficient
space allocated in the
Platform Software memory
pool.

Nucleus Plus could not

create the queue for the
Monitor Task. Check that
there is sufficient space
allocated in the Platform
Software memory pool.
 Nucleus Plus could not
create the Monitor Task.
Check that there is
sufficient space allocated
in the Platform Software
memory pool.
The date and time service
could not be initialised.
The logging API could not
be initialised.
The database could not be
initialised.
A restore defaults
command issued during
power-up failed.
The active group setting
was corrupted.
The database lock could
not be obtained in order to
set the active group.
The data acquisition
service could not be
initialised.

System Services - Sea2lib 15 Serial E2PROM

System Services - Sea2lib 1C Opto Card Error

The output relay contact
service could not be
initialised.
System Services - Ser2lib 19 Relay Card Failure
The fast watchdog timer
could not be
created/started.

The fast watchdog timed

out.
The permanent self test
services could not be
started.
The lockup timer could not
be created/started.
The lockup timer could not
be stopped.

The serial
communications service
locked up during
initialisation.
The LCD service locked up
during initialisation.
The Flash memory service
locked up during
initialisation.
The date and time service
locked up during
initialisation.
The data acquisition
service locked up during
initialisation.
The output relay contact
service locked up during
initialisation.
The logging API locked up
during initialisation.
The database API locked
up during initialisation.
The database API locked
up during instatement of
default settings.
The IRIG-B time
synchronisation locked up
during initialisation.
The product-specific
extension indicated an
error condition.
The continuous self-tests
detected an error in the
SRAM bus.
The continuous self-tests
detected an error in the
SRAM.

The continuous self-tests

detected an error in the
Flash memory checksum.

The continuous self-tests

detected an error in the
code comparison.
The continuous self-tests
detected an error in the
battery-backed SRAM.
The continuous self-tests
detected an error in the
EEPROM checksum.
The continuous self-tests
detected an error in the
acquisition card.

The continuous self-tests

detected an error in relay
card n (numbered from 1).
 The continuous self-tests
detected an error in opto
card n (numbered from 1).
The continuous self-tests
detected an error in the
Analogue Data Sampling.
The secondary self-tests
detected an error in the
fast watchdog.
The secondary self-tests
detected an error in the
battery-backed SRAM.
The secondary self-tests
detected an error in the
bus reset circuit.
The secondary self-tests
detected an error in the
slow watchdog.
The secondary self-tests
detected an error in the
fast watchdog.

The VT ratios could not be

patched because a lock
could not be obtained for
the database.
Analogue input module -
possible missing / faulty
VT.
Dual Input Output Board -
Opto input problem
Dual Input Output Board -
Relay Output problem
The dual characteristic
optos are not fitted.

Front Panel is not correct

type or is faulty

IED Config (based on mcl

flashapihdlr.c, smf_drv.c, file) cannot be initialised in
smfp_drv.c FLASH memory
Flash Memory (Buffer)
Failure - PSL Settings /
User Curves (P14x)
 msf Domain issue.

Invalid Number of Circuit

50300PL\DEV\pl\SRC\ui.c Breakers (Configuration)

dnpdrv.c DNP Time Sync

Allocation of memory for

dr_init.c DR failed
Disturbance Recorder -
Nucleus message received
from incorrect message
dr_task.c queue

Continuous reboot and the

error appears before
dr_bbsup.c reboot

Continuous reboot and the

error appears before
dr_bbsup.c reboot
Alarm Indexing is not
msfx_plat.c correct
Memory Allocation failure
50300PL\DEV\uca2\mb\eci\ (ECIData Measurands -
eciproc.c MX_REF)

50300PL\DEV\uca2\mb\eci\ Bad MSD Table - MSD

eciproc.c (also see Table has NULL Address
eci_api.c) "info" Entry
50300PL\DEV\uca2\mb\eci\ ECI - Bulk Transfer
eciproc.c (also see eci.c, memory fail (Memory
eci_fifo.c) allocation)

50300L1\DEV_C33\Commu
nication\src\scd_drv.c,
scs_drv.c (CPU2),
50300L1\DEV\c\SRC\scc_ty Error when reading DNP3
Drv.c, scl_tyLib.c (CPU1) data from driver.
Flash memory buffer -
initialisation failure
DNP Evolutions - Micom
S1 Extraction of DNP
dnpev_setxfer.c Config File
 DNP Evolutions - Micom
S1 Extraction of DNP
dnpev_setxfer.c Config File

Error Codes (As detected in P443, P445, P446, P541, P542, P543, P544, P545, P546, P547, P841, P540D)

ave been included.

ucts which use the CAA (e.g. P14x, P34x, P64x ?, P74x?).
e.g. P24x, P441?, P442, P444, P741, P742, P743).

Error sub-module(s) Feature Code Error Feature

faultrec_fl.c

faultrec_fl.c

faultrec_fl.c

protapi.c
super.c Event FIFO Overflow
Event FIFO Overflow
Fault FIFO Overflow
 Maintenance Event FIFO
Overflow

superx.c Copro FPGA Download

Coprocessor SRAM
Copro FPGA Download
Coprocessor

Main Card / Co-Processor

Interface
Main Card / Co-Processor
superx.c Interface
Main Card / Co-Processor
superx.c Interface
Main Card / Co-Processor
superx.c Interface

cd_spvr.c Pre K - Co processor

cd_spvr.c Pre K - Co processor

cd_hloc.c Pre K - Co processor

measfn_cfg.c

AR_singlepole.c

cbcond.c

msfx_dist.c, msfx_feed.c etc

Model Number - Hardware

inmonx.c version

Model Number - Number

inmonx.c of Optos

Main Card / Co-Processor

cdbcomm.c Interface
Main Card / Co-Processor
cdbcomm.c Interface
Main Card / Co-Processor
cdbcomm.c Interface

faultrecx.c (Pre-K)

faultrecx.c

thermal.c
 sigma_delta.c Sigma Delta Input Module

sigma_delta.c Sigma Delta Input Module

sigma_delta.c Sigma Delta Input Module

sigma_delta.c Sigma Delta Input Module

sigma_delta.c Sigma Delta Input Module

sigma_delta.c Sigma Delta Input Module

sigma_delta.c Sigma Delta Input Module

sigma_delta.c Sigma Delta Input Module

sigma_delta.c Sigma Delta Input Module

Co-processor stack checker

cop_main.c Co-processor
cop_main.c Co-processor
cop_main.c Co-processor
cop_main.c Co-processor

cop_main.c Co-Processor

cop_iface.c
Diffprep.c Co-Processor
Diffprep.c Co-Processor
cop_sramchecker.c Co-Processor

P442, P444, P741, P742, P743).

pe 14 ? / 16 ?) Error Codes (As Reported by STONE PRODUCTION in LATTES Px40 Products)

24x, P441?, P442, P444, P741, P742, P743).

Error sub-module(s) Feature Code Error Feature

Description / Action

System services Background check task sbs_atPermTask() calls function

sbs_atVerifCode() which checks the Code stored in Flash Memory against the
code stored in SRAM and Internal RAM
System services Background check task sbs_atPermTask() calls function
sbs_atVerifCode() which checks the Code stored in Flash Memory against the
code stored in SRAM and Internal RAM
System services Background check task sbs_atPermTask() calls function
sbs_atVerifCode() which checks the Code stored in Flash Memory against the
code stored in SRAM and Internal RAM
System services Background check task sbs_atPermTask() calls function
sbs_atVerifCode() which checks the Code stored in Flash Memory against the
code stored in SRAM and Internal RAM
System services Background check task sbs_atPermTask() calls function
sbs_atVerifCode() which checks the Code stored in Flash Memory against the
code stored in SRAM and Internal RAM
System services Background check task sbs_atPermTask() calls function
sbs_atVerifCode() which checks the Code stored in Flash Memory against the
code stored in SRAM and Internal RAM
System services Background check task sbs_atPermTask() calls function
sbs_atVerifCode() which checks the Code stored in Flash Memory against the
code stored in SRAM and Internal RAM
System services Background check task sbs_atPermTask() calls function
sbs_atVerifCode() which checks the Code stored in Flash Memory against the
code stored in SRAM and Internal RAM

Description / Action

XCPU3, CPU3 and XCPU2 do not have EEPROM, so Software versions that use
EEPROM (er.g. P54x version 20 - "G" Hardware) may run in "J" Hardware
(CPU2), but not "L" Hardware (CPU3)
Problem arising from time sync
Problem arising from time sync

Most likely function "inmon_InitialiseFlash()" which is called by function

"inmon_Initialise()"

Indicate the FLASH memory driver found a corrupt logical zone when it tried to
initialise the FLASH memory. FLASH memory is used to store relay settings and
other non volatile data. FLASH memory is fitted to the main processor board
which is located within the front panel. The relay should be returned for repair but
if this is not practicable the front panel should be replaced.

Flash Write time-out Error

Flash Read time-out Error

An error has been detected in the acquisition driver. Check the input board and
the opto boards

Analogue input module serial e2prom Failure. Replace analogue input module.
Opto (Status) Input card Failure. Check each digital status input card and replace
as necessary.

An error has been detected in an output relay card. Check the relay boards.
Relay Card Failure. Check each relay output card and replace as necessary.

the fast watchdog has timed out. This suggests the software has stopped running.

The serial driver failed to initialise properly. Check the serial port hardware on the
power supply board and the main processor board.
The LCD driver failed to initialise properly. Check the LCD on the main processor
board.
The Flash memory driver failed to initialise properly. Check the Flash memory on
the main processor board.

The date and time driver failed to initialise properly. Check the real-time clock and
battery-backed SRAM on the main processor board.

The data acquisition driver failed to initialise properly. Check the input board and
the opto boards.

The relay driver failed to initialise properly. Check the relay boards.
The logs failed to initialise properly. Check the battery backed SRAM on the main
processor board.
The database failed to initialise properly. Check the EEPROM on the main
processor board.

The database took too long to commit a change. Check the EEPROM on the main
processor board.

The IRIG-B driver failed to initialise properly. Check the IRIG-B interface hardware
on the IRIG-B board.

The continuous self-checks have found an error in the RAM bus. Check the RAM
on the main processor board.

The continuous self-checks have found an error in the RAM block. Check the
RAM on the main processor board.

The continuous self-checks have found an error in the Flash EPROM checksum.
Check the Flash EPROM on the main processor board, and then try downloading
a new program.

The software is stored in FLASH memory along with a check sum. On power up
the program is copied to SRAM again with a check sum. The program runs from
SRAM. The continuous self-checks have found a difference between the code
stored in FLASH memory against that stored in SRAM. Could be a problem with
either the Flash memory or the SRAM memory on the main processor board, and
then try downloading a new program.

The continuous self-checks have found an error in the battery backed SRAM.
Check the battery, then the RAM on the main processor board.

The continuous self-checks have found an error in the EEPROM. Check the
EEPROM on the main processor board.

The continuous self-checks have found an error on the acquisition board. Check
the input board.

The continuous self-checks have found an error on a relay board. Check the relay
boards.
The continuous self-checks have found an error on an opto board. Check the opto
boards.
The continuous self-checks indicate that the Analogue data interrupt has stopped.
Check the Input module (or Sigma Delta module) operation and replace if
necessary.

Secondary initialisation tests detected a fast watchdog failure. Check the on the
main processor board.

Secondary initialisation tests detected a battery backed SRAM failure. Check the
battery backed SRAM on the main processor board.

Secondary self tests detected a bus reset test failure. Check the main processor
board.

Secondary initialisation tests detected a slow watchdog failure.

Repair the input module or replace with one of the correct type.

Possible Incorrect Address - Check Address (Red Jumper) Link position.

Possible Incorrect Address - Check Address (Red Jumper) Link position.

The XCPU2 board is faulty OR a standard CPU processor board is fitted in place
of XCPU2 (or vice versa). In software development - PDBCONF_HAVE_XCPU2 is
defined in software and non-XCPU2 is fitted or vice-versa.

Function flashapihdlr_InitGeneralBuffer() Reports

SMF_NO_EMPTY_LOGICAL_ZONES (via functions smf_InitBuffer2(),
smfp_LogicalZoneAddrManager()). SMF_LOGICAL_ZONE_INVALID_DATA - The
logical zone stores user configuration setting data that cannot be used by the
application (superseded by the later copy). This problem relates to the size of the
IEC61850 MCL File (IEC61850 Goose Scheme logic is too large to be contained
in the available memory). The customer will have to reduce the size of mcl file (to
less than 32kB) by simplifying the scheme. Check the size of the scheme ".mcl"
file as stored on the (computer) disk prior to downloading it to the relay.
Failure to Initialise the FLASH memory buffer - Sector has no free memory for
another logical zone to be stored. Check the Ribbon cable connections are OK.
Possible front panel fault - replace front panel.
Function msf_GetUpperLimitDATAXFRSUBDOMAIN() - Invalid Switch statement
argument
Excessive number of gates in PSL. Restore defaults and download new PSL.
PSL excessive execution time. Restore defaults and download new PSL.

Affects version 12 software and earlier. This is related to the time synchronisation
being simultaneously provided by two sources: DNP3 and IRIG-B. This error can
be produced if IRIG-B is enabled, and the IRIG-B board is ok and the IRIG-B
signal is OK.
Note that time synchronisation should NOT be from two sources at the same time!
- User must Disable / or disconnect the IRIG-B source or do not allow the DNP3
master to perform time-synchronisation of the relays)!

Check size of SRAM

This error is normal only associated with DR software development. If it occurs in

released software, this could be a memory allocation or SRAM failure issue
Possible relay de-energisation while Disturbance recored was being created or
cleared (Before checksum is stored). Disturbance recorder task Initialisation - Bad
Disturbance record data. BBRAM Checksum is OK, but data is corrupt. If error is
continuous, Remove Battery and power down relay for a minimum of 30 seconds
and then re-energise.
Possible relay de-energisation while Disturbance recored was being created or
cleared (Before checksum is stored). Disturbance recorder task Initialisation - Bad
Disturbance record data. BBRAM Checksum is OK, but data is corrupt. If error is
continuous, Remove Battery and power down relay for a minimum of 30 seconds
and then re-energise.

Function msfX_GetAlarmIndex() Invalid/incorrect ALARMGROUP Index.

Usually transient, will recover on reboot. If permanent, check used memory size
and data model size etc.
MSD Table has Courier Cell Reference with NULL Address - Possible Incorrect
Courier or UDT cell reference specified (IEC61850 Data model mapping error) or
Courier / UDT cell reference access problem. Requires investigation of the relay
code (software) to determine the exact cause.
Usually transient, will recover on reboot. If permanent, check used memory size
and data model size etc. In eci_fifo.c function add_record_to_ddb_list() cannot
allocate memory via malloc call.

CPU2 - DNP Receiver Buffer Overrun OR Invalid Parameter (port) in function

scs_read() OR Read from Empty buffer OR Incorrect DNP destination address in
message. Similar issue in CPU1.
The Flash memory buffer initialisation function flashapihdlr_InitGeneralBuffer() has
reported a non-specified error. Possible SRAM / Flash memory issue.

Default Switch (statement) error

 Bad Cell Ref - Extraction of DNPOE via Settings and Records (e.g. Cell DFC1)

P544, P545, P546, P547, P841, P540D)

Description / Action

The commissioning test module received an error code when writing to the relays.
Check the relay boards.

The commissioning test module received an error code when writing to the LEDs.
Check the processor card.

Fault Record Timestamp error.

Fault Location answer returned for a fault record that did not request it - should
not happed

No spare fault record in which to record the fault.

The error codeis related to the main sampling buffer.

When the relay samples a new set of analogue channels it puts the data in a 2
cycle buffer. This is done in an interrupt. Later the protection task runs and
extracts data from the buffer, thus free up space for new samples. This
maintenance occurs if the buffer becomes full, i.e. samples are put in faster than
they are removed. The maintenance error and reboot clears out the buffer and
allows the protection to restart. The relay runs a multitask operating system which
switches tasks in and out. The sampling interrupt is one of the highest priority
tasks and will always run, the protection task is also high priority but not the
highest. Another task may have run for longer than expected preventing the
protection task from running.

The analogue acquisition converts 16 channels, 13 are CT & VT and 3 are check
channels, into digital samples. The check channels consist of a fixed negative DC
voltage, 0V and a fixed positive DC voltage. After the analogue to digital
conversion the magnitude of the 3 check channels are compared to fixed limits. If
one or more is outside these limits the error 0x8C810000 is generated causing the
relay to reboot. If the problem is temporary the reboot will ensure the relay is
working again. If the reboots are continuous it could indicate a problem with the
analogue input module which needs to be checked and repaired
Unexpected protection command acknowledge received see DTS 2105
Event FIFO Overflow - P540 v55B and earlier software!
Coprocessor FPGA download failed, check current differential board and the
model number
Power on Co-Processor SRAM check failed, check current differential board
Program download failed, check current differential board
Program failed to start, check current differential board
Number of optical channels incorrect, check current differential board and model
number.

Coprocessor reconfiguration cannot be written to database (Data base manager).

Coprocessor data could not be transferred to the main card (read error).
Configuration Settings could not be transferred from the main card to the
coprocessor

Distance Settings could not be transferred from the main card to the coprocessor
The coprocessor has detected an SRAM (Code) error durring run time
background checks
The coprocessor has detected an SRAM (Data) error durring run time background
checks
Analogue check channels (see 0x8C810000). This is the same problem as
detected by the coprocessor
Current differential program stopped, check current differential board.

Checksum for Power Measurement data in BBRAM Fail does not match

Checksum for AR data in BBRAM Fail does not match

BBRAM checksum failed for CB Condtion Monitoring data.

Function msfX_Extract_DigitalDataBus_text() - Illegal DDB text entry for DDB
number xxxx
The hardware version of the model number (15th character) is older than the
minimum supported version for this software. Model Number Digit 15 is returned in
xx (in ASCII hex) if there is an error

P540D - Model Number is checked against the number of opto Status Inputs in
the relay. Model Number Digit 4 is returned in xx (in ASCII hex) if there is an error.
Note that this is really only relevent to P446, P543, P544 and P546 (which have a
fixed number of optos). P443, P445, P545 have more than one option.

P54x Pre-K Coprocessor Write failure

P54x Pre-K Coprocessor Read failure

P54x Pre-K Coprocessor Config failure

Checksum for Fault record data in BBRAM Fail does not match

Checksum for Fault record data in BBRAM Fail does not match

Checksum for Thermal Measurement data in BBRAM Fail does not match
 Cannot Resume Software Task. Transient error / reboot relay.

Default Switch Statement Error. Transient error / reboot relay.

Buffer Overflow Error. Transient error / reboot relay.

An invalid software (HISR) execution has occurred. If error is persistent, may have
to replace card / module.
An invalid channel has been defined when creating a sample system. If error is
persistent, may have to replace card / module.
An invalid sample has been received from system services. If error is persistent,
may have to replace card / module.
An error occured whilst reconfiguring a sample system. If error is persistent, may
have to replace card / module.
An invalid HISR execution has occurred. If error is persistent, may have to replace
card / module.
An error occured whilst reconfiguring the calibration data. If error is persistent,
may have to replace card / module.

The co-processor self checking has detected the stack has overflowed
The co-processor has detected overrun (taken longer than the aloocated 3 or 4
sample window)
The co-processor calibation coeficients (analogue inputs) are not correct
The co-processor DMA data transfer (analogue inputs) has failed
The co-processor Frequency tracking detection is not functioning correctly

Co-processor has detected an error in the analogue acquisition check channels

The error code comes from the co-processor when it tries to read data from the
main processor.
The main processor should write new data every 3 sample and the co-processor
reads it at the same rate. A method of hand shaking is used. If the co-processor
detects that the main processor has not written new data for 15 samples it forces
this error.
This suggests the main processor was busy doing something else.
Writing this data is one of the highest priority tasks the main processor has but
there are higher ones.
Receive Message (Channel1) Buffer Overflow.
Receive Message (Channel2) Buffer Overflow.
Coprocessor Stack check overrun

N in LATTES Px40 Products)

Description / Action

Incompatibility of communications protection with software version.