They are always jittering. I suspect this may be related to ENABLEHSERVO, but I am not sure. The examples online here show something different from what the Atom PRO manual shows for ENABLEHSERVO and the manual contradicts itself.
Yeah, jitter at idle doesn’t seem right at all. To bad you don’t have an O’ Scope to check the signal using regular Serout vs. HSERVO when sending a 1.5mS pulse.
If you have a SSC-32 card, you could use the free LynxTerm and attach the servo in question to it, then click on the “ALL=1500” button and see if it jitters then, or write a loop that instructs the servo to move 1.5mS using Serout and see what happens.
I fried a servo before and it jittered and would only move in one direction no matter what instructions I gave it. It also would move to random locations even if the positions sent were the same. The servo controller was messed up from to much voltage from my variable output wall pack which I no longer use. I only use the LM Regulated wall packs now.
I suggest dropping the operating voltage to closer to the rated 4.8-6v range and see what happens. You could use a rectifier diode from Radio Shack to do this and see if the jitter stops. Jittering will probably cause bare spots to eventually form in the pot and ruin the servo.
First question is what version of the IDE are you using? Second is what else are you doing on the AP. Depending on the version for example: 8.0.1.0 I found that having HSERVO active would cause other pins to have problems. I noticed this first using my LCD as well as other serout commands. Nathan fixed this, but I found on I believe 8.0.1.2 that a serout to my LCD caused the HSERVO signal to screw up, this caused a jitter on the brat legs. I don’t remember if it was fully fixed in 8.0.1.3 or if he was going to fix it for the next release. I will have to check out the brat again to see. I will forward to you a message I sent to him that shows what I mean.
I do have another SSC-32 here and am planning to get it connected up today. I’ve got LynxTerm too.
I need to get one of those wallpacks so I don’t have to charge my battery packs so often. It makes sense to have one when I am just working at the bench.
Nothing else at present. I have just got a section of code I am testing my conversions in, a while loop that is separate from everything else. I’ve already got my multiple PING and multiple Sharp IR ranger code converted and both work fine so far.
The modification you suggested works! As soon as I retest the code with multiple sensors and make sure it works, I should be able to get rid of the Power_Of_2 routine completely.
What is in your while loop? Do you repeat calling HSERVO? I do know that some of the servos on the brat do jitter some, I was not sure if it was because of the load or the like.
I wonder if you do something like:
main
hservo p4/0
pause 100
goto main
if the recalling of hservo with the same value might at times either cause it to recalc and maybe retime, which could cause a jitter. Maybe something I should try to rehook up the cheap OSC to see if I can notice anything… If it is that simple, then I can probably add a simple test to only call hservo if something changed…
I do think the new HSERVO code probably needs a bit more beating on before they make an official release.
Yes, I think it is an HSERVO issue. The Atom PRO is constantly resetting - with a freshly charged up 6.0V battery pack. I have used both fully charged 6.0v and 7.2v battery packs with the same result. I remember you saying that about HS-475’s but the only other battery packs I have here are 7.2v packs. I only have one 6.0v pack.
I remember seeing this kind of behavior when I was messing with the ping)) code awhile back. I am going to be getting back into this again soon with my latest toy so I’ll keep in mind that this still occurs despite the newer IDE and all.
I know that AcidTech responded on that thread showing that the code is not complete. Have you tried running it without the servos connected to see if it resets then?