Are there any hacks for Siglent 3303x-e power supply?

[n3mmr]

I thought I saw a mention of a hack for the FW of the Siglent 3303X-E power supply to enable 1mV set and readout accuracy, or at least 1mV resolution.

Does such a hack actually exist?

[tv84]

https://www.eevblog.com/forum/testgear/siglent-ads-firmware-file-format/msg1830584/#msg1830584

[tautech]

I thought I saw a mention of a hack for the FW of the Siglent 3303X-E power supply to enable 1mV set and readout accuracy, or at least 1mV resolution.

Does such a hack actually exist?

Sure does, tv84 linked it. 

Even for the X-E model, 1mV and 1mA resolution is available within the EasyPower software.

[rolfdegen]

Hallo siglent users

I hacked my new Siglent SPD3303X-E in to SiglenSPD3303X . I am verry happy 

Its verry easy:

First installed EasyPower from Siglent on my Win10 System

Then I install NI-VISA from National Instruments

Than start EasyPower

After that connect a LAN or USB cable

Press Connect symbol under Menu "File" and set in EasyPower 0.001V CH1 (press "Set)

Now press menu "Version"  > "Upgrade" > "Normal Mode" > "UpgradeFile" and load firmware file "SPD3303X-1.01.01.02.05_ConvertFromX-E" and press "Upgrade" and  wait a little bit to upgrade file (see a blue line on LCD screen to Siglent power supply). After this press ok and the Power Supply restart automatically.

It is very simple and nice. Thanks a lot 

My Siglent SPD3303X-E with 1mV and 1mA


Greetings from germany. Rolf

[boggis the cat]

It is very simple and nice. Thanks a lot 

Thank you for the instructions.  Worked fine on a new SPD3303X-E.

 

[MathWizard]

Yeah worked on my too. On a 500kcnt DMM, it tracks well. I have never really load tested it, at least not since I have the 1mV/1mA resolution.

It's pretty quiet, it's my 1st and only PSU, but compared to any wall powered device I've had on the scope, it looks very quiet, at low power anyways.

[Peter_O]

Just did it with a 3303X-E, bought in December.
Works without problems.
PS answers correct S/N to "IDN?" on command line, leaving possible Siglent database entries or the front sticker mismatch. I can live with that. 

Thanks a lot guys!

[xmas111]

Just did it with my 3303X-E too that I bought recently.

Working for me too but does anyone know how to get the "Set" and "Out" to read the same. Mine is off by 4 or 5 mv like in the picture 3 or 4 post above mine.

Thanks

[Tjuurko]

how to get the "Set" and "Out" to read the same

SPD3000X Series Service Manual
https://siglentna.com/download/14764/

Chapter 3  Calibration channel parameters

[xmas111]

Thank you very much!

The procedure might be a little over my head but I'm sure if I take my time I can do it.

Thanks again and I'll let everyone know how it goes.

[charliex]

just updated my X-E to an X. I think i went about it in a slightly different way to others (or i didn't see it being mentioned)

setup easypower and test connections
downloaded the SPD3303X_V1.01.01.02.07R2 firmware

it's easypower that decides if the firmware is the correct version for the device , so i ran it in the debugger, set a breakpoint at the check of the IDN? which is basically right before it says "This file does not match the device!" and set the IP to jump past the check ( swap the jz to a jnz) and continued the update.

Code: [Select]

0x0434B4D 0F BE 4D 0C                             movsx   ecx, [ebp+arg_4]
0x0434B51 3B C1                                   cmp     eax, ecx
0x0434B53 0F 84 A4 00 00 00                       jz      loc_434BFD              <<----- change this to jnz or just set the IP to the target location
0x0434B59 0F BE 55 0C                             movsx   edx, [ebp+arg_4]
0x0434B5D 83 FA FF                                cmp     edx, 0FFFFFFFFh
0x0434B60 0F 84 97 00 00 00                       jz      loc_434BFD
0x0434B66 6A 00                                   push    0           
0x0434B68 6A 00                                   push    0 
0x0434B6A 68 44 82 4F 00                          push    offset aThisFileDoesNo ; "This file does not match the device!"

no firmware mods were necessary.

IDN?
Technologies,SPD3303X,SPD3XIDD4R5442,1.01.01.02.07R2,V3.0

cheers,
charlie

[tv84]

no firmware mods were necessary.

Interesting find. 

In my proposal no software mods were necessary. 

[charliex]

yep this needs no mods to any of the software, just the  flow.

also there are other models listed in there, so might work for others too that are similar situations. the actual firmware update is just a couple of commands and they send over the firmware chunk at a time via visa and UPGRADE1

[xmas111]

just updated my X-E to an X. I think i went about it in a slightly different way to others (or i didn't see it being mentioned)

setup easypower and test connections
downloaded the SPD3303X_V1.01.01.02.07R2 firmware

it's easypower that decides if the firmware is the correct version for the device , so i ran it in the debugger, set a breakpoint at the check of the IDN? which is basically right before it says "This file does not match the device!" and set the IP to jump past the check ( swap the jz to a jnz) and continued the update.

Code: [Select]

0x0434B4D 0F BE 4D 0C                             movsx   ecx, [ebp+arg_4]
0x0434B51 3B C1                                   cmp     eax, ecx
0x0434B53 0F 84 A4 00 00 00                       jz      loc_434BFD              <<----- change this to jnz or just set the IP to the target location
0x0434B59 0F BE 55 0C                             movsx   edx, [ebp+arg_4]
0x0434B5D 83 FA FF                                cmp     edx, 0FFFFFFFFh
0x0434B60 0F 84 97 00 00 00                       jz      loc_434BFD
0x0434B66 6A 00                                   push    0           
0x0434B68 6A 00                                   push    0 
0x0434B6A 68 44 82 4F 00                          push    offset aThisFileDoesNo ; "This file does not match the device!"

no firmware mods were necessary.

IDN?
Technologies,SPD3303X,SPD3XIDD4R5442,1.01.01.02.07R2,V3.0

cheers,
charlie

Using this method do the "set" and "Actual Output" number match up, or are they still off a bit?

Thanks

[tautech]

just updated my X-E to an X. I think i went about it in a slightly different way to others (or i didn't see it being mentioned)

setup easypower and test connections
downloaded the SPD3303X_V1.01.01.02.07R2 firmware

it's easypower that decides if the firmware is the correct version for the device , so i ran it in the debugger, set a breakpoint at the check of the IDN? which is basically right before it says "This file does not match the device!" and set the IP to jump past the check ( swap the jz to a jnz) and continued the update.

Code: [Select]

0x0434B4D 0F BE 4D 0C                             movsx   ecx, [ebp+arg_4]
0x0434B51 3B C1                                   cmp     eax, ecx
0x0434B53 0F 84 A4 00 00 00                       jz      loc_434BFD              <<----- change this to jnz or just set the IP to the target location
0x0434B59 0F BE 55 0C                             movsx   edx, [ebp+arg_4]
0x0434B5D 83 FA FF                                cmp     edx, 0FFFFFFFFh
0x0434B60 0F 84 97 00 00 00                       jz      loc_434BFD
0x0434B66 6A 00                                   push    0           
0x0434B68 6A 00                                   push    0 
0x0434B6A 68 44 82 4F 00                          push    offset aThisFileDoesNo ; "This file does not match the device!"

no firmware mods were necessary.

IDN?
Technologies,SPD3303X,SPD3XIDD4R5442,1.01.01.02.07R2,V3.0

cheers,
charlie

Using this method do the "set" and "Actual Output" number match up, or are they still off a bit?

Thanks

Please study this thread:
https://www.eevblog.com/forum/testgear/how-to-calibrate-siglent-spd1000x-spd3303x-spd3303x-e-series-power-supplies/
Better still RTFM. 

[kevin.memi]

Thanks charliex!
Which debugger did you use? It seems there is another location where it checks and throws an error msg of "This file does not match the device!".

[AVGresponding]

Just scored an RS Pro rebranded one of these, it will be interesting to see if it can be firmware modded in the same way.

[tv84]

Thanks charliex!
Which debugger did you use? It seems there is another location where it checks and throws an error msg of "This file does not match the device!".

Why not do msg #2?   

Just scored an RS Pro rebranded one of these, it will be interesting to see if it can be firmware modded in the same way.

Don't see why not...

[AVGresponding]

Thanks charliex!
Which debugger did you use? It seems there is another location where it checks and throws an error msg of "This file does not match the device!".

Why not do msg #2?   

Just scored an RS Pro rebranded one of these, it will be interesting to see if it can be firmware modded in the same way.

Don't see why not...

Seems it's not so simple. I get the error "Failed to GetUpdateMode". This includes when trying to install the normal X-E update.

[tv84]

Seems it's not so simple. I get the error "Failed to GetUpdateMode". This includes when trying to install the normal X-E update.

Show me a FW file that you have been able to flash successfully.

[AVGresponding]

Seems it's not so simple. I get the error "Failed to GetUpdateMode". This includes when trying to install the normal X-E update.

Show me a FW file that you have been able to flash successfully.

How can I show you something that I don't have?   

The RS user manual states that the file type required is a .ugf and makes no mention of .ADS which may well be the issue.



EDIT: It just worked...   

I guess maybe the EasyPower software is a big buggy, it does hang a bit easily. It now thinks it's a Siglent and the serial number has changed.

[tautech]

Seems it's not so simple. I get the error "Failed to GetUpdateMode". This includes when trying to install the normal X-E update.

Show me a FW file that you have been able to flash successfully.

How can I show you something that I don't have?   

The RS user manual states that the file type required is a .ugf and makes no mention of .ADS which may well be the issue.



EDIT: It just worked...   

I guess maybe the EasyPower software is a big buggy, it does hang a bit easily. It now thinks it's a Siglent and the serial number has changed.

IIRC EasyPower accepts .ugf or ADS firmware files.
Some Siglent rebrands are reconfigured to only accept .ugf firmware.

[AVGresponding]

It was an .ADS file from tv84's .zip file in https://www.eevblog.com/forum/testgear/siglent-ads-firmware-file-format/msg1830584/#msg1830584 that worked, eventually.

The wasn't any difference in how I went about it from the other attempts, all I would say is I had to close the app a couple of times using the task manager when it hung.

The calibration does not appear to have been affected, it tracks perfectly (well within the combined specs) against my Keithley 2000 on both voltage and current.

[dschrier]

I got an SPD3303X-E yesterday and converted it to the X version based on the posts in this thread. The updated back to the latest X firmware from the Siglent site. (1.01.01.02.07R2)

Interesting thing happened. The MAC address is now set to ff:ff:ff:ff:ff:ff and will not get a DHCP address any longer (of course). I can assign a static IP and everything works as expected.

Wondering if anyone has seen this.

[optotester]

I just unlocked using the check bypass method and I kept my MAC address/serial number so it seems safer. You do not need a debugger by the way. The exe is not compressed so you can directly edit it with an hex editor like HxD.
1 - Open EasyPower.exe with an hex editor and look for 0F BE 55 0C (there is only one occurence)
2 - Just before that occurence, replace 0F 84 A4 00 00 00 by 0F 85 A4 00 00 00
3 - Flash the firmware using the new "no check version" of EasyPower you just created