if(){} else{} if(){} VS if(){} else if(){} in PWM control












0












$begingroup$


I'm using timer0 and a gpio pin to generate a 300Hz PWM signal on an ATmega2560.



The details if you care: F_CPU=16M, timer clock prescaler /256, count_max=208



The frequency changes depending on if I use an "if(){} else{} if(){}" or an "if(){} else if(){}".
The first generates 300Hz and the second generates 244Hz. Below is the code that generates the correct frequency. If I delete the curly brackets after the first two else's, I get 244Hz. 



void pwm_on(uint8_t duty){

    if(TCNT0 <= duty){ //portion of counter active

        PORTB |= (1<<7); //turn on PB7

    } else {}

    if(TCNT0 >= duty){ //portion of counter inactive

        PORTB &= ~(1<<7);//turn off PB7

    } else {}

    if(TCNT0 >= COUNT_MAX){ //if counter full

        TCNT0=0;//reset counter

    } else {}

}//pwm_on


Why am I getting such a significant frequency change with code that doesn't change the functionality?



Also calling this function is the only thing I do in Main after initializing.






pwm timer firmware







share|improve this question











$endgroup$








  • 2




    $begingroup$
    I'm voting to close this question as off-topic because it's a C syntax understanding problem and has nothing specifically to do with the hardware the code is running on.
    $endgroup$
    – brhans
    2 days ago










  • $begingroup$
    @brhans I edited the title of the question to specify it is for PWM control since that seems to be the largest point of contention for moving this question to stackoverflow. I am not a computer programmer and this is not a computer programming question. It is about how the syntax is affecting register level hardware timer0, NOT why doesn't this syntax work.
    $endgroup$
    – TammerTheHammer
    2 days ago






  • 1




    $begingroup$
    It doesn't really matter what the end application is - your problem is that you're not understanding standard C syntax. You would have this same problem if you were writing similarly structured code to run on a PC. The fact that you're writing firmware for a micro is only relevant in how this problem is presenting itself - it's just the symptom.
    $endgroup$
    – brhans
    2 days ago






  • 4




    $begingroup$
    Why aren't you using the perhipheral to generate the PWM for you? Which would allow you to dedicate zero CPU time to this task.
    $endgroup$
    – Attie
    2 days ago










  • $begingroup$
    @brhans I have only been asking about the symptom, that being the change in frequency. My understanding shouldn't matter since the question has always been about the symptom.
    $endgroup$
    – TammerTheHammer
    2 days ago
















0












$begingroup$


I'm using timer0 and a gpio pin to generate a 300Hz PWM signal on an ATmega2560.



The details if you care: F_CPU=16M, timer clock prescaler /256, count_max=208



The frequency changes depending on if I use an "if(){} else{} if(){}" or an "if(){} else if(){}".
The first generates 300Hz and the second generates 244Hz. Below is the code that generates the correct frequency. If I delete the curly brackets after the first two else's, I get 244Hz. 



void pwm_on(uint8_t duty){

    if(TCNT0 <= duty){ //portion of counter active

        PORTB |= (1<<7); //turn on PB7

    } else {}

    if(TCNT0 >= duty){ //portion of counter inactive

        PORTB &= ~(1<<7);//turn off PB7

    } else {}

    if(TCNT0 >= COUNT_MAX){ //if counter full

        TCNT0=0;//reset counter

    } else {}

}//pwm_on


Why am I getting such a significant frequency change with code that doesn't change the functionality?



Also calling this function is the only thing I do in Main after initializing.






pwm timer firmware







share|improve this question











$endgroup$








  • 2




    $begingroup$
    I'm voting to close this question as off-topic because it's a C syntax understanding problem and has nothing specifically to do with the hardware the code is running on.
    $endgroup$
    – brhans
    2 days ago










  • $begingroup$
    @brhans I edited the title of the question to specify it is for PWM control since that seems to be the largest point of contention for moving this question to stackoverflow. I am not a computer programmer and this is not a computer programming question. It is about how the syntax is affecting register level hardware timer0, NOT why doesn't this syntax work.
    $endgroup$
    – TammerTheHammer
    2 days ago






  • 1




    $begingroup$
    It doesn't really matter what the end application is - your problem is that you're not understanding standard C syntax. You would have this same problem if you were writing similarly structured code to run on a PC. The fact that you're writing firmware for a micro is only relevant in how this problem is presenting itself - it's just the symptom.
    $endgroup$
    – brhans
    2 days ago






  • 4




    $begingroup$
    Why aren't you using the perhipheral to generate the PWM for you? Which would allow you to dedicate zero CPU time to this task.
    $endgroup$
    – Attie
    2 days ago










  • $begingroup$
    @brhans I have only been asking about the symptom, that being the change in frequency. My understanding shouldn't matter since the question has always been about the symptom.
    $endgroup$
    – TammerTheHammer
    2 days ago














