×

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

Bi-monthly release with minor bug fixes and improvements

Driver OnStep (LX200 like) for INDI

  • Posts: 322
  • Thank you received: 31
I did test the Mount Model change in OnStep with a real controller (although it is still on a breadboard) and indoors (working on a PCB for STM32, so still a few weeks away). The workflow did what I intended it to do.

But it still needs someone to test it under the stars to see if the alignment really made a difference in Goto accuracy after Mount Model.
5 years 8 months ago #27761

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

  • Posts: 174
  • Thank you received: 27
I am currently using azwing's private INDI branch for running my system because with the code in the main branch KStars does not see ONstep focuser. I was wondering when this branch will be merged into main branch? Do we need to do more testing? I can help with this.

Alex.
5 years 8 months ago #27765

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

  • Posts: 452
  • Thank you received: 71
Alex,
To answer your question, yes any help is wellcome.
Concerning a release of the current work it is not likely to happen in the immediate furure but i hope before the end of this year.

My fork is not ready for a release in the master branch for many reasons:
In my opinion the stable version should:
- have no known bugs
- run with an identified Onstep firmware version (preferably the stable one)
- be documented (see github.com/azwing/Kicad_OnStep/blob/mast..._Indi_Driver_Doc.odt)
- all functions should have been tested in real situation
this is not the case of the fork for now.
I think users that download an official version should get something functional, not experimental.

@ Khalid, unfortunately I am in the same situation, no hardware to test in real situation for the time beeing.
5 years 8 months ago #27794

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

  • Posts: 257
  • Thank you received: 22
Total agreement on stable releases vs. testing. As per a discussion at Jasem's git, making a testing branch might be helpful..but we'll need to call something stable to do that. :P
Still raining here.
Last edit: 5 years 8 months ago by Ray Wells.
5 years 8 months ago #27796

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

  • Posts: 452
  • Thank you received: 71
@ Blueshawk.

Can you borrow me some rain ... we are drying out here goo.gl/maps/drZe72NoPKD2
No rain but a lot of clouds.

For me 3stabel" was the already released
Testing the current fork
Development any for tof testing (e.g James's fork)

lets wait james and Khalid to give their idea on this.
5 years 8 months ago #27802

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

  • Posts: 322
  • Thank you received: 31
For me, I always use the stable KStars and INDI versions from Jasem's PPA.

For OnStep, I use the Alpha, since it is the one that has the STM32 port I am working on (low cost, good performance tradeoff).

For the Align code that allows 'Mount Model' in Ekos, no new version of Ekos is needed, but a future Alpha of OnStep will be needed (depending on when I get confirmation that it is working under the stars).

Of course, it is much easier to build a new OnStep version than KStars or INDI.
5 years 8 months ago #27803

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

  • Posts: 322
  • Thank you received: 31
I upgraded to the latest stable version.
indi-bin 1.7.4~201807251425~ubuntu16.04.1 amd64
libindi-data 1.7.4~201807251425~ubuntu16.04.1 amd64

And now OnStep's INDI driver crashes on startup.

There is not much in the log:
[2018-07-31T13:56:55.338 EDT CRIT ][           org.kde.kstars.indi] - INDI driver  "indi_lx200_OnStep"  crashed!
[2018-07-31T13:56:55.728 EDT WARN ][                       default] - QObject::disconnect: Unexpected null parameter
[2018-07-31T13:57:23.062 EDT WARN ][                       default] - QIODevice::write (QTemporaryFile, "/tmp/kstars.B23957"): device not open
[2018-07-31T13:57:23.084 EDT WARN ][                       default] - QSqlDatabasePrivate::removeDatabase: connection 'filter_db' is still in use, all queries will cease to work.
[2018-07-31T13:57:23.084 EDT WARN ][                       default] - QSqlDatabasePrivate::addDatabase: duplicate connection name 'filter_db', old connection removed.
[2018-07-31T13:57:26.915 EDT WARN ][                       default] - QSqlDatabasePrivate::removeDatabase: connection 'filter_db' is still in use, all queries will cease to work.
[2018-07-31T13:57:26.915 EDT WARN ][                       default] - QSqlDatabasePrivate::addDatabase: duplicate connection name 'filter_db', old connection removed.
[2018-07-31T13:57:28.031 EDT CRIT ][           org.kde.kstars.indi] - INDI driver  "indi_lx200_OnStep"  crashed!
[2018-07-31T13:57:28.240 EDT WARN ][                       default] - QObject::disconnect: Unexpected null parameter
[2018-07-31T13:58:09.672 EDT WARN ][                       default] - QIODevice::write (QTemporaryFile, "/tmp/kstars.j23957"): device not open
[2018-07-31T13:58:09.689 EDT WARN ][                       default] - QSqlDatabasePrivate::removeDatabase: connection 'filter_db' is still in use, all queries will cease to work.
[2018-07-31T13:58:09.689 EDT WARN ][                       default] - QSqlDatabasePrivate::addDatabase: duplicate connection name 'filter_db', old connection removed.
[2018-07-31T13:58:22.415 EDT WARN ][                       default] - QSqlDatabasePrivate::removeDatabase: connection 'filter_db' is still in use, all queries will cease to work.
[2018-07-31T13:58:22.415 EDT WARN ][                       default] - QSqlDatabasePrivate::addDatabase: duplicate connection name 'filter_db', old connection removed.
[2018-07-31T13:58:23.180 EDT WARN ][                       default] - QObject::disconnect: Unexpected null parameter
[2018-07-31T13:58:23.567 EDT CRIT ][           org.kde.kstars.indi] - INDI driver  "indi_lx200_OnStep"  crashed!

Was a fix pushed to the next stable version? I'd rather not compile from source if I can do away without that.
5 years 7 months ago #28096

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

  • Posts: 61
  • Thank you received: 8
Unfortunately I can confirm that the Raspberry Pi version crashes as well since a couple of days.
Cheers
Guido
5 years 7 months ago #28144

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

Khalid, can you create a backtrace to see where it crashes? Run indiserver externally like this:
gdb --ex run --eval-command="set follow-fork-mode child" --args indiserver -v indi_lx200_OnStep

In KStars, go to Tools --> Device --> Device Manager --> Client --> Add. The name can be anything "Test". Host: localhost Port: 7624
Click OK, then connect, and try to control the driver from INDI Control Panel. Once it crashes, go back to the console and type in bt to get the backtrace and post it here.
5 years 7 months ago #28154

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

  • Posts: 452
  • Thank you received: 71
@ Khalid and Guido,

Look at the topic www.indilib.org/forum/wish-list/1406-dri...html?start=252#27721

To fix the version some variables need to be expanded to 64 to cope with new lx200driver, but has not been done on version 1.3, I discovered it after release .
I guess for the time beeing we have to work with compiled version.
5 years 7 months ago #28155

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

@azwing: Can the changes be submitted as PR to master?
5 years 7 months ago #28156

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

  • Posts: 322
  • Thank you received: 31

But when we discussed this, we found that OnStep itself never have any response that is more than 50 bytes. So is this still an issue?

As Jasem said, if we have a fix within INDI's OnStep driver, we need a PR for it. If you don't have the time to do it, point me to the file/line and I will do the leg work ...
5 years 7 months ago #28161

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

Time to create page: 0.849 seconds