- Wed Jun 01, 2016 7:23 am
#48387
It's not my code, it's your published V3 interrupt example, using 0 for gpio00 instead of d3 which is apparently nodeMCU specific.
And yes, it would appear that one or other of the two alpha patches has subsequently fixed the V3 problem that was causing the interrupt example to abort with an error on my non-nodeMCU hardware - in fact I can even run your unmodified d3 code on my non-nodeMCU now without aborting on error!
But no, it certainly is still not working correctly or as expected on my non-nodeMCU hardware. Which must now be something for someone else to pursue, because the fact that you say it is working correctly for you puts me right back into similar Deja Vu isolation as with my non-working imagebuttons of 3 weeks ago.
Code: Select all
interrupt 0, [change]
wait
[change]
if io(laststat,0) = 1 then print "Pin put high" else print "Pin put low"
wait
And yes, it would appear that one or other of the two alpha patches has subsequently fixed the V3 problem that was causing the interrupt example to abort with an error on my non-nodeMCU hardware - in fact I can even run your unmodified d3 code on my non-nodeMCU now without aborting on error!
Code: Select all
interrupt d3, [change]
wait
[change]
if io(laststat,d3) = 1 then print "Pin put high" else print "Pin put low"
waitBut no, it certainly is still not working correctly or as expected on my non-nodeMCU hardware. Which must now be something for someone else to pursue, because the fact that you say it is working correctly for you puts me right back into similar Deja Vu isolation as with my non-working imagebuttons of 3 weeks ago.