0












0








0





$begingroup$


I'm using timer0 and a gpio pin to generate a 300Hz PWM signal on an ATmega2560.



The details if you care: F_CPU=16M, timer clock prescaler /256, count_max=208



The frequency changes depending on if I use an "if(){} else{} if(){}" or an "if(){} else if(){}".
The first generates 300Hz and the second generates 244Hz. Below is the code that generates the correct frequency. If I delete the curly brackets after the first two else's, I get 244Hz. 



void pwm_on(uint8_t duty){

    if(TCNT0 <= duty){ //portion of counter active

        PORTB |= (1<<7); //turn on PB7

    } else {}

    if(TCNT0 >= duty){ //portion of counter inactive

        PORTB &= ~(1<<7);//turn off PB7

    } else {}

    if(TCNT0 >= COUNT_MAX){ //if counter full

        TCNT0=0;//reset counter

    } else {}

}//pwm_on


Why am I getting such a significant frequency change with code that doesn't change the functionality?



Also calling this function is the only thing I do in Main after initializing.






pwm timer firmware







share|improve this question











$endgroup$




I'm using timer0 and a gpio pin to generate a 300Hz PWM signal on an ATmega2560.



The details if you care: F_CPU=16M, timer clock prescaler /256, count_max=208



The frequency changes depending on if I use an "if(){} else{} if(){}" or an "if(){} else if(){}".
The first generates 300Hz and the second generates 244Hz. Below is the code that generates the correct frequency. If I delete the curly brackets after the first two else's, I get 244Hz. 



void pwm_on(uint8_t duty){

    if(TCNT0 <= duty){ //portion of counter active

        PORTB |= (1<<7); //turn on PB7

    } else {}

    if(TCNT0 >= duty){ //portion of counter inactive

        PORTB &= ~(1<<7);//turn off PB7

    } else {}

    if(TCNT0 >= COUNT_MAX){ //if counter full

        TCNT0=0;//reset counter

    } else {}

}//pwm_on


Why am I getting such a significant frequency change with code that doesn't change the functionality?



Also calling this function is the only thing I do in Main after initializing.






pwm timer firmware




pwm timer firmware






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited 2 days ago







TammerTheHammer

















asked 2 days ago









TammerTheHammerTammerTheHammer

729




729








  • 2




    $begingroup$
    I'm voting to close this question as off-topic because it's a C syntax understanding problem and has nothing specifically to do with the hardware the code is running on.
    $endgroup$
    – brhans
    2 days ago










  • $begingroup$
    @brhans I edited the title of the question to specify it is for PWM control since that seems to be the largest point of contention for moving this question to stackoverflow. I am not a computer programmer and this is not a computer programming question. It is about how the syntax is affecting register level hardware timer0, NOT why doesn't this syntax work.
    $endgroup$
    – TammerTheHammer
    2 days ago






  • 1




    $begingroup$
    It doesn't really matter what the end application is - your problem is that you're not understanding standard C syntax. You would have this same problem if you were writing similarly structured code to run on a PC. The fact that you're writing firmware for a micro is only relevant in how this problem is presenting itself - it's just the symptom.
    $endgroup$
    – brhans
    2 days ago






  • 4




    $begingroup$
    Why aren't you using the perhipheral to generate the PWM for you? Which would allow you to dedicate zero CPU time to this task.
    $endgroup$
    – Attie
    2 days ago










  • $begingroup$
    @brhans I have only been asking about the symptom, that being the change in frequency. My understanding shouldn't matter since the question has always been about the symptom.
    $endgroup$
    – TammerTheHammer
    2 days ago














  • 2




    $begingroup$
    I'm voting to close this question as off-topic because it's a C syntax understanding problem and has nothing specifically to do with the hardware the code is running on.
    $endgroup$
    – brhans
    2 days ago










  • $begingroup$
    @brhans I edited the title of the question to specify it is for PWM control since that seems to be the largest point of contention for moving this question to stackoverflow. I am not a computer programmer and this is not a computer programming question. It is about how the syntax is affecting register level hardware timer0, NOT why doesn't this syntax work.
    $endgroup$
    – TammerTheHammer
    2 days ago






  • 1




    $begingroup$
    It doesn't really matter what the end application is - your problem is that you're not understanding standard C syntax. You would have this same problem if you were writing similarly structured code to run on a PC. The fact that you're writing firmware for a micro is only relevant in how this problem is presenting itself - it's just the symptom.
    $endgroup$
    – brhans
    2 days ago






  • 4




    $begingroup$
    Why aren't you using the perhipheral to generate the PWM for you? Which would allow you to dedicate zero CPU time to this task.
    $endgroup$
    – Attie
    2 days ago










  • $begingroup$
    @brhans I have only been asking about the symptom, that being the change in frequency. My understanding shouldn't matter since the question has always been about the symptom.
    $endgroup$
    – TammerTheHammer
    2 days ago








