As this code is in its own module, any constants (led1, led2) should be declared ahead of a function where they're used (go_blink). This makes understanding scope a little easier for beginners, IMO. My only beef -- thanks for the tutorial!
Oh, and you are also on my recommendations list, since before spring arrived. I keep all the advanced electronic videos on the bottom, due to not that many people will probably go there, but if they do go there, they will find the best people about the raspberry pi machine. You are one of them people who actually helped me lay out my Pi the way I've got set up. Please know and see that I took your advice. If you look, you will find. I did EXACTLY AS YOU TAUGHT ME!-:)) I do not regret it. You are the best at my layout design. I took it right after you, in the very same image. I use a breadboard by itself as the power to all the other breadboards I have three on a Jamiko Breadboard set tray. I use the other, forth one as my power, separate from the Jamiko ones. The one I use came with an electronics kit, I bought and so far I only lost a light because I forgot a resistor. lol I can only hope you look at my Raspberry Pi videos. I hope you like them. Thanks so much again...
Excellent video!!! This modality definitely worked better for the code I am implement. Thank you very much, and look forward to checking out the rest of the tutorials :)
This is awesome! The new library is simple and easy to use. Love the event features. I have a problem with my button triggering multiple times with one press randomly. Is there a way to ignore multiple button presses within a specified time?
I've been facing problems with my project for weeks and your video solved it in seconds! If I want to use the same button on multiple screens to activate different functions, would I get the GPIO conflict error like what happens with the RPi.GPIO library?
You should not have conflicts with gpiozero as long as you implement/use your buttons correctly. Unfortunately RPi.GPIO makes button usage very difficult and this is why I do not recommend it.
You cannot simply replace an LED with a relay in a simple GPIO circuit. A relay draws too much power and it needs a flywheel diode - you will damage or destroy your Pi. I have an upcoming video on how to use a relay, so stay tuned.
The problem is you are not limiting the current through the pin if it's accidentally set as an output. I explained, more but it just got deleted by YT.
You can also accidentally connect 5V to GPIO or short 3.3V to GND etc. There is always an element of damage risk when you work with Pi headers directly. My suggestion is to keep circuits as simple as possible.
Very good tutorial, much better than anything else out there.
As this code is in its own module, any constants (led1, led2) should be declared ahead of a function where they're used (go_blink). This makes understanding scope a little easier for beginners, IMO. My only beef -- thanks for the tutorial!
Oh, and you are also on my recommendations list, since before spring arrived.
I keep all the advanced electronic videos on the bottom, due to not that many people
will probably go there, but if they do go there, they will find the best people about
the raspberry pi machine. You are one of them people who actually helped me lay out my
Pi the way I've got set up. Please know and see that I took your advice. If you look,
you will find. I did EXACTLY AS YOU TAUGHT ME!-:)) I do not regret it. You are the best at
my layout design. I took it right after you, in the very same image. I use a breadboard
by itself as the power to all the other breadboards I have three on a Jamiko Breadboard
set tray. I use the other, forth one as my power, separate from the Jamiko ones. The one
I use came with an electronics kit, I bought and so far I only lost a light because I forgot
a resistor. lol I can only hope you look at my Raspberry Pi videos. I hope you like them.
Thanks so much again...
Thank you for your kind comment!
Excellent video!!! This modality definitely worked better for the code I am implement. Thank you very much, and look forward to checking out the rest of the tutorials :)
Glad it helped!
This is a very helpful tutorial. I am planning to use this sort of code along with PYQT5 to create a water tank automation.
This is awesome! The new library is simple and easy to use. Love the event features. I have a problem with my button triggering multiple times with one press randomly. Is there a way to ignore multiple button presses within a specified time?
Button class has a "bounce_time" property - set it to an appropriate value to counteract bounce.
I've been facing problems with my project for weeks and your video solved it in seconds! If I want to use the same button on multiple screens to activate different functions, would I get the GPIO conflict error like what happens with the RPi.GPIO library?
You should not have conflicts with gpiozero as long as you implement/use your buttons correctly. Unfortunately RPi.GPIO makes button usage very difficult and this is why I do not recommend it.
Thank you so much, just that global you put it there, really really kills ,e/
Thank you, can i replace the LED to a relay and just press button ON and press same button OFF.
You cannot simply replace an LED with a relay in a simple GPIO circuit. A relay draws too much power and it needs a flywheel diode - you will damage or destroy your Pi. I have an upcoming video on how to use a relay, so stay tuned.
Great video!!! Thanks a lot
I keep readying that if you have a button you need to attach a resistor to it to protect the pi. Is that true?
Raspberry Pi has software-controlled pull-up/pull-down resistors integrated in the chipset. This is why buttons are attached directly to the Pi.
amazing 🙌
The problem is you are not limiting the current through the pin if it's accidentally set as an output. I explained, more but it just got deleted by YT.
You can also accidentally connect 5V to GPIO or short 3.3V to GND etc. There is always an element of damage risk when you work with Pi headers directly. My suggestion is to keep circuits as simple as possible.
Helpful thanks
No problem!