0.00
#...
·
 |
|---|
|
Hi Everyone, I had a strange issue last night with my setup that I have not experienced before: I had polar aligned early in the evening and since the weather was cloudy until later in the night (and my target was obscured for the first hours), I programmed the ASIAir Pro to start the Plan later. I had slewed to the approximate orientation (but no centering as target was obscured) - as you can see below, it pointed quite close to the correct orientation. However when the plan started, it apparently could not control the mount anymore! Here are the first part of the log: Log enabled at 2023/02/21 19:47:15 2023/02/21 19:47:15 Plan NGC 4889 Start 2023/02/21 19:47:15 [Autorun|Begin] NGC4889 Start 2023/02/21 19:47:15 Wait 3h12min45s 2023/02/21 23:00:00 [AutoCenter|Begin] Auto-Center 1# 2023/02/21 23:00:00 Mount slews to target position: RA:13h1m15s DEC:+27°51'7" 2023/02/21 23:00:17 Exposure 5.0s 2023/02/21 23:00:24 Plate Solve 2023/02/21 23:00:25 Solve succeeded: RA:13h1m37s DEC:+27°45'39" Angle = 60.2073, Star number = 254 2023/02/21 23:00:29 [AutoCenter|End] Mount Sync failed 2023/02/21 23:00:31 [AutoCenter|Begin] Auto-Center 2# 2023/02/21 23:00:31 Mount slews to target position: RA:13h1m15s DEC:+27°51'7" 2023/02/21 23:02:01 Exposure 5.0s 2023/02/21 23:02:08 Plate Solve 2023/02/21 23:02:10 Solve succeeded: RA:13h1m39s DEC:+27°45'41" Angle = 60.2015, Star number = 249 2023/02/21 23:02:14 [AutoCenter|End] Mount Sync failed 2023/02/21 23:02:16 [AutoCenter|Begin] Auto-Center 3# 2023/02/21 23:02:16 Mount slews to target position: RA:13h1m15s DEC:+27°51'7" 2023/02/21 23:03:37 Exposure 5.0s 2023/02/21 23:03:44 Plate Solve 2023/02/21 23:03:46 Solve succeeded: RA:13h1m39s DEC:+27°45'41" Angle = 60.1982, Star number = 247 2023/02/21 23:03:50 [AutoCenter|End] Mount Sync failed 2023/02/21 23:03:52 [AutoCenter|Begin] Auto-Center 4# 2023/02/21 23:03:52 Mount slews to target position: RA:13h1m15s DEC:+27°51'7" 2023/02/21 23:05:22 Exposure 5.0s 2023/02/21 23:05:28 Plate Solve This continues all night and ends like this: 2023/02/22 05:55:07 [AutoCenter|End] Plate Solve failed, Star number = 20 2023/02/22 05:55:09 [AutoCenter|Begin] Auto-Center 238# 2023/02/22 05:55:09 Mount slews to target position: RA:13h1m15s DEC:+27°51'7" 2023/02/22 05:56:39 Exposure 20.0s 2023/02/22 05:57:01 Plate Solve 2023/02/22 05:57:02 [AutoCenter|End] Plate Solve failed, Star number = 7 2023/02/22 05:57:04 [AutoCenter|Begin] Auto-Center 239# 2023/02/22 05:57:04 Mount slews to target position: RA:13h1m15s DEC:+27°51'7" 2023/02/22 05:58:34 Exposure 20.0s 2023/02/22 05:58:56 Plate Solve 2023/02/22 05:58:57 [AutoCenter|End] Plate Solve failed, Star number = 7 2023/02/22 05:58:59 [AutoCenter|Begin] Auto-Center 240# 2023/02/22 05:58:59 Mount slews to target position: RA:13h1m15s DEC:+27°51'7" 2023/02/22 06:00:29 Exposure 20.0s 2023/02/22 06:00:51 Plate Solve 2023/02/22 06:00:52 [AutoCenter|End] Plate Solve failed, Star number = 7 2023/02/22 06:00:54 [AutoCenter|Begin] Auto-Center 241# 2023/02/22 06:00:54 [AutoCenter|End] The target timeout 2023/02/22 06:00:55 [Autorun|End] Pause Autorun 2023/02/22 06:00:55 Pause Plan NGC 4889 2023/02/22 06:00:55 Turn Off Cooling 2023/02/22 06:00:55 Stop Tracking 2023/02/22 06:00:57 [Guide] Stop Tracking failed 2023/02/22 06:00:57 Stop Tracking 2023/02/22 06:00:59 [Guide] Stop Tracking failed 2023/02/22 06:02:29 Mount GoTo Home POS failed 2023/02/22 06:02:29 Stop Tracking 2023/02/22 06:02:33 [Guide] Stop Tracking failed 2023/02/22 06:02:33 Stop Tracking 2023/02/22 06:02:35 [Guide] Stop Tracking failed Log disabled at 2023/02/22 06:02:35 It was cloudy by then, which is why almost no starts were detected in the end. So it kept trying, and the the mount kept tracking until 06:00. The mount did stop tracking either here ore a little later, as it was stopped when I went out at 06:40. I could not go to home position and had to shut down and turn RA and DEC manually back to home. After restarting, it behaved as normal again, just like it had when I set it up in the evening. My question is just: has anyone experienced anything similar? Is there a good procedure to avoid this, when the you don't start the plan immediately? I would like to be able to program this without having to get up and check if it then actually happens! Why would the ASIAir loose the connection to the mount while waiting to start the plan? BR Morsing |
0.00
#...
·
·
1
like
|
|---|
|
Hello , I guess I experienced a similar issue with my GEM28. I’m running N.I.N.A. on a Win10 mini PC. For me the issue occurred twice so far. Both times I followed the same procedure. - Slew to the Target with N.I.N.A. and took a test shot for framing. - The mount started tracking as normal (no autoguiding) - Some wait time occurred for setting up my sequence, cooling down the camera, … . - Starting the sequence the mount is slewing to the target and taking a picture to plate solve. - The next slew to center the target is failing. I had to turn off and on the mount to get it working again. My guess is that the mount is trying to slew to the coordinates where it is already tracking at. So no move needed. But this brakes something and the next slew couldn’t be performed. Which Firmware do you use for your GEM28? Mine has 210422 which should be the newest. Regards Christian |
|
0.00
#...
·
|
|---|
|
That does indeed sound very similar to what I saw! It is interesting that it clearly has to do with the mount, not the controlling software or device. I also think I would have been able to fix the issue with a re-boot, if I had discovered it at the time! I think your theory about this happening when the telescope is pointed towards given spot and a command is then given to goto those same coordinates is very interesting. This may somehow cause the mount to loose connection to the controlling computer, though if true, this is clearly a bug. I have previously had no issues with a delayed start like this but thought I would prep it by pointing the telescope in the right direction to begin with! Apparently this may be a bad idea! BR Morsing |
