 | | Deriving power from NXT® motor port A
|
|
This (URL) special cable> allows you to power external devices such as a a motor multiplexer or a wireless camera from your NXT. No need for external bulky battery box! (if your current consumption is low enough, 800mA max). Though plugged into NXT (...) (18 years ago, 25-Apr-07, to lugnet.robotics.nxt.nxthacking, FTX)
|
| |
| | Re: Using NXT Port 4 EIA-485
|
|
(...) Hi Juergen, Yes, I found this night the entries at Lego-Source-Code... and no line about P-NET-Protocol... My first thought was to implement a simple p-net-node at own MCU, but now I can try my own communication from NXT (master) to external (...) (18 years ago, 10-Apr-07, to lugnet.robotics.nxt, lugnet.robotics.nxt.nxthacking)
|
| |
| | Re: Using NXT Port 4 EIA-485
|
|
Hi Christian, (...) the RS-485 interface is directly connected to the AT91SAM7S USART, so you can choose the bit rate quite freely. (...) No, it is not necessary, P-Net is just a field bus which seems to be popular in Denmark, there are others which (...) (18 years ago, 10-Apr-07, to lugnet.robotics.nxt, lugnet.robotics.nxt.nxthacking)
|
| |
| | Re: Using NXT Port 4 EIA-485
|
|
(...) Hi, halfduplex is not the problem when connecting the NXT to an external MCU. My problem is the bitrate of 921,6 kbits/s. Simple cheap MCU like ATMega didn't support this bitrate (as far as I know). To add an external devices (e.g MCU+SD-Card (...) (18 years ago, 9-Apr-07, to lugnet.robotics.nxt, lugnet.robotics.nxt.nxthacking)
|
| |
| | RE: Using NXT Port 4 EIA-485
|
|
I've looked at implementing an interface for RobotC, but I've always struggled with why bother since there are no applications that connect to it. I wish LEGO had implemented an option to provide a logic level "RS-232" UART on port four. Yes, I (...) (18 years ago, 8-Apr-07, to lugnet.robotics.nxt, lugnet.robotics.nxt.nxthacking)
|
| |
| | 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 (...) (18 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 (...) (18 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)) (...) (18 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 (...) (18 years ago, 4-Apr-07, to lugnet.robotics.nxt, lugnet.robotics.nxt.nxthacking)
|
| |
| | 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 (...) (18 years ago, 2-Apr-07, to lugnet.robotics.nxt.nxthacking)
|
