Products > Test Equipment
Open source lxi-tools and liblxi v1.0 released for GNU/Linux
lundmar:
--- Quote from: ralphrmartin on December 28, 2017, 07:29:14 pm ---Screenshot works well now for keysight, producing a bmp file, and for the Rigol, also producing a bmp file. :-+
(Without specifying plugins to use).
Keep up the good work! :)
--- End quote ---
Thanks :)
And thank you for your patience getting the snap running. Great to finally have a Keysight instrument tested working :)
For your testing effort I've added you to the list of contributors.
lundmar:
New releases available via snap or source.
Changes:
https://github.com/lxi-tools/lxi-tools/releases/tag/v1.16
https://github.com/lxi-tools/liblxi/releases/tag/v1.9
The changes fix the keysight-ivx and rigol-dg4000 screenshot plugins. The discover feature has also been improved with a fallback to request ID via HTTP/XML - this should make it possible to discover instruments from e.g. Aim-TTi.
Also added are fixes making it ready for packaging in Debian and FreeBSD.
lundmar:
I know that some people would welcome a GUI for lxi-tools.
Here is a first try at adding a simple QT5 GUI:
In its first iteration it can simply discover instruments via VXI-11.
To keep the UI simple and easy-to-use I think the next step would be to feature a right-click context menu for the listed instruments which provides the following options:
* Send SCPI command
* Take screenshot (only shown if a matching screenshot plugin is available)
* Benchmark
* Copy Instrument ID
* Copy IP Address
The GUI application binary will be named lxi-gui but will also be possible to start via the commandline lxi tool using the following command: lxi gui
If there are any GUI or QT5 designers out there who are interested in helping creating this GUI application feel free to join in :)
Also, if anyone wants to add a custom, fast, simple or advanced GUI for their particular instrument it is now possible with this lxi-tools/QT5 stack. Contributors are welcome to add any useful instrument tools to lxi-tools.
ralphrmartin:
Just a thought: it could perhaps be useful if some of the most common SCPI commands could be available in a menu, e.g. perform self-test.
lundmar:
--- Quote from: ralphrmartin on January 03, 2018, 06:35:33 pm ---Just a thought: it could perhaps be useful if some of the most common SCPI commands could be available in a menu, e.g. perform self-test.
--- End quote ---
Yeah - the "IEEE 488.2 Common Commands".
http://na.support.keysight.com/vna/help/latest/Programming/GP-IB_Command_Finder/Common_Commands.htm
I'm considering introducing separate tabs/panes for each of the following features: Discovery, SCPI, Screenshot, Benchmark.
Then have the SCPI, Screenshot, and Benchmark features operate on the instrument selected in Discovery.
I'm about to focus on implementing the HiSlip protocol - it will be a while before I revisit the GUI so I'm open for ideas and suggestions.
An instrument manufacturer is kindly sponsoring a HiSlip instrument so I will soon have something to test against :-+
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version