Is this necessarily a com failure with the camera or could it be caused by other things, perhaps either: The intervention of a weather shutdown interruption cloud cover? If not, we may have a camera dropping of. Here is a log excerpt. 05:09:28 (exposure complete) 05:09:30 **Pointing update error from MaxIm DL 7: Image not Available: Either the camera aborted the exposure, or no exposure was requested before a download was requested. Please try your exposure again. ACP console log closed 16-Dec-2025 05:09:30 UTC
Sorry for the delay. Adam is our expert on the DLAPI drivers, and he's off on Christmas vacation. I did some experiments and found one way to cause this error to happen. The camera will automatically power down the sensor if it doesn't see a message for ten seconds. It does this to protect the sensor from damage due to improper shutdown. In testing with an older computer, simply connecting to it via Remote Desktop caused all running applications to freeze up for a time - including MaxIm DL. The freeze was long enough that it caused the camera to shut down the sensor, and that meant there really was no image available when MaxIm DL came back to life and tried to download. Everything continued normally when I started the exposures running again. Obviously a temporary network outage could also cause this to happen, but it seems simply having something prevent applications from executing temporarily can also cause it. Maybe check your Windows System logs to see if anything unusual happened just before that error.
Get Danny to follow steps outlined below. When the host's Remote Desktop service determines a client is trying to connect, it spins up several Virtual Devices - this causes stuff including USB (and Thunderbolt ports) to be re-scanned. Post #5 here: https://forum.diffractionlimited.co...rn-off-usb-selective-suspend.7848/#post-59482
