You are on page 1of 12

Error Code Decimal Negative Error Feature

Px40 Platform Error Codes (As detected in P443, P540, P540D) - These may also be applicable to other P

0x0B230136 186843446
0x0B230163 186843491
The Courier serial
communications
service could not be
0x0C010000 initialised.
The Flash memory
service could not be
0x0C020000 initialised.

The Flash memory


service could not be
0x0C020022 201457698 initialised
Nucleus Plus could not
create the slow
0x0C030000 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
0x0C040000 memory pool.

Nucleus Plus could not


create the queue for
the Monitor Task.
Check that there is
sufficient space
allocated in the
Platform Software
0x0C050000 memory pool.

Nucleus Plus could not


create the Monitor
Task. Check that there
is sufficient space
allocated in the
Platform Software
0x0C060000 memory pool.
The date and time
service could not be
0x0C070000 initialised.
The logging API could
0x0C080000 not be initialised.
The database could not
0x0C090000 be initialised.
A restore defaults
command issued
0x0C0A0000 during power-up failed.
The active group
0x0C0B0000 setting was corrupted.
The database lock
could not be obtained
in order to set the
0x0C0C0000 active group.
The data acquisition
service could not be
0x0C0D0000 202178560 initialised.
0x0C0DDB15 202234645 Serial E2PROM

0x0C0DDB1C 202234652 Opto Card Error


The output relay
contact service could
0x0C0E0000 202244096 not be initialised.
0x0C0ED919 202299673 Relay Card Failure
The fast watchdog
timer could not be
0x0C0F0000 created/started.

0x0C100000 202375168
The fast watchdog
0x0C100000 timed out.
The permanent self
test services could not
0x0C110000 be started.

The lockup timer could


0x0C120000 not be created/started.
The lockup timer could
0x0C130000 not be stopped.

The serial
communications
service locked up
0x0C140001 202637313 during initialisation.
The LCD service
locked up during
0x0C140002 202637314 initialisation.
The Flash memory
service locked up
0x0C140003 202637315 during initialisation.
The date and time
service locked up
0x0C140004 202637316 during initialisation.
The data acquisition
service locked up
0x0C140005 202637317 during initialisation.
The output relay
contact service locked
0x0C140006 202637318 up during initialisation.
The logging API locked
0x0C140007 202637319 up during initialisation.
The database API
locked up during
0x0C140008 202637320 initialisation.
The database API
locked up during
instatement of default
0x0C140009 202637321 settings.

The IRIG-B time


synchronisation locked
0x0C14000A 202637322 up during initialisation.
The product-specific
extension indicated an
0x0C150000 error condition.

The continuous self-


tests detected an error
0x0C160010 202768400 in the SRAM bus.
The continuous self-
tests detected an error
0x0C160011 202768401 in the SRAM.
The continuous self-
tests detected an error
in the Flash memory
0x0C160012 202768402 checksum.

The continuous self-


tests detected an error
in the code
0x0C160013 202768403 comparison.
The continuous self-
tests detected an error
in the battery-backed
0x0C160014 202768404 SRAM.
The continuous self-
tests detected an error
in the EEPROM
0x0C160015 202768405 checksum.

The continuous self-


tests detected an error
0x0C1600A0 202768544 in the acquisition card.
The continuous self-
tests detected an error
in relay card n
0x0C1600B0 202768560 (numbered from 0).
The continuous self-
tests detected an error
in opto card n
0x0C1600C0 202768576 (numbered from 0).
The secondary self-
tests detected an error
0x0C170016 202833942 in the fast watchdog.
The secondary self-
tests detected an error
in the battery-backed
0x0C170017 202833943 SRAM.

The secondary self-


tests detected an error
0x0C170018 202833944 in the bus reset circuit.

The secondary self-


tests detected an error
0x0C170019 202833945 in the slow watchdog.

The secondary self-


tests detected an error
0x0C17001A in the fast watchdog.
The VT ratios could not
be patched because a
lock could not be
obtained for the
0x0C180000 database.

The dual characteristic


0x0C1C0000 optos are not fitted.
0x0E020000 235012096
0x0E080000 235405312

0x13240000 321126400 DNP Time Sync

Continuous reboot and


the error appears
0x1C1200F5 470941941 before reboot

Continuous reboot and


the error appears
0x1C1200F6 470941942 before reboot
DNP Evolutions -
Micom S1 Extraction of
0x5E2C05DA DNP Config File

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


2172715008 -2122252288
to to
0x8181xxxx 2172780543 -2122186753
2172780544 -2122186752
to to
0x8182xxxx 2172846079 -2122121217
0x83830000 2206400512

0x8C0F0000 2349793280

0x8C810000 2357264384
0x8D840000
0x928C0000 2458648576 Event FIFO Overflow
0x93830000 2474835968 -1820131328
0x93840000 2474901504 -1820065792
0x93850000 2474967040 -1820000256
0x93860000 2475032576 -1819934720
Main Card / Co-
0x938B0000 2475360256 -1819607040 Processor Interface
0x928C0100 2458648832 Event FIFO Overflow
0x928C0200 2458649088 Fault FIFO Overflow
Maintenance Event
0x928C0300 2458649344 FIFO Overflow

0x93870000 2475098112 -1819869184

0x96800237 2524971575 Pre K - Co processor

0x9681023E 2525037118 Pre K - Co processor


0xAC810000 2894135296 -1400832000
0xB1820000
0xBE820000 3196190720 -1098776576
0xC1820000 3246522368 -1048444928
Main Card / Co-
0xCF840000 3481534464 -813432832 Processor Interface
Main Card / Co-
0xCF850000 3481600000 -813367296 Processor Interface
Main Card / Co-
0xCF860000 3481665536 -813301760 Processor Interface
0xD1810000 3514892288 -780075008
0xD18100B9
0xD5820000 3582066688 -712900608
0xE0000001 Co-processor stack chec

0xE0010006 Co-Processor

0xE0050001
0xE0400001 Co-Processor
Description / Action

P540, P540D) - These may also be applicable to other Px40 products.

Problem arising from time sync


Problem arising from time sync

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.
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.
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.

Excessive number of gates in PSL. Restore defaults and download new PSL.
PSL excessive execution time. Restore defaults and download new PSL.

Affects P54x 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)!

Possible relay de-energisation while Disturbance recored was being created or


cleared. 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. 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.
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.
No spare fault record in which to record the fault.

The error code is 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

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

Distance Settings could not be transferred from the main card to the coprocessor

Number of optical channels incorrect, check current differential board and model
number.
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
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.

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
The co-processor self checking has detected the stack has overflowed

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.
Coprocessor Stack check overrun

You might also like