The scope is working again! Just a breeze, two files on FAT32 USB reboot wait a minute and it is up and running. Further I have the impression a new firmware release is coming up.
Look at screenshot, also the web interface is a bit different. Once in instrument control mode the left navigation stuff disappears and the only way back is via the history buttons of the browser. No big deal, don't know if it is intended or a bug.
The esc key does bring me back from full screen, but not back from the instrument control screen to the home screen, but as said no big issue here.
Well into OT. Time to move on...
Has anybody else noticed that Video Sync as a trigger option is not working as expected ?
I've set the trigger to PAL, on line 1 field 1, but it seems that at different timebases triggering happens at either field 1 or field 2 randomly; and sometimes on both field 1 and field 2.
There is no option for holdoff when Video is the trigger type, unless I'm completely blind and just not seeing it!
Bug:
Power on state is partly setting to defaults instead of last used, example given:
When awg is active and a waveform selected, then turning the scope off, turn it on - the awg remains off and the selected waveform has changed to "DC".
Wanted features:
Decoding: Bitrate displaying and search function adding (last is really useful).
Further it would be nice when decoding of ir-codes (like RC-5, RECS80, NEC ir..) could be added - Afaik none scope got this and therefore it would be unique feature.
AWG should be in the OFF mode after reboot for safety reasons.
Do any of the bugs and feature requests in this thread actually make their way to Siglent?
If not, what is the best route to use so that Bugs/Features do come to their attention?
Beta release of 1.3.5R6.
Further I noticed that the Bode plot never stops it goes over and over and over again. I do not know if that is itended behaviour, but it doesn't do any averaging it just writes over the last bode plot, so I see no use of it, so why not stop after one parse. Further as many others have notices there are sometimes strange dips or peaks in the bode plot.
I can see the use, if you are adjusting things and keep your hands free.
In my case I just want the bode plot of an existing circuit as is. And the point is, often the first parse is oke and the chance of getting strange dips and peaks seems to increase with the iterations. So I want it to stop after a single parse and still be able to walk away and grab some tea.
I had it a few times that the start of the bode plot was oke, I went away to have a drink, because even a single sweep takes time and when I'm back it is busy with a 2nd or 3th iteration and I have a glitch at the start of the bode plot and I have to wait till some iteration that I have no glitch.
I only need a single sweep without a glitch. I will read your link, to see if there if I can find something to lower the chance of having a glitch. But to me an option to either stop after a single sweep or run it continuously seems a valid thing.
Further if I do a sweep in REW via a sound card the sweep takes 10-20 seconds, the same here will take considerably longer. I know REW can not scale up to higher frequencies (but the resolution is much higher), but still in the same range the difference in time is huge. But given the time it takes, it is normal to walk away from it.