CONFIDENTIAL
Paper roll Status commands GS j
Ver. 10.05 p. 325
■ When block data [Header ~ NUL] is being transmitted, ASB status cannot be transmitted. Therefore, you
cannot get the printer status change through ASB status when Block data [Header ~ NUL] is transmitted.
■ With a serial interface, the printer transmits a 4-byte ASB status message without confirming whether the
host can receive data.
■ With a parallel interface, when ASB status is used, it is desirable for the host to be in a reverse idle state.
However, if the host computer cannot always be in the reverse idle state, it is necessary to enter Reverse
Mode regularly to watch for ASB status. If the host is not in the Reverse Mode for a long time, and the
printer has to store ASB status changes to be transmitted, the following 2 sets (8 bytes) of ASB status are
changed to special data and transmitted prior to other transmission data when the host enters Reverse
Mode:
• ASB-1: Status information that shows whether status changes occurred
• ASB-2: The latest ASB status information
If bits have a different value between (ASB-1) and (ASB-2), this means at least one change has occurred.
An example is shown below:
Bit 5 of Status A for ASB-1 and ASB-2 is different. From this information, you can see that the printer
executed a cleaning but it has already finished.
■ Ink ASB status can be differentiated from other transmission data by identified data of the transmission
data group. If the header from the printer is [Hex = 35H/Decimal = 53], the host should process the data up
to NUL [Hex = 00H/Decimal = 0] as ASB status.
[Model-dependent variations] TM-J2000/J2100
Header Status A Status B NUL
ASB-1 0011 0101 0110 0000 0100 0000 0000 0000
ASB-2 0011 0101 0100 0000 0100 0000 0000 0000
Program Example
PRINT #1, CHR$(&H1D);"j";CHR&(2); ← Only sensor status can be selected.
Comments to this Manuals