Nial

Yeah, I was toggling the light on and off multiple times, and it would hit an increasing delay between the light state changing and the interface being re-enabled I also tried setting max birghtness to 255 which unfortunately didn't work. This time I toggled multiple times, disconnected, then reconnected, and tried to toggle again and it happened immediately. So was working before disconnect/reconnect. I've attached the latest logs Thanks for all your hard work!

And here are the logs when the DarkLight software stopped responding

Hey Nathan, thanks for getting back to me so quick! In answer to your first question the light did turn on before it froze And I've retrieved some logs from testing today, I've attached them and hopefully they help. Although it was a bit harder to get it to reproduce today. The toggle button actually started working straight off, however after one or two times there was a long delay before the toggle would happen. I also tested swapping back to the DarkLight program as well, and experienced similar...

I should also mention that once it gets locked up like this I need to disconnect the usb, and power the panel off, before I can use it again

Hey Nathan, Just wanted to flag an issue I’m having using DarLight with NINA. It connects fine, and the open and closing of the panel works great, however toggling the light from the software seems to bring back the CoverCalibrator.get_CoverState() issue. The error from the logs is: 2023-12-05T16:06:42.3781|INFO|FlatDeviceVM.cs|ToggleLight|449|Toggling light to True 2023-12-05T16:08:42.8050|ERROR|DeviceUpdateTimer.cs|Start|103 ASCOM.DriverAccessCOMException (0x80040402): Timed out waiting for received...

Hey Nathan, thanks for the quick response It's actually started working again. I think what may have happened was either of two things: The EEProm library I was using wasn't the one provided in the zip, I let the Arduino IDE install the latest. So I went back and made sure it used the provided library I went into device manager and made sure to disable the setting for putting USB devices to sleep. I suspect that this might have actually been the cause? As if the device was put to sleep, due to all...

Hey, just wondering if this error has popped up for anyone else? I've seen it both from using the program directly, or from connecting through NINA. In NINA it will say that the cover state is unknown, and in the DarkLight program this will happen when trying to connect. It's making the cover pretty difficult to use right now, so not sure if there's something up with. It can be fixed by disabling and re-enabling the usb port.