I just got my SPD3303X-E (SW version 1.01.01.02.05 (latest!), HW version V3.0 (latest??))
Out of the box, with no load and with all voltages and currents set to 0.00, and outputs OFF, CH1 and CH2 say they are in CV mode.
If I then turn all the outputs ON, CH1 goes immediately into CC mode, while CH2 stays CV. Both still show 0V at 0A out.
If I set them both to some low voltage (not necessarily the same voltage) CH1 will stay in CC mode, 0V at 0A out, but CH2 will slowly seek the set voltage in CC mode, then switch to CV (after a few seconds it ends up at the target voltage at 0A).
I do notice that if I set CH1 V to, say, 1 V (or really anything > 0V) and set some current, it will switch to CV and rise to that set voltage. CH2 will do this with with 0.00A.
First question: Can anyone else confirm similar behavior?
Second question: is this normal? Again, this is with no load (about to try some load testing now).
(Seems CH2 will sometimes do this if CH1 is off, but not reliably. CH3 doesn't seem to affect any of this.)
I should add that under load it seems more normal, though I'm still getting used to using the different modes. The channels are in independent mode.
Entirely normal. Just use it.
Consider why it's shipped set like that. If controls were set to max there'd be complaints that the PSU blew things up when first connected.
Adjust to the V you need then A to some reasonable value then turn the channel ON and any current draw above SET will shift the PSU into CC mode.
A little time using it and you will appreciate this behavior.
With a setting of 0A, a small leakage current may trigger the "CC" mode. There may be a slight sensitivity difference between the 2 channels.
Entirely normal. Just use it.
Consider why it's shipped set like that. If controls were set to max there'd be complaints that the PSU blew things up when first connected.
Adjust to the V you need then A to some reasonable value then turn the channel ON and any current draw above SET will shift the PSU into CC mode.
A little time using it and you will appreciate this behavior.
I didn't expect it to be set to max or anything - I just wondered why, when set to 0V 0A, CH1 always powers on into CC mode and CH2 always powers on into CV mode.
With a setting of 0A, a small leakage current may trigger the "CC" mode. There may be a slight sensitivity difference between the 2 channels.
This is why I wondered if this indicates a fault of some kind. Sounds like it may be fine.
I did check the output voltage and current with my Fluke and the channels differ very slightly, which begs another question:
how do you calibrate this device?
I did check the output voltage and current with my Fluke and the channels differ very slightly, which begs another question: how do you calibrate this device?
Did it come with a Cal cert and does it look in order ?
The calibration equipment used at the factory will be listed on the Cal cert.
Typically it's a precision calibrator coupled to a PC running a script that performs an automated Cal process and that's an entirely 'closed case' process.
Did it come with a Cal cert and does it look in order ?
The calibration equipment used at the factory will be listed on the Cal cert.
Typically it's a precision calibrator coupled to a PC running a script that performs an automated Cal process and that's an entirely 'closed case' process.
Yes - it just says an electronic load and digital multimeter were used. No mention of a particular calibrator or how the process works. That's why I asked.
Did it come with a Cal cert and does it look in order ?
The calibration equipment used at the factory will be listed on the Cal cert.
Typically it's a precision calibrator coupled to a PC running a script that performs an automated Cal process and that's an entirely 'closed case' process.
Yes - it just says an electronic load and digital multimeter were used. No mention of a particular calibrator or how the process works. That's why I asked.
I honestly thought there was more than that. I'll get one out for a look as I don't remember ever studying a PSU Cal sheet.
OK so here's the Cal sheet gen:
DMM: 34401A = Keysight
E-load: IT8722......Google....= ITECH
SN#'s and Cal expiry dates included.
So one might expect there's a Cal mode you place the SPD3000X-E into OR do the level adjustments via some secret SCPI commands.
Anyone want to do a mem dump and have a hunt for them ?
OR as I surmised earlier, the DMM and E load are controlled by a PC script and perform a closed box calibration.
Hmmm, there's no service manual for any of the SPD's.....in Siglent's other equipment the Cal procedure is outlined in service manuals......but a hunt reveals a post I made a couple of years ago about Cal procedures:
https://www.eevblog.com/forum/testgear/siglent-technical-support-join-in-eevblog/msg986796/#msg986796
better than a mem dump, grab me the system app and I can probably figure it out for you.
A command you can probably use as a starting point is "printcali" which should print the current calibration.
not to mention if the calibration is anything like the scopes and spectrum analysers, there will just be a .txt file buried in the usr directory with the calibration info.
So one might expect there's a Cal mode you place the SPD3000X-E into OR do the level adjustments via some secret SCPI commands.
Anyone want to do a mem dump and have a hunt for them ?
OR as I surmised earlier, the DMM and E load are controlled by a PC script and perform a closed box calibration.
Hmmm, there's no service manual for any of the SPD's.....in Siglent's other equipment the Cal procedure is outlined in service manuals......but a hunt reveals a post I made a couple of years ago about Cal procedures:
https://www.eevblog.com/forum/testgear/siglent-technical-support-join-in-eevblog/msg986796/#msg986796
I don't think I have any way to log into this directly.
I successfully converted from X-E to X today (via USB), and the slight difference between setting and reality is more noticeable with the extra digit, so being able to at least match the channels up a bit better would be nice.
And as always, it's good to know how to maintain the equipment yourself when possible (in the modern world where trimpot settings are long gone...)
Edit: assuming there is any way to effect a tweak manually (even if it's tweaking cal values slightly - the ability to un-tweak being handy in absence of a full lab for said calibration).
So one might expect there's a Cal mode you place the SPD3000X-E into OR do the level adjustments via some secret SCPI commands.
Anyone want to do a mem dump and have a hunt for them ?
OR as I surmised earlier, the DMM and E load are controlled by a PC script and perform a closed box calibration.
Hmmm, there's no service manual for any of the SPD's.....in Siglent's other equipment the Cal procedure is outlined in service manuals......but a hunt reveals a post I made a couple of years ago about Cal procedures:
https://www.eevblog.com/forum/testgear/siglent-technical-support-join-in-eevblog/msg986796/#msg986796
I don't think I have any way to log into this directly.
I successfully converted from X-E to X today (via USB), and the slight difference between setting and reality is more noticeable with the extra digit, so being able to at least match the channels up a bit better would be nice.
And as always, it's good to know how to maintain the equipment yourself when possible (in the modern world where trimpot settings are long gone...)
Edit: assuming there is any way to effect a tweak manually (even if it's tweaking cal values slightly - the ability to un-tweak being handy in absence of a full lab for said calibration).
Work with member Rerouter on trying to discover the adjustment methods, he's pretty slick at examining the undocumented SCPI commands from within Siglent gear.
better than a mem dump, grab me the system app and I can probably figure it out for you.
A command you can probably use as a starting point is "printcali" which should print the current calibration.
not to mention if the calibration is anything like the scopes and spectrum analysers, there will just be a .txt file buried in the usr directory with the calibration info.
I'm not sure how I'd go about doing this... unlike the other things I've modded, I didn't need to telnet into the PSU to apply the enhancement. Thoughts?
There are 2 scpi commands that come to mind. First is from the scope hacking thread. Reply 85.
https://www.eevblog.com/forum/testgear/unlocking-siglent-sds1104x-e-step-by-step/?allIf that works you should be able to telnet in and grab it. Otherwise I take a shot in the dark that its similar enough to the scopes to work and you try "SHELLCMD cp -r /usr /usr/bin/siglent/usr/mass_storage/U-disk0/"
This should copy everything in the usr directory to a flash drive. You will need to insert one. If it works then there will be an .app file under the siglent directory.
There are 2 scpi commands that come to mind. First is from the scope hacking thread. Reply 85. https://www.eevblog.com/forum/testgear/unlocking-siglent-sds1104x-e-step-by-step/?all
If that works you should be able to telnet in and grab it. Otherwise I take a shot in the dark that its similar enough to the scopes to work and you try "SHELLCMD cp -r /usr /usr/bin/siglent/usr/mass_storage/U-disk0/"
This should copy everything in the usr directory to a flash drive. You will need to insert one. If it works then there will be an .app file under the siglent directory.
This power supply doesn't even *have* a USB port for a flash drive. It'll connect to a PC via USB (or a network via ethernet) but that's all.
There are 2 scpi commands that come to mind. First is from the scope hacking thread. Reply 85. https://www.eevblog.com/forum/testgear/unlocking-siglent-sds1104x-e-step-by-step/?all
If that works you should be able to telnet in and grab it. Otherwise I take a shot in the dark that its similar enough to the scopes to work and you try "SHELLCMD cp -r /usr /usr/bin/siglent/usr/mass_storage/U-disk0/"
This should copy everything in the usr directory to a flash drive. You will need to insert one. If it works then there will be an .app file under the siglent directory.
This power supply doesn't even *have* a USB port for a flash drive. It'll connect to a PC via USB (or a network via ethernet) but that's all.
Use NIVISA Runtime for the connection drivers
AND install it first.
Then EasyPower will then connect seamlessly and you can use the SCPI console within.
Use NIVISA Runtime for the connection drivers AND install it first.
Then EasyPower will then connect seamlessly and you can use the SCPI console within.
When I enter `SHELLCMD telnetd -l/bin/sh -p9999` and press Query, I get a beep (which it seems to only do for invalid commands, the other commands, the output of which is shown in the attached image, seem to work fine.)
Without a place to even plug a flash drive in, though, how is this command supposed to be effective even if it works (not that it appears to)?
I don't know that anyone has successfully started a telnet session with the SPD devices. I don't believe SHELLCMD works on the SPDs, and it certainly isn't for a lack of trying.
Any idea what "Factory mode" is? I've switched it on and switched it off, but I'm not sure what it means.
No idea...
The commands don't have password AFAIK.