Hi,
@ first look the problem comes because PULSOUT commands might not be " interrupted " ... and maybe also because time between two pulse must be kept, say, between 15 and 30 ms ...
Alain
Hi,
@ first look the problem comes because PULSOUT commands might not be " interrupted " ... and maybe also because time between two pulse must be kept, say, between 15 and 30 ms ...
Alain
************************************************** ***********************
Why insist on using 32 Bits when you're not even able to deal with the first 8 ones ??? ehhhhhh ...
************************************************** ***********************
IF there is the word "Problem" in your question ...
certainly the answer is " RTFM " or " RTFDataSheet " !!!
*****************************************
Hello all,
I have tried a minimalist aproach. With only one servo, holding at one position, and no interrupt on change ... just the timer1 interrupt keeping track of elapsed time. The one servo is still very twitchy to the point of not being useable.
BTW, the accuracy of elapsed time is very good when checked with a stopwatch..
Ok
Show us the current test code and tell us about the hardware ( power supply, servo models, how it is all connected, etc )
Dave
Always wear safety glasses while programming.
As mentioned above, the servo runs smooth and quiet when driven by the non-interrupt routine. So, I think the servo and circuit are OK.
However, I now realize that timer1 interrupts are occuring every 10 ms, while the servo pulses are only 1 to 2 ms long. Just guessing, but it seems that timer interrupts that periodically occur during the pulse on-time can signifigantly disrupt the pulse period and cause jittering. Therefore, I think my interrupt-timed approach will not work.
Experiment over.
Bookmarks