 | | Re: RCX Tower Internals
|
|
(...) Mine is like this too, I think. See (URL) compare to see if they look similarly. For me at least, the emitters and detector are slightly above the "clear" section. (...) For me at least, there is no way the components can line up with the (...) (27 years ago, 8-Jun-99, to lugnet.robotics.rcx)
|
| |
| | RCX Tower Internals
|
|
Hi All. I've just had some wierdness with my tower and decided to open it up to see what's inside. My basic issue is that the two emitters and the detector are not lined up (even close) with the "Clear" lens section on the front of the tower. Is (...) (27 years ago, 7-Jun-99, to lugnet.robotics.rcx)
|
| |
| | RE: Floating point support for 1142 bytes
|
|
(...) Let's face it Kekoa, you just couldn't stand not REALLY knowing what the group was talking about so you went and did the work we should have done before the discussion even started. :-) (...) (URL) That's a bit easier to deal with. Way to go. (...) (27 years ago, 28-May-99, to lugnet.robotics, lugnet.robotics.rcx)
|
| |
| | Floating point support for 1142 bytes
|
|
Following some discussion about the topic a few weeks ago, I was sufficiently curious and motivated enough to write a floating point library for the H8/RCX. Initially I thought I'd implement a non-IEEE floating point format optimized for the RCX, (...) (27 years ago, 27-May-99, to lugnet.robotics, lugnet.robotics.rcx)
|
| |
| | JVM port status
|
|
The first phase of the JVM port to the RCX is complete (translating the existing 68HC11 code into C++). We are now testing that to make sure the port did not introduce bugs. The next steps (in parallel) are to finalize the RCX-specific classes and (...) (27 years ago, 21-May-99, to lugnet.robotics.rcx)
|
| |
| | differences between 9719 and 9747?
|
|
What are the exact differences between Mindstorm pack 9719 and 9747 ? -- ***...*** Stefan Prescher prescher@hermes.fho-emden.de (27 years ago, 16-May-99, to lugnet.robotics.rcx)
|
| |
| | RCX JVM port status
|
|
I have created a web page for the RCX JVM port. It contains a brief description of the project, who is working on it, the task decomposition, and the status of those tasks. If anyone is interested in working on the project, please send me email. The (...) (27 years ago, 11-May-99, to lugnet.robotics.rcx)
|
| |
| | Re: Some goals, ideas, etc. for a new bytecode interpreter (long)
|
|
(...) Single-stepping through instructions would be a mode offered by the interpreter, and wouldn't require any breakpoints to be set. I suppose what the debugging information could contain is, instead of a list of valid breakpoints, a list of (...) (27 years ago, 10-May-99, to lugnet.robotics.rcx)
|
| |
| | Re: Some goals, ideas, etc. for a new bytecode interpreter (long)
|
|
(...) You have 4 7-segment characters which could display a 4 character text string (albeit with some of the characters being different case and some confusion between characters). (...) Adding limited functions to check the memory usage without (...) (27 years ago, 10-May-99, to lugnet.robotics.rcx)
|
| |
| | Re: Some goals, ideas, etc. for a new bytecode interpreter (long)
|
|
(...) Sure, but that's what zero padding is for. Since the opcode is IR-only, you don't care too much about length. The only length restriction comes from the second digit of the opcode, assuming you're using the ROM to receive incoming IR data. (...) (27 years ago, 10-May-99, to lugnet.robotics.rcx)
|
