Restriction Placement Affects Execution

#1

I’ve run across this issue with restriction placement a couple of times and am curious if there is a simple explanation for why this first example piston works:

ex1_piston
ex1_piston.png1178×477 21.5 KB

ex1_log

and this second one doesn’t …

ex2_piston
ex2_piston.png1178×409 19 KB

ex2_log

I assume I’m missing something obvious as usual? :thinking: :rofl:

#2

In the first, the piston will always run every 1 minute before encountering the restriction; the latter restricts it up front via the SHM statement before it will run every min if the condition is met.

J

#3

Yes, I get all that. Unfortunately, I wasn’t as clear as I needed to be, provided a somewhat misleading example and compounded the error by posting the wrong log snapshot for the second piston. Bad day, I guess. :roll_eyes:

Anyway, while tinkering with this a bit later I noted I was experiencing a lot of oddities in the way webCoRE (or perhaps ST) was behaving. So I rebooted my hub, performed a clean up & rebuild on webCoRE, and left everything for the next day (in case it was a remote ST issue). Sure enough, the next day it all worked as expected. So for now at least I’m going to forget about it and move on.

Thanks.