×

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

Bi-monthly release with minor bug fixes and improvements

ghoto and Nikon D810A

  • Posts: 33
  • Thank you received: 0
Thanks, Jasem.
I uninstall gphoto2 2.5.4 and install ver. 2.5.12, which works fine for D7100. I'm now out so I'll check it with my D810A later. I hope it works with the newer cameras.
7 years 1 day ago #15735

Please Log in or Create an account to join the conversation.

  • Posts: 33
  • Thank you received: 0
After intalled gphoto2 2.5.11, I checked it works fine with D810A by CLI.
I installed the gphoto2 by use of the script on
github.com/gonzalo/gphoto2-updater
which installs the ghpoto2 binaries under /usr/local/lib and /usr/local/bin.
Since I cannot start INDI from the Ekos, so try to execute "indiserver -m 100 -v indi_nikon_ccd" which returns the following:
2017-03-28T13:37:53: startup: indiserver -m 100 -v indi_nikon_ccd 
2017-03-28T13:37:53: Driver indi_nikon_ccd: pid=7558 rfd=3 wfd=6 efd=7
2017-03-28T13:37:53: listening to port 7624 on fd 4
Child process 7558 died
2017-03-28T13:37:53: Driver indi_nikon_ccd: indi_nikon_ccd: error while loading shared libraries: libgphoto2_port.so.10: cannot open shared object file: No such file or directory
2017-03-28T13:37:53: Driver indi_nikon_ccd: stdin EOF
2017-03-28T13:37:53: Driver indi_nikon_ccd: restart #1
2017-03-28T13:37:53: Driver indi_nikon_ccd: pid=7559 rfd=0 wfd=6 efd=7
2017-03-28T13:37:53: Driver indi_nikon_ccd: indi_nikon_ccd: error while loading shared libraries: libgphoto2_port.so.10: cannot open shared object file: No such file or directory
2017-03-28T13:37:53: Driver indi_nikon_ccd: stderr EOF
2017-03-28T13:37:53: Driver indi_nikon_ccd: restart #2
2017-03-28T13:37:53: Driver indi_nikon_ccd: pid=7560 rfd=0 wfd=6 efd=7
Child process 7559 died
2017-03-28T13:37:53: select(8): Interrupted system call
2017-03-28T13:37:53: good bye

The indiserver crashed because failed to find libgphoto2_port.so.10 and the new ghpoto2 package does not contain it but /usr/local/lib/libgphoto2_port.so.12 and libgphoto2_port.so which is a symbolic link to the former.
To solve this issue, must I build the indi_gphoto or the whole indiserver from the source?
If so, how can I do that on RPi3?
7 years 1 day ago #15750

Please Log in or Create an account to join the conversation.

  • Posts: 33
  • Thank you received: 0
Some progress today, but still cannot control D810A from kstars/Ekos.
I removed the " Daily INDI Library for Raspberry PI 1.4.1" together with its dependencies, then re-install the gphoto2 with the update script. After that, I build and install the INDI server 1.4.1 and 3rd party drivers from the source.

Now I can control D5300, which was not supported by the old gphoto2 2.5.4, just as the old Nikon DSLR such as D7100 and D800E. However, D810A still crashes on my push of the setting button in the INDI control panel as shown in the SS on my first post.
What is strange is that the indicator turned into yellow after I set the image info or save the config. but the generated xml file recorded the configuration. Below is the first several lines of that xml.
<INDIDriver>
<newTextVector device='Nikon DSLR DSC D810A' name='DEVICE_PORT'>
  <oneText name='PORT'>
 
  </oneText>
</newTextVector>
<newNumberVector device='Nikon DSLR DSC D810A' name='CCD_INFO'>
  <oneNumber name='CCD_MAX_X'>
      7360
  </oneNumber>
  <oneNumber name='CCD_MAX_Y'>
      4912
  </oneNumber>
  <oneNumber name='CCD_PIXEL_SIZE'>
      4.8800001144409179688
  </oneNumber>
  <oneNumber name='CCD_PIXEL_SIZE_X'>
      4.8800001144409179688
  </oneNumber>
  <oneNumber name='CCD_PIXEL_SIZE_Y'>
      4.8800001144409179688
  </oneNumber>
  <oneNumber name='CCD_BITSPERPIXEL'>
      8
  </oneNumber>
</newNumberVector>
<newSwitchVector device='Nikon DSLR DSC D810A' name='DEBUG'>
  <oneSwitch name='ENABLE'>
      Off
  </oneSwitch>
  <oneSwitch name='DISABLE'>
      On
  </oneSwitch>
</newSwitchVector>

After that, I push "Disconnect", but nothing occurs and still the INDI server is running.
After rebooting the RPi, when I start INDI, the config is not loaded and behavior of the INDI control pane is the same as before.
I did some command control of gphoto2 on the RPi but nothing different from D5300 occurred, and the output of "indiserver -m 100 -v indi_nikon_ccd" returns the same as D5300. Attached is the log of the Ekos after the INDI started to I pushed "Disconnect".

Any suggestion will be appreciated.
7 years 3 hours ago #15801
Attachments:

Please Log in or Create an account to join the conversation.

Replied by Jasem Mutlaq on topic ghoto and Nikon D810A

The KStars log appear normal. Assuming you built your INDI sources using -DCMAKE_BUILD_TYPE=Debug, please debug as following:
gdb --eval-command="set follow-fork-mode child" --args indiserver -v indi_gphoto_ccd

Then connect to it from KStars/Ekos until driver crashes, go back to terminal and type bt to get backtrace and post it.
7 years 2 hours ago #15804

