 | | Re: RCX & RIS, a fading glory?
|
|
(...) That's a good point...providing Lego carry on making them. It comes down to who makes this wonderous hypothetical system. * We'd hope that Lego would make it...then the motor design is a non-issue. * If not - then I suppose we'd need a 'legacy (...) (24 years ago, 7-Feb-03, to lugnet.robotics)
|
| |
 | | Re: RCX & RIS, a fading glory?
|
|
What about adapter bricks to make the current motors and sensors useful? The command handling is done in the adapter brick, and regular "commands" (those already sent to a motor or sensor) are output to the target device. If enough interest is (...) (24 years ago, 7-Feb-03, to lugnet.robotics)
|
| |
 | | Re: RCX & RIS, a fading glory?
|
|
Despite this thread having become strangely fractured within the lugnet system of threads, and despite the intriguing "what if's" that always get aired when threads like this are allowed to take wing, I have a couple of rather down to earth (...) (24 years ago, 7-Feb-03, to lugnet.robotics)
|
| |
 | | Re: RCX & RIS, a fading glory?
|
|
(...) It's not just a matter of distance - it's a matter of the electrical load on the output of a single device. TTL-type devices have a suprisingly low limit on the number of inputs they can drive. With a 'bus' type device, that would limit you to (...) (24 years ago, 7-Feb-03, to lugnet.robotics)
|
| |
 | | RE: RCX & RIS, a fading glory?
|
|
Marco That's exactly how I see it too. So do we out-vote Steve? I hope not because he may be right. Can anyone come up with a killer argument either way? Peter (24 years ago, 6-Feb-03, to lugnet.robotics)
|
| |
 | | Re: RCX & RIS, a fading glory?
|
|
Steve You're really putting me on the spot aren't you? OK ... (...) Before a download begins, the PC checks whether the named motors exist in the model. If they don't, it offers you the chance to set up a new alias table (which is probably local to (...) (24 years ago, 6-Feb-03, to lugnet.robotics)
|
| |
 | | RE: RCX & RIS, a fading glory?
|
|
Chris (...) particular way. (...) Yes that's exactly how I see it. But Steve has different ideas. He may be right - in my mind, the jury's still out. Peter (24 years ago, 6-Feb-03, to lugnet.robotics)
|
| |
 | | RE: RCX & RIS, a fading glory?
|
|
Marco thought: (...) map in the (...) From a code writing point of view, defining macros that identify the motor is much nicer than having to list out the path to the motor. However, when you have to replace a dodgy motor on an individual, you'll (...) (24 years ago, 6-Feb-03, to lugnet.robotics)
|
| |
 | | Re: Double Rotation Sensor using one sensor port
|
|
Nice device... a photograph of the beast would be even nicer! Too bad this trick can work only with a fast OS (i.e. BrickOS). The other problem is that (afaik) you can't see the rotation direction (but this can often be derived from motor command) (...) (24 years ago, 6-Feb-03, to lugnet.robotics)
|
| |
 | | RE: RCX & RIS, a fading glory?
|
|
(...) hmmm... I prefer the method using a High_Level map in the source code or as a .h file ///.../// #IFDEF _TWINROBOTA_ #INCLUDE 'TwinRobotA_devmap.h' #ENDIF #IFDEF _TWINROBOTB_ #INCLUDE 'TwinRobotB_devmap.h' #ENDIF #IFDEF _TWINROBOTC_ #INCLUDE (...) (24 years ago, 6-Feb-03, to lugnet.robotics)
|