Hi,
Still progressing with the indi implementation of my mcmt32 controller. I have the vital functions up and running (sync, slew, ..). now I am considering implementing additional functions (parking, meridian flip management etc...) but I am rebutted by spending a lot of time reinventing the wheel, since :
1. this has already been done (eg in eqmod)
2. its not completely trivial (at least to my eyes).
3. the highest level functions can be abstracted from the underlying, low-level, mount-specific communication protocol.
4. the number of users of mcmt32 is rather small overall, and among those, linux users are...well... maybe I am the only one
So I am wondering if the best thing I could do at that point, would not consist in rendering mcmt32 eqmod compatible. This could be done by either :
1. emulating the skywatcher protocol in software in the driver (a kind of on-the-fly translation of the serial i/o messages between indi and the mount controller,
2. rewrite the controller's software (firmware, 2 uc32 units, 1per axis), so that it is skywatcher compatible.
At first glance, my feeling is that 1 is more straightforward (and less risky) than 2, I am still wandering in the skywatcher code at the time.
Before engaging in one of these, I'd like to collect expert advices on this issue, and maybe gather some information about the skywatcher protocol and the minimum subset of commands that must be emulated to work with eqmod.
(Should anyone be interested, the codes for the current library, indi driver and firmware are accessible here :
sourceforge.net/p/mcmt32/svn/HEAD/tree/
and those wondering "wtf is mcmt32", a description is here (french only...)
www.astrosurf.com/mcmtii/m32realisat.htm )
Thank you in advance for valuable advices.
Clear skies...