Wildi, Mike, Wotalota,
Wildi- definitely keep going and I look forward to when you get it working. I will continue to test and offer feedback as much as I can.
Mike - You are correct about freezing our software stack, however as Wotalota has pointed out, I too have updated the software since (see my thoughts below). I have also tried getting an earlier driver working but had problems with that (see some earlier posts on this thread).
I have also started looking at the OnStep system recently. Can you tell me what mount you are running that system on (please, pretty please)?
Sadly, my recent call to Astro-Physics just didn't go very well and any mention of open source software (INDI, KStars, etc.) was met with some hostility followed by a rant of software theft and then an argument to convince me the merits of Windows and Ascom. I have used them and know it works OK (sometimes) and like you I am done with proprietary solutions.
Wotalota - right I am in basically the same spot except for one case as follows below.
ALL - I have found that Michael Fulbright's version of the experimental driver is also broken in recent releases. I did find by luck an older SD card that works on a Pi3 (or Tinkerboard, I have to check this) that is from summer or fall of 2019 KStars version 3.3.7 that seems to work OK. To be sure I will have to setup to run some tests so as to verify the full working state of this earlier version since the later versions are not really usable and the reason why I began this post. In any case we do need a working driver until Wildi can get his work more complete and this might relax the pressure on Wildi as well.
1. The standard "Astrophysics" driver (not the Experimental Driver) - I am able to use this driver as long as I use my hand controller to initialize, however it does over wright my park position in the Parkdata xml file to all 0's.
Can that be a quick fix? I need to test further if this driver can be used successfully without the hand controller since once I got it working with the controller I just started to image my target and never got back to further testing.
2. Owing to the weather and other pressure on my time for the foreseeable future what I can do is take my mount back off the pier sometime in the coming days and setup inside for some basic testing with hopes that will help in driver development and testing.
3. The Astro-Physics Experimental driver - once a working version can be determined it would be great to be able to get this back in the INDI stack - maybe as new name such as Astro-Physics Experimental-Fulbright or some such rename. Or whatever may work? Thoughts?