GSi TYMPSTAR 1, Service Manual

Page: 201 / 224

Troubleshooting
CP Error codes
2403 ABORT_DAT_FILE_OPEN_ERR_WRITE_ITEM Data open file failed on Write Item
Subcodes: none
Likely Causes: There was a failed attempt to open a file on
the disc for writing. This can occur if the DOC has filled or
there is a problem with the DOC on the PC104. The PharLap
OS provides the file handling, so any software error here
would be located in the OS kernel for file access, and is very
unlikely.
2404 ABORT_DAT_FILE_READ_BAD_POINTER Bad pointer for read item.
Subcodes: none
Likely Causes: For every item read in the system, has a
corresponding memory buffer. If the memory buffer is not
valid (NULL pointer), we get this error code. This indicates
an internal software failure.
2405 ABORT_DAT_FILE_READ_DATA_FAIL Bad read of a BIN data file - missing or corrupt
Subcodes:
1=Print Format data file.
2=Remote Settings data file.
3=Data Xfer Settings data file.
4=Date/Time Settings data file.
5=Language data file.
6=Test Sequence data file.
7=LCD Contrast data file.
8=Facility Name data file.
Likely Causes: It is most likely that the file is not present or
is not updated. When new software is loaded (or upgraded),
files can be missing or out-of-date. With any new release
that requires an update in data files, the system must be
booted to the CAL DEFAULTS screen and the GSI
USER/KEY DATA must be loaded. If this is not the source
of the problem, one or more data files may have been
corrupted due to a previous system crash (possible if a file
was open for write and system crashes for any reason). It is
also possible to be a DOC failure on the PC104. It is less
likely a software problem with the file system, as all file I/O
occurs through the PharLap OS.
2500 ABORT_INI_SECTION_NOT_FOUND Ini file read - section not found
Subcodes: none
Likely Causes: The .INI file was found, but the section was
not found. With any new release that requires an update in
.INI file, the system must be booted to the CAL DEFAULTS
screen and the GSI USER/KEY DATA must be loaded. If
this is not the source of the problem, one or more data files
may have been corrupted due to a previous system crash
(possible if a file was open for write and system crashes for
any reason). It is also possible to be a DOC failure on the
PC104. It is less likely a software problem with the file
system, as all file I/O occurs through the PharLap OS.
2502 ABORT_INI_FILE_NOT_FOUND Ini file not found during read.
Subcodes: none
Likely Causes: The .INI file was not found for read access; it
should be part of the initial TympStar installation. In this
case one or more data files may have been corrupted due to a
previous system crash (possible if a file was open for write
and system crashes for any reason). It is also possible to be a
DOC failure on the PC104. It is less likely a software
problem with the file system, as all file I/O occurs through
the PharLap OS.
GSI TympStar Version 1 and Version 2 Service Manual 8 - 11