User's Manual

Viewsonic Tweety RF Remote Rev 2.9A November 05, 2001
Universal Electronics Inc. Confidential
Page 23 of 63
Timing Events versus Data Packet transmission for various operational situations:
3.4.2 Time Event / Data Packet Transmission Diagram
Te_2
--------------------------- // ------------------------ // ------------------ 60 seconds ---------------- // ------------------------ // -----------------
Te_1
- ~ 70ms -- // 
~10ms~
Te_2a Te_3
~10ms~
Te_3a, Te_1a
Make Make Break Break
Te_3b, Te_6a
Te_3c, Te_6a
Te_1a
Make Make Make
StkKy
Sleep
Te_4
- // ---- 70ms --- // ----- - // ---- 70ms -- // ----
Notes:
Te_4a
Te_4b
Te_5
Te_6
Time values are approximate and NOT to scale
Te_5a Te_6a
Refer to APPENDIX for notation descriptions used in this Diagram and Table below.
Time Event / Data Packet Transmission
Time Event
Key Press & Time Event Data Packet Transmission & Time Event Remark
Te_1 <K1> is pressed and detected
First Make-Code-Data-Packet (<K1> Scan Code) will be sent. It follows by
about 10 ms delay.
Te_2 <K1> key is still being
depressed
Second Make-Code-Data-Packet (of same <K1> Scan Code as above) will
be sent.
Case where a key press, <K1> say, is
detected. Make-Code-Data-Packets are
sent with 10 ms delay between the data
packets.
Te_4
Te_4a
Te_4b
70 ms after Te_2, <K1> is still
being held from the time event
Te_1 when the <K1> depress
is first detected..
Another 70 ms elapsed after
Te_4 and <K1> is still being
held down
<K1> is still being held down
70 ms after Te_4a.
Make code data packets of K1 are now transmitted.
Another Make code Data Packets are sent
Another Data Packet of Keep-Alive code is sent. See remark column.
This is the case where:
From the time event Te_1 and for
every 70 ms elapsed time interval, and
60 seconds stuck-key timeout has not
been reached, Make code Data-Packet
of the same key will be sent out as long
as key <K!> is still being held down.