 | | LegOS HOWTO
|
|
Considering the recent discussion on this list, I figure this is as good a time as any to point out that my LegOS HOWTO is now posted at (URL) don't be intimidated! I have aimed this page squarely at anyone with a bare minimum of C or C++ (...) (28 years ago, 3-May-99, to lugnet.robotics)
|
| |
 | | Re: Something else is needed, I think...
|
|
(...) I agree on this point. I've been forced to move to legOS not by intrinsic NQC limitations but by those imposed by the RCX firmware. I still prefer to use RcxCC/NQC when I don't need legOS: programs load much faster, it's a pleasant and (...) (28 years ago, 3-May-99, to lugnet.robotics)
|
| |
 | | Re: Something else is needed, I think...
|
|
(...) I don't know if you guys realize this but if anything like this is ever done we must definitely remain compatible (at least partially) with Spirit.ocx protocols. The Spirit.ocx control is a HUGE bonus we must not throw away!! It makes possible (...) (28 years ago, 3-May-99, to lugnet.robotics)
|
| |
 | | Re: Something else is needed, I think...
|
|
(...) we must definitely remain compatible (at least partially) with Spirit.ocx protocols. (...) outside world with endless possibilities, and processing power that it will never be able to match! (...) already been done for us. And please, do not (...) (28 years ago, 3-May-99, to lugnet.robotics)
|
| |
 | | Re: LEGO light sensor schematic
|
|
(...) Ah... much better, I figured one or two components were backwards. Just to clean up the schematic a bit you could flip R1 (75R) to the right side of the Q4. I would also bring R8 (12R) in line with the LED. This would then be a more standard (...) (28 years ago, 3-May-99, to lugnet.robotics)
|
| |
 | | Re: LEGO light sensor schematic
|
|
(...) OK, I fixed that and in the process discovered they should be PNPs. 3Hp83 is a BC857 GP PNP from Philips. Looks better now. (...) I think photo diode used in photovoltaic mode. It looks like it pushes the voltage down from that established by (...) (28 years ago, 3-May-99, to lugnet.robotics)
|
| |
 | | Re: Something else is needed, I think...(long)
|
|
In article <000101be94cb$a8fd58...a@pro150>, Ralph Hempel <rhempel@bmts.com> writes (...) My QBasic program available from www.phesk.demon.co.uk/lego/ can download the Lego firmware from DOS - where can I find your new firmware to test it with, (...) (28 years ago, 3-May-99, to lugnet.robotics)
|
| |
 | | Re: Something else is needed, I think...
|
|
(...) I am not sure how much you can extend the capabilities of the firmware while maintaining its basic dispatch loop. There are some very basic design constraints that would be difficult to change without redoing all of the firmware. If you (...) (28 years ago, 3-May-99, to lugnet.robotics)
|
| |
 | | Re: Something else is needed, I think...
|
|
(...) If you believe you have good ideas for a language, my opinion is that you should propose something to the list, find people who want to work with you on this (assuming you don't want to work alone), ignore the people who say you know nothing (...) (28 years ago, 3-May-99, to lugnet.robotics)
|
| |
 | | Re: Something else is needed, I think...
|
|
I think that a good solution would be to have Legos work as a true operating system that stayed loaded in the brick and would accept downloading compiled programs for it to run. Maybe the firmware replacement idea that has been tossed around could (...) (28 years ago, 3-May-99, to lugnet.robotics)
|
| |
 | | Re: Something else is needed, I think...
|
|
(...) I think new firmware is a good way to go. I would vote for a completely new byte code, perhaps similar in spirit to the original, but designed fresh from the ground up. There is no source for the current firmware, although there is pseudocode (...) (28 years ago, 3-May-99, to lugnet.robotics)
|
| |
 | | Re: Something else is needed, I think...
|
|
(...) If you really want to design a new bytecode that is completely flexible, I suggest using the millions of manhours put into the Java Virtual Machine would be worthwhile. I looked at the idea of porting JVM to the RCX briefly before, but decided (...) (28 years ago, 3-May-99, to lugnet.robotics)
|
| |
 | | RE: Something else is needed, I think...
|
|
(...) If we are going to the trouble of new bytecode, then we need a new compiler. If we design a new compiler, then what language will it be? Yes, we could use C as the base and compile to pcode which is essentially what NQC does if I'm not (...) (28 years ago, 3-May-99, to lugnet.robotics)
|
| |
 | | Re: LEGO light sensor schematic
|
|
(...) [snip] I'm happy to see that some of my concerns have been born out with these changes, it looks more like a happy little circuit now. (...) Are we sure that the photodiode is located in the schematic correctly? It doesn't look like its biased (...) (28 years ago, 3-May-99, to lugnet.robotics)
|
| |
 | | Re: Something else is needed, I think...
|
|
(...) My thoughts on the JVM: - too complicated for what we need or want - no direct support for interfacing with the RCX I envision the new byte code being specific to the RCX, and as simple as possible to get the job done, which is the exact (...) (28 years ago, 3-May-99, to lugnet.robotics)
|
| |
 | | Re: Something else is needed, I think...
|
|
(...) C may be the best choice for a base language to start with simply because its well known. Quite frankly, if the bytecode is written reasonably well, different compilers for different base languages should be very feasible - compilers based on (...) (28 years ago, 3-May-99, to lugnet.robotics)
|
| |
 | | Re: Something else is needed, I think...
|
|
(...) I agree, that would make pbForth much more appealing if the source could be compiled on a pc in a nice gui environment and then the bytecode loaded into the rcx. Not only could someone enhance the gui front end as Mark has suggested, but (...) (28 years ago, 3-May-99, to lugnet.robotics)
|
| |
 | | Re: Something else is needed, I think...
|
|
(...) I guess that depends on who you talk to. Personally, I want an object oriented language with multithreading support. I want to be able to write generic code that can be reused in multiple applications (ie, here is a module that follows a line, (...) (28 years ago, 3-May-99, to lugnet.robotics)
|
| |
 | | RE: Something else is needed, I think...
|
|
(...) Do NOT underestimate the amount of work we are talking about. I took a working version of hFORTH for the PC and ported a few machine specific definitions and rewrote the IO drivers and debugged and tested using GNU tools, and I have 80 hours (...) (28 years ago, 3-May-99, to lugnet.robotics)
|
| |
 | | RE: Something else is needed, I think...
|
|
(...) Once you get around the idea that the RCX does the compiling which makes it platform independent, you will see the light... (...) This is a good plan. You have my full support :-) Cheers, Ralph Hempel - P.Eng ---...--- Check out pbFORTH for (...) (28 years ago, 3-May-99, to lugnet.robotics)
|