FreeLSS:Error saving settings (and wrong pin defaults?)

Exactly! I just noticed they get saved "in session", even with the error, but get lost after a reboot. FreeLSS must be run as root in any case, even if that doesn't seem to allow the settings file to be written to, for some reason.

Alas, I have everything soldered from start on a raspberry prototyping board Very short lived as a decision, but I didn't have a proper perfboard anyway since it hasn't arrived yet, and I was in a hurry to get it up and working.

I did change the pins correctly now, as per official GPIO reference vs wiringpi vs freelss schematics, and now I get some kind of response from the lasers, even though they are erratic (sometimes one laser responds to the toggle function, the other does not, when I retoggle the first one the second turns off/on as well for no apparent reason... no idea what is happening), but still no response at all from the motor, which is buzzing the whole time.

Maybe downgrading FreeLSS to the version that was used by Bill Owens would get me a working device?

Ok, as a very final strand of willpower, being it the last day of the year and just a few hours away from 2016, I rewired everything from the female pin connectors on the raspi protoboard to make it fit the "hardcoded" values in FreeLSS, and I do get a responsive scanner in that everything works, lasers are correctly activated and turntable is correctly rotated.
Overall, tho, it's still unuseable, since even "in session" I cannot save the settings (running as root), because they may show as having been saved (reloading the settings screens, they "stick") but the scanner still doesn't act on them.
For example, before I rewired according to hardcoded values, the correct pin settings were indeed saved into the user interface, but the signals were still being sent to the hardcoded pins (right laser toggled instead of left, motor disabling turning on left laser).
Now, since I have a 0.9° step motor, I tried setting 6400 steps per revolution instead of the default 3200, and like before, these values are saved into the user interface even if the "ERROR" message shows after I press save (I get the error message, but then I reload the settings screen and the values I put there are still at their place), but by instructing the software to do a 360° degree rotation of the turntable in the camera pane, I only get a 180° rotation, which means the software is still acting on the hardcoded value of 3200 steps per revolution, no matter what's showing in the settings dialogue.

So, like this, with settings not being saved, I cannot use the scanner, or I need to manually change the settings file (where is it located?)

Also, as someone else reported in another thread, the preview during the scan doesn't show

HAPPY NEW YEAR PEOPLE! MAY 2016 BE FULL OF FAST, HIGH DETAIL SCANS!

FreeLSS must be ran as root.  This occurs automatically when executing the daemon but when executing via command line you must use sudo.

sudo ./freelss

FreeLSS will create a properties file at the users home directory which will be /.freelss.properties when running as a daemon but running from the command line will create it at /root/.freelss.properties.  This issue has been resolved in later versions of the ATLAS 3D software by defaulting to /var/lib/freelss instead of the users home directory.

I will look into the Error Saving Properties error that you are seeing.  Are you running the latest version of the code available on Github?  Does the software stop running when you receive this error, or can you hit the back button and continue to operate?

- Uriah

Interesting find C_D, after I ran "make startup" I never went back to starting it manually so I really didn't have the opportunity to confront running it manually with sudo and having it autostart at boot.
I may just as well remove the autostartup and see.

Thank you Uriah, here it's the same as C_D, got freelss fresh off github on 31st dec, and I can continue using the software no matter how many times the error shows up.

EDIT: I can confirm: after removing freelss from startup and starting it manually, it still had the "correct" pin settings I had saved from the very first run (reading the file it could save back then), so this time I had to save the "old and wrong" pin settings since I didn't want to reset the connections on the protoboard.
I can now save both the general settings and the setup details, and maybe I can re-enable the startup by adding myself a "run as" command with sudo. Who knows?

In the meantime I'll be having "fun" calibrating everything.

EDIT 2: IT LIVES!!!! I didn't calibrate s**t and didn't even input measurements of the camera and laser position but I launched a low resolution test scan of a vase, and it produces shapes! Also the preview works!
I mean, not that I was expecting anything less, but having built everything myself now I feel enthusiast by witnessing the result

I am testing a 5MP scan right now, and it indeed works, even if several times slower... not yet totally calibrated, but I'll get there, in the end I'll feed it a plaster dental model which is the original intended use.

I second that, I never got automated start working properly either.