Motion Pages

[Pev]

I have been seeing some strange behaviour when getting my Bioloid Humanoid to just stand such as :



Was really starting to annoy me so in pure desperation I turned to the manual.

OOPS turns out it is probably my own fault. I had moved the standing motion to Motion Page 1 for easy reference, however on Page 78 of the manual it states:

"Page 0 and Page 1 have special functions so it is recommended that you do not use them"

Since moving my standing motion away from page 1 all has been fine.

Just thought I'd mention it.........

(A very embarassed and red faced) Pev

[Pev]

Seems I was wrong.... My bioloid is still exhibiting this issue (fault?)....and now even with the Robotis supplied code and motion file I get issues with legs kicking out sideways and other unexpected and unprogrammed movement.

Is anyone else seeing this problem?

Cheers

Pev

[barbar]

hi pev,

same sporadic symptoms over here!

It looks like data-rubbish going through humaloid sometimes when I run a bpg-program. But e.g. if I "play" with poses or individual servos using the motion editor I have no misbehavior. Could it be a problem of the Behavior Control Program? I'm still testing in order to find reproducable conditions.

Also looking forward to feedbacks from others.

(sorry for my ...)

[Pev]

Barbar,

I am seeing exactly the same thing. Everything is fine when working with the motion editor in program mode (except for a few hangs of the software), but once you try to call the motions in a behaviour Control Program things get very sporadic......

Have emailed Robosavvy and Robotis about this today so hopefully will hear something in the next few days....

I have also managed to blow the glass fuse in the CM-5 when the bot went a little mad and servos hit brackets (probably caused a high current drain and blew the fuse for the battery). Am just about to replace it now

Pev

[barbar]

pev,

I'm wondering whether the strange behaviour only occurs when the sensor module is somehow involved. I've written a short program without doing anything with the AX-S1 and (cross fingers) no mistakes til now

(sorry for ...)

[Pev]

Barbar,

Interesting thought - did you actually disconnect the sensor module or just not call it from the code?

I'll have a go at this as well

Pev

[barbar]

sorry Pev,

just had an unprogrammed kick without ax-s1 connected and accessed.

So I'm keeping on testing ..

[Pev]

sorry Pev,

just had an unprogrammed kick without ax-s1 connected and accessed.

So I'm keeping on testing ..

I have just had an unprogrammed arm movement in the motion editor as well so it looks like it may be a bit more than just the Behavioural Control Program. I did notice that there is a verison of the underlying control code for the profdccessor on the CD. It is version 1.10. My CM5 is at version 1.12 according to the robot terminal program. I am wondering it it may be worth downgrading to 1.10......

Think I may wait to hear from Robotis.....

Pev

[inaki]

Ooops. I have downgraded accidentaly to version 1.10 !

I was trying the programming interface and replaced the ROM with the one in the CD. I did not realize that it was an earlier version!!!

Now that I have 'downgraded' do you me to check something in particular ?

[barbar]

dear inaki,

would you please simply build the humanoid and then test if everything is working under 1.1 .. sorry!

[limor]

Hi, I received a message from Robotis saying that they are now aware of this issue and will post a software update in a few days.

[stevo3d]

For those searching for answers, the glitching or unprogrammed motions problem has been solved by patching the CM-5 and all AX-12s as described in this post:
http://robosavvy.com/modules.php?name=F ... opic&t=309

This post shows where to download the software in one handy package, along with some other enhancements and additional robot files:
http://robosavvy.com/modules.php?name=F ... opic&t=336