The driver limits the maximum number of steps of the Prodigy to 2000 while it is capable of going up to 11000.
In other words we are forced to move 4.5mm out of the possible 25mm.
Is there a way around the problem?
I tried modifying the XML file to force a max of 11000, but it doesn't work.
Read More...
I had the same problem while going from version 1.8.1 to version 1.8.5 (bleeding under Fedora).
The "reverse" button no longer worked and the focuser used the direction opposite to that requested.
It was not EKOS (Kstars) which was in question since I had the same problem through PyIndi.
The recompiled version 1.8.5 also didn't work.
However, yesterday's git version works again.
I would not have had the idea if I had not seen this post.
Thank you very much !
Read More...
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 ...
Read More...
I know, but if I use INDI it is precisely because I do not have (and I do not want) Windows at home 
Read More...
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 
Read More...
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?
Read More...
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.
Read More...
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.
Read More...
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.
Read More...