|
|
 | | Re: Robolab, byte codes and assembler
|
| OK You do something great, and all the world is looking at it, finding the finest detail one could have made much better. That's the power of internet-exchange. Don't take this personally. I only wanted to remind the great job they did at LEGO's (...) (22 years ago, 27-Nov-03, to lugnet.robotics.rcx.robolab)
| | | | | Re: Robolab, byte codes and assembler
|
| (...) Please don't take my post as a criticism of the original firmware, I merely wanted to point out alternatives. I agree, the 3ms sample rate is more than adequate for most applications. (...) Yes, the RCX is rugged in many respects, but I think (...) (22 years ago, 27-Nov-03, to lugnet.robotics.rcx.robolab)
| | | | | Re: Robolab, byte codes and assembler
|
| (...) We should not forget that the RCX has initially been designed for kids. So the standard firmware should be considered according to the initial aims, which were to provide a really great tool - toy for children. Therefore the firmware designers (...) (22 years ago, 27-Nov-03, to lugnet.robotics.rcx.robolab)
| | | | | External Power Supply
|
| Hi ! I also have already used an external power supply for my RCX, which was a battery pack of 7 cells (8,4 V) with 2Ah each. It worked quite well but from one day to the another my RCX didn't word any more. I haven't found out jet, why my RCX (...) (22 years ago, 27-Nov-03, to lugnet.robotics)
| | | | | Re: Robolab, byte codes and assembler
|
| (...) By contrast, BrickOS continuously samples each sensor at a rate of about 6.7 samples per millisecond. This is 20 times more often than the standard firmware. It's no wonder it's more accurate at higher rotation rates. Of course, it also (...) (22 years ago, 27-Nov-03, to lugnet.robotics.rcx.robolab)
|
|
