Most recent activity
-
i'm not sure I understand what you mean, but for the time being, the issue is resolved. i just wanted to understand exactly what limitations there are on watches interfering.
the encoders i'm using: https://www.amazon.com/Cylewet-Encoder-15%C3%9716-5-Arduino-CYT1062/dp/B06XQTHDRR/ref=sr_1_4?ie=UTF8&qid=1522902358&sr=8-4&keywords=rotary+encoder -
update - i just tried a2/a3/a4 while i also have i2c on b2 and it's working fine.. i also am watching B14 and it's not interfering with A4 .. so that's a bit confusing, but i guess good enough.
if there are conditions aside from 'same exact number on the pin', please let me know -
I know in the docs it says you can't mix pins like A0 and B0 because they end in the same number, but it appears it goes for A2 / B12 as well. Is this right??
Assuming I want to use all my available pins for setWatch, does that limit me to 10 max?I have a project where I am using 2 pins for I2c and then I need 9 pins watched for 3 rotary encoders with buttons. Is this doable on the pico or original espruino? if not, what are my multiplexing options? (i'm a beginner with muxing)
-
I tried taking out setConsole.. still seems to need a delay. would probably be a good idea to have some sort of an event for 'ready' rather than 'init' if it's an issue of internal processing time to get things going..
-
i suppose i2c initialization could take longer? any way to make it asynchronous?
-
that worked! now can someone explain why? I also noticed that taking the 1500 delay down to 1000 fails as well - does the board inherently have some issue with 'settling' for 1.5 seconds?
I have a project where I'd like to pulse a buzzer. right now i'm using setInterval as I read that digitalPulse should only be used for short durations (in the microseconds). I also recently realized that pwm can be used for this purpose.
the one thing i dont like about setInterval is that it makes the code harder to read with various nested intervals if I want to have different buzz patterns. why does it say digitalpulse should only be used for short intervals? is there some problem if I want to have it on for a second? or a half second?
which of these will yield best power utilization as well? it's not super-critical but if one is 10x more power than another, i'll do the power efficient one.
thanks!