element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • About Us
  • Community Hub
    Community Hub
    • What's New on element14
    • Feedback and Support
    • Benefits of Membership
    • Personal Blogs
    • Members Area
    • Achievement Levels
  • Learn
    Learn
    • Ask an Expert
    • eBooks
    • element14 presents
    • Learning Center
    • Tech Spotlight
    • STEM Academy
    • Webinars, Training and Events
    • Learning Groups
  • Technologies
    Technologies
    • 3D Printing
    • FPGA
    • Industrial Automation
    • Internet of Things
    • Power & Energy
    • Sensors
    • Technology Groups
  • Challenges & Projects
    Challenges & Projects
    • Design Challenges
    • element14 presents Projects
    • Project14
    • Arduino Projects
    • Raspberry Pi Projects
    • Project Groups
  • Products
    Products
    • Arduino
    • Avnet Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • Store
    Store
    • Visit Your Store
    • Choose another store...
      • Europe
      •  Austria (German)
      •  Belgium (Dutch, French)
      •  Bulgaria (Bulgarian)
      •  Czech Republic (Czech)
      •  Denmark (Danish)
      •  Estonia (Estonian)
      •  Finland (Finnish)
      •  France (French)
      •  Germany (German)
      •  Hungary (Hungarian)
      •  Ireland
      •  Israel
      •  Italy (Italian)
      •  Latvia (Latvian)
      •  
      •  Lithuania (Lithuanian)
      •  Netherlands (Dutch)
      •  Norway (Norwegian)
      •  Poland (Polish)
      •  Portugal (Portuguese)
      •  Romania (Romanian)
      •  Russia (Russian)
      •  Slovakia (Slovak)
      •  Slovenia (Slovenian)
      •  Spain (Spanish)
      •  Sweden (Swedish)
      •  Switzerland(German, French)
      •  Turkey (Turkish)
      •  United Kingdom
      • Asia Pacific
      •  Australia
      •  China
      •  Hong Kong
      •  India
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      • Americas
      •  Brazil (Portuguese)
      •  Canada
      •  Mexico (Spanish)
      •  United States
      Can't find the country/region you're looking for? Visit our export site or find a local distributor.
  • Translate
  • Profile
  • Settings
Arduino
  • Products
  • More
Arduino
Arduino Forum Turning on the LED after a while.
  • Blog
  • Forum
  • Documents
  • Quiz
  • Events
  • Polls
  • Files
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Join Arduino to participate - click to join for free!
Actions
  • Share
  • More
  • Cancel
Forum Thread Details
  • State Verified Answer
  • +1 person also asked this people also asked this
  • Replies 18 replies
  • Answers 8 answers
  • Subscribers 393 subscribers
  • Views 3999 views
  • Users 0 members are here
  • led;
  • time
Related

Turning on the LED after a while.

sonys
sonys over 5 years ago

Hello everyone.

 

The task:

Use the button to turn on and off the LED after a while.

 

For example, we pressed a button - the LED turned on and went out after 10 seconds. And so it should turn itself on every 5 minutes for 10 seconds. Then, press the button and the LED stops working and until the next button press, it does not work.

 

What features are better to use? Or who has a similar example?

  • Sign in to reply
  • Cancel

Top Replies

  • jw0752
    jw0752 over 5 years ago +4 suggested
    Hi Sofiia, If you do not need to use an arduino I believe a dedicated circuit using two 555 timers and a flip flop will be able to produce this effect. John
  • shabaz
    shabaz over 5 years ago +3 suggested
    Hi Sofiia, To do this properly is quite an advanced thing. There's a capability inside the Arduino (it is slightly different depending on which Arduino you are using, but at a high level, the concept is…
  • ankur608
    ankur608 over 5 years ago +2 suggested
    For simplicity, you can replace your button with 'push on-off' or add an another 'tact switch' for the same. This will make your code routine much easier. Remember things that can't be reached with just…
