开云体育

Gemini/Nina connection issue

Chuck Schreiner All Messages By This Member #27228 I have now gotten the error message when trying to slew in NINA 'ASCOM Driver Error SlewEquitorialAsync' on several occasions. NINA discord feedback is that this is a connection issue. I have solved it sometimes by rebooting everything, changing where the usb b cable from Gemini plugs into my laptop and/or by changing cables. Last night none of these worked (I didn't have a backup cable).? ? Any suggestions??
Jim Waters #27229 How do you have the Power Management settings configured on your laptop?? Is "Allow the computer to turn off this device..." disabled?? Are other USB devices working on your laptop? ? ----------------------- Jim W Phoenix, AZ USA
Chuck Schreiner All Messages By This Member #27230 Hi Jim, ? I tend to plug Gemini into the Thunderbolt (3.1) port, but sometimes into a USB port directly or thru a USB hub. It (and the 2 USB ports) all have the "allow the computer to turn off this device' enabled. The other UBS devices (cameras, focuser) are working. I only have 2 usb ports and the Thunderbolt.? ? The thing that confuses me is it works intermittently. Last night, it slewed to my main target properly the first time, but after I redirected the mount to regain a better guide star, I could not get the mount to slew back to it - but it would slew to a different target. I have gotten this error message before, and rebooting or rerouting the cable solved it.? ? Thx, ? Chuck
Chuck Schreiner All Messages By This Member #27231 One more data point. When I slewed to get a different guide star (and recalibrate PHD) it was West of meridian (and PHD gave me a warning). I was trying to image M16, east of the meridian. I wouldn't think that would interfere with slewing. But...?
Paul Kanevsky All Messages By This Member #27232 On Sun, Aug 4, 2024 at 02:21 PM, Chuck Schreiner wrote: I have now gotten the error message when trying to slew in NINA 'ASCOM Driver Error SlewEquitorialAsync' on several occasions. NINA discord feedback is that this is a connection issue. I have solved it sometimes by rebooting everything, changing where the usb b cable from Gemini plugs into my laptop and/or by changing cables. Last night none of these worked (I didn't have a backup cable).? ? Any suggestions?? ? Sounds like a communications error between the mount and the PC, but can't tell for sure without seeing the ASCOM driver log for that session: ? What version of the Gemini.NET ASCOM driver are you using? Here are the latest: ? Regards, ? ?-Paul
Jim Waters #27233 On Sun, Aug 4, 2024 at 04:37 PM, Chuck Schreiner wrote: all have the "allow the computer to turn off this device' enabled. These need to be disabled / off, Unchecked.? Is your Hub powered? ----------------------- Jim W Phoenix, AZ USA
Chuck Schreiner All Messages By This Member #27234 My hub is not powered...I have debated (with limited understanding) whether to use a powered hub or not
Paul Kanevsky All Messages By This Member #27235 On Sun, Aug 4, 2024 at 09:27 PM, Chuck Schreiner wrote: My hub is not powered...I have debated (with limited understanding) whether to use a powered hub or not How long is the USB cable? If it's over 3m long, you may want to try a powered hub (or a shorter cable).
Paul Kanevsky All Messages By This Member #27236 On Sun, Aug 4, 2024 at 09:44 PM, Paul Kanevsky wrote: How long is the USB cable? If it's over 3m long, you may want to try a powered hub (or a shorter cable). Also depends on how many devices are plugged into the unpowered hub, and how much power they each need. If you have more than one USB device, you should also try a powered hub.
Chuck Schreiner All Messages By This Member #27237 Thanks, Paul. ? I have 1.1.23... most recent is 1.1.25. I have several logs from last night as I rebooted trying to fix it. I am not sure which log is pertinent to report. I am going to update and if/when I replicate error note the log so I can upload it. ?
Chuck Schreiner All Messages By This Member #27238 Ok, will try powered hub.
Jim Perch All Messages By This Member #27259 I was having time out and other serial connection issues in NINA and joined this group because of those issues. I was even getting a warning when I connected. I saw that there is a new beta release on the Gemini-2 downloads site, 1.26, ?that says it addresses the ‘NINA time warning’. Hopefully this will do the trick for both of us.
Paul Kanevsky All Messages By This Member #27260 On Sun, Aug 11, 2024 at 03:20 PM, <jperciac@...> wrote: I was having time out and other serial connection issues in NINA and joined this group because of those issues. I was even getting a warning when I connected. I saw that there is a new beta release on the Gemini-2 downloads site, 1.26, ?that says it addresses the ‘NINA time warning’. Hopefully this will do the trick for both of us. ? The beta was really for a time mismatch warning between the PC and Gemini. Timeout errors are something different and usually indicate communication problems. How’s Gemini-2 connected to your PC? ?
Jim Perch All Messages By This Member #27261 USB 3.0 directly to the Gemini 2 controller via a 1m USB cable
Paul Kanevsky All Messages By This Member #27262 On Sun, Aug 11, 2024 at 05:32 PM, <jperciac@...> wrote: USB 3.0 directly to the Gemini 2 controller via a 1m USB cable Sounds like there are issues with the USB connection or port on the PC or Gemini side. I'd try a different USB cable, first, just in case.
Jim Perch All Messages By This Member #27263 I tried a different cable and a different port just now and I get the same error messages when I connect:? Ascom: mount connected Ascom: serial port timed out! Ascom: Gemini not responding! Terminating connection NINA: Ascom driver error. Unable to connect to Gemini telescope. Reason: device is not connected NINA: success! Mount connected.? Ascom: Mount is disconnected Ascom: Connecting to Mount… Ascom: Mount is connected.? what a rollercoaster ride. Is this normal when it connects with NINA?
Paul Kanevsky All Messages By This Member #27264 That could be if you have another USB/serial device that is responding to initial Gemini commands. When ASCOM driver searches for the correct COM port, it'll try each one in turn. If one of them responds to Gemini "hello" command, the driver assumes it's Gemini. You may want to make sure you use the correct serial port Gemini is connected to, select that COM port in the driver setup, and turn off Auto-Detect Gemini option: ?
[email protected] All Messages By This Member #27265 开云体育 Not normal, I’d say the ASCOM driver may be out-of-date or corrupt. It would be wise to verify all apps that work with NINA and your mount are up-to-date. toggle quoted message Show quoted text On Aug 11, 2024, at 2:50?PM, jperciac@... wrote: I tried a different cable and a different port just now and I get the same error messages when I connect:? Ascom: mount connected Ascom: serial port timed out! Ascom: Gemini not responding! Terminating connection NINA: Ascom driver error. Unable to connect to Gemini telescope. Reason: device is not connected NINA: success! Mount connected.? Ascom: Mount is disconnected Ascom: Connecting to Mount… Ascom: Mount is connected.? what a rollercoaster ride. Is this normal when it connects with NINA?
Jim Perch All Messages By This Member #27266 Unchecking the Auto-detect box did not help. ?I am going to uninstall/reinstall Ascom, and get a fresh start. Should I uninstall/reinstall Gemini and NINA at the same time to start off really fresh?
Paul Kanevsky All Messages By This Member #27267 On Sun, Aug 11, 2024 at 06:47 PM, Jim Perch wrote: Unchecking the Auto-detect box did not help. ?I am going to uninstall/reinstall Ascom, and get a fresh start. Should I uninstall/reinstall Gemini and NINA at the same time to start off really fresh? I don't see how reinstalling could help, but sure, give it a try. I think you still have a communications problem between the PC and Gemini.

Previous Topic Next Topic