IJ8060-MIB: View SNMP OID List / Download MIB

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. InkJet supports values of 0, 60, 900, 1800, 3600, 5400, 7200, 14400 seconds. A value of 0 means never enter sleep mode based on the print engine idle time. Setting to an unsupported value causes the printer to substitute a value (listed below) and to return <noError> status. Setting this value when the printer is in sleep mode will not cause it to wakeup unless it is set to 0. The values are as follow: <=0 snap to 0 >=1 and <= 479 snap to 60 (1 minute) >=480 and <= 1349 snap to 900 (15 minutes) >=1350 and <= 2249 snap to 1800 (30 minutes) >=2250 and <= 3149 snap to 2700 (45 minutes) >=3150 and <= 4499 snap to 3600 (1 hour) >=4500 and <= 6299 snap to 5400 (90 minutes) >=2700 and <= 5399 snap to 3600 (1 hour) >=5400 and <= 10799 snap to 7200 (2 hours) >=10800 snap to 14400 (4 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.

Controls front-panel date display format. Additional information: Controls front-panel date display format.

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. The behavior of each setting may vary depending on the device. The value will be stored in NVRAM

Allow the printer to be configured as a duplex or simplex printer. There will be a <<hidden>> encoded in this string and decoded by the printer firmware. If the <<hidden>> check passes the printer will be configured accordingly. Additional information: Used to configure engines for duplex enabled or not. Encoded configuration string is passed in, which is decoded by firmware. Firmware verifies config. string is valid, and retrieves device Configuration data. Expandable to accommodate future products configuration needs.

This object specifies whether all direct connect ports (parallel and USB) are available or ignored. JetDirect, embedded network connectivity, and third party add-on cards (such as Firewire) will be unaffected by setting this object.

This PML object can be used to enable or disable supplies status messages from being displayed on the control panel. eShow - show the status messages on the control panel. eDontShow - do not show the status messages on the control panel. Additional information: . This PML Object can be used to enable or disable the supplies status messages from being displayed on the control panel. eShow Show the status messages on the control panel. eDontShow Do not show the status messages on the control panel.

This object is used to inquire about and to control the power state of the device. The exact meaning of each enumeration may vary from device to device, but the general interpretation is as follows: ePowerStateAwake: The device is idle (immediately ready to process a job) or processing a job. ePowerStatePowerSave: The device is in a low power state and will not be immediately available to process an incoming job. A warm-up time of several seconds can be expected. ePowerStateSleep: The device is in a sleep state. It uses less power than when in the power save state. It can also be expected to need a substantially longer warm-up time than when in the power save state. ePowerStateOff: The device is powered off. Note that when the device is powered off then SNMP/PML requests obviously cannot be honored. Therefore ePowerStateOff will likely never be returned from a PML get operation. However, ePowerStateOff could potentially be used in a PML set operation to power down the device if it has a software/firmware controllable power switch. For a given product it may not be possible to have the device enter the requested state due to the current state of the device. E.g., it may not be possible to enter the power save state if the device currently is in the sleep state. In this case a set operation will have an execution outcome of <genErr>. The same execution outcome can be expected if the device is processing a job and an attempt is made to e.g. bring the device into the power save state or the sleep state. A get operation on the object returns the current power state of the device. While the device is transitioning from one state to another one of the values ePowerStateTransitioningToAwake, ePowerStateTransitioningToPowerSave, ePowerStateTransitioningToSleep or ePowerStateTransitioningToOff will be returned from a PML get operation. An attempt to perform a PML set with any of these four values will yield <badValue>. Additional information: nothing beyond old description

writing an integer 0 will do factory reset on system variables, MFP Settings and the .NET database without a reboot. Additional information: nothing beyond old description

Display or DoNotDisplay the warning message on control panel of long grain optimiation. Additional information: nothing beyond old description

ePowerSaveOff - printer stays awake all the time, can only sleep if sleep button is hit. ePowerSaveUseSleepDelay - use sleep delay the old way, sleep schedule is ignored . ePowerSaveUseSleepSchedule - sleep delay time is ignored, stay awake in wake period, sleep in 15 minutes in sleep period. ePowerSaveMaximize - set the sleep delay to 15 minutes, so wether in wake or sleep period it will sleep in 15 minutes. ePowerSaveCustom - set the sleep delay to 45 minutes, use sleep delay during wake period, sleep in 15 minutes in sleep period. Additional information: nothing beyond old description

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: Setting the <<hidden>> object will enable setting this object.

This object will set the cAllPermDevices bit when a full perm storage initialization occurs (as would be the case for a brand new system or as a result of a powerup key sequence or <<hidden>> object request). If only one device was initialized (as would be the case if a disk were added to an existing system or a formatter were swapped out), then only the appropriate collection bits will be returned. If there are no collection bits set then this indicates that no initialization took place.

Sets the printers current time in (UTC). The format of the string is YYYYMMDDHHMMSS. Where YYYY is the year. MM is the month (1-12) DD is the day of the month (1-31) HH is the hour of the day (0-23) MM is the minutes (0-59) SS is the seconds (0-59) Device POS must specify the conditions for setting this object.

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). Additional information: A C structure containing the following fields: typedef struct { ubyte yr; /* year: 3 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).

A read of this object will return the current SERVICE ID value in the printer. The format is YYDDD where: YY = calendar year - 1990 DDD = (calendar month - 1) * 30 + (calendar day of the month or 30, if > 30) A write of this object will only succeed if the MANUFACTURING-CONTROL PML object has been set with the correct <<hidden>>. If the write operation is not allowed, this object will return an <genErr> status. Additional information: Setting the <<hidden>> object will enable setting this object.

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.

Controls front-panel time display format. Set to eTimeDisplayTwelveHour for AM/PM display. Set to eTimeDisplayTwentyFourHour for military-type display. Additional information: 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: 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 accourding to the action defined by JOB-INPUT-AUTO-CONTINUE-MODE. 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. 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. cUSMediaSizeOverride - The device is allowed to substitute US media sizes (letter, etc.) for ISO media sizes (A4, etc.). cISOMediaSizeOverride - The device is allowed to substitute ISO media sizes (A4, etc.) for US media sizes (letter, etc.). Additional information: Returns or sets the device behavior when the desired media is not currently available. cCancelJob - The device cancels the job regardless of other item settings. cAutoMediaSizeOverride - The device is allowed to substitute a different size media. cAutoMediaNameOverride - The device is allowed to substitute a different media name. -- cUSMediaSizeOverride - The device is allowed to substitute -- US media sizes (letter, etc.) for ISO media sizes -- (A4, etc.). -- cISOMediaSizeOverride - The device is allowed to substitute -- ISO media sizes (A4, etc.) for US media sizes -- (letter, etc.). 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 describes the action that is performed when the JOB-INPUT-AUTO-CONTINUE-TIMEOUT expires.

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 Inkjet 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

The string displayed on the devices front panel in place of the printers built-in background status string. It would alternate with warning messages and would overwrite highest Regular Priority Status message such as PAUSED. The object could be used to display higher priority third party messages which are important to be displayed even if printer is offline. This would not overwrite any HighStatus or Error type message. Additional information: 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 lower than the PAUSED message. In other words, this messages can replace all the regular priority status messages as EPOffline is the highest regular status priority. To clear the message, write a null string to BACKGROUND-STATUS-MSG-HIGHER-PRIORITY.

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: 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.

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 <<hidden>> 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. 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. A color printer that only has a RAMDISK installed is treated like there is no disk and therefore this object will not exist. 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

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. Reading it will return the last key pressed either on the control panel or via PML. The device POS will specify which keys are supported.

A counter which increments whenever the contents of the front panel display changes. This object is implemented as a 32-bit signed integer which rolls over to zero when it reaches a maximum value.

Reading this object returns a 32-bit Cyclical Redundancy Check (CRC) which represents the current contents of the display. Additional information: This object has been implimented as an 32-bit CRC for this product.

Reading this object returns a graphical file format image representing the current pixel content of the display. The device POS will specify the expected screen resolution, color depth of the display and graphics file format for a given product (eg. 160x64x1 GIF format OR 640x240x4 JPEG format). If the image is large enough that it needs to be returned in multiple objects then each array object will contain a portion of the image. The image will then need to be reconstructed by a host application. An application that needs to determine if their is an additional object to be retreived will need to perform a GETNEXT operation until there are no more objects in the sub-tree. Additional information: This object returns a GIF image that represents the current contents of the 640x240x2 control panel display. Most display images require more than one instance of this object in order to retreive the complete GIF image.

Writing this object simulates pressing a key on the control panel. Reading it will return the last key pressed either on the control panel or via PML. This object obsoletes/replaces CONTROL-PANEL-BUTTON-PRESS object which was unable to represent each of the possible key combinations of our current control panels (ie. Full QWERTY keyboard). The device POS will specify the full range of keys supported by this object. Additional information: >>>>This object is write-only for hw_rom variant but it is read-write for all other variants.<<<<< Writing this object simulates pressing a key on the control panel. Reading it will return the last key pressed either on the control panel or via PML. This object obsoletes/replaces CONTROL-PANEL-BUTTON-PRESS object which was unable to represent each of the possible key combinations of our current control panels (ie. Full QWERTY keyboard). The device POS will specify the full range of keys supported by this object. The implementation of this object supports the Unified Key Encoding Scheme.

Controls the time zone, which can be chosen from a list of time zones similar to the one used by Microsoft Windows operating system: eTzDateline -12:00 International Date Line West eTzSamoa -11:00 Midway Island, Samoa eTzHawaiian -10:00 Hawaii eTzAlaskan -09:00 Alaska eTzPacific -08:00 Pacific Time (US & Canada); Tijuana eTzUSMountain -07:00 Arizona eTzMexico2 -07:00 Chihuahua, La Paz, Mazatlan eTzMountain -07:00 Mountain Time (US & Canada) eTzCentralAmerica -06:00 Central America eTzCentral -06:00 Central Time (US & Canada) eTzMexico -06:00 Guadalajara, Mexico City, Monterrey eTzCanadaCentral -06:00 Saskatchewan eTzSAPacific -05:00 Bogota, Lima, Quito eTzEastern -05:00 Eastern Time (US & Canada) eTzUSEastern -05:00 Indiana (East) eTzAtlantic -04:00 Atlantic Time (Canada) eTzSAWestern -04:00 Caracas, La Paz eTzPacificSA -04:00 Santiago eTzNewfoundland -03:30 Newfoundland eTzESouthAmerica -03:00 Brasilia eTzSAEastern -03:00 Buenos Aires, Georgetown eTzGreenland -03:00 Greenland eTzMidAtlantic -02:00 Mid-Atlantic eTzAzores -01:00 Azores eTzCapeVerde -01:00 Cape Verde Is. eTzGreenwich 00:00 Casablanca, Monrovia eTzGMT 00:00 Greenwich Mean Time : Dublin, Edinburgh, Lisbon, London eTzWEurope +01:00 Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna eTzCentralEurope +01:00 Belgrade, Bratislava, Budapest, Ljubljana, Prague eTzRomance +01:00 Brussels, Copenhagen, Madrid, Paris eTzCentralEuropean +01:00 Sarajevo, Skopje, Warsaw, Zagreb eTzWCentralAfrica +01:00 West Central Africa eTzGTB +02:00 Athens, Beirut, Istanbul, Minsk eTzEeurope +02:00 Bucharest eTzEgypt +02:00 Cairo eTzSouthAfrica +02:00 Harare, Pretoria eTzFLE +02:00 Helsinki, Kyiv, Riga, Sofia, Tallinn, Vilnius eTzJerusalem +02:00 Jerusalem eTzArabic +03:00 Baghdad eTzArab +03:00 Kuwait, Riyadh eTzRussian +03:00 Moscow, St. Petersburg, Volgograd eTzEAfrica +03:00 Nairobi eTzIran +03:30 Tehran eTzArabian +04:00 Abu Dhabi, Muscat eTzCaucasus +04:00 Baku, Tbilisi, Yerevan eTzAfghanistan +04:30 Kabul eTzEkaterinburg +05:00 Ekaterinburg eTzWestAsia +05:00 Islamabad, Karachi, Tashkent eTzIndia +05:30 Chennai, Kolkata, Mumbai, New Delhi eTzNepal +05:45 Kathmandu eTzNCentralAsia +06:00 Almaty, Novosibirsk eTzCentralAsia +06:00 Astana, Dhaka eTzSriLanka +06:00 Sri Jayawardenepura eTzMyanmar +06:30 Rangoon eTzSEAsia +07:00 Bangkok, Hanoi, Jakarta eTzNorthAsia +07:00 Krasnoyarsk eTzChina +08:00 Beijing, Chongqing, Hong Kong, Urumqi eTzNorthAsiaEast +08:00 Irkutsk, Ulaan Bataar eTzMalayPeninsula +08:00 Kuala Lumpur, Singapore eTzWAustralia +08:00 Perth eTzTaipei +08:00 Taipei eTzTokyo +09:00 Osaka, Sapporo, Tokyo eTzKorea +09:00 Seoul eTzYakutsk +09:00 Yakutsk eTzCenAustralia +09:30 Adelaide eTzAUSCentral +09:30 Darwin eTzEAustralia +10:00 Brisbane eTzAUSEastern +10:00 Canberra, Melbourne, Sydney eTzWestPacific +10:00 Guam, Port Moresby eTzTasmania +10:00 Hobart eTzVladivostok +10:00 Vladivostok eTzCentralPacific +11:00 Magadan, Solomon Is., New Caledonia eTzNewZealand +12:00 Auckland, Wellington eTzFiji +12:00 Fiji, Kamchatka, MarshallIs. eTzTonga +13:00 Nukualofa Additional information: Controls the time zone, which can be chosen from a list of time zones similar to the one used by Microsoft Windows operating system: eTzDateline -12:00 International Date Line West eTzSamoa -11:00 Midway Island, Samoa eTzHawaiian -10:00 Hawaii eTzAlaskan -09:00 Alaska eTzPacific -08:00 Pacific Time (US & Canada); Tijuana eTzUSMountain -07:00 Arizona eTzMexico2 -07:00 Chihuahua, La Paz, Mazatlan eTzMountain -07:00 Mountain Time (US & Canada) eTzCentralAmerica -06:00 Central America eTzCentral -06:00 Central Time (US & Canada) eTzMexico -06:00 Guadalajara, Mexico City, Monterrey eTzCanadaCentral -06:00 Saskatchewan eTzSAPacific -05:00 Bogota, Lima, Quito eTzEastern -05:00 Eastern Time (US & Canada) eTzUSEastern -05:00 Indiana (East) eTzAtlantic -04:00 Atlantic Time (Canada) eTzSAWestern -04:00 Caracas, La Paz eTzPacificSA -04:00 Santiago eTzNewfoundland -03:30 Newfoundland eTzESouthAmerica -03:00 Brasilia eTzSAEastern -03:00 Buenos Aires, Georgetown eTzGreenland -03:00 Greenland eTzMidAtlantic -02:00 Mid-Atlantic eTzAzores -01:00 Azores eTzCapeVerde -01:00 Cape Verde Is. eTzGreenwich 00:00 Casablanca, Monrovia eTzGMT 00:00 Greenwich Mean Time : Dublin, Edinburgh, Lisbon, London eTzWEurope +01:00 Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna eTzCentralEurope +01:00 Belgrade, Bratislava, Budapest, Ljubljana, Prague eTzRomance +01:00 Brussels, Copenhagen, Madrid, Paris eTzCentralEuropean +01:00 Sarajevo, Skopje, Warsaw, Zagreb eTzWCentralAfrica +01:00 West Central Africa eTzGTB +02:00 Athens, Beirut, Istanbul, Minsk eTzEeurope +02:00 Bucharest eTzEgypt +02:00 Cairo eTzSouthAfrica +02:00 Harare, Pretoria eTzFLE +02:00 Helsinki, Kyiv, Riga, Sofia, Tallinn, Vilnius eTzJerusalem +02:00 Jerusalem eTzArabic +03:00 Baghdad eTzArab +03:00 Kuwait, Riyadh eTzRussian +03:00 Moscow, St. Petersburg, Volgograd eTzEAfrica +03:00 Nairobi eTzIran +03:30 Tehran eTzArabian +04:00 Abu Dhabi, Muscat eTzCaucasus +04:00 Baku, Tbilisi, Yerevan eTzAfghanistan +04:30 Kabul eTzEkaterinburg +05:00 Ekaterinburg eTzWestAsia +05:00 Islamabad, Karachi, Tashkent eTzIndia +05:30 Chennai, Kolkata, Mumbai, New Delhi eTzNepal +05:45 Kathmandu eTzNCentralAsia +06:00 Almaty, Novosibirsk eTzCentralAsia +06:00 Astana, Dhaka eTzSriLanka +06:00 Sri Jayawardenepura eTzMyanmar +06:30 Rangoon eTzSEAsia +07:00 Bangkok, Hanoi, Jakarta eTzNorthAsia +07:00 Krasnoyarsk eTzChina +08:00 Beijing, Chongqing, Hong Kong, Urumqi eTzNorthAsiaEast +08:00 Irkutsk, Ulaan Bataar eTzMalayPeninsula +08:00 Kuala Lumpur, Singapore eTzWAustralia +08:00 Perth eTzTaipei +08:00 Taipei eTzTokyo +09:00 Osaka, Sapporo, Tokyo eTzKorea +09:00 Seoul eTzYakutsk +09:00 Yakutsk eTzCenAustralia +09:30 Adelaide eTzAUSCentral +09:30 Darwin eTzEAustralia +10:00 Brisbane eTzAUSEastern +10:00 Canberra, Melbourne, Sydney eTzWestPacific +10:00 Guam, Port Moresby eTzTasmania +10:00 Hobart eTzVladivostok +10:00 Vladivostok eTzCentralPacific +11:00 Magadan, Solomon Is., New Caledonia eTzNewZealand +12:00 Auckland, Wellington eTzFiji +12:00 Fiji, Kamchatka, Marshall Is. eTzTonga +13:00 Nukualofa

Determines whether or not the automatic adjustment for daylight savings time is enabled. If its enabled the device local time will be automatically adjusted for DST period. Additional information: Determines whether or not the automatic adjustment for daylight savings time is enabled. If its enabled the device local time will be automatically adjusted for DST period

A C structure containing the following fields: typedef struct { ubyte hour; /* hour: 0 to 23 */ ubyte weekday; /* weekday: 0(Sunday) to 6 */ ubyte occurrence; /* occurrence in the month: 1 to 5 */ ubyte month; /* month: 1 to 12 */ } dst; where ubyte is an unsigned byte (0-255). Additional information: A C structure containing the following fields: typedef struct { ubyte hour; /* hour: 0 to 23 */ ubyte weekday; /* weekday: 0(Sunday) to 6 */ ubyte occurrence; /* occurrence in the month: 1 to 5 */ ubyte month; /* month: 1 to 12 */ } dst; where ubyte is an unsigned byte (0-255).

