 | | Re: Bluetooth Comm Problem
|
|
(...) I was a little confused about how I was supposed to determine when the message had been received. I wasn't sure whether the ReceiveMessage should be called multiple times or not. Here is my code: // Connection = 1, Queue = 0 (...) (18 years ago, 13-Feb-07, to lugnet.robotics.nxt)
|
| |
| | RE: Bluetooth Comm Problem
|
|
The NXT-G firmware implementation for mailbox messaging is extremely funky. I don't think your code is working properly for this implementation. You need to be continuously calling "ReadMessage" and only check for "a message was found" error code. (...) (18 years ago, 14-Feb-07, to lugnet.robotics.nxt)
|
| |
| | Re: Bluetooth Comm Problem
|
|
Dick, Thanks for the research and all of the valuable information! It's Valentine's Day, so my wife won't allow me the time to try it tonight, but I'll try your suggestions tomorrow and see how it works. By the way, I actually saw a response come (...) (18 years ago, 15-Feb-07, to lugnet.robotics.nxt)
|
| |
| | Re: Bluetooth Comm Problem
|
|
Dick, Thanks! I tried it out tonight and got consistent messages from the PC. You were correct about having to continually do message reads until I get something. I didn't have to do the wait for a second STAT_COMM_PENDING (32) or the 200 ms wait. I (...) (18 years ago, 16-Feb-07, to lugnet.robotics.nxt)
|
| |
| | Re: Bluetooth Comm Problem
|
|
(...) Dick and David, Thanks for posting this conversation here. Even though I'm not participating directly, I am reading it and as I'm touching up the Bluetooth support for pbLua right now, this has given me invaluable insight into how the (...) (18 years ago, 16-Feb-07, to lugnet.robotics.nxt)
|
| |
| | Re: Bluetooth Comm Problem
|
|
Glad we could help Ralph. And I'm sure there will be many great discussions in here as there already have been. (18 years ago, 17-Feb-07, to lugnet.robotics.nxt)
|
