Hello,
I certainly do
Right now it functions as a remote control, with which you can navigate and configure your guiding. What is missing dearly is a how-to, but to summarize:
- Connect the MGen controller to the computer running indiserver with a USB cable.
- Use/adapt the provided udev rules to make sure the device is properly named in /dev. As the device is using a FTDI chip, there might be mismatches and mixups.
- Add 'indi_mgen_autoguider' to the list of drivers started by your indiserver.
- I don't remember if Ekos is providing an entry in the profile drop-down, but when INDI is started there, the MGen driver should appear in its own tab.
- Don't connect the MGen driver, but change the default device path and save your configuration.
- Start the MGen driver, the device should turn on automatically, and a few logs should appear in the MGen tab.
- Go to tab "Remote UI", and enable the remote view. Frames will pop up in the FITS viewer, and you may navigate in the interface using the buttons in the same panel.
Depending on the speed of your network connection, you may raise the frame rate, but be aware that too many frames will kill something, either Ekos or the connection (though it's been a while since I tested the robustness). With wifi I keep this to 1/2 frame per second.
Once configured, calibrated, started, you disable the remote ui, your scope is now guiding. Also always check which CCD Ekos is trying to request frames for. You do not want the MGen frames to show up instead of your light frames
Because this is so nice but also so frustrating (you will probably have this feeling too while using the driver), I'm currently implementing the PHD2 protocol in the driver. This will allow the user to start and stop guiding via Ekos instead of manually.
-Eric