Hi!
A little bit of an update:
I've been experimenting with this problem, and there simply is no way that I can make the raspberry pi take an exposure with the 350D. The same camera works without problems on my laptop, running kubuntu 15.10. And the raspberry pi works nicely with a 70D, so it is not a general problem with indi or the gphoto driver, but seems specific to the 350D.
Driver indi_gphoto version 1.4, interface 10, both on laptop and on raspberry pi. (but the package in the kubuntu laptop is slightly differently named, see post above)
USB-hub or no USB-hub makes no difference.
And there is not much of a logfile produced by indi-gphoto. The only thing is this in the INDI-window:
2016-05-03T14:30:32: Driver indi_gphoto_ccd: snooping on Losmandy Gemini.EQUATORIAL_EOD_COORD
2016-05-03T14:30:32: Driver indi_gphoto_ccd: read <getProperties device='Losmandy Gemini' name='TELESCOPE_INFO'>
2016-05-03T14:30:32: Driver indi_gphoto_ccd: snooping on Losmandy Gemini.TELESCOPE_INFO
2016-05-03T14:30:32: Client 0: sending <setTextVector device="GPhoto CCD" name="ACTIVE_DE
2016-05-03T14:30:32: Driver indi_gphoto_ccd: read <getProperties device='CCD Simulator' name='FILTER_SLOT'>
2016-05-03T14:30:32: Driver indi_gphoto_ccd: read <getProperties device='CCD Simulator' name='FILTER_NAME'>
2016-05-03T14:30:32: Driver indi_gphoto_ccd: read <defTextVector device='GPhoto CCD' name='SHUTTER_PORT'>
2016-05-03T14:30:32: Client 0: queuing <defTextVector device='GPhoto CCD' name='SHUTTER_PORT'>
2016-05-03T14:30:32: Client 0: sending <defTextVector device="GPhoto CCD" name="SHUTTER_P
I note that this ends in a truncated manner, as if the driver crashes.
Anyone got any ideas on this? My May project, depending on this modified camera, seems to be in serious troubles....
Magnus
A little bit of an update:
I've been experimenting with this problem, and there simply is no way that I can make the raspberry pi take an exposure with the 350D. The same camera works without problems on my laptop, running kubuntu 15.10. And the raspberry pi works nicely with a 70D, so it is not a general problem with indi or the gphoto driver, but seems specific to the 350D.
Driver indi_gphoto version 1.4, interface 10, both on laptop and on raspberry pi. (but the package in the kubuntu laptop is slightly differently named, see post above)
USB-hub or no USB-hub makes no difference.
And there is not much of a logfile produced by indi-gphoto. The only thing is this in the INDI-window:
2016-05-03T14:30:32: Driver indi_gphoto_ccd: snooping on Losmandy Gemini.EQUATORIAL_EOD_COORD
2016-05-03T14:30:32: Driver indi_gphoto_ccd: read <getProperties device='Losmandy Gemini' name='TELESCOPE_INFO'>
2016-05-03T14:30:32: Driver indi_gphoto_ccd: snooping on Losmandy Gemini.TELESCOPE_INFO
2016-05-03T14:30:32: Client 0: sending <setTextVector device="GPhoto CCD" name="ACTIVE_DE
2016-05-03T14:30:32: Driver indi_gphoto_ccd: read <getProperties device='CCD Simulator' name='FILTER_SLOT'>
2016-05-03T14:30:32: Driver indi_gphoto_ccd: read <getProperties device='CCD Simulator' name='FILTER_NAME'>
2016-05-03T14:30:32: Driver indi_gphoto_ccd: read <defTextVector device='GPhoto CCD' name='SHUTTER_PORT'>
2016-05-03T14:30:32: Client 0: queuing <defTextVector device='GPhoto CCD' name='SHUTTER_PORT'>
2016-05-03T14:30:32: Client 0: sending <defTextVector device="GPhoto CCD" name="SHUTTER_P
I note that this ends in a truncated manner, as if the driver crashes.
Anyone got any ideas on this? My May project, depending on this modified camera, seems to be in serious troubles....
Magnus