Please Log in or Create an account to join the conversation.

  • Posts: 33
  • Thank you received: 0
Thanks Jasem.
I've built the indiserver following the README.md contained in the source distribution, hence the "-DCMAKE_BUILD_TYPE=Debug" was on.
As you suggested, I ran gdb with the option and opened kstars, started INDI and tried to set some parameters to see the yellow indicator. The type "bt" after (gdb) and the returned is "No stack."

After I saw the yellow indicator, I started the INDI Web manager to turn on and off the indiserver. I could do that, and when I turned off the indiserver, the kstars reported "Sever disconnected". After that, I can start INDI in kstars, but the behavior was the same as before.

Any other way to pin down what causes this issue?
7 years 2 hours ago #15805

Please Log in or Create an account to join the conversation.

Replied by Jasem Mutlaq on topic ghoto and Nikon D810A

gdb should tell you if the driver crashes. You can only do bt once it crashes, not before. It the driver is not crashing then the problem is elsewhere. At one point exactly the driver gets stuck? Can you write all the steps down so I can try to reproduce?
7 years 1 hour ago #15809

Please Log in or Create an account to join the conversation.

  • Posts: 33
  • Thank you received: 0
I did 'bt' each time after I found the yellow indicator. I thought that the driver has not crashed, so tried to turn on and off with the web manager, after seeing the yellow.
What I did is as follows:
1. Start INDI with a profile which registers the Nikon DSLR or GPhoto CCD as the CCD. The server is remote and both "Auto Connect" and "Web Manager" are checked.
2. Then the INDI control panel appears. It seems to be connected to the camera, but the image setting (resolution of the sensor) was not reflected to the panel, while it is in the config xml (I attached it.)
3. Pushing ANY one of the buttons in the INDI control panel turns the indicator into yellow.
4. Both after and before I see the yellow, "Disconnect" in the Ekos panel didn't work, that is, "Stop INDI" is still grayed out.

I tested with D810A, D800E, D5300 and D7100, and only D810A behaves like above. Of course, D5300 didn't work, before I installed the new gphoto2 (2.5.11) and built the indiserver 1.4.1.
7 years 1 hour ago #15811
Attachments:

Please Log in or Create an account to join the conversation.

Replied by Jasem Mutlaq on topic ghoto and Nikon D810A

I just tested with my Canon and no issues. Is there SSH on the Pi? If so, please send me details for access so I can remotely debug the driver.
6 years 11 months ago #15818

Please Log in or Create an account to join the conversation.

  • Posts: 33
  • Thank you received: 0
Yes, sshd is running on my RPi. I've left a message on remote login to you.
6 years 11 months ago #15859

Please Log in or Create an account to join the conversation.

  • Posts: 33
  • Thank you received: 0
Hello Jasem,

After you explored my RPi, I tried different combo with the D810A and saw different behaviors from each. I got another microSD card, on which installed the latest Ubuntu Mate for RPi and the indi-full and kstars-bleeding packages as well as the tightvncserver.

1. indiserver on RPi and kstars on Mac
In contrast to the case of the raspbian where I saw the Indi control panel, even the driver seemed not to start and showed the dialog attached.
I found 2 different logs, which are attached (remote_log_D810A_1.txt and remote_log_D810A_2.txt)

2. indiserver and kstars on RPI
In this case, gphoto started but could not recognize D810A. (see local_RPi_log_D810A.txt)
Is the gphoto2 contained the repository older than 2.5.9? (D810A is supported in ver. >= 2.5.9.)

3. kstars 2.7.6 on Mac
Does not work for any my Nikon DSLR as before. (local_Mac_log_D800E.txt)

How about the progress on this issue?
6 years 11 months ago #16212

Please Log in or Create an account to join the conversation.

Replied by Jasem Mutlaq on topic ghoto and Nikon D810A

I think we should have an updated INDI for Mac release that should fix the GPhoto2 library linking issue soon. For the previous issue, it was an odd somewhat complex issue that occurs when loading properties at startup. Anyway, one way to _test_ this is to disable automatic load of configuration. In KStars, go to Ekos option and set "Load Device Configuration" to Never. Afterwards, try connecting to your Nikon on RPI3 and see if that makes any difference.

Will check with Robert on the Mac release issues.
The following user(s) said Thank You: Koichi Funakubo
6 years 11 months ago #16216

Please Log in or Create an account to join the conversation.

  • Posts: 33
  • Thank you received: 0
Thanks, Jasem.
I did the test following your advise, start INDI with the Ekos option "Load Device Configuration" being "Never".
The D800E works fine in this case and the config can be successfully loaded pushing Load in the INDI control panel. Then stopped the INDI, connected D810A in place of D800E, and started INDI. The control panel appeared and I pushed "Save" the config, and got the yellow as before. After that, any pushing button did not do anything even Disconnect. In the .indi directory on RPI3, there is the config file "Nikon DSLR DSC D810A_config.xml", which seems so natual. After quit and restart the kstars, both D800E and D810A cannot be connected.
I checked on the RPi3 by lsusb and gphoto2 --status that both the cameras are recognized by the RPi3.
Then I rebooted it and started the kstars on Mac. First, I connected the D800E and got the first log. Then stop the INDI and connect the D810A, then start the INDI again. The control panel appeared as before, and I pushed "Load" config and got the yellow again.
After that, all the behaviors are the same. Then I again connected the D800E and restarted the kstars and INDI to get the third log which shows faulty to connect the camera.

The loading config after start of the INDI gave no improvement. I'll have to wait you solve this problem.
6 years 11 months ago #16219
Attachments:

Please Log in or Create an account to join the conversation.

Time to create page: 0.300 seconds