>>>So, you are saying that the approximate coordinates requested in slewing to a poison without a model, is good enough for local plate solving. Do I have that right? as others have said, that's

Minimum spot size off-axis. Rolando

A short session with Mike here at AP might solve your connection problems. Roland

Yes. If your image capture software gets the celestial coordinates from the mount, and then writes them into a FITS header, the plate solver will use them to do a "local" plate solve.

Hi Tom, I'll also have a look to see what I can find. Be patient, I get interrupted a lot! HKH

Hi Here is the log...

Thank you Bill and Don, I will check them out

Hi My understanding is that when a command is sent to the mount to move to a position, by the very design of the non encoder mount, it will move to this location precisely. I will upload a log

Roland, Can you please comment on what parameters you use for optimization of the backfocus distance from the flattener or TCC? Is it nulling curvature over a specified field or is it a trade-off

Dean, Yes, I am using short L-com usb cables and the through the mount usb works well. I added a Pegasus to manage my power cables and that also removed a lot of headaches. If I could just get

This distance should work for the 140ED. What results are you getting? Roland

On Sat, Jul 23, 2022 at 08:49 AM, Roland Christen wrote: For the 140FL lens the back distance is between 98.0 to 98.5mm, measured from the back flange of the TCC. If you use the 18.3mm extension then

Hi Tom, 4-5 arc sec is a HUGE amount. Could you please provide an APCC log file. The APCC log file will have more information in it than an APPM log file. Thanks, Mike Hanson

So, you are saying that the approximate coordinates requested in slewing to a poison without a model, is good enough for local plate solving. Do I have that right? Nathan Going mobile

Hi My understanding is that the slew warning occurs if the requested coordinates are not reached as commanded. They all appear to be 4 or 5 arc seconds off but only with the counterweight bar

That would depend on your camera. Some bin on the FPGA, after readout (but still in-camera), so you get the 4x size reduction (for 2x2 binning) before the image reaches the datalink (USB). But I think

Changed the subject line. I have been running for 3 hours tonight and no repro of the problem at all. For those using extremely wide fields like me (Field radius: 2.326 degrees) and if you know the

Jim & Todd, Thanks for taking a look. Hopefully this won’t turn out to be my only opportunity this new moon cycle, but the forecast for next week isn’t promising. -- Dean Jacobsen Astrobin Image

So that means that binning 2x2 means that image downloads will be slower than 1x1. Unintuitive. probably not noticeable in practice because downloads are saved to disk and that's going to be faster

Hi everyone, I just updated my CP4 and keypad so that technically I can now use the Point+Track model. Since it is recommended that an external planetarium program be used to create the model, I'm