Author Topic: Open source lxi-tools and liblxi v1.0 released for GNU/Linux (Read 90422 times)

N0NB · « **Reply #275 on:** March 20, 2018, 05:23:18 pm »

I double checked and the configure script is properly finding the avahi headers and that liblxi and lxi are linked to the avahi libraries on both the desktop and the VM. As both the desktop and VM have the same version of avahi and other libraries installed, the only difference is that the avahi daemon is running on the desktop and not running in the VM.

Here is the output from lxi discover on the desktop:

Code: [Select]

$ lxi discover
Searching for LXI devices - please wait...

Broadcasting on interface lo
Broadcasting on interface eth0

No devices found

Code: [Select]

$ lxi discover -m
Searching for LXI devices - please wait...

No services found

And the same as run in the VM:

Code: [Select]

$ lxi discover 
Searching for LXI devices - please wait...

Broadcasting on interface lo
Broadcasting on interface eth0
  Found "Siglent Technologies,SDS1202X-E,SDS1EBBXXXXXXX,5.1.3.13" on address 192.168.X.X

Found 1 device

Code: [Select]

$ lxi discover -m
Searching for LXI devices - please wait...

Error: Failed to create client: Daemon not running
No services found

Obviously lxi does not find the avahi daemon in the VM but raises no such complaint on the desktop.

I am puzzled that even when the -m is not used, lxi cannot discover the 'scope.

I need to do some more studying of Wireshark to try and isolate any network traffic from lxi as my network interface is too busy to catch any lxi traffic just by watching it scroll by.

lundmar · « **Reply #276 on:** March 20, 2018, 05:31:16 pm »

Quote from: N0NB on March 20, 2018, 05:23:18 pm

Code: [Select]
$ lxi discover -m Searching for LXI devices - please wait... Error: Failed to create client: Daemon not running No services found
Obviously lxi does not find the avahi daemon in the VM but raises no such complaint on the desktop.

Have you tried starting/restarting the avahi daemon manually before calling lxi?

N0NB · « **Reply #277 on:** March 20, 2018, 06:25:11 pm »

False alarm. It looks like a firewall rule is blocking the reply from the 'scope.

I thought I had looked in the logs a few days ago but Slackware logs a bit differently than Debian.

As I use Shorewall, I added the following rule to allow the 'scope's traffic to pass through:

Code: [Select]

ACCEPT          net:192.168.X.0/24     $FW     udp     -       111

All is well now:

Code: [Select]

$ lxi discover
Searching for LXI devices - please wait...

Broadcasting on interface lo
Broadcasting on interface eth0
  Found "Siglent Technologies,SDS1202X-E,SDS1EBBXXXXXXX,5.1.3.13" on address 192.168.X.X

Found 1 device

The key for me figuring this out was working through the liblxi source and seeing that the network braodcast address is obtained and used for the polling. The 'scope replies but since there is no tracking from a SYN packet, the response was blocked (at least that's how I understand it). I found the firewall logging is placed in /var/log/messages and then found the firewall had blocked the 'scope's address. On Slackware dmesg also includes this output.

Carry on!

lundmar · « **Reply #278 on:** March 20, 2018, 07:19:46 pm »

Quote from: N0NB on March 20, 2018, 06:25:11 pm

False alarm. It looks like a firewall rule is blocking the reply from the 'scope.

I thought I had looked in the logs a few days ago but Slackware logs a bit differently than Debian.

As I use Shorewall, I added the following rule to allow the 'scope's traffic to pass through:

Code: [Select]
ACCEPT net:192.168.X.0/24 $FW udp - 111
All is well now:

Code: [Select]
$ lxi discover Searching for LXI devices - please wait... Broadcasting on interface lo Broadcasting on interface eth0 Found "Siglent Technologies,SDS1202X-E,SDS1EBBXXXXXXX,5.1.3.13" on address 192.168.X.X Found 1 device
The key for me figuring this out was working through the liblxi source and seeing that the network braodcast address is obtained and used for the polling. The 'scope replies but since there is no tracking from a SYN packet, the response was blocked (at least that's how I understand it). I found the firewall logging is placed in /var/log/messages and then found the firewall had blocked the 'scope's address. On Slackware dmesg also includes this output.

Carry on!

Ok. Different distributions different problems

