X Mobile Compatibility List
- Michelle Cabaya (Unlicensed)
*** IMPORTANT NOTE REGARDING BLUETOOTH SCANNERS ***
CXT Software strongly recommends that customers select devices indicated as having "Excellent Compatibility" with X Mobile for dock or mission-critical barcode scanning. For light-duty scanning, the Bluetooth scanners listed below may provide good results with specific Android devices. Due to the large number of available Android devices as well as the variability in Bluetooth support on those devices, customers MUST test Bluetooth scanner and Android device combinations before deploying them to drivers. Customers cannot assume that any Bluetooth scanner will pair reliably with any Android device. CXT Software does not test Bluetooth scanners with all Android devices compatible with X Mobile.
Scanner | Compatibility | Interface | Ruggedized | |
---|---|---|---|---|
Cipher Labs 1660 | Bluetooth | References Comments
Test Results When I initially started testing the unit I first had to pair the unit. This requires that both your Android device and the scanner are in pairing mode. Once they were both in pairing mode the scanner came with these barcode sheets which I scanned that set the passcode to "0000". I was then prompted on the Android device to enter the pairing code "0000". Once I entered the code the device was successfully paired. After pairing was completed I then launched GetBlue and changed my Datasource to BlueTooth which then triggered GetBlue to try and connect to the scanner. Once GetBlue was connected I was able to scan a barcode and see the input being passed into X Mobile. The scanner has dozens of settings that customers will have to navigate on their own as we won't be able to provide support for the devices multiple configuration options. If customers have issues with the device they should start over, this requires the device be reset to defaults, re-paired, and then tested to confirm functionality. The device puts it'self to sleep after approximately 20 minutes of inactivity. Once this happens the user will have to press the power button and wait for the scanner to re-establish communication with the Android device. This process takes about 10 - 30 seconds and seemed to work 5 out of the 5 times I tested resuming from sleep. The scanning quality of this device seemed significantly lower than a dedicated all in one scanner such as the Intermec CN50 or Motorola MC65. The scanners recognition at times took multiple attempts to read barcodes. I would consider this a low-end economy scanner since its recognition was substantially slower and less accurate at times than higher end all in one devices. The device has a single light which from what I saw can change to Blue, Red, and Green. When the device recognizes a barcode the status light appears to flash green momentarily and the unit makes a single beep. The beeping of the unit will most likely cause confusion for drivers since they might be inclined to believe that because the barcode scanner beeped, that they scanned the correct barcode. I couldn't determine if there was a way to disable the acquisition beep on the scanner, but customers should definitely train drivers to ignore the scanner beep and only listen to the X Mobile beeps. The devices manufacturer page indicates the unit should last all day however this might be inconvenient since the batteries would have to be charged daily. My test unit has "NO USB" (1660) connection so charging is only possible by removing the two triple A batteries that power the unit. According to the manufacturer's site it appears there might be two versions of this unit for sale the 1660 and 1661. The one I tested has the two blue buttons on the top (1660). http://www.cipherlab.com/catalog.asp?CatID=8&SubcatID=11&ProdID=469 The last thing to note is that since both the power and scan button are on the same surface it's going to be very common for customers to press the power button instead of the scan button possibly shutting the device off when they're intending to scan a barcode. I don't like this design aspect and I would have put the power button somewhere besides right next to the scan button. Overall the device seems like it will do fine for light duty scanning and will require that customers familiarize themselves in depth with maintaining a Bluetooth connection between their devices. The unit will also require that drivers have some spare batteries since the 1660 unit has no way to charge the batteries. One caveat is that the batteries are triple A and they could be purchased at almost any gas station. Est. Mfg. Date: 2011 | ||
Motorola CS3070 | Bluetooth | References Comments
Test Results Steps taken to test:
Est. Mfg. Date: 2011 | ||
Serial IO KDC200 | Bluetooth | References Comments
Test Results When I initially started testing the unit I first had to pair the unit. This requires that both your Android device and the scanner are in pairing mode. Once the device had been paired, the GetBlue application needs to be configured to use this device to capture barcode scan data. GetBlue is able to be configured to use this device, however, since the device has issues staying paired, GetBlue was not able to stay connected to the device in order to be able to capture barcode scan data. Est. Mfg. Date: Unknown | ||
Serial IO Scanfob® 2002 | Bluetooth | References Comments
Test Results When I initially started testing the unit I first had to pair the unit. This requires that both your Android device and the scanner are in pairing mode. The device can be set to Pairing Mode by either scanning the Start Pairing barcode or by pressing and holding a small button on the unit. This unit was never recognized by the Android device and could not be paired. If the device cannot be paired with a device, you will not be able to use it to scan. Tried to pair this device with different Android devices, however, I encountered the same pairing issue. Est. Mfg. Date: 2002 | ||
Socket Mobile CHS 7P (CX2862-1298) | Bluetooth | References Comments
Test Results Steps taken to test:
Est. Mfg. Date: 2011 | ||
Socket Mobile CHS 7Xi (CX2864-1336) | Bluetooth | References Comments
Test Results Steps taken to test:
Est. Mfg. Date: 2011 | ||
Unitech MS910 | Bluetooth | References Comments
Test Results
Est. Mfg. Date: 2012 |
Compatibility: Excellent compatibility | OS: Android | Ruggedized: Very ruggedized Partially ruggedized Not ruggedized | Cell Carriers: AT&T Mobility | X Mobile Features: GPS |
---|