A C structure containing the following fields: typedef struct { ubyte hour; /* hour: 0 to 23 */ ubyte weekday; /* weekday: 0(Sunday) to 6 */ ubyte occurrence; /* occurrence in the month: 1 to 5 */ ubyte month; /* month: 1 to 12 */ } dst; where ubyte is an unsigned byte (0-255). Additional information: A C structure containing the following fields: typedef struct { ubyte hour; /* hour: 0 to 23 */ ubyte weekday; /* weekday: 0(Sunday) to 6 */ ubyte occurrence; /* occurrence in the month: 1 to 5 */ ubyte month; /* month: 1 to 12 */ } dst; where ubyte is an unsigned byte (0-255).

Controls the offset in minutes to be added to the time when DST is in effect. Additional information: Controls the offset in minutes to be added to the time when DST is in effect

This object is used to reset (set back to factory default for the current time zone) or read the current status of the DST settings. When Set to eResetToDefault, this object can be used to reset all the DST related objects back to their factory default values. Setting this object with an enumerated value of eCustomized has no effect. When a Get operation is performed on this object it will return a value eResetToDefault if all DST settings are still set to they factory value. It will return eCustomized if any DST parameter has been set to a custom value. Additional information: This object is used to reset (set back to factory default for the current time zone) or read the current status of the DST settings. When Set to eResetToDefault, this object can be used to reset all the DST related objects back to their factory default values. Setting this object with an enumerated value of eCustomized has no effect. When a Get operation is performed on this object it will return a value eResetToDefault if all DST settings are still set to they factory value. It will return eCustomized if any DST parameter has been set to a custom value.

To check if Email service is operational on the device. Email is operational if email feature is enabled on the device and the SMTP gateway is configured.

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: 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. The value of this object does not change based on the installed options. The default of this object is the same on all InkJet 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 <<hidden>> 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.

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 <OKNearestLegal ValueSubstituted>.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 <OKNearestLegal ValueSubstituted>.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 <OKNearestLegal ValueSubstituted>.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.

This object returns the formatter serial number for the device. The value returned from this object is the FORMATTERNUMBER system variable. 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: Returns the formatter serial number, prefixed with the PML_UNICODE_PREFIX..

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. Additional information: Returns a string describing the firmware version of the embedded JDI LAN card.

Returns information describing the manufacture of the I/O card installed in MIO/EIO interface 4. May include serial number and firmware revision. Additional information: Returns a string describing the embedded JDI LAN card.

Returns an indication of the type of option installed in MIO/EIO interface 4. See SIMM1-TYPE for an explanation of the enumerations. Additional information: Returns eEmpty if the embedded JDI LAN card is disabled. Returns eIOCard if the embedded JDI LAN card is enabled.

