scotty38

You should try dimming it by, maybe, adding sheets of A4 paper. That's what I do anyway.

Can you link to this please? I ask because the only one I recall was an issue with a set of "older" flat darks that had pixel values higher than the darks. When they took new flat darks the signal levels matched and the calibrated output was fine. Point being it was not a config issue as such.

Ok that's what I was asking, how are you doing it at acquisition?

so you're binning after stacking and not at acquisition time?

I see what you mean, does look a bit odd. How are you binning at acquisition time?

Here you go this is what I used on my 294m: https://www.modernastronomy.com/shop/accessories/adapters/qhy-small-screw-adapter-020063/

There are some QHY adapters that allow removing the default adapter on the camera so these "smaller" cameras can bolt to a 36mm based QHY filter wheel. Maybe that same adapter will allow the bolting to the ZWO wheel. I'll dig out a link and you can decide if it'll work for you.

Maybe not, most likely external DNS server such as 8.8.8.8 for example and local resolution done via netbios names blah blah

You can get tools to force it to connect to a specific AP, again something I had to do too as I fell foul of this one :-). Since I built my Obs and had additional bits that needed connecting ie dome and Cloudwatcher, the cabling meant it made more sense to have my pc off board and run just one USB to the mount etc so my PC is now Ethernet connected anyway.

Pretty sure he means without the reducer on th3 C9.25 so you'll need to bin that bit more.

You probably don't even need to update any dhcp scope etc, just setup a static address in the PC, just put it towards the top of the range and it'll be fine. As it happens I have a managed router from my ISP so I can't change anything myself but I have assigned lots of statics to devices and never had any issues with DHCP assigning one of them to another device. My Mele is setup like this and has been since I've had it, no issues.

Doesn't always work like that if there is no association already established.

I must admit I thought you had an issue connecting to the scope not opening a script file 🙂 🙂

Is the com port etc set up correctly?

I have a GT81 and a dew heater and haven't knowingly seen this issue. Maybe I have it but the heater hides it 🙂 Worth a try for sure.....

Ok if you have a good PA then a platesolve on the desired target should get you there properly, If that's not working you may need someone with an ASIAir to help (I've never used one) but having said that I would double check your coordinates etc in the app to see if they are correct, regardless of how you got them in there.

Just to say there's nothing inherently wrong with doing a PA through the main scope, I do it all the time with the TPPA routine in NINA.

Polar aligning aligns the mount, not the scope. If you have polar aligned correctly you'll most likely need to star align/plate solve etc to get the actual scope synced and pointing where you need it to. If you just slewed back to home after PA I am not surprised you cannot see Polaris as the scope could actually still be pointing "anywhere".

I agree with this and have/had both colour and mono versions and to me at least no issues at all once you "understand" them 🙂 However, if money is not an issue etc etc I would go for a 2600/268 in mono or colour as required, no question. I'd probably only consider the 533 if I was using a particularly long scope for particularly small targets where it might not matter that you had the smaller sensor anyway.

That's good news you sorted it, nice one!

I upgraded my Quieter 2 to Win11 and connect from Win10 machines via RDP and have had no issues whatsoever. I can also connect from a Linux machine with no bother either. Having said that I can also get on via an iPad and iPhone if I'm feeling particularly masochistic 🙂

Ah yes, recall the "fork" issue you were seeing. I think the on scope PC will be a good move, however I can't help thinking that's not your real issue but I'm lost as to what else it can be at the minute.

I think Stuart has a Pegasus UPB so together with something like a Mele he should be well sorted!

Was yours one of the powered types? Do you still have the USB and power going through the mount? I know you said other apps work but what happens if you bypass that just for the sake of testing?

I can't fathom why you seem to be plagued with this issue. I realise I now have different cameras, ie QHY294m and ZWO 120mm but even when I had a ZWO 294mc I didn't get any of these issues either. Yes you have to use the "fork selector" in PHD2 but other than that all was fine and dandy. Choosing native drivers was fine too but from your screen shot you don't seem to have those listed either.. There are many folk using this type of setup in NINA so I'm not convinced it is a NINA issue but I can see why you would think that given your testing but will have a think on this one too