-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Auto Resolve (ASTAP) works but Error after first image during Model Run #239
Comments
Not sure if this is an actual error per se, but at least the model build process does not continue - and I have no idea where this is coming from. |
Herwig, |
Hi Michel, After the first "stop" occurred, I changed log file settings from default to debug - hope MW4 was able to change this "on the fly". If you need another log file, I can redo it tonight. As my 10micron was defective, the control box was for service in Italy and when it came back, all data was of course deleted - so I need a new model; for that, I just yesterday migrated from MW3 to MW4 - this is why I don't know if it was working in previous versions of MW4. |
Hi Michel, |
Herwig, |
Hi Michel, Perhaps the latest ASCOM Driver from ZWO is doing some new tricks? I think it is from April or May 2022 so quite new... |
Herwig, |
Hi Michel, |
Hi Herwig, |
Describe the bug
MW4 v2.2.4, all devices connected and working.
Manual exposure of picture working and resolved successfully with ASTAP
When Trying to run a 3 points model, after first exposure and first (successful) plate solving, an Error is displayed:
Excerpt from log file:
To Reproduce
Steps to reproduce the behavior:
Expected behavior
If this is really an error, it should stop the model build, but apparently the model build process is stalled at 33% (as first point was solved); Elapsed time is stopped counting, but "Cancel" Button is still active (and you have to press it in order to use the software again.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: