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...

Very nice work! Did a quick test and didn't notice any problems. After enabling compression from INDI control panel the files were roughly half size which is quite welcome PixInsight was happy with the files so no complaints from me.

Read More...

If you have the older 12V model of EAF, it requires 12V power connected to be visible to the computer. The newer 5V USB power only version does not need that.

Read More...

Good to hear, let's hope everything works that way! I don't have much free time at the moment but I'll try to upgrade my controller to the same firmware version and reproduce the problem at some point if I could fix the problem or at least understand what causes it and maybe work around it in some way. Thanks for your testing, logs and reports!

Read More...

Actually I just now noticed that you have newer firmware (6.1) in your controller than what I used for testing originally (5.3, 5.4 and 5.7). Checking the Windows driver release notes there seems to be some issues with the connection too and they have increased the status query rate to every second for that reason, but that was the default in INDI driver already. You can try to play with the polling period setting, but I'm not too hopeful. It's currently also limited to once every 1-3s.

There is a hardware watchdog that resets the controller if it doesn't receive commands from ethernet for some time, so if that is on for some reason, that might cause this resetting thing even if the controller receives commands from serial port. The watchdog can be disabled with the Windows driver I think or by connecting to the serial port with some serial communication program like Minicom or Arduino IDE and sending command setEthWatchdog=0

Read More...