lundmar · « **Reply #279 on:** May 05, 2018, 02:34:46 pm »

Hi guys,

Just announcing new releases of lxi-tools and liblxi:

https://github.com/lxi-tools/lxi-tools/releases/tag/v1.20
https://github.com/lxi-tools/liblxi/releases/tag/v1.13

These releases mostly include various bug fixes. Perhaps the most noticeable fix is that now bash auto completion is working with the lxi snap command.

Also, for those new to lua, I've added https://github.com/lxi-tools/lxi-tools/blob/master/test/basic-tests.lua which details concisely how to do basic stuff in Lua. Using this as inspiration you can create some very clean cut and powerful instrument control scripts for whatever purpose you need.

Recently I've been busy with other stuff and haven't had much time to continue the development on lxi-tools. However, during my absence I see that there have been a steady increase in snap users which is great.

Also, rumors are that there is someone out there who have ported lxi-tools to macOS!

Hopefully they will contribute their changes back to the lxi-tools project to benefit everyone. Code contributions are welcome.

crispus · « **Reply #280 on:** June 11, 2018, 07:39:00 am »

Quote from: lundmar on March 13, 2018, 08:48:27 pm

Take a look here, Siglent wrote a post about LXI Tools

Congrats! Keep up the good work

lundmar · « **Reply #281 on:** June 11, 2018, 01:24:34 pm »

Quote from: crispus on June 11, 2018, 07:39:00 am

Quote from: lundmar on March 13, 2018, 08:48:27 pm
Take a look here, Siglent wrote a post about LXI Tools
Congrats! Keep up the good work

Thanks

The next thing on the TODO list is improving the mDNS feature. I expect to add a new discover interface to liblxi which will make it possible for the lxi command line tool to select which network interface is broadcasted on. For example:

Code: [Select]

$ lxi discover --interface wlan0

This way we can avoid broadcasting on all networks available. It will also speed up the discovery step.

The mDNS feature in lxi-gui also needs some TLC.

crispus · « **Reply #282 on:** June 26, 2018, 10:58:32 am »

Did anyone tried to use measure item function on a DS1000z?

Code: [Select]

:MEASure:ITEM OVERshoot,CHANnel2 /* Enable the overshoot measurement of CH2 */ 
:MEASure:ITEM? OVERshoot,CHANnel2 /* The query returns 8.888889e-03 */

I was trying to measure VPP on channel 1, but all it does is to show on the scope's screen the measurement...
The query does not return anything...

lundmar · « **Reply #283 on:** June 30, 2018, 08:09:14 am »

Quote from: crispus on June 26, 2018, 10:58:32 am

Did anyone tried to use measure item function on a DS1000z?
Code: [Select]
:MEASure:ITEM OVERshoot,CHANnel2 /* Enable the overshoot measurement of CH2 */ :MEASure:ITEM? OVERshoot,CHANnel2 /* The query returns 8.888889e-03 */I was trying to measure VPP on channel 1, but all it does is to show on the scope's screen the measurement...
The query does not return anything...

I tried firing your commands and I get this:

Code: [Select]

$ lxi scpi --address 192.168.1.112 ":MEASure:ITEM OVERshoot,CHANnel2"
$ lxi scpi --address 192.168.1.112 ":MEASure:ITEM? OVERshoot,CHANnel2"
9.9E37

crispus · « **Reply #284 on:** July 01, 2018, 09:26:34 am »

Thanks for reply.

As standalone commands it works. I was trying in interactive mode and it doesn't. (build from sources, v1.20)

Code: [Select]

$ src/lxi --version
lxi v1.20
$ src/lxi scpi -a 192.168.1.149 -i
Connected to 192.168.1.149
Entering interactive mode (ctrl-d to quit)

lxi> *IDN?
RIGOL TECHNOLOGIES,MSO1104Z,DS1ZDxxxxxxxx,00.04.04.SP3
lxi> :MEASure:ITEM? OVERshoot,CHANnel2
lxi> 

$ src/lxi scpi -a 192.168.1.149 ":MEASure:ITEM? OVERshoot,CHANnel2"
2.306453e-02

lundmar · « **Reply #285 on:** July 01, 2018, 11:53:16 am »

Quote from: crispus on July 01, 2018, 09:26:34 am

Thanks for reply.

