Quote:
Originally Posted by luka
Rob, sorry about that, hopefully you did not lose any data.
After your post I did a bit more poking around and I think that the problem is caused by the Chinese communication library (DLL) that we are using now. If for whatever reason it fails to read data from the device it just locks up the driver which then locks up SGP. My old driver had timeouts to avoid lockups but now we are relying on the DLL.
By the way, SGP is also partially to blame as it should also be using timeouts to recover and not relying that everything will always work perfectly.
While I could work around the "locking up" problem, I may spend the effort to rewrite the DLL. I can reuse the code from my old driver so it should not take too long. This was on my to do list for some later stage anyway.
|
No guilt required - I was nearby all night keeping a very close eye on things, knowing well it was Beta code you'd shared. When I did pluck it in the milddle of an SGP freeze surprisingly SGP pepped up again and kept going like nothing had happened. Definitely agree that would be nice for Sequence Generator to be more robust - the programmer have frequently commented they do their best to implement ASCOM standards with expectations the gear is playing ball. Your comments re the chinese DLL seem consistent with what's been happening though.
I'm also experiencing infrequent USB challenges with my gear even without the temperhum. Wish I knew if it was power, cables, gear - trying to steadily tick off things on at a time.
Not the most reliable tester right now alas.....
