 | | 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 comments (long) (was: Something else is needed, I think...)
|
|
Some comments on what Chris Phillips wrote: - as far as I know, you will not be able to implement floating point in byte code, it will be too inefficient (mostly in terms of space) - agreed, current firmware does not support fixed point well, and it (...) (28 years ago, 6-May-99, to lugnet.robotics)
|
| |
 | | Re: Some comments (long)
|
|
(...) What is your point? If you want to make sense of the raw values, and want to leverage the ROM code to process the existing sensor types/modes, you need to call a ROM sensor-processing function every time an a/d completes. That was the point I (...) (28 years ago, 6-May-99, to lugnet.robotics)
|
| |
 | | Re: Lego Network Protocol questions
|
|
(...) That was someone else. I came in in the middle :-) (...) See above. (...) Will it be big enough to matter in the slotted protocol context? (...) No problem at all, I'd guess. Cheers, Ben. -- (URL) grandfather once told me that there are two (...) (28 years ago, 6-May-99, to lugnet.robotics)
|
| |
 | | Re: interest in JVM porting effort
|
|
(...) - I agree there will be two projects - if both projects get off the ground in the first place - Partly I disagree with your characterization of the other project; I do not think the goals are quite as stated. The other group wants to (I think) (...) (28 years ago, 6-May-99, to lugnet.robotics)
|