2




2




$begingroup$
I'm voting to close this question as off-topic because it's a C syntax understanding problem and has nothing specifically to do with the hardware the code is running on.
$endgroup$
– brhans
2 days ago




$begingroup$
I'm voting to close this question as off-topic because it's a C syntax understanding problem and has nothing specifically to do with the hardware the code is running on.
$endgroup$
– brhans
2 days ago












$begingroup$
@brhans I edited the title of the question to specify it is for PWM control since that seems to be the largest point of contention for moving this question to stackoverflow. I am not a computer programmer and this is not a computer programming question. It is about how the syntax is affecting register level hardware timer0, NOT why doesn't this syntax work.
$endgroup$
– TammerTheHammer
2 days ago




$begingroup$
@brhans I edited the title of the question to specify it is for PWM control since that seems to be the largest point of contention for moving this question to stackoverflow. I am not a computer programmer and this is not a computer programming question. It is about how the syntax is affecting register level hardware timer0, NOT why doesn't this syntax work.
$endgroup$
– TammerTheHammer
2 days ago




1




1




$begingroup$
It doesn't really matter what the end application is - your problem is that you're not understanding standard C syntax. You would have this same problem if you were writing similarly structured code to run on a PC. The fact that you're writing firmware for a micro is only relevant in how this problem is presenting itself - it's just the symptom.
$endgroup$
– brhans
2 days ago




$begingroup$
It doesn't really matter what the end application is - your problem is that you're not understanding standard C syntax. You would have this same problem if you were writing similarly structured code to run on a PC. The fact that you're writing firmware for a micro is only relevant in how this problem is presenting itself - it's just the symptom.
$endgroup$
– brhans
2 days ago




4




4




$begingroup$
Why aren't you using the perhipheral to generate the PWM for you? Which would allow you to dedicate zero CPU time to this task.
$endgroup$
– Attie
2 days ago




$begingroup$
Why aren't you using the perhipheral to generate the PWM for you? Which would allow you to dedicate zero CPU time to this task.
$endgroup$
– Attie
2 days ago












$begingroup$
@brhans I have only been asking about the symptom, that being the change in frequency. My understanding shouldn't matter since the question has always been about the symptom.
$endgroup$
– TammerTheHammer
2 days ago




$begingroup$
@brhans I have only been asking about the symptom, that being the change in frequency. My understanding shouldn't matter since the question has always been about the symptom.
$endgroup$
– TammerTheHammer
2 days ago










2 Answers
2






active

oldest

votes


















5












$begingroup$

This is more a code syntax question. Could be offtopic, might be moved to stackoverflow.



if(){} else{} if(){} and if(){} else if(){} are different.

With correct indentation and brackets the issue is immediately visible:



if(){} else{} if(){}



if(condition){

  statement

}else{

  statement

}

if(condition){

  statement

}


And



if(){} else if(){} 



if(condition){

  statement

}else{

  if(condition){

    statement

  }

}





share|improve this answer









$endgroup$













  • $begingroup$
    i'm asking about the change in frequency (hardware) caused by the change in syntax (code) which is why I asked it here.
    $endgroup$
    – TammerTheHammer
    2 days ago






  • 7




    $begingroup$
    @TammerTheHammer Of course, but you should learn to use if-else-elseif statements to solve the puzzle. It's not the hardware, but your code.
    $endgroup$
    – Marko Buršič
    2 days ago






  • 1




    $begingroup$
    electronics.stackexchange.com/help/on-topic / @TammerTheHammer you asked in the right stack. this has been discussed many times before and some people try to redirect others to stackOverflow while actually you should ask here for softwares related to programming microcontrollers
    $endgroup$
    – Hasan alattar
    2 days ago






  • 2




    $begingroup$
    @TammerTheHammer Well, looking at the question tittle, people would think you are asking how to use if then statements.
    $endgroup$
    – Marko Buršič
    2 days ago






  • 1




    $begingroup$
    @TammerTheHammer You haven't asked how to use if-else, but that's only because you don't realize it's the root of your problem. code that doesn't change the functionality - here it is.
    $endgroup$
    – Agent_L
    2 days ago





















2












$begingroup$

The reason why my frequency goes down and the period goes up with the "if(){} else if(){}" is because TCNT0 >= duty is always true when TCNT0 >= COUNT_MAX so the last statement that resets the counter at COUNT_MAX never runs so my counter overflows instead of resetting at a count that gets me a frequency of 300Hz.



I figured it out pretty quickly after posting, sorry if I am misusing this site, I'm posting a question on meta to see what the collective thinks so I can learn and use this resource as best as possible.






share|improve this answer











