HP Retail Peripheral Agent Technical User Guide

1) If an application has exclusive use to the peripheral OPOS driver before the

Retail Peripheral Agent has a chance to extract information, the properties

for the peripheral will not be able to be retrieved. The OPOS and service

driver for the peripheral needs to be released and a reboot, reinsertion of

the device, or refresh command needs to occur for the information to be

updated. This is expected behavior per the current implementation of the

UPOS specification.

2) If a peripheral has been configured by the HP Retail Peripheral Agent, the

setting will still appear in the configuration list if the user removes the device

at a later point in time. The removed peripheral’s LND will remain in the

LND field even after clicking on the "Refresh" button in the Retail Peripheral

Threshold Alerts Setting. Once device has been configured, the HP Retail

Peripheral Agent will be set in manual mode. User will need to delete the

peripheral’s LND in the LND field to update the configuration list.

3) Each peripheral can be programmed/set to operate in different

communication modes (single or bi-directional). If a device supports the

UPOS manageability model but operates in the communication mode that

does not support the UPOS manageability mode (i.e. Keyboard mode

where there is no OPOS driver support), the HP Retail Peripheral Agent will

not be able to generate manageability data. If the device is in bi-

directional mode and does not have UPOS driver stack support, the HP

Retail Peripheral Agent will not be able to generate manageability data. To

meet the prerequisite, the device must be in a mode of communication that

can support the UPOS driver stack.

For example, certain USB scanner models can be set to the following

communication mode of operation:

 Com mode (virtual USB to com protocol): this operates in bi-directional

mode where it requires the UPOS driver stack to communicate or a

direct connection (ie using HyperTerminal) to the serial protocol to take

exclusive use of the device. Note: not all UPOS driver stack supports

this mode; refer to device supplier for support information.

 HID mode: this operates in bi-directional mode where it requires the

UPOS driver stack to communicate. Note: not all UPOS driver stack

supports this mode; refer to device supplier for support information.

 Keyboard mode: this operates in a single direction mode of

communication where software can take input from the device FW but

unable to write to the device FW. Due to the single direction

communicating mode, most peripherals in this mode of communication