Products > Test Equipment

Open source lxi-tools and liblxi v1.0 released for GNU/Linux

<< < (62/67) > >>

ralphrmartin:
But the interesting thing is that lxi-tools gets the correct output from the device, e.g. showing the correct identification presumably in response to an *IDN?

Rigol's own ultra sigma also gives the correct output too.

It's only a direct telnet connection that returns this garbled output (verified from a Mac (telnet), a PC (putty) and a Linux box (telnet) - all the same).

Input is clearly going into the device OK, e.g. I can send commands from telnet to turn things on and off and see the expected responses.

Other commands which generate output seem to do the same, sending strings with the correct first character which is then repeated. E.g. If I query the impedance, I get 55, not 50.

How can lxi-tools be getting the correct output, if telnet is not?

lundmar:

--- Quote from: ralphrmartin on October 07, 2020, 04:19:27 pm ---Hi Lundmar

three things, if you are still there and listening:

--- End quote ---

I'm back - I've been busy IRL and neglecting the lxi-tools project for a long time but now I'm back and some interesting changes are coming :)


--- Quote ---(1) Discover and SCPI commands seem to work for Rigol RSA3000 series spectrum analyzers  :-+ but screen shot does not.

--- End quote ---

I'm sure we can figure that one out - just takes a little digging in the RSA 3000 programmers guide and an update to one of the existing rigol screenshot plugins or maybe a new one. Feel free to create a bug report / feature request in the github issue tracker: https://github.com/lxi-tools/lxi-tools/issues


--- Quote ---(2) If you have a 4K display, the GUI is too small to read comfortably - is there any chance of scaling it up for high dpi displays?

--- End quote ---

Yes, hi-dpi scaling support is coming. One of the big changes coming is actually a total rewrite of the lxi-gui application. I've kicked out the old QT based lxi-gui application in favour of a much more modern looking GTK4 based application and that also implies hi-dpi support. You can take a peak at some screenshots of the new lxi-gui application here: https://github.com/lxi-tools/lxi-tools

Part of the move to the new lxi-gui is also to make it easy to install lxi-gui on Windows with the new WSL2/wayland feature.


--- Quote ---(3)  While lxi-tools reads output fine with from the RSA3000, if I simply telnet to its LXI port, the output is garbled: it seems I just get the first character repeated, rather than the expected string, so for example, if I do *IDN? the output is RRRRRRRRRRRRRRRRRRRRRRRR some large number of times rather than the correct string saying Rigol... whatever. Can you enlighten me as to what the issue is here? Is there anything I can do to make simple telnet output the correct strings instead?

--- End quote ---

Yeah, that wont work. LXI compatible instruments uses either VXI11 or raw/TCP for communicating commands - you likely telnetted into the VXI11 port and so you get gobbledygook.

RoGeorge:
Thank you for the new additions, I'm eager to try them (probably next year, my desktop install just died 2 days ago).
So far the new lxi/GUI looks good by the github pics!   :-+



As a feature request, will it be possible to have the LXI GUI as a native install in the repositories, too, same as the lxi-tools, please?

I mean, in the latest Ubuntu 20.04.3 LTS repositories, the lxi-tools can be installed with "sudo apt install lxi-tools", while the GUI can only be installed as a "snap" install.  Some users are trying to avoid snap install for various reasons, I don't like snaps mostly because snap installed programs, when launched, are starting visible slower than a native install.

lundmar:

--- Quote from: RoGeorge on December 26, 2021, 10:14:15 am ---Thank you for the new additions, I'm eager to try them (probably next year, my desktop install just died 2 days ago).
So far the new lxi/GUI looks good by the github pics!   :-+

--- End quote ---

Thanks, I think it is looking pretty good. Writing it in GTK4 has been a nice experience - modern GUI toolkits have improved a lot. The application is really fast now because it renders in OpenGL/GLES/Vulkan and the modern toolkit has many cool subtle features never seen in any classic GUI.


--- Quote ---As a feature request, will it be possible to have the LXI GUI as a native install in the repositories, too, same as the lxi-tools, please?

I mean, in the latest Ubuntu 20.04.3 LTS repositories, the lxi-tools can be installed with "sudo apt install lxi-tools", while the GUI can only be installed as a "snap" install.  Some users are trying to avoid snap install for various reasons, I don't like snaps mostly because snap installed programs, when launched, are starting visible slower than a native install.

--- End quote ---

Yes, once I make an official release the package maintainers will pick them up when they have time and eventually you will see lxi-tools as native packages in various distributions. Snap is just a way to distribute a release quickly but I am aware of the performance hit that snaps take but for this type of application it matters less.

N0NB:
Going from Qt to GTK is definitely not a path well traveled that I've seen.  Regardless, good to see you're back to coding again.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

There was an error while thanking
Thanking...
Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod