gregk01

It's the slightly more work that's putting me off mono as well. Not that I'd normally be averse to it but I'm camping, with the family, in very remote locations so I suspect me being focussed on my imaging in the evening may be frowned upon! I see OSC as being less inclined to have issues and therefore more a set, load a target or 2 in NINA and press go.

I've found myself "trapped" in Western Australia. I live in the UK but was out here visiting family and it's turned into an extended stay. I haven't had much opportunity to image since being here but I'll be heading up to the north west of the state near a town called Exmouth. Unfortunately it's not the best time to image in the Southern Hemisphere but I'll find a couple targets I'm sure.

I'm going to be travelling to a bottle 1 area for a week but will be limited in how much kit I can take. I've settled on my Tak FSQ85 scope, CEM40 mount and am now trying to decide on the camera. I'll be camping with no internet and power being supplied from batteries (charged with solar during the day). I'm struggling with what camera to take. My ASI2600MC pro OSC or my ASI1600 mono (with Astrodon LRGB & NB filters). Given the remoteness of the location, I'm thinking keeping it simple makes sense so the OSC would be the way to go. Given the dark sky would I get a huge benefit from using mono? Or better question would be enough of a benefit to justify the added complexity? Appreciate any views. Greg

So, it appears the problem was a communication issue but related to having to run PHD2 as administrator. It seems that all apps communicating with Stargo need to be installed as admin and then run as admin otherwise they don't communicate. So now I have them talking to each other, tonight I'll play around with the guide settings. Wasn't very smooth last night so assume I can fix this by playing around with the max movements and aggresiveness.

Thanks Ken, the cable is connected, will check the port. Will feel pretty silly is that's the problem.

Thanks all for the advice. Ken, it does seem weird the the mount isn't reporting anything. I have loaded the config file and also went through the Stargo alignment process. I think as a starter I'll uninstall and reinstall the Stargo software and set the mount up again from scratch, see if that helps. Try again tonight!

Logs from the last 2 nights trying various different settings, all resulting in the message ""RA Callibration failed: star did not move enough"" PHD2_GuideLog_2020-08-10_202404.txt PHD2_GuideLog_2020-08-11_200659.txt

The ASCOM driver for the mount

Hi I've been trying for weeks now to get PHD2 guiding working with my new Avalon M-Zero mount. I also have a CEM-25P and have no issues at all with PHD2 on that. I have followed the suggested settings for the M-Zero (as per attached) and then changed those settings following examples of others, but no matter what I do I get the message "RA Callibration failed: star did not move enough". I live in the UK but have 2 weeks of clear and dark skies in Crete and I've already wasted the last 3 nights trying and failing to get the guiding working. Any thoughts or advice would be greatly appreciated. I've attached a couple of screen shots of my settings. Thanks