|
|
 | | Re: Robolab, byte codes and assembler
|
| (...) It really is. I do think somebody made a mistake specific to the rotation sensor, though. I haven't decided yet whether it's the firmware, the sensor, or just the overall mechanism. I can understand how it got past quality control - sometimes (...) (21 years ago, 27-Nov-03, to lugnet.robotics.rcx.robolab)
| | | | | Re: Robolab, byte codes and assembler
|
| (...) Unfortunately, I fear the comparison is all too true! So, is my robot going to blow up? ;) (...) I'd appreciate some specifics. So far, I have not been able to find a way to do this in Robolab. I wrote some code to test raw sensor values and (...) (21 years ago, 27-Nov-03, to lugnet.robotics.rcx.robolab)
| | | | | Re: multiple motors
|
| (...) hmm. see rule #1: (URL) my BIGGEST piece of advice for your sumo robot: make SURE it does not leave the sumo area on it's own." :) Steve (21 years ago, 27-Nov-03, to lugnet.robotics.rcx)
| | | | | 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 (...) (21 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 (...) (21 years ago, 27-Nov-03, to lugnet.robotics.rcx.robolab)
|
|
