StevieDvd

You could consider adding a stepper motor hat ( for example the waveshare aound £20) which would drive a focuser without the need for another power connection and usb port - plus it can run the Pi from a 12v feed too. Though that depends on what focus motor you are planning to add. The case for your Pi looks very project friendly, was it purchased or diy/3d printed?

'Bear in mind' the deed has now been done. Hope it has all gone as you hoped and views well.

Ends 31st June!!! Whoops.

If you have an HEQ5 then probably your tripod is the SW 1.75" stainless steel one already. If you wanted to get a sturdier 2" stainless steel one then either a used CG5 which is a 2" leg version but fits HEQ5/EQ5 - can be hard to find, or the EQ6 one but that needs a £50 adapter. Are you using the legs fully extended? Perhaps consider keeping them short and buy an eq5 extension pillar to fit on your existing tripod.

If you have PA and RA sorted then DEC has to be OK, the axis is 90% to RA and is not adjustable.

Consider the opposite way where your mount was fixed and had no adjustment bolts. If your pier/tripod started perfectly horizontal you would need to adjust it to centre the mount axis with the NCP. It does not matter too much if you adjust the pier or the mount as long as the axis ends up correctly aligned, it's just a little easier (and cheaper) to use the mounts adjusters.

That last snug turn would mis-align the polarscope though Never use the polarscope now, the Handset polar alignment was good enough for an accurate setting until I used a permanent pier setup and the Polar Align software from Themos (a forum member) provided an even better one.

I'm using PC windows and a local astrometry without astrotortilla and found what was needed. If the api field is empty it does not save all settings (I guess that's a check for the new user to make initial settings) just put a number in the api key box. Second the config file is for the location of the astrometry config (mine is /etc/astrometry/backend.cfg) Just need to get the solve settings and local copies of the solve files all tidied up for the cameras I plan to use. Will be using the local solve for SGP too. Hope that helps.

I had a slightly larger error, but small enough I thought, so I tightened everything up to keep the settings and took one last image - but it would not solve. In the morning I uploaded the image manually and it would still not solve until I processed it to make it clearer, must have been some thin cloud that I'd not noticed as the image timings were constant and all earlier attempts were solved fine. So quite pleased the final settings, after tightening everything, ended up the best. BTW. A couple of points I thought worth mentioning: If a poor image is uploaded and the server takes too long while attempting to resolve should PPA handle that?Instead of having an extra button for Nova & Local for each image would it be tidier to have a select radio button to set either Local or Nova and have just one Solve for each?Not sure if using AstroArt5 as a solver will work, although it does have SDK for scripting I'm still having issues using it directly so would not hold out any hope of linking to it. A local nova on the other hand sounds a good idea.

Managed to spend a bit of time getting the alignment as good as I could before the hour got too late or the clouds started to interfere. I hope this is accurate enough to use when I get my guiding setup finished. Once you get the feel for the amount and direction of changes to make on the mount alt/azz bolts it becomes quite easy. I was using a DMK21 with focal reducer and live view so I could almost work out the rough position the stars needed to move to beofre taking and uploading an image. Would have been a lot easier if my computer was nearer the scope, the latop was hooked up in the garage so was popping in/out each time to check improvements. Thanks Themos that's a real nice utility for alignment Steve

Thanks, I worked around the missing directory once I saw the cause. BTW, I also meant to mention that when using a mono camera the overlays are also being saved in mono. As a quick test I added .convert("RGB") to the image open (s) and got the overlays in colour. If that's a safe thing to do without checking the incoming file colours.

Hi Themos, Sorry for not getting back quicker on the v1.03 error O enocuntered. I started ppa.py in Anaconda console as suggested and got this: The system cannot find the path specified. C:\Users\Steve\Anaconda>cd C:\Users\Steve\Documents\PhotoPolarAlign C:\Users\Steve\Documents\PhotoPolarAlign>ppa.py Traceback (most recent call last): File "C:\Users\Steve\Documents\PhotoPolarAlign\PPA.py", line 1501, in <module> APP = PhotoPolarAlign(master=ROOT) File "C:\Users\Steve\Documents\PhotoPolarAlign\PPA.py", line 1495, in __init__ self.Sniff_AstroTortilla() File "C:\Users\Steve\Documents\PhotoPolarAlign\PPA.py", line 1305, in Sniff_AstroTortilla lfn = os.listdir(dir) WindowsError: [Error 3] The system cannot find the path specified: 'C:\\Users\\Steve\\AppData\\Local\\astrotortilla.sf.net\\AstroTortilla/*.*' Not having dabbled in Python before I can't see if there is a new config setting I'm missing to enable/disable local solving. I'm using Win 7 pro as OS and don't have Astrotortilla installed - but do have Astroart5 Hope that's a genuine bug I found for you and not me doing something stupid!

As it looked as if I was going to get some clear sky for a few hours I was ready to use this in real-life mode. Seeing that you had done a couple of updates I downloaded v1.03. When I ran it a command window flashed/disappeared too quickly for me to get the message - though I think it may have been looking for astrotortilla. I then tried v1.02 as well and put my api key in as expected and it would not connect to astrometry.net. So I went back tot the original which did not connect either. It was all my fault as I had the api key stored in an email I sent from work to my home email which capitalised the first character, doh. After fixing that v1.02 worked but still no luck with v1.03. Does v1.03 need a config setting to be made for local solving? In the end I did get it setup and was getting the error down until the next capture I did had no visible stars - the clouds had come across and stopped me from finishing - but good practise and all seemed to be working as advertised so hope to get it finished on next cloud free night.

Hi Themos, Have installed python and PPA and like Earl had the same issue with saving the api key. Though thanks to Earl breaking the ground first I moved it from the defaulted directory (C:\Program Files (x86)) to my user directory and it was then accepted OK. Loaded and solved the example images (h.jpg first then v.jpg) and finally the i.jpg and did the Find Polar Axis and then the Show Improvement. All worked as per your instructions. I presume we would only iterate through the improvement (i.jpg) image(s) as we adjust and get better aligned. Also, noted that the test images are shown as solved (in green) when re-doing the test after closing and restarting due to the saved wcs files. Would suggest a button for reset which deletes the wcs files in case people use the same names for each image - would make an interesting adjustment if they used the wrong ones I'd expect. My next task is deciding which camera to use if we get a clear night. So good work thus far. PS Earl your api key is visible if that is a concern PPS As a new purchaser of Astroart5 I too would be interested in using it for solving as well.

if you can send some clear skies I'd like to have a go as I need to polar align my mount to the garden pier again. I'll be the idiot user - if I understand it then most will.