James replied to the topic 'Indi and EKOS with Canon M3/10/100/6' in the forum. 1 year ago

A further update, yes it does work (to some extent). I'm forcing the ip address in code, just as above. Most of the basic functionality just works. However, you do have to be careful of the settings as the wrong ones will freeze the camera (Canon M10), requiring a reset of the camera, driver, and/or kstars. It's taken me a while to work out how to get it to work.

Most important is making sure "Force Bulb" is switched off (the M10 does not have bulb mode) and the "capture" setting is also switched off (I don't know what this does). Without "capture" switched off it won't do much at all, and I can't work out how to save that option.

I was hoping to add a configuration option that allows you to force the port and model, but I think I've reached my limit. Any help would be appreciated.

For the Canon M10, connection is like this:
1) From camera's playback mode menu, choose to connect to Wifi,
2) If this is the first time making the connection, choose "Connect to smartphone", "Add a Device" + pick the correct wifi network; otherwise just choose the name of the saved connection
3) Start kstars, start ekos, connect to devices.
4) If this is the first time making the connection, the Camera will ask what photos Indi is allowed access to. Select "All images".
5) If the initial connection is taking too long, Indi may show that it fails to connect, but you can just press "Connect" from the Ekos/Indi control panel.
6) The camera screen says "Use target device"
7) From the Indi gphoto_ccd control panel, check Options->Force Bulb = Off; settings->capture = Off
8) Ekos can now control the camera

A few other notes:
* I haven't worked out how to automatically scan the network for a valid camera, the smartphone apps do this automatically but gphoto2 does not. You must pass both the port (ip) and the model strings to gphoto2. The camera reports itself as "Canon EOS M10" in Windows and "Canon" via linux nmap. It has only port 49512 open.
* Initial connection can be flaky. It does work eventually but I don't know why. Once it works, the connection is saved and it is easy to reconnect the camera (at least, until its ip address changes)
* The video stream seems to work, but on closing the stream the camera reports "I/O busy" until the driver is reset.
* It takes a long time to download images and for the camera to be ready again, about 13-15 seconds. When the camera limits you to 30s shots, this REALLY adds up. I don't know if there's a way of disabling the download or allowing download to take place while capturing?

Read More...