Specifications

8/6/2010 KR203 Software Integrator Guide P1028248-001 Rev. A
Appendix B
Programming Example
Background
In order to incorporate the way status monitoring works for the KR203 printer setup, it is
important to understand what happens in a kiosk when you print, and when status
monitoring should take place.
Status monitoring can be handled in two ways:
• Monitoring in the printing application.
• Monitoring in a separate application.
When monitoring takes place in the printing application, normally the printer is observed
before sending a print job to see if the printer is “OK” and then send the print job. After the
print job is signaled as being printed, the status is checked again to see if the printer has
any errors or if the paper has been taken, etc.
Monitoring in a separate application usually doesn’t allow direct interaction with the printed
job so the printer is polled as often as possible to get most accurate information on what
the printer is doing. This is usually very time consuming and care must be taken for
synchronizing with a current print job.
Since the latter example is most commonly used for status monitoring, an event
notification has been incoprorated into the language monitor to allow a monitoring
application to do other tasks and have a separate thread listening for the printer status or
error event change. When this occurs the thread is simply getting the status and reporting
this back to the main program or doing any other kind of reporting.
To accommodate this notification for all error and status changes, two mechanisms have
been incorporated into the language montor.