Build 1076 Locked-Up / Became Unresponsive

Issue #497 closed
Jim Waters created an issue

Description

N.I.N.A. 1.10 Build 1076 locked-up / became unresponsive when changing the PHD2 Plot Drop-Down from “Pixels” to “ArcSeconds” on the N.I.N.A. Imaging Page. I was forced to close down N.I.N.A. and restart everything. PHD2 was still running and guiding.

Equipment connected to N.I.N.A.

  • ASI2600MC Pro
  • Pegasus FocusCube2
  • PHD Guide 2 Rel 2.6.7 Dev 1
  • Gemini Telescope.NET
  • Manual Filter Wheel

Running the current ASCOM Drivers.

EDIT - I forgot to mention that I was dithering during imaging. I am running Win7 Pro x64 with all patches and updates.

Steps to Reproduce

  • I was unable to reproduce this lock-up.

Expected Behavior

Be able to switch from one to the other and back again.

Actual Behavior

N.I.N.A. locked up and was unresponsive. I could’t do anything. I had to close N.I.N.A. and restart. PHD Guide 2 was still running and I could change from “Pixels” to “ArcSeconds” and back again.

Comments (5)

  1. Jonathan MacCollum

    Was PHD2 also locked up during this time, or was only NINA hung during this lock up and PHD2 was completely responsive, completing the dither? Curious if it’s a related or unrelated to #496

  2. Jim Waters reporter

    PHD2 was running, making corrections and plotting the corrections on the graph. I didn’t try to change change anything - Pixels vs arc-seconds on the graph. Next time I will. I don’t recall if a Dither sequence was going on.

    It was just NINA that was locked-up. Nothing would work. There were no UI responses to anything I clicked on or tried to do. I had to use Task-Manager to kill N.I.N.A.

  3. Jim Waters reporter

    I just looked at #496. They could be related. I will be imaging tomorrow. I will try to force this to happen. If it does I will make sure PHD2 is fully functional - Stop / Start guiding, force a recalibration, …etc. I will put NINA in Debug mode.

  4. Stefan B repo owner

    Closing this due to an older build and hopefully it is fixed. If the problem rises again, feel free to re-open the issue

  5. Log in to comment