Would this work with RC servos? - Electronic Circuits Projects Diagrams Free

atferrari · 16th August 2005, 10:40 AM

I intend to control an RC servo using a signal repeating every 4 ms instead of the usually advised 20 msec.

The variation of width will be as required between 1 and 2 ms. No changes here, of course.

Should I expect any problem or is it OK?

Any reply appreciated.

**Nigel Goodwin** · 16th August 2005, 01:35 PM

It's only the MARK that sets the servo position, the SPACE doesn't seem to matter?. But usually you're making the SPACE longer, not shorter, but I see no reason why it won't work - but I should test it first!.

Why are you wanting to use a shorter SPACE anyway?.

atferrari · 16th August 2005, 10:23 PM

Using a 16F628 with 4 MHz clock I couldn't find a way to get the usual 1 to 2 ms every 20 ms but only every 4 ms :!:

The values I've got yesterday were, for 10 bits to be writen to CC1PRL and CCP1CON b5:b4 :

250 for 1 ms
375 for 1,5 ms
500 for 2 ms.

For the period, I get:

prescaler : 16
PR2 : 255

giving 244 Hz, that is: 4 ms (app) period.

JFDuval · 16th August 2005, 11:51 PM

Doing some research on Google would be a good thing.

http://www.google.ca/search?hl=en&q=...G=Search&meta=

By using two timers, one for the 'high' and one for the 'low', you can achieve pretty good timing.

NleahciM · 17th August 2005, 07:11 AM

running a servo at 250 hz is pushing it a bit - some servos will work at that high of a speed, others won't. Try it - and if it works monitor the temperature of the servo - if it's getting really hot then, obviously, you have a problem. Most servos will work up to around 200hz. Some will stop working well before that, unfortunately. I've heard some of the digital ones can go to 400hz - though I don't have any digitals so I am unable to verify this.

**Nigel Goodwin** · 17th August 2005, 09:11 AM

Quote:

Originally Posted by atferrari

Using a 16F628 with 4 MHz clock I couldn't find a way to get the usual 1 to 2 ms every 20 ms but only every 4 ms :!:

The values I've got yesterday were, for 10 bits to be writen to CC1PRL and CCP1CON b5:b4 :

250 for 1 ms
375 for 1,5 ms
500 for 2 ms.

For the period, I get:

prescaler : 16
PR2 : 255

giving 244 Hz, that is: 4 ms (app) period.

That's because you're trying to use the PWM module, it's not intended for servo's, and it's not really suitable - there's plenty of PIC servo examples on the net, google will find them for you.

demestav · 17th August 2005, 11:21 AM

Hello all.

This is not 100% relevant but I believe it may help a bit.
I was working with parallax cont. rotation servo working perfectly with the pulse that it required.

However there was another guy in the lab that was using the same motor with totally different timings but the servo worked just fine! The reason why his timings were wrong is because he messed up with the prescaler. However the "duty cyle" (percentage) of the pulse was correct even if the duration was wrong. Now the key to the whole situation is that those servos had a screw which you can use to adjust its stability. I believe this is why his servo also worked.

Thanks.

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

16th August 2005, 10:40 AM	#1
atferrari	Would this work with RC servos? I intend to control an RC servo using a signal repeating every 4 ms instead of the usually advised 20 msec. The variation of width will be as required between 1 and 2 ms. No changes here, of course. Should I expect any problem or is it OK? Any reply appreciated. __________________ Agustín Tomás In theory, there is no difference between theory and practice. In practice, however, there is.

16th August 2005, 01:35 PM	#2
Nigel Goodwin	It's only the MARK that sets the servo position, the SPACE doesn't seem to matter?. But usually you're making the SPACE longer, not shorter, but I see no reason why it won't work - but I should test it first!. Why are you wanting to use a shorter SPACE anyway?. __________________ PIC programmer software, and PIC Tutorials at: http://www.winpicprog.co.uk

16th August 2005, 10:23 PM	#3
atferrari	The reason for that Using a 16F628 with 4 MHz clock I couldn't find a way to get the usual 1 to 2 ms every 20 ms but only every 4 ms :!: The values I've got yesterday were, for 10 bits to be writen to CC1PRL and CCP1CON b5:b4 : 250 for 1 ms 375 for 1,5 ms 500 for 2 ms. For the period, I get: prescaler : 16 PR2 : 255 giving 244 Hz, that is: 4 ms (app) period. __________________ Agustín Tomás In theory, there is no difference between theory and practice. In practice, however, there is.

16th August 2005, 11:51 PM	#4
JFDuval	Doing some research on Google would be a good thing. http://www.google.ca/search?hl=en&q=...G=Search&meta= By using two timers, one for the 'high' and one for the 'low', you can achieve pretty good timing. __________________ JFDuval jfduval --@-- aqra.ca http://www.aqra.ca

17th August 2005, 07:11 AM	#5
NleahciM	running a servo at 250 hz is pushing it a bit - some servos will work at that high of a speed, others won't. Try it - and if it works monitor the temperature of the servo - if it's getting really hot then, obviously, you have a problem. Most servos will work up to around 200hz. Some will stop working well before that, unfortunately. I've heard some of the digital ones can go to 400hz - though I don't have any digitals so I am unable to verify this.

17th August 2005, 11:21 AM	#7
demestav	Hello all. This is not 100% relevant but I believe it may help a bit. I was working with parallax cont. rotation servo working perfectly with the pulse that it required. However there was another guy in the lab that was using the same motor with totally different timings but the servo worked just fine! The reason why his timings were wrong is because he messed up with the prescaler. However the "duty cyle" (percentage) of the pulse was correct even if the duration was wrong. Now the key to the whole situation is that those servos had a screw which you can use to adjust its stability. I believe this is why his servo also worked. Thanks.