$endgroup$









  • 4




    $begingroup$
    Posting of your own solution to a problem is encouraged.
    $endgroup$
    – AndrejaKo
    2 days ago










  • $begingroup$
    if you compile without optimaziation i think you will get same frequency but much lower than 244Hz anyway. i find it wierd that you right else {}. check this out : cpp.sh/3rcrt
    $endgroup$
    – Hasan alattar
    2 days ago












  • $begingroup$
    @Hasanalattar I'll need to research more on compiling before I'll understand this, but why I use else{} is because i learned misra-c standard in school and it was drilled into my brain that all if(){} statements must have its accompanying else{}.
    $endgroup$
    – TammerTheHammer
    2 days ago






  • 2




    $begingroup$
    Sidenote: To my understanding misra requires else{} only at the end of if ... else if constructs, and not on plain if statements.
    $endgroup$
    – user694733
    2 days ago






  • 1




    $begingroup$
    @TammerTheHammer I tried looking for that MISRA rule, and as far as I can tell there is no such rule. There is one for chained if .. else if ... else if ... which sort of make sense but for a simple if there is no need for an empty else
    $endgroup$
    – r_ahlskog
    2 days ago












Your Answer





StackExchange.ifUsing("editor", function () {
return StackExchange.using("mathjaxEditing", function () {
StackExchange.MarkdownEditor.creationCallbacks.add(function (editor, postfix) {
StackExchange.mathjaxEditing.prepareWmdForMathJax(editor, postfix, [["\$", "\$"]]);
});
});
}, "mathjax-editing");

StackExchange.ifUsing("editor", function () {
return StackExchange.using("schematics", function () {
StackExchange.schematics.init();
});
}, "cicuitlab");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "135"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2felectronics.stackexchange.com%2fquestions%2f429453%2fif-else-if-vs-if-else-if-in-pwm-control%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























2 Answers
2






active

oldest

votes








2 Answers
2






active

oldest

votes









active

oldest

votes






active

oldest

votes









5












$begingroup$

This is more a code syntax question. Could be offtopic, might be moved to stackoverflow.



if(){} else{} if(){} and if(){} else if(){} are different.

With correct indentation and brackets the issue is immediately visible:



if(){} else{} if(){}



if(condition){

  statement

}else{

  statement

}

if(condition){

  statement

}


And



if(){} else if(){} 



if(condition){

  statement

}else{

  if(condition){

    statement

  }

}





share|improve this answer









$endgroup$













  • $begingroup$
    i'm asking about the change in frequency (hardware) caused by the change in syntax (code) which is why I asked it here.
    $endgroup$
    – TammerTheHammer
    2 days ago






  • 7




    $begingroup$
    @TammerTheHammer Of course, but you should learn to use if-else-elseif statements to solve the puzzle. It's not the hardware, but your code.
    $endgroup$
    – Marko Buršič
    2 days ago






  • 1




    $begingroup$
    electronics.stackexchange.com/help/on-topic / @TammerTheHammer you asked in the right stack. this has been discussed many times before and some people try to redirect others to stackOverflow while actually you should ask here for softwares related to programming microcontrollers
    $endgroup$
    – Hasan alattar
    2 days ago






  • 2




    $begingroup$
    @TammerTheHammer Well, looking at the question tittle, people would think you are asking how to use if then statements.
    $endgroup$
    – Marko Buršič
    2 days ago






  • 1




    $begingroup$
    @TammerTheHammer You haven't asked how to use if-else, but that's only because you don't realize it's the root of your problem. code that doesn't change the functionality - here it is.
    $endgroup$
    – Agent_L
    2 days ago


















5












$begingroup$

This is more a code syntax question. Could be offtopic, might be moved to stackoverflow.



if(){} else{} if(){} and if(){} else if(){} are different.

With correct indentation and brackets the issue is immediately visible:



if(){} else{} if(){}



if(condition){

  statement

}else{

  statement

}

if(condition){

  statement

}


And



if(){} else if(){} 



if(condition){

  statement

}else{

  if(condition){

    statement

  }

}





share|improve this answer









$endgroup$













  • $begingroup$
    i'm asking about the change in frequency (hardware) caused by the change in syntax (code) which is why I asked it here.
    $endgroup$
    – TammerTheHammer
    2 days ago






  • 7




    $begingroup$
    @TammerTheHammer Of course, but you should learn to use if-else-elseif statements to solve the puzzle. It's not the hardware, but your code.
    $endgroup$
    – Marko Buršič
    2 days ago






  • 1




    $begingroup$
    electronics.stackexchange.com/help/on-topic / @TammerTheHammer you asked in the right stack. this has been discussed many times before and some people try to redirect others to stackOverflow while actually you should ask here for softwares related to programming microcontrollers
    $endgroup$
    – Hasan alattar
    2 days ago






  • 2




    $begingroup$
    @TammerTheHammer Well, looking at the question tittle, people would think you are asking how to use if then statements.
    $endgroup$
    – Marko Buršič
    2 days ago






  • 1




    $begingroup$
    @TammerTheHammer You haven't asked how to use if-else, but that's only because you don't realize it's the root of your problem. code that doesn't change the functionality - here it is.
    $endgroup$
    – Agent_L
    2 days ago
















