HP-LASERJET-COMMON-MIB: View SNMP OID List / Download MIB

The number of valid bytes in the gdStatusEntry array.

This describes the line state of the peripheral. When non-zero, the peripheral is off-line. When zero the peripheral is on-line.

This describes the state of the paper on the peripheral. When non-zero, the peripheral has a paper problem. When zero, the peripheral does not have a paper problem.

This describes the intervention state of the peripheral. When non-zero, the peripheral requires human intervention to continue working. When zero, it requires no assistance.

This indicates to which read channel state the card should move. When non-zero, the card should indicate that the read channel is idle. When zero, the card should indicate that the read channel is operating. This object is Lan Manager io channel specific. It is kept here for backward compatibility. Starting with firmware release X.20.06 and subsequent releases, this object is obsolete as it provides no relevant data for the new hardware architecture. No current supported applications use this object.

This indicates whether the peripheral is waiting for the Connection termination ACK. When non-zero, it is waiting. When zero, it is not waiting.

This is the error code from the peripheral.

This indicates that the peripheral is out of paper. off (0), paper-out-or-paper-mount (1), manual-paper-feed-needed (2) For some peripherals, such as the HP LaserJet IIISi printer or HP DesignJet plotter, this value is always a zero (0).

This indicates that the peripheral has a paper jam. off (0), paper-jam(1) For some peripherals, such as the HP LaserJet IIISi printer or HP DesignJet plotter, this value is always a zero (0).

This indicates that the peripheral has a low toner condition. off (0), toner-low (1), no-toner-cartridge (2) For some peripherals, such as the HP LaserJet IIISi printer or HP DesignJet plotter, this value is always a zero (0).

This indicates that the peripheral did not receive data fast enough to keep up with the print engine when generating a page. For some peripherals, such as the HP LaserJet IIISi printer or HP DesignJet plotter, this value is always a zero (0).

This indicates that the peripheral did not have enough memory to render an image on a page. For some peripherals, such as the HP LaserJet IIISi printer or HP DesignJet plotter, this value is always a zero (0).

This indicates that the peripheral is processing data from this I/O interface card. For some peripherals, such as the HP LaserJet IIISi printer or HP DesignJet plotter, this value is always a zero (0). For X.20.06 firmware and later firmware releases, this object is not relevant. In order not to break legacy applications which call this object in multi-varbind requests, this value is always zero (0).

This indicates that the peripheral is busy processing print/plot data. For some peripherals, such as the HP LaserJet IIISi printer or HP DesignJet plotter, this value is always a zero (0).

This indicates that the peripheral is waiting for print/plot data to process. For some peripherals, such as the HP LaserJet IIISi printer or HP DesignJet plotter, this value is always a zero (0).

This indicates that the peripheral is initializing or warming up. off (0), initializing (1), warm-up(2) For some peripherals, such as the HP LaserJet IIISi printer or HP DesignJet plotter, this value is always a zero (0).

This indicates that the peripheral cover or door is open. For some peripherals, such as the HP LaserJet IIISi printer or HP DesignJet plotter, this value is always a zero (0).

This indicates that the peripheral is printing or otherwise marking or moving paper. off (0), ordinary-page (1), test-fonts-config-or-start-page (2) For some peripherals, such as the HP LaserJet IIISi printer or HP DesignJet plotter, this value is always a zero (0).

This indicates that the peripheral has a paper output problem such as the output storage bin being full. off (0), output-storage-full (1) For some peripherals, such as the HP LaserJet IIISi printer or HP DesignJet plotter, this value is always a zero (0).

This is the reserved area that is not currently used, but will allow for growth within the gdStatusEntry table.

This indicates if this channel is active. If the value is 0 then this channel is active or the peripheral is idle. If this value is non-zero then another channel is active. This is the Novell io channel

This indicates if this channel is active. If the value is 0 then this channel is active or the peripheral is idle. If this value is non-zero then another channel is active. This is the LLC io channel

This indicates if this channel is active. If the value is 0 then this channel is active or the peripheral is idle. If this value is non-zero then another channel is active. This is the TCP io channel

This indicates if this channel is active. If the value is 0 then this channel is active or the peripheral is idle. If this value is non-zero then another channel is active. This is the Apple talk io channel

The string diplayed on the peripheral front panel. For some peripherals, such as the HP LaserJet IIISi printer or HP DesignJet plotter, this is always a zero length string.

The current job name set by the peripheral. For some peripherals, such as the HP LaserJet IIISi printer or HP DesignJet plotter, this is always a zero length string.

A string indicating the name of the physical port or protocol the printer is currently getting data from.

A string indicating the Appletalk papstatus response.

A formatted string describing this peripheral.

This is the display code that the peripheral uses to tell the card what type of display the front panel of the printer is. Starting with firmware release X.20.06 and subsequent releases, this object is obsolete as it provides no relevant data for the new hardware architecture. No current supported applications use this object.

This value is the representation of what native language the printer is in currently.

This value represents (in seconds) the maximum time of inactivity which must elapse before the JetDirect card switches from the current network protocol to another when a normal end of job is not detected.

This object will enable/disable PJL ustatus. disabled (0), enabled (1)

This value represents what protocols Locally Administered addressing is supported over. This is currently 0 for 802.3 cards and 7 for 802.5 cards. LAA is not supported on 802.3. The value is a mask of bits, 1 for each of the protocols below. +-----------------------------------------------+ | NA | NA | NA | NA | NA | TCP | LLC | NOV | +-----------------------------------------------+

This object is used as a 256 byte NVRAM area for JetAdmin. It is completely managed by JetAdmin. Initially it is initialized to all zeros. A coldboot will re-initialize to all zeros.

The AppleTalk name of the printer.

The AppleTalk type of the printer.

Returns or changes the Energy Star sleep value. If the value is greater than zero, then the device will go into energy saving sleep mode after the print engine has been idle for the number of seconds specified by this object. A value of zero means Energy Star is disabled and the device will not go to sleep based on print engine idle time. The value must be non-negative. Additional information: Returns or changes the Energy Star sleep value. The device will go into energy saving sleep mode after the print engine has been idle for the number of seconds specified by this object. LaserJet 4050 Series supports values of 0, 900, 1800, 3600, 7200, and 10800. A value of 0 means never go to sleep based on print engine idle time. Setting to an unsupported value causes the printer to substitute a value (listed below) and to return <noError> status. The values are as follow: <=0 snap to 0 >=1 and <=1349 snap to 900 (15 minutes) >=1350 and <=2699 snap to 1800 (30 minutes) >=2700 and <=5399 snap to 3600 (1 hour) >=5400 and <=8999 snap to 7200 (2 hours) >=9000 snap to 10800 (3 hours)

Returns eTrue if the device is in energy saving sleep mode, otherwise returns eFalse. Setting SLEEP-MODE to eFalse causes the device to wake up, if it is in sleep mode. Setting SLEEP-MODE to eTrue causes the device to go into sleep mode. Additional information: This object returns eTrue if the device is in energy saving sleep mode, otherwise it returns eFalse. Setting this object to eTrue while the printer is awake will not change the printers current state and will return <genErr> status. NOTE: This object should behave this way when the printer does not have an instant-on fuser. Setting this object to eTrue while printer is already in Sleep Mode will not change the printers current state and will return <noError> status. Setting this object to eFalse while printer is already awake will not change the printers current state and will return <noError> status. Setting this object to eFalse while the printer is asleep causes the device to wake up.

Device control panel lock. A value of eDisabled means the control panel is unlocked and the devices configuration can be modified from the control panel. A value of eEnabled means the control panel is locked, thus the devices configuration cannot be modified from the control panel.

When set to the password value, other service related objects become visible (i.e readable) and/or become writable. When written with any other value, the service related objects become hidden (i.e. are no longer readable) and/or are not longer writable. The objects that can be effected by the SERVICE-PASSWORD object include: SERIAL-NUMBER and TOTAL-ENGINE-PAGE- COUNT. The password value, and the list of objects effected by the SERVICE-PASSWORD being set to the correct value, should be documented in the device POS. Additional information: The objects that can be effected by the SERVICE- PASSWORD are: SCANNER-JAM-PAGE-COUNT, SCANNER-ADF-PAGE -COUNT, SCAN-ADF-PAGE-COUNT, SCANNER-RETRIEVE-SCANLINE, SCANNER-MOTOR-CONTROL, COPIER-ADF-PAGE-COUNT, COPIER- PRINT-PAGE-COUNT, TOTAL-ENGINE-PAGE-COUNT, PRINT-ENGINE- JAM-COUNT, PRINT-ENGINE-MISPICK-COUNT

Handshaking mechanism between host and device to coordinate the download of device specific data. eCfgDownloadIdle - indicates device configuration download activity is not occurring. Device powers up in this state but will otherwise never transition to this state. This state is host settable from eCfgDownloadActive, eCfgDownloadDone, and eCfgDownloadAborted. Host setting to eCfgDownloadIdle while object is in eCfgDownloadActive will cause the download activity to be prematurely terminated. Host setting to this state resets the object to permit another download activity to be initiated. eCfgDownloadStart - indicates host wishes to commence a device configuration download activity. This state is only host settable from eCfgDownloadIdle. Only the device can transition this object from this state to eCfgDownloadActive or eCfgDownloadAborted. Device will not set to this state. eCfgDownloadActive - indicates download activity is in progress. Device transitions object to this state only from eCfgDownloadStart, to signal data download can commence. The device can transition from this state to eCfgDownloadDone or eCfgDownloadAborted. The host can transition from this state to eCfgDownloadIdle. This state is not host settable. eCfgDownloadAborted - indicates the download activity was terminated by the device. Only the device can set to this state from eCfgDownloadStart or eCfgDownloadActive. Only the host can transition from this state to eCfgDownloadIdle. This state is not host settable. eCfgDownloadDone - indicates device has completely received the download data. Device transitions to this state only from eCfgDownloadActive. Only the host can transition from this state to eCfgDownloadIdle. This state is not host settable.

Indicates the type of device specific data to be downloaded.

Handshaking mechanism between host and device to coordinate the upload of device specific data. eCfgUploadIdle - indicates device configuration upload activity is not occurring. Device powers up in this state but will otherwise never transition to this state. This state is host settable from eCfgUploadActive, eCfgUploadDone, and eCfgUploadAborted. Host setting to eCfgUploadIdle while object is in eCfgUploadActive will cause the upload activity to be prematurely terminated. Host setting to this state resets the object allowing a new upload to be initiated. eCfgUploadStart - indicates host wishes to commence a device configuration upload activity. This state is only host settable from eCfgUploadIdle. Only the device can transition this object from this state to eCfgUploadActive or eCfgUploadAborted. Device will not set to this state. eCfgUploadActive - indicates upload activity is in progress. Device transitions object to this state only from eCfgUploadStart, to signal data upload can commence. The device can transition from this state to eCfgUploadDone or eCfgUploadAborted. The host can transition from this state to eCfgUploadIdle. This state is not host settable. eCfgUploadAborted - indicates the upload activity was terminated by the device. Only the device can set to this state from eCfgUploadStart or eCfgUploadActive. Only the host can transition from this state to eCfgUploadIdle. This state is not host settable. eCfgUploadDone - indicates device completely transmitted the upload data. Device transitions to this state only from eCfgUploadActive. Only the host can transition from this state to eCfgUploadIdle. This state is not host settable.

Indicates the type of device specific data to be uploaded.

Specifies the number of seconds that device will wait for data from the host before the device determines the host is being unresponsive. This timeout condition may cause the device to take recourse action regarding the disposition of the download activity. A value of zero indicates device will wait forever for the host data. POS should indicate whether this object value, when set by the host, is remembered between device power cycles. Additional information: This object is volatile and as such will not be retained by the device between power cycles.

Specifies the number of seconds that device will wait for response from the host after transmitting a unit of data before the device determines the host is being unresponsive. This timeout condition may cause the device to take recourse action regarding the disposition of the upload activity. A value of zero indicates device will wait forever for the host response. POS should indicate whether this object value, when set by the host, is remembered between device power cycles Additional information: This object is volatile and as such will not be retained by the device between power cycles.

Returns or changes the location from which code executes. The object allows the user to pick a memory bank to run code from which is different than the default running code bank. A value of 0 means the code executes from the default code bank, which should be documented in the device POS. The list of supported values should be documented in the device POS. Setting to an unsupported value causes the device to return <badValue>. Additional information: Returns or changes the location from which code should be run. The object allows the user to pick a ram bank to run code from which is potentially faster than the onboard ROM. LaserJet 8100 Series and LaserJet 8000 Series support values of 0,4-9. A value of 0 means run code from default ROM device. Values other than 0 indicate a valid RAM bank of size >= 8MBs. Setting to an unsupported value causes the printer to leave the run location set to its previous value.

Controls front-panel date display format.

A C structure containing the following fields: typedef struct { u8bit list_id; s8bit auto_incr; u16bit max_index; u16bit rec_size; u16bit index; u8bit data[]; } PML_device_cfg_param_cmd_t; where u8bit is an unsigned byte (0..255), s8bit is a signed byte (-128..127), and u16bit is an big endian format unsigned short (0..65535). The POS should state which list_ids the device supports. Additional information: HP Laserjet 3200 supports two values for list_id: 0 for configuration parameters and 1 for default configuration parameters.

Provides an advisory locking mechanism for hosts to coordinate exclusive access to a copier device. Setting the object to a unique id will only succeed if the token is currently set to 0. The token is unlocked when it is set to 0. If the token is set to a any value other than 0, then token is locked. If the token was set to a unique id (locked), then an attempt to set (lock) the token will fail. If the token was set to 0 (unlocked), then an attempt to set (lock) the token will succeed in locking the token. A get operation on COPIER-TOKEN will return its current setting. The device does not prevent access to any objects. It is assumed that hosts will be well behaved; respecting this advisory locking mechanism by: 1) acquiring the lock before changing copier objects, and 2) releasing the lock when done changing copier objects. Additional information: Provides an advisory locking mechanism for hosts to coordinate exclusive access. Setting the object to a unique id will only succeed if the token is currently set to 0. The token is unlocked when it is set to 0. If the token is set to a any value other than 0, then token is locked. If the token was set to a unique id (locked), then an attempt to set (lock) the token will fail. If the token was set to 0 (unlocked), then an attempt to set (lock) the token will succeed in locking the token. A get operation on COPY-TOKEN will return its current setting. The device does not prevent access to any objects. It is assumed that hosts will be well behaved; respecting this advisory locking mechanism by: 1) acquiring the lock before changing copy objects, and 2) releasing the lock when done changing copy objects.

Provides an advisory locking mechanism for hosts to coordinate exclusive access to the fax upload features of a device. Setting the object to a unique id will only succeed if the token is currently set to 0. The token is unlocked when it is set to 0. If the token is set to a any value other than 0, then token is locked. If the token was set to a unique id (locked), then an attempt to set (lock) the token will fail. If the token was set to 0 (unlocked), then an attempt to set (lock) the token will succeed in locking the token. A get operation on FAX-UPLOAD-TOKEN will return its current setting. The device does not prevent MAX-ACCESS to any objects. It is assumed that hosts will be well behaved; respecting this advisory locking mechanism by: 1) acquiring the lock before changing any fax-upload objects, and 2) releasing the lock when done changing scan objects. Additional information: Provides an advisory locking mechanism for hosts to coordinate exclusive access. Setting the object to a unique id will only succeed if the token is currently set to 0. The token is unlocked when it is set to 0. If the token is set to a any value other than 0, then token is locked. If the token was set to a unique id (locked), then an attempt to set (lock) the token will fail. If the token was set to 0 (unlocked), then an attempt to set (lock) the token will succeed in locking the token. A get operation on FAX-UPLOAD-TOKEN will return its current setting. The device does not prevent access to any objects. It is assumed that hosts will be well behaved; respecting this advisory locking mechanism by: 1) acquiring the lock before changing fax objects, and 2) releasing the lock when done changing fax objects.

Provides an advisory locking mechanism for hosts to coordinate exclusive access to the fax download features of a device. Setting the object to a unique id will only succeed if the token is currently set to 0. The token is unlocked when it is set to 0. If the token is set to a any value other than 0, then token is locked. If the token was set to a unique id (locked), then an attempt to set (lock) the token will fail. If the token was set to 0 (unlocked), then an attempt to set (lock) the token will succeed in locking the token. A get operation on FAX-DOWNLOAD-TOKEN will return its current setting. The device does not prevent MAX-ACCESS to any objects. It is assumed that hosts will be well behaved; respecting this advisory locking mechanism by: 1) acquiring the lock before changing any fax-download objects, and 2) releasing the lock when done changing scan objects. Additional information: Provides an advisory locking mechanism for hosts to coordinate exclusive access. Setting the object to a unique id will only succeed if the token is currently set to 0. The token is unlocked when it is set to 0. If the token is set to a any value other than 0, then token is locked. If the token was set to a unique id (locked), then an attempt to set (lock) the token will fail. If the token was set to 0 (unlocked), then an attempt to set (lock) the token will succeed in locking the token. A get operation on FAX-DOWNLOAD-TOKEN will return its current setting. The device does not prevent access to any objects. It is assumed that hosts will be well behaved; respecting this advisory locking mechanism by: 1) acquiring the lock before changing fax objects, and 2) releasing the lock when done changing fax objects.

Provides an advisory locking mechanism for hosts to coordinate exclusive access to a specific device or subset of device capabilities. Setting the object to a unique id will only succeed if the token is currently set to 0. The token is unlocked when it is set to 0. If the token is set to a any value other than 0, then token is locked. If the token was set to a unique id (locked), then an attempt to set (lock) the token will fail. If the token was set to 0 (unlocked), then an attempt to set (lock) the token will succeed in locking the token. A get operation on DEVICE-CONFIG-TOKEN will return its current setting. The device does not prevent access to any objects. It is assumed that hosts will be well behaved; respecting this advisory locking mechanism by: 1) acquiring the lock before changing device config objects, and 2) releasing the lock when done changing device config objects. Additional information: Provides an advisory locking mechanism for hosts to coordinate exclusive access. Setting the object to a unique id will only succeed if the token is currently set to 0. The token is unlocked when it is set to 0. If the token is set to a any value other than 0, then token is locked. If the token was set to a unique id (locked), then an attempt to set (lock) the token will fail. If the token was set to 0 (unlocked), then an attempt to set (lock) the token will succeed in locking the token. A get operation on CONFIG-TOKEN will return its current setting. The device does not prevent access to any objects. It is assumed that hosts will be well behaved; respecting this advisory locking mechanism by: 1) acquiring the lock before changing CONFIG objects, and 2) releasing the lock when done changing CONFIG objects.

This object allows the user to view/change the color/mono switching mode for a device. Additional information: This object allows the user to view/change the color/mono switching mode for a device.

Return or set the value of the print engine speed. Where eNormal is the default speed and with each eSlowDownN setting the printer gets progressively slower than the previous speed. Additional information: This object will only be registered once the PE_TEST_PASSWORD is set. This object is used to return or set the value for the engines print speed. This value is written to NVRAM and is persistant. eNormal = Normal engine speed. eSlowDown1 = Decreased engine speed.

Return or set the value for the duplexer installed. eEnabled = The duplexer is installed. eDisabled = The duplexer is not installed. Additional information: This object will only be registered once the PE_TEST_PASSWORD is set. This object is used to return or set the value controlling the duplexer This value is written to NVRAM and is persistant. eDisabled = Disabled Duplexer. eEnabled = Enabled Duplexer.

This object is used to determine whether to prompt the user to enter the appropriate language. Additional information: This object is used to determine whether to prompt the user to enter the appropriate language at boot.

This object is used to determine whether to prompt the user to enter the appropriate country at boot. Additional information: This object is used to determine whether to prompt the user to enter the appropriate country at boot.

Set the location configuration for the device. This affects parameters that vary per region like the default paper size, symbol set, supply reorder URL, and fax parameters if applicable.

This object is used to configure product settings that are stored in secure area of nvram. The object consists of a 16-bit variable in secure nvram. Bits 15-8 are product specific. Bits 7-0 are system specific. Additional information: This object is used to configure product settings that are stored in secure area of nvram. The object consists of a 16-bit variable in secure nvram. Bits 15-8 are product specific. Bits 7-0 are system specific.

This object allows CPE to enable specific bug fixes or enhancements in post-release products. Additional information: This object allows CPE to enable specific bug fixes or enhancements in post-release products.

