Siglent SDG1000X Waveform Generators

[tautech]

Can someone please tell me how the heck I can save beeper:Off and Screensaver:ON ?

Every time I restart the unit, it goes back to the initial settings (beeper:On and Screensaver:Off)

Utility>System>Power On = Last ?

Also, is there a way to overwrite a saved file?

RTFM P78
https://int.siglent.com/upload_file/user/SDG1000X/SDG1000X_UserManual_UM0201X-E01D.pdf
2.12.1 Storage System

1. Can I somehow set the beeper and the scrnsaver to the settings I want for good and all. I have something like 20 saved files. Do I have to go through all of them to change the beeper and scrsaver settings? Also, I don't want to load the last setting when poering on. I want to load the initial settings with the beeper OFF nd the scrsaver OFF.

2. Unless I'm blind there's no mention about overwriting a file in the FM.

1. Unless you set Power On = Last you will always boot with default settings.
2. Overwrite ? What exactly do you want to do ?

[pope]

Can someone please tell me how the heck I can save beeper:Off and Screensaver:ON ?

Every time I restart the unit, it goes back to the initial settings (beeper:On and Screensaver:Off)

Utility>System>Power On = Last ?

Also, is there a way to overwrite a saved file?

RTFM P78
https://int.siglent.com/upload_file/user/SDG1000X/SDG1000X_UserManual_UM0201X-E01D.pdf
2.12.1 Storage System

1. Can I somehow set the beeper and the scrnsaver to the settings I want for good and all. I have something like 20 saved files. Do I have to go through all of them to change the beeper and scrsaver settings? Also, I don't want to load the last setting when poering on. I want to load the initial settings with the beeper OFF nd the scrsaver OFF.

2. Unless I'm blind there's no mention about overwriting a file in the FM.

1. Unless you set Power On = Last you will always boot with default settings.
2. Overwrite ? What exactly do you want to do ?

1. OK thanks

2. IF I make some changes to a saved file, I'd like to press ovewrite and save the changes instead of having to go through the process naming and saving again the file. I hope this makes sense.

[tautech]

2. IF I make some changes to a saved file, I'd like to press ovewrite and save the changes instead of having to go through the process naming and saving again the file. I hope this makes sense.

I don't believe you have the option to edit the file or filename from within the UI, therefore the only way to make those changes is to Save again but of course with a different filename or transfer to a USB stick, delete from the AWG file system then upload again, make your changes and Save.

Interesting dilemma ..... don't know of any AWG's in this price bracket that have a properly powerful File Manager.

[pope]

2. IF I make some changes to a saved file, I'd like to press ovewrite and save the changes instead of having to go through the process naming and saving again the file. I hope this makes sense.

I don't believe you have the option to edit the file or filename from within the UI, therefore the only way to make those changes is to Save again but of course with a different filename or transfer to a USB stick, delete from the AWG file system then upload again, make your changes and Save.

Interesting dilemma ..... don't know of any AWG's in this price bracket that have a properly powerful File Manager.

I don't think you should use a different name. For exmple, if I have a saved file called "X", I can do the following:

Load "X" -> make some changes -> press "save" -> Name the file "X" -> press "save"

Now, it seems like there is still one "X" file but with the new settings. So, kind of overwiting the old "X" file I suppos. I just don't want to go through all this process. I would much rather having a simple "Overwite" button.

[tautech]

Pope, do you have EasyWaveX installed on your PC ?
This might be another way around the limited capabilities of the SDG1000X file system.

[TurboTom]

...
Interesting dilemma ..... don't know of any AWG's in this price bracket that have a properly powerful File Manager.

DG800 / 900 / 2000:

Copy/Paste/Delete functions available, alphanumeric keypad for naming on touchscreen available, relatively comfortable navigation in drive/folder structure possible. It's simply a more modern approach to implementing a decent touchscreen and its integration into an AWG user interface. Siglent should really have a thorough look at an improved U/I of their legacy AWG poducts (SDG 1000 / 2000 / 6000) if they intend to be competitive with this range of instruments for some years to come.

