RN-42-HID-RD1

RN-42-HID-RD1 Datasheet

RN-WIFLYCR-UM-.01 RN-HID-UM

Part	Datasheet
RN-42-HID-RD1	RN-42-HID-RD1 (pdf)

PDF Datasheet Preview
RN-WIFLYCR-UM-.01 RN-HID-UM Bluetooth HID Profile 2012 Roving Networks. All rights reserved. RN-HID-UM Version 1.1r 3/13/2012 USER MANUAL RN-HID-UM-1.1r OVERVIEW Roving Networks Bluetooth modules support a variety of Bluetooth profiles, including human interface device HID , serial port profile SPP , DUN, HCI, and iAP for use with iPad, iPod and iPhone devices. The Bluetooth HID profile enables customers to develop wireless products such as computer keyboards and keypads, trackballs, mice, and other pointing devices, and game controllers gamepads, joysticks, steering wheels, etc. . Additionally, Roving Networks has extended the basic HID capability to allow programmability and control of devices such as the iPad. The HID Human Interface Device profile defines the protocol between: • Device human data input and output to and from the host. • or requests the services of a Human Interface Device. The Bluetooth HID profile allows users to control the HID descriptor, which defines the device’s feature set, and the HID report, which host uses to interpret the data as ASCII values, movement, etc. The HID report format follows the standard universal serial bus USB HID protocol as to leverage existing host drivers. NOTE This user manual focuses specifically on HID. The Roving Networks Bluetooth Advanced User Manual and Apple User Manual cover the functionality of all supported Bluetooth profiles. Because the HID profile is derived from Roving Network’s standard firmware, many of the concepts and commands found in the Advanced User Manual apply as well. In a typical usage scenario such as a keyboard, a device using the Roving Networks Bluetooth HID profile replaces the USB cable. In this case, the ASCII value of a key press is converted to a scan code in a raw HID report that the Bluetooth module sends over the Bluetooth link to the host. The host driver software decodes the raw HID report and passes the key values to the application running on the PC. Figure 1 shows some typical HID environments. Figure Typical HID Environments The type of HID device, such as a keyboard, mouse, or joystick, is defined by the HID descriptor in the raw HID report. RN-HID-UM-1.1r FIRMWARE OVERVIEW To use Roving Networks’ Bluetooth HID profile, you must use a special build of firmware, version or later. When you purchase a Roving Networks Bluetooth product, you must specify that you wish to use this firmware version so that Roving Networks can load it into the module. The part numbers for ordering modules with the HID profile are RN-41-HID and RN-42-HID. NOTE:This user guide assumes the reader has an understanding of Roving Networks standard Bluetooth firmware ASCII command interface and command set. It is strongly recommended that you refer to the Bluetooth Advanced User Manual prior to reading this document. Operational Modes Roving Networks Bluetooth modules operate in two modes data mode default and command mode. While in data mode, the module is essentially a data pipe. When the module receives data, it strips the Bluetooth headers and trailers and passes the user data to the UART. When data is written to the UART, the module constructs the Bluetooth packet and sends it out over the Bluetooth connection. Thus, the entire process of sending/receiving data to the host is transparent to the end microprocessor. You configure the module by putting it into command mode and sending ASCII commands over a serial port or the Bluetooth link. Once you change the configuration parameters, they persist until changed or you perform a factory reset. You enter command mode by opening a terminal emulator and sending the string to the module. You can connect to the module remotely over Bluetooth or via a computer. When you send the module returns CMD, indicating that it is in command mode. Once the module is in command mode, you can send configuration commands to it via the terminal. When you enter a valid command, the adapter returns AOK. It returns ERR for an invalid command and ? for unrecognized commands. Type h <cr> to see a list of commands, and d <cr> to view a summary of the adapter’s current settings. To return to data mode, type --- <cr> or reset the device and re-connect. Profile Configuration The HID firmware supports Bluetooth HID and SPP. You switch between these profiles using ASCII commands. In firmware version and higher, the SPP profile is enabled by default. There are two ways to switch the profile. Using PIO 11 On power up PIO 11 is sampled and if HIGH, HID profile is selected. Otherwise the profile stored in flash is used requires bit 9 to be set in the HID flags register. This is set by default . Using command mode To switch between HID and SPP, use the following commands: S~,6 R,1 // Enables HID profile // Reboot to use HID profile To switch back to SPP, use the following command: S~,0 R,1 // Enables SPP protocol // Reboot to use SPP RN-HID-UM-1.1r Device Discovery & Pairing Since the Roving modules default to SPP, they will show up as “FireFly-ABCD” upon power up, where ABCD are the last four digits of the MAC address. However, if the profile is changed to HID using the commands described above, the modules default to a HID keyboard and is discoverable with the name “FireFly-ABCD”, where ABCD are the last four digits of the MAC address. You can change the device type by setting the descriptor type using the HID flags register. After first pairing the host to a device with the Bluetooth HID module, the host initiates a connection. However, if the initial connection is broken, as the case when the power is cycled, the device must re-connect to the host. The host will not initiate a connection. Using DTR mode 4 default or pairing mode 6 allows the module to auto-connect back to the last paired host. Alternatively, you can reconnect by sending the C command from command mode. Quiet Mode Quite mode causes the device to be non-discoverable and non-connectable temporarily. This command does not survive power cycle. With firmware version and higher, the Q command now has 3 settings that have different responses as follows: // The module is discoverable and able to connect // The module is not discoverable and not able to connect // The module is able to connect but is not discoverable Authentication With firmware version and higher, SA is 2 bits. It can have the values 0, 1, 2, or 4, depending on the mode desired. SA,0 // With this mode, the module uses Bluetooth version NO encryption open mode . This mode is useful for legacy devices that do not need security. This mode is the same as in firmware version For this mode to work, both devices must support open mode. If either device requests authentication, the PIN code will be required. SA,1 // In Bluetooth version the default is keyboard I/O mode which is considered as a secure mode . For Android devices, the user is prompted with a 6-digit code and is asked to verify that the code matches on the module. Because the module cannot display a code, simply press OK or Yes on the remote device to authenticate. SA,2 // This mode corresponds to Bluetooth version Secure Simple Pairing SSP , or just works mode. This mode works with iPhones and PCs, however it may not work appropriately with some Android devices. SA,4 // This mode is PIN code mode, which forces Bluetooth version PIN code authentication. The functionality is similar to firmware version RN-HID-UM-1.1r Encryption In firmware version and higher, encryption is always enabled. In prior versions of firmware, you used the SE command to turn on encryption. Refer to “Creating a Custom UUID” for more information on the SE command functionality in firmware version and higher. Creating a Custom UUID In firmware version and higher, the SE command, SE,<1 16>, is used to set the UUID E stands for extended UUID . The GE command displays the extended UUID.

