Peter, just doubled checked. The wINDI driver send EQUATORI_COORD which are J2000 coordinates, but Ekos only accepts EQUATORIAL_EOD_COORD. I guess you can say Ekos does not support _all_ the properties, but I also think the ASCOM mounts are probably reporting JNow and not J2000 as well.
you're right. wINDI reports EQUATORIAL_COORD or EQUATORIAL_EOD_COORD depending on equatorial system reported by ASCOM. In case of equLocalTopocentric it uses EQUATORIAL_EOD_COORD in other cases (the most probably equJ2000, other choices are quite outdated) it uses EQUATORIAL_COORD.
I don't know if it is possible to configure this particular ASCOM driver to use equLocalTopocentric instead (somewhere in setup dialog I suppose). If it is, it should help. But from API side it is readonly property and can't be changed by wINDI.
So wINDI does provide standard INDI properties, but Ekos doesn't understand them
My system is indeed entirely J2000. I find it much easier given that all standard data is in that reference system when comparing back to input data for example.
Thanks for making changes. I can now connect to my mount via ASCOM.
There is however a next issue: even though the connection screen of Ekos shows the position of the telescope, the telescope tab doesn't seem to be able to get those coordinates. So for example when you slew to a target to get things like this for that reason:
2018-08-27T23:37:56 Job 'NGC 6946' is slewing to target.
2018-08-27T23:37:56 Warning: job 'NGC 6946' found not slewing, restarting.