×

INDI Library v2.0.6 is Released (02 Feb 2024)

Bi-monthly release with minor bug fixes and improvements

[SOLVED] Canon 6D and indi_gphoto_ccd, errors

  • Posts: 365
  • Thank you received: 32
"Bulb mode isn't supported" is the error I get with my Canon 6D and indi_gphoto_ccd when the camera is set on manual. Might make sense, but at least I get through my scheduler for up to 30 second exposures. When I switch the camera itself to Bulb, which I hoped would solve longer exposures, it doesn't function properly. Giving me another error "Failed to set new configuration value (camera busy)", the scheduler acts weird then as well, thinking it exposes for 120 sec, starts to download, but only then the camera's shutter opens for some indefinite exposure.

Clearly the communication between the camera and the driver is having issues when switched to Bulb. I'd love to give a detailed log, but not sure where to set it for the camera..
8 years 5 months ago #5406
The topic has been locked.
  • Posts: 314
  • Thank you received: 34
My first approach would be to test the camera with gphoto2 if bulb mode works.
--= human, without Windows™ =--
pls excuse my bad english! :)
8 years 5 months ago #5421
The topic has been locked.
  • Posts: 365
  • Thank you received: 32
Good suggestion, will try that somewhat later. Now I turned on debug mode and this is what came out, does that reveal anything? I notice in the INDI setting, the only setting that makes sense to me, that the shutter release port setting in main-control is not set to anything.

Btw, the timer and stuff does count down as you can see, but the camera's shutter doesn't actually open.
2015-10-16T15:51:48: Client 0: new arrival from 192.168.178.10:50814 - welcome!
2015-10-16T15:55:19: Driver indi_gphoto_ccd: Starting exposure
2015-10-16T15:55:19: Driver indi_gphoto_ccd:   Mutex locked
2015-10-16T15:55:19: Driver indi_gphoto_ccd: looking for bulb exposure..
2015-10-16T15:55:19: Driver indi_gphoto_ccd: bulb exposure found! id:1
2015-10-16T15:55:19: Driver indi_gphoto_ccd: Using bulb mode. idx:1
2015-10-16T15:55:19: Driver indi_gphoto_ccd: Using widget:eosremoterelease
2015-10-16T15:55:19: Driver indi_gphoto_ccd: request code 0x%04x getting resp error 0x%04x
2015-10-16T15:55:19: Driver indi_gphoto_ccd: Failed to set new configuration value (camera busy), retrying...
2015-10-16T15:55:20: Driver indi_gphoto_ccd: Exposure started
2015-10-16T15:55:20: Driver indi_gphoto_ccd: Time left: 39493
2015-10-16T15:55:25: Driver indi_gphoto_ccd: Time left: 34492
2015-10-16T15:55:30: Driver indi_gphoto_ccd: Time left: 29492
2015-10-16T15:55:35: Driver indi_gphoto_ccd: Time left: 24491
2015-10-16T15:55:40: Driver indi_gphoto_ccd: Time left: 19491
2015-10-16T15:55:45: Driver indi_gphoto_ccd: Time left: 14491
2015-10-16T15:55:50: Driver indi_gphoto_ccd: Time left: 9490
2015-10-16T15:55:55: Driver indi_gphoto_ccd: Time left: 4490
2015-10-16T15:55:59: Driver indi_gphoto_ccd: Time left: 0
2015-10-16T15:55:59: Driver indi_gphoto_ccd: Closing shutter
Last edit: 8 years 5 months ago by Vincent Groenewold.
8 years 5 months ago #5452
The topic has been locked.
  • Posts: 314
  • Thank you received: 34
I don't own an 6D but if you try gphoto2 you might also have a look at this thread , maybe the issue is simmilar to "AWSBarker's" 60D problem. And from the gphoto2
homepage it it said:
--= human, without Windows™ =--
pls excuse my bad english! :)
8 years 5 months ago #5453
The topic has been locked.
  • Posts: 365
  • Thank you received: 32
Ok will try, but if that works, how should I then translate that to the indi driver?

Mmm, having trouble setting settings on Gphoto2 now, maybe this is related to my problem? I can only set things like the eosremoterelease, but no activity on the DLSR as of yet.
pi@raspberrypi ~ $ gphoto2 --set-config shutterspeed=bulb
 
*** Error ***              
The shutterspeed widget is not configurable.
*** Error (-2: 'Bad parameters') ***       
 
For debugging messages, please use the --debug option.
Debugging messages may help finding a solution to your problem.
If you intend to send any error or debug messages to the gphoto
developer mailing list <gphoto-devel@lists.sourceforge.net>, please run
gphoto2 as follows:
 
    env LANG=C gphoto2 --debug --debug-logfile=my-logfile.txt --set-config shutterspeed=bulb
 
Please make sure there is sufficient quoting around the arguments.
Last edit: 8 years 5 months ago by Vincent Groenewold.
8 years 5 months ago #5454
The topic has been locked.
  • Posts: 365
  • Thank you received: 32
Ok so now, after getting into the background of some more errors, I came across some posts suggesting to update gphoto to 2.5.x. Interestingly my Raspberry PI was up-to-date, not seeing a version after 2.4. I compiled it locally and ran it, it's able to open the shutter, but then exits with the error "Failed to set new configuration value Off for configuration entry eosremoterelease. Exactly the same problem as the indi driver has.

Edit: Ok, haha, getting to know the software better and better. It doesn't have an Off option, even though stated in the GPhoto site. So I tried a legal one, Shutterrelease Full. That seems to work! So could it be that libindi-gphoto-ccd has an arguments problem or so?
Last edit: 8 years 5 months ago by Vincent Groenewold.
8 years 5 months ago #5460
The topic has been locked.
Can you now take an image using GPhoto2 in Raspberry PI? If yes, what's the full command?
8 years 5 months ago #5462
The topic has been locked.
  • Posts: 365
  • Thank you received: 32
Yes I can, nicely downloaded the cr2 files. Full command to take a photo and release it afterwards is (ofcourse the 60 seconds is an example);

ps. the binary of 2.5.x is now in /usr/local/bin for me
gphoto2 --set-config eosremoterelease=Immediate --wait-event=60s --set-config eosremoterelease=4 --wait-event-and-download=2s
Last edit: 8 years 5 months ago by Vincent Groenewold.
8 years 5 months ago #5463
The topic has been locked.
and using the SAME command with 2.4.x does not work? Are you using Raspian Wheezy or Jessie now?
Last edit: 8 years 5 months ago by Jasem Mutlaq.
8 years 5 months ago #5465
The topic has been locked.
  • Posts: 365
  • Thank you received: 32
I actually didn't try it on the older version, I first just figured upgrading might have solved it. I switched to Jessie to install Indi 1.1.0 and after that switched back to Wheezy again.
8 years 5 months ago #5468
The topic has been locked.
Does it work with this command?
gphoto2 --set-config eosremoterelease=2 --wait-event=60s --set-config eosremoterelease=4 --wait-event-and-download=2s
8 years 5 months ago #5469
The topic has been locked.
  • Posts: 365
  • Thank you received: 32
Yes it does. Feels like it's getting somewhere. :)

At the very least I could now schedule to run a script or so.
Last edit: 8 years 5 months ago by Vincent Groenewold.
8 years 5 months ago #5470
The topic has been locked.
Time to create page: 0.271 seconds