|
|
 | | Re: train precision
|
| I do think Steve is on the right track here. The train regulator varies the voltage, but the RCX output can't. So you are left with managing (nominally) 9v pulses. But there is another solution. You could add a DCC decoder to your train motor, and (...) (18 years ago, 29-Dec-05, to lugnet.robotics.rcx.legos)
| | | | | Re: train precision
|
| (...) hi Steve, I think the problem is not exactly the same. The lego technic motors run always at the same speed so you need to use that kind of schema for speed control in robots. The train motors are different, they have a speed proportional to (...) (18 years ago, 29-Dec-05, to lugnet.robotics.rcx.legos)
| | | | | Re: train precision
|
| (...) Daniel, One problem you'll run into with most software is that it switches between power and float to adjust the motor levels. It works much better to switch between power and brake. Using most software, the train will continue to speed up, (...) (18 years ago, 27-Dec-05, to lugnet.robotics.rcx.legos)
| | | | | train precision
|
| A couple of years ago, i used brickOS. Then, i changed to Lejos... I have a moc where i use the RCX to control a train with a lego train motor. It is difficult to control the train with LejOS, because it only has 8 output levels. Two solve the (...) (18 years ago, 27-Dec-05, to lugnet.robotics.rcx.legos)
| | | | | earlier version of binutils?
|
| Hi, I have been trying to get brickos to compile on my linux machine. I followed the instructions here: (URL) used binutils version 2.16.1, and gcc version 4.0.2. The cross compile seemed to work. However, when I try to compile brickos, I get the (...) (18 years ago, 22-Dec-05, to lugnet.robotics.rcx.legos)
| | | | | Re: avoid messaging
|
| (...) I'd agree that a physical block is the easiest, although there is a software solution. The RCX can not recieve a command while it's transmitting - so if you saturate the transmitter with things to do, it will not be able to "look" for any (...) (19 years ago, 5-Dec-05, to lugnet.robotics.rcx.robolab, lugnet.robotics.rcx.legos)
| | | | | RE: avoid messaging
|
| Yes, I indeed have an attachment which will act like blockage, but not a full one though. Sounds like this is the fastest and easiest to do. I fully understand the opcodes concept, as I myself wrote compile code before. However, these kids age only (...) (19 years ago, 5-Dec-05, to lugnet.robotics.rcx.robolab, lugnet.robotics.rcx.legos)
| | | | | Re: avoid messaging
|
| (...) If you have an event waiting for a message, I doubt it will have much impact on the speed of the rest of the program. However, this will not catch the messages you're looking for. You can't use the "mail" function to receive op-code, such as (...) (19 years ago, 5-Dec-05, to lugnet.robotics.rcx.robolab, lugnet.robotics.rcx.legos)
| | | | | avoid messaging
|
| Hi In order to avoid unwanted interruption, such as remote shutdown, from other RCX during execution time, I wonder if the only thing can be done to safe-guard my RCX will be having an independent task dedicated to receive message (mail). This, of (...) (19 years ago, 5-Dec-05, to lugnet.robotics.rcx.robolab, lugnet.robotics.rcx.legos)
| | | | | using rotation sensor
|
| Most of you are aware of the speed of the robot often causes parity in distance via the feedback of rotation sensors because of inertia. In our experiment, even with a robot with moderate speed. The parity seems to often occur right at the beginning (...) (19 years ago, 30-Nov-05, to lugnet.robotics.rcx.robolab, lugnet.robotics.rcx.legos)
|
|