5












5








5





$begingroup$

This is more a code syntax question. Could be offtopic, might be moved to stackoverflow.



if(){} else{} if(){} and if(){} else if(){} are different.

With correct indentation and brackets the issue is immediately visible:



if(){} else{} if(){}



if(condition){

  statement

}else{

  statement

}

if(condition){

  statement

}


And



if(){} else if(){} 



if(condition){

  statement

}else{

  if(condition){

    statement

  }

}





share|improve this answer









$endgroup$



This is more a code syntax question. Could be offtopic, might be moved to stackoverflow.



if(){} else{} if(){} and if(){} else if(){} are different.

With correct indentation and brackets the issue is immediately visible:



if(){} else{} if(){}



if(condition){

  statement

}else{

  statement

}

if(condition){

  statement

}


And



if(){} else if(){} 



if(condition){

  statement

}else{

  if(condition){

    statement

  }

}






share|improve this answer












share|improve this answer



share|improve this answer










answered 2 days ago









Jeroen3Jeroen3

11.6k1748




11.6k1748












  • $begingroup$
    i'm asking about the change in frequency (hardware) caused by the change in syntax (code) which is why I asked it here.
    $endgroup$
    – TammerTheHammer
    2 days ago






  • 7




    $begingroup$
    @TammerTheHammer Of course, but you should learn to use if-else-elseif statements to solve the puzzle. It's not the hardware, but your code.
    $endgroup$
    – Marko Buršič
    2 days ago






  • 1




    $begingroup$
    electronics.stackexchange.com/help/on-topic / @TammerTheHammer you asked in the right stack. this has been discussed many times before and some people try to redirect others to stackOverflow while actually you should ask here for softwares related to programming microcontrollers
    $endgroup$
    – Hasan alattar
    2 days ago






  • 2




    $begingroup$
    @TammerTheHammer Well, looking at the question tittle, people would think you are asking how to use if then statements.
    $endgroup$
    – Marko Buršič
    2 days ago






  • 1




    $begingroup$
    @TammerTheHammer You haven't asked how to use if-else, but that's only because you don't realize it's the root of your problem. code that doesn't change the functionality - here it is.
    $endgroup$
    – Agent_L
    2 days ago




















  • $begingroup$
    i'm asking about the change in frequency (hardware) caused by the change in syntax (code) which is why I asked it here.
    $endgroup$
    – TammerTheHammer
    2 days ago






  • 7




    $begingroup$
    @TammerTheHammer Of course, but you should learn to use if-else-elseif statements to solve the puzzle. It's not the hardware, but your code.
    $endgroup$
    – Marko Buršič
    2 days ago






  • 1




    $begingroup$
    electronics.stackexchange.com/help/on-topic / @TammerTheHammer you asked in the right stack. this has been discussed many times before and some people try to redirect others to stackOverflow while actually you should ask here for softwares related to programming microcontrollers
    $endgroup$
    – Hasan alattar
    2 days ago






  • 2




    $begingroup$
    @TammerTheHammer Well, looking at the question tittle, people would think you are asking how to use if then statements.
    $endgroup$
    – Marko Buršič
    2 days ago






  • 1




    $begingroup$
    @TammerTheHammer You haven't asked how to use if-else, but that's only because you don't realize it's the root of your problem. code that doesn't change the functionality - here it is.
    $endgroup$
    – Agent_L
    2 days ago


















$begingroup$
i'm asking about the change in frequency (hardware) caused by the change in syntax (code) which is why I asked it here.
$endgroup$
– TammerTheHammer
2 days ago




$begingroup$
i'm asking about the change in frequency (hardware) caused by the change in syntax (code) which is why I asked it here.
$endgroup$
– TammerTheHammer
2 days ago




7




7




$begingroup$
@TammerTheHammer Of course, but you should learn to use if-else-elseif statements to solve the puzzle. It's not the hardware, but your code.
$endgroup$
– Marko Buršič
2 days ago




$begingroup$
@TammerTheHammer Of course, but you should learn to use if-else-elseif statements to solve the puzzle. It's not the hardware, but your code.
$endgroup$
– Marko Buršič
2 days ago




1




1




$begingroup$
electronics.stackexchange.com/help/on-topic / @TammerTheHammer you asked in the right stack. this has been discussed many times before and some people try to redirect others to stackOverflow while actually you should ask here for softwares related to programming microcontrollers
$endgroup$
– Hasan alattar
2 days ago




$begingroup$
electronics.stackexchange.com/help/on-topic / @TammerTheHammer you asked in the right stack. this has been discussed many times before and some people try to redirect others to stackOverflow while actually you should ask here for softwares related to programming microcontrollers
$endgroup$
– Hasan alattar
2 days ago




