New version of FreeLSS committed to Github (Page 2 of 5)

Thanks Pirvan.  I'm looking forward to your tutorial.

I am about to purchase an Atlas scanner kit (after the holiday postal chaos dies down). This will replace a Rubicon scanner which turned out to be an expensive paperweight which is unlikely ever to produce usable scans. However, I see that certain facilities on the Atlas are available only to the crowd funding backers. Are these facilities now available to all who buy via the Murobo shop or will there be a date when they will become available to all purchasers? Thanks to this forum, I am happy to invest in a scanner which delivers its promises so, like Julius Caesar, I will use my Atlas to cross the Rubicon . . .

I too am planning to get one soon.

Hi Hairu,

I would like to know if you plan to sell the right to upload your last versions of Freelss ?
In my case, I've developped my own design both on the scanner body and electronic interface. I'm ready to buy a serial number and the right to upgrade it regularly.

Thank you for thinking about this feature if you don't mind.

Great ! It looks like I may finally found my christmas present...

If I delete the software from my pi, then follow the steps on github to redownload, will I get the most updated version of the software?

Hi Uriah,

I've been autoupdating for a while now with no problems and have been running 1.14. I just went to update to 1.15 and the software indicated success and restarted. However, FreeLSS did not start up as it usually does. I ran it manually from the home/pi/freelss/src directory and it runs version 1.9! The update process does the same thing. I remember this being a problem with the earlier version and I ran the command that fixed it before but it said that libiw-dev libel-dev were already the newest version.

That said, I can't say for sure that I was running 1.14 before trying the update. I know I was running it before based on some of my posts in this thread but I haven't used it for a while. However, I haven't changed anything on the SD card since last running FreeLSS so I can't imagine how the version reverted to 1.9.

I'm basing the version on the field in the setup page so I assume that is correct. To manually run it, I still cd to home/pi/freelss/src and type sudo ./freelss, correct?

Any suggestions on where I should go from here? It's probably something simple I'm missing or forgot to do, but I'm stuck!

Thanks.

--Dave

Edit: I reposted this question as a new topic with some further information.

FreeLSS 1.17 is available via the ATLAS 3D auto-update system.  This releases adds a new software point cloud renderer, initial support for the new 8MP camera, and the ability to override the camera focal length.

Point Cloud Renderer
There is now a software point cloud renderer that is able to display the scan data at predetermined locations without the need for WebGL or a powerful machine.  This also allows the scans to be previewed directly on the Pi, which enables ATLAS 3D to be a full featured stand-alone scanning system when running with a monitor, keyboard, and mouse directly attached.

Support for the 8MP IMX219 Camera
The 5MP camera has been EOL'd by the Raspberry Pi foundation so initial support has been extended to the new 8MP variant.  However, only "stills" mode is currently supported.  The 5MP camera is still the preferred camera for now.  Unfortunately, using the 8MP camera isn't as simple as just updating the ATLAS 3D software because it relies on newer versions of the Raspbian OS.  The only way to use the 8MP camera is to download the latest version of Raspbian, install FreeLSS Open Source, and then update to FreeLSS Commercial.

Support for overriding the focal length
The camera's focal length can now be overridden.  This allows those interested in trying out new lenses to specify the appropriate focal length for them.

- Uriah

I ran auto-update from 1.16 to 1.17 and the software reported success. However, when it rebooted, freelss did not start up. I am able to run the old version manually in ~/pi/freelss/src but, when I try to run the licensed version in /usr/local/bin, I get an error while loading shared libraries: libjpeg.so.62 (no such file or directory). Any suggestions?

I often have problems like this and, while I can follow instructions, I usually don't have the technical skills to solve them myself. I end up searching through the forums for solutions or just ask here. Is there a central place for installation and upgrade instructions for the licensed version, including installing any necessary Raspian or other updates?

Thanks.

--Dave

ps Based on a solution I just found, I tried the command "sudo apt-get install libjpeg" but got an error "Unable to locate package libjpeg"

Now I get the error:

/usr/lib/arm-linux-gnueabihf/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by ./freelss)

IIRC, I am running an installed version that I upgraded with my serial number and have kept up to date. It was working fine on 1.16 prior to running the auto-update to 1.17 today.

Excellent! Thanks, Uriah.