the code compiles and runs flawlessly in proteus, thats not the issue , check your circuit
![]()
the code compiles and runs flawlessly in proteus, thats not the issue , check your circuit
![]()
Warning I'm not a teacher
Check for what?
If I replace TRISIO=%00101000 with TRISIO=%00001000, it will also work fine (but without a button).
put an oscilloscope/logic analyser on gpio.4 and see what the signal looks like or if you don't have one
put a led on gpio.4 in lieu of whats there now if it does not change state when gpio.5 is read then whatever is on gpio.4 is loading pin excessively.
or else your description of the problem maybe unclear or inaccurate
there are several of these
gosub sub9
i cant see a sub9 anywhere in your code
Warning I'm not a teacher
sub9 'subroutine for spinning - it is there
The whole circuit is assembled into box and potted with epoxy, so have no access to pins, except GPIO.5, I can check it with scope if needed.
only by mcs's good grace to call anything unknown a label, the colon is missingsub9 'subroutine for spinning - it is there
that would be me out .The whole circuit is assembled into box and potted with epoxy,
Warning I'm not a teacher
I potted it because it worked very fine, until I added that input parsing code
I can build another one, that is not an issue...
What is "next" doing? Is that a forgotten relic from previous versions?
low
tre
next
return
subzero:
Bookmarks