Thanks for the heads up. I installed the new driver. I like that is's 64bit and the new settings dialog with the backlash compensation.
When testing the driver with my python application, I got strange temperature readouts (thousands instead of tens of degrees, see screenshot). I suppose I have to divide them by 100 to get the actual temperature in degrees Celsius?
And then, from time to time, I get an exception (probably thrown by ASCOM), stating:
"Temperature value wrong format. Message received from hardware :=0400"
The values displayed in the exception message are either even hundreds with a leading zero ("0300", "0400", ...) or even tens with a leading plus sign ("+20").
Interestingly, when I use the new driver with the POTH hub, the POTH dialog always displays the correct temperature.
What's more (I observed the same behavior with the previous driver version), while the focuser is moving, the driver returns a temperature value of 100. I was wondering if this is intended behavior or a bug.
My testing was not so thorough, but a couple of times, the focuser wouldn't move at all when told to, and the driver would would not respond and hang the application. I never had this with the old driver.
That's all about my observings so far. If I discover anything else, I will let you know.
P.S. I haven't forgot about the 12h test, just haven't had the time yet.. (I do not like to leave the stuff unobserved because my two cats have already shown more interest in the UFO than I feel comfortable with. Probably they think it's a mouse :) ).