Actions
Forum Thread Details
  • Replies 11 replies
  • Subscribers 388 subscribers
  • Views 2845 views
  • Users 0 members are here
Related

A question of Arduino timing

colporteur

I'm working on a small project that requires a three minute timer. Default with power up an LED comes on. Push a button an the LED goes out for three minutes and then lights again. It is a simple circuit using a few pins on an Arduino Nano and the code delay (180000) to get the three minutes. My middle school teaching daughter asked me to build the LED timer (I called it an egg timer) to assist a child in her classroom that has a learning disability.

 

The delay code is a brute force method of counting down time. I did some reading on millis() and thought maybe it is the better approach?

 

I don't have a need to manage other tasks while I wait for time, which is what I see millis() does (I think). I tried generating a block of code for the three minute timer using millis() with little success. I abandoned the exercise and used delay. I have a mental post it note to follow-up on the learning to create a working three minute timer using millis(). The code would count what ever time you set, in this case three minutes.

 

Any insight a member has to offer is welcome. I apologise up front, if my responses to any replies are dumb. I'm a resurrectionist rather than a programmer. I have enough knowledge to kludge together different code parts to create something. I lack the skills to actually program from scratch.

Parents

  • This worked OK for me on a UNO. It sets the board LED on for 3 minutes and then extinguishes it.

     

    void setup() {
    pinMode(13, OUTPUT);    // sets the digital pin 13 as output
    }

     

    void loop() {

    unsigned long myFinishTime;

    myFinishTime = millis() + 180000UL;

    digitalWrite(13, HIGH);

    do {}
      while(myFinishTime > millis());

    digitalWrite(13, LOW);

    do {}
      while (1);
    }

Reply

  • This worked OK for me on a UNO. It sets the board LED on for 3 minutes and then extinguishes it.

     

    void setup() {
    pinMode(13, OUTPUT);    // sets the digital pin 13 as output
    }

     

    void loop() {

    unsigned long myFinishTime;

    myFinishTime = millis() + 180000UL;

    digitalWrite(13, HIGH);

    do {}
      while(myFinishTime > millis());

    digitalWrite(13, LOW);

    do {}
      while (1);
    }

Children
  • in reply to jc2048

    If you want this running continuously, turning on/off for 3 minutes, you can adjust Jon's code slightly (I haven't compiled and run this but it should work ok):

     

    boolean currentState = true;
unsigned long delayTime = 180000; // required delay in milliseconds.

void setup()
     pinMode(13, OUTPUT);
}

void loop() {
     digitalWrite(13, currentState);
     unsigned long startTime = millis();
     while(millis () - startTime <= delayTime) {}; // overkill really, but subtraction avoids timer overflow issue - worth knowing
     currentState != currentState; // toggle currentState between true/flase (high/low)
}

     

    To change the interval, just change the value of delayTime on line 02.

     

    As an aside, and this won't impact this scenario where high accuracy isn't required and the duration is pretty low, the Arduino timer isn't very accurate over extended periods of time.

  • in reply to Andrew J

    I wondered whether to go into the wrap-around of the millis count, but decided not to (it was late at night when I did it and just testing the 3 minute interval seemed like an eternity; I certainly didn't feel like sitting there until the millis count wrapped round).

     

    Since an unsigned long, counting at millisecond intervals, takes 49.7 days to get to the fold around, it didn't seem like it would be too much of an issue for Sean in this particular case.

     

    Your line 11 isn't quite what you wanted.

  • in reply to jc2048

    Yes, I forgot to delete line 11!  I only put in the 'wrap-around' bit because Sean said he was learning and it's worth knowing - as is knowing that the millis() timer isn't very accurate over longer time spans.

  • in reply to Andrew J

    No, I meant you'd need to use it to initialise your startTime variable by setting it to what millis() returns at that moment.

  • in reply to jc2048

    Doh!  I see, yes.  I've updated the code.