This object allows manufacturing to change the product number to a pre-defined alternate after release. This feature will allow manufacturing to assign unique product numbers to custom product bundles when the device is unable to determine its product number in firmware. For example, A HP Color LaserJet CP1515n could be configured to display CP1516n to the customer. This product number must be defined prior to release. Additional information: This object allows manufacturing to change the product number to a pre-defined alternate after release. This feature will allow manufacturing to assign unique product numbers to custom product bundles when the device is unable to determine its product number in firmware. For example, A HP Color LaserJet CP1515n could be configured to display CP1516n to the customer. This product number must be defined prior to release.

Preferred localization language used by the device at boot up time. Setting this object will instruct the device to boot up in that language. Setting this language does not impact device generated PML strings, control panel messages, and text contained in any of the printer generated printed pages. The order of these languages is the same order that is defined for LOCALIZATION-LANGUAGE. Additional information: Preferred localization language used by the device at boot up time. Setting this object will instruct the device to boot up in that language. This will allow the device to NOT show the generic prompt on the CP display, since the device already knows the language.

This object gives the number of seconds to wait before simulating the button press when CONTROL-PANEL-BUTTON-PRESS is next called. Additional information: This object gives the number of seconds to wait before simulating the button press when CONTROL-PANEL-BUTTON-PRESS is next called.

Returns or changes the Auto Low Power sleep value. The device will go into energy saving Auto Low Power mode after the print engine has been idle for the number of seconds specified by this object. Frida supports values of 300 until 14400 seconds. If the value is invalid then it will return status of PML_Status_ErrUnsupValue and will not issue command to the engine. Additional information: Returns or changes the Auto Low Power sleep value. The device will go into energy saving Auto Low Power mode after the print engine has been idle for the number of seconds specified by this object. The product supports values of 0 (Off), 60 (1 minute), 900 (15 minutes), 1800 (30 minutes), 3600 (1 hour), and 7200 (2 hours). If the value is invalid then it will return a status of PML_ERROR_INVALID_OR_UNSUPPORTED_VALUE and will not issue a command to the engine.

This object is used to disengage the pressure on the fuser to prevent roller marks on the fuser, which can occur when the pressure is engaged for long periods of time. Additional information: This object is used to disengage the pressure on the fuser to prevent roller marks on the fuser, which can occur when the pressure is engaged for long periods of time.

This object returns or sets the display contrast setting if the control panel has a display and it supports contrast adjustment. The setting Is stored in NVRAM, so the value is saved over power cycles. Additional information: This object returns or sets the display contrast setting if the control panel has a display and it supports contrast adjustment. The setting is stored in NVRAM, so the value is saved over power cycles.

Enable or disable an optional low speed calibration. This calibration will allow the device to obtain accurate data for use with low speed print modes. Additional information: Enable or disable an optional low speed calibration. This calibration will allow the device to obtain accurate data for use with low speed print modes.

This PML object is used by HP SW drivers to signal the printer that a job is coming, and to start the warm-up process early.The effect of warming up early will reduce the First Page Out time. Additional information: This PML object is used by HP SW drivers to signal the printer that a job is coming, and to start the warm-up process early.The effect of warming up early will reduce the First Page Out time.

This PML object is used by HP SW to enable/disable the printer to send the signal of warm-up process early to engine. The effect of warming up early will reduce the First Page Out time. Additional information: This PML object is used by HP SW to enable/disable the printer to send the signal of warm-up process early to engine. The effect of warming up early will reduce the First Page Out time.

Localization language used by the device for device generated PML strings, control panel messages, and text contained in any of the printer generated printed pages. The order is the same order that is defined in MIO. Since the MIO values start at zero, one has been added to each value.

Indicates if any of the sub-systems in the printer are not ready. A sub-system is not ready if the sub-system is unable to perform its function until some sort of intervention occurs. If there are no items in the NOT- READY-PRINTER collection (i.e. no bits are set), then all printer sub- systems are ready. Each sub-system has a sub-system specific not ready object. If a sub-system specific not ready object contains any items, then the associated item will be in the NOT-READY collection.

Indicates if the hardware controller sub-system in the device is not ready. If there are no items in the collection (i.e. no bits are set), then the hardware controller sub-system is ready. If there is an item present, then the item indicates what is causing the hardware controller sub-system to be not ready. If the cControllerFailure item is in the collection, then a hardware error was detected on the main controller PC board, sometimes called the formatter or the logic broad. Example controller hardware errors include DRAM controller failure, clock failure, memory parity error, and ROM CRC error. The cFirmwareFailure item is in the collection if a firmware/software error was detected. Device specific detailed error information can be retrieved from the error log objects, if the device supports those objects. The POS will list which device failures cause each item to be included in the collection. Additional information: A controller failure occurrence will set the cControllerFailure bit (bit 1). The controller failures are: 62.X Service, 63 Service, 65 Service, 67 Service, 68 Service, and 68 Error. A SIMM failure occurrence will set the cSIMMFailure bit (bit 2). The SIMM failures are 61.X Service, 53-XY-ZZ Error, and 72 Service. A DISK failure occurrence will set the cATFailure bit (bit 3). The DISK failure is FS DISK FAILURE.

Indicates if any of the sub-systems in the device are not idle. The I/O source sub-system is considered not idle if there is unprocessed PDL data in the device. The PDL processing sub-system is considered not idle if the device is processing a print job. The print engine destination sub-system is considered not idle if media is moving (i.e. the device is printing). [other text here describing what causes the other sub-systems to be considered not idle].

To bring the PDL processing sub-system on or off line. If the device is a printer, then the printer does not process print job data when the printer is off line. PML communication persists. Additional information: When the printer is in the Offline state, printing will stop as soon as possible (no more sheets of media are pulled from input trays). The I/O is taken offline also. Setting to eOnline has the following affect: Printer will immediately go to or remain in the Online state; <noError> status is returned. If the printers current state is Offline with a pending error condition that prevents the printer from going to the Online state, the printer will remain in the Offline state; <genErr> status is returned Setting to eOffline has the following affect: Printer will immediately go to or remain in the Offline state; <noError> status is returned. If pages are being printed, those pages will complete with the printer in the Offline state. Setting to eOfflineAtEndOfJob has the following affect: If not in a job or already in the Offline state, the printer will immediately go to or remain in the Offline state; <noError> status is returned. If in a job and the current state is Online, the printer will remain in the Online state, with the value of this object as eOfflineAtEndOfJob, until the end of the job; <noError> status is returned. At the end of the job, the printer goes to the Offline state and the value of this object becomes eOffline. Setting this object to eOffline or eOnline before the end of the job causes the action for that value to be taken immediately.

A device can support a class of errors called continuable errors. When a continuable error is encountered, the device requires a continue event to occur before the device will continue operation. One continue event is setting the CONTINUE object to eInitiateAction. Devices can support other continue events, like auto-continue. A continue event causes the continuable error to be acknowledged, thus allowing the device to continue. Each device needs to list the continuable errors. If the device doesnt currently have an unacknowledged continuable error, the response will contain <genErr>. Additional information: See the CLEARABLE-WARNING and AUTO-CONTINUE objects for the errors that this object will clear.

Indicates if the device will automatically continue after encountering a continuable error. If AUTO- CONTINUE is set to eOn, the device will automatically generate continue event to acknowledge continuable errors. If AUTO-CONTINUE is set to eOff, then some other continue event will have to acknowledge the continuable error. Additional information: If this is set to eOn the device displays an error message and goes offline for ten seconds. After ten seconds the printer automatically returns to the online state. If this is set to eOff then the device displays an error message and goes offline. It remains offline until the operator presses the GO key or until the CONTINUE object is set. If the printer is not idle, the new value may not take effect until a job boundary is reached. If a get is done on this object before the job boundary is reached, the value last set will be returned.

Identifies the date that the device was installed. The format of the string is YYYYMMDDHHmmZ. Where: YYYY is the year. MM is the month (1-12). DD is the day (1-31). HH is the hour of the day (0-23). mm are the minutes (0-59). Z designates Greenwich Mean Time; if Z not specified, value is local time. Device POS must specify the conditions for setting this object. Additional information: Identifies the date that the device was installed. The format of the string is YYYYMMDDHHmmZ. Where: YYYY is the year. MM is the month (1-12). DD is the day (1-31). HH is the hour of the day (0-23). mm are the minutes (0-59). Z designates Greenwich Mean Time; if Z not specified, value is local time. On Products without a real-time clock this object has the inital value of INVALID. While in the invalid state the object may written to. Once the initial install date has been written a new intall date can not be written without resetting the object to INVALID. The behavior on products with real-time clocks is different. The object is set to the initial real-time clock value, usually this is 199000300000. Manufacturing sets the real-time clock to the correct date and sets the INSTALL-DATE to INVALID. Then when the customer turns on the printer for the first time the install date is reset.

Setting to eTrue causes all user NVRAM settings to factory default settings. May also perform POWER-ON- RESET functionality thus loosing print job data. The POS will list which objects are effected by a user NVRAM reset. Some items are NVRAM settings, but not user controllable, so this action may not cause all of NVRAM to be reset. Some examples of NVRAM settings that may not be affected are page count, internally used pen information, line configuration information, etc. Additional information: Setting to eTrue returns the NVRAM items listed below to their factory default values. Performs the same function as the MENU RESET function supported by the control panel except when printer is in Offline state, setting this OID to eTrue will not take the printer to the Online state. DEFAULT-COPIES DEFAULT-MEDIA-SIZE DEFAULT-ORIENTATION DEFAULT-LINES-PER-PAGE DEFAULT-MANUAL-FEED DEFAULT-RET DEFAULT-PRINT-QUALITY PCL-DEFAULT-FONT-SOURCE PCL-DEFAULT-FONT-NUMBER PCL-DEFAULT-FONT-HEIGHT PCL-DEFAULT-FONT-WIDTH PCL-DEFAULT-SYMBOL-SET DEFAULT-VERTICAL-BLACK-RESOLUTION DEFAULT-HORIZONTAL-BLACK-RESOLUTION DEFAULT-PDL CONTEXT-SENSITIVE-PDL-SELECTION ENERGY-STAR IO-TIMEOUT DEFAULT-PAGE-PROTECT POSTSCRIPT-JAM-RECOVERY (PostScript installed) POSTSCRIPT-PRINT-ERRORS (PostScript installed)

A C structure containing the following fields: typedef struct { ubyte yr; /* year: 0 to 99 */ ubyte mon; /* month: 1 to 12 */ ubyte day; /* day: 1 to 31 */ ubyte wday; /* Day of week: 1 to 07 */ ubyte hr; /* hour: 0 to 23 */ ubyte min; /* minute: 0 to 59 */ ubyte sec; /* second: 0 to 59 */ } date_t; where ubyte is an unsigned byte (0-255).

Indicates the number of characters displayable on each row of the printers display.

Indicates the number of rows displayable on the printers display.

If this object is set to eAuto, and the device has an IP address, the IP address of the device will be shown with the READY message. If this object is set to eOff, the IP address will not be shown.

First part of the first line of the printers status message. Additional information: In the Offline state, device only returns 00 OFFLINE and not the actual content of control panel display.

Identifies total amount of RAM, in bytes, available to the controller for general computing.

Indicates if any of the sub-systems in the device in a warning condition. A warning condition exists if the sub-system is useable, but not at its highest state of functionality.

Indicates if the hardware controller sub-system in a warning condition.

Controls front-panel time display format. Set to eTimeDisplayTwelveHour for AM/PM display. Set to eTimeDisplayTwentyFourHour for military-type display.

The number of seconds the device waits after a job related continuable error occurs before automatically continuing. An example job related continuable error is the job requesting a media size that is not available. After the timeout expires, the device will continue processing the job as if a continue event occurred, such as the front panel continue key being pressed. If the value is -1, the device does not automatically continue after a job related continuable error occurs. If the value is 0, the device immediately continues. If the value is greater than 0, the value represents the timeout value in seconds. Additional information: This object is used only for media requests (size and/or name). LaserJet 4050 Series supports any value in the range of -1 to 3600. Setting to a value outside of that range causes the printer to substitute a value (listed below) and to return <noError> status. The values are as follow: <-1 snaps to -1 >3600 snaps to 3600 (60 minutes) The action that occurs when this timeout expires is explained by JOB-INPUT-AUTO-CONTINUE-MODE. It is not the same as the CONTINUE object being set to eInitiateAction or the Select key being pressed on the control panel. See the CONTINUE object description for information on the actions that occur for those conditions. The data for this object is stored in NVRAM.

Returns or sets the device behavior when the desired media is not currently available. cCancelJob - The device cancels the job. The device POS should explain what happens if this item is not the only item in the collection. cAutoMediaSizeOverride - The device is allowed to substitute a different size media. cAutoMediaNameOverride - The device is allowed to substitute a different media name. Additional information: If cCancelJob is set, the current print job will be canceled regardless of other item settings. At least one bit of the collection must be set; setting this object to zero will cause a status of <badValue> to be returned. This object applies to all media requests, including Manual Feed Requests. This object describes the action that is performed when the JOB-INPUT-AUTO-CONTINUE-TIMEOUT expires. The action performed by the CONTINUE object being set to eInitiateAction or the GO key being pressed on the control panel may cause different actions. See the CONTINUE object description for information on the actions that occur for those conditions. The data for this object is stored in NVRAM.

The string displayed on the devices front panel in place of the printers built-in background status string. An example built-in background status string is 00 READY. Additional information: The display size for the LaserJet 4050 Series printers is 2 X 16. The value of this object and the current value of BACKGROUND-STATUS-MSG-LINE2-PART1 are displayed together on the 2-line display, but they must be set independently. If line 2 has been set, and the next message to be displayed only requires line 1, BACKGROUND-STATUS-MSG-LINE2-PART1 must be set to the null string to clear it. This object allows a message to be displayed when it is the highest priority message. Setting this object does not guarantee the message will be displayed; and reading it returns the value last written, not the currently displayed message (use prtConsoleDisplayBufferText to read the display). The priority assigned for displaying this message is one lower than the READY message. In other words, the only message that can be replaced by these objects is the READY message. To clear the message, write a null string to both this object and BACKGROUND-STATUS-MSG-LINE2-PART1.

The string displayed on the devices front panel in place of the printers built-in background status string. An example built-in background status string is 00 READY. Additional information: See BACKGROUND-STATUS-MSG-LINE1-PART1

Setting this object clears all the entries in the error log sub-tree. Additional information: Setting this object removes all errors that have been stored in the printers non-volatile memory.

Returns or sets the time that the printer will wait after an output bin becomes full and the printer is trying to deliver a sheet of media to that output bin. When the timeout expires, the job is processed according to the OUTBINn-OVERRIDE-MODE. A value of -1 indicates that the printer will wait for a continue event. A non- negative value is the number of seconds to wait. Additional information: A value of zero means to continue immediately. The value of this object is stored in NVRAM, so it is maintained across a power cycle. The data for this object is stored in NVRAM.

Indicates that the printer can create multiple, collated originals of a job and shows the level of support for this capability. cCollatedOriginals - The printer can create multiple collated originals, or mopies. This is the base functionality required by the other collection items. cProofAndHold - The printer saves a copy of the job while printing the first mopy. Later, this held job can be released and the rest of the mopies will print. cSecurityPrint - The printer spools the job and holds the job until the user releases the job by entering a password at the printers control panel. cAutoHighlight - The printer prints the job a number of times with a mail distribution list prepended to each job. A different mailing address is highlighted on each mopy. cCollatedAtSpeed - The printer can create multiple collated copies where all copies after the original are printed at engine speed. Additional information: Indicates that the printer can create multiple, collated originals of a job and shows the level of support for this capability. cCollatedOriginals - The printer can create multiple collated originals, or mopies. This is the base functionality required by the other collection items. None of them are supported by Jonah. Without disk, this object will not exist. This will be set at boot-up initialization. If the disk fails, in any way, then the disk error functionality will handle the situation. The value of this object will be: !cCollatedOriginals - Only FLASH installed cCollatedOriginals - IDE is installed combined with/without FLASH cCollatedOriginals - RAMDISK is On combined with/without FLASH

Error status of the configuration download session. POS should indicate the actual error values reserving value 0 as NO ERROR. Additional information: A value of 0 indicates NO ERROR.

Error status of the configuration upload session. POS should indicate the actual error values reserving value 0 as NO ERROR. Additional information: A value of 0 indicates NO ERROR.

The list of languages supported by the device. The languages are primarily, but not limited to, two character codes from ISO 639, each separated by a comma character. Additional information: This string will always be in the Roman-8 character set. See prtLocalizationLanguage for details about each language value.

The list of countries supported by the device. The countries are primarily, but not limited to, two character codes from ISO 3166, each separated by a comma character. Additional information: This string will always be in the Roman-8 character set. See prtLocalizationCountry for details about each country value.

Returns the amount of memory, in bytes, that the device has available for job-related processing or resources. Also known as driver work space (DWS) memory.

Writing this object simulates pressing a button on the control panel.

Set developer motor cams in the position needed for shipping the cartridges installed in the printer if set to eTrue. Additional information: Notifies the engine that it needs to change its shipping state.

The devices MAC address. Additional information: The devices MAC address.

This object allows the user to view whether the extended print modes have been modified from their default settings. Additional information: This object allows the user to view whether the extended print modes have been modified from their default settings.

Identifies the device model number as listed in the HP corporate price list (e.g. C2121A for DeskJet 500C). The string is as specific as possible. Products should note in POS if the model number on the CPL changes but the device reports the previous model number. If the model number changes based on the installed options, the POS should indicate if only the base model number is returned, or if the device senses the installed options and returns the correct model number. If possible, encode the model number in a symbol set (like Roman-8) that matches the ASCII character set and limit the characters used to ASCII characters. Additional information: The value of this object does not change based on the installed options. The default of this object is the same on all LaserJet 4050 Series printers.

Identifies the device model name (e.g. DeskJet 1200C). The string is as specific as possible. Capitalization and spacing should match family naming conventions. Products should note in POS if the model name on the HP corporate price list changes but the device reports the previous device name. If the model name changes based on the installed options, the POS should indicate if only the base model name is returned, or if the device senses the installed options and returns the correct model name. If possible, encode the model name in a symbol set (like Roman-8) that matches the ASCII character set and limit the characters used to ASCII characters. Additional information: Since the value of this object is frequently used in displaying a list of printers, it is kept relatively short in case systems have limited width for their display area. The model name does not change based on sensing of installed options.

Identifies the serial number for the device. If the SERIAL-NUMBER object is set by the user, then setting the object does not need to be protected. If the SERIAL-NUMBER object is set at the factory, then the SERVICE-PASSWORD object must be set correctly before the SERIAL-NUMBER object is writable. If this is a writable object, the POS should indicate the maximum supported string length. If possible, encode the serial number in a symbol set (like Roman-8) that matches the ASCII character set and limit the characters used to ASCII characters. Additional information: This value IS AFFECTED BY NVRAM resets, it is set to the default value of XXXXXXXXXX, when a NVRAM init is done.

Identifies the base system firmware date code. The date code will be encoded in the yyyymmdd format. There may be several versions of the base system firmware. The date code associated with the version of the base system firmware that is being used is reported. There may be other date code objects for other specific modules such as fonts, localization modules, etc.; these other datecode objects are device specific.

This identifies the system code firmware ROM revision code. The format for a revision is major_revision.minor_revision. There may be other ROM revision code objects for other specific ROMs such as font ROMs, localization ROMs, etc; these other ROM revision code objects are device specific.

CCITT senders station id (ex. 08-396-4122).

name for the fax device (ex. HP R&D).

User defined device name. The POS should indicate the maximum supported string length. If the user entered string is too long, the device will store as much as possible and will return the <noError>. Additional information: The maximum supported string length is 32 characters. If the user entered string is too long, the device will store the first 32 characters and will return the <noError> status.

User defined device location. The POS should indicate the maximum supported string length. If the user entered string is too long, the device will store as much as possible and will return the <noError>. Additional information: The maximum supported string length is 16 characters. If the user entered string is too long, the device will store the first 16 characters and will return the <noError> status.

User defined asset number. The POS should indicate the maximum supported string length. If the user entered string is too long, the device will store as much as possible and will return the <noError>. Additional information: The maximum supported string length is 8 characters. If the user entered string is too long, the device will store the first 8 characters and will return the <noError> status.

