Hello marmad,
thanks.
Best regard,
egonotto
The code DSA9LLL and VSA9LLL does also work on DS4014.
Thank you!
The code DSA9LLL and VSA9LLL does also work on DS4014.
Thank you!
Oh boy! The shit has really hit the fan now
All options enabled, bandwidth options not avail an DS4000. ?!
The keys are lost on powercycling.
Someone who owns a DG4000 series should give it a try it as well.
I just looked at the programming manual for the DG4000, and the INSTALL/UNINSTALL SCPI commands are not listed - but they may be undocumented (since it doesn't have purchasable options).
But it can be tested by just using the sequence I posted above for Ultra Sigma (but without the UNINSTALL command). After running the INSTALL command (if you don't get the 'Unsupported command' message), check the model number in System Info.
All options enabled, bandwidth options not avail an DS4000. ?!
The keys are lost on powercycling.
Did you check your model number in System Info after applying the code?
All options enabled, bandwidth options not avail an DS4000. ?!
The keys are lost on powercycling.
Did you check your model number in System Info after applying the code?
is the DS4/6 bandwith upgradeable at all ? - "DSA9" enables 5 options, on the ds2 thats the default 3 + 2x bandwith (100+200).
Someone who owns a DG4000 series should give it a try it as well.
I just looked at the programming manual for the DG4000, and the INSTALL/UNINSTALL SCPI commands are not listed - but they may be undocumented (since it doesn't have purchasable options).
But it can be tested by just using the sequence I posted above for Ultra Sigma (but without the UNINSTALL command). After running the INSTALL command, reboot the AWG and check the model number in System Info.
No, does not work, gives remote command error, in the key is has DS twice, so i think it is only for DS...
did change it in DG but no luck
Someone who owns a DG4000 series should give it a try it as well.
I just looked at the programming manual for the DG4000, and the INSTALL/UNINSTALL SCPI commands are not listed - but they may be undocumented (since it doesn't have purchasable options).
But it can be tested by just using the sequence I posted above for Ultra Sigma (but without the UNINSTALL command). After running the INSTALL command, reboot the AWG and check the model number in System Info.
Can you clarify which string you propose trying via SCPI on the DG? With the DG, it's presumably a model no., not a license thing
is the DS4/6 bandwith upgradeable at all ? - "DSA9" enables 5 options, on the ds2 thats the default 3 + 2x bandwith (100+200).
I don't think so - and only fully-implemented on the DS2000 in FW.03.
DS4K owners could try
LLLLLLL-RLGLLDS-DSB9LLL-LLLLLLL - enable 6 options
LLLLLLL-RLGLLDS-DSD9LLL-LLLLLLL - enable 7 options
LLLLLLL-RLGLLDS-DSH9LLL-LLLLLLL - enable 8 options
(typos fixed, argh ...)
Can you clarify which string you propose trying via SCPI on the DG? With the DG, it's presumably a model no., not a license thing
No need, it's just been checked on the DG - and doesn't work (SCPI command unsupported). But the code changes the model number on the DS2000 (in FW.03).
All options enabled, bandwidth options not avail an DS4000. ?!
The keys are lost on powercycling.
Did you check your model number in System Info after applying the code?
The modelnumber does not change.
DSB9LLL,DSD9LLL,DSH9LLL code works also.
@cybernet
really nice work !
DSA9 - 5 options is the maximum my DS accepts
as DS4 accepts
LLLLLLL-RLGLLDS-DSB9LLL-LLLLLLL - enable 6 options
LLLLLLL-RLGLLDS-DSD9LLL-LLLLLLL - enable 7 options
LLLLLLL-RLGLLDS-DSH9LLL-LLLLLLL - enable 8 options
you could try
LLLLLLL-RLGLLDS-DSR9LLL-LLLLLLL - enable 9 options
LLLLLLL-RLGLLDS-DS99LLL-LLLLLLL - enable 10 options
LLLLLLL-RLGLLDS-DT99LLL-LLLLLLL - enable 11 options
LLLLLLL-RLGLLDS-DV99LLL-LLLLLLL - enable 12 options
as well - this exhausts the available bits, so imho no more than 12 options are possible with their algos ...
you could try
LLLLLLL-RLGLLDS-DSR9LLL-LLLLLLL - enable 9 options
LLLLLLL-RLGLLDS-DS99LLL-LLLLLLL - enable 10 options
LLLLLLL-RLGLLDS-DT99LLL-LLLLLLL - enable 11 options
LLLLLLL-RLGLLDS-DV99LLL-LLLLLLL - enable 12 options
as well - this exhausts the available bits, so imho no more than 12 options are possible with their algos ...
lower codes doesnt work unfortunately.
I have done the following:
- Update to FW 03
- Enter code LLLLLLL-RLGLLDS-DSA9LLL-LLLLLLL
- Downgrade to FW 05
A big thank you to cybernet
So, does this mean that you can permanently change it to a 2202?
And back again to a 2072?
Does this enable all of the trial options too?
Looks like Christmas came early this year!
Another future owner of a DS2072, thanks to your work.
And repentant user of a SDS8102V, thanks to OWON work.
I have done the following:
- Update to FW 03
- Enter code LLLLLLL-RLGLLDS-DSA9LLL-LLLLLLL
- Downgrade to FW 05
Now 20Mhz, 100Mhz and OFF is available in the menu. Also, can I use the 2ns time base.
I see no difference to a DS2202.
Even after rebooting.
A big thank you to cybernet
Very interesting. One thing to consider - it would be worthwhile to discover a key to change the model numbers BACK to original numbers (2072 or 2102), since this could clearly be used as an indicator for voided warranty.
With firmware 03 on a DS2102 I entered your code and then did a self cal. Change to a 2202 seems to stay after a reboot and tested bandwidth is 200Mhz but the options are not retained.
A very big thank you to you all, although new to posting I have been following the DS2000 threads for a while and learnt a lot.
This is correct, however a simple re-entry of the code will re-enable the option goodness again.
AFAIK the FW code is still being prodded by some awesome people here
Please excuse my total ignorance of SCPI, so I may have this wrong.
It looks like a pretty simple task to make a USB dongle to enter the code a boot.
ie wait 15 sec after powerup for boot to complete send SCPI string - gross over simplification but you get the idea.
I have Tweeny 2.0 sitting here just waiting to do something really useful
http://www.pjrc.com/store/teensy.html
Please excuse my total ignorance of SCPI, so I may have this wrong.
It looks like a pretty simple task to make a USB dongle to enter the code a boot.
ie wait 15 sec after powerup for boot to complete send SCPI string - gross over simplification but you get the idea.
I think some people are still hoping for a hack of the official option keys - thus not requiring anything at boot-up. Meanwhile, I hope to release a version of RUU shortly which will send the code automatically on connect (as one temporary measure).
Please excuse my total ignorance of SCPI, so I may have this wrong.
It looks like a pretty simple task to make a USB dongle to enter the code a boot.
ie wait 15 sec after powerup for boot to complete send SCPI string - gross over simplification but you get the idea.
I think some people are still hoping for a hack of the official option keys - thus not requiring anything at boot-up. Meanwhile, I hope to release a version of RUU shortly which will send the code automatically on connect (as one temporary measure).
that would be great ! but as a fall back I could live with a dongle. Rainy weekend here, if I can finish running cables in the ceiling ( ready for the NBN Whoo hooo -100/40 Mb on the way) I will have a hack
Please excuse my total ignorance of SCPI, so I may have this wrong.
It looks like a pretty simple task to make a USB dongle to enter the code a boot.
ie wait 15 sec after powerup for boot to complete send SCPI string - gross over simplification but you get the idea.
I have Tweeny 2.0 sitting here just waiting to do something really useful
http://www.pjrc.com/store/teensy.html
Actually it's not that much of an over-simplification at all. I've been using a RPi to control my DS2000 to have a set of extra hot buttons. I wrote all the comms stuff for it using pyUSB and the USBTMC class is actually very simple to implement. However I've been using a RPi because I wanted a button to that when pushed, it would dump a BMP to a network drive and record audio from a USB mic until the button was released, and store the MP3 with the BMP. As a single button record capture if you will.
But it would be basic to port what I've done across to something like the Microchip USB framework, then any PIC with a USB OTG port could do this. I don't have any experience with the Atmel USB framework, so it's unlikely that I'd port it across to that (and I don't have any usb OTG AVRs.)
Tell you what, I'll add it into my RPi code and post this afternoon. There's probably way too many RPi's sitting around doing nothing at the moment anyway.
Actually it's not that much of an over-simplification at all. I've been using a RPi to control my DS2000 to have a set of extra hot buttons. I wrote all the comms stuff for it using pyUSB and the USBTMC class is actually very simple to implement. However I've been using a RPi because I wanted a button to that when pushed, it would dump a BMP to a network drive and record audio from a USB mic until the button was released, and store the MP3 with the BMP. As a single button record capture if you will.
But it would be basic to port what I've done across to something like the Microchip USB framework, then any PIC with a USB OTG port could do this. I don't have any experience with the Atmel USB framework, so it's unlikely that I'd port it across to that (and I don't have any usb OTG AVRs.)
Tell you what, I'll add it into my RPi code and post this afternoon. There's probably way too many RPi's sitting around doing nothing at the moment anyway.
Thanks Harv, I'll have a look when you post. The Tweeny is actually nice in that you can use arduino code for quick prototyping or C, plenty of GPIO for a button. I thnk it may well be overkill even for this. Let's hope I don't get stuck in the ceiling and get to it