2




2




$begingroup$
@TammerTheHammer Well, looking at the question tittle, people would think you are asking how to use if then statements.
$endgroup$
– Marko Buršič
2 days ago




$begingroup$
@TammerTheHammer Well, looking at the question tittle, people would think you are asking how to use if then statements.
$endgroup$
– Marko Buršič
2 days ago




1




1




$begingroup$
@TammerTheHammer You haven't asked how to use if-else, but that's only because you don't realize it's the root of your problem. code that doesn't change the functionality - here it is.
$endgroup$
– Agent_L
2 days ago






$begingroup$
@TammerTheHammer You haven't asked how to use if-else, but that's only because you don't realize it's the root of your problem. code that doesn't change the functionality - here it is.
$endgroup$
– Agent_L
2 days ago















2












$begingroup$

The reason why my frequency goes down and the period goes up with the "if(){} else if(){}" is because TCNT0 >= duty is always true when TCNT0 >= COUNT_MAX so the last statement that resets the counter at COUNT_MAX never runs so my counter overflows instead of resetting at a count that gets me a frequency of 300Hz.



I figured it out pretty quickly after posting, sorry if I am misusing this site, I'm posting a question on meta to see what the collective thinks so I can learn and use this resource as best as possible.






share|improve this answer











$endgroup$









  • 4




    $begingroup$
    Posting of your own solution to a problem is encouraged.
    $endgroup$
    – AndrejaKo
    2 days ago










  • $begingroup$
    if you compile without optimaziation i think you will get same frequency but much lower than 244Hz anyway. i find it wierd that you right else {}. check this out : cpp.sh/3rcrt
    $endgroup$
    – Hasan alattar
    2 days ago












  • $begingroup$
    @Hasanalattar I'll need to research more on compiling before I'll understand this, but why I use else{} is because i learned misra-c standard in school and it was drilled into my brain that all if(){} statements must have its accompanying else{}.
    $endgroup$
    – TammerTheHammer
    2 days ago






  • 2




    $begingroup$
    Sidenote: To my understanding misra requires else{} only at the end of if ... else if constructs, and not on plain if statements.
    $endgroup$
    – user694733
    2 days ago






  • 1




    $begingroup$
    @TammerTheHammer I tried looking for that MISRA rule, and as far as I can tell there is no such rule. There is one for chained if .. else if ... else if ... which sort of make sense but for a simple if there is no need for an empty else
    $endgroup$
    – r_ahlskog
    2 days ago
















2












$begingroup$

The reason why my frequency goes down and the period goes up with the "if(){} else if(){}" is because TCNT0 >= duty is always true when TCNT0 >= COUNT_MAX so the last statement that resets the counter at COUNT_MAX never runs so my counter overflows instead of resetting at a count that gets me a frequency of 300Hz.



I figured it out pretty quickly after posting, sorry if I am misusing this site, I'm posting a question on meta to see what the collective thinks so I can learn and use this resource as best as possible.






share|improve this answer











$endgroup$









  • 4




    $begingroup$
    Posting of your own solution to a problem is encouraged.
    $endgroup$
    – AndrejaKo
    2 days ago










  • $begingroup$
    if you compile without optimaziation i think you will get same frequency but much lower than 244Hz anyway. i find it wierd that you right else {}. check this out : cpp.sh/3rcrt
    $endgroup$
    – Hasan alattar
    2 days ago












  • $begingroup$
    @Hasanalattar I'll need to research more on compiling before I'll understand this, but why I use else{} is because i learned misra-c standard in school and it was drilled into my brain that all if(){} statements must have its accompanying else{}.
    $endgroup$
    – TammerTheHammer
    2 days ago






  • 2




    $begingroup$
    Sidenote: To my understanding misra requires else{} only at the end of if ... else if constructs, and not on plain if statements.
    $endgroup$
    – user694733
    2 days ago






  • 1




    $begingroup$
    @TammerTheHammer I tried looking for that MISRA rule, and as far as I can tell there is no such rule. There is one for chained if .. else if ... else if ... which sort of make sense but for a simple if there is no need for an empty else
    $endgroup$
    – r_ahlskog
    2 days ago














2












2








2





$begingroup$

The reason why my frequency goes down and the period goes up with the "if(){} else if(){}" is because TCNT0 >= duty is always true when TCNT0 >= COUNT_MAX so the last statement that resets the counter at COUNT_MAX never runs so my counter overflows instead of resetting at a count that gets me a frequency of 300Hz.



I figured it out pretty quickly after posting, sorry if I am misusing this site, I'm posting a question on meta to see what the collective thinks so I can learn and use this resource as best as possible.






share|improve this answer











$endgroup$



