ProjectArcDev's profile picture. Accessible Astronomy • Low Cost Small-Board Driven • 3D Printing • Calibration Automation • Fast/Lightweight C/C++ Framework • Web-Based UI

Project Arc

@ProjectArcDev

Accessible Astronomy • Low Cost Small-Board Driven • 3D Printing • Calibration Automation • Fast/Lightweight C/C++ Framework • Web-Based UI

After moving the project to a new OS, I've decided to move to Apache Netbeans v9 and upgrade OpenCV to v3. Some tying up of loose ends required to progress further.


Managed to get some images from the v2 Pi camera. Hoping to run them through recognition and work out optimal parameters for configs.

ProjectArcDev's tweet image. Managed to get some images from the v2 Pi camera. Hoping to run them through recognition and work out optimal parameters for configs.
ProjectArcDev's tweet image. Managed to get some images from the v2 Pi camera. Hoping to run them through recognition and work out optimal parameters for configs.
ProjectArcDev's tweet image. Managed to get some images from the v2 Pi camera. Hoping to run them through recognition and work out optimal parameters for configs.

Worked on some small optimisations to speed up recognition. Swapped over the test camera from 1.3 to 2.1. Now need to wait for clear skies so I can collect test images for the new rev camera and see what changes in settings are required.


Command line for position recognition now supports both existing images and images retrieved from the built-in Pi camera. Now working on the optimisations for initial selection of points.


Command line support added successfully with some small tweaks needed at some point. Auto Pi camera support next so an image can be caught, processed and results output same as existing ones.


Been working on adding command line argument support to the positioning part of the project. Also plan to upgrade Pi camera on the test rig from v1.3 to v2.1 at some point soon.


Of the 17 images processed, the project managed to resolve 14 with the current algorithms/approach. I'm really happy with that, especially considering it has to contend with trees, buildings and fencing and unoptimised code. Images: original & processed.

ProjectArcDev's tweet image. Of the 17 images processed, the project managed to resolve 14 with the current algorithms/approach. I'm really happy with that, especially considering it has to contend with trees, buildings and fencing and unoptimised code.
Images: original & processed.
ProjectArcDev's tweet image. Of the 17 images processed, the project managed to resolve 14 with the current algorithms/approach. I'm really happy with that, especially considering it has to contend with trees, buildings and fencing and unoptimised code.
Images: original & processed.

Decided to quickly run a test image taken a few days ago to see how the code stood up. Analysis took 5 minutes which is too long but changes are due soon. Seemed to work extremely well other than that. Now Includes pre-warped origin points as well.

ProjectArcDev's tweet image. Decided to quickly run a test image taken a few days ago to see how the code stood up. Analysis took 5 minutes which is too long but changes are due soon. Seemed to work extremely well other than that.
Now Includes pre-warped origin points as well.
ProjectArcDev's tweet image. Decided to quickly run a test image taken a few days ago to see how the code stood up. Analysis took 5 minutes which is too long but changes are due soon. Seemed to work extremely well other than that.
Now Includes pre-warped origin points as well.

Worm and wheel (PETG) from the 3D print shop. Wheel printed better, but again, stringy and blobby in places. The wheel might work, but the worm is definitely not good enough for the project.

ProjectArcDev's tweet image. Worm and wheel (PETG) from the 3D print shop. Wheel printed better, but again, stringy and blobby in places. The wheel might work, but the worm is definitely not good enough for the project.

My last attempt (Colorfabb XT) next to 3D print shop (Standard PETG) materials. Quite surprising that my last print was better quality. The PETG seems to be stringy and blobby. This was definitely worth the effort to see quality results.

ProjectArcDev's tweet image. My last attempt (Colorfabb XT) next to 3D print shop (Standard PETG) materials. Quite surprising that my last print was better quality. The PETG seems to be stringy and blobby. This was definitely worth the effort to see quality results.

In the spirit of maintaining progress despite the somewhat major setback, I've ordered some prints from a 3D print shop. Due mid-week. At the very least, the printer step motors can be repurposed for telescope mount motor drivers.


Seems the damage sustained by the printer when first used and the recent attempts to calibrate z-axis properly with the built in proximity sensor have resulted in continual bad prints. I'll be looking to get a new 3D printer.


After 12 months and some technical difficulties, finally managed to get around to some test prints. This, a worm of a worm/wheel set.

ProjectArcDev's tweet image. After 12 months and some technical difficulties, finally managed to get around to some test prints. This, a worm of a worm/wheel set.

Put together a quick Raspberry Pi test rig for quick and easy deployment when skies are clear.

ProjectArcDev's tweet image. Put together a quick Raspberry Pi test rig for quick and easy deployment when skies are clear.

Optimisation being considered: Grab as many blob keypoints as possible, but weight them based on size (which is basically intensity), using the brightest first, faintest last. Possibly also weighting more near the centre and less further out.


Threw a test Pi out the door to see how it might fair. Took 2 images, one failed to solve, the other surprisingly did after battling the Moon and ground objects (although took about 17mins which is too long). Some optimisations definitely needed.

ProjectArcDev's tweet image. Threw a test Pi out the door to see how it might fair. Took 2 images, one failed to solve, the other surprisingly did after battling the Moon and ground objects (although took about 17mins which is too long). Some optimisations definitely needed.

Calculation of image centre coordinates, effectively Zenith. Almost perfect. The discrepancy? That's down to the #RaspberryPi camera back in 2016 not being 100% level while pointing up, an issue that mount hardware would have catered for. Very pleased with this.

ProjectArcDev's tweet image. Calculation of image centre coordinates, effectively Zenith. Almost perfect. The discrepancy? That's down to the #RaspberryPi camera back in 2016 not being 100% level while pointing up, an issue that mount hardware would have catered for.
Very pleased with this.

Screenshot showing sky image with resolved star (HIP 65378) and test output to calculate decimal Alt/Az (to match result in Stellarium). This is great because Azimuth is also bearing and can be used to help calibrate future hardware axis.

ProjectArcDev's tweet image. Screenshot showing sky image with resolved star (HIP 65378) and test output to calculate decimal Alt/Az (to match result in Stellarium).
This is great because Azimuth is also bearing and can be used to help calibrate future hardware axis.

Some late night success with a tough conversion from C# to C++ for the RA/Dec to Alt/Az values. Hoping the prep work on the new ArcView concept will have been worth it when using it for telescope navigation and motor drive control.


Loading...

Something went wrong.


Something went wrong.