The NVRAM Diagnostics information consist of e-serial number, born-on date, manufacturing date, page counter, finisher counter, jam rate history, event log, and any other device-specific information that the PHD1 stores in NVRAM. This information will be returned as a string with XML format within XML tags. Additional information: The NVRAM Diagnostics information consist of e-serial number, born-on date, manufacturing date, page counter, finisher counter, jam rate history, event log, and any other device-specific information that the PHD2 stores in NVRAM. This information will be returned as a string with XML format within XML tags.

Returns product information identifying PHD device 2. Example: XXXX. Additional information: Returns product information identifying the first paper handling device in the device chaing, PHD device 2. If PDH device 2 does not exist, ERROR-UNKNOWN-OBJECT-IDENTIFIER will be returned.

Returns information describing the manufacture of PHD 2. May include serial number and firmware revision. Additional information: Returns information describing the manufacture of PHD 2. If PHD 2 does not exist, ERROR-UNKNOWN-OBJECT-IDENTIFIER will be returned.

Returns an indication of the type of option installed in PHD interface 2. See SIMM1-TYPE for an explanation of the enumerations. Additional information: Returns an indication of the type of option installed in PHD interface 2. If PHD 2 does not exist, ERROR-UNKNOWN-OBJECT-IDENTIFIER will be returned.

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: Returns an indication of the capacity of the installed option. For eInputPHD or eOutputPHD, or eBindingPHD the number of input trays or output bins is returned. If PHD 2 does not exist, ERROR-UNKNOWN-OBJECT-IDENTIFIER will be returned.

This object is a binary 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. Additional information: If this object is set to eEnable, the Supplies Status messages will not be shown on the CP.

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.

The USB Host protocol is supported by the device when the value returned is eTrue. The USB Host protocol is not supported when the value returned is eFalse.

Returns the serial number of a connected USB device as defined in the Standard Device Descriptor of the Universal Serial Bus Specification Version 2.0.

Returns the description of the manufacturer of a connected USB device as defined in the Standard Device Descriptor of the Universal Serial Bus Specification Version 2.0.

Returns the product description of a connected USB device as defined in the Standard Device Descriptor of the Universal Serial Bus Specification Version 2.0.

Returns the Vendor 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.

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.

The USB-DEVICE-KIND object classifies a USB device into one of four broad categories: \ eUSBStorageDevice(1): The USB device is strictly a device for storing data. \ eUSBNonStorageDevice(2): The USB device has no storage capability (e.g., a card reader). \ eUSBCompositeDevice(3): The USB device has storage capability and additional functionality normally not associated with a storage device. \ eUSBUnsupportedDevice(4): The USB device was detected, but no driver exists for the device or the device draws more current than allowed. \

Returns the name of the low-level USB driver supporting this device.

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>. It uses job IDs in the range of -1..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 will be returned on a read does not apply. A -1 represents the current job

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: InkJet 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. Note: It is possible that traps generated by this object have the same value. This is caused by the architecture of the InkJet System. In the InkJet System, it is highly probable that the object value will change so rapidly that when the trap is processed, PML will read the same value twice. This is timing related and will generally be seen at the end of a job.

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. Smokey 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. InkJet retains the job-info- objects for the MAX_JOBS_IN_LIST (32) 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 2,147,483,647 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.

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 InkJet, 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 none 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 InkJet, 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.

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.

Contains the media size of the printed job. The media size of the first page will decide the media size of the entire job. The return value of this object will only be valid when the printer finishes printing the entire job.

Contains the media type of the printed job. The media type of the first page will decide the media type of the entire job. The return value of this object will only be valid when the printer finishes printing the entire job.

Contains the finishing option used on the printed job. The finishing option specified for the first page will decide the finishing option of the entire job. The return value of this object will only be valid when the printer finishes printing the entire job.

Contains the total number of simplex pages printed in a particular job.

Contains the total number of duplex pages printed in a particular job.

Contains the total number of monochrome pages printed in a particular job.

Contains the total number of color pages printed in a particular job.

Contains the total number of black pixels used in a particular job.

Contains the total number of yellow pixels used in a particular job.

Contains the total number of cyan pixels used in a particular job.

Contains the total number of magenta pixels used in a particular job.

Keeps track of what type of job is processed.

Contains the total number of fixer pixels used in a particular job.

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 32-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 or stored. There are 4 options: eHoldOff: The job is printed but not retained on the disk. eHoldOn: The job is printed and stored temporarily on the disk. eHoldStore: The job is not printed but stored on the disk. eHoldProof: One copy of the job is printed and the remaining copies are stored on the disk.

The variable specifies the security level of the job. eHoldTypePublic: The job does not require a PIN in order to release the job for printing. eHoldTypePrivate: 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. For security purposes, you can no longer get the value of the 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. Bytes 8-11 (optional) contain the PIN for a Private job.

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: Setting this to a value that is not a Held Job on the system or is a Private Held Job returns <ErrUnsupValue>. To delete a private Held Job, you must use the PML object HELD-JOB-PRINT with a quantity of 0 and supply the correct HELD-JOB-PIN with the request. (See HELD-JOB-PRINT)

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, held jobs are not removed, but must be explicitly removed through the Control Panel or the PML object HELD-JOB-DELETE.

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. This object is between 1 and 500. Returns <noSuchName> status if attempting to access this object and there is no storage device is installed.

This object allows the system partition to be written to. It consists of a C structure containing the following fields: typedef struct { ubyte <<hidden>>[8]; ubyte volumenumber; } fs_writeable_system_partition_t; which is described below: Bytes 0 - 7: contain the <<hidden>> Byte 8 : is the volume number Access to this command is controlled by the <<hidden>>. If the <<hidden>> 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 <<hidden>> 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 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 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). 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 is used to control access to the file system of the device. It is always readable. It is writable when <<hidden>> is not the empty string, and a successful write to that object with the current <<hidden>> has preceded the write to this object. In other words, the <<hidden>> 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 <<hidden>> object exits the authenticated state. <<hidden>> must then be written to again with the current <<hidden>> 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 <<hidden>> is the empty string or when a write to <<hidden>> with the current <<hidden>> has preceeded the write to the object. When <<hidden>> is not the empty string then this object becomes read-only after a successful write to it. <<hidden>> must then be written to again with the current <<hidden>> in order to make another write operation on the object possible. If the <<hidden>> is incorrectly set, this object becomes read-only until the <<hidden>> 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 <<hidden>> is the empty string or when a write to <<hidden>> with the current <<hidden>> has preceeded the write to the object. When <<hidden>> is not the empty string then this object becomes read-only after a successful write to it. <<hidden>> must then be written to again with the current <<hidden>> in order to make another write operation on the object possible. If the <<hidden>> is incorrectly set, this object becomes read-only until the <<hidden>> 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.

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 physical 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 physical 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 physical 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 InkJet 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

This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: This item contains the date and the time when the error occurred. It returns the date and the time at which the error occured in hexadecimal. For instance, if date is 2004-Jul-13 and time is 03:15 am when the error was logged, then we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month 07 0d(hex) - corresponds to date 13 03(hex) - corresponds to hour- 03 0f(hex) - corresponds to min- 15. If there is currently no error entry , 00 00 00 00 00 will be returned. See ERROR1-CODE for an explanation of the order used for storing errors.

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.

This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME.

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.

This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME.

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.

This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME.

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.

This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME.

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.

This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME.

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.

This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME.

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.

This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME.

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.

This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME.

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.

This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME.

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.

This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME.

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.

This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME.

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.

This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME.

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.

This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME.

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.

This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME.

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.

This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME.

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.

This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME.

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.

This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME.

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.

This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME.

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.

This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME.

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.

This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME.

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.

This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME.

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.

This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME.

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.

This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME.

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.

This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME.

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.

This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME.

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.

This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME.

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.

This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME.

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.

This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME.

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.

This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME.

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.

This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME.

Contains some sort of 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.

This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME.

Contains some sort of 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.

This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME.

Contains some sort of 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.

This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME.

Contains some sort of 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.

This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME.

Contains some sort of 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.

This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME.

Contains some sort of 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.

This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME.

Contains some sort of 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.

This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME.

Contains some sort of 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.

This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME.

Contains some sort of 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.

This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME.

Contains some sort of 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.

This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME.

Contains some sort of 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.

This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME.

Contains some sort of 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.

This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME.

Contains some sort of 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.

This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME.

Contains some sort of 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.

This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME.

Contains some sort of 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.

This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME.

Contains some sort of 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.

This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME.

Contains some sort of 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.

This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME.

Contains some sort of 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.

This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME.

Contains some sort of 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.

This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME.

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.

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: <table> Protocol | Number ---------+------- UDP/IP | 17 IPX | 1000 MLC | 4660 </table> 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: <table> Address Family | Number ---------------+------- Internet | 2 NetWare | 6 MLC | 22136 </table> 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. 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.

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. eAuto turns on the RAM disk functionality and creates a RAM disk size determined by the printer based on the amount of installed memory.

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 the size of 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.

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. Additional information: This is a volatile set of charge values that will always reset to the default values after a power-cycle. The default values represent a ratio of the page size as compared to a letter or A4 page size. Setting this object has the effect of altering PRINTED-MEDIA-DUPLEX-CHARGE to have a value that is twice that of the simplex charge.

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.

The number of pixels required to completely fill a page of this media size. The device POS will specify the resolution at which this pixel count was calculated. Additional information: The number of pixels required to fill a page of a specific media size. The OID binding is the media size you to query for. Only media sizes which the printer supports will be available.

Total number of letter equivalently weighted pages both color and mono combined with this printer. Additional information: The combined total per page size of simplex and duplex color pages plus simplex and duplex mono pages.

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 printer charge for all paper sizes 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.

This object reports the total source tray usage for the life of the printer. This value is reported on the usage page.

This object reports the total destination bin usage for the life of the printer. This value is reported on the usage page.

Total printer charge for all paper sizes printed in monochrome only. Additional information: This is the total charge over the range of all supported media sizes for duplex and simplex mono pages.

Total printer charge for all paper sizes printed in color only. Additional information: This is the total charge over the range of all supported media sizes for duplex and simplex color pages.

