¿ªÔÆÌåÓý

  1. Gemini-II
  2. Messages
Single Messages Topics Expanded Polls

Re: Gemini ASCOM Driver and NINA Settings when I change equipment

 

I doubt the guiding performance would be affected if you have an incorrect focal length or ratio specified -- most autoguider software deal with pixels, internally. Conversion to arcseconds does require these settings, but that's mostly for human consumption :) Plate solving, centering, etc., might be affected if you have an incorrect image scale, but that depends on the software.

I assume that when you restart your system, NINA will attempt to read these settings from ASCOM driver. Since these were not updated in ASCOM during the previous session, they may be incorrect. This is more about NINA behavior with respect to these settings than about ASCOM, so maybe someone with better knowledge of NINA can answer this.

Regards,

? ?-Paul


On Sun, Jul 9, 2023 at 12:25 PM, <geoffchapman47@...> wrote:

On Sun, Jul 9, 2023 at 12:05 PM, Paul Kanevsky wrote:
I assume that NINA has its own setting that overrides ASCOM. But when you change it in NINA, this cannot be updated in Gemini.NET driver, since ASCOM doesn't support this.
Thanks for these, Paul.

If NINA does indeed 'override ASCOM' - let's say I changed equipment, adding the reducer after boot up and reset my NINA focal length and focal ratio settings to match the added reducer. But let's say I did NOT reset the Gemini driver to match my equipment change - in that case the Gemini drivers and NINA would not agree.

If so, would it affect tracking or guiding performance?

And when I reboot, if I do not reset the Gemini Driver to match my added reducer, wouldn't it import its (now incorrect) focal length setting to NINA, further confusing my equipment?

I have had tracking issues in the past, which now seem largely resolved through mechanical adjustments. But could this have been part of my problem??

Geoff
Join [email protected] to automatically receive all group messages.