@Bob - Thanks for starting this thread! Your stadium scan look great - I can almost tell what kind of SUV you drive . Your scanner appears to be very well calibrated, though I do see that it is slightly seeing itself in the 135-225 sweep angle range. It may be that you are using our older 90 degree bracket design, which had a 100 degree motor cover cone angle, instead of the current 90 degree cone angle.
@ptegler - Nice scans! I especially like the 4 backyard scans combined.
I went ahead and made a screenshot of your combined scan for others to see:
I can see that your sensor still has a little "corkscrew" error, which is caused by the 90 degree bracket being slightly off a clean 90 degrees. This can be fixed by either trying to get your scanner bracket to be more vertical (the three bearings mounted in our latest scanner cover design help with this), or you can adjust the angle parameter in the code.
Here is some input on this from David, our lead software engineer:
The scanner python code contains a parameter for adjusting the mount angle.
This can be specified when creating a ScanSettings object. See README
Additionally, if you want to experiment from the command line you can call the scanner.py script directly with a command line flag. See here
If you want to change the default value used by scanner.py script, you could change the default value here
If you want to change the default value used to instantiate a ScanSettings object, you can change that here.
If you want to leave the scanner code alone, you could also add the mount angle command line parameter to the child_process spawn from the node scan route here
Finally, you could add an input to the front-end form, similar to motor speed or sample rate and use this to adjust the value from the webapp.