Zero capture
Custom
by Raymond
Sat Apr 18, 2009 9:32 pm
Hiya Pedro,
Yes I set to custom/expert and it tests successfully with respect to creating the motions and saving however the remocon behaves eratically. Now witht eh upgrade fo the firmware using 2.15 from Robobuilders site the remocon produces only a Red light error when I press Button 1 as I only saved one motion to the controller. I reverted back to motionbuilder 1.19 as the one on my CD was v1.0 which is pretty old.
Once again I must emphasise in motionbuilder it nehaves as expected it's the saved motion on the controller that is behaving weirdly. I did try three other project variants even one where it shows all the servo dials in aplane row by row fashion. What confuses my mind int he zero posture saying cant write failure. I have a funny suspicion that the software tools are not designed to manage morethan 16 servos and while I can create motions in 18 servos it's not being called properly. I want to confirm this is the case and if so I can bugger the tools and manually create my motions talking directly to the servos which is crap and doing it the hard way... but better than floggin a dead horse with these tools.
Sorry for the rambling but this thing is really annoying me now lol
Mark
Yes I set to custom/expert and it tests successfully with respect to creating the motions and saving however the remocon behaves eratically. Now witht eh upgrade fo the firmware using 2.15 from Robobuilders site the remocon produces only a Red light error when I press Button 1 as I only saved one motion to the controller. I reverted back to motionbuilder 1.19 as the one on my CD was v1.0 which is pretty old.
Once again I must emphasise in motionbuilder it nehaves as expected it's the saved motion on the controller that is behaving weirdly. I did try three other project variants even one where it shows all the servo dials in aplane row by row fashion. What confuses my mind int he zero posture saying cant write failure. I have a funny suspicion that the software tools are not designed to manage morethan 16 servos and while I can create motions in 18 servos it's not being called properly. I want to confirm this is the case and if so I can bugger the tools and manually create my motions talking directly to the servos which is crap and doing it the hard way... but better than floggin a dead horse with these tools.
Sorry for the rambling but this thing is really annoying me now lol
Mark
Another point
by Raymond
Sat Apr 18, 2009 9:48 pm
Hiya,
The serial# on the back of the controller this is only necessary when you register on the controller. download page and not necessary or even writable when we create our own project/motions correct?
This is the only part I don't get in the creation process. Lastly I followed the steps to register the remocon by pressing the middle Red button and it does as documented causing the leds onthe controller to flash so it's registered. Just thought I'd mention that to show compliance with those steps.
Even if I send the message packet replicating the msg the remocon would send I get the same effect which is now a red light error onthe controller when I attempt to activate the saved motion 1.
Thanx for your willingness to help really appreci any ideas and guidance.
I have focused on writing all the software interfaces for Bioloid (AX/RX servos on CM5/CM2+) ,Kondo, Robobuilder, Puolou controllers based on what was documented and tested with single servoc configurations, now the final steps are to create the motion and fine tune so this hiccup is most frustrating!
Mark
The serial# on the back of the controller this is only necessary when you register on the controller. download page and not necessary or even writable when we create our own project/motions correct?
This is the only part I don't get in the creation process. Lastly I followed the steps to register the remocon by pressing the middle Red button and it does as documented causing the leds onthe controller to flash so it's registered. Just thought I'd mention that to show compliance with those steps.
Even if I send the message packet replicating the msg the remocon would send I get the same effect which is now a red light error onthe controller when I attempt to activate the saved motion 1.
Thanx for your willingness to help really appreci any ideas and guidance.
I have focused on writing all the software interfaces for Bioloid (AX/RX servos on CM5/CM2+) ,Kondo, Robobuilder, Puolou controllers based on what was documented and tested with single servoc configurations, now the final steps are to create the motion and fine tune so this hiccup is most frustrating!
Mark
Firmware 2.09 v2 2.15 observation
by Raymond
Sat Apr 18, 2009 11:30 pm
Hi Guys,
I observed that if I reverted to firmware 2.09 from 2.15 the remocon started to respond with eratic movement in 2.09 as opposed to the red error light in 2.15.
I guess the best way to determine what to try is to compare the steps taken by i-Bot to configure and save his motions and execute via the remocon. If he can state which firmware and software versions he used, also which project type he chose. If after all and my own persist to misbehave I would lean towards a manufacturer flaw in the controller.
Thanx
Mark
I observed that if I reverted to firmware 2.09 from 2.15 the remocon started to respond with eratic movement in 2.09 as opposed to the red error light in 2.15.
I guess the best way to determine what to try is to compare the steps taken by i-Bot to configure and save his motions and execute via the remocon. If he can state which firmware and software versions he used, also which project type he chose. If after all and my own persist to misbehave I would lean towards a manufacturer flaw in the controller.
Thanx
Mark