 | | Re: Faster NXT LCD Screen Refresh
|
|
(...) So that is how you did it. I was wondering about this ever since I saw the announcement. Incidentally, this would have been great cross posted to .color as well. <</robotics/nxt/?n=539>> Doug (17 years ago, 22-Mar-07, to lugnet.robotics.nxt.nxthacking, FTX)
|
| |
| | Re: Faster NXT LCD Screen Refresh
|
|
(...) This kind of works. In the first instance, you get two identical shades of grey. In the second instance (and I've tried this) you'd be surprised to see that the difference in shades between the two greys is actually very small. You really need (...) (17 years ago, 22-Mar-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | Re: Faster NXT LCD Screen Refresh
|
|
(...) I already got one shade of grey out of it by flicking between two images at the current rate: (URL) I use all those spare cycles to mix and merge screen layers in real time, so this image has full parallax scrolling. I've been trying to do (...) (17 years ago, 22-Mar-07, to lugnet.robotics.nxt.nxthacking, FTX)
|
| |
| | Re: Faster NXT LCD Screen Refresh
|
|
(...) <snip> (...) This is really interesting. If I understand correctly, to get colors, or at least shades of grey, you have to refresh the screen quickly and the "darker" the pixel, the more often it shows up in the pattern. For example, let's say (...) (17 years ago, 22-Mar-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | 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 (...) (17 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 (...) (17 years ago, 22-Mar-07, to lugnet.robotics.nxt, lugnet.robotics.nxt.nxthacking)
|
| |
| | 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 (...) (17 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 (...) (17 years ago, 21-Mar-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | 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 (...) (17 years ago, 21-Mar-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | 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 (...) (17 years ago, 19-Mar-07, to lugnet.robotics.nxt.nxthacking, lugnet.robotics, lugnet.robotics.nxt)
|
