Thank you, that makes perfect sense. In this case, at a dark site, I'll have the battery right beside the mount, heavy gauge wire, and at 200ah (and LiFePO4 chemistry) there's going to be no

Emilio, “overly paranoid?” Maybe, but your approach should also work very well and give the fewest problems. Personally, if you can do what you’re doing (three separate power sources),

Switching power supplies have very little or no output capacitor filtering, so they are very susceptible to ripple. In fact, some have ripple even when no load is applied. Linear power supplies are

I am curious if my practices are best management practices. I keep my cameras on one power source, my dew heaters on another, and my mount on the third. I don't mix the power sources. Is this

My own experience with running everything off a single, common power source has not given me any issues that could be attributable to doing that. I get the feeling that there are two main reasons

Linwood, In my experience it’s the other way around from what you suggest. It’s the MOUNT motors that dirty up the power – and the camera sees the “dirty” power as noise. Something

There is no risk to damage to the CP controller. The main problem is undervoltage, so if you run many applications from one battery, the terminal voltage might drop below the threshold for the CP to

First, I take all advice from AP seriously, and use a separate power supply for my mount now (AP1100AE). After my first attempt at night at a dark site, I need to redo my battery planning. I ran

Another suggestion worth looking into I hope is your power settings in Windows as I have found that USB connections can be powered off if not active after a period of time. Also check the Device

Have you tried ASCOM Device Hub? I use it and works great. I only use it for connecting multiple software related to ASCOM mounts like A-P V2 mount driver, PHD2, Stellarium, etc. It seems to help

I think Bob's point is more along the lines of don't trust *only* software to keep the unwanted from happening. If you're going to automate roof closures, make sure that your roof control system has

>>>Bob Denny put the fear of God in me to not use ACP automation to park and then close the roof. I'm not sure what to make of advice not to fully use automation software from an automation software

Just looking through your posts, my first inclination is to check the tracking rate that the AP ASCOM driver is reporting while this condition is happening and verify that it's in sidereal; not lunar,

There's not enough information to say for sure, but the most likely reason is the serial port hung. Are you using a USB/serial converter on a USB hub with a USB connection to your camera? If so, try

Yes, I have the Pier and I get fine images in all positions. I park at P5, but Bob Denny put the fear of God in me to not use ACP automation to park and then close the roof. If I use automation, I

Didnt see it listed so just asking, Is the FTDI driver installed?

I'm seeing the AP ASCOM driver "not responding" again, multiple times a night now. Seems the cable replacement was not a permanent fix. Can someone please help? Can't really automate image capture

John, I've followed your thread both here and over on the OpenPHD forum. I have to agree with Joel; the below extract of the steps you took to diagnose the problem and get a successful guiding session

Hi Alex, For ASCOM client applications (NINA, SGPro, etc.), the ASCOM driver's Park Setting setting is used, not APCC's. So, as others have already mentioned, you should set the park position in the

There are two park positions defined when using APCC. One is APCC and is the position it goes to when you hit Park on the same pane (brown arrow below). But the one NINA uses is the one set on the