Siglent SPD3303X-E Hi-Resolution Output Unlock?

[mawyatt]

Sure hope you are right, as I can't use this for the intended purpose at the moment as we need a very precise current limit at low currents.

Having this offset is just a recipe for a mistake and I'm reluctant to use it in this application, could easily damage some expensive ICs.

Hopefully Rob at tautech will get the factory "Secret Code" to reset this CC offset.

I know many pick on Rob because he is a Siglent distributor, but he goes well beyond the call of duty to help folks with Siglent equipment, even if they aren't in his hemisphere

Tautech is the basic reason we've decided on Siglent equipment, and when a new requirement arrises we look to Siglent first, simply because we know the after sales support available thru tautech and we don't buy from tautech here is US, we buy from another excellent resource Saelig in NY.

Best,

[tv84]

I know many pick on Rob because he is a Siglent distributor, but he goes well beyond the call of duty to help folks with Siglent equipment, even if they aren't in his hemisphere

tautech's support in this forum is bigger than the whole northern hemisphere combined!

[2N3055]

I know many pick on Rob because he is a Siglent distributor, but he goes well beyond the call of duty to help folks with Siglent equipment, even if they aren't in his hemisphere

tautech's support in this forum is bigger than the whole northern hemisphere combined!

 

[blurpy]

Sure hope you are right, as I can't use this for the intended purpose at the moment as we need a very precise current limit at low currents.

Having this offset is just a recipe for a mistake and I'm reluctant to use it in this application, could easily damage some expensive ICs.

Hopefully Rob at tautech will get the factory "Secret Code" to reset this CC offset.

Just curious. Did you get this fixed yet?

[mawyatt]

@blurpy,

Not yet 

Still waiting for a factory reply 

Best,

[optotester]

Any news regarding that issue ?

[mawyatt]

No, we haven't received any response from the factory regarding this issue. Not happy with Siglent in this regard, would have at least expected a response of some kind, maybe not favorable, but at least a response.

Best,

[blurpy]

I finally ended up liberating mine now, and it's working great!

I was a bit worried since I read posts about people losing calibration, serial number, and the mac address in different attempts.
But I noted down the serial and mac just in case and went for it (using tv84s instructions).

From reading other experiences, SCPI should have returned the full resolution even before the upgrade, but it did not. Both before FACTORY ON, and after, it was only 10mA resolution. Perhaps they changed that in the latest firmware, which is where I upgraded from. The additional digit did display on the device and with SCPI after the upgrade, so I'm satisfied. It's really nice to have 1mA resolution on current measurement.

There are a few mV difference between "set" voltage and "read" voltage (like others have noted), but the "read" voltage agrees pretty well with my multimeter, so that's fine.

[jonas21]

It appears there is a new HW revision (6.0) of the SPD3303 which requires minimum the 3.10 firmware (V1.01.01.03.10).
As that the conversion is no longer possible with the old patched firmware - this would require 3.10 to be patched.

As the side note: according to the release notes the newest firmware (3.10) is not for older revisions of the SPD3303 as it requires HW 6.0+.

[tv84]

As that the conversion is no longer possible with the old patched firmware - this would require 3.10 to be patched.

Don't remember about what patch you're referring to. But, if you're talking about a conversion patch, you don't need any more patches. Once converted, you can flash the new stock FW.

[blurpy]

2022/09/01 1.01.01.03.10 1. This firmware version only supports V6.1 hardware version of SPD3303X/X-E

Notes:
A. V6.1 hardware version of SPD3303X/X-E do
not support rolling back to the previous
firmware version
B. < V6.1 hardware version of SPD3303X/X-E
do not support upgrading to this version

So at the moment new units can't be converted.

[tautech]

2022/09/01 1.01.01.03.10 1. This firmware version only supports V6.1 hardware version of SPD3303X/X-E

Notes:
A. V6.1 hardware version of SPD3303X/X-E do
not support rolling back to the previous
firmware version
B. < V6.1 hardware version of SPD3303X/X-E
do not support upgrading to this version

So at the moment new units can't be converted.

That's not how I interpret the latest FW as it's in relation to the latest HW changes and how they work with the FW.

Don't have stock for a week or 2 to check however I don't see it impacting on converting X-E to X.

[blurpy]

That's not how I interpret the latest FW as it's in relation to the latest HW changes and how they work with the FW.

