Another "Can not open camera: Power OK?" reason : Gnome got in the way by automounting the camera on detection.
This default gnome behaviour can be disabled by :
Ideally the INDI driver shows more info on why it cannot open the camera. Something like a check with lsusb for the usb port and a grep of lsof for that device which shows to the user wtf is going on; what other process has already opened this camera device.

-- Hans

Error messages like "unable to download/read image" or strange errors in reading or downloading images might be related to memory card in camera being full or fragmented. Formatting the memory card might help,

Magnus

My setup :
canon 6d II via usb//RPi /gphoto/Indi/Ekos-Kstars -

in a session/sequence, is there a simple way not to receive the pix on the RPi?
the remote/client option still assumes that either the Indi server of the Ekos client receives the FITS/native image from the camera. In my case both are on the same machine (RPi). So somehow the image gets onto my RP. I understand this is needed for the astrometry and/or focusing but storing all files fills up the precious little space i have on the RPi .

thanks

Of course, after filming the photo save in the RPI, and automatically downloads to your pc, in the dslr sequence platform there is a local, remote or both, choose both, and give a link to save for each one, on the RPI and for PC

thanks but in that case will the file still not reside on the Pi? i want to save space really. Reading "both" seems to double the disk space required. Am i getting this wrong?

Yes, but the problem is that when you take photo, it saved automatically in stellarmate, and than it will download the file to the PC and than you can delete it, or by pressing remote it will delete it automatically, it's not recommended, mut it can be done, do both, and at home you can delete it, just put a larger SD card 32giga is more then enough.
Good luck mate

i have been working with Marcus Meissner to include Panasonic Lumix cameras in libgphoto2 over wifi/http. (github.com/gphoto/libgphoto2/tree/lumix) this is starting to work well form gphoto2 CLI however the --auto-detect option is not yet avail since libgphoto does need the IP address of the camera to connect to it. so at the moment the CLI options for gphoto2 are:
Is there a way to configure the indi gphoto driver to include these options at startup instead of relying on the --auto-detect?

Thanks

Thank you for your work! Please check out gphoto_open function and see how we can use libgphoto2 to communicate over IP instead of USB. Maybe we can reuse the? That is, we detect if the value in there is an IP address (either ipv4 or ipv6) and then make the appropriate call for libgphoto2.

Hi Jaseem,

it has been a while since i looked at the code. work got in the way...
Anyway i did install the dev stack of indi and 3rdparty drivers in order to see what can be done with the gphoto_open as you suggested. however I am not sure how much of the args are passed and i cannot make much sense of some of what is happening...

for instance:
1)returns
this would lead me to believe that a port "ip:192.168.1.12" in the config panel should be passed on correctly to the driver but i cannot get it to pass .

2) i cannot see howcan be passed as an arg to the driver.
3) also i do not get how gphoto_ccd and gphoto_driver are connected.
4) i tried to create lumix entry in the indi_gphoto_xml.cmake which does appear correctly on the ksars camera menu but fails at launch.
5) it seems that none of the attempts i made in modding the gphoto_open led to any consideration in the execution almost as if the original driver was called but i did change the target from /usr/local to /usr/ ...

anyway long one to ask for you to look at this probably simple feat for you but quite complex for me. I would be quite keen to go back and forth with you if you cannot test the actual driver against the lumix cameras...

Thanks in advance

Robert

Hello Robert,

The process is more involved than that. Edit line 1579 in gphoto_driver.cpp and change it to something like this:
or make that "ptpip:192.168.1.12" .. then compile and install. Then run the indi_gphoto_ccd driver and put a break point at that link (#1579) and press Connect in the driver. It should take you there. See if the rest of the code works fine or if returns any error.

If it is indeed as simple as this, then we can add an IP address property to the driver and if non-empty then we use it there.

Hello fellow community

I know this is an old thread, but I just landed here searching for my problem.

If anyone is having problems taking images with a Nikon Z-series, and restarting everything does not help, there is a nice little detail about the mirrorless Nikons. When you unplug the power while the camera is on, the camera closes the mechanical front curtain (I have an external power-supply instead of the battery). The front curtain stays closed after the next power-on until you manually press the release button on the camera. While the mechanical shutter is closed the camera will not take any pictures or open the front curtain from software commands. You only recognize this in EKOS from capture errors and permanent retries.

A nice side effect is, that you protect your sensor from dust when you unplug the power after an imaging session

I have big problems with Indi-canon, when I connect the 1300D everything is fine, but the configuration of the bits and pixels is wrong.
Here's what comes out..