Why is running a preprogrammed collection not meeting the estimated time?

This is normal. There are a few things that can cause this to happen.

1. Delays sending the command to switch to another frequency can add seconds to the program.
2. The time to upload the waveform at the start can sometimes impact the timer.
3. Using a dwell multiplier like .35 does not always result in exact intergers and the estimated time can be off by a few rounding errors.

Just some examples.

If you note that the program was off by minutes, this may be due to frequencies in the set being blacklisted in the advanced menu and so they were skipped.

Another would be that the use of skip concurrent duplicate freq was in use and a frequency was skipped.

For more details, please check:

Was this article helpful?
0 out of 0 found this helpful



Please sign in to leave a comment.

Articles in this section

See more
Our Blog
Get the latest news and updates first
Our helpline hours:
9 AM – 6PM UTC+8, Monday – Friday
Video Guides
Learn how to use Spooky2 with our short, step-by-step video guides