Yesterday I updated my astro installation, i.e., compiled indi and kstars from git.
Since then my ASI1600 is missbehaving. Or rather, maybe kstars is.
It seems to be related to a configuration entry named GPSStartLine. I have not the foggiest idea what that is. But it's always showing up if I remove the configuration files for the 1600 in $HOME/.indi

The issue is that when starting up this variable has a value of 49152. And things work. But if I go to the indi tab of kstars, there to the 'Controls' tab of the 1600, this value is shown as current. But the value in the 'set' field is 3519. And this is the maximum value that I am allowed to enter. And if I want to set any value of another variable there, GPSStartLine gets set to those 3519.

And after that, the camera will not finish exposures anymore. The exposure counter runs down to 0.10, stays there for a second or so, and then restarts the exposure. After 3 fails I get an error...

I had tried downgrading to the previous version of both INDI and KStars, but still had this problem. So it might be already an older problem (I usually don't touch any settings of the 1600). So for now I can't change any setting of the cam without 'bricking' it

Can anyone confirm this? Where is the 3519 in kstars coming from? The xml.default file also has the 49152 in....

Read More...