Hi all,

I got all excited when I discovered the windows version of ekos: I love the scheduler. But as I have to use Windows (because of unsupported drivers under Linux) I had to use something else until now.

I installed wINDI and Ekos and everything was fine : devices found, INDI server running. When I start Ekos, the INDI config screens are loaded, all the devices are there with their options. I can use them all as expected. But in Ekos, the mount tab is missing. I've tried all I could but didn't find a solution.

What can I do to solve this problem or diagnose it?

Thanks

probably wINDI not providing a required property for Ekos. Try to enable logging and let's see. What devices not supported under Linux?

Thanks for your quick answer. I'd really love being able to use Ekos again.

The devices that aren't properly supported are Toupcam cams (guiding and planetary) and QHY183C (I tried to get it working for a long time on a rpi3 but eventually gave up). I also had lots of problems about a year ago with my ZWO ASI120MM when ZWO messed up their drivers but it was eventually sorted.

wINDI log:
Ekos/INDI log:
I don't see any more logs.

Thanks.

Hi Jasem,

Any ideas?

Thanks.

wINDI does not provide all the standard properties expected by Ekos so there are some issues here.

Jasem, which properties are missing? Peter

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.

Hi Jasem,

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.

ascom-standards.org/Help/Platform/html/P...EquatorialSystem.htm

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

Peter

Yes you are right. I'll try to update Ekos to accept EQUATORIAL_COORD as well. Thanks for the investigation!

Thanks both very much.

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.

Hi Jasem,

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.

The mount control window has the same problem.

Thanks.

Thanks for the report.. more issues fixed now. Check later with the nightly release.

binary-factory.kde.org/job/KStars_Nightly_win32/

Wait until the nightly for today is built.