PDF Datasheet Preview

RN-WIFLYCR-UM-.01 RN-HID-UM

Bluetooth HID Profile
2012 Roving Networks. All rights reserved. RN-HID-UM Version 1.1r 3/13/2012

USER MANUAL

RN-HID-UM-1.1r

OVERVIEW

Roving Networks Bluetooth modules support a variety of Bluetooth profiles, including human interface device HID , serial port profile SPP , DUN, HCI, and iAP for use with iPad, iPod and iPhone devices. The Bluetooth HID profile enables customers to develop wireless products such as computer keyboards and keypads, trackballs, mice, and other pointing devices, and game controllers gamepads, joysticks, steering wheels, etc. . Additionally, Roving Networks has extended the basic HID capability to allow programmability and control of devices such as the iPad.

The HID Human Interface Device profile defines the protocol between:
• Device human data input and output to and from the host.
• or requests the services of a Human Interface Device.

The Bluetooth HID profile allows users to control the HID descriptor, which defines the device’s feature set, and the HID report, which host uses to interpret the data as ASCII values, movement, etc. The HID report format follows the standard universal serial bus USB HID protocol as to leverage existing host drivers.

NOTE This user manual focuses specifically on HID. The Roving Networks Bluetooth Advanced User Manual and Apple User Manual cover the functionality of all supported Bluetooth profiles. Because the HID profile is derived from Roving Network’s standard firmware, many of the concepts and commands found in the Advanced User Manual apply as well.

In a typical usage scenario such as a keyboard, a device using the Roving Networks Bluetooth HID profile replaces the USB cable. In this case, the ASCII value of a key press is converted to a scan code in a raw HID report that the Bluetooth module sends over the Bluetooth link to the host. The host driver software decodes the raw HID report and passes the key values to the application running on the PC. Figure 1 shows some typical HID environments.

Figure Typical HID Environments

The type of HID device, such as a keyboard, mouse, or joystick, is defined by the HID descriptor in the raw HID report.

RN-HID-UM-1.1r

FIRMWARE OVERVIEW
To use Roving Networks’ Bluetooth HID profile, you must use a special build of firmware, version or later. When you purchase a Roving Networks Bluetooth product, you must specify that you wish to use this firmware version so that Roving Networks can load it into the module. The part numbers for ordering modules with the HID profile are RN-41-HID and RN-42-HID.