For Reference, see Rigol's Manual, page 2-73 ff.

Edit: Manual link added

[pope]

Pope, do you have EasyWaveX installed on your PC ?
This might be another way around the limited capabilities of the SDG1000X file system.

I haven't installed it yet as I'm not interested in the arbitrary capabilities. Also, I don't feel like turning on the PC for such simple tasks 

[123rolle]

-Ok, after latest firmware it shows 1062X and works with 60MHz.-

I have 1032X and getting 1022X when removing the license. When I have only backups of original and original data in the NSP_system_info.xml file I am getting 1062X... ? Tried booting multiple times and always same thing.

Max freq is 60MHz though when it says 1022X. Only 30MHz when it says 1062X?

[BillyO]

Just a couple of questions.

Has anyone tried to create an SDG1000X license key using the python script or does that only work with scopes?

Would it be possible to update it to produce SDG license keys?

[tautech]

Just a couple of questions.

Has anyone tried to create an SDG1000X license key using the python script or does that only work with scopes?

Would it be possible to update it to produce SDG license keys?

Apparently.
See here:
https://www.eevblog.com/forum/testgear/siglent-sdg2042x-hack-door-closed/msg4018144/#msg4018144

[Sly]

First of all, I am a newbie here, thanks everyone for the awesome work you all have done.

I can confirm that updating the SDG1032X with the aforementioned script works.

There is no need for telnetting using the .ADS file unless you want to change PART II items like the max. Ramp frequency.
You can just telnet to port 5024 issuing SCPI commands. This option is on by default.

I replaced the NSP_system_info.xml with the original .xml file from my backup, changing it back to the original SDG1032X. Running the script and telnetting the SCPI commands I was able to change back to the SDG1062X.

I now have a working <bandwidth_update_licence> section for 60MHz using the '60M' option in the script. Becarefull you have to use the  SCOPEID variable to store the serial number. This is different than when using almost the same script for SDS devices. So please check if the output of the '30M' option matches your original license using the MCBD? query.

When using the MCBD XXXXXX command to set the new licence, get rid of all ['',''] characters first.

I you do use the telnet.ADS method, I found that the USB stick is found under /usr/bin/siglent/usr/mass_storage/U-disk0
which makes is easy to store the original and modified xml files externally.

Is there any reason not do it this way and just remove the license section? Does it make difference?

[BillyO]

Thanks.

I have no problem connecting to the AWG and I can issues the *IDN? command and get teh model and serial numbers, but it does not respond when I enter SCOPEID?.

Any suggestion?

Never mind.  I figured out you have to enter the model number as SDG1000X, not SDG1032X.

All good now and reporting as and running as a SDG1062X!

So, in improving my SDG1032X to SDG1062X performance, I followed this procedure

1. Telnet on port 5024 to the device.  Your telnet app should be setup for local echo.
2. Issue a MCBD? query.  This will return your current licence key.  Record this for later.
3. Issue a MD5_SRLN? query.  This will return you serial number.  Record this too.
4. Issue a MD5_PR? Query.  This will return your model number (should be SDG1000X)
5. Update the python script (below) such that SCOPEID and SN are set to your serial number.
6. Run the script.  It will return keys for a number of options.  Make sure the key for 30M matches the key you recorded in step 2 above.
7. If your key and the 30M key match exactly then note the key for 60M.  This is the one you will use.
8. Back at the telnet session issue the command MCBD 0123456789ABCDEF where 0123456789ABCDEF is whatever the python script returned for the 60M key.
9. Issue a *IDN? Command.  It should return a string that now identifies your unit as a SDG1062X.

Code: [Select]

import hashlib

