What is causing the problems?
In my experience, I have found that in almost all cases the Bluetooth problems were initiated by teams having the FCS application running at the same time as LabVIEW/Robot C. Teams that were careful to close their programming environment before launching the FCS and vice versa generally avoided the Bluetooth problems.
If you need to quickly alternate between LabVIEW and the FCS, one technique that some teams have used is to ONLY connect over USB through LabVIEW, leaving the Bluetooth connection free for the FCS.
How do I recover from this problem?
If you are experiencing BT connections problems, I have found that the best way to recover is to:
1. Close LabVIEW/RobotC and the FCS.
2. Open Windows' Bluetooth Devices from Control Panel or the Systray in the bottom right of your screen.
3. Remove the NXT from the Devices list and close Bluetooth Devices.
4. Turn off the NXT.
5. Remove the BT dongle if it is an external adapter.
6. Plug the BT dongle back in.
7. Turn on the NXT.
8. Launch the FCS, LabVIEW or RobotC (whichever you want to use) and attempt to reconnect.
This works 90% of the time. If it does not work for you, you should reboot the computer as well.
Good luck!
Tony
