Loop mode should establish initial conditions (disconnected or connected) or block if in wrong state

[terrillmoore]

Ubuntu 20.04 LTS / XFCE / 2101

I am testing mass storage on an embedded host. Each pass takes about 47 seconds to run, so I set the test up at 60 seconds with a 90% duty cycle.

I pressed start without noticing that the switch was already on. I expected that either Cricket would turn off the switch and wait the off part of the duty cycle, or that it would refuse to start the loop ("need to start loop in disconnected state" or similar).

Suggested behavior: calculate the "off" time, and start by turning off for that period of time. Either add an extra half cycle (so that loop always ends in off) or end the loop in the starting state. (Preferred for test control is that the operator can specify the desired starting action (connect or disconnect) and then the program puts in the extra half cycle to make sure the test starts with a connect after minimum disconnect, or disconnect after minimum connect.