A value indicating the threshold value for this category of pages. The device POS will indicate the units of measure for this threshold value. Additional information: This usage threshold represents the number of 600dpi color pixels requested for a given image. The OID bindings for this object are as follows: 1 = Professional (BEST) - Full Color > 90K color pixels 2 = Professional (BEST) - Accent Color <= 90K color pixels 3 = General Office (GOOD) - Full Color > 90K color pixels 4 = General Office (GOOD) - Accent Color <= 90K color pixels These objects are normally read-only.

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. Additional information: The usage (simplex/duplex/dimplex count and charge objects described here and below detail the usage for the printer for each catagory of threshold/PQ and media size - as defined in the PCL Implementors Guide and in the Media Size Table in the hpmib.txt. The OID bindings are based on the coverage threshold/PQ and media size. For example: The format for the OID is as follows: 1.1.16.7.1.1.m.n <----------> | | | | | / | \ Base OID | media size [1..32768] \ \ Threshold/PQ Category [1..4] m - Threshold/PQ values are 1..4: 1) Color Threshold 1 - Print Quality Best 2) Color Threshold 2 - Print Quality Best 3) Color Threshold 1 - Print Quality Good 4) Color Threshold 2 - Print Quality Good n - media size integer as defined in the Media Size Table in the hpmib.txt. The sum of all PML object values with the same base OID and m value for a given media size will be returned by the corresponding PRINTED-MEDIA-COLOR-XXX-COUNT/CHARGE object.

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.

This object reports the total of monochrome simplex pages printed on this device. This value is the sum of all PRINTED-MEDIA-SIMPLEX-COUNT.n counter values.

This object reports the total of monochrome duplex pages printed on this device. This value is the sum of all PRINTED-MEDIA-DUPLEX-COUNT.n counter values.

This object reports the total of monochrome dimplex pages printed on this device. This value is the sum of all PRINTED-MEDIA-DIMPLEX-COUNT.n counter values.

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. Additional information: This is a volatile set of charge values that will always reset to the default values after a power-cycle. The default values represent a ratio of the page size as compared to a letter or A4 page size. Setting this object has the effect of altering SCANNED-MEDIA-DUPLEX-CHARGE to have a value that is twice that of the simplex charge.

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

Charge for each duplex page scanned, for this media size. Additional information: Setting this object has the effect of also altering the corresponding value for SCANNED-MEDIA-SIMPLEX-CHARGE with exactly half the value of the Duplex charge. Since the simplex charge is always half the duplex charge - this means that the first decimal place of the duplex charge must be evenly divisible by 2. This means that a Set operation to this object with a value of 2.3 will generate a PML response of OK_NEAREST_LEGAL_VALUE_SUBSTITUTED and the value written will snap to 2.2. The simplex charge will also take on a value of 1.1. The snap behavior for this object will always be as follows based on the first decimal place: if even then accept, otherwise snap to the next lower tenth.

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 pages printed from this source tray. Additional information: This object will track how many images have been printed with the original source tray as one of the following: 1. Envelope Feeder 2. Manual Feed Tray 3. Tray 1 4. Tray 2 5. Tray 3 6. Tray 4 7. Tray 5 8. External Tray 9. Other

Total number of pages printed to this destination bin. Additional information: This object will track how many images have been printed with the original destination bin as one of the following: 1. Face Down Bin 2. Face Up Bin 3. Bin 1 4. Bin 2 5. Bin 3 6. Bin 4 7. Bin 5 8. Other

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 objects input is a null-terminated string representing a fully-qualified path name for an executable file. This object causes the file to be executed by the OS. Additional information: This objects input is a null-terminated string of two or more whitespace-separated tokens. The first token is a path to a directory to make the current working directory. The second token is a path to an executable file to be executed. Any remaining whitespace-separated tokens are optional and will be passed as parameters to the executable. The paths to the directory and executable can be either PJL style (e.g., 1:\app\example) or UNIX-style (e.g., /hpmnt/dsk_ide1a/app/example). The executable is run in a separate process.

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 a 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.

Contains some sort of time stamp indicating when warning 1 occurred. Example time stamps include the actual time the warning 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 WARNING occurred. If there is currently no WARNING entry for this object, a 0 will be returned. Note that 0 may also be returned when there is a valid WARNING, but a current page count was unavailable. If WARNING1-CODE object also returns 0, then an WARNING has not yet been logged for this object. See WARNING1-CODE for an explanation of the order used for storing WARNINGs.

Contains a device specific warning code. Each device POS should list what warnings are logged to the warning log and the meaning of each supported warning code value. Additional information: Returns a device specific WARNING code. If the WARNING code returned is 0, then the printer has not yet logged an WARNING for this object. When the maximum number of WARNINGs is reached (30 on InkJet printers), and a new WARNING occurs, the WARNING in WARNING1-CODE will be replaced by the one in WARNING2-CODE, and so on until the last WARNING object will be given the value of the new WARNING. The WARNING 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 WARNING 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 WARNING 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 WARNING: 68 001A Example: If the WARNING is 55.04.241, then the WARNING 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 WARNING: 55.04.241

This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: This item contains the date and the time when the WARNING occurred. It returns the date and the time at which the WARNING occured in hexadecimal. For instance, if date is 2004-Jul-13 and time is 03:15 am when the WARNING was logged, then we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month 07 0d(hex) - corresponds to date 13 03(hex) - corresponds to hour- 03 0f(hex) - corresponds to min- 15. If there is currently no WARNING entry , 00 00 00 00 00 will be returned. See WARNING1-CODE for an explanation of the order used for storing WARNINGs.

Contains some sort of time stamp indicating when warning 2 occurred. Example time stamps include the actual time the warning 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 WARNING1-TIME-STAMP.

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

This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME.

Contains some sort of time stamp indicating when warning 3 occurred. Example time stamps include the actual time the warning 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 WARNING1-TIME-STAMP.

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

This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME.

Contains some sort of time stamp indicating when warning 4 occurred. Example time stamps include the actual time the warning 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 WARNING1-TIME-STAMP.

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

This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME.

Contains some sort of time stamp indicating when warning 5 occurred. Example time stamps include the actual time the warning 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 WARNING1-TIME-STAMP.

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

This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME.

Contains some sort of time stamp indicating when warning 6 occurred. Example time stamps include the actual time the warning 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 WARNING1-TIME-STAMP.

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

This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME.

Contains some sort of time stamp indicating when warning 7 occurred. Example time stamps include the actual time the warning 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 WARNING1-TIME-STAMP.

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

This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME.

Contains some sort of time stamp indicating when warning 8 occurred. Example time stamps include the actual time the warning 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 WARNING1-TIME-STAMP.

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

This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME.

Contains some sort of time stamp indicating when warning 9 occurred. Example time stamps include the actual time the warning 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 WARNING1-TIME-STAMP.

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

This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME.

Contains some sort of time stamp indicating when warning 10 occurred. Example time stamps include the actual time the warning 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 WARNING1-TIME-STAMP.

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

This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME.

Contains some sort of time stamp indicating when warning 11 occurred. Example time stamps include the actual time the warning 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 WARNING1-TIME-STAMP.

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

This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME.

Contains some sort of time stamp indicating when warning 12 occurred. Example time stamps include the actual time the warning 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 WARNING1-TIME-STAMP.

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

This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME.

Contains some sort of time stamp indicating when warning 13 occurred. Example time stamps include the actual time the warning 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 WARNING1-TIME-STAMP.

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

This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME.

Contains some sort of time stamp indicating when warning 14 occurred. Example time stamps include the actual time the warning 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 WARNING1-TIME-STAMP.

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

This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME.

Contains some sort of time stamp indicating when warning 15 occurred. Example time stamps include the actual time the warning 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 WARNING1-TIME-STAMP.

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

This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME.

Contains some sort of time stamp indicating when warning 16 occurred. Example time stamps include the actual time the warning 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 WARNING1-TIME-STAMP.

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

This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME.

Contains some sort of time stamp indicating when warning 17 occurred. Example time stamps include the actual time the warning 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 WARNING1-TIME-STAMP.

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

This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME.

Contains some sort of time stamp indicating when warning 18 occurred. Example time stamps include the actual time the warning 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 WARNING1-TIME-STAMP.

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

This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME.

Contains some sort of time stamp indicating when warning 19 occurred. Example time stamps include the actual time the warning 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 WARNING1-TIME-STAMP.

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

This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME.

Contains some sort of time stamp indicating when warning 20 occurred. Example time stamps include the actual time the warning 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 WARNING1-TIME-STAMP.

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

This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME.

Contains some sort of time stamp indicating when warning 21 occurred. Example time stamps include the actual time the warning 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 WARNING1-TIME-STAMP.

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

This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME.

Contains some sort of time stamp indicating when warning 22 occurred. Example time stamps include the actual time the warning 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 WARNING1-TIME-STAMP.

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

This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME.

Contains some sort of time stamp indicating when warning 23 occurred. Example time stamps include the actual time the warning 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 WARNING1-TIME-STAMP.

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

This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME.

Contains some sort of time stamp indicating when warning 24 occurred. Example time stamps include the actual time the warning 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 WARNING1-TIME-STAMP.

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

This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME.

Contains some sort of time stamp indicating when warning 25 occurred. Example time stamps include the actual time the warning 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 WARNING1-TIME-STAMP.

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

This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME.

Contains some sort of time stamp indicating when warning 26 occurred. Example time stamps include the actual time the warning 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 WARNING1-TIME-STAMP.

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

This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME.

Contains some sort of time stamp indicating when warning 27 occurred. Example time stamps include the actual time the warning 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 WARNING1-TIME-STAMP.

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

This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME.

Contains some sort of time stamp indicating when warning 28 occurred. Example time stamps include the actual time the warning 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 WARNING1-TIME-STAMP.

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

This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME.

Contains some sort of time stamp indicating when warning 29 occurred. Example time stamps include the actual time the warning 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 WARNING1-TIME-STAMP.

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

This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME.

Contains some sort of time stamp indicating when warning 30 occurred. Example time stamps include the actual time the warning 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 WARNING1-TIME-STAMP.

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

This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME.

Contains some sort of time stamp indicating when warning 31 occurred. Example time stamps include the actual time the warning 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 WARNING1-TIME-STAMP.

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

This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME.

Contains some sort of time stamp indicating when warning 32 occurred. Example time stamps include the actual time the warning 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 WARNING1-TIME-STAMP.

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

This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME.

Contains some sort of time stamp indicating when warning 33 occurred. Example time stamps include the actual time the warning 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 WARNING1-TIME-STAMP.

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

This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME.

Contains some sort of time stamp indicating when warning 34 occurred. Example time stamps include the actual time the warning 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 WARNING1-TIME-STAMP.

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

This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME.

Contains some sort of time stamp indicating when warning 35 occurred. Example time stamps include the actual time the warning 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 WARNING1-TIME-STAMP.

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

This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME.

Contains some sort of time stamp indicating when warning 36 occurred. Example time stamps include the actual time the warning 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 WARNING1-TIME-STAMP.

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

This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME.

Contains some sort of time stamp indicating when warning 37 occurred. Example time stamps include the actual time the warning 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 WARNING1-TIME-STAMP.

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

This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME.