As standalone commands it works. I was trying in interactive mode and it doesn't. (build from sources, v1.20)
Code: [Select]
$ src/lxi --version lxi v1.20 $ src/lxi scpi -a 192.168.1.149 -i Connected to 192.168.1.149 Entering interactive mode (ctrl-d to quit) lxi> *IDN? RIGOL TECHNOLOGIES,MSO1104Z,DS1ZDxxxxxxxx,00.04.04.SP3 lxi> :MEASure:ITEM? OVERshoot,CHANnel2 lxi> $ src/lxi scpi -a 192.168.1.149 ":MEASure:ITEM? OVERshoot,CHANnel2" 2.306453e-02

Thanks for reporting the bug. Luckily it was a simple fix:
https://github.com/lxi-tools/lxi-tools/commit/c244dbe573d191f8bd2513f0f61638209bc528dc

I haven't tested it but it should do the trick

crispus · « **Reply #286 on:** July 01, 2018, 12:17:50 pm »

So quick. It works. Thanks.

lundmar · « **Reply #287 on:** July 08, 2018, 09:43:56 am »

FYI - I've just pushed a new release of lxi-tools:

https://github.com/lxi-tools/lxi-tools/releases/tag/v1.21

It basically only includes the latest change to fix interactive mode when firing question SCPI commands. The main reason I'm pushing a new stable release is to update the lxi-tools snap on the stable release channel because some users have reported issues with missing fonts - an issue which is automagically fixed by an update because of some updated snapcraft infrastructure.

HoracioDos · « **Reply #288 on:** July 10, 2018, 12:57:21 pm »

Quote from: lundmar on July 08, 2018, 09:43:56 am

automagically

This has been my preferred word for years

. I see that's universal. Why everyone loves automagic solutions?

lundmar · « **Reply #289 on:** July 10, 2018, 02:53:12 pm »

Quote from: HoracioDos on July 10, 2018, 12:57:21 pm

Quote from: lundmar on July 08, 2018, 09:43:56 am
automagically
This has been my preferred word for years . I see that's universal. Why everyone loves automagic solutions?

Easy, everyone loves magic

lundmar · « **Reply #290 on:** August 17, 2018, 07:50:54 am »

Here is a shout out and big thank you to Siglent for supporting the open source lxi-tools project!

They have recently decided that we can keep the SDS1204X-E which was lent to us to support the ongoing development of lxi-tools. See https://www.eevblog.com/forum/testgear/open-source-lxi-tools-and-liblxi-v1-0-released-for-gnulinux/msg1394796/#msg1394796

The device has been very helpful for the development and testing of lxi-tools. It will now become a permanent part of a regression test setup to make sure lxi-tools will continue to work with Siglent devices.

Personally I'm happy to finally see instrument manufacturers be serious about supporting open source - this way we will all get better tools for our instruments. It is also worth noticing that Siglent is very responsive to feedback from the EEVBlog forum users and I'm sure that has helped make their instruments better and more desirable. I wish more manufacturers would do the same. It's the new way of doing business. Good job Siglent

https://www.siglentamerica.com/application-note/lxi-tools/
https://www.siglentamerica.com/video/lxi-tools/

List of lxi-tools sponsors: https://github.com/lxi-tools/lxi-tools#9-sponsors

lundmar · « **Reply #291 on:** August 17, 2018, 10:21:32 am »

Just some interesting statistics retrieved from the snap system:

This statistics only count snap installs, not lxi-tools installations installed via native distro packages.

cnkz · « **Reply #292 on:** September 12, 2018, 05:48:31 pm »

I tried to compile the tools....

First the install steps description in the readmes are not correct, they say:

Code: [Select]

./configure; make; make install But there are no configure scripts...

I think i need to use the autogen.sh scripts to generate the configure scripts but they do give errors:

a) for liblxi

Code: [Select]

