Thanks Luka,
I'll take you up on that in week or so then.
The focuser position change seems to be common to all of these new ASA focuser, but the manufacturer seems to think it's a feature rather than a bug, and since the way it works is by constantly adjusting the focuser to maintain the measured position the reported position probably does change by a micron. In Practice, the critical focus zone for this scope is 30 microns so a 1 micron change is insignificant- and focusmax, ASA's own sequence software have no trouble with this.
Unfortunately, I'm trying to use SGPro for observatory control, as so far it's my preference. But I can see the path of least resistance is going to be getting another sequence program to do the work.
Anyway - figured it's about time I grew up and learnt to code in C#...
Quote:
Originally Posted by luka
Hi Andrew, coffee would be great but I am stretched very thin until the middle of the week after next so probably can't make it before then.
Two ways you can approach the problem:
1. Write the intermediary driver - take the ASCOM template for focuser and then pass all the calls to the DLL of the original driver. Then you only need to modify the position reading to include the tolerance.
2. If you have the focuser commands, you can probably use an existing ASCOM focuser source code (there are few on the net) as a starting point and then just re-implement the commands.
Just wondering, is this a problem with your focuser or with the model? If latter the manufacturer should be fixing the issue?
|