 | | Re: About firmwares
|
| (...) Well, LejOS is Java-based and Java is an interpreted language - so that will presumably make it slower than a natively programmed machine-code/C system like LegOS. I've never used LejOS - but I can certainly confirm that LegOS is *HUGELY* (...) (23 years ago, 20-Oct-01, to lugnet.robotics)
| | | | | Re: About firmwares
|
| (...) Lejos is somewhere in the middle. Whether that is fast enough depends on your project, if it needs reaction times in the 100ms range no problem, at 10-20ms it gets really tough (sensors are read every 3ms). It also has has a clock with 1ms (...) (23 years ago, 20-Oct-01, to lugnet.robotics)
| | | | | Re: About firmwares
|
| (...) That's what I'd expect. (...) Yes - I doubt that you really *need* all that performance on something like a Lego robot - particularly given the relatively limited amount of memory in the beast. (...) Just to clarify: NQC isn't "firmware" - it (...) (23 years ago, 20-Oct-01, to lugnet.robotics)
| | | | | Re: About firmwares
|
| (...) Yes, it's easier to use than Lejos, no doubt about it. (...) I think it's "not quite" in the control structures but "very little" in the data structures. (...) It's not that hard to replace the firmware, and with the Lejos firmware you get a (...) (23 years ago, 21-Oct-01, to lugnet.robotics)
| | | | | Re: About firmwares
|
| (...) Yes...and no...the control structures (which include parallelism) are somewhat more than C has in *some* ways - but you are certainly right about data structures - which are limited to 16 bit integers and (with version 2.x firmware) small (...) (23 years ago, 22-Oct-01, to lugnet.robotics)
| | | | | Re: About firmwares
|
| (...) Yes. (...) Yes, I did that too. (...) I'd make that Lejos, and LegOS only if I need that last bit of performance, and I have a lot of time for programming. Jürgen (23 years ago, 23-Oct-01, to lugnet.robotics)
| |
