 | | Re: What should you do with a stuck motor?
|
|
Citando Steve Hassenplug <Steve@TeamHassenplug.org>: On Wed, June 29, 2005 4:19 pm, Jordan Bradford said: > Last night I had a new-style 9V motor attached directly to a 40-tooth gear that > was turning an 8-tooth gear. There was a fair amount of (...) (21 years ago, 30-Jun-05, to lugnet.robotics)
|
| |
 | | Re: R2D2 Sounds - A Warning my RCX has laryngitis.
|
|
(...) Hi Dick. No the frequency and loop number are managed by containers, but the note duration was set by using a control (or directly specified) in the version that caused the problem. (21 years ago, 29-Jun-05, to lugnet.robotics)
|
| |
 | | Re: What should you do with a stuck motor?
|
|
On Wed, June 29, 2005 4:19 pm, Jordan Bradford said: (...) The folks at LEGO are VERY good about replacing messed up motors. I've done it all on-line, before. Steve (21 years ago, 29-Jun-05, to lugnet.technic, lugnet.robotics)
|
| |
 | | What should you do with a stuck motor?
|
|
Last night I had a new-style 9V motor attached directly to a 40-tooth gear that was turning an 8-tooth gear. There was a fair amount of torque involved, and my motor stalled after a while. Now the thing won't turn unless I really force it. What (...) (21 years ago, 29-Jun-05, to lugnet.technic, lugnet.robotics, FTX)
|
| |
 | | RE: R2D2 Sounds - A Warning my RCX has laryngitis.
|
|
The note duration must be a compile time constant. By any chance were you trying to use a run-time variable (Robolab container) for this? This could explain your problem. -----Original Message----- From: news-gateway@lugnet.com (...) (21 years ago, 29-Jun-05, to lugnet.robotics)
|
| |
 | | Re: Does any RCX firmware allow a variable to survice shutdown?
|
|
Thanks for your help everyone. As predicted, it was simply that I was defining my variables in the program, and it hadn't occurred to me that they were already persistant and I was actually resetting them myself. Can there ever be a better answer (...) (21 years ago, 29-Jun-05, to lugnet.robotics)
|
| |
 | | Re: Does any RCX firmware allow a variable to survice shutdown?
|
|
(...) Here's a very simple NQC example using the standard LEGO firmware. #pragma noinit int a; task main() { a++; } This simple NQC program will increment global variable zero by one each time it is run. You can turn off the RCX and turn it back on (...) (21 years ago, 29-Jun-05, to lugnet.robotics)
|
| |
 | | Re: Does any RCX firmware allow a variable to survice shutdown?
|
|
(...) Global variables in the standard LEGO firmware(s) are persistent (i.e., their values are not lost when you turn off the RCX). You describe turning the RCX off and on using the "start/stop" button. I am guessing that you mean the red button (...) (21 years ago, 29-Jun-05, to lugnet.robotics)
|
| |
 | | Re: An Idea for new Mindstorms - event potential?
|
|
(...) I'm not knocking the fly, I'm saying that landing on the ceiling is a very difficult problem to solve by realtime calculated piloting (even using a desktop PC). But it needs very little calculation at all if the problem is almost entirely (...) (21 years ago, 29-Jun-05, to lugnet.robotics)
|
| |
 | | Re: An Idea for new Mindstorms - event potential?
|
|
Citando Steve Baker <sjbaker1@airmail.net>: Justin wrote: > A fly can land on the ceiling not > because it is smart (it isn't), but because it's body is built such that the > laws of physics themselves automate a process that would be prohibitively (...) (21 years ago, 28-Jun-05, to lugnet.robotics)
|