About printer emulations

The RPM user interface launches a utility which establishes a connection with your printer and performs the following queries:

@PJL INFO ID
@PJL INFO CONFIG
@PJL INFO MEMORY
@PJL INFO PAGECOUNT
@PJL INFO STATUS
@PJL INFO VARIABLES
@PJL INFO USTATUS

The purpose of this is so that the client application can query the printer and get realistic results, identical to or very close to what the client expects.

We also found that the majority of status readback results relied on data returned from these queries.

The utility composes the query results from the printer into a file stored in a PRINTERS folder alongside the RPM jobs and other data. RPM can then respond to queries authentically. RPM does not try to control or alter the PJL in the print job, although you can do that with the string translator.

Please note that the AppSocket protocol configuration form includes a field for serial number so you can keep the information private if you wish. The value for the ID field is what we use to display printer emulations.