It takes time to find the camera that mirror lockup works correctly.
If we have simple commands and procedures to investigate, I think many people will try it.
I will try a new build tonight.
Thank you for your information.
I understood that mirror lockup Enable/Disable is not working properly.
The operation seems to be different in some camera models.
Is there a way to disable mirror lockup?
I am worried that the camera will be damaged, as errors will show on the camera side.
I have a problem.
I am using Canon T7i (X9i).
The INDI module I am using is indi-gphoto (2.2 to 201807161307 ~ ubuntu 16.04.1).
Although 1 second capture works, can not capture longer than that (eg 2 seconds).
If the capture operation fails, all subsequent capture commands will not be accepted and capture will be impossible.
Sometimes Err 70 is displayed on the camera.
I will attach a log.
When using Canon EOS 600D, there seems to be no trouble.
Are there any advice?
I tried your advice. It worked very well!
A memory leak has not occurred.
The problem is solved with the latest nightly builds.
I checked my environment.
Cause my nightly builds automatic download script seemed to be failing.
Also, as you say, note that this problem occurs on the current stable version.
I feel the same way. I am in trouble in exactly the same situation.
If you can reproduce the problem, can you post a log?
It will surely help you to analyze the situation.
The normal log is as follows.
INFO 1001.632236 sec : Exposure done, downloading image... DEBUG 1007.745475 sec : read_libraw: raw_width: 6288 top_margin 0 left_margin 0 first_visible_pixel 0 DEBUG 1007.780411 sec : read_libraw: rawdata.sizes.width: 6288 rawdata.sizes.height 4056 memsize 51008256 bayer_pattern RGGB DEBUG 1007.900445 sec : read_libraw: memsize (51008256) naxis (2) w (6288) h (4056) bpp (16) pattern (RGGB) DEBUG 1008.470803 sec : Uploading file. Ext: fits, Size: 51013440, sendImage? Yes, saveImage? No DEBUG 1009.271505 sec : Upload complete
The error log is as follows.
INFO 1052.571810 sec : Exposure done, downloading image... ERROR 1057.966632 sec : Cannot convert /tmp/indi_V62GLb : Unsufficient memory ERROR 1057.967516 sec : Exposure failed to parse raw image.
An error is output by the read_libraw () function defined in indi-gphoto / gphoto_readimage.cpp.
Looking at the source code, the result of Libraw 's raw2image () is an error.
It is considered an error due to memory shortage, so I do not know whether there is a problem with libraw or indi_gphoto.
There is a possibility that indi_gphoto forgot to release memory.
I tracked memory usage. (ps aux command)
It is a comparison of VSZ and RSS when I capture 10 times.
Count %MEM VSZ RSS COMMAND 1 10.2 150068 96820 indi_canon_ccd 2 13.7 183432 129996 indi_canon_ccd 3 17.2 216544 163108 indi_canon_ccd 4 20.7 249664 196228 indi_canon_ccd 5 24.1 282784 229348 indi_canon_ccd 6 27.6 315916 262480 indi_canon_ccd 7 31.1 349064 295628 indi_canon_ccd 8 34.6 382224 328788 indi_canon_ccd 9 38.1 415392 361956 indi_canon_ccd 10 41.6 448560 395124 indi_canon_ccd
The memory used is increasing about 33000 kb each time it is taken.
And that memory is not freed when the capture is over.
The only way to free it is to restart the INDI server.
Thanks for your advice.
Both "Single Window Open" and "Single Preview Tab" have been checked in my setting options.
It seems that this is not the cause, as the INDI server and the KStars client are running on separate machines.
I have a problem.
I was capturing using canon T7i.
I download the captured image to the client in FITS format.
After 15 consecutive captures, KStars output the following error.
Cannot convert /tmp/indi_V62GLb : Unsufficient memory Exposure failed to parse raw image.
And capture was aborted.
When I monitor the memory consumption of the INDI server, many free memory decreases per capture.
When an error is output, the free memory of the server is almost empty.
Also, memory is not freed until the INDI server is restarted.
In order to resolve this error, it was necessary to stop the INDI server and restart it.
There were no such errors in the past.
Do you have good advice?
I am using the following. and Log.
Raspberry Pi 3
Ubuntu Mate 16.04
INDI Latest nightiy builds
KStars Latest nightiy builds
I have a same problem.
I am using MoonLite Focuser (compatible).
Camera is Canon DSLR, filter wheel is not used.
KStars is 2.9.4, INDI is 1.7.0.
KStars freezes in the middle of autofocus.
It seems to happen after several autofocus data points are gathered.
Because KStars crashed, log could not be obtained.
I try to get the log again tonight.
I'm looking forward to KStars v 2.9.4.
Can I set the exposure time in PAA refresh phase to 1 second or less?
I am using the V4L2 camera for the guide.
The exposure time of this camera can not be longer than 0.5 seconds.
In order to use with PAA, it is necessary to set the exposure time to 0.5 seconds or less in the refresh phase.
Is there any way?
I updated the INDI library. It worked well!