state change detection in the 21st century

[Terrypin]

All of the LED action takes place in the last few lines of the program.

Code: [Select]

if (buttonPushCounter % 4 == 0)
Until the first button press, buttonPushCounter = 0.  0 % 4 = 0 so the LED is HIGH.  
Unless the buttonPushCounter is greater than 0 do not turn the LED on.

Code: [Select]

if (buttonPushCounter % 4 == 0 && buttonPushCounter > 0)
   {
      digitalWrite(ledPin, HIGH);
      }
  
   else
   {
      digitalWrite(ledPin, LOW);
   }

Thanks, understood.

[windoze_killa]

*I find Eagle and KiCad too complex for the simple boards that I make.

I have used Altium for years but since I am trying to avoid Windoze like the plague and I am now using Linux I have installed KiCad and for a freebie it is awesome. Maybe a bit complex for simple stuff but I make some not quite so simple stuff.

[dougp]

Code: [Select]

buttonState = digitalRead(buttonPin);
 In the 21st century, "buttonState" doesn't have global scope (it wouldn't be a Boolean either)

+ reply #3


Would bool buttonState = (bool) digitalRead(buttonPin); be more correct?

[TheMemberFormerlyKnownAsAWOL]

Code: [Select]

bool buttonState = digitalRead(buttonPin) == HIGH; Might be. Or maybe even "== LOW"

[runaway_pancake]

Is the issue bad form?

If my sketch has --
bool pbState;
and 
pbState = digitalRead(pb);
then

if (pbState)

works [correlating 1, HIGH, true; 0, LOW, false)]

[aarg]

If truth be told, HIGH and LOW are very prosaic names. If they weren't already all over the Arduino planet, I'd be quite happy using 0 and 1 for I/O states.

[larryd]

_5volts
_0volts



VCC
GND

[TheMemberFormerlyKnownAsAWOL]

_5volts
_0volts

No - discriminatory towards the 3.3V variants

[lastchancename]

Just being pedantic...

It would be nice to flip your initial schematics horizontally to depict signal flow from left to right...
Just a thought to introduce the learners to logical schematic layout.

You did well with positive higher, and negative lower.

Sorry !