Hi All,
I have now successfully integrated my Fuji X-T2 into INDI using the gphoto2-based driver. Exposures work successfully with Native Raw and JPEG, there are still some issues with FITS w/r to debayering. However I have found a strange behavior when I set Upload to "Local": After the image is successfully written to the local storage the driver continuous to show "downloading" for about 15 seconds before the next capture is started and the GUI is unresponsive in that period (Spinning wheel on MacOS). This becomes a problem e.g. in the polar alignment routine, because it severely affects the refresh-rate. I have created a debug logfile when that happens:
All steps above take less than 2 seconds (for a 1sec test exposure) until the "Upload complete" is written and the file appears on the local storage. The delay of about 15secs happens afterwards but nothing more is written to the log, so I have no idea what the driver is doing in that period. Furthermore it seems that after the capture, the Upload mode was automatically switched to "Client" in the INDI control panel. So this might have something to do with the problem.
I have replicated the issue on MacOs as well as on Astroberry/Debian, both with latest kstars 3.5.0 and libgphoto 2.5.26 and both with INDI Client and Server on the same machine (so actually "Local" and "Client" should not make any difference at all).
Does anyone have an idea whats going on here and how I can further debug this?
Cheers
- Uwe
The following user(s) said Thank You: Jasem Mutlaq
Good analysis! Yes, the Polar alignment routine needs the image in order to analyze it. So even if you set ti LOCAL, it is automatically set to CLIENT when there is a need to load the image and analyze it in Ekos.
That makes sense, although if INDI server and client is on the same box, there should be no need to transfer anything. And I am still trying to understand where the 15sec delay comes from. The debug log shows nothing.
It is technically transferring data between INDI and Ekos, even on the same machine. I think perhaps the delay is due to loading the image and debayering.
Thanks for the quick reply! I have started to analyze the gphoto source-code yesterday and already suspected that this happens after the return from the gphoto lib. So that probably means I need to also install the kstars source and dig deeper...
I have actually switched off the auto debayering to test, but this did not make any difference with this delay, so probably this issue is not directly connected to de-bayering. There was actually another issue with debayering the Fuji X-trans files anyway, but I decided to focus on this problem first.
Thanks, please let us know of any issues you find. Apparently, using PAA with DSLRs is quite messy at the moment due to the delay, so it's not just your issue. Any insights on why this is happening is appreciated.