NINA did not react! "ERROR: Camera Timeout - Camera did not set image as ready after exposuretime + 60 seconds"

[Albert.Fetscher]

During a running sequence sometimes it happens that NINA lost the connection to the camera (Canon EOS 250D) and is then 100% busy and did not react for further commands. NINA writes in this case many error messages in the logfile in an endless manner. The logfile size increases rapidly.

I have to switch off the camera, disconnect the USB cable from the camera, reboot the Mini-PC, connect USB cable to camera and switch on the camera again.

‌

Relevant logfile extract:

2023-05-28T23:07:38.0021|ERROR|CameraVM.cs|Capture|761|Camera Timeout - Camera did not set image as ready after exposuretime + 60 seconds
2023-05-28T23:07:38.0031|ERROR|EDCamera.cs|DownloadExposure|500|CANON: No new image is ready for downlaod
… 14 x same message
2023-05-28T23:07:38.0031|ERROR|EDCamera.cs|DownloadExposure|500|CANON: No new image is ready for downlaod
2023-05-28T23:07:38.0041|ERROR|EDCamera.cs|DownloadExposure|500|CANON: No new image is ready for downlaod
… 22 x same message
2023-05-28T23:07:38.0051|ERROR|EDCamera.cs|DownloadExposure|500|CANON: No new image is ready for downlaod
… and so on in an endless manner

‌

[Albert.Fetscher]

It's happening again today!

As usual, a sequence has started and everything seems to be fine. But after only 2 pictures were taken, the error message mentioned above "Camera Timeout - Camera did not set image as ready after hazard time + 60 seconds" came up again.
Look at the corresponding log file (I cut out the large number of lines (10034749 times) at the end that contained the same error messages "ERROR|EDCamera.cs|DownloadExposure|500|CANON: No new image is ready for download" multiple times) and the associated screenshot.

Any help is greatly appreciated.

[Albert.Fetscher]

  <div class="preview-container wiki-content"><!-- loaded via ajax --></div>
  <div class="mask"></div>
</div>

</div> </form>

[Stefan B]

Duplicate of #956.

[Albert.Fetscher]

Thank you very much for your fast reply!

I understand that this issue is duplicate, but what is the reason for this strange behaviour of NINA to endless writing the same error message in the logfile? This will rapidly increase the logfile file size and also it will lock NINA (looks like starvation due to endless events) so that NINA did not accept user input (like close window).

In the previous NINA version I don´t had this problem! (A lot of Windows 11 updates since then.)

What can I do now? Is there a work-around available? Can I help to reproduce this issue?

[Stefan B]

You can check if there are some firmware updates available for the cam.

Additionally you can try out the ASCOM.DSLR driver - it might work better (https://github.com/FearL0rd/ASCOM.DSLR/blob/master/README.md)

[Albert.Fetscher]

I already have the latest firmware update for the cam, i.e. the latest ASCOM Platform 6.6 Service Pack 1(“AscomPlatform661.3673“) since 14.11.2022 on my Windows 11 mini-PC, and never had this problem.

[Stefan B]

I’m referring to a different ascom driver to interface with the camera itself, not the platform. Check the link that i’ve posted, that explains how to install it.