It now has the model number listed again, phew.
LXI Connectivity
Hey Guys.. I'm thinking of getting one of these but I've never connected anything to ethernet or remote controlled, but would like to do this the the electronic load. So I read about SCPI ( Command set ) VISA ( some api ) and LXI..
I see LXI specified in other manufacturers models ( Keysight e.g. ) but nowhere can I see LXI mentioned in the Siglent data sheet. Although they do show a video promoting the use of LXI, it doesn't specifically mention these electronic loads.
Do I need LXI? What are the pros and cons? Or, has it got it but not mentioned?
Interesting.. I read into that, that the Siglent must have LXI by virtue that it has Ether net connectivity and is not a LeCroy device?
Yes it is a bit confusing however there are more clues to the performance of these loads in the programming guide and the EasySDL software.
Trend charts can be set to a max of 24 hours and readings recorded only as fast as every second and there's no apparent max file size however using just the instrument a 999s limit is imposed with a 1 us resolution.
I need to become more familiar with these and a few minutes bashing around in EasySDL finds a power of features that seem pretty simple to use however as we are out of stock for the next while can't do any tests.
Have a bash around in the 20 MB EasySDL package however if you do end up getting one of these loads do remember to install NIVISA for the connectivity drivers before attempting to connect the load otherwise your PC OS will install the incorrect ones for sure.
EasySDL SW:
https://int.siglent.com/download/softwares/?CateIdss=12
New firmware for SDL1000X/X-E models:
Version: V1.1.1.21R2
498 KB
https://int.siglent.com/upload_file/zip/firmware/Electronic_load/SDL1000X_X-E_V1.1.1.21R2_EN.zip
Release notes
1. Fix bug: DHCP turn to be ON state after send *RST command.
2. Some units will crash after run for some time.
New firmware for SDL1000X/X-E models:
Version: V1.1.1.21R2
498 KB
https://int.siglent.com/upload_file/zip/firmware/Electronic_load/SDL1000X_X-E_V1.1.1.21R2_EN.zip
Release notes
1. Fix bug: DHCP turn to be ON state after send *RST command.
2. Some units will crash after run for some time.I ran into this bug almost two years ago, so I was quite curious about the fix. It turns out there is still a bit of an issue. I can telnet to port 5025 and manually issue the *RST command, and the instrument resets while retaining its IP settings. Yay! But when issuing the *RST command using pyvisa/pyvisa-py, pyvisa craps out. All my other instruments perform a reset just fine using this method, so there is still something not quite right here.
I am currently using five of these loads in a remote controlled setup, so I would love to see this sorted. If I can help I gladly will.
import pyvisa as visa
visa_rm = visa.ResourceManager('@py')
eload_ip = '192.168.1.5'
sdl = visa_rm.open_resource('TCPIP::'+eload_ip+'::INSTR')
After running this in the console, sdl.query('*IDN?')
produces the well-known SDL1000x ID string, and no errors. The instrument can be operated remotely without issue. But after trying sdl.write('*RST')
the following error is produced after a brief wait: VisaIOError: VI_ERROR_IO (-1073807298): Could not perform operation because of I/O error.
From that point onwards, it is no longer possible to access the instrument until the sdl object is re-created. My guess is that Pyvisa times out waiting for a VXI-11 handshake that never comes, and the instrument is only accessible again after reconnecting. import pyvisa as visa
visa_rm = visa.ResourceManager('@py')
eload_ip = '192.168.1.5::5025'
sdl = visa_rm.open_resource('TCPIP::'+eload_ip+'::SOCKET')
sdl.write_termination = '\x0A'
sdl.read_termination = '\x0A'
This sets up a socket connection instead of a VXI-11 connection to port 5025. The instrument accepts this. With a socket connection I can saysdl.write('*RST')
to the instrument, watch it reset itself and continue operating it from a known state. Yay! sdl.write('*RST')
sdl.write(':SOUR:FUNC VOLT')
sdl.write(':SOUR:VOLT:LEV:IMM 10')
print(sdl.query('*IDN?'))
With a socket connection it times out on the last line. However, the instrument does enter constant voltage mode at 10 V after 7 seconds following reset. The program just doesn't block at the write operations and only times out at the query because the instrument doesn't respond to queries within seven seconds after reset. With a VXI connection, the snippet times out on the first line because it now does block on the write operations and only continues when a write operation is complete, which after a reset takes 7 seconds. So generally, VXI is safer because program flow only continues when the instrument has carried out the command and is ready to carry out the next one. But it is also slower due to the blocking write operations and RPC calls that the instrument must carry out.Okay, great! Yeah, I guess that the response time of 7 seconds is a "trap for young players" that got me. I hope that my experience can help other people to avoid this pitfall.