Peter Sütterlin replied to the topic 'ASI1600 and GPSStartline' in the forum. 5 months ago

OK, some more info.

The GPSStartLine variable is from the libASICamera2 library. Grep-ing for it signals a match. This is with the lastest 1.31 version of libasi. The previous version I had installed was version 1.29. grep doesn't find the variable there.

I've now connected the 1600 to my laptop, removed all earlier camera configuration (.ZWO/ASIconfig.xml and .indi/ZWO CCD ASI1600MM Pro_config.xml*). Then started kstars and EKOS/INDI with a local configuration and only the ZWO camera.
As said before, it comes up with a value of 49152 for GPSStartLine (and 269 for GPSEndLine, FWIW).
I can take a preview in the capture tab that way. If I enter e different gain/offset and press preview it does still do a preview, but does NOT change gain/offset.

I then tried setting up a single-frame sequence. That one first immediately aborted, my fault. I had still refocus-on-T-change active and it wanted to focus first...
After de-activating it the sequence ran, but without changing the gain/offset to the requested values. Log shows an error
complaining that GPSStartLine has a value outside the allowed range, and obviously then doesn't continue to set parameters.
If I change it to the allowed maximum, as reported earlier the exposures will no longer finish.

Worth to note is that the maximum allowed value (3519; for both StartLine and EndLine) is the sensor height of the ASI166 minus one, which makes me think something is initialized wrong(?). Are those limits coming from the library? Or is it within INDI?

I've now downgraded libasi and indi-asi to the last working state I had, and again removed INDI and ZWO config files.
With that, everything works as expected.

Would be great if someone with an ASI1600 could verify/confirm this issue... (it seems cam-specific, at least my 2600 doesn't show those GPS* variables)

Attached is the logfile of my test session.

Read More...