cappyjack:
I am interested in using the new ping library but am concerned about the interrupt driven version. I am using an arduino uno, 2 parallax ping sensors mounted on servo motors (from Parallax). I want to drive each servo 180 deg to make a full 360 sweep as fast as I can. After each servo move, I want to ping a distance and use that value to play a small wav file. I put an Adafruit wav shield on my arduino and found that it uses the only 16 bit timer. The servo library from arduino uses it too. So I found another servo library that uses an 8 bit timer on the AT328 and I can play wavs and mover servos. I cannot get good pings all the time with the standard ping code.It appears that the new ping libary uses the 16 bit timer, too. But, in the revision history, it appears that an earlier version does not. Is that correct? I would appreciate any suggestions. Thank you.
First, you don't need to use the timer interrupts at all with NewPing. The default method doesn't use any of the timers and works just fine. Via polling, you can still do very effective timed events without using timer interrupts at all.
If you're sketch is event-driven and you're trying to use a timer for the ping, NewPing offers an option of using timer 2, which is an 8bit timer. It uses timer 2 because timer 1 is used with the standard servo library.
If you're not creating a multi-tasking event-driven sketch, you probably shouldn't be using NewPing's timer event method. So, the question should really be, why do you think you need to use the timer interrupt method of NewPing? Do you really have a need for it? Is the rest of your sketch event-driven where it's justified and would be beneficial?
Tim