Do do you center yourservo to the 50 position before you attached your horn? That would be where EZI builder thanks center is. Then attach the horn to your neutral position. after you make sure that is the case set your minimum position to 50 and see what happens.

The other thing I did was built a switch circuit with a transistor in resistor in a diode. I used that circuit to turn on the power to the servo after the enable signal is sent from ARC. I attached the switching circuit to a digital port on EZ-B and used ARC to switch the transistor on and off. this is how I was able to smooth out the startup of the Servo. again, this is just the workaround I don't know why ARC jumps to the absolute minimum settings that start up.

Let me know what happens. DJ did seem interested in this problem when I was talking about it in my thread.

@DJ, IT WORKED! The problem came from setting another servo speed than "0" before the init position.

I voluntarily set the speed before the init position, because i prefered to see the robot slowly move its arms and head to a neutral position at startup. The script by itself worked well, if not launched after a power on...

So, I clearly have missed something, because I don't understand why setting a slower speed induce a return of the servo to position "0", before moving to the defined position, and only after a power on.

Concerning the electrical pulse, I indeed observe it each time I power on the EZB and servos move to a random position, but very close to their previous position (before power on). What I observed could happens long after power on the EZB... It didn't change anything if I launched the script immediatly before power on or 10 minutes after.

In any case, you saved my day and Wall-E don't have its scary wierd behavior anymore. Thanks.

@Dave, thanks for the help

Thank you again DJ. first chance I get I need to redo my startup script so this won't happen to me anymore. thanks guys for bringing this up. my project keeps running better and better everyday thanks to this group.

It makes sense logically and there is no way around it.

When you set the speed to a value 0, that means instant.

When you set the speed to a value other than 0, it means ramp between the two positions.

When you move a servo to position 10, it was at position 0 during power up. That is because the ez-b tells the servo what position to move. It does not know the position before. It commands the position. It is impossible to read the position.

i was setting speeds first like at(10) .then run position to were i need it .so ineed to set all my servos to servospeed (d0,0) in script init. i see you the # simbol not sure what that does confused @dj

@DJ, thanks for the explanation. It's indeed makes sense now... I think that beacause everything goes smoothly with servos in ARC, I forgot that it does not know the position of the servos at start-up.

@csa459, the # symbol is inserted before a part of the code you don't want to be executed by the script. It is used to give non-executed informations. Example:

# This lign of code is not executed, but the next one is
This lign is executed

oh ok @fredec is all my servospeed need 0 to start with ?in the code

Yes, use the same script that the one proposed by @DJ as an init. script: set first all the servos speed to "0", and then move the servos to the desire position. After that, you are free to set new slower servos speed for all the other scripts you want to use.