On Sat, May 25, 2024 at 04:02 AM, Sean wrote:
? ? ?05/24/2024 22:33:06 ? ? ? ?14:03:12 ? ?54¡ã 13' 57" ? ?00¡ã 06' 59"? ? ? ? ? ??00:00:01? ? ? 00¡ã 06' 59" ? ?10.27? ? ? ? ? ? ? ? ?295.33? ? ? ? ? ? ? ? 179.6327463348333
Sean,
This looks similar to a rare issue the occurred on my Gemini-2 board.? Something observed using ASIAIR during beta which David and Rene resolved for me.? My ASIARI would Go-To a target, and would get very near, attempt to adjust, and fail to acquire the target by some sub-minute amount.? ?David Partridge sent a note where Rene had suggested I send the controller a :p0# command.
The similarity here, to my case, seen using the Target, JNow and J2000 references. From SkySafari (to limit possible data sources difference non stellar and dates) the JNow and J2000 positions of M101 on SkySafari equate to:?
JNow = 14:04:05 / +54:13:54 and
J2000 = 14:03:12 / +54:21:04.? {colored to hopefully make it clearer}
Notice that on NINA's corrected position in the second line, the RA (basically) matches the
J2000 value (14:03:12 versus
14:03:12) but the DEC value (basically) matches the
JNow value (+54:13:57 versus +
54:13:54).? An apparent split J2000/JNow address instead of a JNow/JNow for the RA/DEC components.? Resulting in NINA trying again.
My sending this command to Gemini-2 straightened out the issue within the Gemin-2 logic.? I've never seen the behavior since.??Try also sending a :p0# command.? Easiest way, with ASCOM connected to the mount to use the ASCOM App "Setup"->"Command Terminal" to? Type the command :p0# into the console window and press Enter.? Something small, see if the behavior changes.
?
Note too that no one else saw this behavior, the conclusion being, I likely did something or left something out on conversion.??
Regards,
Doug
