Products > Test Equipment
Open source lxi-tools and liblxi v1.0 released for GNU/Linux
lundmar:
--- Quote from: RoGeorge on November 06, 2017, 06:28:09 pm ---Feature request 6.3. - make model optional, and auto identify the model using the IP and *IDN?
--- End quote ---
Thanks for this good idea feature request :-+ . I've implemented it in https://github.com/lxi/lxi-tools/commit/4b07a40e1c07afb099b0842a34e1f01e8031b462
This means that the lxi tool can now be used like this:
--- Code: ---$ lxi screenshot --address 192.168.1.210
Loaded rigol-1000 screenshot plugin
Saved screenshot image to screenshot_192.168.1.210_2017-11-10_16:07:48.png
--- End code ---
The way it works is that it retrieves the ID string of the instrument and matches that against regular expressions provided in each plugin. The plugin with most matches is selected. Using regular expression matching is quite powerful so I expect this will work fine for future needs. Currently, only the Rigol plugins work with this feature as they are the only ones defining useful .regex entries. The other plugins will have to follow when someone shows up with real instruments that can be tested.
Also, I've done away with any model vs. plugin confusion and simplified the interface to manually specify which screenshot plugin to use:
--- Code: ---$ lxi screenshot --address 192.168.1.210 --plugin rigol-1000
Saved screenshot image to screenshot_192.168.1.210_2017-11-10_16:08:36.png
--- End code ---
--- Quote from: RoGeorge on November 06, 2017, 06:28:09 pm ---Feature request 6.5. - add an option for instrument ID in the filename (can be more than just 1 oscilloscope on the same network, so after a save there is no way to identify where from is the captured screen)
--- End quote ---
I've implemented a compromise solution in https://github.com/lxi/lxi-tools/commit/080681f7af460b47c24ad09f46809fa65c5cb687
Trying to add unique instrument ID in the screenshot filename is troublesome because the IDN strings have no strictly guaranteed format (only guidelines) so we can run into all sorts of trouble trying to render something useful from it. Hence the alternative solution is to simply embed the instrument IP in the screenshot filename to help tell from which instrument screenshot files originate. It's not an unique identifier but it is sufficient for most use cases.
lundmar:
Some important features and bug fixes have been added so I'm releasing a new version of lxi-tools:
https://github.com/lxi/lxi-tools/releases/download/v1.7/lxi-tools-1.7.tar.xz
For a summary of changes please see:
https://github.com/lxi/lxi-tools/releases/tag/v1.7
Thanks to especially RoGeorge for his thorough testing and useful feature requests. Also thanks to dpenev for his testing and help fixing the rigol-2000 screenshot plugin. I've added the instruments that you guys have tested working in the list of tested instruments in the README of lxi-tools.
P.S.: I want to add you guys to the list of contributors in the AUTHORS file. If you are ok with that, please let me know.
lundmar:
I've refined and added some more information to the original post that started this thread. People might find it useful information.
dpenev:
Hello,
A bit off topic but can be useful for someone .
I have SSA3021X and inspired by the lxi-tool I have implemented procedure to capture the instrument screen from a PC.
It uses lxi-tool to send ":MMEMory:STORe" command
and telnet to download the file.
I hope Siglent will implement a way to transfer a file using scpi command so this script will become unnecessary
extract the two scripts from the tar in a directory
from this directory execute
--- Code: ---./ssa3000x_print print.png
--- End code ---
Note that you need to specify the file name with the extension png.
I guess each time new file name is required.
Files with path is not supported.
The shell scrip is not polished but is working for me.
Feel free to improve and please share.
Thanks
Dimitar
lundmar:
--- Quote from: dpenev on November 13, 2017, 09:18:39 pm ---I hope Siglent will implement a way to transfer a file using scpi command so this script will become unnecessary
--- End quote ---
I hope so too. It's quite the detour to have to go manually retrieve the screenshot file like that through the back channel but nice job getting there ;)
You should request Siglent to create a new firmware for the SSA3000 so that it becomes possible to simply dump the screenshot directly via the VXI11 channel. It would be faster and more elegant and should be trivial for them to implement.
I like the fact they are using TI AM335x but its funny to see how they did not remove the traces of the "evm" strings.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version