Products > Test Equipment
Open source lxi-tools and liblxi v1.0 released for GNU/Linux
lundmar:
--- Quote from: borjam on November 09, 2017, 01:23:36 pm ---Speaking of what I might feel inclined to send a bottle of Spanish red wine northwards ;)
--- End quote ---
Guys don't send me that much red wine as I'm not much of a wine drinker. However, I'll accept some of that fine Argentinian beef and Spanish chorizo ha ha :D
dpenev:
--- Quote from: lundmar on November 09, 2017, 10:55:11 am ---
1. Can there be a option for png instead of bmp? png are smaller.
The image format depends on which formats the instrument supports. PNG is certainly the preferred format but not all instruments support it. The Rigol 2000 series supports PNG for internal storage of screenshots but it is not documented whether it is possible to retrieve PNG remotely. Please try out the '"rigol_2000_png" branch and let me know if it creates a proper PNG for you. If not I'm afraid it is not possible unless the lxi tool itself starts doing BMP->PNG conversion but I think that is a bad idea. I would rather provide the raw material straight from the instrument and then the user can do as they please.
--- End quote ---
I have tested the rigol_2000_png branch. It produce file with png extension but it is actually a bit map, same size, BMP header.
--- Quote from: lundmar on November 09, 2017, 10:55:11 am ---
--- Quote from: dpenev on November 09, 2017, 08:39:41 am ---2. The following doesn't work
dpenev@yni:~$ lxi scpi -ra 192.168.1.59 -m rigol-2000 "CHAN1 DISP?"
lxi: invalid option -- 'm'
--- End quote ---
Correct. The scpi command does not accept '-m'. Only the screenshot command requires this in order to use the corresponding screenshot plugin.
See 'lxi --help' or 'man lxi' to see which options applies to which command.
--- Quote from: dpenev on November 09, 2017, 08:39:41 am ---dpenev@yni:~$ lxi scpi -ra 192.168.1.59 "CHAN1 DISP?"
Error: Timeout
Error: Failed to receive message
Can I send scpi commands to my DS2000
--- End quote ---
Yes, I expect so. Please try without the '-r' option. The raw option is faster but also less reliable because it uses basic RAW/TCP instead of the VXI11/TCP. Perhaps the instrument has crashed maybe due to an invalid command in which case the instrument has a hard time to recover in case of RAW/TCP (handled better by VXI11).
--- End quote ---
Yes without -r I seems to get better results, thank you.
--- Quote from: lundmar on November 09, 2017, 10:55:11 am ---
--- Quote from: dpenev on November 09, 2017, 08:39:41 am ---3. I have Siglent SSA3021X instrument.
lxi screenshot -a 192.168.1.59 #Doesn't work for it. Is it a big deal to add support?
--- End quote ---
If the instrument is LXI compatible, that is, it supports the VXI11/TCP protocol then it should just work.
However, it is not clear to me which Siglent instruments supports VXI11. The documentation for Siglent instruments seem sparse on this topic.
It is possible this instrument does not support VXI11 in which case you might want to try the --raw option instead and maybe in combination with --raw-port if the default port differs from 5555. You might have to do some digging to figure out what port is used (if used at all).
Actually, I've been in contact with Siglent asking if they would like to support the project with some of their instruments for testing so that we can make the tools work with their instruments. Sadly, I haven't heard from them yet. Feel free to write Siglent and ask them to support this project. I think there is a Siglent support thread in this forum where they are listening ;)
--- End quote ---
The Siglent SSA3000 programing manual is at http://www.siglentamerica.com/USA_website_2014/Documents/Program_Material/SSA3000X_ProgrammingGuide_PG0703X_E03D.pdf
Some results below which probably answers some of the questions you have defined ?
dpenev@yni:~/lxi-tools$ lxi scpi -a 192.168.1.61 "*IDN?"
Siglent Technologies,SSA3032X,SSA3XXXXXXXXXXXXX,1.2.8.5a
dpenev@yni:~/lxi-tools$ lxi scpi -a 192.168.1.61 ":SYSTem:TIME?"
024429
dpenev@yni:~/lxi-tools$ lxi scpi -a 192.168.1.61 ":SYSTem:DATE?"
20171110
dpenev@yni:~/lxi-tools$ lxi scpi -a 192.168.1.61 "FREQuency:STAR?"
+1.2560000000E+07
dpenev@yni:~/lxi-tools$ lxi scpi -a 192.168.1.61 "FREQuency:STOP?"
+2.2560000000E+07
dpenev@yni:~/lxi-tools$ lxi scpi -a 192.168.1.61 ":MMEMory:STORe"
dpenev@yni:~/lxi-tools$ lxi screenshot -a 192.168.1.61
Error: Missing model
dpenev@yni:~/lxi-tools$ lxi screenshot -a 192.168.1.61 -m rigol-2000
Error: Failed to receive message
dpenev@yni:~/lxi-tools$ lxi screenshot -a 192.168.1.61 -m rigol-1000
Error: Failed to receive message
dpenev@yni:~/lxi-tools$
It seems ":MMEMory:STORe" can capture the screen but not sure if the data can be retreated remotely.
--- Quote from: lundmar on November 09, 2017, 10:55:11 am ---
--- Quote from: dpenev on November 09, 2017, 08:39:41 am ---4. Few other test samples
lxi screenshot -m rigol-1000 #doesn't work for DP832.
--- End quote ---
I wouldn't expect it to since the plugin is tailored for the 1000z series scopes.
I took a quick look at the DP800 programmers manual and I couldn't find any evidence that it supports remote screenshot downloads so I'm afraid it is not possible to create a working plugin for this series unless there is an undocumented screenshot feature that I'm not aware of.
--- End quote ---
I see
--- Quote from: lundmar on November 09, 2017, 10:55:11 am ---
--- Quote from: dpenev on November 09, 2017, 08:39:41 am ---lxi scpi -a 192.168.1.60 "*IDN?" #OK for my DP832.
It is interesting that for the DP832 If I send wrong scpi command I see "Wrong command" on the instrument display and I can not get any response from now on unless i reboot DP832. Is it a problem of DP832?
--- End quote ---
Please try make sure _not_ to use the raw option in this case. We know that Rigol has issues with stalling invalid commands which ends up blocking the RAW/TCP channel. With VXI11/TCP the client tells the instrument that commands are executed under a certain timeout and it handles it accordingly so you can continue to send commands. With RAW/TCP there is no such mechanism.
In general I can't recommend using the --raw option unless you really need performance gain.
--- End quote ---
I see
Thank you
Dimitar
lundmar:
--- Quote from: dpenev on November 09, 2017, 07:11:58 pm ---I have tested the rigol_2000_png branch. It produce file with png extension but it is actually a bit map, same size, BMP header.
--- End quote ---
Ok. Then it does not look like it is possible to download a PNG screenshot. BMP will have to do for the 2000 series.
--- Quote from: dpenev on November 09, 2017, 07:11:58 pm ---The Siglent SSA3000 programing manual is at http://www.siglentamerica.com/USA_website_2014/Documents/Program_Material/SSA3000X_ProgrammingGuide_PG0703X_E03D.pdf
Some results below which probably answers some of the questions you have defined ?
dpenev@yni:~/lxi-tools$ lxi scpi -a 192.168.1.61 "*IDN?"
Siglent Technologies,SSA3032X,SSA3XXXXXXXXXXXXX,1.2.8.5a
dpenev@yni:~/lxi-tools$ lxi scpi -a 192.168.1.61 ":SYSTem:TIME?"
024429
dpenev@yni:~/lxi-tools$ lxi scpi -a 192.168.1.61 ":SYSTem:DATE?"
20171110
dpenev@yni:~/lxi-tools$ lxi scpi -a 192.168.1.61 "FREQuency:STAR?"
+1.2560000000E+07
dpenev@yni:~/lxi-tools$ lxi scpi -a 192.168.1.61 "FREQuency:STOP?"
+2.2560000000E+07
dpenev@yni:~/lxi-tools$ lxi scpi -a 192.168.1.61 ":MMEMory:STORe"
dpenev@yni:~/lxi-tools$ lxi screenshot -a 192.168.1.61
Error: Missing model
dpenev@yni:~/lxi-tools$ lxi screenshot -a 192.168.1.61 -m rigol-2000
Error: Failed to receive message
dpenev@yni:~/lxi-tools$ lxi screenshot -a 192.168.1.61 -m rigol-1000
Error: Failed to receive message
dpenev@yni:~/lxi-tools$
It seems ":MMEMory:STORe" can capture the screen but not sure if the data can be retreated remotely.
--- End quote ---
I did a quick scan through the manual and it does not seem like there is any documented ways to download a screenshot. Yes, you can store screenshots in the local memory subsystem but there are no ways to download that file remotely either. It's a bit silly they don't support such useful feature. Also, the description of each SCPI command is quite lacking. So, unfortunately it seems it will not be possible to create a screenshot plugin to support this Siglent instrument. I guess the only positive thing here is that sending scpi commands to the instrument works fine.
dpenev:
Indeed,
BTW did you get some useful information from silentna about screen capture from their oscilloscopes?
Thanks
Dimitar
lundmar:
--- Quote from: dpenev on November 09, 2017, 08:14:14 pm ---Indeed,
BTW did you get some useful information from silentna about screen capture from their oscilloscopes?
Thanks
Dimitar
--- End quote ---
No useful details. SDS1000X/SDS2000X are claimed to support screenshots but without instruments to test on I'm going to focus on other features and instruments.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version