Anyway, I still have issue with any park position. As preamble, everything works properly with the win+ascom conf. On rpi3 with latest kstars + indi lib, gtocp4 V.11, on the ap_exp driver.
For example, I select "park from P2", The log says
2018-05-07T15:46:40: [INFO] Site location updated to Lat 49:08:00 - Long 6:10:00
2018-05-07T15:46:40: [INFO] Mount is unparked.
2018-05-07T15:46:40: [INFO] calcParkPosition: parkPos=2 parkAlt=0.000000 parkAz=90.000000
2018-05-07T15:46:40: [INFO] Computing PARK2 position...
but kstars reports the mount on Az:0, Alt:-40:51:08. This is the same as for any park position I select, the driver reports correct alt/az but kstars reports the mount on some other position. I have double checked time and gps position. but I do not understand what's happening.
It looks like you told the driver you were unparking from the Park 2 position - is that correct?
I really recommend using the default for the unpark from location which is to have the mount assume you are unparking it from the position it was last parked in.
The option to set the unpark from location is for when things get confused and you need to start from a known position.
I can't really help much on the EKOS side of things perhaps someone might know why it would not be using the alt/az reported by the INDI driver.
have just verified that that latest build of the Astro-Physics Experimental driver fixes the problem I had with Park Positions. They are all correct for me with a CP3 and V level firmware. I did my test on a source code build under OSX. My stellarmate is still on the old code and still has the problem.