Ray said: Especially if you had it loaded for a while, it is also important to check you have a database that matches the image scale. See https://www.hnsky.org/astap.htm H17 doesn't work well

Thanks for clarifying. I didn't catch that.

Just to be clear, this is a reference to PulseGuide, the software application I wrote almost 20 years ago. This is not the same as the ASCOM pulseguide method. -Ray

That's a matter of the performance of your computer and the plate-solver. If you were using SkyX, PinPoint, or PlateSolve2, I would be surprised. If it's ASTAP, it's likely the plate-solver

I would just use a thicker washer to emulate the solid knob. To me, it looks like the washer under your button-head screw is ALMOST good enough as-is, but potentially could bend into the slot in the

I am convinced that the issue is either within windows or could be related to the fact that I have the mount not directly connected to the computer, no doubt. I was hoping that someone else had run

I have two 8” extensions which I never separate when transporting the Eagle tripod/pier. As you know, the two 8” extensions are joined by three machines knobs. Since I never separate these

That was my understanding of your analysis indeed. 100% agree on that. That's why I put the quotes to "smarter" (as with everything, syntax is important ;-) ) Sébastien

Hi, I started a dummy modeling APPM run indoor last night using the NASA Skyview camera and the Mach2. Platesolving wasn’t especially great at those Nasa Skyview images and so slow that at some

You wanted to know why APPM couldn't get the RA/Dec from your image. The official answer is that you supplied a non-compliant FITS image. APPM can't guess how other applications might break the

As I said, I am using my own ASCOM driver test application. It doesn't use buttons. It just has the ability to set a MoveAxis value, which stays until changed. This makes it easy to confirm the mount

Thanks for the analysis, Ray. I suppose then ASTAP and ASPS must interpret those fields in a "smarter" way by removing the leading blank before parsing as you propose for the next build or use the

>>>Interesting Andy. I use phd2 for guiding and my virtual ports are 20 and 21 I believe. i've only used ports 20 and 21, and had no issues with APCC. i don't think port numbers that high are the

My mount is connected directly to my computer. All my imaging gear, etc... is connected through a Pegasus Advance which is mounted on the OTA. This cables off to the PC which is under the mount.

You need to make sure that APCC closes itself rather than having another program terminate it improperly. When APCC closes itself it closes (inactivates) the virtual ports. If the program is

There is something going on with my Com ports that I don't quite understand and the virtual ports in APCC seem to interfere with my actual com ports. Chris do you have your mount connected directly to

Interesting Andy. I use phd2 for guiding and my virtual ports are 20 and 21 I believe. I have no problems that I know of. I have not used the new apcc pro update yet, so maybe this port number thing

I have an update. Had my virtual port set to com10 and it didn't work. When I set the virtual port to com20 everything worked fine. Is it OK to keep the port at com 20? I read in the manual that I

Hi Ray, I have the Jog utility but I am trying to use the three point polar alignment routine with NINA and that requires the client app to be able to use the Moveaxis command. If it's working for you

Andy, APCC has always supported the "MoveAxis" command through the ASCOM driver. I just tried it, and it works for me using the V1 chip using my own ASCOM test application. BTW, since you are