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

[tv84]

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

Although more universal that method is riskier since you can flash any FW... untested and/or improper versions also...

[juansalvo94]

Hello!

Do anyone know how to change the mac address of these power supplies? I've two of them and both have the same mac address, but i can't have them both plugged in lan network

best regards!

[tautech]

Hello!

Do anyone know how to change the mac address of these power supplies? I've two of them and both have the same mac address, but i can't have them both plugged in lan network

best regards!

Welcome to the forum.

There is a new bug introduced in V1.01.01.02.07R2 firmware and not present in V1.01.01.02.05 where the  IP address is not saved correctly.
The patch files below corrects this until a full firmware version is released.

Note
Remove the txt file extension and install the ADS file in the normal way.

[d4db0d]

Hopefully it is alright to dredge up an old topic. I wanted to save someone some time and/or heartache.

I purchased a SPD3303X-E that arrived with hardware version V6.1 and software version V1.01.01.03.10. I didn't pay too much attention to this and tried tv84's procedure from the original link in this thread. EasyPower warned me that the firmware did not match, which I should have heeded but am too stupid to quit. I performed the EasyPower hex edit and forced the firmware update and was met with a dead unit.

 

During my panic searching and self-loathing, I couldn't find any recovery instructions. I figured Siglent had some sort of bootloader or firmware update methodology, and held all the buttons while powering it up. Found that holding the adjust knob in while powering on boots to the firmware load screen, huzzah!

Firmware Recovery Steps (Hardware V6.1)

• Download SPD3303X-E V1.01.01.03.10 ADS from Siglent
• Power off
• Hold adjust knob in
• Power on. Device should boot in firmware mode.
• Start EasyPower -> Version -> Upgrade
• Choose firmware mode and select the SPD3303X-E V1.01.01.03.10 firmware*

*Note: I used the hex-edited EasyPower exe for this, but should work without it

While researching, I found that hardware V6.1 was incompatible with the previous (V1.01.01.02.yy) versions of the firmware, which was likely causing the issue.

After getting through all that, I was able to send the SDS3303X OS using the hex edited EasyPower. Doing this removed my cal coefficients, so I calibrated the unit using https://www.eevblog.com/forum/testgear/siglent-sds3303x(-e)-calibration-fw1-01-01-02-07r2-best-practice/ and it's working like a clock!

Hope this helps, and thanks to everyone for the great tools and documentation.

[akkk44]

Glad you succeed! My 3303X-E will just boot into the firmware upgrade state after I directly upload the firmware of 3303X into it using the modified easypower.exe. Did I miss something?
-edit:
I didn't read the Release Notes first. It stated that: "B. < V6.1 hardware version of SPD3303X/X-E do not support upgrading to this version (SPD3303X_V1.01.01.03.10.ADS)". The result was the PSU will boot into the firmware update screen after reboot.

[tautech]

Glad you succeed! My 3303X-E will just boot into the firmware upgrade state after I directly upload the firmware of 3303X into it using the modified easypower.exe. Did I miss something?

Welcome to the forum.

Maybe check your hardware is V6.1 or for an earlier version for which you must use the correct FW version.

[akkk44]

Thank you, My Hardware version was V3.0. I am trying to get NI MAX to recognize my PSU but so far I had no luck. I have both the USB and LAN connected, NI MAX can see a USB VISA device but can not do a thing, and it can't see the PSU on LAN although easypower can. Maybe I missed a driver or something?
-Edit:
I installed labview with NI package manager and now I can connect to the PSU with LAN. Maybe something needed was installed along side the labview.

[tautech]

Thank you, My Hardware version was V3.0. I am trying to get NI MAX to recognize my PSU but so far I had no luck. I have both the USB and LAN connected, NI MAX can see a USB VISA device but can not do a thing, and it can't see the PSU on LAN although easypower can. Maybe I missed a driver or something?

Quite likely.

If you download the free EasyPower SW and read the install instructions, it requires NIVISA Runtime at the least (smaller package than NIVISA full install) for the connectivity drivers.
https://int.siglent.com/upload_file/zip/software/Power_Supply/EasyPower_1.01.01.18.zip

What is your PC OS ?
Some think they know best and install the incorrect driver especially for USB and that needs be removed and the correct one linked to the device.

Files attached for guidance.

[akkk44]

Thanks a lot for the kindness!
I will briefly describe what I have done for future me or anyone interested:
Note: I have a 3303X-E with hardware version 3.0
- Download and install Easypower from Siglent, modify easypower.exe per @optotester's instruction.
- Download and install NI package manager.
- Install NI-VISA, NI MAX, and "LabView and drivers" from NI package manager. (I think it is the "driver" included by "LabView and drivers" that matters.)
- Connect to the PSU via LAN in NI MAX. Once done, the VISA test panel will be available.
- Write the "FACTORY ON" SCPI command per @tv84's instruction. (May not be necessary)
- Upgrade the PSU with this firmware (SPD3303X-1.01.01.02.05.ADS)
- The PSU will reboot and become 3303X

-edit:
I didn't read the Release Notes first. It stated that: "B. < V6.1 hardware version of SPD3303X/X-E do not support upgrading to this version (SPD3303X_V1.01.01.03.10.ADS)". The result was the PSU will boot into the firmware update screen after reboot.

[CraigD73]

What is the  firmware update process for an SPD3303X-E that has been updated with the expanded resolution.   
The current condition:
        FW shows 1.01.01.02.05
        HW version V3.0
        Product type SPD3303X

How does one update to the latest FW 1.01.01.02.07R2 without messing up the expanded resolution?  Normal SPD3303X update for Siglent  or do I need a special file?
Craig

[TERRA Operative]

Just use the EasyPower software and the normal SPD3033X firmware (not the -E firmware) as usual.

[CraigD73]

Thanks, that is what I thought -- worked great

[TERRA Operative]

For anyone searching in the future, here is a step by step guide on hacking these power supplies:

https://www.eevblog.com/forum/testgear/siglent-spd3303x-e-hi-resolution-output-unlock/msg5347535/#msg5347535