Subject:
|
RE: RCX & RIS, a fading glory?
|
Newsgroups:
|
lugnet.robotics
|
Date:
|
Thu, 6 Feb 2003 15:11:32 GMT
|
Original-From:
|
"Marco Correia" <Marco.Correia@soporcel.pt>
|
Reply-To:
|
<MARCO.CORREIA@SOPORCEL.PTnomorespam>
|
Viewed:
|
784 times
|
| |
|
|
> -----Original Message-----> Andrew J. Huang
> One way to do location aware is to make every bus
> brick a network node and source-route packets
> between the device and the RCX. Then, you write
> your programs based on location. For example you
> create a packet that specifies a 10 revolution CCW
> rotation and send it:
> - down the neck-link,
> - out the first right appendage link,
> - past the rotator cuff node,
> - past the elbow-joint node
> - number 1 in the daisy chain
> This would then pull/release a pair of tendons
> that would un-grasp the thumb.
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 'TwinRobotC_devmap.h'
#ENDIF
//ELSE
// compiler will stop with an error like
// "RightHand_Finger1 device unkown !"
//...
OnFor(10,RightHand_Finger1);
OnFor(10,RightHand_Finger2);
OnFor(10,RightHand_Finger4);
//...
//send to rotation sensor+stepper motor
//a "rotate Neck to a 45 degree position"
OnToDegrees(45,NeckServo)
//...
/////////////////////////////////////////
rather than refering to a device with something like:
/////////////////////////////////////////
//...
OnFor(10,'\down the neck-link\out the first right appendage link\past the
rotator cuff node\past the elbow-joint node\number 1 in the daisy chain');
OnFor(10,'\down the neck-link\out the first right appendage link\past the
rotator cuff node\past the elbow-joint node\number 2 in the daisy chain');
OnFor(10,'\down the neck-link\out the first right appendage link\past the
rotator cuff node\past the elbow-joint node\number 4 in the daisy chain');
//...
//send to rotation sensor+stepper motor
//a "rotate Neck to a 45 degree position"
OnToDegrees(45,'\neck base')//...
/////////////////////////////////////////
...even if something like the following could be used:
/////////////////////////////////////////
//...
SetCurrentDeviceNode('\down the neck-link\out the first right appendage
link\past the rotator cuff node\past the elbow-joint node');
OnFor(10,'number 1 in the daisy chain');
OnFor(10,'number 2 in the daisy chain');
OnFor(10,'number 4 in the daisy chain');
//...
//send to rotation sensor+stepper motor
//a "rotate Neck to a 45 degree position"
OnToDegrees(45,'\neck base')//...
//...
/////////////////////////////////////////
mc.
|
|
Message has 1 Reply:
 | | 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 (...) (22 years ago, 6-Feb-03, to lugnet.robotics)
|
Message is in Reply To:
| | RE: RCX & RIS, a fading glory?
|
| Marco, Yes, I agree that logical mappings will help the problem. But consider this example: You have motors with the friendly names of motor1.. motor20 You write a program and specify the associations: left arm = motor1, right=motor2, etc. I believe (...) (22 years ago, 4-Feb-03, to lugnet.robotics)
|
8 Messages in This Thread:
  
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
