Arduino Adjustable Countdown Timer 

An diesem Punkt (3. Schalter zu Kommunikation 16) bin ich auch gescheitert. Ansonsten sehr gut erklärt👍 wenn man alles hat😉

I answer myself because I just tested it, the first question was common anode, and if you can change the pins so that it runs on arduino uno, you can use the analog inputs and make them outputs. Put the buzzer pin on pin1 that was free, button 3 on pin 0 and button 4 on A5. You have to declare it (int button4 = A5;) in the void setup (pinMode (A4, OUTPUT); so you can use the A0 A1 A2 A3 A4 and A5 of the arduino uno as outputs.

@@55dj55nava Thanks Antonio for testing this out! I am sure that it will be helpful for others. Sorry - I did not look into this page for some time and missed your question

@@dsavchuk1 Thanks for your answer, a greeting

@@55dj55nava Hi Antonio, I think you mentioned that you developed a 3d printed case that may work for this project. I can certainly add a link to it at the project site.

Thanks too! It's a good improvement :) That's what good about arduino - you can reprogram it to whatever is needed!

@@dsavchuk1 just start learning programming...

In the code, really close to the top where it says: int digit_pin[] = {6, 9, 10, 11} Instead of the 1st number being 6, turn it into 0

Is there a difference in brightness between the digits that are supposed to be lit and those that are not supposed to be lit? There were multiple reports that some light "bleeds" to other segments, but that seemed to be a hardware issue.

@@dsavchuk1 they all bright up but some of the segments is slightly brighter than some of the other segments. It is very hard to see the numbers or it might be like you said the hardware.

@@AeyZeiNS I'm sorry - I'm afraid that this not about the code, but about hardware, unfortunately. I'd try to check all the connections, but I assume that you've done this already.

@@dsavchuk1 double checked the connections as well and tried redoing it, results still the same. But I appreciate the help.

​@@AeyZeiNS if u still want it, on top change define DIGIT_ON LOW to HIGH and DIGIT_OFF HIGH to LOW and then in every case from 0-10 change SEGMENT_OFF to ON and OFF to ON its working for me

Thanks! Everything can be done - but the code has to be modified significantly, of course. The one in the project deals with the physical buttons. But several functions can be used.

@@dsavchuk1 I want to dose a manual coffee grinder by timing. In fact, I want to do Single espresso with a button, for example 4 sec. Double espresso, for example 8 seconds, with a button. however, since these times vary according to the size of the coffee bean, the moisture content in it, and the temperature of the gears of the mill, I have to intervene in the time. so I want to be able to change these times easily with a smart device android phone. This is actually what I'm trying to do.

@@muhammedmenap I never worked with the bluetooth module before. I hope that at some point will have time for that. The potential is certainly there.

@@dsavchuk1 You are absolutely right. Bluetooth is a great way to streamline the user interface in automation systems. Wireless is definitely important. I look forward to it with great impatience.

I am not sure if this setup can be done with 13 pins. There are more connections to be made in the scheme with the selected hardware. However, you can try to use TM1637 display that only needs 4 pins (see, for example, create.arduino.cc/projecthub/ryanchan/tm1637-digit-display-arduino-quick-tutorial-ca8a93). But then you will need to modify the code significantly too.

The black circle is the speaker

thanks , i was confused alot

how about for the pin 14 and 15? in arduino uno

Thank you

Did you mean Arduino Uno? If so, please see my answer to the question of Ray Rank below. You will need to change one of the pins.

I just took a regular piece of wire, cut it to necessary length, and stripped on two sides. But this is just so that the project looks nicer.

@@dsavchuk1 another question, can i copy the exact coding you give on your link? or do i need to change it a bit?

@@aaisyahhumaira3496 it should work if you just copy the code

Aside math.h, no other library is needed. And there is a way to go around math.h if needed as described in another comment. It also should work on Arduino Uno as well, but you may need to change the pins as the number of digital pins in UNO is one less than I used in this project in MEGA. You may try to use analog pins instead. If it will not work for the buttons, you can probably use them for segments to free up some digital pins. One of them is analog anyway, so it should work, I guess. For example, you can assign "int segF = A1;" and use digital pin 7 for the reset button. If this does not work, you can simply use pin 6 that currently corresponds to the first digit of the display. Then the countdown will be limited to 999, but still gives you something. Then you would need to change the first line of SwitchDigit function to "for (int i=1; i

@@dsavchuk1 thanks for the reply... highly appreciated...

hello...is there any way to make the start as both start and stop button? looking forward for your reply and highly appreciated it...thanks...more power

@@dsavchuk1 used pins 1 and 0 for 16 and 17 replacement..

You'll have to modify the code. But you can still use the functions related to the buttons.

can i ask you what is the little changes in the arduino uno? thanks

@@tanggooo I had to change some pins as you can see from the ide I used: drive.google.com/file/d/1BbM65IB5-t7GQVdbI71rUYhrAz3Cfh5p/view?usp=sharing I also had to change: #define DIGIT_ON LOW // per un display con catodo in comune (for a display with common cathode) #define DIGIT_OFF HIGH in: #define DIGIT_ON HIGH // per un display con anodo in comune (for a display with common anode) #define DIGIT_OFF LOW Moreover, to use the countdown for minutes instead of seconds, I changed the PrintNumber this way: void PrintNumber(int n, unsigned int time) { and in the loop: while (!Countdown(countdown_time, 59002)) { // instead of the 59962 suggested

i have the same problem - did you find a fix?

@@amangeee No, I didn't. As I used only the last two digits, it didn't bother me too much, so I didn't look for a solution for too long.

Maybe something like this will work for you: create.arduino.cc/projecthub/mattywausb/one-kitchen-timer-to-cook-it-all-1afdab?ref=search&ref_id=countdown%20timer&offset=10

i been at your situation but i tried to managed the issue I just transfer the start button at other pin because i think the pin 13 is also the pin use for the LED built in the arduino board, i transfer it and i changed at the set up instead of INPUT_PULLUP I changed it to just INPUT but the wiring also changed from Positive to button and button to the pin location...but i put a resistor from the pin to ground to prevent unnecessary noise....hope it will help...

ভাই ওয়েট করেন ,আমি টেস্ট করে সফল হলে আপনাকে জানাব

@@shoumikahmed6373 thanks 👍

@@shoumikahmed6373 Was the result of the experiment successful? And how to fix it?

@@bomboba6191 Yes, There was a small bug in the code..I had fixed that but forgot what I fixed. Thats was about 7 segment.I used common anode display..For that .... #define DIGIT_ON HIGH #define DIGIT_OFF LOW #define SEGMENT_ON LOW #define SEGMENT_OFF HIGH This will work...For common cathod you have to change High to Low. Now 2nd one... For relay take a variable int LEDPin =3;(You can take any pin and variable you want like Relaypin) at void setup pinMode (LEDPin,output); Now don't copy everything...I have changed many things..Just look where I used digital write LEDPin.. bool Countdown(int n, int del){ for (int q=n; q>0; q--){ PrintNumber(q,del); digitalWrite(LEDPin, HIGH); if (digitalRead(button2)==LOW) { return false; } } digitalWrite(LEDPin, LOW); PrintNumber(0,0); playTone(150,350); return true; } void reset() { int m, zeros, d, pressed3 = 0, pressed4 = 0; m=countdown_time; struct struct_digits dig; dig = IntToDigits(countdown_time); digitalWrite(LEDPin, LOW); while (digitalRead(button1)==HIGH) { for (int j=0; j 20) { if (countdown_time > 0) { countdown_time -= 1 ; } dig = IntToDigits(countdown_time); } pressed4 += 1; } else if (digitalRead(button3)==LOW) { if (pressed3 == 0 || pressed3 > 20) { if (countdown_time

@@moshiurrahmanmeraj6640 Vai..Kaj kore...Baniye felen.

Thanks! No, I did not work on selling it. So far it's been just a hobby

I did not install it manually and "#include " was enough for me. What chip do you have? There are some limitations according to www.arduino.cc/en/math/h They also have a reference to avr-libc library that probably can be installed if math.h is not found automatically. I only use that library for a function pow to compute 10^i, which may be an overkill. If installing a library does not work, you can add the following function: int pow10(int n) { int x=1; for(int i=0; i

Thanks! Just follow the link in the description to the project page on the arduino projecthub. It's all there

@@dsavchuk1 the code that you have shared tried to upload but did not work as it showed an error "FQBN not provided"

@@mantamang6452 It looks like this is a problem you have to solve on your side: support.arduino.cc/hc/en-us/articles/360020843439-Error-2-UNKNOWN-no-FQBN-provided

In line 289 of the code replace 962 by 59,968 and check if you get exactly minutes. You may need to adjust this number a bit to be more accurate. For example, after you do this modification, measure how long does it actually take for the timer to go down from 10 to 0. If it's a bit less than 10 minutes, increase that number a bit.

@@dsavchuk1 first off, awesome project! I'm trying to implement the changes you described to make it go by minutes, but the max value allowed in that function is "32000". 33,000 - thus 59,969 - automatically set off the buzzer. Any ideas or something else I need to change?

@@jesusjones1024 In line 215 change int time with unsigned in time : void PrintNumber(int n, unsigned int time) {

Well, this is because it takes roughly 38 milliseconds for arduino to complete the rest of the code per cycle. This, of course, can be done better for better accuracy, but I believe it will make the code more complicated. So this is kind of a compromise.

Perhaps the problem is resolved by now - the link does open up on my end