The reason why my frequency goes down and the period goes up with the "if(){} else if(){}" is because TCNT0 >= duty is always true when TCNT0 >= COUNT_MAX so the last statement that resets the counter at COUNT_MAX never runs so my counter overflows instead of resetting at a count that gets me a frequency of 300Hz.



I figured it out pretty quickly after posting, sorry if I am misusing this site, I'm posting a question on meta to see what the collective thinks so I can learn and use this resource as best as possible.







share|improve this answer














share|improve this answer



share|improve this answer








edited 2 days ago

























answered 2 days ago









TammerTheHammerTammerTheHammer

729




729








  • 4




    $begingroup$
    Posting of your own solution to a problem is encouraged.
    $endgroup$
    – AndrejaKo
    2 days ago










  • $begingroup$
    if you compile without optimaziation i think you will get same frequency but much lower than 244Hz anyway. i find it wierd that you right else {}. check this out : cpp.sh/3rcrt
    $endgroup$
    – Hasan alattar
    2 days ago












  • $begingroup$
    @Hasanalattar I'll need to research more on compiling before I'll understand this, but why I use else{} is because i learned misra-c standard in school and it was drilled into my brain that all if(){} statements must have its accompanying else{}.
    $endgroup$
    – TammerTheHammer
    2 days ago






  • 2




    $begingroup$
    Sidenote: To my understanding misra requires else{} only at the end of if ... else if constructs, and not on plain if statements.
    $endgroup$
    – user694733
    2 days ago






  • 1




    $begingroup$
    @TammerTheHammer I tried looking for that MISRA rule, and as far as I can tell there is no such rule. There is one for chained if .. else if ... else if ... which sort of make sense but for a simple if there is no need for an empty else
    $endgroup$
    – r_ahlskog
    2 days ago














  • 4




    $begingroup$
    Posting of your own solution to a problem is encouraged.
    $endgroup$
    – AndrejaKo
    2 days ago










  • $begingroup$
    if you compile without optimaziation i think you will get same frequency but much lower than 244Hz anyway. i find it wierd that you right else {}. check this out : cpp.sh/3rcrt
    $endgroup$
    – Hasan alattar
    2 days ago












  • $begingroup$
    @Hasanalattar I'll need to research more on compiling before I'll understand this, but why I use else{} is because i learned misra-c standard in school and it was drilled into my brain that all if(){} statements must have its accompanying else{}.
    $endgroup$
    – TammerTheHammer
    2 days ago






  • 2




    $begingroup$
    Sidenote: To my understanding misra requires else{} only at the end of if ... else if constructs, and not on plain if statements.
    $endgroup$
    – user694733
    2 days ago






  • 1




    $begingroup$
    @TammerTheHammer I tried looking for that MISRA rule, and as far as I can tell there is no such rule. There is one for chained if .. else if ... else if ... which sort of make sense but for a simple if there is no need for an empty else
    $endgroup$
    – r_ahlskog
    2 days ago








4




4




$begingroup$
Posting of your own solution to a problem is encouraged.
$endgroup$
– AndrejaKo
2 days ago




$begingroup$
Posting of your own solution to a problem is encouraged.
$endgroup$
– AndrejaKo
2 days ago












$begingroup$
if you compile without optimaziation i think you will get same frequency but much lower than 244Hz anyway. i find it wierd that you right else {}. check this out : cpp.sh/3rcrt
$endgroup$
– Hasan alattar
2 days ago






$begingroup$
if you compile without optimaziation i think you will get same frequency but much lower than 244Hz anyway. i find it wierd that you right else {}. check this out : cpp.sh/3rcrt
$endgroup$
– Hasan alattar
2 days ago














$begingroup$
@Hasanalattar I'll need to research more on compiling before I'll understand this, but why I use else{} is because i learned misra-c standard in school and it was drilled into my brain that all if(){} statements must have its accompanying else{}.
$endgroup$
– TammerTheHammer
2 days ago




$begingroup$
@Hasanalattar I'll need to research more on compiling before I'll understand this, but why I use else{} is because i learned misra-c standard in school and it was drilled into my brain that all if(){} statements must have its accompanying else{}.
$endgroup$
– TammerTheHammer
2 days ago




2




2




$begingroup$
Sidenote: To my understanding misra requires else{} only at the end of if ... else if constructs, and not on plain if statements.
$endgroup$
– user694733
2 days ago




$begingroup$
Sidenote: To my understanding misra requires else{} only at the end of if ... else if constructs, and not on plain if statements.
$endgroup$
– user694733
2 days ago




1




1




$begingroup$
@TammerTheHammer I tried looking for that MISRA rule, and as far as I can tell there is no such rule. There is one for chained if .. else if ... else if ... which sort of make sense but for a simple if there is no need for an empty else
$endgroup$
– r_ahlskog
2 days ago




$begingroup$
@TammerTheHammer I tried looking for that MISRA rule, and as far as I can tell there is no such rule. There is one for chained if .. else if ... else if ... which sort of make sense but for a simple if there is no need for an empty else
$endgroup$
– r_ahlskog
2 days ago


















draft saved

draft discarded




















































Thanks for contributing an answer to Electrical Engineering Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid …



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


Use MathJax to format equations. MathJax reference.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2felectronics.stackexchange.com%2fquestions%2f429453%2fif-else-if-vs-if-else-if-in-pwm-control%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







-

Popular posts from this blog

數位音樂下載

Image
數位音樂下載 為非以「實體」方式來販賣音樂的相關產品，而使用數位格式如mp3、AAC等文件格式來進行銷售販賣的一种音乐产业形式。著名的數位音樂下載服務商有iTunes Store、RecoChoku、Google Play音乐和微软Zune等。数字音乐下载在二十一世纪初一度风靡全球， [1] [2] 使得传统唱片产业走向衰落，但其自身也在2010年代流媒体音乐服务如Apple Music、Spotify等的挤压下迅速失去市场份额。 [3] [4] 数字音乐下载有便于携带、传播迅速、制作简单成本低等优点，与流媒体音乐相比也能更好保障音乐人权益； [5] 但它同时很可能带来侵犯版权和滥用的情形， [6] 也给音乐产业带来了诸多不利影响。数字音乐下载为音乐人和乐迷提供了更加便捷直接的交流渠道，也一定程度上推动了网络音乐人的出现和独立音乐的迅速发展。 [7] 目录 1 历史 1.1 技术积淀（1987-2000） 1.2 出现与兴起（2000-2004） 1.3 唱片市场的颠覆者（2004-2007） 1.4 巅峰和衰落（2005-2013） 1.5 摇摇欲坠的现状与不可预知的明天（2014至今） 2 主要文件格式 2.1 PCM编码格式 2.1.1 WAV 2.1.2 APE 2.1.3 FLAC 2.2 苹果推出的无损文件格式 2.2.1 AIFF 2.2.2 ALAC 2.3 有损压缩格式 2.3.1 MP3 2.3.2 AAC 3 主要市场 3.1 iTunes Store 3.2 Google Play音乐商店 3.3 亚马逊音乐商店 3.4 部分其他音乐商店 4 影响与评价 4.1 对音乐产业的影响 4.2 对科技行业的影响 4.3 正面评价 4.4 负面评价 4.4.1 侵权问题 4.4.2 经营模式不明晰 4.4.3 不适应移动时代 4.5 文化现象 5 延伸阅读 6 参考资料 历史 苹果iTunes+iPod的软硬件搭配让数字音...
Read more

When can things happen in Etherscan, such as the picture below?

Image
2 I don't know why balance of the address is 0. when can this situation? etherscan balances share | improve this question asked yesterday Ru Hi Ru Hi 11 1 New contributor Ru Hi is a new contributor to this site. Take care in asking for clarification, commenting, and answering. Check out our Code of Conduct. add a comment  |  ...
Read more

格利澤436b

Image
格利泽436b 太陽系外行星 太陽系外行星列表 艺术家笔下的格利泽436b 母恆星 母恆星 Gliese 436 星座 獅子座 赤經 ( α ) 11 h  42 m  11.0941 s [1] 赤緯 ( δ ) +26° 42′ 23.652″ [1] 距離 33.4 ly (10.2 pc) 光譜類型 M2.5 V [1] 軌道參數 半长轴 ( a ) 0.0291±0.0004 [2] AU 軌道離心率 ( e ) 0.150±0.012 [2] 公轉週期 ( P ) 2.643904±0.000005 [3] d (0.00723849 y) 軌道傾角 ( i ) 85.8 +0.21 −0.25 [3] ° 角距 ( θ ) 2.794 mas 近星點時間 ( T 0 ) 2,451,551.716 ±0.01 JD 半振幅 ( K ) 18.68±0.8 m/s 物理性质 质量 ( m ) 22.2±1.0 [2] M ⊕ 半徑 ( r ) 4.327±0.183 [2] [4] R ⊕ 密度 ( ρ ) 1.51 g cm -3 表面重力 ( g ) 1.18 g 溫度 ( T ) 712±36 [2] K 發現 發現時間 2004 發現者 巴特勒、沃格特、 馬西 et al. 發現方法 徑向速度、凌日法 發現地點 美國加利福尼亞州 發表論文 出版 其他名稱 Ross 905 b, GJ 436 b, [5] LTT 13213 b, GCTP 2704.10 b, LHS 310, AC+27:28217 b, Vyssotsky 616 b, HIP 57087 b, GEN# +9.80120068 b, LP 319-75 b, G 121-7 b, LSPM J1142+2642 b, 1RXS J114211.9+264328 b, ASCC 683818 b, G 147-68 b, UCAC2 41198281 b, BP...
Read more