SCOPEID = '0123456789ABCD' # Set to your serial number
SN = '0123456789ABCD' # Also set to your serial number
Model = 'SDG1000X'
          # 'SDG1000X', 'SDS1000X-E', 'SDS2000X-E', 'SDS2000X+', 'SDS5000X', 'ZODIAC-'

bwopt = ('25M', '30M', '40M', '50M', '60M', '70M', '100M', '150M', '200M', '250M', '300M', '350M', '500M', '750M', '1000M', 'MAX')
otheropt = ('AWG', 'WIFI', 'MSO', 'FLX', 'CFD', 'I2S', '1553', 'FG', '16LA')

hashkey = '5zao9lyua01pp7hjzm3orcq90mds63z6zi5kv7vmv3ih981vlwn06txnjdtas3u2wa8msx61i12ueh14t7kqwsfskg032nhyuy1d9vv2wm925rd18kih9xhkyilobbgy'

def gen(x):
h = hashlib.md5((
hashkey +
(Model+'\n').ljust(32, '\x00') +
opt.ljust(5, '\x00') +
2*(((SCOPEID if opt in bwopt else SN) + '\n').ljust(32, '\x00')) +
'\x00'*16).encode('ascii')
).digest()
key = ''
for b in h:
if (b <= 0x2F or b > 0x39) and (b <= 0x60 or b > 0x7A):
m = b % 0x24
b = m + (0x57 if m > 9 else 0x30)
if b == 0x30: b = 0x32
if b == 0x31: b = 0x33
if b == 0x6c: b = 0x6d
if b == 0x6f: b = 0x70
key += chr(b)
return key.upper()

for opt in bwopt:
print('{:5} {}'.format(opt, gen(SCOPEID)))

for opt in otheropt:
print('{:5} {}'.format(opt, gen(SN)))


[Ringmodulator]

Thank you for this hack!Works as described.

Still, the SDG1032X/1062X does not sync correctly to the external 10MHz input.
It works up to 30MHz output signal, but above it, the output frequency is too low.
At 50MHz it outputs around 49.9 MHz and is not stable.

FW 1.01.01.33R3

This problem does not exist with FW 1.01.01.33R1B6

Chris

[Wrenches of Death]

Still, the SDG1032X/1062X does not sync correctly to the external 10MHz input.
It works up to 30MHz output signal, but above it, the output frequency is too low.
At 50MHz it outputs around 49.9 MHz and is not stable.

FW 1.01.01.33R3

This problem does not exist with FW 1.01.01.33R1B6

Any idea if this problem also exists with "normal" SDG1062X models?

thanks
WoD

[Ringmodulator]

There are probably not that manny original 1062X arround.

With the license hack, there should not be any difference between them.

Most likely, this is a firmware bug.

Chris

Still, the SDG1032X/1062X does not sync correctly to the external 10MHz input.
It works up to 30MHz output signal, but above it, the output frequency is too low.
At 50MHz it outputs around 49.9 MHz and is not stable.

FW 1.01.01.33R3

This problem does not exist with FW 1.01.01.33R1B6

Any idea if this problem also exists with "normal" SDG1062X models?

thanks
WoD

[tubularnut]

I do have a real 1062X, plus a Leo Bodnar 10MHz GPS reference.

I'll set them up tomorrow, and let you know the outcome. I've not had any noticeable issues previously.

[Wrenches of Death]

I do have a real 1062X, plus a Leo Bodnar 10MHz GPS reference.

I'll set them up tomorrow, and let you know the outcome. I've not had any noticeable issues previously.

Much appreciated, and many thanks!

WoD

[Wrenches of Death]

There are probably not that manny original 1062X arround.

With the license hack, there should not be any difference between them.

Most likely, this is a firmware bug.

Agreed, but they may be more likely to fix it if it they know it doesn't just affect the hacked models.

WoD

[tubularnut]

