Symbol MC70 User Manual page 133

Troubleshooting Bluetooth Connection (Continued)
Table 6-2
Problem
Piconet (the The EDA suspends and
connection between a the Bluetooth radio power
Bluetooth master and turns off.
one or more
Bluetooth slaves) One of the devices are out
drops. of range.
My application Device went out of range or
created a successful was shut off.
RFCOMM session
with another
Bluetooth device but
the session was
dropped.
After completing an The Microsoft Bluetooth
RFCOMM session stack holds a baseband
with another connection for ten seconds
Bluetooth device, I after an application closes
was unable to create its session and exits. This
a virtual COM port to was designed to allow for
connect to another speedy connections to the
Bluetooth device. same device if other
profiles were to connect.
Cause
An application can register for notification of an EDA resume by
creating a message queue using the CreateMsgQueue() API
and power notifications using the RequestPowerNotifications()
API (refer to the SMDK Help File). After an application receives
a resume notification it should close open Bluetooth sessions
and reopen them.This reestablishes the piconet lost during the
suspend.
Check the return value of APIs for errors. Look for a DCD state
change event in the Microsoft Bluetooth stack DCD window of
the Bluetooth connection.
Either wait 10 seconds, choose a different COM port number for
the virtual COM port, or modify
HKLM\software\Microsoft\bluetooth\l2cap\IdlePhys (which
defines the number of seconds to hold the connection).
Maintenance & Troubleshooting
Solution
6 - 5