Author Topic: Open source lxi-tools v2.7 released  (Read 19696 times)

0 Members and 1 Guest are viewing this topic.

Offline lundmarTopic starter

  • Frequent Contributor
  • **
  • Posts: 436
  • Country: dk
Re: Open source lxi-tools v2.0 released
« Reply #25 on: February 07, 2022, 09:49:27 pm »
Hello lundmar,

I looked in your code out of interest, because I wanted to know which programming language you use. I don't know C, but I poked around in the code a bit and I noticed the structure with the flags. You use the operation flags 'WaitLock' and 'End'. I don't use flags in my programs, and so I could fix the error with DM3068. But I may be wrong, I just looked in the browser at Github.

Code: [Select]
vxi11.c

int vxi11_send(void *data, const char *message, int length, int timeout)
183 {
...
193     write_params.flags = 0x9;
...

Peter

It's okay - we figured out the problem here: https://github.com/lxi-tools/lxi-tools/issues/42

lxi-tools is working perfectly fine with the DM3068 - it was simply a user misconfiguration of the device that prevented it from responding.

It's been a long time since I've written the vxi11 client code so I had to take a quick look at the vxi11 spec and it turns out that even though I'm setting the waitlock flag, it does not have any effect because I set the lock_timeout value to 0. This means it will return with an error immediately in case the device is locked by another link, which is basically the same as not using the waitlock flag. I probably should change the flag but this code has been tested with many instruments and so far none have failed yet.
« Last Edit: February 07, 2022, 10:27:40 pm by lundmar »
https://lxi-tools.github.io - Open source LXI tools
https://tio.github.io - A simple serial device I/O tool
 

Offline Sergeant82d

  • Newbie
  • Posts: 5
  • Country: us
Still no joy on RPI4
« Reply #26 on: February 10, 2022, 01:33:52 am »
Martin,

I finally had time to work on my home lab RPI4, reworking it and getting it back up and running. New SD Card, new OS install, all updates, installed and updated Snapd, and snap installed v2.1. I did edit the "original" file that was preventing it, but...  :(

It is installed, and works from the command line, but only gives GTK errors for the lxi-gui version.

Quote

pi@raspberrypi:~ $ lxi-tools.lxi-gui

(lxi-gui:2036): Gtk-WARNING **: 19:18:25.159: Theme parser error: Default-light.css:3:20-21: Expected ':'

(lxi-gui:2036): Gtk-WARNING **: 19:18:25.169: Theme parser warning: Default-light.css:1389:19-208: Unterminated block at end of document

(lxi-gui:2036): Gtk-WARNING **: 19:18:25.169: Theme parser warning: Default-light.css:118:32-1389:208: Unterminated block at end of document

(lxi-gui:2036): Gtk-WARNING **: 19:18:25.169: Theme parser warning: Default-light.css:100:1164-1389:208: Unterminated block at end of document

(lxi-gui:2036): Gtk-WARNING **: 19:18:25.169: Theme parser warning: Default-light.css:95:111-1389:208: Unterminated block at end of document

(lxi-gui:2036): Gtk-WARNING **: 19:18:25.170: Theme parser warning: Default-light.css:95:75-1389:208: Unterminated block at end of document

(lxi-gui:2036): Gtk-WARNING **: 19:18:25.170: Theme parser warning: Default-light.css:95:39-1389:208: Unterminated block at end of document

(lxi-gui:2036): Gtk-WARNING **: 19:18:25.170: Theme parser warning: Default-light.css:93:92-1389:208: Unterminated block at end of document

(lxi-gui:2036): Gtk-WARNING **: 19:18:25.170: Theme parser warning: Default-light.css:93:11-1389:208: Unterminated block at end of document

(lxi-gui:2036): Gtk-WARNING **: 19:18:25.170: Theme parser warning: Default-light.css:91:66-1389:208: Unterminated block at end of document

(lxi-gui:2036): Gtk-WARNING **: 19:18:25.170: Theme parser warning: Default-light.css:62:786-1389:208: Unterminated block at end of document

(lxi-gui:2036): Gtk-WARNING **: 19:18:25.170: Theme parser warning: Default-light.css:62:693-1389:208: Unterminated block at end of document

(lxi-gui:2036): Gtk-WARNING **: 19:18:25.171: Theme parser warning: Default-light.css:37:99-1389:208: Unterminated block at end of document

(lxi-gui:2036): Gtk-WARNING **: 19:18:25.171: Theme parser warning: Default-light.css:16:195-1389:208: Unterminated block at end of document

(lxi-gui:2036): Gtk-WARNING **: 19:18:25.171: Theme parser warning: Default-light.css:16:162-1389:208: Unterminated block at end of document

(lxi-gui:2036): Gtk-WARNING **: 19:18:25.171: Theme parser warning: Default-light.css:16:35-1389:208: Unterminated block at end of document

(lxi-gui:2036): Gtk-WARNING **: 19:18:25.171: Theme parser warning: Default-light.css:7:898-1389:208: Unterminated block at end of document

(lxi-gui:2036): Gtk-WARNING **: 19:18:25.171: Theme parser warning: Default-light.css:7:836-1389:208: Unterminated block at end of document

(lxi-gui:2036): Gtk-WARNING **: 19:18:25.171: Theme parser warning: Default-light.css:7:402-1389:208: Unterminated block at end of document

(lxi-gui:2036): Gtk-WARNING **: 19:18:25.171: Theme parser warning: Default-light.css:4:583-1389:208: Unterminated block at end of document

(lxi-gui:2036): Gtk-WARNING **: 19:18:25.172: Theme parser warning: Default-light.css:3:15-1389:208: Unterminated block at end of document

(lxi-gui:2036): Gtk-WARNING **: 19:18:25.172: Theme parser warning: Default-light.css:3:13-1389:208: Unterminated block at end of document

(lxi-gui:2036): Gtk-WARNING **: 19:18:25.172: Theme parser error: gtk.css:1:75-76: Expected a valid selector

(lxi-gui:2036): Gdk-ERROR **: 19:18:26.686: Resource path /org/gtk/libgtk/icons/16x16/actions/value-decrease-symbolic.symbolic.png is not a valid image: Error reading png (IDAT: CRC error)
Trace/breakpoint trap



As I said - from the command line, it works fine. But... I don't want to use the command line! This is hobby stuff - I don't use it all day, or often enough to remember all the commands. Sorry.  :-//

Thanks for your help. Very much looking forward to seeing my lineup of Siglent machines on there!
 

Offline lundmarTopic starter

  • Frequent Contributor
  • **
  • Posts: 436
  • Country: dk
Re: Still no joy on RPI4
« Reply #27 on: February 10, 2022, 02:14:10 am »
As I said - from the command line, it works fine. But... I don't want to use the command line! This is hobby stuff - I don't use it all day, or often enough to remember all the commands. Sorry.  :-//

That's perfectly fine - I made lxi-gui for those who prefer graphical applications. Unfortunately I suspect the problem is that the ARM build is inherently broken with GTK4 for now. The errors I see makes little sense.

Update: I've talked to some of the GTK4 developers. They say that GTK4 for arm64 is largely untested so they are not surprised there are errors.

I'll update GTK4 once they do the next official release and then maybe the problem goes away.
« Last Edit: February 10, 2022, 02:35:09 am by lundmar »
https://lxi-tools.github.io - Open source LXI tools
https://tio.github.io - A simple serial device I/O tool
 

Offline lundmarTopic starter

  • Frequent Contributor
  • **
  • Posts: 436
  • Country: dk
Re: Still no joy on RPI4
« Reply #28 on: February 10, 2022, 10:07:50 pm »
Quote

pi@raspberrypi:~ $ lxi-tools.lxi-gui

(lxi-gui:2036): Gtk-WARNING **: 19:18:25.159: Theme parser error: Default-light.css:3:20-21: Expected ':'

(lxi-gui:2036): Gtk-WARNING **: 19:18:25.169: Theme parser warning: Default-light.css:1389:19-208: Unterminated block at end of document

...

(lxi-gui:2036): Gtk-WARNING **: 19:18:25.172: Theme parser error: gtk.css:1:75-76: Expected a valid selector

(lxi-gui:2036): Gdk-ERROR **: 19:18:26.686: Resource path /org/gtk/libgtk/icons/16x16/actions/value-decrease-symbolic.symbolic.png is not a valid image: Error reading png (IDAT: CRC error)
Trace/breakpoint trap

Please try latest snap edge version on your RPI4:

Code: [Select]
$ snap refresh lxi-tools --edge

It uses an older version of GTK4 which prepares the resources such as Default-light.css in a different way. If it works I will work with the GTK4 devs to get it fixed in their latest version.
https://lxi-tools.github.io - Open source LXI tools
https://tio.github.io - A simple serial device I/O tool
 

Offline Sergeant82d

  • Newbie
  • Posts: 5
  • Country: us
RPI4 - GTK issues (fixed?)
« Reply #29 on: February 11, 2022, 12:00:28 am »
Thank you, Martin - it works!

Now that I'm in it, I do miss the "Live View" option on the screen shots tab. But otherwise, too new for me to comment on.

Thank you again.
Brad

1409392-0" alt="" class="bbc_img" />
 

Offline lundmarTopic starter

  • Frequent Contributor
  • **
  • Posts: 436
  • Country: dk
Re: RPI4 - GTK issues (fixed?)
« Reply #30 on: February 11, 2022, 01:00:12 am »
Thank you, Martin - it works!

That's great - pretty cool to see it running on a cheap single board computer like the RPI. That makes for a really cheap and handy lab setup :)

For arm64/armhf, I've upgraded the snap stable channel to use this working build so you can go back to the stable snap channel like so:
Code: [Select]
$ snap refresh lxi-tools --stable

I'll confirm the result with the GTK4 developers to see if we can fix the issue in the latest GKT4 source.

Once we have fixed it I may have to ask you to test again.

Quote
Now that I'm in it, I do miss the "Live View" option on the screen shots tab. But otherwise, too new for me to comment on.

That may return eventually but for now it is what it is :)
https://lxi-tools.github.io - Open source LXI tools
https://tio.github.io - A simple serial device I/O tool
 

Offline Sergeant82d

  • Newbie
  • Posts: 5
  • Country: us
RPI4 - GTK issues (fixed?)
« Reply #31 on: February 11, 2022, 01:49:57 am »
Thanks - yes, it still works with the stable version.   :-+


### EDITED TO ADD ###

I just installed the new 64-bit Raspberry Pi OS on my 4GB RPI4, and this program worked immediately on it, as well as the older 32-bit version. Just FYI.
« Last Edit: February 11, 2022, 06:20:27 pm by Sergeant82d »
 

Offline lundmarTopic starter

  • Frequent Contributor
  • **
  • Posts: 436
  • Country: dk
Re: RPI4 - GTK issues (fixed?)
« Reply #32 on: February 12, 2022, 07:13:58 pm »
Thanks - yes, it still works with the stable version.   :-+


### EDITED TO ADD ###

I just installed the new 64-bit Raspberry Pi OS on my 4GB RPI4, and this program worked immediately on it, as well as the older 32-bit version. Just FYI.

Good. I've also made a workaround for GTK4 so now the ARM64/ARMHF builds should work with the latest GTK4. These changes have been applied to the stable snap channel.
« Last Edit: February 15, 2022, 08:46:46 pm by lundmar »
https://lxi-tools.github.io - Open source LXI tools
https://tio.github.io - A simple serial device I/O tool
 

Offline Sergeant82d

  • Newbie
  • Posts: 5
  • Country: us
V2.1 Feature Request
« Reply #33 on: February 15, 2022, 11:24:11 pm »
Martin, I would like to ask for a new "Preferences" option, to set default folders to save files (screenshots, scripts, etc.) to. Thanks.
 

Offline lundmarTopic starter

  • Frequent Contributor
  • **
  • Posts: 436
  • Country: dk
Re: V2.1 Feature Request
« Reply #34 on: February 16, 2022, 12:34:58 am »
Martin, I would like to ask for a new "Preferences" option, to set default folders to save files (screenshots, scripts, etc.) to. Thanks.

You mean so that when you press "Save As.." it will always open the folder that you configured via the options?

I'm afraid that is going beyond the behaviour of the standard file chooser dialog. I don't really want to change this standard behaviour.

I understand navigating from your home folder to your save folder of choice can be tedious to repeat. However, there is a way to make that much easier: add a bookmark to your folder. Simply press "Save As.." and navigate to your folder of choice and right click the folder and click "Add to bookmarks". From then on you will have a bookmark to that folder in the left sidebar of the file dialog for easy direct navigation. Give it a try.
« Last Edit: February 16, 2022, 04:58:31 am by lundmar »
https://lxi-tools.github.io - Open source LXI tools
https://tio.github.io - A simple serial device I/O tool
 
The following users thanked this post: Sergeant82d

Online RoGeorge

  • Super Contributor
  • ***
  • Posts: 6203
  • Country: ro
 
The following users thanked this post: lundmar

Offline electrodacus

  • Super Contributor
  • ***
  • Posts: 1862
  • Country: ca
    • electrodacus
Re: Open source lxi-tools v2.0 released
« Reply #36 on: March 14, 2022, 04:27:43 am »
Just found this and wanted to install as I expect a DSA815 and have a lot of tests to do.
Unfortunately I'm on the very old Linux Mint 17.1 and do not want to upgrade this year as there are to many things that I need so upgrading will be time consuming.
Then I checked what Snap Store as it is new to me and I do not like the idea seems almost like a closed source tool (guess I'm getting old :) ).
Need to find some other alternative or just do the scans manually and save the csv to USB stick for now.

Offline lundmarTopic starter

  • Frequent Contributor
  • **
  • Posts: 436
  • Country: dk
Re: Open source lxi-tools v2.0 released
« Reply #37 on: March 14, 2022, 02:11:47 pm »
Just found this and wanted to install as I expect a DSA815 and have a lot of tests to do.
Unfortunately I'm on the very old Linux Mint 17.1 and do not want to upgrade this year as there are to many things that I need so upgrading will be time consuming.
Then I checked what Snap Store as it is new to me and I do not like the idea seems almost like a closed source tool (guess I'm getting old :) ).
Need to find some other alternative or just do the scans manually and save the csv to USB stick for now.

Yes, DSA815 should work. It is on the list of tested instruments.

Regarding availability of lxi-tools. I'm afraid you can't have it both ways. You can't run an old distribution and have new software be available via the distributions package repositories.

The next best thing is to use snap or flatpak which are both open source and allows software maintainers to distribute their latest software in self contained environments, even on older distributions.

Alternatively, you could try find a distribution which ships the latest versions of lxi-tools and install that in a VM with bridged network adapter.

I would just go with snap if it is available on your old Mint version - it is by far the easiest way and it is actually open source (GPL). Nothing to fear there.
https://lxi-tools.github.io - Open source LXI tools
https://tio.github.io - A simple serial device I/O tool
 

Offline electrodacus

  • Super Contributor
  • ***
  • Posts: 1862
  • Country: ca
    • electrodacus
Re: Open source lxi-tools v2.0 released
« Reply #38 on: March 14, 2022, 05:03:05 pm »
Yes, DSA815 should work. It is on the list of tested instruments.

Regarding availability of lxi-tools. I'm afraid you can't have it both ways. You can't run an old distribution and have new software be available via the distributions package repositories.

The next best thing is to use snap or flatpak which are both open source and allows software maintainers to distribute their latest software in self contained environments, even on older distributions.

Alternatively, you could try find a distribution which ships the latest versions of lxi-tools and install that in a VM with bridged network adapter.

I would just go with snap if it is available on your old Mint version - it is by far the easiest way and it is actually open source (GPL). Nothing to fear there.

Thanks for the replay. You make a lot of good points.
I will have been willing to use a old version of lxi-tools if it was available for my distro as I do not need the graphical interface just the most basic command line.
I dislike the proprietary nature of snap (based on the super amount of research I done on the subject).
I was not aware lxi-tools was available as a flatpak (I will make a search after).
VM is also a solution but currently Windows is the only OS I run in a VM once a year to do my taxes.
Mint developers seems to agree with my view on snap and so it is not included in the recent Mint releases.
This is the article that I read yesterday when I made that original comment https://www.zdnet.com/article/linux-mint-dumps-ubuntu-snap/

Offline lundmarTopic starter

  • Frequent Contributor
  • **
  • Posts: 436
  • Country: dk
Re: Open source lxi-tools v2.0 released
« Reply #39 on: March 15, 2022, 08:02:00 pm »
I will have been willing to use a old version of lxi-tools if it was available for my distro as I do not need the graphical interface just the most basic command line.
I dislike the proprietary nature of snap (based on the super amount of research I done on the subject).
I was not aware lxi-tools was available as a flatpak (I will make a search after).
VM is also a solution but currently Windows is the only OS I run in a VM once a year to do my taxes.
Mint developers seems to agree with my view on snap and so it is not included in the recent Mint releases.
This is the article that I read yesterday when I made that original comment https://www.zdnet.com/article/linux-mint-dumps-ubuntu-snap/

There is an experimental flatpak here https://github.com/lxi-tools/lxi-tools.flatpak but you will have to build and maintain it yourself because I have decided not to maintain a flatpak because flatpak is only designed for distributing single binary GUI applications and not command line tools, meaning I can't distribute lxi-tools fully featured via flatpak. Also, distributing stuff via flatpak is very slow because it has to go through reviews etc.

This is in contrast to snap which supports distributing multiple binaries of any type and it allows software maintainers to literally distribute new releases within seconds. Also, having made both a flatpak and a snap for lxi-tools, I find that snap is technically much better designed and easier to use than flatpak.

Sure, Canonical made some unfortunate political decisions regarding back end store support but I think those will be sorted out in the future if they want snap to become a success. Personally I'm more focused on the technical side of things and I find snap the best technical choice.
https://lxi-tools.github.io - Open source LXI tools
https://tio.github.io - A simple serial device I/O tool
 

Offline electrodacus

  • Super Contributor
  • ***
  • Posts: 1862
  • Country: ca
    • electrodacus
Re: Open source lxi-tools v2.0 released
« Reply #40 on: March 15, 2022, 08:43:47 pm »
There is an experimental flatpak here https://github.com/lxi-tools/lxi-tools.flatpak but you will have to build and maintain it yourself because I have decided not to maintain a flatpak because flatpak is only designed for distributing single binary GUI applications and not command line tools, meaning I can't distribute lxi-tools fully featured via flatpak. Also, distributing stuff via flatpak is very slow because it has to go through reviews etc.

This is in contrast to snap which supports distributing multiple binaries of any type and it allows software maintainers to literally distribute new releases within seconds. Also, having made both a flatpak and a snap for lxi-tools, I find that snap is technically much better designed and easier to use than flatpak.

Sure, Canonical made some unfortunate political decisions regarding back end store support but I think those will be sorted out in the future if they want snap to become a success. Personally I'm more focused on the technical side of things and I find snap the best technical choice.

I understand your point. I'm just a particular case with particular preferences not even sure why I made the initial comment.

I looked a bit more in to the new to me standards and there is not much of a difference between flatpak and snap. Maybe Appimage was more like what I guessed flatpak is but not the case and even Appimage is not what I will have liked. I will have liked just a zip file that is decompressed and contained all dependencies and the executable file sort of like Blender was distributed last time I checked.

The problem with the current state of GNU/Linux is that if you want to use your computer for productivity like I do and have multiple software that took time to install and configure and then you need some time later another software that requires a newer version of some library updating that library my break one or more of your older software.  I have no idea what the solution to this is but I will take more time to study this next year when I will likely upgrade the computer that should also last 10 years as this last computer I have based on i7-3370 and I'm not willing to install an OS more than 2x over that period so once every 5 years.  As far as I see there is absolutely no innovation in either software of hardware to worth upgrading more often.

Online nctnico

  • Super Contributor
  • ***
  • Posts: 26907
  • Country: nl
    • NCT Developments
Re: Open source lxi-tools v2.0 released
« Reply #41 on: March 15, 2022, 10:32:44 pm »
The problem with the current state of GNU/Linux is that if you want to use your computer for productivity like I do and have multiple software that took time to install and configure and then you need some time later another software that requires a newer version of some library updating that library my break one or more of your older software.  I have no idea what the solution to this is but I will take more time to study
The solution is quite simple: include all libraries (from libc and onwards) & other binaries your software needs to run. That is how professional software makers distribute their software as well. That way there is very little chance that the software doesn't work due to a system library missing or being the wrong version. There is no other way around it but hard drive space is cheap anyway.
There are small lies, big lies and then there is what is on the screen of your oscilloscope.
 

Offline electrodacus

  • Super Contributor
  • ***
  • Posts: 1862
  • Country: ca
    • electrodacus
Re: Open source lxi-tools v2.0 released
« Reply #42 on: March 15, 2022, 11:29:43 pm »
The solution is quite simple: include all libraries (from libc and onwards) & other binaries your software needs to run. That is how professional software makers distribute their software as well. That way there is very little chance that the software doesn't work due to a system library missing or being the wrong version. There is no other way around it but hard drive space is cheap anyway.

That is how I will prefer to do things. While it works it not an elegant solution due to the size of each application.
On the other hand I see super simple basic software or even drivers that for no reason is a half gigabyte download (that is the case for this basic spectrum analyzer).
I mostly do embedded software and from this perspective things are much simpler just a .bin file containing all that is needed. As for the source code that is distributed with all needed libraries as there also things change and not only that but become incompatible.

Offline lundmarTopic starter

  • Frequent Contributor
  • **
  • Posts: 436
  • Country: dk
Re: Open source lxi-tools v2.0 released
« Reply #43 on: March 16, 2022, 03:09:46 pm »
The problem with the current state of GNU/Linux is that if you want to use your computer for productivity like I do and have multiple software that took time to install and configure and then you need some time later another software that requires a newer version of some library updating that library my break one or more of your older software.  I have no idea what the solution to this is but I will take more time to study this next year when I will likely upgrade the computer that should also last 10 years as this last computer I have based on i7-3370 and I'm not willing to install an OS more than 2x over that period so once every 5 years.  As far as I see there is absolutely no innovation in either software of hardware to worth upgrading more often.

Do what I do. Always keep your work station up to date with latest version of your preferred Linux distribution to benefit from latest features and security updates(!). I develop embedded micro-controller firmware and complete embedded Linux stacks for various clients and when I need something to be available for many years I simply setup my work space (toolchain, tools, source repos, etc.) in separate VMs so I can always spin them up if I need to go back and make updates. This way I can make sure that my development environments for various clients are always preserved while enjoying a fully up to date Linux work station.

To me it is absolutely inconceivable to run a 5 or 10 year old Linux system as my daily driver work station. We have very different views of what warrants an upgrade. I would argue that security and bug fix updates alone justify keeping everything up to date but more importantly there are sooooooo many components of the Linux ecosystem that are constantly evolving making your Linux experience so much better. I mean, it's 2022 and this is the time for running technologies like Gnome/Wayland, the new pipewire audio framework, systemd, vulkan, and the other zillion application/library updates etc. If you stick with an old Linux distribution you are asking for trouble and get a lesser Linux experience and you are in essence opting out of using a lot of new software. To me, that is a terrible strategy.
« Last Edit: March 16, 2022, 04:39:27 pm by lundmar »
https://lxi-tools.github.io - Open source LXI tools
https://tio.github.io - A simple serial device I/O tool
 

Offline electrodacus

  • Super Contributor
  • ***
  • Posts: 1862
  • Country: ca
    • electrodacus
Re: Open source lxi-tools v2.0 released
« Reply #44 on: March 16, 2022, 05:48:38 pm »

Do what I do. Always keep your work station up to date with latest version of your preferred Linux distribution to benefit from latest features and security updates(!). I develop embedded micro-controller firmware and complete embedded Linux stacks for various clients and when I need something to be available for many years I simply setup my work space (toolchain, tools, source repos, etc.) in separate VMs so I can always spin them up if I need to go back and make updates. This way I can make sure that my development environments for various clients are always preserved while enjoying a fully up to date Linux work station.

To me it is absolutely inconceivable to run a 5 or 10 year old Linux system as my daily driver work station. We have very different views of what warrants an upgrade. I would argue that security and bug fix updates alone justify keeping everything up to date but more importantly there are sooooooo many components of the Linux ecosystem that are constantly evolving making your Linux experience so much better. I mean, it's 2022 and this is the time for running technologies like Gnome/Wayland, the new pipewire audio framework, systemd, vulkan, and the other zillion application/library updates etc. If you stick with an old Linux distribution you are asking for trouble and get a lesser Linux experience and you are in essence opting out of using a lot of new software. To me, that is a terrible strategy.

The equivalent of your separate VM for long therm projects is my computer as I'm my own client and I only have one long therm project (multiple devices but in the same series).
Access to different computer hardware is more difficult or in some cases impossible from a VM.
I'm off grid in the middle of nowhere with a fairly low speed internet connection 2Mbps both up and down so always updating the OS is not a great option plus I consider security to be higher with the auto updates disabled.
There are no bugs in anything that I use (there may be but not affecting me). I see nothing that can make my experience better with newer software.
I do get your perspective as that is how I will work 10 to 20 years ago (always having the latest Linux distribution and testing multiple new distribution each year and also change the hardware fairly frequent).
Even my phone is on Android 4.4 and now on third battery (replaceable battery model) and have no intention to replace it unless it fails (recently I got another similar model with replaceable battery and Android 9 in case this one fails as it is my main and only internet connection).
Phone is used as a phone and access point only thus newer version will have no advantages as I do not need any other futures.
My wife has a newer Chromebook tablet with support until 2028 and the inability to control when update happens or if you even want to do that seems to me a much higher security risk (you have no control over your own device is like you do not even own it).
And software will do nothing to protect you if hardware is compromised as it is the case with all recent x86 and most ARM. Maybe my next computer will be an IBM Power 10 based assuming I can find something next year.


A good recent example in therms of security is the Airthings Wave that I purchased about a year ago and now it is a paper weight.
It measures radon gas, CO2, temperature, humidity, pressure.
In order to use it it requires you to register the device first update the firmware and then you can connect trough the app over bluetooth.
The app requires GPS to be enabled so exact location is known and it will upload data to cloud. I was going to immediately send it back but I noticed that I can use it on that (backup phone I have if I turn OFF WiFi so any outside connection).  It worked I think for about 6 months this way and then it stopped allowing me access to device and required a internet connection in order to continue to have access.
There is no way to clear the internal logged data (logged in the device not just the phone) and so as soon as I will connect this to internet it will make an update and upload all logged data to Airthings cloud. Since I'm not willing to share the data I can no longer use the device at all.
Even selling to someone else is not an option as the device was already registered that includes my details and exact GPS location and so if someone else will register (assuming it is even allowed) the 6 months of logged data will still be in the cloud.
You may think that is not an issue to share this data but I obviously disagree. Just the CO2 levels alone can reveal a huge amount about the way you live so how long you are at home how many people in the home when you are opening the windows, when you sleep (just to name a few) and in combination with all other sensors it can provide an almost unrestricted access to your life.

Sorry for the super long rambling. I was triggered by the "security updates"

Offline lundmarTopic starter

  • Frequent Contributor
  • **
  • Posts: 436
  • Country: dk
Re: Open source lxi-tools v2.0 released
« Reply #45 on: March 16, 2022, 10:20:50 pm »
Sorry for the super long rambling. I was triggered by the "security updates"

Ha ha, yes - that was quite a ramble triggered by you confusing "security updates" with "automatic updates".

I'm no distro shopper - that is something you do when you are learning Linux. I've been running Ubuntu Linux exclusively since 2004 and my installations have never installed system security updates automatically - that is an opt in feature.

Either way, you have to be careful with any connected product you buy in this IoT era to protect your privacy and that is exactly why it is even more important to keep up with security updates. It would be foolish to insist on running old software with known vulnerabilities that makes you the easy target of a long list of CVEs.
https://lxi-tools.github.io - Open source LXI tools
https://tio.github.io - A simple serial device I/O tool
 

Offline electrodacus

  • Super Contributor
  • ***
  • Posts: 1862
  • Country: ca
    • electrodacus
Re: Open source lxi-tools v2.0 released
« Reply #46 on: March 16, 2022, 11:12:28 pm »
Ha ha, yes - that was quite a ramble triggered by you confusing "security updates" with "automatic updates".

I'm no distro shopper - that is something you do when you are learning Linux. I've been running Ubuntu Linux exclusively since 2004 and my installations have never installed system security updates automatically - that is an opt in feature.

Either way, you have to be careful with any connected product you buy in this IoT era to protect your privacy and that is exactly why it is even more important to keep up with security updates. It would be foolish to insist on running old software with known vulnerabilities that makes you the easy target of a long list of CVEs.

:) I do not think I confused security updates and automatic updates.  The main reason automatic updates are a thing is supposedly for security when that may actually be the opposite.

I also started playing with Linux around the same time frame early 2000's first attempting to install RedHat (was not a fan) but then I found a way more user friendly Knoppix Live CD version that I installed and gave up using Windows at home then I got a Ubuntu Live CD (was testing many other versions) and was supper impressed with the out of the box hardware support.

The problem is bad quality software to begin with and just patching vulnerabilities when the become public will not solve much if anything.
I for example disable Hyper Threading ever since the vulnerability related to that where announced but there are so many more than can not be fixed by any software patch.
There will be no choice very soon in what you buy as everything will be internet connected and as my Airthing device can not be used without.
So while you still have control now on auto-updates in Linux it will not be long until they will be mandatory. Maybe at first just security related updates then all the others.

Offline Kibabalu

  • Regular Contributor
  • *
  • Posts: 106
  • Country: de
Re: Open source lxi-tools v2.0 released
« Reply #47 on: August 21, 2022, 04:14:22 pm »
...

I will release a binary soon.

Any news regarding the binary for macOS?
 

Offline lundmarTopic starter

  • Frequent Contributor
  • **
  • Posts: 436
  • Country: dk
Re: Open source lxi-tools v2.0 released
« Reply #48 on: September 26, 2022, 11:35:08 am »
...

I will release a binary soon.

Any news regarding the binary for macOS?

I hope that someone eventually will maintain a package for brew so it becomes easy to install on mac. Also, to get it working on mac someone needs to adapt the mDNS backend for mac (Bonjour etc.).
« Last Edit: September 26, 2022, 11:42:31 am by lundmar »
https://lxi-tools.github.io - Open source LXI tools
https://tio.github.io - A simple serial device I/O tool
 

Offline lundmarTopic starter

  • Frequent Contributor
  • **
  • Posts: 436
  • Country: dk
Re: Open source lxi-tools v2.0 released
« Reply #49 on: October 14, 2022, 08:51:43 pm »
FYI - I've just released lxi-tools v2.2 which includes various updates, bug fixes, and a new popular requested feature which allows for adding instruments manually in case they are not discoverable.

Full release details are available here: https://github.com/lxi-tools/lxi-tools/releases/tag/v2.2

As usual, snap version is available immediately, distributions will take some time to update.

Happy hacking!

/Martin
https://lxi-tools.github.io - Open source LXI tools
https://tio.github.io - A simple serial device I/O tool
 
The following users thanked this post: coromonadalix, RoGeorge, dibro


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf