Actually....you just need two 500Mhz probes
And...The new firmware 1.3.7R5 has been released!hh
https://www.siglenteu.com/service-and-support/firmware-software/digital-oscilloscopes/#sds2000x-plus
Good news! You just need to add 'SENT','MANC' in bwopt to unlock the new options!
https://repl.it/@wxq849034624/PrettyAbleGuiltware-1
You do whatever you want.
Yep. I found a new pair for 145€ plus shipping. Not a bad deal if they are genuine.
https://repl.it/@wxq849034624/PrettyAbleGuiltware-1
It does't work
Actually....you just need two 500Mhz probes
Yes, that's what I figured.And...The new firmware 1.3.7R5 has been released!hh
https://www.siglenteu.com/service-and-support/firmware-software/digital-oscilloscopes/#sds2000x-plus
Good news! You just need to add 'SENT','MANC' in bwopt to unlock the new options!
https://repl.it/@wxq849034624/PrettyAbleGuiltware-1
Nice. They care about fixing bugs.
I'd have loved if they actually fixed the trace display with a proper interpolation filter instead of providing another display option for the menu :-/
I see the glitches in the Bode plot were addressed. That's encouraging!
What was the verdict about the SPI protocol decoding errors? It seems they didn't fix that (yet)?
https://repl.it/@wxq849034624/PrettyAbleGuiltware-1
It does't work
https://repl.it/@wxq849034624/PrettyAbleGuiltware-1
It does't work
Yeah, same result here.
I steamed straight in and hit the run key which produced a full list of license keys but the MANC and SENT keys were rejected as invalid. It didn't help that the order in the scope list and their appearance in the Python output were switched but even after trying the proper keys in both upper and lower case, it then dawned on me that perhaps I should have replaced the '0000000000000000' place markers in the scope-id field. It made not one jot of difference. The same license keys were produced regardless not only of how I entered the scope-id or even whether I deleted that line altogether!
It's a little worrying that editing the scope-id makes no difference to its output. I've previously used an on-line python script to successfully generate license keys a couple of months back but I can't remember which hoops had to be jumped through so I think I'm simply doing something wrong (hopefully not giving my scope id away to a harvester).
John
I believe I found the problem with the linked script. It seems that that site no-longer allows you to change the python code and run it. For example, if you replace all of the code with "print('hello world')" you would think you'd get the string "hello world" when run, but you don't... at least I don't. It still runs the original code which means it's not using your scope ID.
If you take the code and run it in your own python interpreter it does actually work. I can confirm.
Also... that site seems to be giving me a crazy amount of verification images to click on just to make sure I'm human... way more then I've seen on any other site.
Also... that site seems to be giving me a crazy amount of verification images to click on just to make sure I'm human... way more then I've seen on any other site.
I believe I found the problem with the linked script. It seems that that site no-longer allows you to change the python code and run it. For example, if you replace all of the code with "print('hello world')" you would think you'd get the string "hello world" when run, but you don't... at least I don't. It still runs the original code which means it's not using your scope ID.
If you take the code and run it in your own python interpreter it does actually work. I can confirm.
Also... that site seems to be giving me a crazy amount of verification images to click on just to make sure I'm human... way more then I've seen on any other site.
After registration (even with fake email address) the script works very well.
https://repl.it/@wxq849034624/PrettyAbleGuiltware-1
I verified it on my scope.
If not, is it a problem with the architecture or should we expect it to appear in a newer firmware?