No news unfortunately
would be great if we could just start and stop the MGEN

The USB connection seems to provide a view on the controller screen, and a way to depress controls.
With the eventual capability to exchange configuration files with the MGen, it might be possible to automate some procedures.
And this would probably also give access to the APN shutter control, along with the nice random offset feature.
But there are still many ifs (and I need to push other changes related to v4l2, it's been a long time since I could test with clear skies here).
-Eric

Well, that does sound promising...
If I can be of any help in testing or otherwise, please let me know

Hi There,

MGEN with INDI - control would be great. The MGEN is IMHO the best device for standalone guiding. Lacerta did help those astrel guys to let their cam trigger MGEN's dithering. I just asked Lacerta "... if they can provide protocol for control or any API/SDK that would help.." like Jasem suggested.
It's Christmastime so they might be very busy now...

Andreas

This was fast,

so they aren't that busy. Here is what Tommy of Lacerta wrote:

hallo Andreas,

ja wir liefern gern das Protokoll für die Kommunikation über den USB Port,
--yes we provide the protocol for communication over USB port
und freuen uns wenn sich jemand bereit findet eine INDI Implikation zu machen.
--and we are happy if someone likes to do a INDI implication
Ich hänge das pdf mit den Protokoll Infos hier an, und hoffe daß es weiter hilft.
--I'm attaching the pdf with the protocols and hope it is helping

Ich bin mit Andrea Ricciardi von Astrel in Kontakt und weiß dass er eine komplette INDI Lösung
--I'm in contact with Andrea Ricciardi of Astrel and I know that he wants to get a complete INDI solution
über das TinyAstro OS an bord der Astel anstrebt. Der MGEN erhält jetzt den Trigger zum Dithern
--over the TinyAstro OS on bord the Astrel(Cam). The MGEN gets the trigger for dithering now
und meldet das vollzogene Dithern an die Astrel zurück - funzt tadellosest.
--and states back to astrel when dithering is finished - works great.

Mit iAstrohub funktioniert der MGEn inzwishen auch schon in entsprechender Weise.
--With iAstrohub the MGEN works accordingly
Bitte mich auf dem Laufenden halten, bzw wenn weiterführende Info nötig ist dann verbinde ich mit unserem MGEN Entwickler.
--Please keep me up to date, if further information is necessary I'll connect to our MGEN developer.

lg Tommy

EDIT: File was removed due to request from MGEN. Jasem

double post, deleted

thanks Jasem

@ all: Developers are warmly welcome to contact us at shop-wien(...)teleskop-austria.at
to get MGEN's USB communication protocol. We just don't want have posted it open on the net.

clear skies, Tommy

Understood! That's the reason I couldn't find that documentation again when I saw it earlier this year... I'm interested in giving this a try, Tommy, how should we proceed? You want to review source code after it is tested and before it is pushed?
-Eric

EDIT: I also received the document, thanks Here's what I'll possibly try (after pushing the other V4L2 activity I'm currently working out):

- Step 1: hello-firmware indi driver with basic informative gadgets, connect/disconnect and link robustness management
- Step 2: remote user interface navigation, eventually with retrieval of the interface frames as remote screen
- Step 3: automated user interface navigation (locked to specific firmware version) to build scenarii to functions such as star detection, calibration and guiding
- Step 4: bonus time, such as dithering or external exposure control, or fiddling with storage configuration files

Obviously, no attempt to manage firmware upgrades at all. No promises on how long this will take, of course
-Eric

Hello,

I've got the rough edges of the driver sorted out thanks to the documentation
Right now I have a stable driver maintaining a robust connection, reading versions, voltage levels, and user interface frames.

However, how should I proceed to provide that user interface to the end-user?
I was looking for a way to display a raw black&white image in the driver interface, but I don't see any.
Do I need to develop a new panel in Ekos or is there another way to do this?

Thanks,
-Eric

Sorry I'm not following. Why do you need a specific user interface for this driver?

Ah, sorry for being opaque... Let me clarify.

The MGen is an autoguider, with a CCD and a ST4 connector. The interface to the CCD is connected to a command block, which has a LCD user interface with a few buttons. Roughly the procedure to start guiding is always the same:
1. Turn the device on and access the main menu
2. Find the best suited star in the current live view
3. Calibrate the guider by letting it compute drifts
4. Start guiding, and stop guiding

I've been looking into which INDI:: interfaces are best suited for each step using the device (CCD, Guider...), but that's not my point yet.

There are I/Os to transfer the contents of LCD user interface to the computer, and button states back to the command block (their PC application provides this feature).
As a first step in remote control, I'm looking for a way to reproduce that LCD user interface for the end-user.
Should I develop an external script with its own user interface, or is there a way to embed that more generically in an INDI client?

Thanks,
-Eric

Since this appears to be specialized functions for the device, I suggest you develop a client for it specifically. Not sure how you can use INDI there since everything operates within the device? Can you send external guiding commands to it? You probably need a new INDI:: interface for such a device, or a mesh-up for existing INDI device classes.