 | | NXTRC: Using Bluetooth with NXT under Linux.
|
|
Hi, I wrote a program that allows to communicate with a NXT brick under Linux using a Bluetooth link. With this program you can upload and download programs run them and other stuff. You can find more info and get the source at (URL). Our site is (...) (19 years ago, 6-Apr-07, to lugnet.robotics.nxt, lugnet.robotics)
|
| |
| | Logging from NXT to PC via Bluetooth
|
|
I have been working for some time on an advanced NBC application that sends/logs data over Bluetooth from the NXT to a PC. The header for the file explains, in detail, how it works, so I'll just paste it here. It is compiled with a pre-released (...) (19 years ago, 6-Apr-07, to lugnet.robotics.nxt)
|
| |
| | Re: GCC vs. IAR compiler: Could GCC be tweaked to generate code as tight as IAR?
|
|
(...) I read a paper that attributed most of the code size increases in gcc generated code to the printf library - search for AN52-ARM-C-Benchmark.pdf to read the paper. Out of curiosity I built the firmware using the newlib libc and the gcc 4.1.1 (...) (19 years ago, 5-Apr-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | RE: Faster NXT LCD Screen Refresh
|
|
Change the init message for the LCD display driver to perform wrap around. Offset 12 in the following structure from 0x88 to 0x89. Otherwise it will keep overwriting the same line. Your code snippet doesn't show it, but I'm sure you kept the call (...) (19 years ago, 4-Apr-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | 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)) (...) (19 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 (...) (19 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 (19 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 (...) (19 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 (...) (19 years ago, 2-Apr-07, to lugnet.robotics.rcx)
|
| |
| | RE: IR Problems
|
|
RCX IR does not require direct line of sight. All sorts of reflections will work. Especially if you're in a "smallish" (bedroom, home office) room. The RCX firmware always has the IR turned off. "Wait for mail" and "send mail" is just a higher (...) (19 years ago, 2-Apr-07, to lugnet.robotics.rcx)
|
