 | | Faster NXT LCD Screen Refresh
|
|
Here's a trick to get a faster rate on the LCD display refresh. It currently takes 16 milliseconds to refresh the NXT LCD. 16 "messages" are sent to the LCD. One message is sent per millisecond. There are two messages from the ARM to the LCD for (...) (18 years ago, 22-Mar-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | pbLua Beta 3 - Available
|
|
All, pbLua beta 3 is available now at: (URL) This new version has the bug in the regulation fixed, and the default motor mode is brake, not float. I've also updated the API docs to correct errors (there are probably more) and added an install doc (...) (18 years ago, 22-Mar-07, to lugnet.robotics.nxt, lugnet.robotics.nxt.nxthacking)
|
| |
| | Re: pbLua Fun at OSX
|
|
(...) Finally, I did something right - by accident! Christian, could I ask you to please send me (off list if you like) some screen shots of what happens when you connect the NXT? I can't remember if I sent you Mac instructions, but you just look (...) (18 years ago, 21-Mar-07, to lugnet.robotics.nxt)
|
| |
| | pbLua Fun at OSX
|
|
Hello World, pbLua-Beta2 is out and 90% of my wishes are true now :D Running pbLua with OSX worked out of the box... 1. Flashing NXT and reboot the box once 2. checking for new NXT-Device (ls -la /dev/tty.usb*) 3. connecting with screen to NXT (...) (18 years ago, 21-Mar-07, to lugnet.robotics.nxt)
|
| |
| | Re: The standard NXT firmware & the case of the missing opcodes
|
|
(...) I guess what I'm saying is '<<=', 'OP_ASL' and 'OP_LSL' are all the same thing (zero fill). '>>=' means either 'OP_ASR' (smear fill) or 'OP_LSR' (zero fill) depending on whether your target is signed or not. If you wanted direct equivalents (...) (18 years ago, 21-Mar-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | Re: The standard NXT firmware & the case of the missing opcodes
|
|
(...) Having used shifts in Z80 assembly before, I can see the uses of the different types. However, I can't see how I'd want anything other than arithmetical in the NBC opcodes. The only times I used logical, rotating, or with-carry-bit shifts was (...) (18 years ago, 21-Mar-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | Re: Adding syscalls/opcodes to NXT-G
|
|
(...) Can you flesh this out a bit? What do you have in mind when you say "create from it a new program clump"? The current version of the firmware limits the size of this buffer to 64 bytes. I increased that limit in my recent changes to be 800 (...) (18 years ago, 21-Mar-07, to lugnet.robotics.nxt)
|
| |
| | Adding syscalls/opcodes to NXT-G
|
|
One of the biggest problems with extending the current FW is that the NI compiler for NXT-G/NXTToolkit is not so flexible. In particular, one can't add new syscalls. Here's a suggestion I would be happy to hear your ideas on - the NXT-G compiler has (...) (18 years ago, 21-Mar-07, to lugnet.robotics.nxt)
|
| |
| | The standard NXT firmware & the case of the missing opcodes
|
|
There are several opcodes defined in c_cmd_bytecodes.h which are missing from the VM implementation in c_cmd.c Here are the ones that are not implemented: //Family: Bit manipulation #define OP_CMNT 0x0A // dest, src #define OP_LSL 0x0B // dest, src (...) (18 years ago, 21-Mar-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | new NXT mailinglist established
|
|
Hello! A new NXT mailinglist is established. Because there are no german mailinglists until now, this mailinglist is for german speaking (not necessary native) people around the world. You need an (free) yahoo account to participate! (URL) (18 years ago, 19-Mar-07, to lugnet.robotics.nxt)
|
| |
| | Re: Enhanced standard NXT firmware
|
|
... (...) Hi John, I just tried to load it and just tested the "Try-me" light sensor. It worked fine. Not so much help, but I can try some more another day. Good work. Rasmus (...) (18 years ago, 19-Mar-07, to lugnet.robotics.nxt.nxthacking, lugnet.robotics, lugnet.robotics.nxt)
|
| |
| | Battery Level NXT-G Block
|
|
I've posted a new NXT-G Block that reads the battery level from the UI module IOMAP. Can also be used as a sensor block to detect low power conditions. Details and download: (URL) Ziv NXTasy.org (18 years ago, 19-Mar-07, to lugnet.robotics.nxt)
|
| |
| | Last call for my New York City NXT Meet-Up
|
|
I have the LEGO MINDSTORMS NXT ROBOTICS SET and since I'm so "into it", my father and I were thinking we could start up a Lego MindStorms NXT Meet up group/club in New York City where we could meet once a month (or every other month), build, (...) (18 years ago, 18-Mar-07, to lugnet.robotics.nxt)
|
| |
| | Detecting stall and slip conditions in NXT-G
|
|
I published a new "sensor" NXT-G Block that monitors that actual power sent to the NXT servos. This is useful to detected both stall conditions as well as the move challenging slip conditions. Full description and download are here: (URL) Ziv (...) (18 years ago, 18-Mar-07, to lugnet.robotics.nxt)
|
| |
| | MinMax NXT-G Block
|
|
I've published a small NXT-G block that allows to find the minimal and maximal value of a varying input. Description and download are here: (URL) Ziv NXTasy.org (18 years ago, 18-Mar-07, to lugnet.robotics.nxt)
|
| |
| | Missing links?
|
|
Hi guys, Are there missing any links in the "stable" section (the one with the links to RobotC, pbLua NBC etc) to the left of the forum (most likely since I put them there...)? I don't know if all can edit it but otherwise you can probably write to (...) (18 years ago, 18-Mar-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | Re: Enhanced standard NXT firmware
|
|
(...) I would have liked to have one permanently, but it seems a little steep. Last summer I got a limited edition (32KB or something) along with the an AT91 evaluation board. (...) Perhaps Section 5.1 is useful: (URL) I just tried to post but it (...) (18 years ago, 17-Mar-07, to lugnet.robotics.nxt.nxthacking, lugnet.robotics, lugnet.robotics.nxt)
|
| |
| | Re: Enhanced standard NXT firmware
|
|
(...) It actually was not a very big deal. I was familiar with the firmware source code since I had looked at it quite a bit since it was released, trying to figure out how to get it to compile with GCC. All the RIC bug fixes were things I figured (...) (18 years ago, 17-Mar-07, to lugnet.robotics.nxt.nxthacking, lugnet.robotics, lugnet.robotics.nxt)
|
| |
| | Re: Enhanced standard NXT firmware
|
|
(...) <snipped description> Holy crap John! You've been really busy! For anyone poking around in this forum, I can say that what John has done is pretty significant. I have written my own firmware for the brick so I know how much work must have gone (...) (18 years ago, 17-Mar-07, to lugnet.robotics.nxt.nxthacking, lugnet.robotics, lugnet.robotics.nxt)
|
| |
| | Enhanced standard NXT firmware
|
|
Over the past couple days I have used the IAR Embedded Workbench to implement some enhancements and bug fixes for the standard NXT firmware. The bug fixes are as follows: 1. RIC drawing code incorrectly checked the size of the OP_LINE structure for (...) (18 years ago, 16-Mar-07, to lugnet.robotics.nxt.nxthacking, lugnet.robotics, lugnet.robotics.nxt)
|
