LeafLabs Garden » Topic: PWM dutyCycle

LeafLabs Garden » Topic: PWM dutyCycle http://forums.leaflabs.com/topic.php?id=929 A place to share, learn, and grow... en-US Fri, 22 Jan 2016 00:23:24 +0000 http://bbpress.org/?v=1.0.2 <![CDATA[Search]]> q http://forums.leaflabs.com/search.php gbulmer on "PWM dutyCycle" http://forums.leaflabs.com/topic.php?id=929#post-5771 Wed, 27 Jul 2011 10:15:26 +0000 gbulmer 5771@http://forums.leaflabs.com/ I had a look at the timer setup, 'void timer_init(timer_dev_num timer_num, uint16 prescale)` in libmaple timers.c & timer.h, the mode is: <pre><code>timer->CR1 = ARPE; // No clock division // Do not buffer auto-reload preload // Edge aligned // Upcounter // Do not stop counter at update event // Update events enabled (etc, see bits [1:2]) // Counter disabled for now</code></pre> and APRE is: <code>#define ARPE BIT(7) // Auto-reload preload enable</code> This means the counter in the timer is in 'up-count' mode, and not 'up/down count' mode, so the prescaler is 22. gbulmer on "PWM dutyCycle" http://forums.leaflabs.com/topic.php?id=929#post-5768 Wed, 27 Jul 2011 08:28:05 +0000 gbulmer 5768@http://forums.leaflabs.com/ poslathian - is their a bug in <code>void setPrescaleFactor(uint32 factor)</code> ? If not, that can be used to set the prescaler, and nothing else should be needed; pwmWrite should 'Just Works' (TM:-) It happens that a 50Hz frequency for the model servo is quite close to the clock divided by 65,536 (the normal reload value) pre-scaled by 11 or 22, depending on whether the timer is in 'up counting' mode (prescale 22), or 'up/down counting' mode (prescale 11. The only question is whether the timers are set up for 'symmetric' PWM using 'Center-Aligned' 'up/down counting' mode, or simple 'up counting' mode, which effects the prescale value used. The documentation for timer_mode at <a href="http://leaflabs.com/docs/libmaple/api/timer.html#project0timer_8h_1a28110292f2481f7b44d1517fb4ce3c15" rel="nofollow">http://leaflabs.com/docs/libmaple/api/timer.html#project0timer_8h_1a28110292f2481f7b44d1517fb4ce3c15</a> says the default for the timer is 'TIMER_PWM'. Edit: I checked the code for <code>timer_int</code> and the counter is in 'up-count' mode, so the appropriate prescaler value 22. (I realise this calculation is MCU clock dependant, but, at the moment all LeafLabs boards, and mine, run at 72MHz :-) iRobotGoddard on "PWM dutyCycle" http://forums.leaflabs.com/topic.php?id=929#post-5759 Tue, 26 Jul 2011 14:08:03 +0000 iRobotGoddard 5759@http://forums.leaflabs.com/ thanks alot! poslathian on "PWM dutyCycle" http://forums.leaflabs.com/topic.php?id=929#post-5758 Tue, 26 Jul 2011 14:07:24 +0000 poslathian 5758@http://forums.leaflabs.com/ btw, thats for a timer interrupt. If you just need the PWM frequency changed, you can just call timer_set_period and jump straight to pwmWrite ... I just pulled this from a sketch I happened have handy. poslathian on "PWM dutyCycle" http://forums.leaflabs.com/topic.php?id=929#post-5757 Tue, 26 Jul 2011 14:06:29 +0000 poslathian 5757@http://forums.leaflabs.com/ perhaps the hand written docs for the timers are more useful? <a href="http://leaflabs.com/docs/lang/api/hardwaretimer.html#lang-hardwaretimer" rel="nofollow">http://leaflabs.com/docs/lang/api/hardwaretimer.html#lang-hardwaretimer</a> unfortunately, the setPeriod function had a bug introduced in 0.0.11 by accident. You can use this function instead: <pre><code>/* 0.0.11 breaks timer setPeriod, so lets provide a working version here */ uint16 timer_set_period(HardwareTimer timer, uint32 microseconds) { if (!microseconds) { timer.setPrescaleFactor(1); timer.setOverflow(1); return timer.getOverflow(); } uint32 cycles = microseconds*(72000000/1000000); // 72 cycles per microsecond uint16 ps = (uint16)((cycles >> 16) + 1); timer.setPrescaleFactor(ps); timer.setOverflow((cycles/ps) -1 ); return timer.getOverflow(); }</code></pre> and you can incant the setperiod like this: <pre><code>#define AUDIO_RATE 15 /* timer period in us */ ... // Setup Timer Timer2.setChannel1Mode(TIMER_OUTPUTCOMPARE); /* 0.0.11 IDE bug, setPeriod is no good */ //Timer2.setPeriod(AUDIO_RATE); // in microseconds timer_set_period(Timer2,AUDIO_RATE); Timer2.setCompare1(1); // overflow might be small Timer2.attachCompare1Interrupt(handler_t);</code></pre> iRobotGoddard on "PWM dutyCycle" http://forums.leaflabs.com/topic.php?id=929#post-5752 Tue, 26 Jul 2011 13:38:45 +0000 iRobotGoddard 5752@http://forums.leaflabs.com/ LOL thanks alot. I can understand the frustration. Well I actually found out that my code was working, BUT my pin 5 was bad...probably a cause by my negligence. At any rate, I can control my servos BUT I am trying to control a fan. This may be a wiring issue, due to lack of documentation for the fan we bought, but I want to try every approach before I assume that the choice in fan was bad. gbulmer on "PWM dutyCycle" http://forums.leaflabs.com/topic.php?id=929#post-5750 Tue, 26 Jul 2011 13:08:39 +0000 gbulmer 5750@http://forums.leaflabs.com/ For a normal (analogue) model servo, you want a pulse frequency of close to 50Hz, i.e. 20 millisecond cycle duration (Some seem to work with 16millisecond). Then the pulse needs to be between 1 millisecond and 2 milliseconds long, with 1.5 milliseconds being centre '90 degrees'. There is documentation of a Maple timer interface here: <a href="http://leaflabs.com/docs/libmaple/api/timer.html" rel="nofollow">http://leaflabs.com/docs/libmaple/api/timer.html</a> The documentation is so baroque, ugly and complex, that I can't see the wood for the trees. Maybe you will have better luck. Timer's are 16 bits, so ideally, it will count to 65,536 in 20 milliseconds, or at 50Hz. For a simple square wave, that needs a prescaler of 21.97, so lets call that 22. That is less than 1% error, which servos should easily cope with. For a symetric PWM signal, it is half that, i.e. 11 (I'm a bit busy to check which one it is) So the 72MHz clock is divided by 22, (or 11) to give 3,273 KHz basic count rate. So each count is about 0.3 micoseconds That will need the "void timer_set_prescaler(timer_dev * dev, uint16 psc)" function. Then the timer will give the right servo signal frequency. Then the angle is a value between 1msec and 2msec. Which would be pwmWrite values of 1msec/0.3microsec = 3273 1.5msec/0.3micros = 4909 2msec/0.3microsec = 6546 HTH {Start Rant: The documentation for Timer is very hard to navigate. Grrr. End Rant.} iRobotGoddard on "PWM dutyCycle" http://forums.leaflabs.com/topic.php?id=929#post-5748 Tue, 26 Jul 2011 11:39:08 +0000 iRobotGoddard 5748@http://forums.leaflabs.com/ I'm sorry I wrote that completely wrong! Ok so maple run's off of 72MHz, and I am trying to control a servo. I'm guessing the maple is running extremely to fast to control the servo. So I'm assuming it is as simple as connecting the servo directly yo the maple's VCC, GND, and whatever pin I choose to use for control. For instance if I choose pin5 for my PWM control. I just simply write: void pwmWrite(uint8 FanPin, uint16 37768) would this be what I need to control the PWM at half the rate? And yes, how would I set the frequency? gbulmer on "PWM dutyCycle" http://forums.leaflabs.com/topic.php?id=929#post-5747 Tue, 26 Jul 2011 11:32:41 +0000 gbulmer 5747@http://forums.leaflabs.com/ I'm not sure what you mean. The Maple runs at 72MHz. So the shortest possible pulse is much slower than 300MHz. The duty cycle of a PWM signal is set with pwmWrite <a href="http://leaflabs.com/docs/lang/api/pwmwrite.html#lang-pwmwrite" rel="nofollow">http://leaflabs.com/docs/lang/api/pwmwrite.html#lang-pwmwrite</a> The signature is: void pwmWrite(uint8 pin, uint16 duty_cycle) so the duty-cycle is a number in the range 0 to 65,535, with 0 being continuously off, and 65,535 continuously on. Everything else is duty_cycle periods of the underlying timer's count period. Do you mean pwm frequency? iRobotGoddard on "PWM dutyCycle" http://forums.leaflabs.com/topic.php?id=929#post-5745 Tue, 26 Jul 2011 11:02:50 +0000 iRobotGoddard 5745@http://forums.leaflabs.com/ Can someone explain how to alter your duty cycle on your PWM pins using the Maple rev5 based on the instrument you are controlling? For example if my pwm controlled component operates on 300MHz but the Maple operates on 16MHz how can we calculate, on the maple, how to change our duty cycle to fit the needs of the component? The issue is correctly programming the maple.