Most recent activity
-
I'm using Alkaline and have checked the 3.3v line, and it appears consistent.
I also hooked up a 5V power supply straight to the USB power and ground to see if there was something going on there, but same behaviour.
I do sometimes get good behaviour but other times I do not.
Is there a way to disable sleep mode? I'm wondering if that might be messing with it.
-
Thanks for responding!
I've attached my circuit diagram because I don't think there are any issues there.
I'm not printing any text, but am writing to the eeprom at every event. I don't think that would cause an issue but you would know better than I.
Everything is grounded together, and all components are being powered by the pico's 3.3v VDD so there should be no difference in voltage when on battery vs USB. (The diagram is incorrect in that aspect, it indicates that I've wired the PIR's directly to BAT)
No USB-TTL converter handy unfortunately :(
IF you think of any other possibilities I'd greatly appreciate it!
-
Hello,
I had a look and couldn't find any info on this so any help would be appreciated.
I have a pico hooked up to two PIR sensors (and an eeprom) and everything works great. I wave my hand in front of one sensor, and I get a trigger, I wave my hand in front of the other, and I get a different trigger (using pins B1 and A7 indicating the signals with an LED flash). This great behaviour happens when plugged into the USB connector.
Things go wrong when I power it with an external battery (3xAA). Everything still works, except every time I trigger one sensor, it's LED and then immediately the other LED blinks indicating that both sensors have tripped. I've gone back and forth between USB and battery power many times and can replicate the behaviour consistently. I've tried different pins (A2 and A4), am running v1.79 of the firmware, and don't know what's going on.
Using batteries is key to my project. Has anyone else experienced differences in behaviour like this and can anyone give me clues as to what might be going on?
Are you referring to deep sleep as being disabled by default? I used setSleepIndicator(LED1) to watch the sleep pattern and it definitely went to snoozetown (which is awesome!) I just am not sure what else could explain the different behaviours.
On an entirely unrelated note that may be of interest to you: After sending code that had some behaviour which included lighting up LED's upon pin event (worked great), I removed the bit of code that lit up the LED's but left everything else unchanged, and sent it again, the LED behaviour was the same as for the original code despite that code being gone (incorrect behaviour). I then left the code unchanged, reflashed the Pico and then sent the code again, now no LED behaviour (correct behaviour). It seems that ghost code was surviving and being called somehow. Not sure if that's at all useful to you...
I also just wanted to say: Thanks for making the Pico! It's a blast and definitely makes trying new concepts quick and easy.