 | | Re: Faster NXT LCD Screen Refresh
|
|
(...) Could you be a little more specific regarding the changes you made to this method: UBYTE DisplayUpdate(UWORD Height,UWORD Width,UBYTE *pImage) { static UWORD State = 0; static UWORD Line; if (State == 0) { if (DisplayWrite(CMD,(U...itString)) (...) (20 years ago, 4-Apr-07, to lugnet.robotics.nxt.nxthacking)
|
| |
 | | NXT Bluetooth Message Performance
|
|
Any have any experience with communicating over Bluetooth with 'master' connected to more than one NXT? If so, can you share any performance results? My guess is that it is very slow. My expectation is that when there is one master NXT and two slave (...) (20 years ago, 4-Apr-07, to lugnet.robotics.nxt, lugnet.robotics.nxt.nxthacking)
|
| |
 | | Re: IR Problems
|
|
Hi Tom, I tried to send you a private mail, but the email address I have doesn't work anymore. Could you give me the new one? -Claude (20 years ago, 3-Apr-07, to lugnet.robotics.rcx)
|
| |
 | | NXT-to-NXT Messaging
|
|
The following is a good topic for this list. It deals with NXT-to-NXT messaging. It's based on an original post in the "nxtasy" forums. There's lots of room for improvement / enhancement in the NXT-to-NXT messaging. Especially when more that two (...) (20 years ago, 2-Apr-07, to lugnet.robotics.nxt.nxthacking)
|
| |
 | | RE: IR Problems
|
|
Elizabeth is quite right. It's easy to get collisions on the IR "bus" if two devices are sending (or replying) simultaneously. What I've done in the past with two RCXs is define one RCX as primary that is periodically (every 100 to 250 milliseconds (...) (20 years ago, 2-Apr-07, to lugnet.robotics.rcx)
|