I have a signal that gives a pulse once every second. My window is set to 1s/div, and the trigger position at 10%. So after a trigger it takes 9 seconds to fill the window. Then after 1 or 2 seconds a new trigger should be seen, and a new window written. But it takes up to 30 seconds before a new trigger is seen, meaning that a couple of dozen are ignored.
What gives? (.psdata file attached)
I have just tried using your psdata file, I then set the signal generator to generate a 2V 1Hz signal and it re triggers after 1 or 2 seconds as expected.
What signal are you using ?
Is it capturing data into the first division on the screen, but not triggering ?
The signal is a 1 pulse per second PWM signal, pulses are 100 or 200 ms wide (it's DCF77).
I don't see any data scrolling through the first division pre-trigger. It's just the previous data which appear frozen.
When I setup my scope anew it works as expected, but after I loaded the .psdata file the 30 seconds blackout returned (only it's now 40 seconds, whereas the 30 seconds I had before were rather consistent). Neither closing and reopening the program, nor shutting down and repowering the scope seems to help.
I set the timescale to 1ms/div and then triggering seems normal, but when I go up from there the blackouts return: about 5 seconds at 200ms/div, 15 seconds at 500ms/div to 40 seconds at 1s/div.
I also tried triggering on a faster signal (several kHz), but also then the 40 seconds blackout remains at 1s/div.
I wanted to do an uninstall/reinstall of the software (BTW v6.10.16.2), to see if there was anything with the settings mixed up. However, after reinstall I noticed my settings had been preserved (timebase, sub views, channels,... Even the window size). So I took out Revo Uninstaller Pro, which also cleans up the registry and remaining files.
Another reinstall, and the settings are still there. Which files do I have to delete for a clean slate?