OK the scope can decode some stuff, so it's working at least.
As far as I can see, if CH3 is the clock, nothing changes on it's rising edges.
Try setting the trigger to Ch3 and add 100us of Holdoff.
This should give stable triggering and no need to Stop the scope.
Then you can set a much slower timebase, Stop the scope and H Pos (pan) through the packets.
Oscilloscope music was mentioned in another thread, and I wanted to see how this scope would do. I think it came out pretty well. I might eventually put more effort into making a better quality video. Or not. 🤷
Side note: it looked better as filmed at 120fps, but youtube cut that in half. Still looks pretty cool though.
Oscilloscope music was mentioned in another thread, and I wanted to see how this scope would do. I think it came out pretty well. I might eventually put more effort into making a better quality video. Or not. 🤷
Side note: it looked better as filmed at 120fps, but youtube cut that in half. Still looks pretty cool though.
Holy moly. An ultimate torture test for the AD converters. This is how we should test them.
@josh: Your settings are ?(horzionztal, memory, etc)
Btw:
In my attempts, the images are always upside down.
@josh: Your settings are ?(horzionztal, memory, etc)
Btw:
In my attempts, the images are always upside down.
10kpts for the memory to keep it faster/smoother. Going up higher either adds weird thickness, or slows it down.
horizontal I didn't bother adjusting in XY mode (maybe I was lucky?), the main thing was to make sure the mV/div was equal on X and Y. Settings are clear in the video at 00:26. Timebase 10bits, 100us/div, 10kpts, 10MSa/s; channels at DC50, 300mV/div.
If your images aren't oriented correctly (e.g. upside down), then you need to reverse the channel inputs (physically change which input L and R output are connected to).
When I tried to upgrade to V1.6.2R1 version, my scope froze and stopped responding. The standard combination of power and math softkeys for rebooting does not work either. Now only the proud name of Siglent is on the screen. This of course makes me happy, but I want something more.
Which firmware version do you currently have on it, the last one before this new update?
I'll leave it unplugged overnight to let it cool
. I'll try to repare it tomorrow.
When I tried to upgrade to V1.6.2R1 version, my scope froze and stopped responding. The standard combination of power and math softkeys for rebooting does not work either. Now only the proud name of Siglent is on the screen. This of course makes me happy, but I want something more.
Can you state the previous FW version ?
V1.5.2R3 ?
Should you need recovery assistance PM me with your email address.
I'll leave it unplugged overnight to let it cool . I'll try to repare it tomorrow.
There has been a situation where there may be upgrade issues when File Manager -> local space is very small. I'm not sure if this is the case with you.
Don't worry, it can be restored. Tautech has helped some people recover.
I'll leave it unplugged overnight to let it cool . I'll try to repare it tomorrow.
There has been a situation where there may be upgrade issues when File Manager -> local space is very small. I'm not sure if this is the case with you.
Don't worry, it can be restored. Tautech has helped some people recover.
Does NOT apply to SDS2000X Plus.
Please send PM and explain where you came across this info.
I'll leave it unplugged overnight to let it cool . I'll try to repare it tomorrow.
There has been a situation where there may be upgrade issues when File Manager -> local space is very small. I'm not sure if this is the case with you.
Don't worry, it can be restored. Tautech has helped some people recover.
Does NOT apply to SDS2000X Plus.
Please send PM and explain where you came across this info.
This is my guess, because other people have also upgraded this version without issues, so there is a difference on the machine, or the upgrade has not been completed and shut down, or the upgrade method may be different(udisk or web)?
Rigol 800 upgrade will prompt to ensure 200M Bytes of local space.
Hi,
just tried to update my SDS2000X+ to 1.6.2R2 with the same effect Famalex reported: the device hangs in the boot screeen
Previous version was 1.5.2R1 and I tried to update via the file manager and USB-stick
Hope there is help to fix this without sending the oscilloscope to Siglent ...
Hi,
just tried to update my SDS2000X+ to 1.6.2R2 with the same effect Famalex reported: the device hangs in the boot screen
Previous version was 1.5.2R1 and I tried to update via the file manager and USB-stick
Hope there is help to fix this without sending the oscilloscope to Siglent ...
Just reported to Siglent with urgency.
Currently I'm doing tests......Please be aware after this V1.6.2R1 installation first boot time will be 2+ minutes.....be patient.
PM me with your email.
Hi,
just tried to update my SDS2000X+ to 1.6.2R2 with the same effect Famalex reported: the device hangs in the boot screen
Previous version was 1.5.2R1 and I tried to update via the file manager and USB-stick
Hope there is help to fix this without sending the oscilloscope to Siglent ...
Just reported to Siglent with urgency.
Currently I'm doing tests......Please be aware after this V1.6.2R1 installation first boot time will be 2+ minutes.....be patient.
PM me with your email.
I had also a uggly experience on update:
. as using external USB stick
. fw gets loaded
. reboot as never gets in action
. tested again no any better
. then once complaining about low local space
. ok deleted all on the local disk
. tested again without success
. rebooted
. now it worked
the bug is that the space calculation is false as in addition more space is required to do a proper reboot and required fw update
All.
We are successfully recovering these boot freezes and successfully reinstalling the latest V1.6.2R1 firmware.
V1.6.2R1 has been pulled from websites.
In XY mode the timebase doesn't matter, because the scope is not plotting voltage*time, but voltage*voltage
Hi,
many thanks to tautech for the fast support
I could fix my scope and now version 1.6.2R1 is running :-)
Thanks to Tautech and everyone involved in solving this problem. I was the first victim of this bug, but apparently I will be the last to correct it. I just don't have free time.
I updated mine to 1.6.2R1 using the web interface.
As tautech says it did take much longer to start when it rebooted but it did eventually start.
Is the issue strictly when updating from USB or is it more "random"?
I updated from USB and had no issues at all.
Hello,
It seem that the V1.6.2R1 firmware has been removed, I don't find it anymore on
previously given.
Frex