| Products > Test Equipment |
| Open source lxi-tools and liblxi v1.0 released for GNU/Linux |
| << < (56/67) > >> |
| N0NB:
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: ---$ lxi discover Searching for LXI devices - please wait... Broadcasting on interface lo Broadcasting on interface eth0 No devices found --- End code --- --- Code: ---$ lxi discover -m Searching for LXI devices - please wait... No services found --- End code --- And the same as run in the VM: --- Code: ---$ 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 --- End code --- --- Code: ---$ lxi discover -m Searching for LXI devices - please wait... Error: Failed to create client: Daemon not running No services found --- End code --- 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:
--- Quote from: N0NB on March 20, 2018, 05:23:18 pm --- --- Code: ---$ lxi discover -m Searching for LXI devices - please wait... Error: Failed to create client: Daemon not running No services found --- End code --- Obviously lxi does not find the avahi daemon in the VM but raises no such complaint on the desktop. --- End quote --- Have you tried starting/restarting the avahi daemon manually before calling lxi? |
| N0NB:
False alarm. It looks like a firewall rule is blocking the reply from the 'scope. :palm: 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: ---ACCEPT net:192.168.X.0/24 $FW udp - 111 --- End code --- All is well now: --- Code: ---$ 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 --- End code --- 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:
--- 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. :palm: 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: ---ACCEPT net:192.168.X.0/24 $FW udp - 111 --- End code --- All is well now: --- Code: ---$ 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 --- End code --- 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! :-+ --- End quote --- Ok. Different distributions different problems ;D |
| lundmar:
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. |
| Navigation |
| Message Index |
| Next page |
| Previous page |