Recovery From Mechanical Errors - TransAct Epic 3000 Programmer's Manual

Table of Contents

Advertisement

Communications

Recovery from Mechanical Errors

The Ithaca Inquire commands and the Epson [DLE][ENQ] and [DLE][EOT] commands
allow most printer error status to be read and in some cases recovery attempted. Paper
jams and auto-cutter faults can be recovered, however, any data not previously printed
will be lost.
If the application is to support error recovery, the application should use the appropriate
status request commands to query the printer periodically. If an error response is such
that the fault is recoverable, the host application should interact with the operator and
request that the fault be corrected. (IE. Clear Paper Jam) When the operator indicates
that the problem has been corrected, the host can issue a reset request.
If a serious error occurs, the printer will halt and enter fault error mode. If the fault is
such that the printer can maintain communications with the host, the print status request
and response system will remain active. The status of the system will however remain
static, i.e. the status responses will reflect the state of the system when the fault
occurred.
There are errors that cannot be reported to the host system. These errors are such that
the integrity of the printer do not allow continued operation. That is there is no way to
report the error. These errors occur (for the most part) during power up diagnostics.
They are as follows:
EEPROM READ ERROR
The Internal EEPROM is not readable or the check sum is bad.
Pressing the Power Button will attempt to rewrite the configuration information.
This may leave the printer configured incorrectly.
EEPROM WRITE ERROR
The Internal EEPROM is defective. There is no recovery.
SOFTWARE ERROR VECTOR
These errors can occur during operation. They signal a serious problem with the
system. In most cases this error will also generate a Watch Dog reset. A power
cycle will generally recover normal printer operation. An ESD event or a
firmware bug generally causes these errors. The printer maintains an error log,
this log contains additional information about the fault and is printed during
manual configuration. The information in this log should be reported to Transact
to identify the exact cause of the fault.
USERSTORE FORMAT ERROR
The User Store data in FLASH has an invalid format. Pressing the Power Button
will erase the user store and reformat it. This can be caused by a firmware
update.
FLASH WRITE ERROR
The Program Flash has failed. There is no recovery from this error.
COM ADAPTER ERROR
The communications interface card is not supported by the firmware or is
missing. There is no recovery.
Page 246
FST 9000 Programmer's Guide
Power up only
Power up/down and Configuration only
Can occur at any time.
Power up or User Store Write Operations
Power up or User Store Write Operation.
Power up only
Rev A
100-14362

Advertisement

Table of Contents
loading

Table of Contents