Sorry, my intention was not to hurt you.
I still thank you for your proposal.
I'm going to install a Windows VM to recover the firmware ...
I know, but if I use INDI it is precisely because I do not have (and I do not want) Windows at home
I recompiled version 1.8.5 and it works almost perfectly.
Some problems with the current values, but this must be due to my old firmware version which I cannot update because Pegasus does not provide its firmware on its site
I have 2 questions.
Is there a known problem with the PowerBox V2 under Fedora 31?
Whether through KStars / EKOS or directly in Python through PyIndi, the symptom is the same: at the end of the 1st polling period (I tried a minute for testing) the client receives a "newDevice" followed by 'a disconnection. In addition with Kstars the app is friezed.
For information I installed the latest versions of Kstars (3.4.2) and libindi-bleeding (1.8.1).
Finally is there a particular reason why the different versions of libindi from the lupinix repository are always for 1.8.1 while the last version is in 1.8.5?
It works very well in USB
Sorry for the bad translation, I meant "capture" or "frame".
I have just collected the images of this night, and all have passed without problem
The only difference: I gave an old USB cable.
I had indeed changed both camera and USB cable. It is obviously my USB cable which is defective.
The incident is closed.
I did not understand the reasons for the crash of kstars only during my catches of flats, but not with lights.
I finally found the cause.
I left the histogram window displayed to see the effect of setting my flat box. Systematically kstars planted after 3 or 4 photos.
All I need to do is close the histogram window with each test, and then I can chain a series of flats without any problem.
With a setup consisting of an ASI1600 main camera and an ASI178 secondary camera, no way to achieve more than thirty poses without arriving at an infinite loop of a given pose.
A stop, then immediate recovery causes a new looping from the first pose.
However, if I stop the ASI178, and I restart my series, then I see no problem.
This is obviously related to the cohabitation between the 2 cameras ZWO.
Indeed with a setup consisting of an SX694 and the ASI178 I have no problem.
Same with the ASI1600 alone without the ASI178.
My raw images taken in SII with an exposure time of 60 "have a very low signal. When I calibrated them with my old master bias the result was catastrophic.
Indeed I had made this one with INDI but in LIGHT mode and not BIAS. Result, even with an exposure time of 0.001 secs, in reality the exposure was of the order of 1 sec.
I have just done a bias, but in BIAS mode, and this time actually no matter how long it takes, I see in the FITS header a duration of 0.0001 sec.
So I have calibrated my images again with this new bias, and this time I have a correct result.
The error came from the fact that I had forgotten to check the box BIAS
Thank you very much Peter
Thank you for the idea, but the locale is ok.
The duration is well taken into account with my ASI178MM, and the bias obtained with this last camera are correct.
I can not make bias with the SX694.
Whether it's in 1 second or 1/1000 second, the picture is the same, with a much too high background level.
With no Windows PC I can not use the software provided by Starlight to generate my bias ...
Is it a driver or configuration problem?
I have the same WCS problem, but this is an error and not a warning.
Curiously the first 2 captures of the PA process work.
It is during the third capture that the error message appears.
I tried with astrometric resolution online, but the problem persists.