Pegasus Astro DMFC Focuser Bug/Crash
Posted: Wed May 16, 2018 8:10 am
Hi Robin,
The Pegasus Astro DMFC focus controller uses +ve/-ve integer values, it is designed to be set to 0 at an arbitrary focus point and then can be driven in the +/- from this reference point.
The problem comes that the design of the SC focus interface only accepts +ve integers so if the value is -ve it crashes on connection.
The ASCOM driver for Pegasus allows the focuser to be sent a goto 0 command on connect, which stops it crashing on connect, but the
UI won't then allow it to drive in the -ve direction below 0.
Adding the +ve values only details to the manual would have saved a bit of head scratching.
Allowing a checkbox protected "allow -ve values" and associated functionality would help us out, this is becoming a widely used device as it's cheaper and more universal than the market incumbents.
Thanks in advance, Phil
The Pegasus Astro DMFC focus controller uses +ve/-ve integer values, it is designed to be set to 0 at an arbitrary focus point and then can be driven in the +/- from this reference point.
The problem comes that the design of the SC focus interface only accepts +ve integers so if the value is -ve it crashes on connection.
The ASCOM driver for Pegasus allows the focuser to be sent a goto 0 command on connect, which stops it crashing on connect, but the
UI won't then allow it to drive in the -ve direction below 0.
Adding the +ve values only details to the manual would have saved a bit of head scratching.
Allowing a checkbox protected "allow -ve values" and associated functionality would help us out, this is becoming a widely used device as it's cheaper and more universal than the market incumbents.
Thanks in advance, Phil