Search Results

I found a similar issue when I developed code to display on a VGA monitor. The reason for the slight jitter is that when an interrupt fires, it can't stop in the middle of an instruction. So there ar …

frequency desired const long timer1_OCR1A_Setting = F_CPU / 1000; const byte outputPin = 10; // Timer 1 "B" output: OC1B void setup() { pinMode (outputPin, OUTPUT); // set up Timer 1 // Fast PWM … top at OCR1A TCCR1A = bit (WGM10) | bit (WGM11) | bit (COM1B1); // fast PWM, clear OC1B on compare TCCR1B = bit (WGM12) | bit (WGM13) | bit (CS10); // fast PWM, no prescaler OCR1A = timer1_OCR1A_Setting …

Timer 1 on the Atmega328P (such as is found on the Uno) to get you into that ball park: const unsigned long countTo = 33658; // F_CPU / 8 / 29.71 / 2 void setup () { pinMode (10, OUTPUT); // PWM … , top at OCR1A TCCR1A = bit (WGM10) | bit (WGM11); // PWM TCCR1B = bit (WGM13) | bit (CS11); // PWM, prescaler of 8 OCR1A = countTo - 1; // zero relative OCR1B = (countTo / …

two PWM signals together into a AC signal. … Then there was a transformer and RC filter to smooth out and amplify the PWM. Sorry I can't be more help, but it was a while ago, and I didn't make all of it. …

The other answers about the way you can configure the timers are very good, but Edgar Bonet's comment goes to the heart of the matter. Do you need accuracy? Your example of 98.23Hz suggests that you …

kHz: const byte LED = 3; // Timer 2 "B" output: OC2B const long frequency = 50000L; // Hz void setup() { pinMode (LED, OUTPUT); TCCR2A = bit (WGM20) | bit (WGM21) | bit (COM2B1); // fast PWM … , clear OC2B on compare TCCR2B = bit (WGM22) | bit (CS21); // fast PWM, prescaler of 8 OCR2A = ((F_CPU / 8) / frequency) - 1; // zero relative OCR2B = ((OCR2A + 1) / 2) - 1; …

Based on my understanding though, sending analog signals to a non-PWM pin would just check for a threshold and send either LOW or HIGH, as opposed to being able to send variable voltages to a PWM pin. … What is the point of PWM pins if its also possible to send variable high/low signals to non-PWM pins? Well, the PWM pins output high/low signals asynchronously. …

The lower prescalers will give you finer control. The bigger prescalers necessarily have coarser control. From my web page about timers is this table of prescalers: n -- Prescale 1 -- -- Prescal …

TCCR2A = bit (WGM20) | bit (COM2B1) | bit (COM2A1) | bit (COM2A0); TCCR2B = bit (CS21); // phase correct PWM, prescaler of 8 OCR2A = dutyCycle; // duty cycle out of 255 … OCR2B = 255 - dutyCycle; // duty cycle out of 255 } // end of setup void loop() { } How it works The code uses Timer 2 (an 8-bit timer) to count up to 255 in phase-correct PWM mode. …

Using this slightly modified version of your code: // A sketch that creates an 8 MHz, 50% duty cycle PWM and a 250 kHz, // 6-bit resolution PWM with varying duty cycle (changes every 5 µs // or about …

Something like this should work: With this code on a Uno: void setup () { } void loop () { analogWrite (3, analogRead (A0) / 4); } For slightly more details see my post about doing that.

The comment by the OP under the question is: I meant how do I set the OC1A pin when i'm using the clear-on-match CTC mode (and vice versa) I know toggle changes it every match, but I don't understand …

Do the PWM pins accept current whilst low? The pins sink current when low. And yes, that is commonly done. The pins are not "do nothing" at LOW, and "put 5V there" at HIGH. …

PWM, fast PWM or something else) and whether each output should be the same or different frequencies. According to the Leonardo product page: PWM: 3, 5, 6, 9, 10, 11, and 13. … Provide 8-bit PWM output with the analogWrite() function. So even if you lose two to Timer 0, you should have 5 outputs left (it looks like the "B" side of Timer 1 and Timer 4 share the same pin). …

Why my loops are very complicated? OK, here is your loop: uint8_t fade_seq; // <--- initially zero void loop() { loop1: fade_seq++; while (fade_seq==1) { fade_red(1); } Serial.println(fade_ …