User defined string containing the name of the person or group that is responsible for the device. The POS should indicate the maximum supported string length. If the user entered string is too long, the device will store as much as possible and will return the <noError>. Additional information: User defined system contact. The maximum supported string length is 16 characters. If the user entered string is too long, the device will store as much as possible and will return the <noError> status.

The fax device line interface unit (LIU) identifier. The LIU number identifies the telephone system electrical characteristics supported by this device. Additional information: In this LaserJet MFP this value is stored in 3 bits on the LIU.

Returns an indication of the type of option installed in SIMM slot 1. eEmpty means the device did not detect any option installed in the interface slot. eUnknown means the device doesnt recognize the installed option. eUnSupported means the device recognizes the installed option, but does not support the option. eReadOnlyMemory means the installed option contains ROM Ics. eVolatileRandomAccessMemory means the installed option contains RAM ICs that loose data when the power is turned off. eNonVolatileRandomAccessMemory means that the installed option contains RAM ICs that do not loose data when the power is turned off. eFlashMemory means that the installed option contains a type of non-volatile RAM that needs to be erased before it can be written. eDiskDrive means the installed option contains a disk drive. eRamRom means the installed option contains both volatile random access memory and read only memory. eInputPHD means the installed option is an input paper handling device. eOutputPHD means the installed option is an output paper handling device. eIOCard means the installed option is an I/O card. Additional information: This object is used for describing DIMMs instead of SIMMs on LaserJet 4050 Series. eRamRom is used to denote LaserJet 4050 Seriess combo simm.

Returns an indication of the capacity of the SIMM installed in SIMM slot 1. The capacity is dependent on the type of option, as indicated by the SIMM1-TYPE object. This object has no meaning if the installed option type is eUnknown or eReadOnlyMemory. This object contains the size, in bytes, if the installed option type is eVolatileRandomAccessMemory, eNonVolatileRandomAccessMemory, eFlashMemory, or eDiskDrive. If the type of the installed option is eRamRom, this object contains the size, in bytes, of the random access memory. If the type of the installed option is eInputPHD, the capacity indicates the number of input trays supported by the installed option. If the type of the installed option is eOutputPHD, the capacity indicates the number of output bins supported by the installed option. If the type of the installed option is eIOCard, the capacity indicates the number of logical I/O ports supported by the I/O card. Additional information: Returns an indication of the capacity of the installed option in bytes. This object is not supported unless the SIMM1-TYPE type is eVolatileRandomAccessMemory, eRamRom, or eFlashMemory. For eRamRom only the size of the Ram portion of the SIMM is returned.

Returns an indication of the type of option installed in Bank 1 of SIMM slot 1. See SIMM1-TYPE for a description. Additional information: This object is used for describing the type of DIMM banks. Each physical DIMM slot has up to 2 banks.

Returns an indication of the capacity of Bank 1 of the SIMM installed in SIMM slot 1. See SIMM1-CAPACITY for a description. Additional information: Returns an indication of the capacity of the installed bank option in bytes. This object is not supported unless the SIMM1-BANK1-TYPE type is eReadOnlyMemory, eFlashMemory, eEDORandomAccessMemory, eSDRandomAccessMemory, eSRandomAccessMemory, or eFPMRandomAccessMemory.

Returns an indication of the type of option installed in Bank 2 of SIMM slot 1. See SIMM1-TYPE for a description. Additional information: This object is used for describing the type of DIMM banks. Each physical DIMM slot has up to 2 banks.

Returns an indication of the capacity of Bank 2 of the SIMM installed in SIMM slot 1. See SIMM1-CAPACITY for a description. Additional information: Returns an indication of the capacity of the installed bank option in bytes. This object is not supported unless the SIMM1-BANK2-TYPE type is eReadOnlyMemory, eFlashMemory, eEDORandomAccessMemory, eSDRandomAccessMemory, eSRandomAccessMemory, or eFPMRandomAccessMemory.

Returns an indication of the type of option installed in SIMM slot 2. See SIMM1-TYPE for a description. Additional information: This object is used for describing DIMMs instead of SIMMs on LaserJet 4050 Series. eRamRom is used to denote LaserJet 4050 Seriess combo simm.

Returns an indication of the capacity of the SIMM installed in SIMM slot 2. See SIMM1-CAPACITY for a description. Additional information: This object is used for describing DIMMs instead of SIMMs on LaserJet 4050 Series. Returns an indication of the capacity of the installed option in bytes. This object is not supported unless the SIMM2-TYPE type is eVolatileRandomAccessMemory, eRamRom, or eFlashMemory. For eRamRom only the size of the Ram portion of the SIMM is returned.

Returns an indication of the type of option installed in Bank 1 of SIMM slot 2. See SIMM1-TYPE for a description. Additional information: This object is used for describing the type of DIMM banks. Each physical DIMM slot has up to 2 banks.

Returns an indication of the capacity of Bank 1 of the SIMM installed in SIMM slot 2. See SIMM1-CAPACITY for a description. Additional information: Returns an indication of the capacity of the installed bank option in bytes. This object is not supported unless the SIMM2-BANK1-TYPE type is eReadOnlyMemory, eFlashMemory, eEDORandomAccessMemory, eSDRandomAccessMemory, eSRandomAccessMemory, or eFPMRandomAccessMemory.

Returns an indication of the type of option installed in Bank 2 of SIMM slot 2. See SIMM1-TYPE for a description. Additional information: This object is used for describing the type of DIMM banks. Each physical DIMM slot has up to 2 banks.

Returns an indication of the capacity of Bank 2 of the SIMM installed in SIMM slot 2. See SIMM1-CAPACITY for a description. Additional information: Returns an indication of the capacity of the installed bank option in bytes. This object is not supported unless the SIMM2-BANK2-TYPE type is eReadOnlyMemory, eFlashMemory, eEDORandomAccessMemory, eSDRandomAccessMemory, eSRandomAccessMemory, or eFPMRandomAccessMemory.

Returns an indication of the type of option installed in SIMM slot 3. See SIMM1-TYPE for a description.

Returns an indication of the capacity of the SIMM installed in SIMM slot 3. See SIMM1-CAPACITY for a description. Additional information: This object is used for describing DIMMs instead of SIMMs on LaserJet 4050 Series. Returns an indication of the capacity of the installed option in bytes. This object is not supported unless the SIMM3-TYPE type is eVolatileRandomAccessMemory, eRamRom, or eFlashMemory. For eRamRom only the size of the Ram portion of the simm is returned.

Returns an indication of the type of option installed in Bank 1 of SIMM slot 3. See SIMM1-TYPE for a description. Additional information: This object is used for describing the type of DIMM banks. Each physical DIMM slot has up to 2 banks.

Returns an indication of the capacity of Bank 1 of the SIMM installed in SIMM slot 3. See SIMM1-CAPACITY for a description. Additional information: Returns an indication of the capacity of the installed bank option in bytes. This object is not supported unless the SIMM3-BANK1-TYPE type is eReadOnlyMemory, eFlashMemory, eEDORandomAccessMemory, eSDRandomAccessMemory, eSRandomAccessMemory, or eFPMRandomAccessMemory.

Returns an indication of the type of option installed in Bank 2 of SIMM slot 3. See SIMM1-TYPE for a description. Additional information: This object is used for describing the type of DIMM banks. Each physical DIMM slot has up to 2 banks.

Returns an indication of the capacity of Bank 2 of the SIMM installed in SIMM slot 3. See SIMM1-CAPACITY for a description. Additional information: Returns an indication of the capacity of the installed bank option in bytes. This object is not supported unless the SIMM3-BANK2-TYPE type is eReadOnlyMemory, eFlashMemory, eEDORandomAccessMemory, eSDRandomAccessMemory, eSRandomAccessMemory, or eFPMRandomAccessMemory.

Returns an indication of the type of option installed in SIMM slot 4. See SIMM1-TYPE for a description.

Returns an indication of the capacity of the SIMM installed in SIMM slot 4. See SIMM1-CAPACITY for a description. Additional information: Returns an indication of the capacity of the installed option in bytes. This object is not supported unless the SIMM4-TYPE type is eVolatileRandomAccessMemory.

Returns an indication of the type of option installed in SIMM slot 5. See SIMM1-TYPE for a description.

Returns an indication of the capacity of the SIMM installed in SIMM slot 5. See SIMM1-CAPACITY for a description. Additional information: Returns an indication of the capacity of the installed option in bytes. This object is not supported unless the SIMM5-TYPE type is eVolatileRandomAccessMemory.

Returns an indication of the type of option installed in SIMM slot 6. See SIMM1-TYPE for a description.

Returns an indication of the capacity of the SIMM installed in SIMM slot 6. See SIMM1-CAPACITY for a description. Additional information: Returns an indication of the capacity of the installed option in bytes. This object is not supported unless the SIMM6-TYPE type is eVolatileRandomAccessMemory.

Returns an indication of the type of option installed in SIMM slot 7. See SIMM1-TYPE for a description.

Returns an indication of the capacity of the SIMM installed in SIMM slot 7. See SIMM1-CAPACITY for a description. Additional information: Returns an indication of the capacity of the installed option in bytes. This object is not supported unless the SIMM7-TYPE type is eVolatileRandomAccessMemory.

Returns an indication of the type of option installed in SIMM slot 8. See SIMM1-TYPE for a description.

Returns an indication of the capacity of the SIMM installed in SIMM slot 8. See SIMM1-CAPACITY for a description. Additional information: Returns an indication of the capacity of the installed option in bytes. This object is not supported unless the SIMM8-TYPE type is eVolatileRandomAccessMemory.

Identifies the AT model number. If the disk was manufactured by HP, then the model number is the one listed in the HP corporate price list. If possible, encode the model number in a symbol set (like Roman-8) that matches the ASCII character set and limit the characters used to ASCII characters. Additional information: The model number is obtained from the disk using the IDE (Intelligent Drive Electronics) Identify command. This objects is only supported if a disk is installed. Returns <noSuchName> status if attempting to perform a Get on this OID with no disk installed. Returns <noSuchName> status if attempting to perform a Set, EnableTrap, or DisableTrap on this OID with no disk installed.

Returns product information identifying the AT storage device. Example: C3014A Additional information: The product information is obtained from the disk using the IDE (Intelligent Drive Electronics) Identify command. This objects is only supported if a disk is installed. Returns <noSuchName> status if attempting to perform a Get on this OID with no disk installed. Returns <noSuchName> status if attempting to perform a Set, EnableTrap, or DisableTrap on this OID with no disk installed.

Returns information describing the manufacture of this particular AT. May include serial number and firmware revision. Additional information: Returns the model number, serial number, and firmware revision of the installed disk. This information is obtained from the disk using the IDE (Intelligent Drive Electronics) Identify command. Example: HP C3014A JP932412W9 K2A4A059. This objects is only supported if a disk is installed. Returns <noSuchName> status if attempting to perform a Get on this OID with no disk installed. Returns <noSuchName> status if attempting to perform a Set, EnableTrap, or DisableTrap on this OID with no disk installed.

Returns an indication of the type of option installed in this particular AT interface. See SIMM1-TYPE for an explanation of the enumerations. Additional information: eEmpty means the device did not detect any AT. eDiskDrive means the AT contains a disk drive.

Returns an indication of the capacity of the installed option. See SIMM1-CAPACITY for an explanation of the meaning of the value of this object. Additional information: This object contains the size, in bytes, of the installed disk option. This objects is only supported if a disk is installed. Returns <noSuchName> status if attempting to perform a Get on this OID with no disk installed. Returns <noSuchName> status if attempting to perform a Set, EnableTrap, or DisableTrap on this OID with no disk installed.

Returns product information identifying the I/O card. Example: XXXX

Returns information describing the manufacture of the I/O card installed in MIO/EIO slot 1. May include serial number and firmware revision. Additional information: The format of the string returned is determined by the manufacturer of the EIO device. There is no standard for content of the string.

Returns an indication of the type of option installed in MIO/EIO slot 1. See SIMM1-TYPE for an explanation of the enumerations.

Returns product information identifying the I/O card. Example: XXXX

Returns information describing the manufacture of the I/O card installed in MIO/EIO slot 2. May include serial number and firmware revision. Additional information: The format of the string returned is determined by the manufacturer of the EIO device. There is no standard for content of the string.

Returns an indication of the type of option installed in MIO/EIO slot 2. See SIMM1-TYPE for an explanation of the enumerations.

Returns product information identifying the I/O card. Example: XXXX

Returns information describing the manufacture of the I/O card installed in MIO/EIO interface 3. May include serial number and firmware revision. Additional information: The format of the string returned is determined by the manufacturer of the EIO device. There is no standard for content of the string.

Returns an indication of the type of option installed in MIO/EIO interface 3. See SIMM1-TYPE for an explanation of the enumerations.

Returns product information identifying the I/O card. Example: XXXX

Returns information describing the manufacture of the I/O card installed in MIO/EIO interface 4. May include serial number and firmware revision

Returns an indication of the type of option installed in MIO/EIO interface 4. See SIMM1-TYPE for an explanation of the enumerations

Returns product information identifying the PHD device. Example: XXXX

Returns information describing the manufacture of this particular PHD. May include serial number and firmware revision.

Returns an indication of the type of option installed as PHD 1. See SIMM1-TYPE for an explanation of the enumerations. Additional information: Returns an indication of whether or not the envelope feeder is installed on the printer. A value of eEmpty means that the envelope feeder is not installed.

Returns an indication of the capacity of the installed option. See SIMM1-CAPACITY for an explanation of the meaning of the value of this object. Additional information: The LaserJet 4000 Series envelope feeder has a single tray.

Returns product information identifying PHD device 2. Additional information: If at least one (1) external paper handling device is attached to the printer, then this object will exist, otherwise <noSuchName> should be returned. This object returns product information about the first paper handling device in the device chain.

Returns information describing the manufacture of PHD 2. May include serial number and firmware revision. Additional information: If at least one (1) external paper handling device is attached to the printer, then this object will exist, otherwise <noSuchName> should be returned. This object returns the name of the manufacturer of the first paper handling device.

Returns an indication of the type of option installed in PHD interface 2. See SIMM1-TYPE for an explanation of the enumerations. Additional information: If at least one (1) external paper handling device is attached to the printer, then this object will exist, otherwise <noSuchName> should be returned. This object returns whether the device is an input device, an output device, or an unknown device which may be developed in the future.

Returns an indication of the capacity of the installed option. See SIMM1-CAPACITY for an explanation of the meaning of the value of this object. Additional information: If at least one (1) external paper handling device (EPHD) is attached to the printer, then this object will exist, otherwise <noSuchName> should be returned. This object returns the number of input trays or output bins, depending the the device type (see PHD2-TYPE) for the first EPHD in the device chain.

Returns product information identifying PHD device 3. Additional information: If at least two (2) external paper handling devices are attached to the printer, then this object will exist, otherwise <noSuchName> should be returned. This object returns product information about the second paper handling device in the device chain.

Returns information describing the manufacture of PHD 3. May include serial number and firmware revision. Additional information: If at least two (2) external paper handling devices are attached to the printer, then this object will exist, otherwise <noSuchName> should be returned. This object returns the name of the manufacturer of the second paper handling device.

Returns an indication of the type of option installed in PHD interface 3. See SIMM1-TYPE for an explanation of the enumerations. Additional information: If at least two (2) external paper handling devices are attached to the printer, then this object will exist, otherwise <noSuchName> should be returned. This object returns whether the second device is an input device, an output device, or an unknown object which may be developed in the future.

Returns an indication of the capacity of the installed option. See SIMM1-CAPACITY for an explanation of the meaning of the value of this object. Additional information: If at least two (2) external paper handling devices (EPHD) are attached to the printer, then this object will exist, otherwise <noSuchName> should be returned. This object returns the number of input trays or output bins, depending the the device type (see PHD3-TYPE) for the second EPHD in the device chain.

Returns product information identifying PHD device 4. Additional information: If at least three (3) external paper handling devices are attached to the printer, then this object will exist, otherwise <noSuchName> should be returned. This object returns product information about the third paper handling device in the device chain.

Returns information describing the manufacture of PHD 4. May include serial number and firmware revision. Additional information: If at least three (3) external paper handling devices are attached to the printer, then this object will exist, otherwise <noSuchName> should be returned. This object returns the name of the manufacturer of the third paper handling device.

Returns an indication of the type of option installed in PHD interface 4. See SIMM1-TYPE for an explanation of the enumerations. Additional information: If at least three (3) external paper handling devices are attached to the printer, then this object will exist, otherwise <noSuchName> should be returned. This object returns whether the third device is an input device, an output device, or an unknown device which may be developed in the future.

Returns an indication of the capacity of the installed option. See SIMM1-CAPACITY for an explanation of the meaning of the value of this object. Additional information: If at least three (3) external paper handling devices (EPHD) are attached to the printer, then this object will exist, otherwise <noSuchName> should be returned. This object returns the number of input trays or output bins, depending the the device type (see PHD4-TYPE) for the third EPHD in the device chain.

Returns product information identifying PHD device 3. Additional information: If at least four (4) external paper handling devices are attached to the printer, then this object will exist, otherwise <noSuchName> should be returned. This object returns product information about the fourth paper handling device in the device chain.

Returns information describing the manufacture of PHD 5. May include serial number and firmware revision. Additional information: If at least four (4) external paper handling devices are attached to the printer, then this object will exist, otherwise <noSuchName> should be returned. This object returns the name of the manufacturer of the fourth paper handling device.

Returns an indication of the type of option installed in PHD interface 5. See SIMM1-TYPE for an explanation of the enumerations. Additional information: If at least four (4) external paper handling devices are attached to the printer, then this object will exist, otherwise <noSuchName> should be returned. This object returns whether the fourth device is an input device, an output device, or an unknown device which may be developed in the future.

Returns an indication of the capacity of the installed option. See SIMM1-CAPACITY for an explanation of the meaning of the value of this object. Additional information: If at least four (4) external paper handling devices (EPHD) are attached to the printer, then this object will exist, otherwise <noSuchName> should be returned. This object returns the number of input trays or output bins, depending the the device type (see PHD5-TYPE) for the fourth EPHD in the device chain.

Returns product information identifying PHD device 6. Additional information: If at least five (5) external paper handling devices are attached to the printer, then this object will exist, otherwise <noSuchName> should be returned. This object returns product information about the fifth paper handling device in the device chain.

Returns information describing the manufacture of PHD 6. May include serial number and firmware revision. Additional information: If at least five (5) external paper handling devices are attached to the printer, then this object will exist, otherwise <noSuchName> should be returned. This object returns the name of the manufacturer of the fifth paper handling device.

Returns an indication of the type of option installed in PHD interface 6. See SIMM1-TYPE for an explanation of the enumerations. Additional information: If at least five (5) external paper handling devices are attached to the printer, then this object will exist, otherwise <noSuchName> should be returned. This object returns whether the fifth device is an input device, an output device, or an unknown device which may be developed in the future.

Returns an indication of the capacity of the installed option. See SIMM1-CAPACITY for an explanation of the meaning of the value of this object. Additional information: If at least five (5) external paper handling devices (EPHD) are attached to the printer, then this object will exist, otherwise <noSuchName> should be returned. This object returns the number of input trays or output bins, depending the the device type (see PHD6-TYPE) for the fifth EPHD in the device chain.

This object is a OCTET STRING enumeration which the peripheral uses to inform the JetDirect card that the Jet-Direct card embedded web server should display the web proxy configuration settings. The Jet Direct card web server will display the if and only if this object is both implemented and set to eOn. A peripheral may implement this object in order to have another host, like a JetDirect card, include a reference to the peripherals web content. The peripheral will read the proxy configuration using the XIP2 sysInfo Get methods

System variable EWS_REQUEST_CONTROL_PANEL_SUPPPLIES_STATUS requires a PML interface so that WJA can directly access it without needing EWS support for that

This object allows one to get/set the setting of the FIH EXTRA PULSES FEATURE item. This either turns the feature on or off based on customer requirement

Returns the Product ID of a connected USB device as defined in the Standard Device Descriptor of the Universal Serial Bus Specification Version 2.0. The value will be in the range 0..65535.

