 | | 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: Programming for NXT
|
|
(...) Would it help to add a "Last Updated: mm/dd/yyyy" to this page? Thank you Andy (18 years ago, 13-Feb-07, to lugnet.robotics.nxt)
|
| |
| | 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: BricxCC release 3.3.7.16
|
|
(...) Agreed, even if you select NXT target BricxCC insists to use .nqc as default extension. Misleading at best... Philo (18 years ago, 13-Feb-07, to lugnet.robotics, lugnet.robotics.nxt)
|
| |
| | RE: Bluetooth Comm Problem
|
|
(...) A visual review looks like everything is appropriate. The only thing I can think of is whether, on the NXT, you are calling "ReadMessage" more than once. You should have a loop that runs for at least 50 (or better yet 150) milliseconds. (...) (18 years ago, 13-Feb-07, to lugnet.robotics.nxt)
|
