 | | 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)
|