Writing this object allows a device self test to be started. Reading this object provides an indication what self-test is currently executing, if any. Actual self-test operation is device specific. A self test may not be allowed at any arbitrary time. If the device supports the requested self test, but can not start the execution of the self test when requested, the device will respond with <genErr>. If a non-destructive self test is being started, the device will generate a response before the self test is completed. RECOMMENDATION: If the device is ready (i.e. the NOT- READY-PRINTER object does not contain any items, except maybe being off-line) and is idle (i.e. the NOT-IDLE object does not contain any items), this request should always succeed. This provides a mechanism for driver writers to always determine if the action will succeed or not. Additional information: The eNonDestructiveSelfTest performs limited testing on the printer and its attached paper handling devices. After the self-test is complete a configuration page is printed. The recommended way to cause a configuration page to be printed is to use the PRINT-INTERNAL-PAGE object. Setting this object to eNonDestructiveSelfTest results in a status of <noError> and a value of eNonDestructiveSelfTest being returned. If the printer is not idle (whether printing an external job or printing an internal page), this action will be delayed until the next job boundary. See the PRINT-INTERNAL-PAGE object for more details.

Writing this object to a value other than eNotPrintingAnInternalPage causes the device to attempt to print an internally generated page. Reading this object provides an indication what internally generated page is currently being printed, if any. The actual page is device specific. Some devices may support continuously printing an internally generated page. Setting this object to eNotPrintingAnInternalPage terminates continuously printing internally generated pages. An internally generated page may not be allowed to be printed at any arbitrary time; under what conditions it will succeed or fail is device specific. If the device supports the requested page, but can not start printing the page when requested, the device will respond with <genErr>. RECOMMENDATION: If the device is ready (i.e. the NOT- READY-PRINTER object does not contain any items, except maybe being off-line) and is idle (i.e. the NOT-IDLE object does not contain any items), this request should always succeed. This provides a mechanism for driver writers to always determine if the action will succeed or not. Additional information: Previous products used ePCLDemoPage1ConfigurationPage(300) for the Configuration or Self Test page. This product uses eDeviceDemoPage1ConfigurationPage(3). LaserJet 4050 Series does not support continuously printing a demo page. When this object is set to a valid value, the status returned is <noError> and the value returned is ePrintingAnUnknownInternalPage. If the printer is idle, the page will be printed immediately. If the printer is currently printing another job, the internal page requested will not print until that job is finished. Setting this object to a valid value causes the desired page to be formatted and put in the printers print queue. While the page is being formatted a get on this object will return the value ePrintingAnUnknownInternalPage. Once the page (or pages) is finished being formatted, this object returns a value of eNotPrintingAnInternalPage, even though the page may not have finished being printed. Setting this object multiple times will queue up the requests, but only a limited number will be queued. Once the queue is full, additional requests will be ignored.

Returns or controls how the device will track clearable warnings. A clearable warning indicates a transient event in the device. The device will continue after the transient event occurs. If CLEARABLE-WARNING is eOff, the device does not track clearable warnings. If CLEARABLE-WARNING is eOn, all clearable warnings will be tracked until cleared (acknowledged). If CLEARABLE- WARNING is eJob, a clearable warning generated due to an event that occurs because of the print job being processed will be automatically cleared when the device has finished processing the job. Example clearable warning events include the device altering resolution or page protection due to memory constraints. The POS will document what transient events are treated as clearable warnings. Additional information: If set to eOn, the warning is displayed until the GO key is pressed or the CONTINUE object is set. If set to eJob, the warning is displayed until the end of the job in which it was generated.

Cancels the print job whose ID matches the value written to the CANCEL-JOB object. The host first learns the job ID using the CURRENT-JOB-PARSING-ID command. If the printer has completely processed the job, the printer responds with <badValue>. If the value of the CURRENT-JOB-PARSING-ID is smaller than the value written to the CANCEL-JOB object, then the printer responds with <badValue>. When read, returns the value of the last job ID what was canceled, or -1 to indicate no job has been canceled. Additional information: If the value written matches the ID of a job that is currently being canceled (for any reason), the printer responds with <noError>. LaserJet 4050 Series uses job IDs in the range of 0..32767. Because the ID number can wrap to zero, CURRENT-JOB-PARSING-ID may be smaller than the value written to this object; when this occurs, no error will result as long as the ID is for a currently processing job. This object is write only, so the comment in the general description stating the job ID or -1 will be returned on a read does not apply.

Returns the current value of an object in the job-info sub-tree whose value has changed. Define the object identifier for the object whose value has changed as job-info.required-field.optional-field.job-id. job-info represents the OID prefix of all objects in the job-info sub-tree. Required-field represents the OID field value that follows the job-info prefix. Since some objects in the job-info sub-tree have two OID fields between the job-info prefix and the job-id, the optional-field represents the OID field between the required-field and the job-id field, if present. Using this definition, the format for the JOB-INFO-CHANGE-ID binary value can be described as follows: Bytes 0-3 : required-field Bytes 4-7 : optional-field, or all zeros if there is no optional field Bytes 8-11: Job ID. Bytes 12-n : The value of the object job-info. required-field.optional-field.job-id. All multi-byte values stored in Motorola (big-endian) format, where the most significant byte occurs first. Additional information: LaserJet 4050 Series will use this object to report changes to the job-info-pages-printed and job-info-state objects. The required-field (bytes 0 through 3) will designate whether the change to be reported involves the pages printed (13) or job state (15). The optional-field (bytes 4 through 7) will always be zeroes. The value-field (bytes 12 through 15) will contain the new value for pages printed or job state cast to a 32-bit integer.

The time, in minutes, that the printer will wait before automatically deleting a held job. This allows the printer to automatically clean up jobs that have been forgotten (held but never released). Additional information: This only applies to temporary held jobs, i.e., HOLD=ON or PROOF. This is a global timer that only affects the jobs that are sent after it is set. A value of 0 means never delete the jobs. Setting it to an unsupported value causes the printer to substitute a value (listed below) and to return <noError> status. LaserJet 4050 Series supports values of 0, 60, 240, 1440, and 10080 The values are as follows: <=0 snap to 0 (disabled) >=1 and <=150 snap to 60 (60 minutes) >=151 and <=840 snap to 240 (4 hours) >=841 and <=2880 snap to 1440 (1 day) >=2881 snap to 10080 (1 week)

Contains the printer assigned job identification for the job currently being processed by the processing PDL sub- system. The job ID is a monotonically increasing number. The job ID may be reset to zero at power-up and may roll over to zero after reaching some maximum value. Additional information: A value of -1 is returned when the printer is not parsing a job. When data for a new job is detected, this object is updated (the job may or may not turn out to be a Null Job); however, the trap does not occur until the printer determines that it is not a Null Job. (A job is considered to be a null job if it has no name or job attribute, causes no pages to be printed, and consumes MIN_JOB_SIZE (9) or fewer bytes.) A trapped value will differ from the previous value by one or more. Some job-info- objects are created when the first data bytes are received. If the printer determines that the job is a Null Job, the job-info- objects related to the Null Job are deleted. LaserJet 4050 Series retains the job-info- objects for the MAX_JOBS_IN_LIST (12) most recent jobs that are not Null Jobs. The first job received after power-up will have job ID 1, and the job ID will increment to 32767 before rolling to zero. To distinguish whether a power cycle or a rollover causes a reduction in the job ID value, the object prtGeneralConfigChanges can be watched and if it increments at the same time as the drop is observed in the value of CURRENT-JOB-PARSING-ID, then a power cycle is the most likely cause.

Permits host to specify an action to be applied with a particular fax.

Contains the fax job identification of the fax to be acted upon by the action specified by the object FAXJOB- ACTION.

Indicates sources of the fax image for transmission. Also specifies the temporal order of the data sources. eSrcHostOnly - The fax document images will be wholly downloaded from the host. eSrcScannerOnly - The fax document images originate wholly from the device scanner/ADF subsystem. eSrcHostThenScanner - The fax document is composed of images downloaded from the host and pages from the scanner/ADF subsystem. The host downloaded pages will be faxed first, followed by the pages in the scanner/ADF. eSrcScannerThenHost - The fax document is composed of pages in the scanner/ADF and the images downloaded from the host. The document in the ADF is faxed first, followed by the pages downloaded from the host. wSrcHostThenMemory - The fax document is composed of pages downloaded from the host and images already stored within the device. The fax transmission will contain the host downloaded pages followed by the images in the device memory. eSrcHostToMemoryOnly - Permits fax images to be downloaded into device memory for later use with eSrcHostThenMemory. Additional information: GECKO NOTE: eSrcHostToMemoryOnly is included for development and testing only. eSrcHostToMemoryOnly will not be an allowed value for this object in the released product.

Allows the host to enable or disable duplex printing on a device for the next fax job. Additional information: Allows the host to enable or disable duplex printing on a device for the next fax job.

Contains the device assigned job identification for the current fax downloading job. The job ID is monotonically increasing number. The job ID may be reset to zero or may roll over to zero after reaching some maximum. The maximum value before the rollover should be stated in the POS. Additional information: The maximum value before this object rolls over to 0 is 2,147,483,648. Behavior of this object once the value rolls over to 0 is not specified.

Contains the device assigned job identification for the currently fax reception job. The job ID is monotonically increasing number. The job ID may be reset to zero or may roll over to zero after reaching some maximum. The maximum value before the rollover should be stated in the POS. Additional information: The maximum value before this object rolls over to 0 is 2,147,483,648. Behavior of this object once the value rolls over to 0 is not specified.

Contains the device assigned job identification for the current fax transmission job. The job ID is monotonically increasing number. The job ID may be reset to zero or may roll over to zero after reaching some maximum. The maximum value before the rollover should be stated in the POS. Additional information: The maximum value before this object rolls over to 0 is 2,147,483,648. Behavior of this object once the value rolls over to 0 is not specified.

Contains the device assigned job identification for the current fax upload job. The job ID is monotonically increasing number. The job ID may be reset to zero or may roll over to zero after reaching some maximum. The maximum value before the rollover should be stated in the POS. Additional information: The maximum value before this object rolls over to 0 is 2,147,483,648. Behavior of this object once the value rolls over to 0 is not specified.

Status of receiving fax session 1.

Status of sending fax session 1.

Error status of the fax reception session 1. Additional information: Error status of the fax transmission session 1.

The page number of the fax page currently being transmitted via send fax session 1. Starts with page number 1.

The page number of the fax page currently being received via fax reception session 1. Starts with page number 1.

Represent the number of seconds of phone-connect time for a fax reception session 1.

Represent the number of seconds of phone-connect time for send fax session 1.

Provides applications with the ability to clear or print the fax transaction log. eIdle - no action is occurring on the fax log. eClear - clear the fax log. ePrintLatest - print the latest entry in the fax log. ePrintAll - print all the entries in the fax log. When this object is set to a non-eIdle value by an application, the given action starts. When the action is complete, this object is changed back to eIdle by the device. A hosts request to write this object will be rejected when the object is not eIdle. When eIdle, the host may set the object to any value (including eIdle).

Specifies when fax transaction logs are to be printed.

Contains the first part of this print jobs name. The last OID field for this dynamic object contains the job ID. Additional information: The job name is the string specified by the NAME= parameter of the @PJL JOB command which allows a maximum of 80 characters. The first 40 characters are in this object and the second 40 are in job-info-name2. The symbol set is Roman-8. When jobs are nested, the value assigned to this object is the name provided by the most recent @PJL JOB NAME= command. If no name is provided, a null string is returned.

Contains the second part of this print jobs name. The last OID field for this dynamic object contains the job ID. Additional information: See job-info-name1.