Contains some sort of time stamp indicating when warning 38 occurred. Example time stamps include the actual time the warning 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 WARNING1-TIME-STAMP.

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

This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME.

Contains some sort of time stamp indicating when warning 39 occurred. Example time stamps include the actual time the warning 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 WARNING1-TIME-STAMP.

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

This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME.

Contains some sort of time stamp indicating when warning 40 occurred. Example time stamps include the actual time the warning 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 WARNING1-TIME-STAMP.

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

This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME.

Contains some sort of time stamp indicating when warning 41 occurred. Example time stamps include the actual time the warning 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 WARNING1-TIME-STAMP.

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

This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME.

Contains some sort of time stamp indicating when warning 42 occurred. Example time stamps include the actual time the warning 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 WARNING1-TIME-STAMP.

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

This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME.

Contains some sort of time stamp indicating when warning 43 occurred. Example time stamps include the actual time the warning 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 WARNING1-TIME-STAMP.

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

This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME.

Contains some sort of time stamp indicating when warning 44 occurred. Example time stamps include the actual time the warning 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 WARNING1-TIME-STAMP.

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

This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME.

Contains some sort of time stamp indicating when warning 45 occurred. Example time stamps include the actual time the warning 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 WARNING1-TIME-STAMP.

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

This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME.

Contains some sort of time stamp indicating when warning 46 occurred. Example time stamps include the actual time the warning 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 WARNING1-TIME-STAMP.

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

This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME.

Contains some sort of time stamp indicating when warning 47 occurred. Example time stamps include the actual time the warning 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 WARNING1-TIME-STAMP.

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

This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME.

Contains some sort of time stamp indicating when warning 48 occurred. Example time stamps include the actual time the warning 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 WARNING1-TIME-STAMP.

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

This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME.

Contains some sort of time stamp indicating when warning 49 occurred. Example time stamps include the actual time the warning 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 WARNING1-TIME-STAMP.

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

This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME.

Contains some sort of time stamp indicating when warning 50 occurred. Example time stamps include the actual time the warning 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 WARNING1-TIME-STAMP.

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

This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME.

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. Additional information: This device will always return eTrue.

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 a 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 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. Additional information: When the value of this object is changed, it takes effect immediately. It is recommended that the printer be offline and not in a job when this object is changed.

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.

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. The value will be updated at the end of every scan job.

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. The return value of this object will reset to the lower multiple of 10 at a power cycle. The value will be updated at the end of every scan job.

This item is incremented by 1 for each sheet that is scanned through the ADF in 1-sided scan mode. Additional information: The value will be updated at the end of every scan job.

This item is incremented by 2 for each sheet that is scanned through the ADF in 2-sided scan mode. Additional information: The value will be updated at the end of every scan job.

This relates to the number of pages scanned for copying. This item is incremented by 2 for each sheet scanned through the ADF in 2-sided scan mode, and it is incremented by 1 for flatbed scans. Scanning for testing and calibration purposes are NOT TO BE INCLUDED in this count. Additional information: The value will be updated at the end of every scan job.

This relates to the number of pages scanned for fax/send. This item is incremented by 2 for each sheet scanned through the ADF in 2-sided scan mode, and it is incremented by 1 for flatbed scans. Scanning for testing and calibration purposes are NOT TO BE INCLUDED in this count. Additional information: The value will be updated at the end of every scan job.

The number of scan-to-folder scan jobs. Additional information: The number of scan-to-folder scan jobs.

The number of fax scan jobs. Additional information: The number of fax scan jobs.

Returns or changes default copies. Default copies is the default values used by the PDL to control the number of copies of each page in the print job that are printed. The print job can override this value. The list of supported values should be documented in the device POS. Additional information: The supported values are 1 through 32000. Setting to an unsupported value causes the printer to substitute in a snap value and to return <noError> status. The snaps are as follows: <1 snaps to 1 >999 snaps to 32000

Instructs the PDL processing sub-system to finishing processing the current page of the current job. Form feed is also known as close page or eject page. If the PDL processing sub-system is in a FORM-FEED-NEEDED state, this causes the device to flush or finish processing the current page of the current job. If the device is not in the FORM-FEED-NEEDED state, an <genErr> will occur.

Returns or changes the value of the default vertical black resolution. The units are dots per inch. Additional information: In InkJet changing this OID also causes DEFAULT-HORIZONTAL-BLACK RESOLUTION to change. DEFAULT-HORIZONTAL-BLACK-RESOLUTION and DEFAULT-VERTICAL-BLACK-RESOLUTION must always be the same. The supported values are: Grizzly: 300, 600, 1200 Color Products: 600 Cayenne: 300, 600 Setting to an unsupported value causes the printer to substitute in a snap value and to return <noError> status. The snap values are as follow: Grizzly: 450 >= n < 900 snaps to 600 n >= 900 snaps to 1200 Color Products: n snaps to 600 Cayenne: n < 450 snaps to 300 n >=450 snaps to 600

Returns or changes the value of the default horizontal black resolution. The units are dots per inch. Additional information: In InkJet changing this object also causes DEFAULT-VERTICAL-BLACK RESOLUTION to change. DEFAULT-HORIZONTAL-BLACK-RESOLUTION and DEFAULT-VERTICAL-BLACK-RESOLUTION must always be the same. The supported values are: Grizzly: 300, 600, 1200 Color Products: 600 Cayenne: 300, 600 Setting to an unsupported value causes the printer to substitute in a snap value and to return <noError> status. The snap values are as follow: Grizzly: n < 450 snaps to 300 450 >= n < 900 snaps to 600 n >= 900 snaps to 1200 Color Products: n snaps to 600 Cayenne: n < 450 snaps to 300 n >=450 snaps to 600

Returns or changes the default page protection behavior. If eOff, the device does not reserve memory for holding the entire raster form of a processed page. If eOn, then memory is reserved. If eAuto, the device determines the amount of memory to reserve. Additional information: Setting to eOn causes MET to be more conservative, but it will not allocate memory to hold an entire rasterized page.

Returns or changes the default number of lines per page. The POS indicates the supported values. An unsupported value causes the printer to use the closest supported value, causing the printer to return the <noError>. Additional information: The supported values in InkJet are 5 to 128. Setting to an unsupported value causes the the printer to substitute in a snap value and to return <noError> status. The snap values are as follow: <5 snaps to 5 >128 snaps to 128

Returns or changes the default vertical motion index. The unit of measure for VMI is centipoints per line. The POS indicates the supported values. An unsupported value causes the printer to use the closest supported value, causing the printer to return <noError>.

This indicates the default media size. A write of an unsupported value causes an <ErrorInvalidOrUnsupported Value>. Complete list of supported media sizes along with their dimensions are listed in the Media Size Table near the end of this document. (for a full list of media size enums see the end of this file)

Returns or sets the media size that is used as the DEFAULT-MEDIA-SIZE when a cold reset occurs.

Returns or sets the media name that is used until the media name is changed by a print job command. Additional information: Returns or sets the media name that is used until the media name is changed by a print job command. This string must be one of the MEDIAn-NAME objects. This object is localized if the corresponding MEDIAn-NAME object is localized. The data for this object is stored in NVRAM.

Returns or changes the reprint (jam recovery) setting. If eOn, then the device will reprint pages jammed pages. If eOff, the device will not attempt to reprint jammed pages. If eAuto, a device dependent algorithm (which should be documented in the POS) will be used to determine if the page gets reprinted. This object controls all PDLs, unless a specific PDL supports its own reprint control mechanism. To date, only PostScript has a PDL reprint control mechanism.

Controls the number of levels used (per pixel) when printing grayscale or color images.

