Hi everyone,
We are working on the 1st maintenance release for the RS507 firmware. The new firmware will add Bluetooth SPP (Serial Port Profile) and HID (Human Interface Device) profile support to the RS507 in addition to the current interface to our MPA-based terminals.
A beta version is planned to be available by mid June 2011 and the MR is planned to be released into production by mid September 2011. No hardware changes are planned for this release.
Currently, we have an early beta version that was developed last year under a CPR that requires to flash the special firmware in the field. However this version excludes the concurrent interface to the MPA-based terminal and has a bug (in the BT stack) that prevents auto reconnect in HID mode. Never-the-less, this version is available from me upon request and justification and is already being successfully used by several customers.
This early beta version was only tested with PCs running Windows XP SP3 but seems to work with other devices as well. If the PC does not include a built-in Bluetooth radio, a USB dongle is required. Most USB dongles seem to work well in SPP. However, so far only Socket USB dongle works in HID (model BL4543-734 (http://www.socketmobile.com/products/bluetooth-barcode-scanners/accesso…). It uses the Microsoft BT stack and pairs easily to the RS507. If the RS507 reboots or goes out of range and then back in range, it automatically reconnects to the PC without any user interaction required.
Once the MR firmware is released, the HID issue should be solved.
As far as non-Windows PC and non-Motorola MPA-based devices, once we release the SPP and HID as part of the current MR, we expect it to work with any device that supports SPP or HID. However, since we do not plan to test it with non-Windows PC devices, we will need the TA help in verifying it before you set your customers expectations.
In HID, pairing is by discovery only. With devices that support BT 2.1 which includes Secure Simple Pairing (SSP), no passkey will be required.
In SPP, pairing can be performed either by discovery or by scanning a special Code128 barcode that includes the prefix FNC3B followed by the device Bluetooth address (BD address). If passkey is required (BT 2.0 or earlier), the default passkey used by the RS507 is 12345, otherwise the RS507 can load the requested passkey by scanning the barcodes representing the 5 digits one by one (these barcodes are available also in the RS507 PRG).
For all Non-MPA-based devices, no CPR should be requested and the burden is on the customer, partner and the TA supporting them to verify proper operation.
Please note that some of the non-windows devices do not support both SPP and HID, for example Apple’s iPAD supports HID only while RIM’s Blackberry Torch 9800 OS 6 supports only SPP.
Amnon Ish-Hurwitz
4 Replies
With regards to the non-Motorola Windows Mobile-based devices using the SPP protocol, would it be possible to control the RS507 scanner via APIs described in the BT_Scanning_Programmer_s Guide? Attached is document for referrence. Customer requires this level of RS507 scanner control for their fleet of multi-vendor devices.
Hi,
We are setting up 2 mandatory training sessions for our TAs who are being targeted for this unofficial beta tests.
Only TAs who will participate in one of these two training sessions will receive the beta firmware package.
If you did not receive the invitation but had previous communication with me about it, please contact me by email with a detailed reason. Amnon Ish-Hurwitz
Just to clarify...does this mean that the CPR firmware will be combined with our proprietary scanner mode firmware, so partners doesn't have to reflash new units before delivering the RS507 to customers? And when it comes to SPP and HID mode will the RS507 support ADF rules like any other scanner from us? Today it is very limited or broken.
Yes and Yes.