Indicates what printer sub-systems are currently processing this print job. The last OID field for this dynamic object contains the job ID. cSourceSubsystem - some of the job is in the printer I/O subsystem. cProcessingSubsystem - some of the job is in the printer imaging processing subsystem. cDestinationSubsystem - some of the job is being printed. Additional information: For LaserJet 4050 Series, cSourceSubsystem and cProcessingSubsystem will always be set and cleared together. They are set when the beginning of the job is detected, and they are cleared when the end of the job is parsed. A non-printing job will never set cDestinationSubsystem. When a page is ready to be printed (the intermediate has been built and the page is `closed by the personality), cDestinationSubsystem will be set even if a page of a previous job is currently being printed. cDestinationSubsystem remains set until the last page of the job has finished printing. If a page requires extensive processing and allows all the previous pages of a job to complete printing, cDestinationSubsystem will remain set until the last page of the job has finished printing.

Indicates which I/O source, the print job was received over. The value maps to port numbering scheme supported in the DEVICE/SOURCE-SUBSYSTEM/IO/PORTS sub-tree.

Indicates the number of pages processed by the processing subsystem. If neither the cSourceSubsystem or the cProcessingSubsystem items are in the associated JOB-INFO-STAGE object, then this object contains the total number of pages processed for this job. The last OID field for this dynamic object contains the job ID. Additional information: This object is incremented by one when a page is processed (`closed by the personality), regardless of the number of pages that are printed as a result of the single page processed. In other words, it does not matter how many identical copies of a page are printed or no pages may be printed if operating in silent run mode, this count is incremented exactly once. A page is considered processed when all of the input data has been processed for a page (that is, when the intermediate has been produced, and the personality has `closed the page. At this time, the image of the page is not necessarily completely formed.)

Indicates the number of pages printed by the destination subsystem. If non of the cSourceSubsystem, cProcessingSubsystem or cDestinationSubsystem items are in the associated JOB-INFO-STAGE object, then this object contains the total number of pages printed for this job. This value may increase by two each time for duplex jobs. The last OID field for this dynamic object contains the job ID. Additional information: If multiple copies of a page are printed, each copy is counted individually.

Indicates the number of bytes of data processed by the processing subsystem. If neither of the cSourceSubsystem or cProcessingSubsystem items are in the associated JOB-INFO-STAGE object, then this object contains the size of this job, in bytes. The last OID field for this dynamic object contains the job ID. Additional information: This count may be incremented by values other than one as blocks of data are processed; blocks of data (which may be as large as 2K bytes) will be processed in a varying amount of time. During the processing of a job and even when a job completes, an exact count of the number of I/O bytes processed by the job is not necessarily to be expected.

Indicates the state of the job. The last OID field for this dynamic object contains the job ID. eAborted - the print job was aborted. eWaitingForResources - the print job requires resources that are not currently available. Example resources that can cause the job to wait include the print engine or PDL processor being unavailable. The print engine could be unavailable due to paper out, paper jam, staple out, stapler jam, marking agent low, output bin full, etc. The PDL processor could be unavailable due to an off-line condition. Each printer specific object specification should state which conditions cause a job to be waiting for resources and also state which objects can be retrieved by an application to determine the exact cause of a resource being unavailable. ePrinted - the job has printed. The related JOB-INFO- OUTCOME object indicates if any problems were encountered while the job was processed. eRetained - the job can be reprinted. eTerminating - the job was aborted or cancelled and is currently is terminating. eInterrupted - the job has been interrupted. The job can be continued. ePaused - the job has been paused. The job can be continuted. eCancelled - the job has been cancelled. eProcessing - the job is currently being printed normally.

Indicates if any warning or error conditions were encountered while processing the assoicated job. The last OID field for this dynamic object contains the job ID. Additional information: In LaserJet 4050 Series, warnings and errors are not recorded in this object. Although no meaningful information can be obtained from this object, it is kept around for the compatibility needs of existing software.

Indicates which output bins this job has delivered printed pages to. The last OID field for this dynamic object contains the job ID. Additional information: The bins designated by this collection include the printers own output bins as well as the `logical output bins associated with any attached external paper handling devices. (The mapping of the physical output bins of an external paper handling device to its `logical output bins depends on the usage mode of the device. For instance, in `mailbox mode, there is one-to-one correspondence of `logical output bins to physical bins, whereas in `stacker mode, one `logical output bin may map to several physical bins.) Although LaserJet 5000 Series and LaserJet 4000 Series both come with two output bins -- a face-down bin on the top of the device and a face-up bin at the back of the device -- firmware will not provide a means of selecting between the two, nor will it report which of the two gets used. For this reason, bit 0 (cOutbin1) of this collection is being used to designate both of these bins together.

Indicates which physical output bins this job has delivered printed pages to. The last OID field for this dynamic object contains the job ID. Additional information: The output bins designated by the bits of this collection include the standard output bin(s) plus the physical bins of attached external paper handling devices. The configuration (if any) of external paper handling devices will determine the mapping of individual bits in this collection to the physical bins of the devices. For LaserJet 4050 Series (LaserJet 4050), the cOutbin1 is used for Face Down bin, cOutbin2 is used for Face Up bin, and 3-15 are used for the 13 optional output bins (12 plus an extension to the Face Up bin) for backwards compatibility with LaserJet 8000 Series/LaserJet 8100 Series and forwards compatibility with future printers. However, since LaserJet 4050 Series cannot distinguish output going to the Face Up or Face Down bin in the firmware because the diverter can only be moved manually, bit 0 (cOutbin1) is being used to designate both of these bits together. If an external paper handling output device is connected, then bit 2 (cOutbin3) will represent the devices first output bin (and so on).

Returns the value that was set in PJL via the SET JOBATTR= command. Attribute objects are saved sequentially, starting with 1, after the start of a job. If more attributes are set than there are objects to store them, the excess JOBATTR values are ignored. If the corresponding SET JOBATTR= command has not been received when a get is done for this object, a status of <noSuchName> will be returned.

Returns the value that was set in PJL via the SET JOBATTR= command. See JOB-INFO-ATTR-1 for details.

Returns the value that was set in PJL via the SET JOBATTR= command. See JOB-INFO-ATTR-1 for details.

Returns the value that was set in PJL via the SET JOBATTR= command. See JOB-INFO-ATTR-1 for details.

Returns the value that was set in PJL via the SET JOBATTR= command. See JOB-INFO-ATTR-1 for details.

Returns the value that was set in PJL via the SET JOBATTR= command. See JOB-INFO-ATTR-1 for details.

Returns the value that was set in PJL via the SET JOBATTR= command. See JOB-INFO-ATTR-1 for details.

Returns the value that was set in PJL via the SET JOBATTR= command. See JOB-INFO-ATTR-1 for details.

Returns the value that was set in PJL via the SET JOBATTR= command. See JOB-INFO-ATTR-1 for details.

Returns the value that was set in PJL via the SET JOBATTR= command. See JOB-INFO-ATTR-1 for details.

Returns the value that was set in PJL via the SET JOBATTR= command. See JOB-INFO-ATTR-1 for details.

Returns the value that was set in PJL via the SET JOBATTR= command. See JOB-INFO-ATTR-1 for details.

Returns the value that was set in PJL via the SET JOBATTR= command. See JOB-INFO-ATTR-1 for details.

Returns the value that was set in PJL via the SET JOBATTR= command. See JOB-INFO-ATTR-1 for details.

Returns the value that was set in PJL via the SET JOBATTR= command. See JOB-INFO-ATTR-1 for details.

Returns the value that was set in PJL via the SET JOBATTR= command. See JOB-INFO-ATTR-1 for details.

Returns the value that was set in PJL via the SET JOBATTR= command. See JOB-INFO-ATTR-1 for details.

Returns the value that was set in PJL via the SET JOBATTR= command. See JOB-INFO-ATTR-1 for details.

Returns the value that was set in PJL via the SET JOBATTR= command. See JOB-INFO-ATTR-1 for details.

Returns the value that was set in PJL via the SET JOBATTR= command. See JOB-INFO-ATTR-1 for details.

Returns the value that was set in PJL via the SET JOBATTR= command. See JOB-INFO-ATTR-1 for details.

Returns the value that was set in PJL via the SET JOBATTR= command. See JOB-INFO-ATTR-1 for details.

Returns the value that was set in PJL via the SET JOBATTR= command. See JOB-INFO-ATTR-1 for details.

Returns the value that was set in PJL via the SET JOBATTR= command. See JOB-INFO-ATTR-1 for details.

Returns the value that was set in PJL via the SET JOBATTR= command. See JOB-INFO-ATTR-1 for details.

Returns the value that was set in PJL via the SET JOBATTR= command. See JOB-INFO-ATTR-1 for details.

Returns the value that was set in PJL via the SET JOBATTR= command. See JOB-INFO-ATTR-1 for details.

Returns the value that was set in PJL via the SET JOBATTR= command. See JOB-INFO-ATTR-1 for details.

Returns the value that was set in PJL via the SET JOBATTR= command. See JOB-INFO-ATTR-1 for details.

Returns the value that was set in PJL via the SET JOBATTR= command. See JOB-INFO-ATTR-1 for details.

Returns the value that was set in PJL via the SET JOBATTR= command. See JOB-INFO-ATTR-1 for details.

Returns the value that was set in PJL via the SET JOBATTR= command. See JOB-INFO-ATTR-1 for details.

The number of requested collated copies. The value was supplied with the job via PJL QTY variable, the PostScript Collate and NumCopies entries in the page device dictionary, or via some other mechansim.

The page number being printed within the current copy of a collated multi-copy job. This value changes when the job-info-pages-printed changes. The job-info-pages- printed indicates the total number of pages printed in the job, while this object indicates the number of pages printed for this copy of a collated multi-copy job. Additional information: The number of pages in the current copy of a collated multi-copy job which have been completely printed and safely delivered to the output bin.

Number of pages in a single copy of a collated multi- copy job.

Number of collated copies completely printed and delivered to the output bin at time of query.

User name that is obtained by the driver through some internal method or from user input. Additional information: The following is a general description for all the JOB-MANAGEMENT objects described below. These object describe the attributes of the dynamic list containing all the stored jobs on the disk available for printing or deleting via the job-management feature. The jobs on this list are not deleted from the disk unless explicitly specified by the user. A print job may be specified for retention by PJL commands in the data stream. Following is a list of the PJL commands (i.e. these comments describe the PJL implementation and in some cases do not reflect the PML implementation.): @PJL SET HOLD=OFF|ON|PROOF|STORE|PRINT GENERAL DESCRIPTION: This variable specifies the retention classification of the job. The values indicate whether the job is printed immediately and/or stored. OFF: The job is printed but not retained on disk after printing. This is the default value. ON: This setting may be thought of as free proof-and-hold. The requested number of copies will be printed and the job will be temporarily stored on disk. The job will then be available for printing additional copies through the control panel and through PML. There will be a limit to the number of these temporary jobs that may be stored, and when the limit is exceeded the oldest job will be removed from the disk. PROOF: One copy of the job is printed and remaining copies are stored on disk. The job is then available to select for printing via the control panel menus or PML. The job will be deleted from the disk when the disk space is needed for another proof and hold job but only after the additional copies have been printed. It will also be deleted when the user sends down another proof and hold job with the same job name, or the user explicitly deletes the job. STORE: The job is not printed immediately but is retained on disk. The job is available to select for printing via the control panel DEFAULT VALUE: OFF The value will be stored in RAM only, not in NVRAM. The legal PJL commands are SET and INQUIRE. DEFAULT is not allowed. The variable will appear in the PJL INFO VARIABLES list. @PJL SET USERNAME=<80 bytes> GENERAL DESCRIPTION: Eighty-character user name that is obtained by the driver through some internal method or from user input. If the job stream does not contain a USERNAME the default value will be NO USER NAME. The driver is responsible for determining the size of the printers control panel and sending a string of appropriate length. DEFAULT VALUE: NO USER NAME The value will be stored in RAM only, not in NVRAM. The legal PJL commands are SET and, INQUIRE. DEFAULT is not allowed. The variable will appear in the PJL INFO VARIABLES list. @PJL SET JOBNAME=<80 bytes> GENERAL DESCRIPTION: Eighty-character job name that may be generated by the driver or obtained from user input. This value may be used in conjunction with the USERNAME to select a job from the front panel. If the job stream does not contain a JOBNAME, the printer will assume no job name; each subsequent job that is sent down by the same user would replace the users last job on disk. The driver is responsible for determining the size of the printers control panel and sending a string of appropriate length. NOTE: The limit of 80 bytes is a PJL limit. The limit for PML will be 40 bytes. DEFAULT VALUE: NULL STRING The value will be stored in RAM only, not in NVRAM. The legal PJL commands are SET and INQUIRE. DEFAULT is not allowed. The variable will appear in the PJL INFO VARIABLES list. @PJL SET HOLDTYPE=PUBLIC|PRIVATE GENERAL DESCRIPTION: This variable specifies the privacy level of the job. PUBLIC: The job does not require a PIN in order to be released for printing. This is the default value. PRIVATE: The job requires a PIN in order to be released for printing. The PIN is specified by the HOLDKEY variable. If the HOLDTYPE is set to PRIVATE, a HOLDKEY value must be specified. If no HOLDKEY is specified, the job will be considered PUBLIC. DEFAULT VALUE: PUBLIC The value will be stored in RAM only, not in NVRAM. The legal PJL commands are SET and INQUIRE. DEFAULT is not allowed. The variable will appear in the PJL INFO VARIABLES list. @PJL SET HOLDKEY=4 digits, 0000...9999 GENERAL DESCRIPTION: A 4-digit string, each digit 0-9, that is specified in the job stream and then required to be entered in order to release the job for printing. If a HOLDTYPE is PRIVATE, a HOLDKEY value must be specified. If no HOLDKEY value is specified, a job will be considered PUBLIC. DEFAULT VALUE: NULL STRING The value will be stored in RAM only, not in NVRAM. The legal PJL commands are SET and INQUIRE. DEFAULT is not allowed. The variable will appear in the PJL INFO VARIABLES list. The format for the OID is as follows: 3.4.1.6.x.y <-----> | | | | \ / | job-id in the system / \ PML_JOB_MGNT_ROOT_OID \ job attribute 1..6 x values are 1..6: 1) user-name: user name that is obtained by the driver through some internal method or from user input. 2) job-name: job name may be generated by the driver or obtained from user input. 3) hold: indicates the retention classification of the job. The values indicate whether the job is printed immediately and/or stored. There are 4 options: OFF: The job is printed but not retained on the disk. ON: The job is printed and stored temporarily on the disk. STORE: The job is not printed but stored on the disk. PROOF: One copy of the job is printed and the remaining copies are stored on the disk. 4) holdtype: The variable specifies the security level of the job. PUBLIC: The job does not require a PIN in order to release the job for printing. PRIVATE: The job requires a PIN in order to be released for printing. 5) quantity: number of copies to print. Valid values are 0..999. 6) pin: A 4 digit string, each digit is 0-9, that is specified in the job stream and then required to be entered in order to release the job for printing. y : an unsigned 15 bit number which uniquely identifies the job. The job id for the job remains the same for the job until it is deleted from the held jobs list. For example, the OID below is asking for the user name of the job whose id is 3. The application would issue: OID get 3.4.1.6.1.3 For example, the <getnext> OID values sequence is as follows: OID returned OID getnext 3.4.1.6 3.4.1.6.1.1 getnext 3.4.1.6.1.1 3.4.1.6.1.2 getnext 3.4.1.6.2.1 3.4.1.6.2.2 ... getnext 3.4.1.6.1.6 3.4.1.6.1.7 getnext 3.4.1.6.2.1 3.4.1.6.2.2 getnext 3.4.1.6.5.2828 3.4.1.6.6.1 NOTE: for example above, job id 2828 is the last job in the list of held jobs. ... Also supported is <getnext> on the job attributes: OID returned OID getnext 3.4.1.6.1 3.4.1.6.1.1 getnext 3.4.1.6.6 3.4.1.6.6.1

The job name may be generated by the driver or obtained from user input.

Indicates the retention classification of the job. The values indicate whether the job is printed immediately and/or stored. There are 4 options: OFF: The job is printed but not retained on the disk. ON: The job is printed and stored temporarily on the disk. PROOF: One copy of the job is printed and the remaining copies are stored on the disk. STORE: The job is not printed but stored on the disk.

The variable specifies the security level of the job. PUBLIC: The job does not require a PIN in order to release the job for printing. PRIVATE: The job requires a PIN in order to be released for printing.

Number of copies to print.

A string that is specified in the job stream and then required to be entered in order to release the job for printing. PIN stands for Personal Identification Number. Additional information: Must be a 4 digit string, each digit must be 0..9 or a null string if there is no pin.

Instructs the printer to schedule the specified held job for printing with the specified number of copies. The job-id is used to identify which job to print. A held job can also be printed from the control panel. Additional information: Bytes 0-3 is the job id of the job to print. Bytes 4-7 is the number of copies to print.

Instructs the printer to delete the specified held job from the list. The job-id is used to identify which job to delete. A held job can also be deleted from the control panel. Additional information:

Sets the maximum number of jobs which can be stored in the held job list. Additional information: Sets the size of the temporary job lists queue.

Enables or disables Job Retention (Job Hold). The valid values are eDisabled and eEnabled. (Specifying an invalid mode causes an <badValue> error to be returned.) When eDisabled is specified all Job Retention (Hold, Proof, Store, PIN Printing) is disabled. When eEnabled is specified, the Job Retention characteristics of a given job are defined by the PJL variable SET HOLD. Additional information: When disabled, currently held jobs are not removed, but must be explicitly removed through the Control Panel or the PML object HELD-JOB-DELETE.

Specifies the error reason for most recent unsucessful photo card access. Additional information: Specifies the error reason for most recent unsucessful photo card access.

Reads or writes the default number of copies to be printed during photo application print jobs. This value is saved over a power cycle. Additional information: Reads or writes the default number of copies to be printed during photo application print jobs. This value is saved over a power cycle.

Reads or writes the number of copies to be printed during the next photo application print job. This value is not saved over power cycles. Additional information: Reads or writes the number of copies to be printed during the next photo application print job. This value is not saved over a power cycle.

Reads or writes the default media size to be used during the next photo application print job. This value is not saved over power cycles. Additional information: Reads or writes the default media size to be used during the next photo application print job. This value is not saved over a power cycle.

Reads or writes the media type to be used on the next photo application print job. This value is not saved over power cycles. Additional information: Reads or writes the media type to be used on the next photo application print job. This value is not saved over a power cycle.

Reads or writes the default image size to be used during photo application print jobs. This value is saved over power cycles. Additional information: Reads or writes the default image size to be used during photo application print jobs. This value is saved over a power cycle. Valid image sizes are determined by the PHOTO-IMAGE-SIZE-SET pml object.

Reads or writes the image size to be used during the next photo application print job. This value is not saved over power cycles. Additional information: Reads or writes the image size to be used during the next photo application print job. This value is not saved over a power cycle. Valid image sizes are determined by the PHOTO-IMAGE-SIZE-SET pml object.

Reads or writes the list of images to print during the next photo application print job. Each image number or number range must be separated by a comma. The image number corresponds to the location of the file on the image card. For example, if there are 10 images on the photo card, then you could select 1-10 or 1,2,3,4,5 or 1,2,3,4-9. The same image number can also appear multiple times in the list. i.e. 1,2,2,2,3,3,4,4,5. This value is not saved over power cycles and only applies to the next job. Additional information: Reads or writes the list of images to print during the next photo application print job. Each image number or number range must be separated by a comma. The image number corresponds to the location of the file on the image card. For example, if there are 10 images on the photo card, then you could select 1-10 or 1,2,3,4,5 or 1,2,3,4-9. The same image number can also appear multiple times in the list. i.e. 1,2,2,2,3,3,4,4,5. This value is not saved over a power cycle, and only applies to the next job.

Reads the number of printable photo images found on the inserted memory card. If 0, then no images were found, or the card was not properly inserted. Additional information: Reads the number of printable photo images found on the inserted memory card. If 0, then no images were found, or the card was not properly inserted.

Controls initiating photo application features. Additional information: Controls initiating photo application features.

Reads or writes the page count for color pages printed by the photo application. This value is saved over power cycles. Additional information: Reads or writes the page count for color pages printed by the photo application. This value is saved over a power cycle.

Reads or writes the page count for monochrome pages printed by the photo application. This value is saved over power cycles. Additional information: Reads or writes the page count for monochrome pages printed by the photo application. This value is saved over a power cycle.

This is only writable in service mode. This object changes the set of valid image sizes for the device. The image sizes groups are as follows: eImageSizeSetInch1: Wallet, 3x4in, 3 1/2 x 5in, 4x6in, 5x7in, 8x10in, full page eImageSizeSetInch2: Wallet, 3 1/2 x 5in, 4x6in, 5x7in, 6x8in, 8x10in, full page eImageSizeSetCentimeter1: 6x8cm, 7x10cm, 9x13cm, 10x15cm, 13x18cm, 15x21cm, 20x25cm, full page eImageSizeSetCentimeter2: 7x10cm, 9x13cm, 10x15cm, 13x18cm, 20x25cm, full page eImageSizeSetCentimeter3: 6x8cm, 9x13cm, 10x15cm, 13x18cm, 15x21cm, 18x24cm, 20x25cm, full page . Additional information: This is only writable in service mode. This object changes the set of valid image sizes for the device. The image sizes groups are as follows: eImageSizeSetInch1: Thumbnail, Wallet, 3x4in, 3 1/2 x 5in, 4x6in, 5x7in, 8x10in, full page, panorama eImageSizeSetInch2: Thumbnail, Wallet, 3 1/2 x 5in, 4x6in, 5x7in, 6x8in, 8x10in, full page, panorama eImageSizeSetCentimeter1: Thumbnail, 6x8cm, 7x10cm, 9x13cm, 10x15cm, 13x18cm, 15x21cm, 20x25cm, full page, panorama eImageSizeSetCentimeter2: Thumbnail, 7x10cm, 9x13cm, 10x15cm, 13x18cm, 20x25cm, full page, panorama eImageSizeSetCentimeter3: Thumbnail, 6x8cm, 9x13cm, 10x15cm, 13x18cm, 15x21cm, 18x24cm, 20x25cm, full page, panorama

writing this object causes the page counts, insert counts, or all photo counts to be cleared and reset to 0. Additional information: writing this object causes the page counts, insert counts, or all photo counts to be cleared and reset to 0.

Reads or writes the count for the number of times a compact flash memory card has been inserted in the device. This value is saved over a power cycle. Additional information: reads or writes the count for the number of times a compact flash memory card has been inserted in the device. This value is saved over a power cycle.

Reads or writes the count for the number of times a memory stick memory card has been inserted in the device. This value is saved over a power cycle. Additional information: reads or writes the count for the number of times a memory stick memory card has been inserted in the device. This value is saved over a power cycle.

Reads or writes the count for the number of times a memory stick pro memory card has been inserted in the device. This value is saved over a power cycle. Additional information: reads or writes the count for the number of times a memory stick pro memory card has been inserted in the device. This value is saved over a power cycle.

Reads or writes the count for the number of times a smart media memory card has been inserted in the device. This value is saved over a power cycle. Additional information: reads or writes the count for the number of times a compact flash memory card has been inserted in the device. This value is saved over a power cycle.

Reads or writes the count for the number of times a secure digital memory card has been inserted in the device. This value is saved over a power cycle. Additional information: reads or writes the count for the number of times a compact flash memory card has been inserted in the device. This value is saved over a power cycle.

Reads or writes the count for the number of times a MultiMediaCard memory card has been inserted in the device. This value is saved over a power cycle. Additional information: reads or writes the count for the number of times a MultiMediaCard memory card has been inserted in the device. This value is saved over a power cycle.

Reads or writes the count for the number of times an xD-Picture memory card has been inserted in the device. This value is saved over a power cycle. Additional information: reads or writes the count for the number of times an xD-Picture memory card has been inserted in the device. This value is saved over a power cycle.

Device should use DTMF dialing if eToneDial, pulse dial if ePulseDial.

Device to permit redial upon detecting certain error conditions.

Sets the answering-priority when using a shared voice line. eManualAnswer - Device will not automatically answer the phone. User must answer and push START button. eFaxAnswer - Device should assume call is fax, send CED immediately upon answering. eTadAnswer - (Telephone Answering Device Mode) Device allows downstream TAD to answer but device will eavesdrop for fax CNG signal. If a CNG detected, cut off the downstream device, send CED. Do nothing if CNG not detected.

Number of rings before the fax device answers the phone if FAX-ANSWER-MODE is not set to MANUAL-MODE.

Device to answer the incoming call based on detecting the the specified type of telephone ring.

The amount of memory, in bytes, used by the file system to buffer file data. Additional information: Reports the amount of memory, in bytes, reserved for use by the file system. Returns <noSuchName> status if attempting to access this object and there is no storage device is installed. The values remain constant across reboots. Possible Values: FILE-SYSTEM-MAX-OPEN-FILES 32 512 EIO DISK 69916 198556 EIO DISK + 1 2MB Flash 88940 217580 1 2MB Flash 33052 161692

The number of open files allowed at one time. Opening a file when the maximum number of files are currently open will fail. Additional information: Indicates the number of open files a personality (e.g. PCL or PostScript) is guaranteed to be able to open before the file system runs out of file handles. After writing this object, the printer must be rebooted (powercycled) before the change takes effect. This object supports any value between 32 - 512 inclusive. If a value Less then 32 then it snaps to 32 if greater then 512 it snaps to 512. The factory default value is dependent on the amount of installed RAM. The default value of 32 is when Memory <= 4MB, 128 is if the memory is > 4MB. Performing a cold reset sets this object back to the factory default value. Returns <noSuchName> status if attempting to access this object and there is no storage device is installed. Default for LaserJet 4000 Series/LaserJet 5000 Series is 32 Default for LaserJet 8000 Series/LaserJet 8100 Series/LaserJet 4050 Series is 128

This test object that will not be supported in any released product. Setting this object allows the next file system call return code to be specified or to simulate uninitialized or unistalled volumes. The POS will specify the binary format. Additional information: A three byte binary value. The first byte indicates what function is being effected by this set. value | function ------+------------------ 1 | PersFSCtl 2 | PersFSDirClose 3 | PersFSDirCreate 4 | PersFSDirDelete 5 | PersFSDirOpen 6 | PersFSDirRead 7 | PersFSDirReadStd 8 | PersFSDirRewind 9 | PersFSDirSeek 10 | PersFSDirTell 11 | PersFSFileClose 12 | PersFSFileDelete 13 | PersFSFileMove 14 | PersFSFileOpen 15 | PersFSFileRead 16 | PersFSFileSeek 17 | PersFSFileStatus 18 | PersFSFileWrite 19 | PersFSFlush 20 | PersFSVolChk 21 | PersFSVolFix 22 | PersFSVolInit 23 | PersFSVolStatus The return value of the function being effected will return the value -1 to indicate an error occurred. The second byte is the value returned by the next call to PersFSErrNo() (after the call being effected is called). Refer to the Copernicus Personality Interface Volume 2 Disk File System documentation for a list of values returned by PersFSErrNo(). The third byte indicates which call to the specified file system routine will fail. A value of one means the first call will fail. A value of two means the second call will fail, and so on. Writing this object causes any previous write to this object to be invalidated. Note: The error triggering mechanism is actually implemented at the message interface to the file system rather than at the PersFSxxx() function call interface. This is easier to do, and it is better for NFS because NFS uses the message interface rather than the PersFSxxx() functions. Fortunately there is a one-to-one mapping between messages and PersFSxxx() functions so everything works out nicely. The printer will uninitialize the mass storage device if the first byte is one of the values listed below. value | meaning ------+------------------ 101 | Effects the printer state 102 | Effects the data on the device The Moby printer supports 3 volumes zero, so the second byte must be 0 - 2. The third byte has no meaning and must be zero.

This object allows the system partition to be written to. It consists of a C structure containing the following fields: typedef struct { ubyte password[8]; ubyte volumenumber; } fs_writeable_system_partition_t; which is described below: Bytes 0 - 7: contain the password Byte 8 : is the volume number MAX-ACCESS to this command is controlled by the password. If the password supplied is incorrect the command will fail. The volumenumber is a volume number of an existing system partition. Additional information: Returns <noSuchName> status if attempting to access this object and there is no storage device is installed. Returns <badValue> if the password is incorrect or if the volume requested is not present.

Changes a system partition to be READ-ONLY. The value is the volume number to change. If the volume number specified is NOT a system partition an error is returned. Additional information: Returns <noSuchName> status if attempting to access this object and there is no storage device is installed. Returns <badValue> if the volume requested is not present.

Setting this object causes the specified filename to be deleted, after first validating that the authentication data is correct for the specified user ID. The format for this object is a C structure: typedef struct { sint32 UserId; uint16 AuthenticationDataLen ubyte AuthenticationData[] char Filename[]; } fs_delete_files_t; which is described below: Bytes 0 - 3: contains a user id represented as a multi-byte value that is stored in big-endian format, where the most significant byte occurs first. Bytes 4 - 5 : Length of the Athentication data that follows starting at offset 6. Stored as a multi-byte value that is stored in big-endian format, where the most significant byte occurs first. Bytes 6 - 6+AuthenticationDataLen : a ubyte array containing the Authentication data used to verify MAX-ACCESS for this operation. Bytes starting at offset (6+AuthenticationDataLen+1): A null terminated character array representing the ASCII file name to be deleted. The length of the string will be limited by the remaining space in the object. This string represents a fully-qualified path name which may specify a filename or a regular expression that may match multiple files (e.g <path>/*.exe). Access to this command is controlled by the UserId and the authentication data. If the UserID or authentication data supplied is incorrect the command will fail. The device POS will specify any limitations to the length of the filename string, what constitutes a correct user ID, what constitutes correct authentication data, and the significance of any return values. Additional information: Setting this object causes the specified filename to be deleted, after first validating that the authentication data is correct for the specified user ID. This object is always present. The format for this object is a C structure: typedef struct { sint32 UserId; uint16 AuthenticationDataLen ubyte AuthenticationData[] char Filename[]; } fs_delete_files_t; Bytes 0 - 3: contains a user id represented as a multi-byte value that is stored in big-endian format, where the most significant byte occurs first. Bytes 4 - 5 : Length of the authentication data that follows starting at offset 6. Stored as a multi-byte value that is stored in big-endian format, where the most significant byte occurs first. Bytes 6 - 6+AuthenticationDataLen : a ubyte array containing the authentication data used to verify MAX-ACCESS for this operation. Bytes starting at offset (6+AuthenticationDataLen+1): A null terminated character array representing the ASCII file name to be deleted. The length of the string will be limited by the remaining space in the object. This string represents a fully-qualified path name which may specify a filename or a file-type regular expression that may match multiple files (e.g., <path>/*.exe). MAX-ACCESS to this command is controlled by the UserId and the authentication data. If the UserID or authentication data supplied is incorrect the command will fail. The device POS will specify any limitations to the length of the filename string, what constitutes a correct user ID, what constitutes correct authentication data, and the significance of any return values.

This object acts as a gate keeper for write access to the PML objects FILE-SYSTEM-EXTERNAL-ACCESS-CAPABILITIES, FILE-SYSTEM-ERASE-MODE, and FILE-SYSTEM-WIPE-DISK. The object can be viewed as always being in one of 4 states: State 0 --> Un-initialized: FILE-SYSTEM-SECURITY-ACCESS-PASSWORD is the empty string and a pmlget operation on the object will return the string 0. This will be the state after an NVRAM init which is the only way to set the object to the empty string. It cannot be set to the empty string through PML. In this state write access to FILE-SYSTEM-EXTERNAL-ACCESS-CAPABILITIES, FILE-SYSTEM-ERASE-MODE and FILE-SYSTEM-WIPE-DISK is disabled while write access to the object itself is enabled. A successful set operation on the object in this state will return the string SET and will result in a transition to State 3. State 1 --> The Password is set to a non-empty string: A pmlget operation on the object will return the string 1 regardless of the actual stored password value. In this state write access to FILE-SYSTEM-EXTERNAL-ACCESS-CAPABILITIES, FILE-SYSTEM-ERASE-MODE and FILE-SYSTEM-WIPE-DISK is disabled. The only string the object itself can be successfully set to while in this state is the current value of the password. Setting the object to its current value causes a transition to State 2 which is an authenticated state. The value returned from such a set operation will be the string OK. State 2 --> The password is in an authenticated state: The gate to write to the PML objects FILE-SYSTEM-EXTERNAL-ACCESS-CAPABILITIES, FILE-SYSTEM-ERASE-MODE, and FILE-SYSTEM-WIPE-DISK is open. One, and only one, write operation can be performed on one of these three objects. During such a write operation the object itself will transition to State 1 thus closing the gate. In State 2 a pmlset operation on the object will result in the password being set and a transfer to State 3. The value returned from a set operation in this state on FILE-SYSTEM-SECURITY-ACCESS-PASSWORD will be SET. A pmlget operation on the object will return the string 2 regardless of the actual password value. State 3 --> The password was just changed: A pmlget operation on the object will return the string 3. Otherwise behaviors in State 3 are exactly like in State 1.

This object is used to control access to the file system of the device. It is always readable. It is writable when FILE-SYSTEM-SECURITY-ACCESS-PASSWORD is not the empty string, and a successful write to that object with the current password has preceded the write to this object. In other words, the FILE-SYSTEM-SECURITY-ACCESS-PASSWORD must be in the authenticated state for a write on FILE-SYSTEM-EXTERNAL-ACCESS-CAPABILITIES to succeed. After the object has successfully been written to, it becomes read-only, and the FILE-SYSTEM-SECURITY-ACCESS-PASSWORD object exits the authenticated state. FILE-SYSTEM-SECURITY-ACCESS-PASSWORD must then be written to again with the current password in order to make another write operation on FILE-SYSTEM-EXTERNAL-ACCESS-CAPABILITIES possible. cDisablePJLFileSystemAccess - All file system access through PJL will be disabled. cDisablePMLFileSystemWrite - All file-systems-related PML objects such as FILE-SYSTEM-DELETE-FILES or hrPartitionLabel become read-only. For objects that are normally write-only this means that no successful operations can now be performed on them. cDisableNFSFileSystemAccess - All NFS file system access will be disabled. cDisablePSFileSystemAccess - All file system access through PostScript will be disabled. cDisableEWSFileSystemAccess - All access to the file system by the Embedded Web Server will be disabled.

This object is used to control how file data is handled when files are deleted. It is always readable. It is writable when FILE-SYSTEM-SECURITY-ACCESS-PASSWORD is the empty string or when a write to FILE-SYSTEM-SECURITY-ACCESS-PASSWORD with the current password has preceeded the write to the object. When FILE-SYSTEM-SECURITY-ACCESS-PASSWORD is not the empty string then this object becomes read-only after a successful write to it. FILE-SYSTEM-SECURITY-ACCESS-PASSWORD must then be written to again with the current password in order to make another write operation on the object possible. If the FILE-SYSTEM-SECURITY-ACCESS-PASSWORD is incorrectly set, this object becomes read-only until the password is correctly set. The logical settings for this object are: NonSecureFastErase - When a file is deleted, only the reference to it in the file system tables is removed. No file data is overwritten. This is the default setting. This is the setting when both bits in the collection are set to 0. SecureFastErase - File information is overwritten with identical, random character pattern when it is deleted. This is the setting when cEraseMode0 is set to 1 and cEraseMode1 is set to 0. SecureSanitizeErase - Secure, repetitive algorithm used to overwrite all deleted file information and remove any residual data persistence. A random character is written to all bytes of deleted sectors. Then the complement of that character and finally, another random character is written. This is the setting when cEraseMode0 is set to 0 and cEraseMode1 is set to 1. Note that an error will be returned for an attempt to set both bits of the collection to 1.

This object is a non-leaf node which will have one leaf node under it for each file system in the printer. The leaf nodes will be in a 1-to-1 correspondence with the hrDeviceIndex objects. This object specifies for each leaf node whether the file system on the device is going to be erased according to the setting of the FILE-SYSTEM-ERASE-MODE referenced by the corresponding hrDeviceIndex. A file system will be overwritten on system reboot if this object is set to 1. It will be unchanged if this object is set to 0. If this objects value is -1 then the file system cannot be wiped. If the file system contains the permstore, the permstore will be saved off and restored after the file-system wipe is completed. This object is always readable. It is writable when FILE-SYSTEM-SECURITY-ACCESS-PASSWORD is the empty string or when a write to FILE-SYSTEM-SECURITY-ACCESS-PASSWORD with the current password has preceeded the write to the object. When FILE-SYSTEM-SECURITY-ACCESS-PASSWORD is not the empty string then this object becomes read-only after a successful write to it. FILE-SYSTEM-SECURITY-ACCESS-PASSWORD must then be written to again with the current password in order to make another write operation on the object possible. If the FILE-SYSTEM-SECURITY-ACCESS-PASSWORD is incorrectly set, this object becomes read-only until the password is correctly set.

This object is a non-leaf node which will have one leaf node under it for each file system in the printer. The leaf nodes will be in a 1-to-1 correspondence with the hrDeviceIndex objects. This object specifies for each leaf node the status of a disk wipe in progress. A return value of -1 indicates that no disk wipe is in progress. A return value in the range of 0 to 100 indicates the percent done for a disk wipe in progress. All other values are illegal.

The number of times the file system has received requests to open a file for reading. Opening a file for both reading and writing will cause this value to change. The POS should state if a power cycle causes the counter is be reset to zero. Additional information: Reset to the factory default value after a power cycle. Returns <noSuchName> status if attempting to access this object and there is no storage device is installed. This value is increamented when a file is opened.

The number of times the file system has received requests to open a file for writing. Opening a file for both reading and writing will cause this value to change. The POS should state if a power cycle causes the counter is be reset to zero. Additional information: Reset to the factory default value after a power cycle. Returns <noSuchName> status if attempting to access this object and there is no storage device is installed. This value is increamented when a file is opened.

A counter indicating the number of file system requests that completed successfully. The POS should state if a power cycle causes the counter is be reset to zero. Additional information: Reset to the factory default value after a power cycle. Returns <noSuchName> status if attempting to access this object and there is no storage device is installed.

A counter indicating the number of file system requests that completed unsuccessfully. The POS should state if a power cycle causes the counter is be reset to zero. Additional information: Reset to the factory default value after a power cycle. Returns <noSuchName> status if attempting to access this object and there is no storage device is installed.

A value indicating the number of bytes of RAM currently used by the file system firmware. Additional information: Reset to the factory default value after a power cycle. Returns <noSuchName> status if attempting to access this object and there is no storage device is installed. This will veri depending on the number and size of Mass Storage devices installed.

A value indicating the maximum number of bytes of RAM used by the file system firmware. The POS should state if the value is reset to zero after a power cycle. Additional information: Reset to the factory default value after a power cycle. Returns <noSuchName> status if attempting to access this object and there is no storage device is installed.

Returns eTrue if a file system has been written to the mass storage device(s) which will hold file data contained in this file system. Returns eFalse otherwise. Each POS needs to specify the relationship between file systems and the physical storage devices that can hold the data contained in those file systems. Additional information: This objects is only supported if a disk is installed. Returns <noSuchName> status if attempting to perform a Get on this OID with no disk installed. Returns <noSuchName> status if attempting to perform a Set, EnableTrap, or DisableTrap on this OID with no disk installed.

Returns the total size, in bytes, of the mass storage space configured to hold the file data (and file system information) assoicated with files stored in this file system. This refers to hardware capacity, independent of any space consumed by the file system overhead or user files. Additional information: This objects is only supported if a disk is installed. Returns <noSuchName> status if attempting to perform a Get on this OID with no disk installed. Returns <noSuchName> status if attempting to perform a Set, EnableTrap, or DisableTrap on this OID with no disk installed.

Returns the total amount, in bytes, of unused storage space currently available to this file system. Additional information: This objects is only supported if a disk is installed. Returns <noSuchName> status if attempting to perform a Get on this OID with no disk installed. Returns <noSuchName> status if attempting to perform a Set, EnableTrap, or DisableTrap on this OID with no disk installed.

Supports write-protecting the file system. Setting FILE-SYSTEM-WRITE-PROTECT to eEnabled blocks any modification of the contents of the file system. Setting FILE-SYSTEM-WRITE-PROTECT to eDisabled allows modification of the contents of the file system. Additional information: This objects is only supported if a disk is installed. Returns <noSuchName> status if attempting to perform a Get, or Set on this OID with no disk installed. Returns <noSuchName> status if attempting to perform an EnableTrap, or DisableTrap on this OID with no disk installed.

Setting this object to eInitializing causes file system 2 to be initialized. Reading this object indicates if the file system is currently being initialized. Additional information: The hrDeviceIndex value for the mass storage device is the same value that is used to index into the FILE-SYSTEM sub-tree. Since this product supports up to 3 mass storage device, and since the hrDeviceIndex for the mass storage devices will start at 2 if the mass storage device is installed, the FILE-SYSTEM2-INITIALIZE-VOLUME object will be the object that allows the mass storage device to be initialized that is the 1st device.

Setting this object to eInitializing causes file system 3 to be initialized. Reading this object indicates if the file system is currently being initialized. Additional information: The hrDeviceIndex value for the mass storage device is the same value that is used to index into the FILE-SYSTEM sub-tree. Since this product supports up to 3 mass storage device, and since the hrDeviceIndex for the mass storage devices will start at 2 if the mass storage device is installed, the FILE-SYSTEM3-INITIALIZE-VOLUME object will be the object that allows the mass storage device to be initialized that is the 2nd device.

Setting this object to eInitializing causes file system 4 to be initialized. Reading this object indicates if the file system is currently being initialized. Additional information: The hrDeviceIndex value for the mass storage device is the same value that is used to index into the FILE-SYSTEM sub-tree. Since this product supports up to 3 mass storage devices, and since the hrDeviceIndex for the mass storage devices will start at 2 if the mass storage device is installed, the FILE-SYSTEM4-INITIALIZE-VOLUME object will be the object that allows the mass storage device to be initialized that is the 3rd device.

Contains some sort of time stamp indicating when error 1 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: This item contains the engine page count when the error occurred. If there is currently no error entry for this object, a 0 will be returned. Note that 0 may also be returned when there is a valid error, but a current page count was unavailable. If ERROR1-CODE object also returns 0, then an error has not yet been logged for this object. See ERROR1-CODE for an explanation of the order used for storing errors.

Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: Returns a device specific error code. If the error code returned is 0, then the printer has not yet logged an error for this object. When the maximum number of errors is reached (30 on LaserJet 4050 Series printers), and a new error occurs, the error in ERROR1-CODE will be replaced by the one in ERROR2-CODE, and so on until the last error object will be given the value of the new error. The error number is returned in the upper 16 bits. If it is 68, 69, 79, or 80, then the sub code is returned in the lower 16 bits (eg. 68 001C, where the subcode is already a hexadecimal value). If the error number is any other number, then the 1st sub code (XX) will be in bits 15-8 and the 2nd sub code (YY) will be in bits 7-0 (eg. 55.04.02) where XX=04 and YY=02). Example: If the error is 68 001A, then the value returned will be 4456474. To break it down: 4456474 = 0x0044001A The upper 16 bits: 0x0044 = 68 The lower 16 bits: 0x001A = 001A Which is the error: 68 001A Example: If the error is 55.04.241, then the error code will be 3605745. To break it down: 3605745 = 0x003704F1 The upper 16 bits: 0x0037 = 55 The upper byte of the lower 16 bits: 0x04 = 04 The lower byte of the lower 16 bits: 0xF1 = 241 Which is the error: 55.04.241

Contains some sort of time stamp indicating when error 2 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP.

Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE.

Contains some sort of time stamp indicating when error 3 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP.

Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE.

Contains some sort of time stamp indicating when error 4 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP.

Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE.

Contains some sort of time stamp indicating when error 5 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP.

Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE.

Contains some sort of time stamp indicating when error 6 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP.

Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE.

Contains some sort of time stamp indicating when error 7 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP.

Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE.

Contains some sort of time stamp indicating when error 8 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP.

Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE.

Contains some sort of time stamp indicating when error 9 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP.

Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE.

Contains some sort of time stamp indicating when error 10 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP.

Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE.

Contains some sort of time stamp indicating when error 11 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP.

Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE.

Contains some sort of time stamp indicating when error 12 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP.

Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE.

Contains some sort of time stamp indicating when error 13 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP.

Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE.

Contains some sort of time stamp indicating when error 14 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP.

Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE.

Contains some sort of time stamp indicating when error 15 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP.

Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE.

Contains some sort of time stamp indicating when error 16 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP.

Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE.

Contains some sort of time stamp indicating when error 17 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP.

Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE.

Contains some sort of time stamp indicating when error 18 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP.

Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE.

Contains some sort of time stamp indicating when error 19 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP.

Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE.

Contains some sort of time stamp indicating when error 20 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP.

Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE.

Contains some sort of time stamp indicating when error 21 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP.

Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE.

Contains some sort of time stamp indicating when error 22 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP.

Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE.

Contains some sort of time stamp indicating when error 23 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP.

Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE.

Contains some sort of time stamp indicating when error 24 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP.

Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE.

Contains some sort of time stamp indicating when error 25 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP.

Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE.

Contains some sort of time stamp indicating when error 26 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP.

Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE.

Contains some sort of time stamp indicating when error 27 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP.

Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE.

Contains some sort of time stamp indicating when error 28 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP.

Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE.

Contains some sort of time stamp indicating when error 29 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP.

Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE.

Contains some sort of time stamp indicating when error 30 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP.

Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE.

Contains some sort of time stamp indicating when error 31 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP.

Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE.

Contains a time stamp indicating when error 32 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP.

Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE.

Contains a time stamp indicating when error 33 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP.

Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE.

Contains a time stamp indicating when error 34 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP.

Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE.

Contains a time stamp indicating when error 35 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP.

Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE.

Contains a time stamp indicating when error 36 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP.

Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE.

Contains a time stamp indicating when error 37 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP.

Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE.

Contains a time stamp indicating when error 38 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP.

Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE.

Contains a time stamp indicating when error 39 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP.

Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE.

Contains a time stamp indicating when error 40 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP.

Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE.

Contains a time stamp indicating when error 41 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP.

Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE.

Contains a time stamp indicating when error 42 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP.

Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE.

Contains a time stamp indicating when error 43 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP.

Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE.

Contains a time stamp indicating when error 44 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP.

Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE.

Contains a time stamp indicating when error 45 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP.

Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE.

Contains a time stamp indicating when error 46 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP.

Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE.

Contains a time stamp indicating when error 47 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP.

Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE.

Contains a time stamp indicating when error 48 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP.

Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE.

Contains a time stamp indicating when error 49 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP.

Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE.

Contains a time stamp indicating when error 50 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP.

Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE.

A counter which changes when a mass storage based resource has been added or deleted. Additional information: The value of this counter changes each time the MASS-STORAGE-RESOURCE-CHANGED object is set to eTrue. The value also changes when the mass storage device is initialized. However, the value does not change when a mass storage device is removed and a different mass storage device is installed. Initializing all volumes sets this object back to the factory default value. A reboot sets this object back to the factory devalut value. Returns <noSuchName> status if attempting to access this object and there is no storage device is installed.

Setting to eTrue causes MASS-STORAGE-RESOURCE-CHANGE- COUNTER to be incremented. Additional information: Returns <noSuchName> status if attempting to access this object and there is no storage device is installed.

This test object that will not be supported in any released product. Setting this object allows the next RPC call return code to be specified. The POS will specify the binary format. Additional information: The format of the binary data is a one of three formats. The first format is no binary data, which indicates the next RPC reply should not be modified. The other two formats are described in RFC 1057 and encoded using XDR (i.e. the value is the data used to instead of the actual RPC reply). The second format is when reply_stat is MSG_ACCEPTED and accept_stat is something other than SUCCESS. The third format is when reply_stat is MSG_DENIED. Notice that all RPC replies that do not contain any results are supported.

Array of Berkeley sockets style protocol addresses used to bind RPC to a communications protocol family. Setting an instance of this array object to a zero length binary value disables the transport protocol indicated by that instance. All multi-bytes fields are in network (or big-endian) order. Bytes 1 and 2 indicate the transport protocol. Some of the transport protocol mapping information can be found in RFC 1010 Assigned Numbers. A list of interesting transport protocol number mappings include: Protocol | Number ---------+------- UDP/IP | 17 IPX | 1000 MLC | 4660 Bytes 3 and 4 indicate the address family. The address family uses the same mapping as the BSD sockets address family. A list of interesting address family mappings include: Address Family | Number ---------------+------- Internet | 2 NetWare | 6 MLC | 22136 The format the fifth and following bytes is dependent on the address family. For the Internet address family, bytes 5 and 6 contain the port number, bytes 7 through 10 contain the IP address, and the following eight bytes are unused. For NetWare, bytes 5 through 8 are the network number, bytes 9 through 14 are the node number, and bytes 15 and 16 are the socket number. Additional information: The length of the binary value is zero if the instance of an object in the rpc-bind-protocol-address array is not in use. An unfortunate side effect of the implementation is initializing the mass storage device sets this object back to the factory default value. Returns <noSuchName> status if attempting to access this object and there is no storage device is installed.

A counter indicating the number of RPC requests that completed successfully (reply_data stat is SUCCESS). The POS should state if a power cycle causes the counter is be reset to zero. Additional information: Reset to the factory default value after a power cycle. Returns <noSuchName> status if attempting to access this object and there is no storage device is installed.

A counter indicating the number of RPC requests that completed unsuccessfully (reply_data stat is not SUCCESS). The POS should state if a power cycle causes the counter is be reset to zero. Additional information: Reset to the factory default value after a power cycle. Returns <noSuchName> status if attempting to access this object and there is no storage device is installed.

An array of Berkeley sockets style protocol addresses that the NFS service has been bound to successful. The format is that same as the array of RPC-BIND-PROTOCOL- ADDRESS of objects. Additional information: Returns <noSuchName> status if attempting to access this object and there is no storage device is installed.

This test object that will not be supported in any released product. Setting this object allows the next mount call return code to be specified. The POS will specify the binary format. Additional information: A one byte binary value. The byte indicates what procedure is being effected by this set. value | function ------+------------------ 1 | Mount will return an fhstatus of 0. 2 | Dump will return an empty table.

The amount of memory, in bytes, used by the Network File System server to buffer file data. Additional information: Reports the amount of memory, in bytes, reserved for use by the NFS server. An unfortunate side effect of the implementation is initializing the mass storage device sets this object back to the factory default value. Also includes the memory used by other firmware components in addition to the NFS server. Returns <noSuchName> status if attempting to access this object and there is no storage device is installed.

The maximum amount of data transferred in one NFS server read data call. Additional information: An unfortunate side effect of the implementation is initializing the mass storage device sets this object back to the factory default value. Returns <noSuchName> status if attempting to access this object and there is no storage device is installed. Rebooting causes this value to reset to factory default. value < 256 snaps to 256 value > 1500 snaps to 1500

The maximum amount of data transferred in one NFS server write data call. Additional information: An unfortunate side effect of the implementation is initializing the mass storage device sets this object back to the factory default value. Returns <noSuchName> status if attempting to access this object and there is no storage device is installed.

This test object that will not be supported in any released product. Setting this object allows the next NFS call return code to be specified. The POS will specify the binary format. Additional information: A three byte binary value. The first byte indicates what procedure is being effected by this set. value | function ------+------------------ 1 | GetAttr 2 | SetAttr 3 | reserved 4 | Lookup 5 | reserved 6 | Read 7 | reserved 8 | Write 9 | Create 10 | Remove 11 | Rename 12 | reserved 13 | reserved 14 | MkDir 15 | RmDir 16 | ReadDir 17 | StatFS The second byte is the stat value returned by the next call to procedure specified by the value of the first byte. The second byte can not be zero. Refer to RFC 1094 for a list of stat values. The third byte indicates which call to the specified file system routine will fail. A value of one means the first call will fail. A value of two means the second call will fail, and so on. Writing this object causes any previous write to this object to be invalidated.

A counter indicating the number of NFS requests that completed without error. The POS should state if a power cycle causes the counter is be reset to zero. Additional information: Reset to the factory default value after a power cycle. Returns <noSuchName> status if attempting to access this object and there is no storage device is installed.

A counter indicating the number of NFS requests that completed with an NFS status other than NFS_OK (0). The POS should state if a power cycle causes the counter is be reset to zero. Additional information: Reset to the factory default value after a power cycle. Returns <noSuchName> status if attempting to access this object and there is no storage device is installed.

A value indicating the number of bytes of RAM currently used by the NFS firmware. Additional information: Reset to the factory default value after a power cycle. Returns <noSuchName> status if attempting to access this object and there is no storage device is installed.

A value indicating the maximum number of bytes of RAM used by the NFS firmware. The POS should state if the value is reset to zero after a power cycle. Additional information: Reset to the factory default value after a power cycle. Returns <noSuchName> status if attempting to access this object and there is no storage device is installed.

This test object that will not be supported in any released product. Setting this object allows the next RPC bind call return code to be specified. The POS will specify the binary format. Additional information: A one byte value. value | meaning ------+------------------ 1 | Next GetPort or GetAddr will receive port 0 | (indicating the service is not supported). 2 | Next Dump will receive an empty table.

A counter indicating the number of RPC bind (RPC program number 100000, version 2) requests that completed successfully. The POS should state if a power cycle causes the counter is be reset to zero. Additional information: Reset to the factory default value after a power cycle. Returns <noSuchName> status if attempting to access this object and there is no storage device is installed.

A counter indicating the number of RPC bind (RPC program number 100000, version 2) requests that completed unsuccessfully. The POS should state if a power cycle causes the counter is be reset to zero. Additional information: Reset to the factory default value after a power cycle. Returns <noSuchName> status if attempting to access this object and there is no storage device is installed.

A counter indicating the number of XIP requests that were processed. The POS should state if a power cycle causes the counter is be reset to zero. Additional information: The number of XIP datagrams that have been received by the XIP service. Reset to the factory default value after a power cycle. Returns <noSuchName> status if attempting to access this object and there is no storage device is installed.

A counter indicating the number of XIP data in datagrams that were dropped (typically due to the printer being flooded with XIP requests ). The POS should state if a power cycle causes the counter is be reset to zero. Additional information: Reset to the factory default value after a power cycle. Returns <noSuchName> status if attempting to access this object and there is no storage device is installed.

Returns or controls RAM disk support. eOFF turns off the RAM disk functionality. eOn turns on the RAM disk functionality and creates a RAM disk whose size is controlled by the RAM-DISK-SIZE object. eAuto turns on the RAM disk functionality and creates a RAM disk size determined by the printer based on installed options and other memory related settings. Additional information: Returns or controls RAM disk support. eOFF turns off the RAM disk functionality. eOn turns on the RAM disk functionality and creates a RAM disk whose size is controlled by the RAM-DISK-SIZE object. eAuto turns on the RAM disk functionality and creates a RAM disk size determined by the printer based on the amount of installed memory. The automatic size will be 25 percent of all memory above 4MB.

Returns or controls the size of the RAM disk. The device POS specifies the minimum memory requirements. The object MAXIMUM-RAM-DISK-MEMORY specifies the maximum memory available for the RAM disk. Additional information: Returns or controls the size of the RAM disk. The values that can be set depend on the current setting of the RAM-DISK-MODE object, and the amount of memory available above 4MB. Use the MAXIMUM-RAM-DISK-MEMORY object to determine the amount of additional memory available for the RAM disk.

This objects name is misleading. This object does not return the maximum configurable RAM disk size. Instead, it returns the maximum amount of memory, in bytes, that can used to increase the size of the RAM disk. Additional information: This object returns the maximum amount of additional memory that is available for increasing the size of the RAM disk.

This test object will not be supported in any released product. Setting this object allows the next call to the mass storage block driver 2 to return the specified code. The POS will specify the binary format. Additional information: The hrDeviceIndex value for the mass storage device is the same value that is used to index into the DISK-STORAGE-BLOCK-DRIVERS sub-tree. Since this product only supports one mass storage device, the hrDeviceIndex for the mass storage device will be 2 if the mass storage device is installed. The value is a two byte value. The value of the first byte indicates the return code, as described in the following table: value | meaning ------+------------------ 1 | After the next power cycle, indicate the | mass storage device is not installed. Only affects the | printer state after the next power cycle. 2 | After the next power cycle, indicate the | mass storage device is not initialized. Changes the | contents of the mass storage device so the mass storage device becomes | uninitialized. 3 | After the next power cycle, indicate the | mass storage device is defective. Only affects the | printer state after the next power cycle. 4 | Cause the specified call to the read block | routine to indicate read failure. 5 | Cause the specified call to the write block | routine to indicate write failure. 6 | After the next power cycle, indicate the | mass storage device failed the power-on self-test, but | completed the initialization sequence | successfully. Only affects the | printer state after the next power cycle. 7 | Cause the driver to behave, after the next power | cycle, as if the mass storage device had the serial number | SN00000000. This is a one-shot effect and the | driver reverts to normal behavior if the printer | is power cycled a second time. The second byte indicates on which call to the specified block driver the failure will start to occur. If the value of the first bytes is four or five, then the value of the second byte in indicates which call to the specified block driver routine will fail. A value of one means the first call will fail. A value of two means the second call will fail, and so on. If the value of the first byte is one, two, three, six, or seven, then the value of the second byte is ignored. Writing this object causes any previous write to this object to be invalidated.

Total number of simplex pages printed in this media size. Additional information: The 5 usage (simplex/duplex count, simplex/duplex click charge and paper size total) objects described here and below detail the usage for the printer for each paper size defined in the PCL Implementors Guide and in the Media Size Table in the hpmib.txt. The OID binding is based on the click attribute and paper size. For example: The format for the OID is as follows: 3.4.1.5.x.y <-----> | | | | \ / | paper size / \ PRINTER-CLICK_TOTALS ROOT \ OID click attribute 1..5 x values are 1..5: 1) simplex count 2) simplex click charge 3) duplex count 4) duplex click charge 5) printer or scanner paper size total (i.e. depends if the root OID is referrring to the printer or scanner). y : paper size as defined in the Media Size Table in the hpmib.txt

Charge for each simplex page printed in this media size.

Total number of duplex pages printed in this media size.

Charge for each duplex page printed in this media size. Additional information: The click charges for duplex printed media.

The total charge for pages printed in this media size.

Total number of letter equivalently weighted pages both color and mono combined with this printer

Total number of mono dimplex pages printed in this media size. A dimplex page is one that has been printed in duplex mode but the back side is blank. Dimplex pages occur when the printer firmware inserts a blank page in order to complete a duplexed job which is sent to the printer with an odd number of pages

Total number of simplex pages printed on this media size

Total number of duplex pages printed on this media size

The object is used to get the information on new duplex counting mechanism. With this new mechanism the Duplex count would represent actual Duplex count and not half of the count. eTrue means feature is available for the user

Total printer charge for all paper sizes printed.

Reports the average toner area coverage of all pages printed over the life of the device. Counts pixels on each page, divides pixel count by pixels possible on a page to give the percentage of coverage, and keeps a rolling average percent weighted by area printed.

Total number of staples used.

The first line of usage instructions for the device user.Appears on Line 1 of the usage page.

The second line of usage instructions for the device user.Appears on Line 1 of the usage page.

The third line of usage instructions for the device user.Appears on Line 1 of the usage page.

The fourth line of usage instructions for the device user.Appears on Line 1 of the usage page.

A value indicating the threshold value for this category of pages. The device POS will indicate the units of measure for this threshold value

This enumeration describes the selected print quality for this category of printed pages

Total number of simplex pages printed for this category of printed pages

Total number of duplex pages printed for this category of printed pages

Total number of simplex plus duplex pages printed multiplied by the unit charge for each given media size for this category of printed pages

Total number of dimplex pages printed for this category of printed pages

Total number of simplex pages printed for this category of printed pages

Total number of duplex pages printed for this category of printed pages

Total number of simplex plus duplex pages printed for this category of printed pages

Total number of dimplex pages printed for this category of printed pages

Total number of simplex pages scanned, for this media size. Additional information: The 5 usage (simplex/duplex count, simplex/duplex click charge and paper size total) objects described here and below detail the usage for the scanner for each paper size defined in the PCL Implementors Guide and in the Media Size Table in the hpmib.txt. The OID binding is based on the click attribute and paper size. For example: The format for the OID is as follows: 3.4.1.5.x.y <-----> | | | | \ / | paper size / \ PRINTER-CLICK_TOTALS ROOT \ OID click attribute 1..5 x values are 1..5: 1) simplex count 2) simplex click charge 3) duplex count 4) duplex click charge 5) printer or scanner paper size total (i.e. depends if the root OID is referrring to the printer or scanner). y : paper size as defined in the Media Size Table in the hpmib.txt The click charge objects are of data type real and have a single digit of precision. Setting these objects to more than a single digit of precision will cause truncation at a single digit, for example, if click charge is set to 15.475 and later retrieved with a get, the value will be 15.400 for this object.

Charge for each simplex page printed in this media size.

Total number of duplex pages scanned, for this media size.

Charge for each duplex page scanned, for this media size.

The total charge for pages scanned, for this media size.

Total scanner charge or cost for all paper sizes scanned.

Total number of color simplex pages printed in this media size

Total number of color duplex pages printed in this media size

The total count for color pages printed in this media size

Total number of color dimplex pages printed in this media size. A color dimplex page is a color page that has been printed in duplex mode but the back side is blank. Dimplex pages occur when the printer firmware inserts a blank page in order to complete a duplexed job which is sent to the printer with an odd number of pages

Total number of mono pages printed in this fuser mode

Total number of color pages printed in this fuser mode

The total count for pages printed in this fuser mode

Total number of pages printed from this source tray

Total number of pages printed to this destination bin

This object provides information on whether the printer has the ability to communicate the write-status of the firmware download while the download is taking place.

If the design of the firmware-download implementation does not allow PML interaction during the download process, this value provides an estimation of the time where the printer will not be able to engage in PML communication. Additional information: If the design of the firmware-download implementation does not allow PML interaction during the download process, this value provides an estimation of the time where the printer will not be able to engage in PML communication. The calculated time is expected to be 140 secs. However, this time may increase as high as 280 secs as the flash part nears the maximum flash count.

Tells the number of times that firmware has been downloaded to the flash part. Additional information: Tells the number of times that firmware has been downloaded to the flash part. The default value will vary depending on how many times the firmware is rolled before shipping.

Provides the current or last reportable state of the firmware download process. The current state may not necessarily be the current state, but could be the post-mortem state.

Reports the manufacturer specified number of times that firmware can be downloaded to the flash part. A value of -1 means that there is no limit. A value of 0 means that downloading firmware is not permitted by this part. Any other positive integer value corresponds to the number of times that firmware can be downloaded to the flash part. Additional information: Reports the manufacturer specified number of times that firmware can be downloaded to the flash part. A value of -1 means that there is no limit. A value of 0 means that downloading firmware is not permitted by this part. Any other positive integer value corresponds to the number of times that firmware can be downloaded to the flash part. The current maximum write count is 500. This may change as flash technology evolves.

This returns the name of the printer. This should match the name in the header of the upgrade image being sent to the flash part. If the name does not match with the name returned then the image that we are attempting to download does not upgrade the printer firmware. Additional information: This object returns the HP name of the printer. This should match what is in the PJL header of the RFU job Web Jet Admin uses this to ensure the printer is available to be upgraded.

This object will return a string value representing the current revision of firmware that the printer is operating with. This is used to determine if code needs to be upgraded when an firmware bundle comes in, in an upgrade job. Additional information: Web Jet Admin uses the version string that is returned to determine what peices of an RFU bundle need to be upgraded when an RFU job is being built. This objects will return the version string of the printer.

This object provides information on whether the upgradable device has the ability to communicate the write-status of the upgrade while the upgrade is taking place.

If the design of the device upgrade implementation does not allow PML interaction during the download process, this value provides an estimation of the time where the device will not be able to engage in PML communication. The time returned will depend upon what device is attempting to be upgraded.

Tells the number of times that firmware for device X has been downloaded to the flash part. The default value will vary depending on how many times the firmware is rolled before shipping.

Provides the current or last reportable state of the device upgrade process. The current state may not necessarily be the current state, but could be the post-mortem state.

Reports the manufacturer specified number of times that firmware for device X can be downloaded to the flash part. A value of -1 means that there is no limit. A value of 0 means that downloading firmware is not permitted by this part. Any other positive integer value corresponds to the number of times that the firmware for device X can be downloaded to the flash part. The current maximum write count is 500. This may change as flash technology evolves.

This returns the name of the upgradable device. This should match the name in the header of the upgrade image being sent to the flash part. If the name does not match with any of the names returned then the device that we are attempting to upgrade is unavailable for upgrading. Additional information: This object returns the HP name of the printer and the upgradable devices. There is one Name object per upgradable device. This should match what is in the PJL header of the RFU job Web Jet Admin uses this to ensure the printer or device is available to be upgraded.

This object will return a string value representing the current revision of firmware that device X is operating with. This is used to determine if code needs to be upgraded when an firmware bundle comes in, in an upgrade job. Additional information: Web Jet Admin uses the version string that is returned to determine what peices of an RFU bundle need to be upgraded when an RFU job is being built. This internal object will return the current version string of the printer or device that it corresponds to.

Enables or disables the ability to upgrade the firmware associated with any device that is available to be upgraded. This will be set to on or off at the RFU level in that if this mode is on any available device can be upgraded and if this mode is off none of the devices can be upgraded. There is not an individual mode for each device. Trying to set this to a value other than eOn or eOff will cause an UnsupportedValue error to occur.

Returns eTrue if the device is able to process PJL user group variables. See the PJL Technical Reference for the proper syntax for setting these variables. Because there may be many user groups in some environments, this object allows a client application to optimize the print job by including user groups only when the device is able to process them

This object is used to enable/disable toner miser plus feature

The supported values are ON and OFF. The toner miser plus feature is turned OFF by default

This PML object is used by the WJA tool to allow administrators to enable or disable EWS information tab protection. When this option in selected/turned on the user will not be able to MAX-ACCESS anything on the EWS without logging in with the EWS device <<hidden>>(in case the EWS device <<hidden>> is configured). If the option is turned off the user will be able to access the information tab on the EWS page without providing the EWS device <<hidden>>(in case the EWS device <<hidden>> is configured), for all other tabs on the EWS page the user will have to login with EWS device <<hidden>>

This object is the master switch for the ePrint feature. By default this should be eOff(1). This differs from EPRINT-ENABLED in that ePrint connot be registered with the cloud when this is diabled while EPRINT-ENABLED allows registration and temporary disablement

Returns the current setting of the ePrint feature

This is the configured ePrint email address

This object reports the current setting of ePrint e-mail

This is the configured ePrint printer code

This object reports the current setting of the ePrint web services

This number represents the instance of jdi that has ePrint registered

This object is used to indicate whether the device supports ePrint or not. By default this should be eOff(1), but will be set to eOn(2) if the device supports ePrint

This object is used to indicate whether the JDI supports ePrint or not. By default this should be eOff(1), but will be set to eOn(2) if JDI supports ePrint

This custom fax modem commands will be executed on the modem every time a fax modem is initialized along with the predefined set of commands

Sets the index of the primary network interface to be used for outbound routing. Index 1 is EIO, 2 is wireless station, 3 is wireless access point and 4 is JDI.

Enable or disable wireless direct printing.

The amount of time, in seconds, to wait for more print job data to be received before an I/O timeout occurs. The I/O channel being timed is the I/O channel that received the data associated with the current print job. If an I/O timeout occurs, the PDL processing sub-system assumes all the data associated with the current print job has been received, and processes the end of job in an PDL specific manner. The POS specifies the supported values. Additional information: If an I/O timeout occurs,the PDL processing sub-system will consider it an end of job condition only if there is data from another I/O subsystem waiting to be processed. The supported values are 5 to 300 seconds. Setting to a value outside the supported range returns <noError> status and the value will be snapped to the nearest supported value.

Indicates if the device will switch between I/O channels when a job boundary is encountered and print job data is available on another I/O channel.

Returns or controls the manner in which the device performs I/O data buffering. I/O data buffering allows additional print job data to be buffered by the I/O sub- system in an effort to allow the computer sending the data to perform other tasks and to keep the PDL processing sub-system busy. eOff, I/O buffering is disabled. When eOn, I/O buffering is enabled and the IO-BUFFER-SIZE object controls the amount of memory set aside for I/O buffer. When eAuto, I/O buffering is enabled and the I/O buffer size is determined automatically by the device and the IO-BUFFER-SIZE object is not used. Additional information: In a PCL-only printer, all values may be set at any time. When there is less than 4M of memory installed, setting this object to eOn or eAuto will cause <badValue> to be returned. At exactly 4M of memory, eOn is not a valid setting. At more than 4M of memory any setting is valid, subject to the conditions listed in the interactions below.

Returns or configures the amount of memory, in bytes, dedicated to I/O print job data buffering. Attempting to set to an unsupported value causes the device to use the closest supported value. Each device POS should document the list of supported values. Additional information: In LaserJet 4050 Series the minimum supported value is 10K bytes (10240). The maximum supported value is dependent on total memory installed and the amount of memory currently being used by other memory consumers. Use the MAXIMUM-IO-BUFFERING-MEMORY object to determine this value. The following rules determine legal values for this object: 1) Sizes less than 10K bytes will snap to 10K bytes. 2) Sizes between 10K and 100K bytes will be rounded to the nearest 10K. 3) Sizes between 100K bytes and the maximum value allowed will round to the nearest 100K bytes. If the value had to be snapped or rounded, <noError> will be returned along with the actual value that was written. Attempting to set this object when IO-BUFFERING is eOff will cause a status of <genErr> to be returned. When IO-BUFFERING is eOff, reading this object will return a value of zero.

This objects name is misleading. Returns the maximum amount of additional memory, in bytes, that can be dedicated to buffering print job data.

Indicates if the I/O sub-system in the device is not ready. If there are no items in the collection (i.e. no bits are set), then the I/O sub-system is ready. If there is an item present, then the item indicates what is causing the I/O sub-system to be not ready. If the I/O sub-system is not ready due to a soft error, the soft error is considered to be an auto-continuable error, thus it can be acknowledged by setting the CONTINUE object to eTrue.

Indicates if the I/O sub-system in a warning condition.

Returns or changes the maximum parallel I/O port speed. An eSlow setting causes a 10 us busy pulse per received byte of data. An eFast setting causes a 1.5 us busy pulse per received byte of data. In rare cases, setting this value to eFast can cause the parallel port to no longer transfer data reliably.

Returns or changes whether the parallel I/O port supports bidirectional communication.

Returns or changes the maximum parallel I/O port speed, for port 1. This object is only supported if this port is a parallel port. An eSlow setting causes a 10 us busy pulse per received byte of data. An eFast setting causes a 1.5 us busy pulse per received byte of data. In rare cases, setting this value to eFast can cause the parallel port to no longer transfer data reliably.

Returns or changes whether the parallel I/O port supports bidirectional communication for port 1. This object is only supported if this port is a parallel port. Additional information: A get on this object returns the current mode for the parallel port. Setting this object specifies whether or not bidirectional communications will be allowed.

Behaves as SCLs Set Scanner Contrast Level command which is used for setting the scanner contrast level. Range is 0..100. Additional information: There are 11 different tonemap that will be used on scan images to change the contrast. Software can set the contrast setting to -125, -100, -75, -50, -25, 0, 50, 75, 100, and 125 to select the different tonemaps. A user can also set the value to -127, which is a special mode used by manufacturing to tell the device to use all linear tonemaps and to perform no gamma correction. The scan pml object does not snap the pml scan-contrast. However, the contrast setting is mapped to the correct tonemap within the device.

struct { unsigned_32bit x_res; /* 1st four bytes; big endian */ unsigned_32bit y_res; /* 2nd four bytes; big endian */ } Sets the scanning resolution. The x and y resolutions in this object are in fixed-point with 16 bits of fraction, and 16 bits of integer, and are in dots per inch. X is horizontal; Y is vertical. Examples of computing x_res and y_res: 300 dots/inch:round(300 * 65536) = 19660800 16 dots/mm: round(16 * 25.4 * 65536) = 26633830. If the device does not support the given combination, then itll select the nearest supported values in a device-dependent manner (documented in the POS). Additional information: The 4-pack device will support only: 100, 150, 200, 300 and 600. The Host SW may scale the image to many more resolutions. If an invalid resolution setting is passed to the device or the setting is greater than the max value(600ppi), the device will set the resolution to the default value. If the resolution setting is not 100, 150, 200, 300 or 600, the value is snapped up. For instance, if the value is < 100, the resolution is snapped to 100. If the value is between 101-149, the value is snapped to 150, etc. NOTE: The last 16 bits of the horizontal and vertical settings are ignored. Only the first 16 bits of the horizontal and vertical resolution setting are used.

Sets the method used when scanning. eBiLevelThesholded - One bit per pixel, using simple thresholding of greyscale scan data. eBiLevelHalfToned - One bit per pixel, using some kind of half-toning technique (such as dithering or error- diffusion) to approximate greyscale scan data. eGrey16 - 4 bits per pixel to represent 16 shades of grey. eGrey64 - 6 bits per pixel to represent 64 shades of grey. e3BitColor - 1 bit thresholded per Red, Green, and Blue plane. eGrey128 - 7 bits per pixel to represent 128 shades of grey. eGrey256 - 8 bits per pixel to represent 256 shades of grey. e24BitColor - 24 bits per pixel, 8 bits for Red, 8 bit for Green, and 8 bits for Blue.

Indicates the type of data compression applied to the image data in the scanning upload session.

Indicates the level of compression to be applied to the scanned image data for upload. Range is normalized to be between 0..100. The device POS determines the mapping of the normalized scale to the actual Q factor for JPEG. Additional information: The 4-pack will use the SCAN-COMPRESSION-FACTOR for JPEG as described above in the General Description.

Error status of the image scanning upload session.

Handshake mechanism between host and device to initiate scan operation and coordinate the transfer of scanned image data to the host. This object serves both as an indicator of scan upload activity as well as a trigger for the host to alter scan upload progress. The handshake is on a per page basis to allow greater host control. eScanUploadIdle - indicates the scan upload activity is not occurring. Host setting this object to eScanUploadIdle from eScanUploadActive will cause the scan upload activity to be prematurely terminated. Host may set object to this state at any time. Device sets object to this state only upon initial power up but will otherwise never set to this state of its own accord. eScanUploadStart - indicates host requesting to commence a scan to host operation. Host may set object to this state from eScanUploadIdle or eScanUploadNewPage. Device will not set object to this state of its own accord. eScanUploadActive - indicates scan upload activity is occurring. The device sets object to this state to indicate host may commence receiving scanned image data. During this state, the device will be writing scanned image data to the I/O channel. eScanUploadAborted - indicates the scanning and scan upload activity has terminated in error state. This value is set by the device. This state is not settable by the host. The host should transition this state to eScanUploadIdle. eScanUploadDone - indicates the device is signaling successful completion of scan upload activity and there are no more document pages in the scanner/ADF. The application should set this object to eScanUploadIdle. eScanUploadNewPage - indicates the device is signaling successful completion of scan upload activity for the current page and there remains at least one page in the scanner/ADF available for scanning. Host may choose to begin scan upload cycle by setting object to eScanUploadStart or end the cycle by setting object to eScanUploadIdle. Additional information: eScanUploadNewPage - indicates the device is signaling successful completion of scan upload activity for the current page. There may be a page in the device or not. The device will wait to prefeed another page until the application sets the object to eScanUploadStart. This was to fix a bug on HP LaserJet 1100 that a prefed page would cause a jam if the application set the object to eScanUploadIdle. The application could not create another scan job until the prefed page was removed. Host may choose to begin scan upload cycle by setting object to eScanUploadStart or end the cycle by setting object to eScanUploadIdle.

Sets the left scanner margin. The unit of measure should be documented in the device POS. Additional information: The margin value must be a multiple of 4 for alignment reasons. If the entered value is not a multiple of 4, the resolution value will be snapped down to the closest value divisible by 4.

Sets the right scanner margin. The unit of measure should be documented in the device POS. Additional information: The margin value must be a multiple of 4 for alignment reasons. If the entered value is not a multiple of 4, the resolution value will be snapped down to the closest value divisible by 4.

Identifies the serial number for the scanner accessory. If this is a writable object, the POS should indicate the maximum supported string length. This string should only use characters from the US-ASCII code set. Additional information: The serial number is 5 digit decimal number.

Model number of the scanner accessory. This string should only use characters from the US-ASCII code set. Additional information: Model number for the Fujitsu scanner.

Total number of sheets that have been fed through the Automatic Document Feed (ADF) accessory. Additional information: The Automatic Document Feed (ADF) count is incremented each time a sheet feeds through the ADF.

Total number of scans performed by a flatbed scanner accessory. Additional information: The count is only incremented when a sheet is scanned on the FLATBED.

Recommended cleaning interval in units of sheets scanned. Additional information: Recommended cleaning interval is in units of sheets scanned.

The number of sheets scanned since the last cleaning was performed. Additional information: The number of sheets that have gone through the ADF since the last cleaning was performed.

Recommended maintenance interval in units of sheets scanned. Additional information: Recommended maintenance interval is in units of sheets scanned.

The number of sheets scanned since the last maintenance was performed. Additional information: The number of sheets that have gone through the ADF since the last maintenance was performed.

ROM revision of the scanner accessory firmware. Additional information: ROM revision of the Fujitsu scanner is downloaded from the scanner after the attached scanner establishes communications to the printer.

Boot ROM revision of scanner copy processor firmware. Boot code to initialize the copy processor, establish communications with the scanner, and load the runtime code. Additional information: Boot ROM revision of the Pixel Magic - Copy Processor firmware is downloaded from the scanner after the attached scanner establishes communications to the printer.

Revision of the runtime firmware for the scanner copy processor. Runtime code which retrieves scanned data from the scanner and sends it to other devices such as a printer or PC host. Additional information: Revision of Pixel Magic - Copy Processor firmware shipped on the disk which is download into RAM for execution.

Revision of scanner service agent firmware. Service agent which accepts scanned data and processes scanner copy processor requests, resident in a device such as a printer or PC host. Additional information: Revision of the Scanner Service Agent firmware shipped on the disk as a Service Provider entity to retrieve scanned data from the scanner.

Revision of the control panel user interface firmware. Additional information: Revision of the copy processor user interface firmware shipped on the disk.

This object is used by the host to check which type of calibration this scan device supports. The device pos will describe the meaning and intent of each type of scan calibration supported. Additional information: This object is used by the host to check which type of calibration the firmware supports. This is in anticipation of the fact that the initial release of HP Laserjet 3200 will be calibrated off of a sheet, but the Rest of World release will be calibrated off of the platen.

Returns the contents of the NVRAM (Non-Volatile RAM) located in the scanner accessory. Additional information: Read bytes 0..39 of the NVRAM in the scanner. The Fujitsu Controller board has a total of 128 bytes of NVRAM.

Returns the second part of the contents of the NVRAM (Non-Volatile RAM) located in the scanner accessory. Additional information: Read bytes 40..79 of the NVRAM in the scanner. The Fujitsu Controller board has a total of 128 bytes of NVRAM.

Returns the third part of the contents of the NVRAM (Non-Volatile RAM) located in the scanner accessory. Additional information: Read bytes 80..119 of the NVRAM in the scanner. The Fujitsu Controller board has a total of 128 bytes of NVRAM.

Returns the fourth part of the contents of the NVRAM (Non-Volatile RAM) located in the scanner accessory. Additional information: Read bytes 120..127 of the NVRAM in the scanner. The Fujitsu Controller board has a total of 128 bytes of NVRAM.

Lets the host application set up target (eg.scan) destinations. The destinations can be a host network address and/or an application to be launched on that host. The string sent down has a list of KEYWORD=value; items. The data sent down also contains a string to be displayed in the device LCD display. The device POS specifies the number of strings that can be handled (eg. 20) and the replacement/expiration policy as new target destinations are added. Additional information: For push scanning on the 4-pack, there will be a limitation to the number of unique strings sent to the device via UI-ADD-OPTION. A host registers for push scanning by using the UI-ADD-OPTION object. HP Laserjet 3200 will limit the number of hosts registered for push scanning to 20. HP LaserJet 1220 will have a limitation of 1. Another limitation for the 4-pack is that the DISPLAY value must be at most 18 characters. This limitation is due to the control panel display.

Triggers a job from the device based on the option selected.

Lets the host application delete target eg. scan destinations that were setup with UI-ADD-OPTION. The host sends down the entire string that was sent earlier. The firmware looks for an exact match in its lists and deletes the requested option. Additional information: Removes an existing option only if it is uniquely matched by the given object value.

Indicates a count of the total pages jammed in the scannerslifetime.

Indicates a count of the total pages scanned through the ADF on the device. This may include scan to host jobs, copyjobs, and fax jobs. If only the total pages scanned to the host are wanted, use SCAN-ADF-PAGE-COUNT.

Indicates the total pages scanned through the ADF to the host from the device. If the total pages scanned through the scanner are needed for all features, including copy and fax jobs, use the SCANNER-ADF-PAGE-COUNT object.

Indicates the image type of the scan data.

Indicates the subsampling used for Scan Data. 4:1:1, 4:2:2, and 4:3:3 subsampling are used to modify the scan image quality and amount of scan data by reducing the number of samples or pixels of the luminous and chrominance data.

This object facilitates the sending of a scan line of data from the scanner to a host. It grabs either raw or corrected data. SERVICE-PASSWORD must be set correctly to use this object. cScannerRequestRawScanLine - This is set by the host in order to signal to the firmware that it wants an scan line of raw (no PRNU or DSNU correction)data to be sent back up to the host. cScannerRequestCorrectedScanLine - This is set by the host in order to signal to the firmware that it wants a scan line of corrected (PRNU or DSNU correction) data to be sent back up to the host. cScannerSendDataRequest - This is set by firmware to indicate that it has acquired the scan line from scan engine and is ready to send the data to the host. cScannerSendDataOK - This is set by the host to indicate that it is ready to receive the data from the device. cScannerSendDataDone - This is set by the firmware to indicate that the transfer of data is complete. cScannerPickSheet - This is set by the host to tell the device to pick and stage the sheet of paper in the ADF. cScannerFlushSheet - This is set by the host to tell the device to flush the sheet of paper currently in the device. Additional information: This object is meant to be used by Manufacturing in order to facilitate the sending of a scan line of data from the scanner over HDT. It grabs either raw or corrected data.

This objects is set to the number of steps that the scan motor should move. SERVICE-PASSWORD must be setcorrectly to use this object. Additional information: This objects is set to the number of steps that the scan motor should move. It is meant to be used by Manufacturing in order to position the scanner shipping blocks.

Used to set the height of a scan image in Decapoints. The use of Decapoints as units of measure eliminates the need for the user to understand the scanner mechanics and the device supported resolutions. Additional information: This object will be used to set the height of the scan image. The height will be entered using the measurement of 1/720th of an inch. This will eliminate the host being tied to the scanner mechanics and needing to know what resolutions and number of lines the device supports.

This object is used to obtain statistics about the scan line that was previously obtained using the SCANNER-RETRIEVE-SCANLINE object. Just as SERVICE-PASSWORD must be set correctly for SCANNER-RETRIEVE-SCANLINE, it must be set correctly to use this object as well. Additional information: This object is used to obtain statistics about the scan line that was previously grabbed using the SCANNER_ RETRIEVE_SCANLINE object, max string is 256 bytes. The format is the following: max red value; position; min red value; position; max red pixel to pixel difference; position; red mean; max blue value; position; min blue value; position; max blue pixel to pixel difference; position; blue mean; max green value; position; min green value; position; max green pixel to pixel difference; position; green mean;

Describes the control language and formats supported for this scanner.

A 32-bit quantity that indicates the gamma correction to use on the scan image. The first 16 bits indicate the integral portion of the gamma correction. The last 16 bits indicate the fraction portion in units of 1/65536. An example is gamma correction value of 2.2 will be representedas 0x00023333 (2 & 13107/65536ths)). The 4-pack products (HP Laserjet 3200, HP Laserjet 1220, HP Laserjet 2200 & HP Laserjet 1200) software will set the gamma correction to be applied on the scan data. IPE SW will request a value of 1.0, which indicates no gamma correction. TWAIN software will request a value of 2.2 for grayscale scans and 2.9 for color scans. The device pos will indicate any deviation from the above description. Additional information: Indicates the gamma correction to use on the scan image. The first 16 bits indicate the integral portion of the gamma correction. The last 16 bits indicate the fraction portion and in units of 1/65536. An example is gamma correction value of 2.2 will be represented as 0x00023333 (2 & 13107/65536ths).

Indicates if the scan image should be padded with white data or not.

This relates to the number of copy pages printed on a device. The output sheet that is duplexed (made 2- sided) should be counted as 2 pages

This object tracks the page count for the pages scanned from the flatbed.

This object tracks the page count for the pages scanned for all jobs from the flatbed. This includes scan to host jobs, fax jobs, and copy jobs.

Used to specify whether optional hardware is installed or not. Additional information: This HP LaserJet MFP uses this object to allow a host to query whether or not it has an ADF installed, Letter/A4 flatbed, or Legal flatbed.

This object accesses a table used by firmware to modify clock edge values for CCD scanner modules. Additional information: This object accesses a table used by firmware to modify clock edge values for CCD scanner modules.

Returns a table of clock edges used by the scanner. Additional information: Returns a table of clock edges used by the scanner.

Setting this object to eYes will cause firmware to run the next scan job as if it were a copy job, using copy values for scanner h/w and image processing, and then return the data to the host as if it were a scan job. Setting this object to eNo will cause firmware to process scan jobs in the normal way. Additional information: Setting this object to eYes will cause firmware to run the next scan job as if it were a copy job, using copy values for scanner h/w and image processing, and then return the data to the host as if it were a scan job. Setting this object to eNo will cause firmware to process scan jobs in the normal way.

Indicates whether and why the scanner is not ready. A set bit indicates a problem. Additional information: ISSUES: HP LaserJet 1100 only used cScannerFeederJam. Tahiti does not have an ADF sensor. Can cScannerFeederEmpty still be used (i.e. when the device tries to pull a page, but the ADF is empty or a mispick occurred). cInvalidScannerMediaSize may be used. If a page is longer that 33 inches normally this would be shown to the host as a Jam. However, can the device use cInvalidScannerMediaSize instead?

Enumerates the range of selectable scanning resolutions. Format as follows: Each supported resolution is in the format: (m)x(n) where m describes the x dpi resolution along the paper width. n describes the y dpi resolution along the paper length. A scanner that supports several resolutions would enumerate each resolution separated by a comma. A scanner that supports a continuous resolution range would format its range as: (m1-m2)x(n1- n2) where m1 < m2, n1 < n2

Returns or changes the state of the calibration operation. cScanCalibrationIdle - indicates that calibration is not in progress. cScanCalibrationStart - This state is set by host to request calibration initiation. Device should not set to this state. cScanCalibrationActive - Indicates device is in calibration mode. Device sets cScanCalibrationActive to signal calibration is in process. cScanCalibrationAborted - Set by device to indicate calibration was prematurely terminated. Set by host when a calibration error occurs. cScanCalibrationSendDataRequest - Set by host when host wants to send data to the device. cScanCalibrationSendDataRequestOK - Set by the device to tell the host that the device is ready to accept data. cScanCalibrationSendDataRequestDone -Set by the device to indicate the data was received by the device. cScanCalibrationRequestScanBuffer - Set by the host to request a buffer from the device. cScanCalibrationDone - Set by the host to inform the device calibration is complete. The sequence of bits being set and the restrictions for setting bits should be documented in the device POS. Additional information: This object was originally defined for use on HP LaserJet 1100. HP Laserjet 3200 we will not be using values 3-6. These are no longer applicable since the calibration is completely contained within firmware.

Error status of the most recent calibration session. eNoError(1) - The calibation was successful. eUnknownCalibrationError(2) - An unknown error occurred. eScannerFeederEmpty(3) - The feeder contained nothing to scan. eLowMemory(4) - Insufficient memory available to complete the calibration. eWriteFailed(5) - Write to NVRAM failure. eScannerBusy(6) - Scanner is busy. Detailed information about the cause and remedy for each error should be documented in the device POS. Additional information: This object was originally defined for use on HP LaserJet 1100. We are proposing the new enums number 7-9. Note: Option 9 would only be set during a factory calibration to indicate that at least one pixel was not correctable by the digital calibration factors.

Indicates the scanner button has been pressed. The value changes to eOn(2) when the button is pressed. The host acknowledges the button press by setting the value to eOff(1).

Provides PWM and analog gain for the color channels. The range will vary based on scan mode. The device specific POS should describe the valid range. The format is the following: PWM value; red analog gain; green analog gain; blue analog gain. Additional information: The range will vary based on scan mode. The values will differ from those of San Diego. The initial value can be obtained at the start of warmup and the final value can be obtained at the end of warmup. The warmup period is about 2 minutes. The format is the following PWM value; red analog gain; green analog gain; blue analog gain;. The valid values for PWM value are 580 - 730 and the valid values for analog gains are 1.00-5.80. The gains are reported with accuracy to 2 decimal places. A sample return value would be 584;1.00;1.34;1.00;

Provides the pixel at which the LMW starts, as the ratio of the average LMW value to the six pixel average value. The device specific pos should specify the valid ranges for each value. The format is the following: LMW position; ratio of LMWavg to 6 pixel avg. Additional information: Provides the pixel at which the LMW starts as well as the ratio of the average LMW value over a 6 pixel average value. A algebraic representation of this ratio is: Average of Light Monitor Window pixels ______________________________________ Average of 6 test point pixels The 6 test point pixels do not inlcude any of the Light Monitor Window. A sample return value would be 50;0.059;.