|
|
 | | Blue screen of death
|
| So, it took me a while, and I THINK, I MIGHT have solved the stupid rcx crash thing. My code has a wait until command. it is peppered throughout the code and it is a simple way for me to wait until BOTH the X and the Y are in position before i do a (...) (23 years ago, 14-Feb-02, to lugnet.org.ca.rtltoronto)
| | | | | Re: Robot - Accuracy
|
| (...) There's a reason why it's inaccurate at slow speed, and a fix (requires taking apart the sensor and some soldering!) here (URL) (23 years ago, 13-Feb-02, to lugnet.org.ca.rtltoronto)
| | | | | Re: Robot – Accuracy
|
| (...) ummm, magic?? :) -- Chris Pretend this says something funny (23 years ago, 13-Feb-02, to lugnet.org.ca.rtltoronto)
| | | | | Re: Robot Accuracy
|
| (...) increase. (...) That is the biggest problem I have. Even with my anti-external light shell (see here: (URL) I still need to adjust the value between day time and night time testing. (23 years ago, 13-Feb-02, to lugnet.org.ca.rtltoronto)
| | | | | Re: Robot – Accuracy
|
| (...) And what do you think keeps your code alive when you turn the RCX off? As for a stack problem, this would only happen when the RCX is executing your code. Whenever you download a program the memory is autmatically cleared. The stack idea is (...) (23 years ago, 13-Feb-02, to lugnet.org.ca.rtltoronto)
|
|
