GSi TYMPSTAR 1, Service Manual

Page: 203 / 224

Troubleshooting
CP Error codes
2801 ABORT_RTC_TIME_WRITE_ERR Error attempting to update the RTC
Subcodes: getlasterror() - see Windows documentation
Likely Causes: The PharLap OS performs Real-Time-Clock
read/writes. These are modeled after the Windows API calls.
Any failures are associated with a faulty RTC on the PC104
or indicate an internal software failure.
2902 ABORT_HW_PRINTER_ADD_JOB_FAIL Error attempting to add printer job. Out of Memory.
Subcodes: none
Likely Causes: Memory is allocated for the print buffers;
when a print job is submitted the system checks to ensure that
there is enough memory available for printing. Since the
biggest possible canvas is pre-allocated, this would indicate
an internal software failure.
2903 ABORT_HW_PRINTER_TIMEOUT Error waiting for printer to be ready. BUSY stuck asserted.
Subcodes: none
Likely Causes: Print BUSY was stuck asserted. We know
there are ESD problems that can cause this BUSY line to
latch, so internal recovery is provided. If the BUSY line is
still asserted after the recovery phase, we failsafe with this
code. The most likely source of this problem is Printer
board hardware (including CPLD), or possibly the printer
firmware. It is also possible that there is a failure in the
data/control line path from the printer board through the
digital board to the printer port connector on the PC104.
2905 ABORT_HW_PRINTER_CANVAS_NULL Printer canvas was NULL when submitting print job.
Subcodes: none
Likely Causes: After the print job is spooled, the print job is
submitted and we check to ensure that the buffer passed was
non-NULL. Since we pre-allocate our canvas buffers, this
would indicate an internal software failure.
2906 ABORT_HW_PRINTER_ADD_JOB_FULL Printer canvas was full when attempting to add a job.
Subcodes: none
Likely Causes: After the print job is spooled and submitted,
the system checks to ensure that there is enough room in the
printer buffers for this new canvas. Since we pre-allocate our
canvas buffers to be large enough (and we expect that the
printer should be able to take in bytes fast enough) this would
indicate an internal software failure. It is possible that the
printer firmware is taking in bytes slower than expected (but
not slow enough to assert the
ABORT_HW_PRINER_TIMEOUT failsafe).
2907 ABORT_HW_KBD_BAD_TEXT_FIELD_IDX Bad text field index (patient name, id, etc)
Subcodes: none
Likely Causes: The CP software maintains an internal index
for which text field is currently active (Patient name, ID,
Tester) and if that index ever gets out of range then this
failsafe occurs. Since the software directly controls this
index, this code would indicate an internal software failure.
3000 ABORT_RT_RAM_TEST_FAIL Regulatory Testing - RAM Test Failure.
Subcodes: cData - data byte that failed R/W.
Likely Causes: PC104 SRAM or other PC104 failure.
3001 ABORT_RT_SEREE_TEST_FAIL Serial EEPROM failure
Subcodes: read data byte
Likely Causes: Probe EE faulty or a problem with the
data/control path from probe back to the digital board.
GSI TympStar Version 1 and Version 2 Service Manual 8 - 13