 | | RCX display
|
|
Hi, I suppose it must have been done before, because it is so obvious, but I can't seem to be able to find information about it on the web. Can anybody tell me how to access the RCX display directly, that is, for example, display numbers or such? A (...) (24 years ago, 26-Jan-01, to lugnet.robotics.rcx)
|
| |
| | Re: legOS lcd management and thoughts on velocities
|
|
(...) Yes, I have written that support. First you have to enable it, by removing the comments from the line in legOS/boot/config.h. Then recompile the kernel and all apps. After you have programmed the rotation sensor in the usual way you can read (...) (24 years ago, 26-Jan-01, to lugnet.robotics.rcx.legos)
|
| |
| | Visual NQC 2001 Beta 2
|
|
To all testers, Runtime error 380 stands for invalid property. This can happen when you try to compile a program in the editor. I had the error ones during development but it didn't come up anymore. Next week I'm starting bugfixing again and see if (...) (24 years ago, 26-Jan-01, to lugnet.robotics.rcx.nqc)
|
| |
| | How many motors can accept a RCX ?
|
|
Hi, everybody <DISCLAIMER> Excuse me first for my newbieness here on Lugnet. and also for my frenchieness, but it's not my fault ! </DISCLAIMER> I have a question I'd like to submit: Because of extreme needs of power/ acceleration (it was about (...) (24 years ago, 26-Jan-01, to lugnet.robotics.rcx)
|
| |
| | RE: Confusion regarding the POWER_OFF command.
|
|
(...) I was too. It's a bit goofy, so I'll try to explain as I go... (...) That's fine - the only thning you need to do (I think - I'm away from my RCX) is to put POWER_INIT just before POWER_OFF. The POWER_INIT word initializes the interrupt (...) (24 years ago, 25-Jan-01, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: Visual NQC 2001
|
|
I have downloaded and installed Beta 2. I am having a problem that I had with beta 1. When I "Compile" I get a "Runtime Error '380' Invalid Property Value". Am I alone in this problem? If so, what does it mean? Is something missing from my Win98? -- (...) (24 years ago, 25-Jan-01, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: sleep efficientcy
|
|
(...) value (...) There are two issues: 1 do you want to do anything while waiting, 2 how quick do you want to respond to the event. In both cases using an event is better. You can do something else until the event happens (synchronization issuses (...) (24 years ago, 25-Jan-01, to lugnet.robotics.rcx.legos)
|
| |
| | Visual NQC 2001
|
|
I've fixed a lot of problems thanks to your testing and reporting. Beta relase 2 is now available on (URL) (24 years ago, 25-Jan-01, to lugnet.robotics.rcx.nqc)
|
| |
| | Confusion regarding the POWER_OFF command.
|
|
I'm a little confused with the POWER_OFF word. From reading the documentation, I would have though the following would work: POWER_INIT : test BEGIN DO-WORK POWER_OFF 0 UNTIL ; When 'test' is executed, both 'DO-WORK' and 'POWER_OFF' are executed, (...) (24 years ago, 25-Jan-01, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: sleep efficientcy
|
|
(...) value (...) Ross, I can't speak about efficiency - I dont know enogh about embedded programming, but I've had better results using wait_event. I've tried both msleep() and yield() in a loop, and just calling wait_event with a function that (...) (24 years ago, 25-Jan-01, to lugnet.robotics.rcx.legos)
|
