Possible bug with nightly build 1.11, NINA Closes connection to equipment for no reason
[X] Is the issue reproducible? (Not sure)
[ ] Are you running the latest version? (Latest Nighly build)
[ ] Are all prerequisites that are mentioned inside the manual met?
Description
I had a sequence that was working normally and was supposed to loop until 2:43am, and suddently at 23:16 it closed connection to the equipment for no reason.
Steps to Reproduce
- Would need to restart the attached complex sequencer
Expected behaviour
Should’ve continue looping until 2:43am and then moved to another target.
Actual behaviour
Closed connection at a random time.
Attaching LOG and Complete sequence used.
Hope this helps for the Nightly build to be more stable, it is wonderful !.
Comments (5)
-
-
reporter Hello Dale, thanks for the quick reply. The Telescope was unattended, i promise, i was actually sleeping at that time.
Maybe i have something wrong on my Sequence?. i attached it for revision.
again thank you so much for the quick support.
-
repo owner Hi,
these messages will also be emitted when the connection closes unexpectedly. As everything disconnected at once it could be that the connection to a USB hub was lost or suspended by windows power saving.
-
reporter Hello Stefan, That sounds more like it. Maybe Windows crashed. I’ll try it one more time and report back.
thanks so much,
Clear skies.
-
repo owner - changed status to closed
assuming problem is solved
- Log in to comment
Looking at the log, there is the following:
Followed by an error emitted by your mount’s ASCOM driver.
There is no automatic way to disconnect equipment in NINA, so any equipment disconnects would have to be user-initiated by pressing each equipment’s disconnect button, pressing the master disconnect/reconnect button in the lower left of the window, or by closing the application.
It would appear that since the Camera, Telescope, and Focuser were all purposefully disconnected at the same time, so you might have clicked on the master connect/disconnect button in the lower left of NINA’s screen by accident. There is no other way for devices to suddenly gracefully disconnect like this in short order.
The ASCOM driver error message is a different matter, likely because the Telescope driver was disconnected.