Thank you Gentlemen, turning off the sound notification does indeed solve the problem! Sorry for not thinking about this.
Just in passing, here is another non-critical issue which happens frequently with high acquisition rates. As you can see below the image file numbering scheme is quite erratic at times:
-rw-rw-r-- 1 bertin bertin 4248000 Feb 21 23:49 NGC2683_Light_0.500_secs_2018-02-21T23-49-11_1938.fits
-rw-rw-r-- 1 bertin bertin 4248000 Feb 21 23:49 NGC2683_Light_0.500_secs_2018-02-21T23-49-12_1939.fits
-rw-rw-r-- 1 bertin bertin 4248000 Feb 21 23:49 NGC2683_Light_0.500_secs_2018-02-21T23-49-13_1939.fits
-rw-rw-r-- 1 bertin bertin 4248000 Feb 21 23:49 NGC2683_Light_0.500_secs_2018-02-21T23-49-14_1940.fits
-rw-rw-r-- 1 bertin bertin 4248000 Feb 21 23:49 NGC2683_Light_0.500_secs_2018-02-21T23-49-15_1940.fits
-rw-rw-r-- 1 bertin bertin 4248000 Feb 21 23:49 NGC2683_Light_0.500_secs_2018-02-21T23-49-16_1941.fits
-rw-rw-r-- 1 bertin bertin 4248000 Feb 21 23:49 NGC2683_Light_0.500_secs_2018-02-21T23-49-17_1941.fits
-rw-rw-r-- 1 bertin bertin 4248000 Feb 21 23:49 NGC2683_Light_0.500_secs_2018-02-21T23-49-18_1942.fits
-rw-rw-r-- 1 bertin bertin 4248000 Feb 21 23:49 NGC2683_Light_0.500_secs_2018-02-21T23-49-19_1943.fits
-rw-rw-r-- 1 bertin bertin 4248000 Feb 21 23:49 NGC2683_Light_0.500_secs_2018-02-21T23-49-20_1944.fits
-rw-rw-r-- 1 bertin bertin 4248000 Feb 21 23:49 NGC2683_Light_0.500_secs_2018-02-21T23-49-21_1945.fits
-rw-rw-r-- 1 bertin bertin 4248000 Feb 21 23:49 NGC2683_Light_0.500_secs_2018-02-21T23-49-22_1945.fits
-rw-rw-r-- 1 bertin bertin 4248000 Feb 21 23:49 NGC2683_Light_0.500_secs_2018-02-21T23-49-23_1945.fits
-rw-rw-r-- 1 bertin bertin 4248000 Feb 21 23:49 NGC2683_Light_0.500_secs_2018-02-21T23-49-24_1945.fits
-rw-rw-r-- 1 bertin bertin 4248000 Feb 21 23:49 NGC2683_Light_0.500_secs_2018-02-21T23-49-25_1945.fits
-rw-rw-r-- 1 bertin bertin 4248000 Feb 21 23:49 NGC2683_Light_0.500_secs_2018-02-21T23-49-26_1945.fits
-rw-rw-r-- 1 bertin bertin 4248000 Feb 21 23:49 NGC2683_Light_0.500_secs_2018-02-21T23-49-27_1945.fitsbtw, is this forum the best place where to report and file specific bugs? I have started to dig into the code, I will try my best to help.
Thanks!
Read More...
Thanks for the tip Leonard! Here the output of ls -l /proc/29669/fd, where 29669 is the PID of kstars when running an acquisition sequence from the CCD simulator (the same happens with the ASI camera, connected remotely or not):
...
lrwx------ 1 bertin bertin 64 Feb 25 00:14 1570 -> socket:[876722]
lrwx------ 1 bertin bertin 64 Feb 25 00:14 1571 -> socket:[876723]
lrwx------ 1 bertin bertin 64 Feb 25 00:14 1572 -> socket:[871147]
lrwx------ 1 bertin bertin 64 Feb 25 00:14 1573 -> socket:[871148]
lrwx------ 1 bertin bertin 64 Feb 25 00:14 1574 -> socket:[874775]
lrwx------ 1 bertin bertin 64 Feb 25 00:14 1575 -> socket:[874776]
lrwx------ 1 bertin bertin 64 Feb 25 00:14 1576 -> socket:[875769]
lrwx------ 1 bertin bertin 64 Feb 25 00:14 1577 -> socket:[875770]
lrwx------ 1 bertin bertin 64 Feb 25 00:14 1578 -> socket:[871149]
lrwx------ 1 bertin bertin 64 Feb 25 00:14 1579 -> socket:[871150]
...And it goes on and on until I stop the acquisition. Aborting does not close the sockets, I have to quit kstars to free the descriptors. It happens only when the exposure time is about 1s or less, irrespective the raster size (the simulator takes only a few ms to generate the 128x128 rasters in this test). This is with fast looping off (I have to turn it off otherwise it creates all kinds of issues). The other processes (indiserver and indi_simulator_ccd) do not accumulate descriptors.
- Emmanuel.
Read More...
I suspected that the "Failed to save file to" in "Upload: Client" mode was due to Ekos running out of file descriptors. This seems indeed to be the case. The problem vanishes when I push the number of open file descriptors to 4096 per user (was 1024 by default on my system). Sounds like a close() is missing somewhere 
.
Read More...
OK thanks, I will try with the GIT version! Transfer time with a 4MB image is significantly less than 0.5s when writing directly to an SSD, even using CFITSIO . Well anyway for now the limiting factor seems to be the ASIGetExpStatus() issue.
btw I hope you will be able to reproduce the "Failed to save file to" bug with large sequences in the "Upload: Client" mode. In practice this is the most annoying issue with high acquisition rates.
Thanks again!
- Emmanuel.
Read More...
Are you using KStars from GIT master?
No, I am using kstars-bleeding-2.9.2-7.2. I suppose that the bleeding version is very close to a nightly build?
Read More...
No I did not. I just tried it: when it is activated, in the sequence queue one single exposure is completed and then nothing more happens for both ASI and the CCD simulator. The spinning widget still turns, and I can abort the sequence, but that's it. The first time I tried it with the simulator the whole KStars crashed immediately when I started the sequence.Btw, did you turn on "Rapid Looping" in the ASI driver or CCD Simulator? It's under Options.
Read More...
