3rd-party drivers such as the ASI driver depend on the main INDI libraries and need to be recompiled when the base library is updated. If you get your INDI from PPA, the packages occasionally fall out of sync and get eventually fixed when recompiled. If you compile everything yourself, just compile and install the main INDI library first (and make sure you don't have old copies left over in the system) and then compile the 3rd party drivers against that version.
Read More...
I just uploaded a pull request to update ASI Camera SDK to 1.32 which was released yesterday. I finally also found the change log for previous versions and it seems that camera should have been supported already with the 1.31 version, which is the current version in INDI repository. In any case, help is on the way hopefully 
Read More...
Use PHD2 with my EQ8 and have the setting off, there doesn't seem to be anything needed to reuse the calibration on either side of the pier.
Read More...
There are actually two values that define the maximum range that is available, one is in INDI, which is the one you see as "Max. Position" setting, and then the firmware limit, which is used to define the range for the control. It's possible that the "Max. Position" has been saved from earlier and doesn't automatically increase, but the range you can set it to should, at least it did for me after updating the firmware and going over 60000 worked, though my focuser doesn't allow for much more than that. As for the relative position behavior, have to check that it doesn't have some other issue, I usually don't use it for anything myself, just the absolute position.
Read More...
You need to update libasi before compiling as it updates the EAF library to have this function. It's also included in the 3rd-party repo.
Read More...
This has been implemented in the current EAF driver version which queries the available step range from the EAF SDK and does support the extend the range in the new firmware. It should be included in INDI 2.0.1 release already, but requires update in Astroberry.
Read More...
I don't see any fundamental reason why it would not, but it also requires version of INDI with XISF plugin and drivers compiled against that version (no changes required in the driver as such, it's handled by the INDI camera base class). If there is nothing meaningful in the logs, it's worth checking that you have libindixisf.so plugin installed and so on.
Read More...
One thing to check is if the mount is using sidereal tracking rate, I once had lunar tracking rate enabled by accident as I had images Moon earlier and then moved to deep sky objects.
Read More...
It comes from the base INDI::Dome class which does it automatically, currently there is no option to turn it off without editing that.
Read More...