| all | frequencies |
|
exhibits | applications |
|---|---|---|---|---|
| manual |
| app s | submitted / available | |||||||
|---|---|---|---|---|---|---|---|---|
| 1 |
|
users manual | Users Manual | 274.58 KiB | ||||
| 1 | Block Diagram | |||||||
| 1 | External Photos | |||||||
| 1 | Internal Photos | |||||||
| 1 | ID Label/Location Info | |||||||
| 1 | Operational Description | |||||||
| 1 | Cover Letter(s) | |||||||
| 1 | Test Report | |||||||
| 1 | Test Setup Photos |
| 1 | users manual | Users Manual | 274.58 KiB |
Revision 0.1 NMB TECHNOLOGIES 2/16/2001 9730 INDEPENDENCE AVE CHATSWORTH, CA 91311 U.S.A TEL: (818) 341-3355 FAX: (818) 772-0866 Requirement Specification NMB Wireless Keyboard with POINTING Devices RF-Receiver and the HOST(Viewsonic) For the and Rev. 0.4 1 Revision 0.1 Revision History DATE 02/16/01 04/22/01 07/09/01 11/27/01 Revision 0.1 0.2 0.3 0.4 Changes and Additions First Draft 2/16/2001 By Ely Palarca Ely Palarca Ely Palarca Ely Palarca 2 Revision 0.1 2/16/2001 CONTENT INTRODUCTION .....................................................................................................................................................................................................4 OVERVIEW ............................................................................................................................................................................................................4 UART INTERFACE ...............................................................................................................................................................................................4 POWER-ON-RESET..............................................................................................................................................................................................5 SLEEP MODE........................................................................................................................................................................................................5 WAKE UP MODE...................................................................................................................................................................................................5 DATA PACKET.......................................................................................................................................................................................................6 KEY TYPES ...........................................................................................................................................................................................................7 STUCK KEY ...........................................................................................................................................................................................................7 KEYBOARD OR REMOTE SLEEP MODE...............................................................................................................................................................7 KEEP ALIVE ..........................................................................................................................................................................................................7 RESYNC BUTTON .................................................................................................................................................................................................7 RF POWER MANAGEMENT..................................................................................................................................................................................7 TRANSMITTER DATA INPUT LEVEL......................................................................................................................................................................7 DATA CODING.......................................................................................................................................................................................................7 HARDWARE INTERFACE.......................................................................................................................................................................................8 GENERAL SPECIFICATION....................................................................................................................................................................................9 FREQUENCY PLAN .............................................................................................................................................................................................10 FREQUENCY CONTROL......................................................................................................................................................................................10 FUNCTIONAL BLOCK DIAGRAM..........................................................................................................................................................................11 UART INTERFACE .............................................................................................................................................................................................11 POWER DOWN....................................................................................................................................................................................................12 TIMING PROTOCOL.............................................................................................................................................................................................12 SET/RESET KEYBOARD STATUS INDICATORS .................................................................................................................................................12 REPEAT KEYS.....................................................................................................................................................................................................12 DEVICE ID AND DEVICE NUMBER .....................................................................................................................................................................12 CHANNEL SYNCHRONIZATION ...........................................................................................................................................................................13 COMMANDS SUMMARY ......................................................................................................................................................................................14 NMB KEYBOARD DATA PACKET.......................................................................................................................................................................16 REMOTE UEI KEY DATA PACKET .....................................................................................................................................................................16 NMB POINTING DEVICE DATA PACKET ...........................................................................................................................................................17 UEI POINTING DEVICE DATA PACKET..............................................................................................................................................................17 STUCK KEY DATA PACKET ................................................................................................................................................................................17 SLEEP DATA PACKET.........................................................................................................................................................................................18 KEEP ALIVE DATA PACKET................................................................................................................................................................................18 RF-RECEIVER CONNECTOR ..............................................................................................................................................................................18 RF-RECEIVER MECHANICAL..............................................................................................................................................................................18 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16. 18. 19. 20. 21. 22. 23. 24. 25. 26. 27. 28. 29. 30. 31. 32. 33. 34. 35. 36. 37. 38. FIGURES TABLES FIGURE 1: RF- RECEIVER AND IP-BOARD INTERFACE (UART).................................................................................................................................4 FIGURE 2: UART PROTOCOL .......................................................................................................................................................................................4 FIGURE 3 .........................................................................................................................................................................................................................7 FIGURE 4: RF- RECEIVER AND IP-BOARD INTERFACE (UART)...............................................................................................................................11 FIGURE 5: UART PROTOCOL .....................................................................................................................................................................................12 TABLE 1: DATA FRAME.................................................................................................................................................................................................4 TABLE 2: RF_TRANSMITTER / RF_RECEIVER HARDWARE INTERFACE ...................................................................................................................8 TABLE 3 ...........................................................................................................................................................................................................................8 TABLE 4: TRANSMITTER FREQUENCY PLAN .............................................................................................................................................................10 TABLE 5: RECEIVER FREQUENCY PLAN....................................................................................................................................................................10 TABLE 6: FREQUENCY CONTROL FOR TRANSMITTER..............................................................................................................................................11 TABLE 7: FREQUENCY CONTROL FOR RECEIVER ....................................................................................................................................................11 TABLE 8: DATA FRAME...............................................................................................................................................................................................12 TABLE 9: DEVICE ID AND REMOTE DEVICES ............................................................................................................................................................12 TABLE 10: RF-RECEIVER COMMANDS FROM THE HOST ..........................................................................................................................................14 TABLE 11: RF-RECEIVER CONNECTOR PINOUT..........................................................................................................................................................18 TABLE 12: SCAN CODE TABLE.....................................................................................................................................................................................19 3 2/16/2001 Introduction Revision 0.1 1. This document gives the minimum firmware specification required for a Custom Wireless NMB Keyboard with Pointing Device which is intended to be used with the Viewsonic Display Monitor. 2. This battery-powered remote keyboard transmits RF signal to the Base Unit (RF-Receiver), which connects to the Viewsonic Large Screen Monitor display unit through an UART serial interface. The communication medium is 2.4GHZ. It has 10 programmable channels and each remote unit has its Device ID to avoid interference. Overview Functional Block Diagram NMB Keyboard with Pointing RF TX Base Unit Receiver TX Viewsonic Large Screen Display Monitor
(UART) RX UEI Remote Control Figure 1: Keyboard/Remote, RF- Receiver and IP-Board interface (UART) RF TX The NMB remote devices communicate wirelessly through the Base Unit (RF-Receiver) one way and the Viewsonic Display Monitor interfaces to the Base Unit through an UART port. The NMB keyboard and the UEI Remote must have a minimum distance of one meter from the RF-Receiver for proper operation. UART Interface 3. The UART interface requires only four lines, Receive (RX), Transmit (TX), GND, and +5Vcc. The communication link will be half-duplex; meaning that each side is either a RF-Receiver or the HOST at any given time. Protocol Format of RF-RECEIVER (UART) to the HOST. 3.1 The RF-Receiver communicates serially with the Host at 9600-baud over a 4-lines connection. Data packets are exchanged over the Receive and Transmit line. Start 0 1 2 3 4 5 6 7 Stop Idle
(51 hex) Idle Figure 2: UART Protocol 3.2 Data Frame Bit 1 Bit 2 Bit 3 Bit 4 Bit 5 Bit 6 Bit 7 Bit 8 Bit 9 Bit 10 Table 1:Data Frame Start Bit D0 D1 D2 D3 D4 D5 D6 D7 Stop Bit 4 Always '0'
Data 0 (LSB) Data 1 Data 2 Data 3 Data 4 Data 5 Data 6 Data 7 (MSB) Always '1'
2/16/2001 Sleep Mode Wake Up Mode Power-On-Reset Revision 0.1 4. The wireless Keyboard with Pointing Device will generates a "power-on-reset" when power is first applied to the unit. The keyboard will test the checksum of the read-only memory (ROM), and random access memory (RAM) test. On satisfactory completion of the test, keyboard scanning begins and the pointing device will begin scan the sensor. 5. The keyboard and the pointing device unit are to provide reduced power consumption sleep mode. If no data packet is transmitted within XX seconds, RF transmitter can go to sleep mode. While in this mode, the unit must maintain the current status. 6. When the keyboard key or pointing device is pressed or moved, the unit will wake up and transmit the key data or movement data. 5 Data Packet Revision 0.1 7. It is recommended that for the FSK direct modulation system of the RF communications, the Data Format below is recommended. 2/16/2001 Sync Byte Preamble Device Number 8bits Device ID/
X Coord Status 8 bits
8 bits Y Coord /
Scan code 8 bits Checksum 8 bits 16 bits 9600-baud rate (104.1 us/bit) 64 bits 16 bits Baud:
Total bits:
Sync Bytes:
Preamble:
Device Number:
Device ID/ Status: 8-bits Device ID:
Sync data bytes are used to stabilize the demodulation of the receiver side after a period of no signal input. Recommended four byte of "hex 0F". It is used for decoder bit sync. Recommended 2 bytes of "hex 55". 8-bits, Device number will be maximum of decimal 99, hex 63 Bit 0 - Bit 2 = 000b for RF-Receiver, 001b for NMB keyboard, 010b for UEI key data, 011b for NMB Pointing device, 100b for UEI Pointing device Keyboard Status Data:
Bit 3 = Reserved (0) Bit 4 = Reserved (0) Bit 5 = Reserved (0) Bit 6 = Reserved (0) Bit 7 = Battery Status (0=ok, 1= low) Pointing Device Status Data:
Bit 3 = Pointing Device Left Button Status (1 = Down, 0 = Up) Bit 4 = Pointing Device Right Button Status (1 = Down, 0 = Up) Bit 5 = X coordinate sign (0 = positive, 1 = negative) Bit 6 = Y coordinate sign (0 = positive, 1 = negative) Bit 7 = Battery Status (0=ok, 1= low) X coordinate/ :
Y coordinate/ Scan code: 8 bits 8 bits Keyboard Data = Reserved (0) Pointing Device =X-Data: 8 bits Keyboard Data: Scan Code (Make/Break) * Scan codes are shown in Table 2 Pointing Device = Y-Data: 8 bits Checksum:
(Device Number + Device ID/ Status + Xcoord + Ycoord/Scan Code) 6 Key Types Revision 0.1 8. All keys including the Pointing Device buttons are make/break. When a key or button is pressed, the unit will transmit the following data as shown in the protocol. For reliable data transmission, keystroke and control push buttons packets are transmitted twice wirelessly from NMB Remote Devices. 2/16/2001 MAKE 8ms MAKE BREAK 8ms BREAK Stuck key Keep Alive Keyboard or Remote Sleep Mode 9. Transmitter shall enable the "Stuck Key" bit and transmit it to the Receiver when a stuck key is detected after xx ms. 10. The remote devices shall enable the "Sleep Mode" bit when the Remote or Keyboard is to enter Sleep Mode. 11. The remote devices shall enable the "Keep Alive" bit when the user is holding a key down (not typing) for more than 70ms. 12. Hold down the Resync button and press one of the numeric keys (1-0) to select the channel number. At this time, the 'signature ID' (Resync make code = 76hex) will be sent at the selected channel. The data format of the signature ID is the same as the key data packet described in the NMB keyboard data packet. 13. RF Power On Allocate Frequency Tx Data Input RF Power Management T1 X Resync Button T2 X X Figure 3. Timing Sequence in RF Power Management. Transmitter Data Input Level T1 = Power On Stable Time. Typically, it should be T1 > 5ms T2 = Frequency Stable Time. Typically, it should be T2 > 20ms 14. The transmitter data input level should be fixed as the supply voltage drops when using battery. It is required that the Input level will be Vp-p = 100mv (+/- 10%). 15. Data coding is necessary for the wireless communication, which is to eliminate the DC offset of the demodulation caused by the series of 1's or 0's. The Manchester Coding is recommended here. Data Coding 7 Hardware Interface Revision 0.1 16. The interface to the RF-Transmitter and RF-Receiver module shall be described in the table below. 2/16/2001 Pin Number Tx-Module Rx-Module Parameter Input voltage Ground TX-Data Input Synthesizer Enable Synthesizer SDA Synthesizer SCK 1 2 3 4 5 6 2.2 V min. Ground Data input TTL input TTL input TTL input 3.3 V min. Ground Data output TTL input TTL input TTL input Table 2:RF_Transmitter / RF_Receiver Hardware Interface 17. Serial Input Data Timing Table 3. Serial Input Data Timing for Selecting Channel. 8 Revision 0.1 18. General Specification The performance requirements are contained in the table below 2/16/2001 Parameter Number of channels Channel spacing Receive frequency band Demodulation Receiver sensitivity Data rate Transmit frequency band Modulation Radiated power FCC Requirements Duplex type RF frequency tolerance Temperature range Power source Power consumption Dimensions Weight Other requirements Table 2. General Specification Tx Module 10 channels 500 kHz N/A Description Rx Module 10 channels*
N/A 2400 to 2483.5 MHz Minimum Maximum Maximum Fundamental Spurious emissions Operating Storage Nominal Maximum operational supply current PLL lock on time N/A N/A 19.2 kbps 2400 to 2483.5 MHz N/A FSK detection
-90 dBm 19.2 kbps FSK
-10 dBm 50 millivolts/meter @
3 meters 500 microvolts/meter
@ 3 meters Transmit only 10 ppm N/A N/A N/A 500 microvolts/meter
@ 3 meters Receive only 10 ppm 0 to 50 C
-10 to 60 C 2.5 VDC 15 mA 0 to 50 C
-10 to 60 C 3.3 VDC 40 mA 28mm x 22mm x 8mm To be determined 50 ms 32 mm x 45mm x 8mm To be determined 10 ms Rqmt No. 4.1 4.2 4.3 4.4 4.5 4.6 4.7 4.8 4.9 4.10 4.11 4.12 4.13 4.14 4.15 4.16 4.17 Note
* : The output data of channel 1-5 and channel 6-10 are different. Channel 1~5 : Tx input data Rx output data 9 Revision 0.1 19. Frequency Plan 2/16/2001 Table 4: Transmitter Frequency Plan Channel 1 2 3 4 5 6 7 8 9 10 Tx module transmit frequency 2446.7 MHz 2448.7 MHz 2449.7 MHz 2451.7 MHz 2454.7 MHz 2456.3 MHz 2457.3 MHz 2459.3 MHz 2462.3 MHz 2464.3 MHz Table 5: Receiver Frequency Plan Channel Rx module Local 1 2 3 4 5 6 7 8 9 10 frequency 2436.0 MHz 2438.0 MHz 2439.0 MHz 2441.0 MHz 2444.0 MHz 2467.0 MHz 2468.0 MHz 2470.0 MHz 2473.0 MHz 2475.0 MHz Frequency Control 20. Serial data is processed using SDA, SCK, LE pins of the RF-Module for the Transmitter and the Receiver. Binary serial data is entered through the SDA pin. One bit of data is shifted into the shift register onto the rising edge of the clock (SCK). When the load enable (LE) pin is high, stored the data latched. After the two 19-bit register being latched, the frequency will be locked. CH 1 2 3 4 5 6 7 8 9 10 Freq. 2446.7 MHz 2448.7 MHz 2449.7 MHz 2451.7 MHz 2454.7 MHz 2456.3 MHz 2457.3 MHz 2459.3 MHz 2462.3 MHz 2464.3 MHz 19-bit Register 19-bit Register 0010000000001010001 0010000000001010001 0010000000001010001 0010000000001010001 0010000000001010001 0010000000001010001 0010000000001010001 0010000000001010001 0010000000001010001 0010000000001010001 10 0010111111000100110 0010111111001001110 0010111111001100010 0010111111010001010 0010111111011000110 0010111111101100110 0010111111101111010 0010111111110100010 0010111111111011110 0011000000010000110 Revision 0.1 Table 6:Frequency Control for Transmitter 2/16/2001 CH 1 2 3 4 5 6 7 8 9 10 Freq. 2436.0 MHz 2438.0 MHz 2439.0 MHz 2441.0 MHz 2444.0 MHz 2467.0 MHz 2468.0 MHz 2470.0 MHz 2473.0 MHz 2475.0 MHz 19-bit Register 19-bit Register 1011000000000010001 1011000000000010001 1011000000000010001 1011000000000010001 1011000000000010001 1011000000000010001 1011000000000010001 1011000000000010001 1011000000000010001 1011000000000010001 0000100101101001000 0000100101101001100 0000100101101001110 0000100101101010010 0000100101101011000 0000100101110000110 0000100101110001000 0000100101110001100 0000100101110010010 0000100110001010110 Table 7: Frequency Control for Receiver
* Default Remote Device Channel will be number 1 and Device Number will 00 respectively. Functional Block Diagram RF- RECEIVER UNIT Tx RxD
+5V GND IP-Board 21. Figure 4: RF- Receiver and IP-Board interface (UART) UART Interface 22. The UART interface requires only four lines, Receive (RX), Transmit (TX), GND, and +5Vcc. The communication link will be half-duplex; meaning that each side is either a RF-Receiver or the HOST at any given time. 22.1 Protocol Format of RF-RECEIVER (UART) to the HOST. The RF-Receiver communicates serially with the Host at 9600-baud over a 4-lines connection. Data packets are exchanged over the Receive and Transmit line. The RF-Receiver only sends one make and one break code for each key pressed. After 70ms, Keep alive packet will be send until the key press is released. Start 0 1 2 3 4 5 6 7 Stop Idle
(51 hex) Idle 11 Figure 5: UART Protocol 2/16/2001 Revision 0.1 22.2 Data Frame Bit 1 Bit 2 Bit 3 Bit 4 Bit 5 Bit 6 Bit 7 Bit 8 Bit 9 Bit 10 Start Bit D0 D1 D2 D3 D4 D5 D6 D7 Stop Bit Always '0'
Data 0 (LSB) Data 1 Data 2 Data 3 Data 4 Data 5 Data 6 Data 7 (MSB) Always '1'
Power Down Timing Protocol Table 8: Data Frame 23. In the event of Power Down, all the critical parameters and Channel Number in the RF-Transmitter and RF-Receiver unit will be save. 24. Transmission of Data Packet between the RF-Receiver and the HOST must have a delay at least four byte times (about 4ms at 9600 baud) between the last byte of one data packet and the first byte of the ID code of the next data packet. There must be no more than two bytes times delay (about 2ms at 9600 baud) between the ID code and data byte(s) within a packet. 25. Three Status indicators Num Lock, Caps Lock, and Scroll Lock can be activated or deactivated by pressing the respective keys from the transmitter keyboard. Once the HOST receives the scan code of these keys, the HOST will activate and deactivate the status of each function in the screen 26. When a key is pressed and held, the make scan code is sent. After a delay of 70ms +/- 20%, the Remote Device will send a "Keep Alive Data"- packet every 70ms until the break scan code is received. 27. When remote device has a Device ID and Device Number. Device ID shows the category of the Remote device. The following table shows the device Ids for different categories. Set/Reset Keyboard Status Indicators Device ID and Device Number Repeat Keys Remote Device Keyboard Keypad Remote Control Keypad Keyboard Pointing Device Remote Control Pointing Device Device ID 1 2 3 4 12 Table 9: Device ID and Remote Devices 2/16/2001 Revision 0.1 Device Number is pre-loaded in the factory before the device is shipped. The number is chosen randomly from 0 to 99. The Host will validate the received data packet by checking the Device Number is registered for that Device ID or not. After the channel synchronization, the Device Number of each remote device will be registered in the host. Note that for both keyboard and remote control, keypad and pointing device have the same Device Number. During synchronization, only Device ID of the keypad and the Device Number will be sent. The host should also register the Device Number for the pointing device of the corresponding device. 28. There are 10 channels, which are numbered from 1 to 0, to be used in the communication between the RF-Receiver and the remote devices as keyboard and remote control. For reliable data transmission, keystroke and control push buttons packets are transmitted twice wirelessly from UEI /NMB Devices. Channel Synchronization 28.1 Changing Channel of the RF-Receiver The Host using the command Set Channel can change the channel of the RF-Receiver. The details can be found in the section, Set Channel. Normally, the HOST will show the channel number on the screen and then wait for the reception of the signatures (i.e. Re-Sync code, 76hex, defined in Table 2) from the remote devices for confirmations. 28.2 Changing Channel of the Remote Device The channel of the remote device can be changed as the following procedure. 1. 2. Hold down the Sync button on the device Press the button on the numeric keypad on the remote device to select the channel number. At this time, the signature will be sent continuously at the selected channel until the button is released. The data format of the signature id the same as the key data packet describe in the section, NMB keyboard Data Packet. 13 Revision 0.1 29. The following commands that the HOST may send and their hexadecimal values. Commands Summary 2/16/2001 Hex Value Table 10: RF-Receiver commands from the HOST Command Set Channel Channel Open Channel Close Get Version Number Read RSSI F1 F2 F3 F4 F5 29.1 Set Channel (Hex F1) This command will be used to set the RF channel of the receiver. Host Command:
< Channel Number >
7 6 5 4 3 2 1 0
<hex F1> < Device ID=0 >
1 1 1 1 0 0 0 1 0 0 0 0 0 0 0 0 2nd Byte 1st Byte 3rd Byte 1st Byte:
2nd Byte:
3rd Byte:
Bit 0 - Bit 2 = < Device ID = 000b >
Bit 3 - Bit 7 = Reserved
<CMD =hex F1>
<Channel Number>
RF-Receiver Respond:
7 6 5 4 3 2 1 0 2nd Byte 0 0 0 0 0 0 0 0 1st Byte 1st Byte 2nd Byte Bit 0 - Bit 2 = < Device ID = 000b >
Bit 3 - Bit 7 = Reserved
<Channel Number>
29.2 Channel Open / Close Commands The System can issue Channel Open or Close commands ( hex F2 or hex F3) to the RF-Receiver. The default state on power-on will be Channel Close. When the Channel is Close the RF-
Receiver will ignore incoming RF data. 29.2.1 Channel Open ( Hex F2) On the receipt of this command, The RF-Receiver will open the communication link between the HOST and RF-Receiver. Host Command:
<hex F2>
1 1 1 1 0 0 1 0
< Device ID=0 >
0 0 0 0 0 0 0 0 1st Byte 2nd Byte 1st Byte:
Bit 0 - Bit 2 Bit 3 - Bit 7
= < Device ID=0 >
= Reserved 14 Revision 0.1 2nd Byte:
<CMD =hex F2>
2/16/2001 RF-Receiver Respond:
7 6 5 4 3 2 1 0 2nd Byte 0 0 0 0 0 0 0 0 1st Byte 1st Byte 2nd Byte Bit 0 - Bit 2 = < Device ID = 000b >
Bit 3 - Bit 7 = Reserved
<Channel Number>
29.2.2 Channel Closed ( Hex F3) On the receipt of this command, The RF-Receiver will closed the communication link between the HOST and RF-Receiver. Host Command:
<hex F3>
1 1 1 1 0 0 1 1
< Device ID=0 >
0 0 0 0 0 0 0 0 1st Byte 2nd Byte 1st Byte:
2nd Byte:
Bit 0 - Bit 2 Bit 3 - Bit 7
<CMD =hex F3>
= < Device ID=0 >
= Reserved RF-Receiver Respond:
7 6 5 4 3 2 1 0 2nd Byte 0 0 0 0 0 0 0 0 1st Byte 1st Byte 2nd Byte Bit 0 - Bit 2 = < Device ID = 000b >
Bit 3 - Bit 7 = Reserved
<Channel Number >
29.3 Get Version Number ( Hex F4) On the receipt of this command, The RF-Receiver will send the version number of the firmware to the HOST. Host Command:
<hex F4>
1 1 1 1 0 0 1 1
< Device ID=0 >
0 0 0 0 0 0 0 0 1st Byte 2nd Byte 1st Byte:
2nd Byte:
Bit 0 - Bit 2 Bit 3 - Bit 7
<CMD =hex F4>
= < Device ID=0 >
= Reserved
< Channel Number >
7 6 5 4 3 2 1 0
<Device ID> < Version Number >
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 3rd Byte 2nd Byte 1st Byte RF-Receiver Respond:
1st Byte 2nd Byte
<Version Number, max = dec. 99, hex 63>
Bit 0 - Bit 2 = < Device ID = 000b >
Bit 3 - Bit 7 = Reserved 15 Revision 0.1 3rd Byte
<Channel Number >
2/16/2001 29.4 Read RSSI ( Hex F5) Not implemented On the receipt of this command, The RF-Receiver will send the RSSI value of the current channel to the HOST. This command is used for testing purpose or future enhancement. Host Command:
<hex F5>
1 1 1 1 0 0 1 1
< Device ID=0 >
0 0 0 0 0 0 0 0 1st Byte 2nd Byte 1st Byte:
2nd Byte:
Bit 0 - Bit 2 Bit 3 - Bit 7
<CMD =hex F5>
= < Device ID=0 >
= Reserved
< Channel Number >
7 6 5 4 3 2 1 0
<Device ID> < RSSI value,max=dec.255 >
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 3rd Byte 2nd Byte 1st Byte RF-Receiver Respond:
1st Byte 2nd Byte 3rd Byte
< RSSI value,max=dec.255 >
Bit 0 - Bit 2 = < Device ID = 000b >
Bit 3 - Bit 7 = Reserved
<Channel Number >
NMB Keyboard Data Packet 30. The Keyboard data packet format is three bytes long. The first byte consists of the Device Number followed by the second byte = Device ID (001b) and the battery status bit, the third byte = Scan Code
(Make/Break) of the Keyboard. Scan Code Table 10
<Scan Code>
Device ID + Battery Status 7 0 0 0 0 0 0 1 7 6 5 4 3 2 1 0
<Device Number>
7 6 5 4 3 2 1 0 3rd Byte 2nd Byte 1st Byte 1st Byte:
2nd Byte:
<Device number, max. of dec. 99>
Bit 0 - Bit 2
= Device ID = 001b
= Reserved ( 0 ) Bit 3 - Bit 6 Bit 7
= Battery Status, 0 = ok, 1 = low
<Scan Code> (Make / Break) 3rd Byte:
* Scan Code are shown Remote UEI Key Data Packet 31. The Remote UEI key data packet format is three bytes long. The first byte consists of the Device Number followed by the second byte = Device ID (010b) and the battery status bit, the third byte = Scan Code
(Make/Break) of the Remote Key. Scan Code Table 10.
<Scan Code>
Device ID + Battery Status 7 0 0 0 0 0 1 0 7 6 5 4 3 2 1 0
<Device Number>
7 6 5 4 3 2 1 0 3rd Byte 2nd Byte 1st Byte 1st Byte:
2nd Byte:
3rd Byte:
<Device number, max. of dec. 99, hex 63>
Bit 0 - Bit 2 Bit 3 - Bit 6 Bit 7
<Scan Code> (Make / Break) 16
= Device ID = 010b
= Reserved ( 0 )
= Battery Status, 0 = ok, 1 = low
* Scan Code are shown Revision 0.1 32. The data packet format is four bytes long. NMB Pointing Device Data Packet 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0 4th 3rd Byte 2/16/2001 7 6 5 4 3 2 1 0 1st Byte 7 6 5 4 3 0 1 1 2nd Byte
<Device Number, max = dec 99, hex 63>
Bit 0 - Bit 2 Bit 3 Bit 4 Bit 5 Bit 6 Bit 7
= Device ID = 011b
= Left Button Status (1=Down, 0=Up
= Right Button Status (1=Down, 0=Up)
= X-Coordinate sign (0=positive, 1=negative)
= Y-Coordinate Sign (0=positive, 1=negative)
= Battery Status, 0 = ok, 1 = low) 1st Byte:
2nd Byte:
3rd Byte:
4th Byte:
UEI Pointing Device Data Packet
<X-data>
<Y- data>
33. The data packet format is four bytes long. 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0 3rd Byte 7 6 5 4 3 1 0 0 2nd Byte 7 6 5 4 3 2 1 0 1st Byte
<Device Number, max = dec 99, hex 63>
Bit 0 - Bit 2 Bit 3 Bit 4 Bit 5 Bit 6 Bit 7
<X-data>
<Y- data>
= Device ID = 100b
= Left Button Status (1=Down, 0=Up
= Right Button Status (1=Down, 0=Up)
= X-Coordinate sign (0=positive, 1=negative)
= Y-Coordinate Sign (0=positive, 1=negative)
= Battery Status, 0 = ok, 1 = low) Stuck Key Data Packet 34. Receiver shall send this command when a stuck key is detected.
<hex FC>
3rd Byte 7 6 5 4 3 2 1 0 Device ID + Battery Status 7 0 0 0 0 2 1 0 7 6 5 4 3 2 1 0
<Device Number>
2nd Byte 1st Byte 4th 1st Byte:
2nd Byte:
3rd Byte:
4th Byte:
1st Byte:
2nd Byte:
3rd Byte:
<Device number, max. of dec. 99, hex 63>
Bit 0 - Bit 2 Bit 3 - Bit 6 Bit 7
<CMD = hex FC>
= Device ID (001 = Keyboard, 010b = Remote)
= Reserved ( 0 )
= Battery Status, 0 = ok, 1 = low 17 Sleep Data Packet Revision 0.1 35. Receiver shall send this command when the Remote or the wireless keyboard is about to enter sleep mode. This way, the IP board can fully aware of the transmitter state.
<hex FD>
2/16/2001 3rd Byte 7 6 5 4 3 2 1 0 Device ID + Battery Status 7 0 0 0 0 2 1 0 7 6 5 4 3 2 1 0
<Device Number>
2nd Byte 1st Byte 1st Byte:
2nd Byte:
<Device number, max. of dec. 99, hex 63>
Bit 0 - Bit 2 Bit 3 - Bit 6 Bit 7
<CMD = hex FD
= Device ID = 010b
= Reserved ( 0 )
= Battery Status, 0 = ok, 1 = low 3rd Byte:
Keep Alive Data Packet (Revised) 36. This code will be sent only when the user is holding a key down (not typing), this is to provide a keep alive timeout in the IP board. If the Keep Alive code is not receive within 200ms, the IP board will timeout and release the Break Code of the held key.
<hex FE>
Device ID + Battery Status 7 0 0 0 0 0 1 0 7 6 5 4 3 2 1 0
<Device Number>
7 6 5 4 3 2 1 0 3rd Byte 2nd Byte 1st Byte 1st Byte:
2nd Byte:
3rd Byte:
<Device number, max. of dec. 99, hex 63>
Bit 0 - Bit 2 Bit 3 - Bit 6 Bit 7
<CMD =hex FE>
= Device ID (0 01 = keyboard, 010= remote control)
= Reserved ( 0 )
= Battery Status, 0 = ok, 1 = low 37. RF-Receiver connector Connector type:
Vendor: Long Chu Electronics Co. Ltd Type: P200 (Straight Type) Pitch: 2.0mm Current rating: 2amp Insulation Resistance: 1000 mega ohm, min. Table 11: RF-Receiver connector pinout Pin #
1 2 3 4 5 6 Name Vcc GND RxD TxD NC GND Comments
+5V power Ground Received serial data from IP board to RF-Receiver. Transmitted serial data from RF-Receiver to IP board. No Connect Ground RF-Receiver mechanical 38. Add mechanical outline of module including dimension, mounting, etc.. 18 Revision 0.1 2/16/2001 Table 12: Scan Code Table Key #
Description Make Code Num_Lock Print Scrn Scroll Lock Back Space ESC F1 F2 F3 F4 F5 F6 F7 F8 F9 F10 F11 F12 Pause
1 / !
2 / @
3 / #
4 / $
5 / %
6 / ^
7 / &
8 / *
9 / (
0 / )
Home Tab Q W E R T Y U I O P
A S D F G H J K L
Page Up Caps Lock 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 10 11 12 13 14 15 16 17 18 19 1A 1B 1C 1D 1E 1F 20 21 22 23 24 25 26 27 28 29 2A 2B 2C 2D 2E 2F 30 31 32 33 34 35 36 37 38 39 3A 3B Break Code Key #
81 82 83 84 85 86 87 88 89 8A 8B 8C 8D 8E 8F 90 91 92 93 94 95 96 97 98 99 9A 9B 9C 9D 9E 9F A0 A1 A2 A3 A4 A5 A6 A7 A8 A9 AA AB AC AD AE AF B0 B1 B2 B3 B4 B5 B6 B7 B8 B9 BA BB 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 115 115 116 117 19 Description Page Down L_Shift Z X C V B N M
Right_Shift Up Arrow End Control FN LWIN ALT Space Bar APP INS DEL Left Arrow Down Arrow Right Arrow Reverse Play Forward Record Stop Pause Instant Replay Jump CH Jump Present EPG
+100 Multi-View Back Forward Stop Refresh Search Favorites Web home Get mail Mute Pip Previous Menu Channel Up Channel Down Right Click Left Click Volume Down Volume Up Power Re-Sync Make Code Break Code 3D 3E 3F 40 41 42 43 44 45 46 47 48 49 4A 4B 4C 4D 4E 4F 50 51 52 53 54 55 56 57 58 59 5A 5B 5C 5D 5E 5F 60 61 62 63 64 65 66 67 68 69 6A 6B 6C 6D 6E 6F 70
73 74 75 76 BD BE BF C0 C1 C2 C3 C4 C5 C6 C7 C8 C9 CA CB CC CD CE CF D0 D1 D2 D3 D4 D5 D6 D7 D8 D9 DA DB DC DD DE DF E0 E1 E2 E3 E4 E5 E6 E7 E8 E9 EA EB EC ED EE EF F0
F3 F4 F5 F6 Revision 0.1 60 Enter 3C BC 118 2/16/2001
* Set and Reset in Pointing Device Data Packet. 20 Revision 0.1 39. 2/16/2001 Change Device Number Press Re_sync + Fn and held down for 3 seconds, then enter 2- digits Device Number 0-9. Select Device Channel Number. Press Re_Sync and held down, then enter Channel Number 1 or 2, 3, 4, 5, 6, 7, 8, 9, 0. Test Mode Channel testing. Transmitter channel must default to channel 1. Press 1 + 3 + C and held down for 6 seconds and release, Ten channels will be tested and after the testing, the channel number will return to default channel. Frequency testing. Press 1 + 3 + F and held down for 6 seconds and release. The device channel frequency can be measured by using spectrum analyzer. Pressing F4, the transmitter will transmit one and zero continously. Pressing F3, the transmitter will exit on frequency testing. 21 40. 40. FEDERAL COMMUNICATIONS COMMISSION INTERFERENCE STATEMENT This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following measures:
-- Reorient or relocate the receiving antenna.
-- Increase the separation between the equipment and receiver.
-- Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.
-- Consult the dealer or an experienced radio/TV technician for help. CAUTION:
Any changes or modifications not expressly approved by the grantee of this device could void the user's authority to operate the equipment. FCC RF Radiation Exposure Statement This equipment complies with FCC RF radiation exposure limits set forth for an uncontrolled environment. This equipment should be installed and operated with a minimum distance of 20cm between the radiator and your body.
| frequency | equipment class | purpose | ||
|---|---|---|---|---|
| 1 | 2002-03-13 | 2446.7 ~ 2464.3 | DXX - Part 15 Low Power Communication Device Transmitter | Original Equipment |
| app s | Applicant Information | |||||
|---|---|---|---|---|---|---|
| 1 | Effective |
2002-03-13
|
||||
| 1 | Applicant's complete, legal business name |
NMB Technologies Corp.
|
||||
| 1 | FCC Registration Number (FRN) |
0008923468
|
||||
| 1 | Physical Address |
Hi Tek Keyboard Division
|
||||
| 1 |
Chatsworth, California 91311
|
|||||
| 1 |
United States
|
|||||
| app s | TCB Information | |||||
| 1 | TCB Application Email Address |
t******@timcoengr.com
|
||||
| 1 | TCB Scope |
A2: Low Power Transmitters (except Spread Spectrum) and radar detectors operating above 1 GHz
|
||||
| app s | FCC ID | |||||
| 1 | Grantee Code |
AQ6
|
||||
| 1 | Equipment Product Code |
3900
|
||||
| app s | Person at the applicant's address to receive grant or for contact | |||||
| 1 | Name |
J**** G****
|
||||
| 1 | Title |
Director of Engineering
|
||||
| 1 | Telephone Number |
818 3********
|
||||
| 1 | Fax Number |
818 3********
|
||||
| 1 |
j******@nmbtc.com
|
|||||
| app s | Technical Contact | |||||
| n/a | ||||||
| app s | Non Technical Contact | |||||
| n/a | ||||||
| app s | Confidentiality (long or short term) | |||||
| 1 | Does this application include a request for confidentiality for any portion(s) of the data contained in this application pursuant to 47 CFR § 0.459 of the Commission Rules?: | Yes | ||||
| 1 | Long-Term Confidentiality Does this application include a request for confidentiality for any portion(s) of the data contained in this application pursuant to 47 CFR § 0.459 of the Commission Rules?: | No | ||||
| if no date is supplied, the release date will be set to 45 calendar days past the date of grant. | ||||||
| app s | Cognitive Radio & Software Defined Radio, Class, etc | |||||
| 1 | Is this application for software defined/cognitive radio authorization? | No | ||||
| 1 | Equipment Class | DXX - Part 15 Low Power Communication Device Transmitter | ||||
| 1 | Description of product as it is marketed: (NOTE: This text will appear below the equipment class on the grant) | RF Keyboard with Integrated Pointing Device | ||||
| 1 | Related OET KnowledgeDataBase Inquiry: Is there a KDB inquiry associated with this application? | No | ||||
| 1 | Modular Equipment Type | Does not apply | ||||
| 1 | Purpose / Application is for | Original Equipment | ||||
| 1 | Composite Equipment: Is the equipment in this application a composite device subject to an additional equipment authorization? | No | ||||
| 1 | Related Equipment: Is the equipment in this application part of a system that operates with, or is marketed with, another device that requires an equipment authorization? | No | ||||
| 1 | Is there an equipment authorization waiver associated with this application? | No | ||||
| 1 | If there is an equipment authorization waiver associated with this application, has the associated waiver been approved and all information uploaded? | No | ||||
| app s | Test Firm Name and Contact Information | |||||
| 1 | Firm Name |
DEKRA Testing and Certification Co., Ltd.
|
||||
| 1 | Name |
S**** H********
|
||||
| 1 | Telephone Number |
886-2******** Extension:
|
||||
| 1 | Fax Number |
886-2********
|
||||
| 1 |
s******@quietek.com
|
|||||
| Equipment Specifications | |||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Line | Rule Parts | Grant Notes | Lower Frequency | Upper Frequency | Power Output | Tolerance | Emission Designator | Microprocessor Number | |||||||||||||||||||||||||||||||||
| 1 | 1 | 15C | 2446.70000000 | 2464.30000000 | 0.0000700 | ||||||||||||||||||||||||||||||||||||
some individual PII (Personally Identifiable Information) available on the public forms may be redacted, original source may include additional details
This product uses the FCC Data API but is not endorsed or certified by the FCC