bit 0 = (1) initialize data FIFOs, (0) no effect. These are the Littlebear
So, for example, if a 03 is the value entered, both of the above operations will be performed. If 01 is entered, only the controller status byte will be cleared, and if 02 is entered, only the
16.7Command: “r”
This command is used to read a register from the controller address space. After “r” is entered, LBTEST will prompt for the address to be read. A
16.8Command: “s”
The status command is used to retrieve the status from the copier. The possible status requests are as follows:
Engine default status | (00h) |
Current engine status | (01h) |
Output placement | (02h) |
print/scan status | (10h) |
Cover status | (11h) |
Paper misfeed status | (12h) |
Service call number | (13h) |
Scanner setting status | (14h) |
Command status | (FFh) |
All of the status requests are described in the interface document and will not be described in detail in this document. In general, the user must enter the HEX number corresponding to the status to be retrieved. LBTEST will display a line in this format:
Success retrieving status: to_go:XX signals: YY sts: ZZ ZZ ZZ ZZ ZZ ZZ ZZ ZZ ZZ
Where XX is currently not used (this information may be ignored), YY is the controller status byte (described below), and ZZ are the status bytes from the copier corresponding to the requested
status type (described in the interface spec).
The controller status byte is a
bit 7 = Print/Scan underflow/overflow occurred.
bit 6 = Copier set command failure bit for last command. bit 5 = Print/Scan did not complete successfully.
bit 4 = Command/Status communication failure between controller/copier.
bit 3 = Controller computed checksum error in status from copier.
Print Server Manual | 63 | A741 |