I'd like to see the subroutines that Lego supplies to change the ports/bits. A "port" usually means an 8 bit wide I/O thing -- 8 bits that are all written at one time, because they share an address. A "bit" is one single wire in a port. Did you try taking the original program, and replacing ALL gosubs with print statements? You want to see if there are extra unexpected writes to the "wrong" motor. Bill This email is free of malware because I run Linux. On Sat, Jan 28, 2017 at 3:02 PM, Evan Koblentz via vcf-midatlantic < vcf-midatlantic@lists.vintagecomputerfederation.org> wrote:
Try moving lines 60, 70, 80 to be located AFTER 90, 100, 110, i.e. change their line numbers to 116,117,118. If the new order of operations causes the other motor to stutter, then the culprit is probably the I/O writes, as per my previous email.
Already tried that. Thought I mentioned it in the original message. The result of that experiment is it's still the bit/port/motor controlled by button 0 that stutters, even though the button 1 code comes first.