Parents
  • shabaz
    0 shabaz over 5 years ago

    Hi Sofiia,

     

    To do this properly is quite an advanced thing. There's a capability inside the Arduino (it is slightly different depending on which Arduino you are using, but at a high level, the concept is the same) called a timer. The timer can be programmed to generate something called an 'interrupt' which calls a special function (called an interrupt service routine) regularly, for example every second.

    Then, you can use a global variable to count these 1-second ticks. Another global variable can be used to store state information related to (say) button press.

    Button-presses need debouncing, that is another topic too,

    To make a long story short, these two topics will require a lot of reading.

    Some resources are here:

    Timers and interrupts: https://learn.adafruit.com/multi-tasking-the-arduino-part-2/timers

    Button debounce: https://blog.adafruit.com/2009/10/20/example-code-for-multi-button-checker-with-debouncing/

    • Cancel
    • Vote Up +3 Vote Down
    • Sign in to reply
    • Verify Answer
    • Reject Answer
    • Cancel
Reply
  • shabaz
    0 shabaz over 5 years ago

    Hi Sofiia,

     

    To do this properly is quite an advanced thing. There's a capability inside the Arduino (it is slightly different depending on which Arduino you are using, but at a high level, the concept is the same) called a timer. The timer can be programmed to generate something called an 'interrupt' which calls a special function (called an interrupt service routine) regularly, for example every second.

    Then, you can use a global variable to count these 1-second ticks. Another global variable can be used to store state information related to (say) button press.

    Button-presses need debouncing, that is another topic too,

    To make a long story short, these two topics will require a lot of reading.

    Some resources are here:

    Timers and interrupts: https://learn.adafruit.com/multi-tasking-the-arduino-part-2/timers

    Button debounce: https://blog.adafruit.com/2009/10/20/example-code-for-multi-button-checker-with-debouncing/

    • Cancel
    • Vote Up +3 Vote Down
    • Sign in to reply
    • Verify Answer
    • Reject Answer
    • Cancel
