Hi!

I'm experienceing a new strange problem here. Quite suddenly, after having taken hundreds of flats during the day, the Canon 350D starts having problems. I connect, it and take a picture, and get the message "WARNING: Could not wait for event." in the log window. After this the R-Pi freezes and I have to unplug and reboot it. I first believed this had to do with power failures, so I exchange the power connectors. And then switched USB cable, But it doesn't help. Problem seems to be intermittent, though. It was there, then disappeared and then returned when I was going to start on a long series of imaging.... Attached is a gphoto indi log from when the error happened.

Edit: I found out that the log file was quite empty. The log in the INdi console says:

2017-02-14T20:51:20: WARNING: Could not wait for event.
2017-02-14T20:51:19: WARNING: Could not wait for event.
2017-02-14T20:51:14: Exposure complete
2017-02-14T20:51:14: Reading exposure...
2017-02-14T20:51:14: Closing shutter
2017-02-14T20:51:14: Time left: 0
2017-02-14T20:51:13: Time left: 1000
2017-02-14T20:51:13: Starting 1 sec exposure
2017-02-14T20:51:13: Exposure started
2017-02-14T20:51:13: Opening remote serial shutter port: /dev/shutter ...
2017-02-14T20:51:13: Using predefined exposure time: 1 seconds
2017-02-14T20:51:13: Setting new configuration OK.
2017-02-14T20:51:13: Setting radio/menu widget shutterspeed: 16 (1)
2017-02-14T20:51:13: Best match: 1 seconds Index: 16
2017-02-14T20:51:13: Finding optimal exposure setting for 1 seconds...
2017-02-14T20:51:13: Using camera predefined exposure ranges.
2017-02-14T20:51:13: Setting new configuration OK.
2017-02-14T20:51:13: Setting radio/menu widget imageformat: 0 (RAW)
2017-02-14T20:51:13: Setting new configuration OK.
2017-02-14T20:51:13: Setting radio/menu widget iso: 13 (1600)
2017-02-14T20:51:13: Mutex locked
2017-02-14T20:51:13: Starting exposure (exptime: 1 secs, mirror lock: 0)
2017-02-14T20:50:14: Session log file /home/pi/.indi/logs/2017-02-14/indi_gphoto_ccd/indi_gphoto_ccd_20:50:02.log
2017-02-14T20:50:14: Toggle Logging Level -- Driver Debug
2017-02-14T20:50:13: Toggle Debug Level -- Driver Debug
2017-02-14T20:50:10: Debug is enabled.
2017-02-14T20:50:07: Device configuration applied.
2017-02-14T20:50:07: Loading device configuration...
2017-02-14T20:50:07: Detected Canon EOS 350D DIGITAL Model Canon EOS 350D DIGITAL.
2017-02-14T20:50:07: Canon DSLR is online.

Any assistance very warmly welcome - this effectively stops me from imaging.

Magnus

Small update: problem occurs even when connecting camera directly to laptop, with and without USB-hubs. But NOT on a laptop with older version of Indi:

$ sudo dpkg -l | grep indi-full
ii indi-full 1.3~201701171119~ubuntu16.10.1 amd64 Instrument-Neutral Device Interface library - Full INDI

Magnus

Update:

I think the problem is solved. I eperimented with a lot, different cables, different pwer sources for the camera and so on. It seemed that the problem only occurred when the shutter relase cable was attached (that is needed for exposures longer than 30 secs).

Finally, though, formatting the CF card in the camera seemed to solve the issue. (About the same time I exchanged the sd card in the raspberry for another sd card, with the exact same img written on it.) Possibly, some problem with the CF card caused problems in saving the image, for some reason freezing the raspberry.

Magnus