./autogen.sh 
autoreconf: Entering directory `.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal --force 
autoreconf: configure.ac: tracing
autoreconf: configure.ac: not using Libtool
autoreconf: running: /usr/bin/autoconf --force
configure.ac:22: error: possibly undefined macro: AC_ENABLE_SHARED
      If this token and others are legitimate, please use m4_pattern_allow.
      See the Autoconf documentation.
configure.ac:23: error: possibly undefined macro: AC_ENABLE_STATIC
autoreconf: /usr/bin/autoconf failed with exit status: 1

b) for lxitools

Code: [Select]

./autogen.sh 
autoreconf: Entering directory `.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal --force 
autoreconf: configure.ac: tracing
autoreconf: configure.ac: not using Libtool
autoreconf: running: /usr/bin/autoconf --force
autoreconf: running: /usr/bin/autoheader --force
autoreconf: running: automake --add-missing --copy --force-missing
configure.ac:6: installing './ar-lib'
configure.ac:6: installing './compile'
configure.ac:4: installing './install-sh'
configure.ac:4: installing './missing'
src/Makefile.am:2: error: library used but 'RANLIB' is undefined
src/Makefile.am:2:   The usual way to define 'RANLIB' is to add 'AC_PROG_RANLIB'
src/Makefile.am:2:   to 'configure.ac' and run 'autoconf' again.
src/Makefile.am: installing './depcomp'
autoreconf: automake failed with exit status: 1

Any idea how to fix that?

lundmar · « **Reply #293 on:** September 13, 2018, 08:13:01 am »

Quote from: cnkz on September 12, 2018, 05:48:31 pm

I tried to compile the tools....

First the install steps description in the readmes are not correct, they say:
Code: [Select]
./configure; make; make install But there are no configure scripts...

I think i need to use the autogen.sh scripts to generate the configure scripts but they do give errors:

It's because you pulled the git development code. What you want to do is download and use the release tarballs - only they include the configure script etc..

If you don't want to bother with autotools I recommend simply installing lxi-tools via snap to get latest version:

Code: [Select]

$ snap install lxi-tools

If you do insist on building from git source please see the top post in this thread where you will find a description of how to build from git source.

cnkz · « **Reply #294 on:** September 14, 2018, 08:25:15 pm »

Thanks, i tried (first time) snap and it works.

lundmar · « **Reply #295 on:** September 15, 2018, 09:19:33 am »

Quote from: cnkz on September 14, 2018, 08:25:15 pm

Thanks, i tried (first time) snap and it works.

Great

Snap is pretty cool - it is working on the most popular gnu/linux platforms and it makes it very easy for me to push updates to end users.

awallin · « **Reply #296 on:** September 24, 2018, 07:27:04 pm »

There's now a quick hack at python bindings for liblxi over here: https://github.com/lxi-tools/python-liblxi

if you are brave and want to test then:
- checkout that repo
- git submodule init&update
- autogen and configure in the liblxi-dir
- out of source cmake-build for the python module

I did not have time to test with real hardware yet - may or may not work...
do post issues and pull-requests on github if you find bugs or fix them!

thanks, Anders.

lundmar · « **Reply #297 on:** April 13, 2019, 08:03:00 pm »

For a while, the screenshot feature in the snap version of lxi-gui has been broken because of a bug revealed by an updated snap toolchain.

This issue has now been solved and an updated lxi-tools snap is available.

lundmar · « **Reply #298 on:** May 01, 2019, 11:10:57 pm »

Quote from: shodan@micron on April 26, 2019, 07:07:54 am

Thanks dear lundmar!
I trying make console datalogger based on your's liblxi, for my Raspberry Pi.
Low power consumption of Raspberry Pi - is very good for very long measurement's cycle. Now i can do measurement's without my PC.

Your's lib work fine via VXI-11.

I hope share first release on next week, now it testing and debugging stage.

Good stuff

I'm glad liblxi seems to perform well for your data logger application. Using the rpi for a low cost data logger is an excellent idea.

enz · « **Reply #299 on:** May 07, 2019, 07:48:15 am »

Today I cloned the lxi-tools git repository.
I tried to compile the lxi-gui under windows with QT-Creator.
But I got an error about a missing include file "lxi.h".
It is included from main.cpp and mainwindow.cpp.

I couldn't find it in the project directory tree.

Maybe it is missing in the project?

Best regards,
Martin


EEVblog Main Site	EEVblog on Youtube	EEVblog on Twitter	EEVblog on Facebook	EEVblog on Odysee

Poll

What OS platform would you like to see lxi-tools ported to next?

Author Topic: Open source lxi-tools and liblxi v1.0 released for GNU/Linux (Read 90422 times)

Share me