Chapter 5: Programming commands 89
A776-PG00001 C 12/09 A776 (B780) Programming Guide
Flash memory user sector status (n = 4 or n = 52)
Bit O/On Hex Decimal Status for transmit status
0 – – – Undened. Fixed to o.
1 – – – Undened. Fixed to o.
2 O 00 0 User data storage write successful
On 04 4 User data storage write failed, specied area not erased.
3 O 00 0 Flash logo area adequate, denition stored.
On 08 8 Flash logo area not adequate for recent denition.
4 O 00 0 Not used. Fixed to o.
5 O 00 00 No thermal user-dened characters written to ash.
On 20 32 Thermal user-dened characters written to ash.
6 O 00 0 No impact user-dened characters written to ash.
On 04 64 Impact user-dened characters written to ash.
7 – – – Undened.
Send printer software version
ASCII US V
Hexadecimal 1F 56
Decimal 31 86
The printer returns 8 bytes containing the boot and ash software version. The rst 4 bytes returned are an ASCII string
for the boot version.
The second 4 bytes are an ASCII string for the ash version. Example: For 1.234.56 (8 bytes), the boot version is 1.23 and
the ash version is 4.56.
Real-time commands
The real time commands provide an application interface to the printer even when the printer is
not handling other commands:
• Real-timestatustransmission:GS(Hex1D)sequenceandDLE(Hex10)sequence
• Real-timerequesttoprinter:GS(Hex1D)sequenceandDLE(Hex10)sequence
• Real-timeprinterstatustransmission
The batch mode printer status commands are placed in the printer’s data buer as they are
received and handled by the rmware in the order in which they were received. If the paper exhausts while printing
data that was in the buer ahead of the status command, the printer
goes busy at the RS-232C interface and suspends processing the data in the buer until paper
is reloaded. This is true for all error conditions: knife home error, thermal printhead overheat, etc. In addition, there
is no way to restart the printer after a paper jam or to cancel a slip waiting condition when using the wait for slip
command.
The real-time commands are implemented in two ways in order to overcome the limitations of batch mode status
commands. Both implementations oer the same functionality; which one you choose depends on the current usage
of your application.