Thanks for checking Howard. That .101 is the address the CP4 gave to my Mac/iPad, indeed the .1 is for the CP4 itself. At one time I had both the iPad and the Mac connected, and the first one got .100

My Kaspersky Internet security is detecting malware in the latest download of Apccstandardlatest.exe and requiring a disinfect/restart of WIN10 Pro. UDS:trojan.win32.generic Questioning if this is an

Contact me off-group, Peter, and let me make sure you have the very latest loader and program files. Mag. 7 or Better Skies! Howard Hedlund Astro-Physics, Inc. AP Phone: 815-282-1513 Direct

Thanks much, Ray. Greatly appreciate the info.

michael mccann wrote: You’re right, and I’m seeing that there’s a conversion factor I hadn’t take into account. Thanks for being persistent. You are most welcome. I am pretty

Hi Bruce, Dale Ghent did a great writeup on using NINA with A-P mounts. If you haven't read this yet, please take a look: https://daleghent.com/nina-and-astro-physics-mounts If you do not desire to

Hi Marty, Since you mention TPoint, does that mean you have SkyX? If so, have you tried plate-solving any of your images with SkyX's image link? If needed, there is a much deeper stellar database

Hi Geoff, That part of the documentation could be better worded. "Slew" was meant to be a move either by button presses or setting the move rate to a fast speed in APCC or the ASCOM driver and just

Hi Brian, APPM can also use NINA, SGPro, SkyX, CCDSoftV5, and MaximDL to take images through their automation interfaces. -Ray

Hi Aygen, I'm glad that the new driver works in your setup! Thanks for letting us know! Best regards, -Ray

I've been using NINA to image with my AP1100 (no encoders) in my observatory. I connect NINA to the AP driver and everything is working fine. The only thing I have not done is to set up safety

I've tried four cameras, all coupled to a focal reducer. I've tried binning from 1x1 to 3x3. Sensor data (microns and arcminutes): Sensor 1: Pixel = 5.9 and FOV = 1.4x0.9; unbinned image scale = 0.40

You’re right, and I’m seeing that there’s a conversion factor I hadn’t take into account. Thanks for being persistent. Cheers

I'm sorry, somewhere in here I have gotten lost. Which number is 20+ degrees off. In all cases it looked to me like you did a conversion from decimal degrees to degrees/minutes/seconds when you

In the APCC documentation the following warning appears frequently: "The Meridian Limits, are primarily tracking limits in the west, and counterweight-up slewing guides for APCC's advanced slew logic

So I don’t have a way to grab an exact coordinate reading from three processes that run serial. So I don’t expect ASCOM, APCC, NINA Equipment->Telescope RA/DEC values to be all exact. Obviously

Do we have a difference in format. Let's start with your first case, where for RA you had almost identical values except the fits header. You showed a conversion of 23.461914 to 23:27:42.89 but

And since I’m shooting M74 tonight APCC. 01:37:53.04. 15:47:03.44 Image fits header 24:10:26.76. 15:47:14.64 PI image solver 01:36 : 41.067. 15: 47:

Thanks, Ray! You said "Regarding the 70 Mpix image not loading, I assume you are using the camera’s ASCOM Camera driver? There are some VERY inefficient ASCOM drivers that require over 1 GB of ram

Thanks Linwood So I reset park position 3 then used NINA Framing to sleep and center on M 33. I then RA/Dec values from ASCOM, APCC, NINA->Equipment->Telescope RA/Dec, NINA plate-solve routine, the