Still, the SDG1032X/1062X does not sync correctly to the external 10MHz input.
It works up to 30MHz output signal, but above it, the output frequency is too low.
At 50MHz it outputs around 49.9 MHz and is not stable.

FW 1.01.01.33R3

This problem does not exist with FW 1.01.01.33R1B6

Chris

I've tested my SDG1062X on both FW 1.01.01.33R1B6 & 1.01.01.33R3.

Measured on an SDS2354X-Plus, and SVA1032X. 10MHz GPS sync from a Leo Bodnar Precision GPS Reference Clock to the SDG and SVA. External sync locks on with no issues.

Measurements are pretty close to 50MHz

Caveat: I'm not a metrology expert, I'm just showing what I see.

[Ringmodulator]

Hi tubularnut,

thanks for checking!

Interesting...

I have tested my unit again with two different GPSDOs and an ocxo, sin and sqare output, direct and 50ohm feedthrough.

The result is still the same:

FW 1.01.01.33R3 does not generate correctly above 30MHz.
With FW 1.01.01.33R1B6 it is OK.

My unit is a 1032X with license "hack".

Chris

[BillyO]

Still, the SDG1032X/1062X does not sync correctly to the external 10MHz input.
It works up to 30MHz output signal, but above it, the output frequency is too low.
At 50MHz it outputs around 49.9 MHz and is not stable.

FW 1.01.01.33R3

This problem does not exist with FW 1.01.01.33R1B6

Any idea if this problem also exists with "normal" SDG1062X models?

thanks
WoD

I have not tried the external reference yet, but it seems to me that once "improved" it does a fine job of tracking the internal reference.  I am not sure why using an external reference would make any difference al all.  It also seems a little odd that if the 1032 was substantially different hardware why it would even respond to the license to make it a 1062.  It seems like wasted effort on behalf of Siglent to create two different machines but then make them able to have the same functionality, run the same firmware and respond to the same license keys.

We need more data points

[Ringmodulator]

I dont think, that there is an issue with my setup, because with FW 1.01.01.33R1B6 this problem is not there and the unit works as expected, also above 30MHz.

There is a chance, that it is related to the hardware version.
My unit is 02-01-00-24-00 and identifies as SDG1062X. It was born as SDG1032X.

Chris

[Wrenches of Death]

I have tested my unit again with two different GPSDOs and an ocxo, sin and sqare output, direct and 50ohm feedthrough.

The result is still the same:

FW 1.01.01.33R3 does not generate correctly above 30MHz.
With FW 1.01.01.33R1B6 it is OK.

My unit is a 1032X with license "hack".

I have the same setup and problem here. I also tried attenuating the clock input signal with a couple of variable step attenuators to make sure that it wasn't being overdriven. They made no difference.

thanks!
WoD

[Wrenches of Death]

I dont think, that there is an issue with my setup, because with FW 1.01.01.33R1B6 this problem is not there and the unit works as expected, also above 30MHz.

There is a chance, that it is related to the hardware version.
My unit is 02-01-00-24-00 and identifies as SDG1062X. It was born as SDG1032X.

For what it's worth, mine has the same hardware revision. I just installed the older B6 firmware revision and it's stable as hell. I'd bet money that this is a firmware "issue" with the R3 revision.

thanks!
WoD


.

[nedeb]

I have just received my SDG1032X and everything looks good so far, except: the device freezes when I try to control it from the PC through USB (with LAN it works fine). Has anyone else experienced something like this, and is there any fix?

I'm using the following Python script:

Code: [Select]

#!/usr/bin/python3

import pyvisa as visa

rm = visa.ResourceManager('@py')

addr = 'USB0::62700::4355::SDG1XDCX6R2773::0::INSTR'

dev = rm.open_resource(addr)

# Uncommenting the following lines doesn't help:
#dev.write_termination = '\n'
#dev.read_termination = None
#dev.query_delay = 0.01

print(dev.query('*IDN?'))

(The device freezes immediately when I execute the script)