Hi. Thank you for your feedback.
For your parameter settings, go to the AVALON forum on the AVALON homepage.
The StarGO2 controller is a Raspberry Pi4 computer with INDI or ASCOM based drivers and controllers. Completely different to the classical StarGO interface and software.
Since the SG2 is INDI-based, I can adjust any parameter in the native SG2 INDI driver via EKOS or iINDI. The actual problem is, that both the ASIAIR and the SG2 are INDI severs. The ASIAIR software does not seem to be able to communicate with a second INDI server, while it is expecting an INDI client. This would be possible when using so called chained INDI servers. ZWO and ASIAIR do not support this configuration.
The only INDI driver that seems to be working in this configuration is the LX200 BASIC driver on the ASIAIR. This driver does not seem to provide/include guiding or slewing commands. Therefore, guiding is not possible.
I have been successfully using PHD2 from another computer for guiding. PHD2 accepts remote INDI servers.
If ZWO would accept and allow chained INDI servers, they would potentially “loose” their proprietary support of only ASI-based hardware. Because another INDI server could allow any hardware. This is a support nightmare for ZWO, obviously. I think, however, ZWO should make exceptions for remote INDI-based mount controllers. There are not many out there, so it is probably not on top of their to-do list.