You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First i want to say thank you Tobias for a wonderful board. This little fella will be very usefull for my projects :D
I haven't had the time to look too much into it yet though, but i did test it out a little. I saw that the board has a feature to turn the wemos off completly by cutting J1. By cutting do you mean to remove a connection between the two pads? Mine came without any connection there and the images on this github page shows them not connected either. I tried to bridge the two pads by soldering them together, but this didn't change anything.
I assume by completely shutting off the wemos it shouldn't be able to turn back on again by a deepsleep timer, but only by a trigger from the MicroWakeupper right?
The text was updated successfully, but these errors were encountered:
The 2 pads are connected via a on board trace. Use a sharp knife and cut the trace between (on the board backside).
If you have a multimeter, switch to continuity and check if the 2 pads are not connected anymore.
Yes. Completely turned off until the next trigger event.
First i want to say thank you Tobias for a wonderful board. This little fella will be very usefull for my projects :D
I haven't had the time to look too much into it yet though, but i did test it out a little. I saw that the board has a feature to turn the wemos off completly by cutting J1. By cutting do you mean to remove a connection between the two pads? Mine came without any connection there and the images on this github page shows them not connected either. I tried to bridge the two pads by soldering them together, but this didn't change anything.
I assume by completely shutting off the wemos it shouldn't be able to turn back on again by a deepsleep timer, but only by a trigger from the MicroWakeupper right?
The text was updated successfully, but these errors were encountered: