Siglent SDL1000X/SDL1000X-E Electronic Load

[TheDefpom]

My new 200W Load unit just arrived, no time to reprogram it into a 300W but will be looking to do that in the coming weeks

I will be interested in hearing about changing from 200W to 300W, what is involved in that?

[Elasia]

My new 200W Load unit just arrived, no time to reprogram it into a 300W but will be looking to do that in the coming weeks

I will be interested in hearing about changing from 200W to 300W, what is involved in that?

I'm thinking it is most likely similar to converting a SPD3303X-E to a SPD3303X, same main board in both the 200W and 300W versions, even the missing 4th load resistor

[tv84]

My new 200W Load unit just arrived, no time to reprogram it into a 300W but will be looking to do that in the coming weeks

Enjoy!

Code: [Select]

File Header Size: 00000070
00000000 - File Header Checksum: FFFFFA79 [00000004-0000006F] (with only the File Header decrypted)  CKSM OK
00000004 - File Size: 000B6388
0000000C - Product_ID: 700
00000026 - Vendor/Brand: SIGLENT
0000003A - USB Host Controller: ISP1763
---------- Block 1 ------------- STM32 32-bit ARM Cortex -----------
00000070 - Type: 00000002
00000074 - Offset: 0000007C  [0000007C-0000CB03]
00000078 - Size: 0000CA88
0000007C - Vector Table:        (Little Endian - Flash(ROM): 0x08000000 - SRAM: 0x20000000)
0000007C ---        Initial SP value: 20005778
00000080 ---                   Reset: 08000198  (Thumb mode)
00000084 ---                     NMI: 08008F60  (Thumb mode)
00000088 ---              Hard fault: 08003EC0  (Thumb mode)
0000008C --- Memory management fault: 08008F5C  (Thumb mode)
00000090 ---               Bus fault: 08000DA0  (Thumb mode)
00000094 ---             Usage fault: 08009AC0  (Thumb mode)
00000098 ---                   Rsvd1: 00000000
0000009C ---                   Rsvd2: 00000000
000000A0 ---                   Rsvd3: 00000000
000000A4 ---                   Rsvd4: 00000000
000000A8 ---                  SVCall: 0800916E  (Thumb mode)
000000AC ---          Rsvd for Debug: 0800172E  (Thumb mode)
000000B0 ---                   Rsvd5: 00000000
000000B4 ---                  PendSV: 08008F9C  (Thumb mode)
000000B8 ---                 Systick: 08009268  (Thumb mode)
000000BC --- IRQ0 to IRQ80  [000000BC-000001FF]
00000200 --- Start of Reset function code (???) -  should use Loading address=0x08000014 + File offset=0x0000007C in IDA Pro
---------- Block 2 ------------- STM32 32-bit ARM Cortex -----------
0000CB04 - Type: 3E012701
0000CB08 - Offset: 0000CB10  [0000CB10-000B6387]
0000CB0C - Size: 000A9878
0000CB10 - Vector Table:        (Little Endian - Flash(ROM): 0x08000000 - SRAM: 0x20000000)
0000CB10 ---        Initial SP value: 2002CF38
0000CB14 ---                   Reset: 08040450  (Thumb mode)
0000CB18 ---                     NMI: 0804C510  (Thumb mode)
0000CB1C ---              Hard fault: 0804B5B0  (Thumb mode)
0000CB20 --- Memory management fault: 0804C50C  (Thumb mode)
0000CB24 ---               Bus fault: 08044924  (Thumb mode)
0000CB28 ---             Usage fault: 08052F28  (Thumb mode)
0000CB2C ---                   Rsvd1: 00000000
0000CB30 ---                   Rsvd2: 00000000
0000CB34 ---                   Rsvd3: 00000000
0000CB38 ---                   Rsvd4: 00000000
0000CB3C ---                  SVCall: 08040360  (Thumb mode)
0000CB40 ---          Rsvd for Debug: 08044B94  (Thumb mode)
0000CB44 ---                   Rsvd5: 00000000
0000CB48 ---                  PendSV: 080403B4  (Thumb mode)
0000CB4C ---                 Systick: 0804E188  (Thumb mode)
0000CB50 --- IRQ0 to IRQ90  [0000CB50-0000CCBB]
0000CCBC --- Start of Reset function code (???) -  should use Loading address=0x080402A4 + File offset=0x0000CB10 in IDA Pro
  File Processed OK


[Elasia]

<3

[JxR]

My new 200W Load unit just arrived, no time to reprogram it into a 300W but will be looking to do that in the coming weeks

Enjoy!

Well, it isn't what I was hoping it was...because yes I'm crazy enough to put in on a flash drive and see what happens (which was nothing but an error).  So, what is this?

[tv84]

My new 200W Load unit just arrived, no time to reprogram it into a 300W but will be looking to do that in the coming weeks

Enjoy!

Well, it isn't what I was hoping it was...because yes I'm crazy enough to put in on a flash drive and see what happens (which was nothing but an error).  So, what is this?

It's something for Elasia try and see if you get what you were hoping for.

[techneut]

I was thinking about buying a Korad KEL103 load, 300W very cheap 379 Euro but with a horrible UI.
Now that I see that tv84 and Elasia are working theire magic I will wait because the Siglent looks good but at 900 Euro it's out of my price range.

[Elasia]

I was thinking about buying a Korad KEL103 load, 300W very cheap 379 Euro but with a horrible UI.
Now that I see that tv84 and Elasia are working theire magic I will wait because the Siglent looks good but at 900 Euro it's out of my price range.

It will be abit on this one as this is more normal embedded firmware, not till late summer till I start tinkering, although my 24Vx25A power supplies just arrived and have 10 awg due next week so if I need a distraction its there

[OoVoO]

My new 200W Load unit just arrived, no time to reprogram it into a 300W but will be looking to do that in the coming weeks

Enjoy!

We are waiting for the result 

[Elasia]

I looked at this today and found out my stlink device.. is dead.. so much for that lol

[TheDefpom]

I looked at this today and found out my stlink device.. is dead.. so much for that lol

Damn, thats not good.

I have been trying to do a very light loading of a 3.6V lithium cell for the past couple of days (to determine how much juice is left in a memory backup battery I pulled from a Datron 1062 (I replaced it with a new cell), as a result I discovered a small improvement I would like for the loads GUI, that is for it to include decimal values of the battery discharge mAh accumulation, if it is less than 1mAh it does not consider the value (or display it) so if you stop the load and restart it the accumulated (<0) amount is not considered and it starts from 0 again without the prompt to continue the previous test.

Maybe Siglent can add a decimal place or 2 to the accumulated mAh reading so when doing this very low current/low capacity tests it allows you see/keep the results.

Realistically this is right on the limit of what it can measure anyway, draining a cell at 2mA-4mA is a a tough ask when it comes to accuracy anyway as it only has a 1mA resolution, and this probably isn't a common usage case either.

[Elasia]

You would be better served making a dedicated circuit using a shunt resistor to measure voltage drop over and a known load.. and use a high count dmm

And yeah.. only used that one a few times too.. bastards lol, i'll have a new one in a week or so

[JxR]

Recently I've been working on creating python drivers for most of my instruments.  This is the forth I've done so far, and is ~90-95% complete(no bug free promises).  Since I made these for myself I don't expect to provide any more documentation than I already have.  Also, I'm fairly new to python so please keep that in mind. I welcome constructive feedback.

Anyways, if you would like a python way to drive your SDL1000X series from a console, or for use in a more complex script:

https://github.com/JxR-TestMeasure/siglent_sdl1000x

[JxR]

Just adding an example script using the Siglent1020X-E (and Agilent366XX) python library I posted above:
Measure: 200us 1.5A pulse

Code: [Select]

from siglent_sdl1000x import Device as Siglent1000X
from agilent_66321B import Device as Agilent36621B
import matplotlib.pyplot as plt

ps = Agilent36621B()
load = Siglent1000X()

# Configure load
# Configure pulse
# a: 50mA, 20ms (low level)
# b: 1.5A, 0.2ms (high level)
load.cc.dyn.set_a_and_b(0.05, 1.5, 0.02, 0.0002)
load.cc.dyn.pulse_mode('CONT')
load.cc.dyn.current_range(5)
load.cc.dyn.voltage_range(36)
load.cc.dyn.set_slew_both(0.5)

# Configure the power supply
ps.ch1.voltage(3.3)
ps.ch1.current(2)
ps.ch1.current_range(3)
# Configure the power supply sampling
ps.log.sample_offset(-10)
ps.log.sample_points(4096)
ps.log.integration_time(0.0000156)
# Configure the power supply trigger
ps.log.trig.source('INT')
ps.log.trig.sense('CURR')
ps.log.trig.current_slope('POS')
ps.log.trig.current_level(0.2)

# Commence measurement
ps.ch1.on()
load.cc.dyn.on()
ps.log.start_meas_sample()

# Turn instruments off
load.cc.off()
ps.ch1.off()

# Plot results
plt.plot(ps.log.log_data['seconds'][0:-1], ps.log.log_data['current'][0:-1])
plt.ylim(0, 1.7)
plt.xlim(0, 0.0005)
plt.xlabel(r'time [s]')
plt.ylabel(r'current [A]')
plt.title('Siglent SDL1020X Dynamic CC Pulse Test')
plt.grid()
plt.show()
plt.figure(figsize=(12, 10))

Result:

[tautech]

Defpom checks the rated capacity of newly acquired rechargeable 9V batteries.........

[alpelectronics]

Hi. Is there any update for hacking 200W version to 300W. Im currently planning to get one 200W version.

[Elasia]

Hi. Is there any update for hacking 200W version to 300W. Im currently planning to get one 200W version.

Life happened, still sitting on the shelf

[tautech]

 
EasyDL software is now available online.
Requires  firmware version of SDL1000X/X-E is '1.1.1.21'

Version 8.5
19 MB
https://siglentna.com/download/18916/
https://www.siglenteu.com/download/9943/

Requires the NIVISA Runtime package for USB and LAN drivers. RTFM.   

Not yet had a chance to test it.....

[marmelade]

So whats the verdict with these loads?

Do they work as advertised or is there anything odd like with the dynamic (miss-) behaviour of the Rigol?

As far as I am arware of, there are no software hacks known to the public - or are there?

[jasonbrent]

My new 200W Load unit just arrived, no time to reprogram it into a 300W but will be looking to do that in the coming weeks

Enjoy!

Code: [Select]


00000200 --- Start of Reset function code (???) -  should use Loading address=0x08000014 + File offset=0x0000007C in IDA Pro
snip...
0000CCBC --- Start of Reset function code (???) -  should use Loading address=0x080402A4 + File offset=0x0000CB10 in IDA Pro
  File Processed OK


Ordered a 200W unit a few moments ago.... perhaps I'll have time to futz with this in the near future.

In the interim, @tv84 -- what did you use to generate the output here? specifically the load/offset guesses for IDA?

-j

[tv84]

In the interim, @tv84 -- what did you use to generate the output here? specifically the load/offset guesses for IDA?

From memory, I think it was educated guessing with a bit of trial and error.

[atimos]

I looked at the firmware for a bit and the device type and power limit can be conveniently set via SCPI:

Code: [Select]

SYSTem:DEVICE:PRODUCTUG:ID 1
SYSTem:DEVICE:POWERUG 300

Gives me 4 digits of resolution and a power limit of 300 watts on my SDL1020X-E.

Note that the model string you see in the UI will not be changed by these operations. It is stored separately in the flash and has only cosmetic value for *IDN? and the GUI as far as I can tell and does not affect the functionality at all (there is one place where it is used as a fallback if the numeric product id is unset/0xff, but even if this code path triggered for your unit before doing the above, it won't anymore after the ID has actually been set by the SYSTem:DEVICE:PRODUCTUG:ID command. I guess this is just a workaround for a past blooper in their manufacturing process. See the attached screenshot for the relevant part of the firmware if you're curious). Still, if you want to change it, you can modify that string as well using another command: SYSTem:DEVICE:PRODUCTUG SDL1030X (note that this a wholly different command from the one in the above snippet: There is no :ID suffix!)

If you want to experiment with this, I suggest you dump the relevant parts of the config flash so you can revert to the original settings using

Code: [Select]

FLAsh:READ? addr

which reads a single byte from addr. Both addr and the returned value are decimal and addr can range from 0 to 65535. The power limit is stored as a little endian value at offsets 0xee-0xef/238-239 (0x00c8 = 200W for me originally). The sub-model id is stored at 0x124/292 and was 2 for me originally. Note that there seem to be other values than 1 and 2 for that identifier that are handled differently in the firmware; this might be related to other OEM versions, as there is other functionality (such as setting the manufacturer string or changing the boot logo) that seems geared towards whitelabeling these boxes.

I haven't actually measured the performance of the load with these settings, as I'm not entirely certain that the hardware is really fully equivalent between the different versions and I don't want to break this device just yet. If somebody else has voided their warranty anyway and is willing to give this a try, I'd be happy to hear about that. For what it's worth, my Hardware Version is 03-03-020.

EDIT 2021-01-01: Made the wording about the model string more explicit, as it has caused some confusion.

[TheDefpom]

I looked at the firmware for a bit and the device type and power limit can be conveniently set via SCPI:

Code: [Select]

SYSTem:DEVICE:PRODUCTUG:ID 1
SYSTem:DEVICE:POWERUG 300

Gives me 4 digits of resolution and a power limit of 300 watts on my SDL1020X-E. Note that the model string will not be changed by this by default (it's stored explicitly in the flash as well and can be changed with SYSTem:DEVICE:PRODUCTUG).
... my Hardware Version is 03-03-020.

Well I couldn't resist... my 1020X-E is now a 300W unit, with 4 digits of resolution....

The only trouble is now it has forgotten its model name (doesn't show on the info screen, or when getting an IDN?), my unit is hardware version 02-02-020

Originally it returned this: (SN obscured obviously)

Read Operation
Return Count: 56 bytes
Siglent\sTechnologies,SDL1020X-E,SDL1Xxxxxxxxxx,1.1.1.21\n


It now returns this:

Read Operation
Return Count: 47 bytes
Siglent\sTechnologies,\s,SDL1Xxxxxxxxxx,1.1.1.21\n

I haven't figured out how to correct this yet, I have tried sending the "SYSTem:DEVICE:PRODUCTUG" in various ways, including specifying the model explicitly "SYSTem:DEVICE:PRODUCTUG:ID SDL1030X" etc. without luck, I'm not at all experienced with SCPI so I'm not even sure if I am doing the command correctly.

[TheDefpom]

Ahh, never mind, I solved it, I sent this to the unit: SYSTem:DEVICE:PRODUCTUG SDL1030X

It now has the model number listed again, phew.

*IDN? now returns this:
Read Operation
Return Count: 54 bytes
Siglent\sTechnologies,SDL1030X,SDL1Xxxxxxxxxx,1.1.1.21\n

I glanced through the firmware and found the SCPI command list in there, that gave me a clearer picture of what I was supposed to be sending.

There is a nice section starting at 2AF38.

[gussy]

Thanks for the info atimos and Defpom! I have a SDL1020X-E on the way which will hopefully get a similar treatment.