 | | Re: Some comments (long)
|
|
(...) Assuming you use the ROM to receive things, which would be prudent in terms of space but not strictly necessary, the lengths of the opcodes in the message receiving code are determined by the lowest three bits of the opcode: 0 means length 0, (...) (28 years ago, 6-May-99, to lugnet.robotics)
|
| |
 | | Re: Some more comments and suggestions.
|
|
(...) That's a good pseudo-question. It would actually be quite easy to set up a focused group/list for this, as has been done for legOS, NQC, and pbFORTH; the viability is only dependent on the interest in having more room to breathe. Anything (...) (28 years ago, 6-May-99, to lugnet.robotics)
|
| |
 | | Removal of the LED in Light Sensors
|
|
There is a common operation on LEGO light sensors that involves removal of the LED. The belief is; If the LED is removed, then the sensor works better as an ambient light sensor. I have simulated the LEGO light sensor circuit with and without the (...) (28 years ago, 6-May-99, to lugnet.robotics)
|
| |
 | | FW: Some comments (long)
|
|
-----Original Message----- From: Ralph Hempel [mailto:rhempel@bmts.com] Sent: Thursday, May 06, 1999 3:25 PM To: John A. Tamplin Subject: RE: Some comments (long) (...) Hmmm, as I understand it, the A/D sampling takes place periodically during the (...) (28 years ago, 6-May-99, to lugnet.robotics)
|
| |
 | | Re: Some comments (long)
|
|
(...) Unfortunately, the ROM code (as I understand it) does not implement any mechanism other than polling. I would like to do things like block a thread until a sensor value matched some criteria. The only efficient way to do that is to have the (...) (28 years ago, 6-May-99, to lugnet.robotics)
|
| |
 | | Re: Lego Network Protocol questions
|
|
(...) I was under the impression you wanted to sync a clock to the rhythm of bit arrivals. You cannot do this. You can definitely sync a clock to the rhythm of byte arrivals. I was trying to point out this distinction to you. You must have been (...) (28 years ago, 6-May-99, to lugnet.robotics)
|
| |
 | | Re: LEGO light sensor schematic
|
|
(...) Sorry about that, I glued it back together with liquid plastic cement. I don't think it can take another operation and survive. I can't remember seeing a number inside and I was looking in there when you wedge the pc board in place. You might (...) (28 years ago, 6-May-99, to lugnet.robotics)
|
| |
 | | Re: Some comments (long) (was: Something else is needed, I think...)
|
|
Mark Tarrabain wrote in message <3730DE97.EFB3BF9A@l....bc.ca>... (...) It is probably true that a floating-point library cannot (should not?) be built into the firmware. It would probably be better for this to be supported by the compiler(s). But (...) (28 years ago, 6-May-99, to lugnet.robotics)
|
| |
 | | Re: Some comments (long)
|
|
(...) Could you explain what you mean by this, exactly? I would have figured that if a new interpreter is designed from scratch, the lengths of the opcodes could be hard-coded into the interpreter in some way. I was not suggesting that any existing (...) (28 years ago, 6-May-99, to lugnet.robotics)
|
| |
 | | Re: Some comments (long)
|
|
(...) Not that I disagree with the elegance of being able to define a class that implements a new way of reading a sensor; however, I thought I'd point out two issues you might want to consider: First, the ROM already contains a significant amount (...) (28 years ago, 6-May-99, to lugnet.robotics)
|