| | Re: fast firmware downloader
|
|
(...) I'm willing to cover the DOS port since I'm working on a DOS->RCX comm project already. I already have my HP LX200 doing minimal comm with the RCX with hopes of having it ride alongside as a computational component. -Wes Matchett (25 years ago, 28-Oct-99, to lugnet.robotics.rcx.legos, lugnet.robotics.rcx, lugnet.robotics.rcx.pbforth)
|
|
| | Re: fast firmware downloader
|
|
(...) I'll start by pulling the 4x code into the NQC source base. That should make it trivial to build a stand-alone command line based downloader for Win32 (95/nt/98), Linux, Solaris, and Mac 68k/ppc under MPW. We could also get Win3.1 and DOS (...) (25 years ago, 28-Oct-99, to lugnet.robotics.rcx.legos, lugnet.robotics.rcx, lugnet.robotics.rcx.pbforth)
|
|
| | Re: legOS limitation
|
|
Hi Colin, (...) The one task per priority level requirement is gone at least since March. There is a priority chain mechanism now, with round-robin scheduling within a priority level. (...) Yes, a task won't die while higher-priority tasks are (...) (25 years ago, 27-Oct-99, to lugnet.robotics.rcx.legos)
|
|
| | Re: IR questinos and more
|
|
Hi Sergey, (...) if you intend only to transmit, you may just disable receiving altogether. (...) for an axle. yes, angle=rotation. (...) using the rotation sensor. otherwise, slippage may occur. night, markus. (25 years ago, 27-Oct-99, to lugnet.robotics.rcx.legos)
|
|
| | Re: LegOS 0.2.0a multi-threading problem
|
|
(...) I'd say this is the way to leave it, since it seems to be how you meant it in the first place. It's just very annoying to take out the batteries if ON/OFF is pressed by mistake while something is running. (...) Don't know, I've never used (...) (25 years ago, 27-Oct-99, to lugnet.robotics.rcx.legos)
|
|
| | legOS limitation
|
|
Hey, this is a small but frustrating one. This is in legOS 1.7 but I beleive it will still be in 2.0 as it's caused by the 1 priority to a task requirement. If you write code like the following: while(1){ wait(for something); kill(t1); t1 = (...) (25 years ago, 27-Oct-99, to lugnet.robotics.rcx.legos)
|
|
| | Re: LegOS 0.2.0a multi-threading problem
|
|
(...) If ON/OFF is desired while programs run, just drop the if. If ON/OFF isn't to work while programs run, it has to be this: if(nb_tasks<=3) { killall(PRIO_HIGHEST); return 0; // killall doesn't kill self } break; What does standard firmware do? (...) (25 years ago, 27-Oct-99, to lugnet.robotics.rcx.legos)
|
|
| | Re: LegOS 0.2.0a multi-threading problem
|
|
(...) Following up to myself, but here's the error (kernel/program/.c) lines 255-260: case KEY_ONOFF: // works only if no programs are running. if(nb_tasks<=3) { killall(PRIO_HIGHEST); } return 0; ^^^^ This should be 'break'. The way the code is (...) (25 years ago, 27-Oct-99, to lugnet.robotics.rcx.legos)
|
|
| | IR questinos and more
|
|
Hi All. I'm trying to build an IR proximity sensor with LegOS, by using the on-board transmitter and light sensor. I'm having problems figuring out how to send data, however. I tried using lnp_logical_write(), but 'cu -l /dev/ttyS0' doesn't show any (...) (25 years ago, 27-Oct-99, to lugnet.robotics.rcx.legos)
|
|
| | Re: LegOS 0.2.0a multi-threading problem
|
|
(...) That would be nice, actually. I have only one problem with stability - every once in a while, the "Run" key stops working, and all the other keys as well (don't remember exactly, but I think that's how it is). The program keeps running (...) (25 years ago, 27-Oct-99, to lugnet.robotics.rcx.legos)
|