Hi Mike,
I do not have the latest pull from source but I do have the latest PPA available (at this time) for the Raspberry Pi. I hope this will at least be of some use. I looked over this thread briefly and it seems some of the failures I had in testing may be related to the problems indicated in the thread. I have attached logs.
I know this test data may seem long but please read it all carefully as I have included test information that should help work out the bugs.
Configuration used in this test:
Raspberry Pi 3, Ubuntu Mate 16.04.03, KStars/Ekos/INDI 2.8.9 (Latest PPA as of this test due to Launchpad maintenance)
Canon Rebel XTi (400D)
FTDI USB to serial converter as TTYUSB0
Hap Griffin Serial port bulb trigger cable with LED (the LED is very useful for testing)
* Important note - this camera will expose up to 30 seconds max. A bulb cable is needed for greater than 30 seconds (same as 350D according to the specifications here):
en.wikipedia.org/wiki/Canon_EOS_350D
Canon 400D (XTi) INDI/Ekos test:
1. Turn on camera and connect to RPI3.
2. Start KStars/Ekos
3. Connect Ekos with Canon 400D only (created a profile with only the 400D)
4. Did not use the mirror lock feature yet, just testing exposure settings.
5. Began a series of exposures in Ekos as follows:
0.1 sec - worked - camera triggered
0.5 sec - worked - camera triggered
1 sec -
failed - camera hung - had to push button on camera to trigger the exposure then the image downloaded. The bulb cable also triggered at this time.
1 sec - worked - looks like both the camera is set to 1 sec and the bulb cable triggers as well
1 sec - same as above
10 sec - worked - bulb cable triggered
20 sec - worked - bulb cable triggered
30 sec - worked - bulb cable triggered
35 sec - worked - bulb cable triggered
60 sec - worked - bulb cable triggered
10 sec - worked - bulb cable triggered
1 sec - worked - bulb cable triggered (camera rear display switched from bulb to read 1” and then back to bulb after exposure completed) the bulb cable also triggered
0.5 sec-
failed - rear camera display read 0”5 but the camera did not trigger - I had to push the button to trigger the camera then the display changed back to bulb and the image downloaded.
0.5 sec - worked - camera triggered and rear display read 0”5 and the camera display changed back to bulb
0.1 sec - worked - camera triggered and rear display read 1/10 and the camera display changed back to bulb
35 sec - worked - bulb cable triggered
Turn on Mirror Lockup:
6. Disconnected from Ekos and INDI
7. Turned off camera and then back on.
8. Went into camera menu and turned on the Mirror Lockup in the settings.
9. Started Ekos and connected to camera and set the mirror lock delay in INDI to 2 seconds.
10. Began a series of exposures in Ekos as follows:
0.1 sec -
failed - mirror lock triggered but camera hung - had to push button on camera then the exposure worked and downloaded.
0.1 sec -
failed - mirror lock triggered but camera hung - had to push button on camera then the exposure worked and downloaded.
0.5 sec - worked
0.5 sec -
failed - mirror lock triggered but camera hung - had to push button on camera then the exposure worked and downloaded.
1 sec -
failed- mirror lock triggered but camera hung - had to push button on camera then the exposure worked and downloaded.
10 sec - worked - Mirror locked and after 2 seconds the camera exposed for 10 seconds and downloaded
20 sec - worked - Mirror locked and after 2 seconds the camera exposed for 20 seconds and downloaded
35 sec - worked - Mirror locked and after 2 seconds the camera exposed for 35 seconds and downloaded
60 sec - worked - Mirror locked and after 2 seconds the camera exposed for 60 seconds and downloaded
It seems that this mostly works except where exposures go below 1 second and the control goes back to the camera from the bulb cable. Some further troubleshooting will be needed to determine what causes the failures at first then they seem to work when the exposure timing is not changed (mostly true, especially if the exposure are longer than 1 sec).
I hope this is of some help to you and/or developers for the driver.