BackCommon connection issues with Bluetooth
12 Jun 2007
Below are common issues encountered when using Bluetooth wireless technology on an Archer or Allegro Field PC. Possible solutions to each issue are also provided below.
Archer Field PC
Please follow each and every step of the procedures for setting up Bluetooth on the Archer Field PC provided on the following websites.
Bluetooth setup with Microsoft drivers (built-in Bluetooth)
Bluetooth setup with Socket drivers (used with the Socket BT CF card)
No Passkey Required by Bluetooth Device
When creating a Bluetooth partnership with a device that does not require a passkey, the Microsoft drivers used by the built-in Bluetooth module (and a few CF and SDIO BT cards) will still require a passkey to be entered.
If you can assign a passkey to the connecting device, it is recommended that a passkey be assigned to the device. Otherwise, please follow the exact procedures described in step 4 of the "Bluetooth Device Partnership" section of the "Bluetooth setup with Microsoft drivers" FAQ webpage.
Cannot re-connect to Bluetooth device after turning on (resuming) the Archer
When you shut off (suspend) the Archer Field PC, the Bluetooth also shuts off (unloads). When you turn on (resume) the Archer, it takes several seconds for the Bluetooth to also turn on (reload). If you leave a software program open while the Archer was off, you may need to disconnect and reconnect the Bluetooth device in the software, or exit and re-open the software before you can connect again. Safely exit software programs before suspending using the Application Manager program.
Bluetooth partnership with device has disappeared
When setting up the virtual COM port used by the Bluetooth device, if the "Secure Connection" checkbox is checked, then for security purposes the partnership with the Bluetooth device will be removed after the first connection has ended and must be re-created for each future connection.
To avoid having the Bluetooth partnership with a device be deleted after each connection, please uncheck the "Secure Connection" checkbox when setting up the virtual COM port as described in step 4 of the "Bluetooth Virtual COM Ports" section of the "Bluetooth setup with Microsoft drivers" FAQ webpage.
Allegro Field PC
Please follow the procedures for installing the Socket Bluetooth CF card adapter in the Allegro provided on our website at:
Bluetooth icon in System Tray has disappeared
Make sure the Bluetooth CF card adapter is firmly inserted in the Allegro.
Try removing the adapter for 10 seconds, and then re-insert.
Try resetting the system by tapping on Start > Programs > Utilities > Reset System.
Try restoring the saved system by tapping on Start > Programs > Utilities > Restore System.
Remove the battery and wall charger for 20 minutes.
Cannot re-connect to Bluetooth device after turning on (resuming) the Allegro
When you shut off (suspend) the Allegro Field PC, the Bluetooth also shuts off (unloads). When you turn on (resume) the Allegro, it takes several seconds for the Bluetooth to also turn on (reload). If you left a software program open while the Allegro was off, you may need to disconnect and reconnect the Bluetooth device in the software, or exit and re-open the software before you can connect again.
I can see the Bluetooth GPS receiver in the list of Bluetooth Receivers in Carlson SurvCE, but I cannot connect to it.
Try discovering and bonding to the Bluetooth GPS receiver outside of the Carlson SurvCE software, and uncheck the "This is a Bluetooth device" checkbox in COM Port Settings in SurvCE. Instructions for discovering and bonding outside of SurvCE can be found in the Bluetooth section of the Allegro CX Field PC manual, available on our website at:
It is recommended to update the Allegro CX Field PC to operating system release 1.06, which also contains the latest version 6.3.15.0 of the Socket Communications Bluetooth drivers. This OS update can be downloaded from our website at:
It is recommended to update to version 1.61.07 or higher of the Carlson SurvCE software, which is available at:
