View Single Post
  #4   Spotlight this post!  
Unread 23-10-2008, 13:35
jbbjjbt jbbjjbt is offline
VRC Coach
AKA: Jon T
VRC #0177 (Twisted Botz)
Team Role: Coach
 
Join Date: Feb 2006
Rookie Year: 2004
Location: Gloucester, VA
Posts: 110
jbbjjbt is an unknown quantity at this point
Re: [FTC]: Bluetooth/NXT issues

Here's some information from the Carnegie Mellon - Robotics Academy
forum answering someone else's problem but may be applicable here.

http://www.education.rec.ri.cmu.edu/....php?f=33&t=68

Quote:

I've been worrying, frankly, that the combination of the complexity of the hardware/software setup and the propensity of some parts of it, especially the Bluetooth wireless connection, to fail, would be too frustrating, especially to teams with little or no experience.

So, first of all, you aren't the only ones having a lot of trouble. The only way to get things working and keep them working is to learn a systematic approach to troubleshooting. The number and amount of things which tend to go wrong is always greater than you'd guess, and will get suplemented by human error to the degree that you lose patience/get annoyed.

This is going to sound like a tremendously fatuous thing to say, but this difficult, failure-prone system is a wonderful opportunity to learn about real project process. I've found it to be significantly more similar to the real-world robotic projects I've worked on than other educational robotics problems.

So: what is a systematic approach to troubleshooting?
1. Stay calm. The goal isn't to get things working, it's to learn. Problems are an opportunity to learn.
2. Troubleshooting depends on locating where the problem is. Fixing the problem is usually easy. The problem is figuring out what, and especially where, the problem is.
3. So: keep trading things out until you can find the source of the problem.

In your case, specifically, I'd try.

1. Reload the LabVIEW firmware onto the NXT. This has the effect of giving you a fresh start. I think the NXT with LabVIEW tends to lose Bluetooth functionality with time, somehow, though this has not been confirmed by National Instruments. In any case, I've reloaded the firmware a total of a dozen times.
2. Once you've reloaded the firmware, try the autonomous program again. It should work. If it doesn't try another NXT, or take the batteries out of the only one you have and put them back again.
3. Connect the NXT to the computer via USB, and then try to connect to the Controller station. If you can connect, close the station, take away the USB, open the station and try to connect via Bluetooth, making sure you follow the instructions exactly.

I find it interesting that we are using a "difficult, failure-prone system" and that "The goal isn't to get things working, it's to learn. Problems are an opportunity to learn."

Any comments???
__________________
Jon Thompson
Coach
VRC 177 Twisted Botz
Sponsored by FRC 122
NASA Knights
Reply With Quote