Indicates if the PDL processing sub-system has made marks on the current page and the source subsystem has been idle for a device specific amount of time. Additional information: InkJet will set this object to eTrue when it has made marks on the current page, the IO-TIMEOUT has expired while PCL was running in `backward-compatibility mode (which is caused by jobs consisting purely of PCL data with no prepended PJL commands), and no data is pending on another I/O. Once it is set to eTrue, more data on the same I/O will cause this object to be set to eFalse, until the above conditions are met again.

Total number of PCL pages printed by the device. Additional information: In InkJet the PCL page count is kept in NVRAM, and the NVRAM value is updated at least every 10 pages. NOTE: The value returned by this object will be incremented every page but if power is lost between NVRAM updates, up to 9 pages of the page count may be lost. The page count counter will be reset to zero after 16,777,215 (2^24-1) pages. The page count is incremented when a sheet of media is pulled from an input tray. A duplex printed sheet will cause this counter to be incremented by two.

Returns or changes the value of the default font source variable in NVRAM.

Returns or changes the value of the default font number variable in NVRAM. Writing an unsupported value causes the printer to generate an <badValue>. Additional information: Valid numbers or 0 - 255, but only font numbers that are included in the PCL FONT LIST are selectable.

Total number of PostScript pages printed by the device. Additional information: This object is only supported if the PostScript option is installed. In InkJet the count is kept in NVRAM, and the NVRAM value is updated at least every 10 sheets. NOTE: The value returned by this object will be incremented every sheet but if power is lost between NVRAM updates up to 9 sheets of the count may be lost. The counter will be reset to zero after 16,777,215 (2^24-1) pages.

Returns or changes the value of the print PostScript errors setting. If eOn, PostScript prints an error page showing the error encountered and the stack at the time of the error. Additional information: This object is only supported if the PostScript option is installed.

This object will be used to enable or disable the use of the Adobe Postscript Paper Handling Model in the printer firmware. By default it is enabled which means that PostScript will always defer the media selection to HP Paper Handling Model. Additional information: nothing beyond old description

Contains version of PDF that is supported on the device.

Total number of PDF pages printed by the device.

Used to tell whether the device supports PDF.

Returns or changes the value of the print PDF errors setting. If eOn, PDF prints an error page showing the error encountered and the stack at the time of the error.

This object tracks the page count for the pages sent to the print engine for fax jobs. In order to write this object <<hidden>> must be set correctly. Additional information: Returns the number of fax pages printed.

To check if PC Fax Send is enabled on the device. Also used by administrators to enable or disable PC Fax Send on the device

To check if a fax can be sent from a PC to the device. This checks if a Fax service is supported on the MFP and if the administrator has enabled PC Fax Send for the device. Additional return types may be supported later to indicate why PC Fax Send is not operational on the device

To check if the embedded Fax accessory or the Fax Service available on the device supports Notification for Faxes Sent

To check if Billing Code is enabled on the device for Faxes sent

The Minimum number of Billing Code digits that has to be specified for Faxes sent from the device. Range: 1 - 16

The actual Billing Code applicable for Faxes sent from the device

A Universal Resource Locator (URL) from which the Embedded Web Server can be configured. Any limitation on the size of this URL will be specified in the device POS.

Each collection bit represents a device or Embedded Web Server feature that can be enabled or disabled via this object.

Sets a string identifying the media name that is to be used in place of the currently requested media. The substitution will continue until another media is selected. If set to a named media that is not currently available the requested media is not overridden. Additional information: When a request is received to print on a size and type of media that is not currently available, this object contains the desired media name as set by the print job. This object should be set to a media name that is currently available in the printer. If a paper mount request is not pending, attempting to get or set this object will cause <noSuchName> to be returned. Setting this object to a string other than one of the MEDIAn-NAME objects (MEDIA-NAMES-AVAILABLE is applied) will cause a status of <badValue> to be returned.

Sets the media size that is to be used in place of the currently requested media size. Additional information: When a request is received to print on a size and type of media that is not currently available, this object contains the desired size as set by the print job. This object should be set to a media size that is currently available to the printer. If a paper mount request is not pending, attempting to get or set this object will cause <noSuchName> to be returned.

This PML object can be used to configure the low threshold for supplies. Additional information: This PML object can be used to configure the Low Threshold for Supplies.

This PML object is used to control Cartridge Out Override feature. Additional information: This object is used for the following purposes: 1. Set MarkEmptyOverride for a given cartridge. 2. Set/clear NonHPEnabled for a given cartridge. 3. Query internal variable SupplyUserConfirm for a given cartridge. 4. Query internal variable ConfirmedNonHP for a given cartridge.

When the value of the system variable is set to eDuplexBlankPagesAuto, it means to Smart Duplex in any of the specified conditions. This selection is logically equivalent to NO, do not duplex blank pages if not duplexing them obtains a performance enhancement. When the value of the system variable is set to eDuplexBlankPagesYes, it means to disable Smart Duplexing. Additional information: When the value of the system variable is set to eDuplexBlankPagesAuto, it means to Smart Duplex in any of the specified conditions. This selection is logically equivalent to NO, do not duplex blank pages if not duplexing them obtains a performance enhancement. When the value of the system variable is set to eDuplexBlankPagesYes, it means to disable Smart Duplexing. This PML object setting is only valid when the job has not requested a source tray. If the source tray has not been requested and setting is YES, then we disable smart duplexing. If the source tray has not been requested and setting is AUTO, then we do smart duplexing in some cases

This PML object will provide the additional image rotation that is applied to a printed job depending on the presence or absence of a finisher device or the value of the SVM_ALWAYS_MATCH_OUTPUT_ORIENTATION variable. Additional information: This PML object will provide the additional image rotation that is applied to a printed job depending on the presence or absence of a finisher device and/or the state of the IMAGE ROTATION menu element.

Total number of pages printed by the device. POS indicates if the total engine page count is kept in NVRAM, and the maximum supported value before the page count rolls over to zero. Additional information: nothing beyond old description

Total number of color pages printed by the device. Additional information: Total number of color pages printed by the device. The valid range of this object is 0 to 2^24-1. When the number of color pages printed exceeds the maximum color page count, the value will roll to zero. A duplexed sheet of media will cause the counter to be incremented by two.

Total number of sheets of media that have been duplex printed. A sheet is counted if it travels through the duplex page path, regardless of whether or not marks are made on the page. The POS will indicate if the value is kept in NVRAM. Additional information: Total number of sheets of media that have been duplex printed. A sheet is counted if it travels through the duplex page path, regardless of whether or not marks are made on the page. This value is kept in NVRAM however the NVRAM value is only updated every 10 sheets. NOTE: The value returned by this object will be incremented every sheet but if power is lost between NVRAM updates up to 9 sheets of the count may be lost. The counter will be reset to zero after 16,777,215 (2^24-1) pages.

Print engine revision string. Additional information: Print engine revision string. The symbol set for this string is Roman-8.

Provides the page count when the last DHALF calibration occurred. A -1 indicates that a calibration of this kind has not taken place yet. This object exists (and is meaningful) only in color printers. Additional information: Provides the page count when last DHALF calibration occurred. A -1 indicates that a calibration of this kind has not taken place yet. This object exists (and is meaningful) only in color printers.

Provides the time (in UTC - Universal Time Code format) when the last DHALF calibration occurred. This value could be zero if no calibration has taken place or if the printer lacked real-time. This object exists (and is meaningful) only in color printers. Additional information: Provides the time (in UTC - Universal Time Code format) when last DHALF calibration occurred. This value could be zero if no calibration has taken place and / or if the printer lacked real-time. This object exists (and is meaningful) only in color printers.

Provides the page count when last CPR calibration occurred. A -1 indicates that a calibration of this kind has not taken place yet. This object exists (and is meaningful) only in color printers. Additional information: Provides the page count when last CPR calibration occurred. A -1 indicates that a calibration of this kind has not taken place yet. This object exists (and is meaningful) only in color printers.

Provides the time (in UTC - Universal Time Code format) when the last CPR calibration occurred. This value could be zero if no calibration has taken place or if the printer lacked real-time. This object exists (and is meaningful) only in color printers. Additional information: Provides the time (in UTC - Universal Time Code format) when last CPR calibration occurred. This value could be zero if no calibration has taken place and / or if the printer lacked real-time. This object exists (and is meaningful) only in color printers.

Indicates if the device will automatically try to load media from the next input media tray in the auto-select sequence (defined by each device) when it cannot load media from the current tray. Locked trays will not be permitted in the auto-select sequence. This object has no meaning if there is only one unlocked input media tray. Additional information: Indicates if the device will automatically try to load media from the next input media tray in the auto-select sequence (defined by each device) when it cannot load media from the current tray. Locked trays will not be permitted in the auto-select sequence. This object has no meaning if there is only one unlocked input media tray.

Sets the printers custom paper dimension in the feed direction (direction parallel to the direction of paper feeding). The value for this object is specified in micrometers or tenthousandths of an inch, depending upon the value of CUSTOM-PAPER-DIM-UNIT. The valid range is engine-dependent and should be documented in the POS for each product. Additional information: Get/Set custom paper dimension (height). The return/set value is either in micrometers or 10,000ths of inches. A tray has to be in custom switch or without media size sensor to be able to set the custom dimension. If it is successfully setting the dimension value, the size of a tray is set to CUSTOM. If the current XFeed value is greater than the new Feed value, the firmware will silently set the XFeed to match the new Feed value.

Sets the printers custom paper dimension in the cross-feed direction (direction ninety degrees relative to the direction of paper feeding). The value for this object is specified in micrometers or tenthousandths of an inch, depending upon the value of CUSTOM-PAPER-DIM-UNIT. The valid range is engine-dependent and should be documented in the POS for each product. Additional information: Get/Set custom paper dimension (width). The return/set value is either in micrometers or 10,000ths of inches. A tray has to be in custom switch or without media size sensor to be able to set the custom dimension. If it is successfully setting the dimension value, the size of a tray is set to CUSTOM. If the new XFeed Dim is greater than the current Feed Dim, INVALID_OR_UNSUPPORTED_VALUE is returned.

The units of measure used to specify the width and height of the printers default custom paper size. The unit of measure of eTenThousandthsOfInches is 0.0001 inches. Additional information: The units of measure used to specify the width and height of the printers default custom paper size. The unit of measure of eTenThousandthsOfInches is 0.0001 inches.

Sets the printers default custom paper size dimension in the feed direction (direction parallel to the direction of paper feeding). The value for this object is specified in micrometers or tenthousandths of an inch, depending upon the value of DEFAULT-CUSTOM-PAPER-DIM-UNIT. The valid range is engine-dependent and should be documented in the POS for each product. Additional information: Sets the printers default custom paper size dimension in the feed direction (direction parallel to the direction of paper feeding). The value for this object is specified in micrometers or tenthousandths of an inch, depending upon the value of DEFAULT-CUSTOM-PAPER-DIM-UNIT. The valid range is engine-dependent and should be documented in the POS for each product.

Sets the printers default custom paper size dimension in the cross-feed direction (direction ninety degrees relative to the direction of paper feeding). The value for this object is specified in micrometers or tenthousandths of an inch, depending upon the value of DEFAULT-CUSTOM-PAPER-DIM-UNIT. The valid range is engine-dependent and should be documented in the POS for each product. Additional information: Sets the printers default custom paper size dimension in the cross-feed direction (direction ninety degrees relative to the direction of paper feeding). The value for this object is specified in micrometers or tenthousandths of an inch, depending upon the value of DEFAULT-CUSTOM-PAPER-DIM-UNIT. The valid range is engine-dependent and should be documented in the POS for each product.

The maximum physical media size in the feed direction of this input device expressed in units of measure specified by INPUT- TRAY-MIN-MAX-DIM-UNIT. A value of (-1) implies unlimited, a value of (-2) implies unknown. Additional information: The maximum physical media size in the feed direction of this input device expressed in units of measure specified by PrtInputDimUnit. A value of (-1) implies unlimited, a value of (-2) implies unknown. Refer to Printer Management Standards web page, http://bldlabs.boi.hp.com/BLDPrinterLab/Project/PrinterManagement, for more details in the original format of the Standard Printer MIB.

The maximum physical media size across the feed direction of a particular input device expressed in units of measure specified by INPUT-TRAY-MIN-MAX-DIM-UNIT. A value of (-1) implies unlimited, a value of (-2) implies unknown. Additional information: The maximum physical media size across the feed direction of this input device expressed in units of measure specified by PrtInputDimUnit. A value of (-1) implies unlimited, a value of (-2) implies unknown. Refer to Printer Management Standards web page, http://bldlabs.boi.hp.com/BLDPrinterLab/Project/PrinterManagement, f or more details in the original format of the Standard Printer MIB.

The minimum physical media size in the feed direction of a particular input device expressed in units of measure specified by PrtInputMinMaxDimUnit. A value of (-1) implies unlimited, a value of (-2) implies unknown. Additional information: The minimum physical media size in the feed direction of this input device expressed in units of measure specified by PrtInputDimUnit. A value of (-1) implies unlimited, a value of (-2) implies unknown. Refer to Printer Management Standards web page, http://bldlabs.boi.hp.com/BLDPrinterLab/Project/PrinterManagement, for more details in the original format of the Standard Printer MIB.

The minimum physical media size across the feed direction of a particular input device expressed in units of measure specified by PrtInputMinMaxDimUnit. A value of (-1) implies unlimited, a value of (-2) implies unknown. Additional information: The minimum physical media size across the feed direction of this input device expressed in units of measure specified by PrtInputDimUnit. A value of (-1) implies unlimited, a value of (-2) implies unknown. Refer to Printer Management Standards web page, http://bldlabs.boi.hp.com/BLDPrinterLab/Project/PrinterManagement, for more details in the original format of the Standard Printer MIB.

If this object is set to eDisplay, whenever a paper tray is opened, refilled, and closed in a printer, the end user is prompted with a message To change size or type press check on the control panel. If this object is set to eDoNotDisplay, then the end user will not be prompted with this message whenever a paper tray is opened, refilled, and closed in a printer. Additional information: Whenever a paper tray is opened and closed, the user is provided with two options Display and Do Not Display, through the menu item Size/Type Prompt.On selecting Display he chooses to get prompted with the message to change the size or type of paper. Whereas he is not prompted with this message in case he chooses Do Not Display.

Returns the media size that is currently configuredconfigured in tray #1. This object can be set to indicate the media size currently loaded, if the printer supports input trays that can not sense the media size. Complete list of supported media sizes along with their dimensions are listed in the Media Size Table near the end of this document. Additional information: Returns the media size that is currently configuredconfigured in tray #1. This object can be set to indicate the media size currently loaded, if the printer supports input trays that can not sense the media size. Complete list of supported media sizes along with their dimensions are listed in the Media Size Table near the end of this document.

Provides the number of the Paper Handling Device that contains this input tray. Additional information: Provides the number of the Paper Handling Device that contains this input tray.

Returns the media size that is currently configured in tray #2. Complete list of supported media sizes along with their dimensions are listed in the Media Size Table near the end of this document. Additional information: Returns the media size that is currently configured in tray #2.

Provides the number of the Paper Handling Device that contains this input tray. Additional information: Provides the number of the Paper Handling Device that contains this input tray.

Returns the media size that is currently configured in tray #3. Complete list of supported media sizes along with their dimensions are listed in the Media Size Table near the end of this document. Additional information: Returns the media size that is currently configured in tray #3.

Provides the number of the Paper Handling Device that contains this input tray. Additional information: Provides the number of the Paper Handling Device that contains this input tray.

Returns the media size that is currently configured in tray #5. Complete list of supported media sizes along with their dimensions are listed in the Media Size Table near the end of this document. Additional information: Returns the media size that is currently configured in tray #5.

Provides the number of the Paper Handling Device that contains this input tray. Additional information: Provides the number of the Paper Handling Device that contains this input tray.

Returns the media size that is currently configured in tray #5. Complete list of supported media sizes along with their dimensions are listed in the Media Size Table near the end of this document. Additional information: Returns the media size that is currently configured in tray #5.

Provides the number of the Paper Handling Device that contains this input tray. Additional information: Provides the number of the Paper Handling Device that contains this input tray.

Returns or sets the bin that will be used for additional sheets of media when the current bin is full and printing is allowed to continue. Additional information: Returns or sets the bin that will be used for additional sheets of media when the current bin is full and printing is allowed to continue. The data for this object is stored in NVRAM.

Returns or sets the device behavior when this output bin condition causes printing to stop. cCancelJob - The device cancels the job. cOutbinFullOverride - The device sends subsequent media to the overflow bin. cOutbinAttentionOverride - The device ignores the attention condition and continues printing. cBinderAttentionOverride - The device ignores the binder attention condition and continues printing. Additional information: Returns or sets the device behavior when this output bin condition causes printing to stop. cCancelJob - The device cancels the job, regardless of other bit settings. cOutbinFullOverride - The device sends subsequent media to the overflow bin. If this bin is the overflow bin, this bit is ignored. cOutbinAttentionOverride - The device ignores the attention condition and continues printing. cBinderAttentionOverride - The device ignores the binder attention condition and continues printing. This object describes the action that is performed when the JOB-OUTPUT-AUTO-CONTINUE-TIMEOUT expires. If no bits are set, no override action is taken (the printer will continue to wait).

The maximum number of sheets of 20 pound paper that can be bound by the binding device that serves this output bin. If a job exceeds this number and the job has requested binding, cBindingError will be set in NOT- READY-DESTINATION-PRINT-ENGINE. Additional information: The maximum number of sheets of 20 pound paper that can be bound by the binding device that serves this output bin. If a job exceeds this number and the job has requested binding, cBindingError will be set in NOT- READY-DESTINATION-PRINT-ENGINE.

Provides the number of the Paper Handling Device that contains this output bin. Additional information: Provides the number of the Paper Handling Device that contains this output bin.

A device specific description of the last error encountered for output bin 1. Each POS should document the meaning of all supported error information. Additional information: This is a description of the current error state of a finishing device. (ie stapler). If the bin does not support any finishing capabilities then the object will return <badValue>. The possible return values are as follows: Byte1, Byte2, and Byte3 should be 0x00. as they are reserved for future use. Byte4 is a bit field that can be interpreted as follows: bit 0 - unused bit 1 - eBinderOut Out of staples bit 2 - eBinderLimit Too many pages to finish bit 3 - eBinderJam Staple jammed in stapler bit 4 - eBinderAlign Pages arent aligned correctly to finish. bit 5 - unused bit 6 - unused bit 7 - unused NOTE: Because HP is marketing a device with a max of 16 bins the OUTBIN-MAXIMUM-BINDING objects are 3-18 but the external device specification requires support of up to 315 output bins. Therefore if these bins exist above 16, then the coresponding objects will also exist OUTBIN19-MAXIMUM-BINDING ... OUTBIN317-MAXIMUM-BINDING

Returns or sets the device behavior when this output bin condition causes printing to stop. cCancelJob - The device cancels the job. cOutbinFullOverride - The device sends subsequent media to the overflow bin. cOutbinAttentionOverride - The device ignores the attention condition and continues printing. cBinderAttentionOverride - The device ignores the binder attention condition and continues printing. Additional information: Returns or sets the device behavior when this output bin condition causes printing to stop. cCancelJob - The device cancels the job, regardless of other bit settings. cOutbinFullOverride - The device sends subsequent media to the overflow bin. If this bin is the overflow bin, this bit is ignored. cOutbinAttentionOverride - The device ignores the attention condition and continues printing. cBinderAttentionOverride - The device ignores the binder attention condition and continues printing. This object describes the action that is performed when the JOB-OUTPUT-AUTO-CONTINUE-TIMEOUT expires. If no bits are set, no override action is taken (the printer will continue to wait).

The maximum number of sheets of 20 pound paper that can be bound by the binding device that serves this output bin. If a job exceeds this number and the job has requested binding, cBindingError will be set in NOT- READY-DESTINATION-PRINT-ENGINE. Additional information: The maximum number of sheets of 20 pound paper that can be bound by the binding device that serves this output bin. If a job exceeds this number and the job has requested binding, cBindingError will be set in NOT- READY-DESTINATION-PRINT-ENGINE.

Provides the number of the Paper Handling Device that contains this output bin. Additional information: Provides the number of the Paper Handling Device that contains this output bin.

A device specific description of the last error encountered for output bin 2. Each POS should document the meaning of all supported error information. Additional information: This is a description of the current error state of a finishing device. (ie stapler). If the bin does not support any finishing capabilities then the object will return <badValue>. The possible return values are as follows: Byte1, Byte2, and Byte3 should be 0x00. as they are reserved for future use. Byte4 is a bit field that can be interpreted as follows: bit 0 - unused bit 1 - eBinderOut Out of staples bit 2 - eBinderLimit Too many pages to finish bit 3 - eBinderJam Staple jammed in stapler bit 4 - eBinderAlign Pages arent aligned correctly to finish. bit 5 - unused bit 6 - unused bit 7 - unused NOTE: Because HP is marketing a device with a max of 16 bins the OUTBIN-MAXIMUM-BINDING objects are 3-18 but the external device specification requires support of up to 315 output bins. Therefore if these bins exist above 16, then the coresponding objects will also exist OUTBIN19-MAXIMUM-BINDING ... OUTBIN317-MAXIMUM-BINDING

Returns or sets the device behavior when this output bin condition causes printing to stop. cCancelJob - The device cancels the job. cOutbinFullOverride - The device sends subsequent media to the overflow bin. cOutbinAttentionOverride - The device ignores the attention condition and continues printing. cBinderAttentionOverride - The device ignores the binder attention condition and continues printing. Additional information: Returns or sets the device behavior when this output bin condition causes printing to stop. cCancelJob - The device cancels the job, regardless of other bit settings. cOutbinFullOverride - The device sends subsequent media to the overflow bin. If this bin is the overflow bin, this bit is ignored. cOutbinAttentionOverride - The device ignores the attention condition and continues printing. cBinderAttentionOverride - The device ignores the binder attention condition and continues printing. This object describes the action that is performed when the JOB-OUTPUT-AUTO-CONTINUE-TIMEOUT expires. If no bits are set, no override action is taken (the printer will continue to wait).

The maximum number of sheets of 20 pound paper that can be bound by the binding device that serves this output bin. If a job exceeds this number and the job has requested binding, cBindingError will be set in NOT- READY-DESTINATION-PRINT-ENGINE. Additional information: The maximum number of sheets of 20 pound paper that can be bound by the binding device that serves this output bin. If a job exceeds this number and the job has requested binding, cBindingError will be set in NOT- READY-DESTINATION-PRINT-ENGINE.

Provides the number of the Paper Handling Device that contains this output bin. Additional information: Provides the number of the Paper Handling Device that contains this output bin.

A device specific description of the last error encountered for output bin 3. Each POS should document the meaning of all supported error information. Additional information: This is a description of the current error state of a finishing device. (ie stapler). If the bin does not support any finishing capabilities then the object will return <badValue>. The possible return values are as follows: Byte1, Byte2, and Byte3 should be 0x00. as they are reserved for future use. Byte4 is a bit field that can be interpreted as follows: bit 0 - unused bit 1 - eBinderOut Out of staples bit 2 - eBinderLimit Too many pages to finish bit 3 - eBinderJam Staple jammed in stapler bit 4 - eBinderAlign Pages arent aligned correctly to finish. bit 5 - unused bit 6 - unused bit 7 - unused NOTE: Because HP is marketing a device with a max of 16 bins the OUTBIN-MAXIMUM-BINDING objects are 3-18 but the external device specification requires support of up to 315 output bins. Therefore if these bins exist above 16, then the coresponding objects will also exist OUTBIN19-MAXIMUM-BINDING ... OUTBIN317-MAXIMUM-BINDING

Returns or sets the device behavior when this output bin condition causes printing to stop. cCancelJob - The device cancels the job. cOutbinFullOverride - The device sends subsequent media to the overflow bin. cOutbinAttentionOverride - The device ignores the attention condition and continues printing. cBinderAttentionOverride - The device ignores the binder attention condition and continues printing. Additional information: Returns or sets the device behavior when this output bin condition causes printing to stop. cCancelJob - The device cancels the job, regardless of other bit settings. cOutbinFullOverride - The device sends subsequent media to the overflow bin. If this bin is the overflow bin, this bit is ignored. cOutbinAttentionOverride - The device ignores the attention condition and continues printing. cBinderAttentionOverride - The device ignores the binder attention condition and continues printing. This object describes the action that is performed when the JOB-OUTPUT-AUTO-CONTINUE-TIMEOUT expires. If no bits are set, no override action is taken (the printer will continue to wait).

The maximum number of sheets of 20 pound paper that can be bound by the binding device that serves this output bin. If a job exceeds this number and the job has requested binding, cBindingError will be set in NOT- READY-DESTINATION-PRINT-ENGINE. Additional information: The maximum number of sheets of 20 pound paper that can be bound by the binding device that serves this output bin. If a job exceeds this number and the job has requested binding, cBindingError will be set in NOT- READY-DESTINATION-PRINT-ENGINE.

Provides the number of the Paper Handling Device that contains this output bin. Additional information: Provides the number of the Paper Handling Device that contains this output bin.

A device specific description of the last error encountered for output bin 4. Each POS should document the meaning of all supported error information. Additional information: This is a description of the current error state of a finishing device. (ie stapler). If the bin does not support any finishing capabilities then the object will return <badValue>. The possible return values are as follows: Byte1, Byte2, and Byte3 should be 0x00. as they are reserved for future use. Byte4 is a bit field that can be interpreted as follows: bit 0 - unused bit 1 - eBinderOut Out of staples bit 2 - eBinderLimit Too many pages to finish bit 3 - eBinderJam Staple jammed in stapler bit 4 - eBinderAlign Pages arent aligned correctly to finish. bit 5 - unused bit 6 - unused bit 7 - unused NOTE: Because HP is marketing a device with a max of 16 bins the OUTBIN-MAXIMUM-BINDING objects are 3-18 but the external device specification requires support of up to 315 output bins. Therefore if these bins exist above 16, then the coresponding objects will also exist OUTBIN19-MAXIMUM-BINDING ... OUTBIN317-MAXIMUM-BINDING

Returns or sets the device behavior when this output bin condition causes printing to stop. cCancelJob - The device cancels the job. cOutbinFullOverride - The device sends subsequent media to the overflow bin. cOutbinAttentionOverride - The device ignores the attention condition and continues printing. cBinderAttentionOverride - The device ignores the binder attention condition and continues printing. Additional information: Returns or sets the device behavior when this output bin condition causes printing to stop. cCancelJob - The device cancels the job, regardless of other bit settings. cOutbinFullOverride - The device sends subsequent media to the overflow bin. If this bin is the overflow bin, this bit is ignored. cOutbinAttentionOverride - The device ignores the attention condition and continues printing. cBinderAttentionOverride - The device ignores the binder attention condition and continues printing. This object describes the action that is performed when the JOB-OUTPUT-AUTO-CONTINUE-TIMEOUT expires. If no bits are set, no override action is taken (the printer will continue to wait).

The maximum number of sheets of 20 pound paper that can be bound by the binding device that serves this output bin. If a job exceeds this number and the job has requested binding, cBindingError will be set in NOT- READY-DESTINATION-PRINT-ENGINE. Additional information: The maximum number of sheets of 20 pound paper that can be bound by the binding device that serves this output bin. If a job exceeds this number and the job has requested binding, cBindingError will be set in NOT- READY-DESTINATION-PRINT-ENGINE.

Provides the number of the Paper Handling Device that contains this output bin. Additional information: Provides the number of the Paper Handling Device that contains this output bin.

A device specific description of the last error encountered for output bin 5. Each POS should document the meaning of all supported error information. Additional information: This is a description of the current error state of a finishing device. (ie stapler). If the bin does not support any finishing capabilities then the object will return <badValue>. The possible return values are as follows: Byte1, Byte2, and Byte3 should be 0x00. as they are reserved for future use. Byte4 is a bit field that can be interpreted as follows: bit 0 - unused bit 1 - eBinderOut Out of staples bit 2 - eBinderLimit Too many pages to finish bit 3 - eBinderJam Staple jammed in stapler bit 4 - eBinderAlign Pages arent aligned correctly to finish. bit 5 - unused bit 6 - unused bit 7 - unused NOTE: Because HP is marketing a device with a max of 16 bins the OUTBIN-MAXIMUM-BINDING objects are 3-18 but the external device specification requires support of up to 315 output bins. Therefore if these bins exist above 16, then the coresponding objects will also exist OUTBIN19-MAXIMUM-BINDING ... OUTBIN317-MAXIMUM-BINDING

Returns or sets the print quality level. This value is used when print jobs do not indicate the desired print quality. Additional information: nothing beyond old description

If this object is set to eEnabled, the paper mount message that is normally posted(To use another tray....) is turned off thereby disallowing the user to specify another tray from which paper can be taken for printing. However, on setting this object to eDisabled the paper mount message is posted allowing the user to specify another tray for paper feed. Additional information: The feature provides a menu item under TRAY BEHAVIOUR, i.e USE ANOTHER TRAY which has two options ENABLED and DISABLED. Whenever the menu item is set to ENABLED, it provides the user with the ability to select another tray from which paper could be provided for the job. However on selecting DISABLED forces the user to provide paper through the same tray, after the paper mount message is posted, in either cases.

This object is used to send device-specific data to the paper handling device. The meaning of the device-specific command is dependent on the paper handling device and must be specified in the POS. If the paper handling device does not accept the command, then an <badValue> will be returned. If the device accepts the command, it may still be processing the command after the response has been returned. Depending on the device, the application may need to query PHDx-DEVICE-MEMORY to see when the command has completed. Additional information: This object is used to send device-specific data to the paper handling device. The meaning of the device- specific command is dependent on the paper handling device and must be specified in the POS. If the paper handling device does not accept the command, then an <badValue> will be returned. If the device accepts the command, it may still be processing the command after the response has been returned. Depending on the device, the application may need to query PHDx-DEVICE-MEMORY to see when the command has completed.

The value of this object controls which of the MEDIAx-NAME objects are supported. If a bit is set to zero, then attempting to get or set the corresponding MEDIAx-NAME objects will return <noSuchName>. Additional information: Setting a bit to one will cause the corresponding MEDIAn- objects to be available (attempting to access an unavailable object will return <noSuchName>). MEDIA1- objects are always present, as this is the default media. If this object is set to a value that does not include cMediaName2Available, that bit will be set and a status of <noError> will be returned.

Returns or sets the number of 300 dpi dots by which the image is shifted. Shift is relative to the leading edge of the medium as the medium flows through the marking engine with the side to be imaged facing the observer. The leading edge is the North edge and the other edges are defined by the normal compass layout of directions with the compass facing the observer. The adjustment is for all pages printed. A positive value moves the image away from the leading edge of the medium. A negative value moves the image closer to the leading edge of the medium. The value 0 will return the image to its factory default position. Additional information: Returns or sets the number of 300 dpi dots by which the image is shifted. Shift is relative to the leading edge of the medium as the medium flows through the marking engine with the side to be imaged facing the observer. The leading edge is the North edge and the other edges are defined by the normal compass layout of directions with the compass facing the ob server. The adjustment is for all pages printed. A positive value moves the image away from the leading edge of the medium. A negative value moves the image closer to the leading edge of the medium. The value 0 will return the image to its factory default position. The value of this object is stored in NVRAM.

Media 1 name. Additional information: The order of these objects is determined by the order of SysOD_MediaTypeEnum. The symbol set for this string is Roman-8.

Length restricted version of the media name 1. The length restriction is required to allow the media name to be displayed on the devices control panel. The device POS must state the maximum number of characters allowed. If the device also has a limitation on what characters in a character set can be used (e.g. only uppercase characters allowed), the POS should also state character restrictions. Additional information: The order of these objects is determined by the order of SysOD_MediaTypeEnum. Length restricted version of the media name 1. The length restriction is required to allow the media name to be displayed on the devices control panel. The maximum supported string length is 9 characters. If the user entered string is too long, the device will store the first 9 characters and will return the <noError> status. The characters must be in the range 20H to 7FH except 5C cannot be used. The default symbol set is Roman-8 for English; additional legal symbol sets are ISOLatin5, ISOLatin2 and Windows31J. Setting this object with characters outside of the range or of an illegal symbol set will cause an error status of <badValue> to be returned. This string is localized according to prtConsoleLocalization. If this object represents a standard type, and the user attempts to set the object, OK Nearest Legal Value Substituted will be returned, and the standard value is retained. If this object represents a user defined type, and the user attempts to set the object, then the set will be successfull.

Number of sheets of media 1 that have been printed. The device POS should state whether this value is lost across a power cycle or kept in NVRAM. Additional information: Number of sheets of media 1 that have been printed. This page count is saved in NVRAM after every 10 pages. The maximum value is 4,294,967,295 which will never be reached in normal operation. The page count is incremented when a sheet of media is pulled from an input tray. A duplex printed sheet will cause this counter to be incremented by one.

Media 2 name. Additional information: See MEDIA1-NAME.

Length restricted version of the media name 2. See MEDIA1-SHORT-NAME for details. Additional information: See MEDIA1-SHORT-NAME.

Number of sheets of media 2 that have been printed. See MEDIA1-PAGE-COUNT for details. Additional information: See MEDIA1-PAGE-COUNT.

Media 3 name. Additional information: See MEDIA1-NAME.

Length restricted version of the media name 3. See MEDIA1-SHORT-NAME for details. Additional information: See MEDIA1-SHORT-NAME.

Number of sheets of media 3 that have been printed. See MEDIA1-PAGE-COUNT for details. Additional information: See MEDIA1-PAGE-COUNT.

Media 4 name. Additional information: See MEDIA1-NAME.

Length restricted version of the media name 4. See MEDIA1-SHORT-NAME for details. Additional information: See MEDIA1-SHORT-NAME.

Number of sheets of media 4 that have been printed. See MEDIA1-PAGE-COUNT for details. Additional information: See MEDIA1-PAGE-COUNT.

Media 5 name. Additional information: See MEDIA1-NAME.

Length restricted version of the media name 5. See MEDIA1-SHORT-NAME for details. Additional information: See MEDIA1-SHORT-NAME.

Number of sheets of media 5 that have been printed. See MEDIA1-PAGE-COUNT for details. Additional information: See MEDIA1-PAGE-COUNT.

Media 6 name. Additional information: See MEDIA1-NAME.

Length restricted version of the media name 6. See MEDIA1-SHORT-NAME for details. Additional information: See MEDIA1-SHORT-NAME.

Number of sheets of media 6 that have been printed. See MEDIA1-PAGE-COUNT for details. Additional information: See MEDIA1-PAGE-COUNT.

Media 7 name. Additional information: See MEDIA1-NAME.

Length restricted version of the media name 7. See MEDIA1-SHORT-NAME for details. Additional information: See MEDIA1-SHORT-NAME.

Number of sheets of media 7 that have been printed. See MEDIA1-PAGE-COUNT for details. Additional information: See MEDIA1-PAGE-COUNT.

Media 8 name. Additional information: See MEDIA1-NAME.

Length restricted version of the media name 8. See MEDIA1-SHORT-NAME for details. Additional information: See MEDIA1-SHORT-NAME.

Number of sheets of media 8 that have been printed. See MEDIA1-PAGE-COUNT for details. Additional information: See MEDIA1-PAGE-COUNT.