Some problems and complaints
Some problems and complaints
by inaki
Wed May 17, 2006 6:54 pm
Now I am working with my Quadpod, so I am only using 8 servos. I am using ROM 1.10 because of my accidental downgrading!:-(
When playing from behavior Control sometimes one of the servos goes to zero position even in motions that work well under Motion Editor. This happens at random.
The Page 2 Motion refuses to run. It might be because that warning that tells against using page one and two. I will try to skip these two pages.
Motion Editor communications link with the robot breaks sometimes. I don't know why. It is totally random.
The fact that Behaviour Control and Motion Editor are separate programs is a pain in the ass, because each one wants the COM port for itself ! The motion editor should be a function integrated in Behaviour Control.
By the way, is there a way to save motion pages to disk from the Motion Editor ? The only way I see is saving to robot and then from robot to disk.
When playing from behavior Control sometimes one of the servos goes to zero position even in motions that work well under Motion Editor. This happens at random.
The Page 2 Motion refuses to run. It might be because that warning that tells against using page one and two. I will try to skip these two pages.
Motion Editor communications link with the robot breaks sometimes. I don't know why. It is totally random.
The fact that Behaviour Control and Motion Editor are separate programs is a pain in the ass, because each one wants the COM port for itself ! The motion editor should be a function integrated in Behaviour Control.
By the way, is there a way to save motion pages to disk from the Motion Editor ? The only way I see is saving to robot and then from robot to disk.
by barbar
Wed May 17, 2006 9:14 pm
I have downgraded my humanoid to a chest with attached arms = 6 servos and sensor module (I dont want him to walk away 
). The unprogrammed random movements (servos got to zero position? really?) seem to have reduced but are not completely gone. I hope that the robotis-fix will help. Thanks to Limor and Pev for complaining in Korea.
Despite the problems the Bioloid is a great thing. I'm just teaching my amputated humanoid to grab and hold the beer bottle on my table
Im thinking about building a humanoid with waist rotation, wrists, claws and sensors on the feet (that means further 5 AX-12 and 2 AX-S1, Limor?). Lets wait until the bugs are fixed and the money is saved.
I agree with inaki concerning the com port sharing problems. I'ts the same with the terminal program I use for motion editing (the motion editor is a little bit slowly). We will need a CM-5 c-programmer in the forum to integrate the functions into one program
inaki: How would you upload motion pages to your pc? 1. Boot Loader 2. UP 0X0E000, FFFF 3. Menu, Recieve File 4. What the hell is "push SW for starting"?
). The unprogrammed random movements (servos got to zero position? really?) seem to have reduced but are not completely gone. I hope that the robotis-fix will help. Thanks to Limor and Pev for complaining in Korea.
Despite the problems the Bioloid is a great thing. I'm just teaching my amputated humanoid to grab and hold the beer bottle on my table
Im thinking about building a humanoid with waist rotation, wrists, claws and sensors on the feet (that means further 5 AX-12 and 2 AX-S1, Limor?). Lets wait until the bugs are fixed and the money is saved.
I agree with inaki concerning the com port sharing problems. I'ts the same with the terminal program I use for motion editing (the motion editor is a little bit slowly). We will need a CM-5 c-programmer in the forum to integrate the functions into one program
inaki: How would you upload motion pages to your pc? 1. Boot Loader 2. UP 0X0E000, FFFF 3. Menu, Recieve File 4. What the hell is "push SW for starting"?
by inaki
Wed May 17, 2006 11:10 pm
Barbar, your method to save motions to disk is somewhat involved but I am afraid is the only way to save just one Motion. I prefer the Behavior Control-Robot Motion option, although it saves all motions at the same time!
What would say a new guy to robotics if we explain that he/she need to enter boot mode (pressing the # key is funny), then chose an option from a text menu in a terminal program (oops don't forget to disconnect COM port in Motion Editor), hey please check the address and length of the data in first place , then press a button on the robot, ... Just to save a motion ?
I think the Robotis software need an urgent general overhaul!
What would say a new guy to robotics if we explain that he/she need to enter boot mode (pressing the # key is funny), then chose an option from a text menu in a terminal program (oops don't forget to disconnect COM port in Motion Editor), hey please check the address and length of the data in first place , then press a button on the robot, ... Just to save a motion ?
I think the Robotis software need an urgent general overhaul!
by barbar
Wed May 17, 2006 11:53 pm
I apologize, of course you're right inaki! I was so fixed on textbased talking to the cm-5, that I simply forgot the option in the behaviour contol program.
So I wont use this method any more:
- get boot loader running
- type in: up 0x0e000, 10000
- choose Recieve File in the Files menu
- name the file and click save
- press start-button on the CM-5
- wait until 65536 byte have been uploaded
- press end-key on the keyboard
- press mode-button on the CM-5
And overhauling the Robotis software would really be a good thing to do!
So I wont use this method any more:
- get boot loader running
- type in: up 0x0e000, 10000
- choose Recieve File in the Files menu
- name the file and click save
- press start-button on the CM-5
- wait until 65536 byte have been uploaded
- press end-key on the keyboard
- press mode-button on the CM-5
And overhauling the Robotis software would really be a good thing to do!
by Pev
Thu May 18, 2006 5:42 pm
Some interesting observations. Here are my thoughts for what they are worth lol
The manual states that page 0 and page 1 of the motion memory(?) are used for special functions and should not be used, however in the graphical motion editor there is no page 0 (that I can access) so I am guessing that in the graphical tool they mean page 1 and page 2. Would be useful if the manual and interfaces all matched.
I have also seen the comms link to the software (both motion editor and Behavior Control Editor) fail for no apparent reason. However I have moved my programming onto my desktop machine and no longer use a USB to serial converter. This has greatly reduced the number of comms failures (I've only had one since I stopped using the converter)
I don't disagree with the idea of the motion editor being a function of the Behaviour Control Program but don't see this as a big issue. This is mainly because I am storyboarding my motions (very basic sketches), creating the motions and only then using the Behaviour Control Program to script them together. Using this method I rarely have the comms conflict, but my way of working obviously will not suit everyone and a consolidation of the programs would be good.
One thing I would like to be able to do is actually write the behaviour control programs as text rather than using the click/double click graphical interface.... I just am more used to the classic programming approach and would prefer to be able to see more of my program on screen rather than having to scroll about due to the ammount of space the graphical interface takes up. (Having said that I think it is very good for novices such as my nephew to get him into programming the robot)
I am looking forward to seeing the fix and this will basically get me back on track to try to put the humanoid through its paces as well as getting some other bots built from the kit.
Barbar/Anaki, thanks for the info on saving single pages of motions, hadn't worked that out yet and can see it being useful to move a motion from one motion file to another, which I am sure I am going to need to do.
So anyways thats my 2p worth
Pev
The manual states that page 0 and page 1 of the motion memory(?) are used for special functions and should not be used, however in the graphical motion editor there is no page 0 (that I can access) so I am guessing that in the graphical tool they mean page 1 and page 2. Would be useful if the manual and interfaces all matched.
I have also seen the comms link to the software (both motion editor and Behavior Control Editor) fail for no apparent reason. However I have moved my programming onto my desktop machine and no longer use a USB to serial converter. This has greatly reduced the number of comms failures (I've only had one since I stopped using the converter)
I don't disagree with the idea of the motion editor being a function of the Behaviour Control Program but don't see this as a big issue. This is mainly because I am storyboarding my motions (very basic sketches), creating the motions and only then using the Behaviour Control Program to script them together. Using this method I rarely have the comms conflict, but my way of working obviously will not suit everyone and a consolidation of the programs would be good.
One thing I would like to be able to do is actually write the behaviour control programs as text rather than using the click/double click graphical interface.... I just am more used to the classic programming approach and would prefer to be able to see more of my program on screen rather than having to scroll about due to the ammount of space the graphical interface takes up. (Having said that I think it is very good for novices such as my nephew to get him into programming the robot)
I am looking forward to seeing the fix and this will basically get me back on track to try to put the humanoid through its paces as well as getting some other bots built from the kit.
Barbar/Anaki, thanks for the info on saving single pages of motions, hadn't worked that out yet and can see it being useful to move a motion from one motion file to another, which I am sure I am going to need to do.
So anyways thats my 2p worth
Pev
by barbar
Fri May 19, 2006 6:06 pm
Pev wrote:I have also seen the comms link to the software (both motion editor and Behavior Control Editor) fail for no apparent reason. However I have moved my programming onto my desktop machine and no longer use a USB to serial converter. This has greatly reduced the number of comms failures
Confirmed! No comms breaks any more since moving away from USB-serial-converter (using behavior control prog and terminal prog). But for what reason? I thought either something works stable or not at all ...
Pev wrote:One thing I would like to be able to do is actually write the behaviour control programs as text rather than using the click/double click graphical interface....
same with me ...
. Going to bed ... two hours sleep ...Misprint in manual: AX-12 Address 46 (existence of movement)
by barbar
Wed May 24, 2006 1:56 pm
Misprint in manual page 30: AX-12 Address 46 (existence of movement)
wrong:
1 when executing a move command otherwise 2
correct:
1 when executing a move command otherwise 0
wrong:
1 when executing a move command otherwise 2
correct:
1 when executing a move command otherwise 0