CONFIDENTIAL
Paper roll Status commands GS j
Ver. 10.0 1 p. 329
With a serial interface, the printer transmits a 4-byte ASB status message without confirming whether the
host can receive data. ASB status, except for the XOFF code, is always consecutive.
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 the header. If the data transmitted
from the printer is [Hex = 35H/Decimal = 53], the host should process 4-byte data up to NUL [Hex = 00H/
Decimal = 0] as ASB status. When identifying an ASB status message, there are exceptions, as follows:
When processing block data [Header ~ NUL], do not identify ASB status.
When the host communicates with the printer by XON/XOFF control, the host should process data
consisting of 4 bytes, except for the XOFF code, as ASB status. ASB status configuration is different from
that of the XOFF code.
[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.