Don't have stock for a week or 2 to check however I don't see it impacting on converting X-E to X.

My interpretation is that new hardware units require new firmware, and will be bricked if downgraded by using the current conversion firmware. Do you think not?

[tautech]

That's not how I interpret the latest FW as it's in relation to the latest HW changes and how they work with the FW.

Don't have stock for a week or 2 to check however I don't see it impacting on converting X-E to X.

My interpretation is that new hardware units require new firmware, and will be bricked if downgraded by using the current conversion firmware. Do you think not?

I think not.
Siglent firmware has popped up flags if attempted to be installed in the wrong HW.
The release notes claim:
do not support

This does NOT mean brick. The firmware will not be loaded and a HW incompatibility warning will be issued.
Siglent do not need to make more work for their Tech support.
You are overthinking this.

[blurpy]

Interesting, Siglent changed the productId.

SPD3303X used to be productId 64, now it's 70
SPD3303X-E used to be productId 65, now it's 71.

I think you are reading me wrong. I'm not claiming Siglent did not think of a way to stop devices being bricked. See what I just wrote, that's how they solved it.

I'm just pointing out that it won't be possible to use the current conversion firmware because the new hardware is unsupported.

[tautech]

I'm just pointing out that it won't be possible to use the current conversion firmware because the new hardware is unsupported.

You think. We'll see.

[blurpy]

I'm just pointing out that it won't be possible to use the current conversion firmware because the new hardware is unsupported.

You think. We'll see.

Be sure to let us know how it goes, but making sure you are testing on a v6.1 hardware unit of course.

[jonas21]

FWIW: i tried to install 3.10 on my HW rev. 3.0 device - it didnt work, easypower will just say the firmware doesnt match the device (no matter if X or X-E). So atleast this way you cant brick it.
As this way is impossible, i expect a device with HW 6.x to also refuse a firmware lower than 3.1. So unless there is a "conversion firmware" with version 3.10 it will likely
not be possible to unlock it.

[tv84]

Gentlemen, I think this is what you are searching for.

Supposedly they allow the conversion of a X into X-E and a X-E into X, using the (almost) stock FW packages.

I take no responsibility on what you do with these files..

Only for V6.1 hardware version, as Siglent says!

[mawyatt]

Any news regarding that issue ?

@blurpy and optotester

Must apologize for the seriously late response. We sent the SDP to Siglent NA and they corrected the problem and honored the warranty even tho we had "enabled" to an X from an X-E.

We just had to pay for shipping to Siglent NA, they even covered return shipping!!

So hat's off to Siglent NA (again, they helped long ago with potential DSO issue that was caused by spilled drink into the DSO  ), and another reason why they have become our preferred test equipment supplier, they've earned this

Best,

[WhiteSpin]

Thanks so much for providing this. Could anyone confirm that they successfully unlocked a siglent with the new hardware ID? Additionally it would be great to know if the 100mA offset remains as a problem with the new hardware&firmware. Thanks!

[funhobby]

Gentlemen, I think this is what you are searching for.

Supposedly they allow the conversion of a X into X-E and a X-E into X, using the (almost) stock FW packages.

I take no responsibility on what you do with these files..

Only for V6.1 hardware version, as Siglent says!

Works perfectly with the newest SPD3303X-E. Thanks!

[XerXes777]

Gentlemen, I think this is what you are searching for.

Supposedly they allow the conversion of a X into X-E and a X-E into X, using the (almost) stock FW packages.

I take no responsibility on what you do with these files..

Only for V6.1 hardware version, as Siglent says!

Works perfectly with the newest SPD3303X-E. Thanks!

How i can use it?
Please give me short manuel.

[tautech]

Gentlemen, I think this is what you are searching for.

Supposedly they allow the conversion of a X into X-E and a X-E into X, using the (almost) stock FW packages.

I take no responsibility on what you do with these files..

Only for V6.1 hardware version, as Siglent says!

Works perfectly with the newest SPD3303X-E. Thanks!

How i can use it?
Please give me short manuel.

First go back to reply #1 and follow link offered then come back to last reply from tv84.

[XerXes777]

Please tell me the best way to get the update to 1.01.01.03.10 and to use the hack.
I can do an update to 1.01.01.03.10.
And then i can use the hack from:
https://www.eevblog.com/forum/testgear/siglent-spd3303x-e-hi-resolution-output-unlock/msg4503400/#msg4503400
?