NOTE:This user guide assumes the reader has an understanding of Roving Networks standard Bluetooth firmware ASCII command interface and command set. It is strongly recommended that you refer to the Bluetooth Advanced User Manual prior to reading this document.

Operational Modes

Roving Networks Bluetooth modules operate in two modes data mode default and command mode. While in data mode, the module is essentially a data pipe. When the module receives data, it strips the Bluetooth headers and trailers and passes the user data to the UART. When data is written to the UART, the module constructs the Bluetooth packet and sends it out over the Bluetooth connection. Thus, the entire process of sending/receiving data to the host is transparent to the end microprocessor.

You configure the module by putting it into command mode and sending ASCII commands over a serial port or the Bluetooth link. Once you change the configuration parameters, they persist until changed or you perform a factory reset. You enter command mode by opening a terminal emulator and sending the string to the module. You can connect to the module remotely over Bluetooth or via a computer. When you send the module returns CMD, indicating that it is in command mode.

Once the module is in command mode, you can send configuration commands to it via the terminal. When you enter a valid command, the adapter returns AOK. It returns ERR for an invalid command and ? for unrecognized commands. Type h <cr> to see a list of commands, and d <cr> to view a summary of the adapter’s current settings. To return to data mode, type --- <cr> or reset the device and re-connect.

Profile Configuration

The HID firmware supports Bluetooth HID and SPP. You switch between these profiles using ASCII commands. In firmware version and higher, the SPP profile is enabled by default. There are two ways to switch the profile.

Using PIO 11 On power up PIO 11 is sampled and if HIGH, HID profile is selected. Otherwise the profile stored in flash is used requires bit 9 to be set in the HID flags register. This is set by default .

Using command mode To switch between HID and SPP, use the following commands:

S~,6 R,1
// Enables HID profile // Reboot to use HID profile

To switch back to SPP, use the following command:

S~,0 R,1
// Enables SPP protocol // Reboot to use SPP

RN-HID-UM-1.1r

Device Discovery & Pairing

Since the Roving modules default to SPP, they will show up as “FireFly-ABCD” upon power up, where ABCD are the last four digits of the MAC address. However, if the profile is changed to HID using the commands described above, the modules default to a HID keyboard and is discoverable with the name “FireFly-ABCD”, where ABCD are the last four digits of the MAC address. You can change the device type by setting the descriptor type using the HID flags register.

After first pairing the host to a device with the Bluetooth HID module, the host initiates a connection. However, if the initial connection is broken, as the case when the power is cycled, the device must re-connect to the host. The host will not initiate a connection.

Using DTR mode 4 default or pairing mode 6 allows the module to auto-connect back to the last paired host. Alternatively, you can reconnect by sending the C command from command mode.

Quiet Mode

Quite mode causes the device to be non-discoverable and non-connectable temporarily. This command does not survive power cycle.

With firmware version and higher, the Q command now has 3 settings that have different responses as follows:
// The module is discoverable and able to connect
// The module is not discoverable and not able to connect
// The module is able to connect but is not discoverable

Authentication

With firmware version and higher, SA is 2 bits. It can have the values 0, 1, 2, or 4, depending on the mode desired.

SA,0
// With this mode, the module uses Bluetooth version NO encryption open mode . This mode is useful for legacy devices that do not need security. This mode is the same as in firmware version For this mode to work, both devices must support open mode. If either device requests authentication, the PIN code will be required.

SA,1
// In Bluetooth version the default is keyboard I/O mode which is considered as a secure mode . For Android devices, the user is prompted with a 6-digit code and is asked to verify that the code matches on the module. Because the module cannot display a code, simply press OK or Yes on the remote device to authenticate.

SA,2
// This mode corresponds to Bluetooth version Secure Simple Pairing SSP , or just works mode. This mode works with iPhones and PCs, however it may not work appropriately with some Android devices.

SA,4
// This mode is PIN code mode, which forces Bluetooth version PIN code authentication. The functionality is similar to firmware version

RN-HID-UM-1.1r

Encryption

In firmware version and higher, encryption is always enabled. In prior versions of firmware, you used the SE command to turn on encryption. Refer to “Creating a Custom UUID” for more information on the SE command functionality in firmware version and higher.

Creating a Custom UUID

In firmware version and higher, the SE command, SE,<1 16>, is used to set the UUID E stands for extended UUID . The GE command displays the extended UUID.

Notice: we do not provide any warranties that information, datasheets, application notes, circuit diagrams, or software stored on this website are up-to-date or error free. The archived RN-42-HID-RD1 Datasheet file may be downloaded here without warranties.

Datasheet ID: RN-42-HID-RD1 648080