Children
  • sonys
    0 sonys over 5 years ago in reply to shabaz

    I made sketches, look, please. I need to add time, but I'm already confused with the millis () function. Correct, if there's a mistake.

     

    class PauseFlasher
    {
      const unsigned long maxValue = 4294967295UL; // maximum counter value
    
      int ledPin; 
      long OnTime; 
      long OffTime; 
      long PeriodFlashing; 
      long PeriodPause; 
    
      int ledState; 
      int ledFlashing; 
      int keyState, oldKeyState; 
      unsigned long previousMillis;
      unsigned long previousFlashingMillis; 
      unsigned long previousKeyMillis;
    
      public:
      PauseFlasher(int pin, long on, long off, long flashing, long pause)
      {
       ledPin = pin;
       pinMode(ledPin, OUTPUT);
    
       OnTime = on;
       OffTime = off;
       PeriodFlashing = flashing;
       PeriodPause = pause;
    
       ledState = HIGH;
       ledFlashing = HIGH;
       keyState = LOW;
       oldKeyState = HIGH;
       previousMillis = 0; 
       previousFlashingMillis = 0; 
       previousKeyMillis = 0;
      }
    
      void Update()
      {
        unsigned long currentMillis = millis(); 
        unsigned long temp_time=0, temp_time1=0;
    
        if (currentMillis >= previousFlashingMillis) temp_time1 = currentMillis - previousFlashingMillis;
        else temp_time1 = maxValue - previousFlashingMillis + currentMillis;
    
        if ((ledFlashing==HIGH) && (temp_time1 >= PeriodFlashing))
        {
          ledFlashing = LOW; 
          previousFlashingMillis = currentMillis; 
          digitalWrite(ledPin, ledFlashing); 
          keyState = LOW;
          oldKeyState= HIGH;
        }
        if ((ledFlashing==LOW) && (temp_time1 >= PeriodPause))
        {
          ledFlashing = HIGH; 
          previousFlashingMillis = currentMillis ; 
          digitalWrite(ledPin, ledFlashing); 
          keyState = LOW;
          oldKeyState= HIGH;
        }
    
        if(ledFlashing==HIGH)
        {
          if (currentMillis >= previousMillis) temp_time = currentMillis - previousMillis;
          else temp_time = maxValue  - previousMillis + currentMillis;
          
          if((ledState == HIGH) && (temp_time >= OnTime))
          {
            ledState = LOW; // выключаем
            previousMillis = currentMillis; 
            digitalWrite(ledPin, ledState); 
          }
          else if ((ledState == LOW) && (temp_time >= OffTime))
          {
            ledState = HIGH; // включаем
            previousMillis = currentMillis ; 
            digitalWrite(ledPin, ledState); 
          }
        }
        if(ledFlashing==LOW)
        {
          if (digitalRead(2)==HIGH)
          {
            if(millis()-previousKeyMillis>100)
            {
              previousKeyMillis = millis();
              if(keyState==oldKeyState)
              {
                if(keyState==LOW) keyState=HIGH;
                else if(keyState==HIGH) keyState=LOW;
                digitalWrite(ledPin, keyState);
              }  
            }
          }
          else oldKeyState=keyState;
        }
      }
    };
    
    PauseFlasher led1(13, 100, 200, 5000, 15000);
    
    void setup(){}
    
    void loop()
    {
      led1.Update();
    }

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • Verify Answer
    • Reject Answer
    • Cancel
  • shabaz
    0 shabaz over 5 years ago in reply to sonys

    Hi Sofiia,

     

    The code is hard to follow, possibly line 54 might need changing from "if" to "else if" but I'm only guessing, I could only partially understand the code.

    You can use Serial.println to print out debug to try to get an idea where the code executes, and the values of variables to debug this, so that you can be sure that the values in the variables are what you expect.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • sonys
    0 sonys over 5 years ago in reply to shabaz

    Thanks. It remains to understand where to write what numbers (which I need), otherwise I’m already confused. Can you help me please?

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • beacon_dave
    0 beacon_dave over 5 years ago in reply to shabaz

    Another couple of potentially useful resources:

     

    Level Up Your Arduino Code: External Interrupts

    https://www.youtube.com/watch?v=J61_PKyWjxU

     

     

     

    Level Up Your Arduino Code: Timer Interrupts

    https://www.youtube.com/watch?v=2kr5A350H7E

     

     

    This one is not Arduino IDE but still a good introduction to the AVR peripherals such as GPIO and timer/counters:

     

    Getting Started With AVR

    https://www.youtube.com/playlist?list=PLtQdQmNK_0DRhBWYZ32BEILOykXLpJ8tP

    • Cancel
    • Vote Up +2 Vote Down
    • Sign in to reply
    • Verify Answer
    • Reject Answer
    • Cancel
  • shabaz
    0 shabaz over 5 years ago in reply to sonys

    There's no guideline on where to write the values, it just needs to be done wherever you suspect (after running the code and seeing the result for example) there could be an error, or wherever you want to be sure the value is changing as expected.

    You can comment them out afterwards if you don't need them after debugging.

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • Verify Answer
    • Reject Answer
    • Cancel
element14 Community

element14 is the first online community specifically for engineers. Connect with your peers and get expert answers to your questions.

  • Members
  • Learn
  • Technologies
  • Challenges & Projects
  • Products
  • Store
  • About Us
  • Feedback & Support
  • FAQs
  • Terms of Use
  • Privacy Policy
  • Legal and Copyright Notices
  • Sitemap
  • Cookies

An Avnet Company © 2025 Premier Farnell Limited. All Rights Reserved.

Premier Farnell Ltd, registered in England and Wales (no 00876412), registered office: Farnell House, Forge Lane, Leeds LS12 2NE.

ICP 备案号 10220084.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube