why need to connect RB to make motions ?
why need to connect RB to make motions ?
by Florent_Lyon
Sun Jul 20, 2008 9:55 pm
Hello all,
MotionBuilder V1 works without connection, meanwhile the new v1.13 beta requires to connect the Robot to do anything.
... so actually I keep using the V1 when I need to test basic things, while I switch to the v1.13 to test wheel mode. It is quicker for me to build the move before connecting, and I want to use the servos as less as possible: I mean only when it worth to run my motions.
I have asked to robobuilder.net and they replied the following message:
"Motion building has always to be done with the robot connected to your PC. It is because MotionBuilder uses the Home position data from the robot."
I am not convinced there is a technical limitation. On my mind the functions should be improved in the way of user needs... so am I the only one who use MotionBuilder without connecting the robot ?
MotionBuilder V1 works without connection, meanwhile the new v1.13 beta requires to connect the Robot to do anything.
... so actually I keep using the V1 when I need to test basic things, while I switch to the v1.13 to test wheel mode. It is quicker for me to build the move before connecting, and I want to use the servos as less as possible: I mean only when it worth to run my motions.
I have asked to robobuilder.net and they replied the following message:
"Motion building has always to be done with the robot connected to your PC. It is because MotionBuilder uses the Home position data from the robot."
I am not convinced there is a technical limitation. On my mind the functions should be improved in the way of user needs... so am I the only one who use MotionBuilder without connecting the robot ?
