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

This can happen when messages are getting queued up and cannot be sent out to the mount. Does this not happen when you disconnect from the ASCOM conditions hub? -Ray

Nice. Thanks for the comments Mark. Let me/us know when you put a longer package on the 1100. Myself I'm working with a new Stowaway on an old G11 Digital mount and waiting until I can swing an

I have no idea what this error means. I just changed my weather monitoring from using ASCOM Conditions Hub using a combination of Pegasus Sensors and API's to using a Lunatico Rain Sensor which has

Hi Howard, The button rates for directional buttons are minor and not terribly an issue for me. I have a bit of OCD and I always like to install the latest and greatest software/firmware. :-) I cannot

Please disregard my previous message. After trying it out, It seems your IP configuration is correct. Sorry for any confusion. That said, once you have joined the GTOCP4_NET_XXX, can you ping the

Port #23 is correct for IP connections with a CP4 Is the error being thrown by SkySafari 6 Pro for iOS? Or for Mac OSX? Or for both? I need to reconfigure things for Access Point mode, but I

I will try to reproduce your issue, but I have 2 keypads that have been loaded with the Java loader several times during recent testing. You can stay with 4.19.3 if you don’t mind the following:

Howard, I went ahead and re-installed Keypad version 4.19.5 and it was not successful. I successfully reverted back to Keypad version 4.19.3. It could be the following reasons: 1) I didn't follow your

Not 100% sure about this but IIRC, the last byte (digit) of the mount's IP address when using the access-point mode should correspond to your CP's serial number, (if you have not changed the default