28 Jan
2017
28 Jan
'17
2:21 p.m.
2. I would eliminate all the motor control stuff and just have the Basic code print a message on the screen, or turn a pixel off or on, to indicate it's intention to change the motor state. That way you can determine for certain that the problem is entirely within the Basic program.
Yup. Dan and I tried the same kind of thing. I did a simplified version just now: 70 IF B0>127 THEN PRINT "BUTTON ZERO ON" 100 IF B1>127 THEN PRINT "BUTTON ONE ON" Took out lines 80 and 110. It works as expected when running: nothing happens until I press either button, then the appropriate messages show up, and they stop when I release the buttons.