Products > Test Equipment

Open source lxi-tools v2.0 released

<< < (3/22) > >>

optotester:
Pull request done on lxi-tools and liblxi for macOS compatibility.
liblxi can be easily compiled with meson, but I would advise to use XCode to generate a signed library.

For lxi-tools it is more complex and I did not adapt the meson build files, it has to be build through XCode (you can install the dependencies through brew, except gtk and gtksourceview5).
For gtk, you must compile manually this version: https://gitlab.gnome.org/sumibi-yakitori/gtk/-/commits/wip/chergert/yakitori/macos-fixes
For gtksourceview, you must compile the master version.

Before compiling, do not forget to run:

--- Code: ---glib-compile-resources --target=lxi_gui-resources.c --generate-source lxi_gui.gresource.xml --c-name=lxi_gui

--- End code ---

Before launching for the first time, do not forget to install the config file either:

--- Code: ---cp data/io.github.lxi-tools.lxi-gui.gschema.xml /usr/local/share/glib-2.0/schemas
glib-compile-schemas /usr/local/share/glib-2.0/schemas
--- End code ---

I will release a binary soon.

lundmar:

--- Quote from: optotester on February 03, 2022, 04:13:10 pm ---Pull request done on lxi-tools and liblxi for macOS compatibility.

--- End quote ---

Thanks, I'll review the PR as soon as possible.

For building on MacOs I trust you will take care of that. I don't have access to a Mac environment.

I assume MacOs has Brew channels for distributing 3rd party applications.

probe:
Hi Lundmar,

Many thanks for this fantastic tool!
May I give some feedback? LXI-tools was able to discover 5 devices (Rigol DS1054Z, Siglent SDS2104x plus, Siglent SSA 3021X Plus, Rigol DG1022Z and Rigol DP832, all "hacked" into their more capable versions (e.g. The SSA 3021X plus now thinks its is a SVA1032X) but funnily enough the only device that isn't liberated doesn't show up when running lxi discover, a Rigol DM3068. It is reachable though when I run lxi benchmark -a <IP address>. I'm happy to help out if you want me to help make it discoverable.

More pressing thing, I tried to run LXI-tools V2 on Kali, Ubuntu and Raspberry pi OS. Kali and Rpi don't have the V2 yet, Ubuntu does but when I try to run lxi-gui it gives an error that it can not connect to a screen. I installed V2 on Rpi via snap but also there you get the error that lxi-gui can not start due to a x-window error. I'm posting this from a Mac so can not post the precise error but will try in a separate post.

BTW, building from source on Kali is painful...

probe:
pi@raspberrypi:~ $ lxi-gui

(lxi-gui:2313): Gdk-ERROR **: 16:44:18.660: The program 'lxi-gui' received an X Window System error.
This probably reflects a bug in the program.
The error was 'GLXBadFBConfig'.
  (Details: serial 2141 error_code 167 request_code 152 (GLX) minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the GDK_SYNCHRONIZE environment
   variable to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

lundmar:

--- Quote from: probe on February 04, 2022, 03:33:18 pm ---Many thanks for this fantastic tool!
May I give some feedback?

--- End quote ---
Thank you. Of course, feedback is very welcome so we can fix any bugs found!


--- Quote ---LXI-tools was able to discover 5 devices (Rigol DS1054Z, Siglent SDS2104x plus, Siglent SSA 3021X Plus, Rigol DG1022Z and Rigol DP832, all "hacked" into their more capable versions (e.g. The SSA 3021X plus now thinks its is a SVA1032X) but funnily enough the only device that isn't liberated doesn't show up when running lxi discover, a Rigol DM3068. It is reachable though when I run lxi benchmark -a <IP address>. I'm happy to help out if you want me to help make it discoverable.

--- End quote ---

Hmm. I actually have the smaller brother DM3058 sitting right next to me and it discovers fine using the default discovery method. It does not support discovery via mDNS though. Both of these products are LXI certified and they should be discoverable with the current implementation, especially since I believe they share the same firmware codebase. Which discovery method are you using? Default or mDNS? See lxi-gui preferences.


--- Quote ---More pressing thing, I tried to run LXI-tools V2 on Kali, Ubuntu and Raspberry pi OS. Kali and Rpi don't have the V2 yet, Ubuntu does but when I try to run lxi-gui it gives an error that it can not connect to a screen. I installed V2 on Rpi via snap but also there you get the error that lxi-gui can not start due to a x-window error. I'm posting this from a Mac so can not post the precise error but will try in a separate post.

BTW, building from source on Kali is painful...

--- End quote ---

Building lxi-tools with lxi-gui is a bit involved and painful on most distributions right now because lxi-gui requires very recent versions of core components such as GTK4.6.0, libadwaita 1.0.1, etc.

I don't expect lxi-tools to work easily or maybe at all on older distributions, with or without snap.

I think both of your issues may require quite a lot of debug so I would ask you to report your bugs in the Github issue tracker here: https://github.com/lxi-tools/lxi-tools/issues

Then we can continue from there.

Thanks.

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