If you have leds that are active low then make your program for active high leds and invert the outputs at the end, it's much easier to work with also for simulating the program when you test it with active high leds.
Debounce time is always located after the input contacts.
Look at Rlightshow (S/R) it's always set and 1 cycletime reset, for what reason? and what does it do?
Tue Dec 12 2017, 01:32:32
(no subject)(by Ziggy)
Any comments on variation in light output from LEDs?
Tue Dec 12 2017, 16:15:42
(no subject)(by MGP)
I can't see your leds or schematic, so I can only guess.
There are so many things that can go wrong... usually hardware or wrong setup.
A cycletime of 0.1mS is as for me too short, try 0.2mS or more.
Tue Dec 12 2017, 17:37:33
(no subject)(by Ziggy)
Determined what the problem was.
Code was poorly structured.
The LED drive conditions were not combined into a single statement but rather a number of rungs defining LED conditions.
Each rung would be calculated, do its thing and the net outcome would be an LED accessed multiple times per cycle.