
LZ85194
32
IrDA Control Peripheral Engine User
’
s Guide
Reducing Interference on Legacy CE Remote Control Systems
(DC BIAS Scheme)
DC BIAS scheme is one of the effective schemes described in IrDA-Control standard spec-
ifications to reduce the interference on the legacy CE remote control systems. PE supports
this DC BIAS scheme which can be enabled by a simple command on SS-Wire interface.
The proper output signals can be obtained from PE to the DC BIAS circuit, by μP to issue
Set_DcBias Command to PE.
In order to enable the DC BIAS mode, Set_DcBias command needs to be issued after issu-
ing Set_Peripheral_Info command for PFID and Peripheral Info setting, after the reset
(either hardware or software) of PE.
Tips for Peripheral Implementation
Codes (Report Packet) For Sending Packets To The Host
Please follow USB HID specifications report format for the HID peripherals, if the report
format is defined in USB HID specifications*.
NOTE:
*Universal Serial Bus (USB) Device Class Definition for Human Interface devices (HID) Firmware
Specification Version 1.0, Final.
Key-Repeat Operation for Keyboards
The μP should send the
‘
make code
’
of the pressed key by Send_Data_withAck (or
Send_Data) to PE, once every 180 ms - 200 ms while the key is pressed.
The Randomness of PFID
More than two peripherals with the same PFIDs cannot communicate with the Host within
the same area, at the same time. Thus the value of PFID has importance to differentiate
the peripheral devices, one from the others. If DIP SW for PFID is not provided, reasonable
consideration should be made on this issue. One may want to utilize unsure parameters
to generate the random numbers.
After reset, PFID must be set by following the instruction given with the Message. For
example, in case of a keyboard, if Set_Peripheral_Info(0) is to be executed by the very first
stroke, one may possibly use time gap between the power on and the very first key stroke,
or time gap between key stroke and release, or even both. The generated PFIDs of the
peripherals is recommended to be evaluated with the sniffer (packet analyzer).
Enum Button Functionality
The button(s) to which the Enumeration function is assigned must NOT be repeated, but
should be designed to issue Manual_Enum_withBinding (or Manual_Enum) command
once per one key-stroke. If Manual_Enum_withBinding (or Manual_Enum) command is
sent several times per single key-stroke, the
‘
Scan Mechanism
’
will not perform properly.
If this mechanism is not implemented with
‘
Enum
’
button (or equivalent method), the
peripheral device will only be able to communicate with other Host devices by re-insertion
of the battery, or other equivalent methods.