×

INDI Library v2.0.6 is Released (02 Feb 2024)

Bi-monthly release with minor bug fixes and improvements

wINDI + Ascom Eqmod + win Ekos = missing mount tab

  • Posts: 712
  • Thank you received: 174
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 :P

Peter
5 years 7 months ago #28453

Please Log in or Create an account to join the conversation.

Yes you are right. I'll try to update Ekos to accept EQUATORIAL_COORD as well. Thanks for the investigation!
5 years 7 months ago #28454

Please Log in or Create an account to join the conversation.

  • Posts: 12
  • Thank you received: 0
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.
5 years 7 months ago #28455

Please Log in or Create an account to join the conversation.

  • Posts: 12
  • Thank you received: 0
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.
5 years 7 months ago #28995

Please Log in or Create an account to join the conversation.

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.
Last edit: 5 years 7 months ago by Jasem Mutlaq.
5 years 7 months ago #29001

Please Log in or Create an account to join the conversation.

  • Posts: 12
  • Thank you received: 0
Thanks Jasem. I'm happy to test. I really like the way Ekos works and I'd like to be able to use it with my hardware. It was close last night.
5 years 7 months ago #29002

Please Log in or Create an account to join the conversation.

  • Posts: 12
  • Thank you received: 0
Hi Jasem,

I confirm that in builds 171 and later the mount tab can now read the mount's position. Thanks for the fix.

The bad news is that the plate solve tab doesn't seem to be able to.

Thanks.
5 years 6 months ago #29095

Please Log in or Create an account to join the conversation.

Just fixed that, so hopefully tonight build will fix your issue.
The following user(s) said Thank You: Cedric
5 years 6 months ago #29098

Please Log in or Create an account to join the conversation.

  • Posts: 12
  • Thank you received: 0
Great! Thanks. I should have a night of testing tonight. I'll feedback tomorrow.
5 years 6 months ago #29099

Please Log in or Create an account to join the conversation.

  • Posts: 12
  • Thank you received: 0
Hi Jasem,

Here are my findings for tonight with build #174:
- the plate solve tab now has access to mount position.
- when trying to solve a position, the position gets further and further from the target after each solve (I used astrometry, Ekos seems to confuse and crash ansvr) . Essentially if you have a maximum distance from target set, you'll never get there. A single solve and sync works fine. A conflict between the adapting mount model in Eqmod and some internal Ekos model maybe? (I used Eqmod on dialog, so only the last sync values are kept)
- when you change the astrometry server (e.g. In my case from astrometry to ansvr and back), Ekos doesn't try to authenticate after the server change. So if you use ansvr, changing to astrometry fails because Ekos uses the ansvr session id in the API requests. Changing from astrometry to ansvr works because ansvr doesn't actually care about user and session id.
- when slewing from a scheduled plan, the slewing is extremely slow. Looking at the Ascom commands, it appears that Ekos doesn't wait for the goto to finish. It sends the same slew order over and over again every second or so. As a result, the mount slew is interrupted every second and starts again. The one slew I tried took several minutes. A slew from kstars works as expected though.

Thanks.
Last edit: 5 years 6 months ago by Cedric.
5 years 6 months ago #29141

Please Log in or Create an account to join the conversation.

  • Posts: 12
  • Thank you received: 0
FYI, I experimented with INDI for Windows used from Ekos in a Linux VM last night (hadn't thought of doing that before) and the slewing problem is there too.
(using ekos nightly since the mount position issue exists in bleeding)
Last edit: 5 years 6 months ago by Cedric.
5 years 6 months ago #29278

Please Log in or Create an account to join the conversation.

  • Posts: 12
  • Thank you received: 0
Jasem, do you want me to report those as bugs somewhere?

Thanks.
Last edit: 5 years 6 months ago by Cedric.
5 years 6 months ago #29468

Please Log in or Create an account to join the conversation.

Time to create page: 2.046 seconds