 | | Re: pbLua Hardware access
|
|
(...) There are no hidden commands, but if it's ABSOLUTELY necessary I can add peek and poke for bytes, words and longs. This may be more dangerous than it's worth :-) What hardware do you need access to? Ralph (17 years ago, 19-May-07, to lugnet.robotics.nxt, lugnet.robotics.nxt.nxthacking)
|
| |
| | Re: pbLua PCF8574
|
|
(...) No ideas yet, Christian. I do have a Mindsensors kit here to look at over the weekend. Are you SURE you are sending the correct string to read the registers? Can you post the code you're using for the test here? Cheers, Ralph (17 years ago, 19-May-07, to lugnet.robotics.nxt, lugnet.robotics.nxt.nxthacking)
|
| |
| | pbLua Hardware access
|
|
Hi, is there a way to access the NXT-hardware directly with pbLua ? Are there any hidden commands to allow this ? Any idea ? Thanks in advance Bye Christian (17 years ago, 18-May-07, to lugnet.robotics.nxt, lugnet.robotics.nxt.nxthacking)
|
| |
| | pbLua PCF8574
|
|
Hi, has anybody successfully tried to read ports from I2C connected PCF8574 with pbLua (Beta-8) ? Writing and setting ports is no problem, but reading ports fails. The return value is every times 0 (not NIL) Any idea ? Thanks in advance Bye (...) (17 years ago, 18-May-07, to lugnet.robotics.nxt, lugnet.robotics.nxt.nxthacking)
|
| |
| | Re: Building and downloading NXT firmware
|
|
(...) Thanks for trying: You need just to look at the NXTGCC project. You should probably be able to start by reading nxt.pdf at (URL) then install either the winarm or (URL) toolchains. Finally download the zip file from (URL) see if you can (...) (17 years ago, 14-May-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | Building and downloading NXT firmware
|
|
Hello Hackers, That's my first post to this group so I would like to introduce myself shortly: I'm a 34 year old german who has studied computer science some years ago. Being on the job for a few years I decided to go back to the university to get a (...) (17 years ago, 11-May-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | 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 (...) (17 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 (...) (17 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 (...) (17 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 (...) (17 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 (...) (17 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 (...) (17 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 (...) (17 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)) (...) (17 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 (...) (17 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 (...) (17 years ago, 2-Apr-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | Re: Enhanced standard NXT firmware
|
|
(...) That's great news, David. I'm glad that you are having success using the new CommExecuteFunction system call. I haven't had a chance to test it at all yet personally but I was very confident that it would just work seeing as how exposing it (...) (17 years ago, 28-Mar-07, to lugnet.robotics.nxt.nxthacking, lugnet.robotics, lugnet.robotics.nxt)
|
| |
| | Re: Enhanced standard NXT firmware
|
|
"John Hansen" <afanofosc@comcast.net> wrote in message news:JF0sGr.M2w@lugnet.com... (...) implement (...) big snip Great job John. And thank you especially for CommExecuteFunction. I couldn't believe that Lego didn't allow a way to make a Bluetooth (...) (17 years ago, 28-Mar-07, to lugnet.robotics.nxt.nxthacking, lugnet.robotics, lugnet.robotics.nxt)
|
| |
| | More firmware enhancements
|
|
I have implemented OP_WAIT and a variant of OP_WAIT which takes a variable rather than an immediate numeric value (which in nbc is called "waitv"). I also modified NBC to accept a command line switch that tells it whether the firmware supports waits (...) (17 years ago, 22-Mar-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | Re: Faster NXT LCD Screen Refresh
|
|
(...) Okay, there's a little more to it than this. If you have a display that supports greyscales, it can control the level of the voltage jolt that's applied to each pixel during the actual refresh cycle. That way you get a smoother display with (...) (17 years ago, 22-Mar-07, to lugnet.robotics.nxt.nxthacking, FTX)
|
