×

INDI Library v1.9.7 Released (29 Jul 2022)

Bi-monthly INDI Library released with new drivers and bug fixes.

Driver OnStep (LX200 like) for INDI

  • Posts: 11
  • Thank you received: 0
I downloaded a new update today on the rPi, and now OnStep driver shows the 'Rotator' tab (thanks again, James).

PHD2 (2.6.9dev5) keeps crashing when connecting to the mount, but it does the very same when connecting to the Telescope Simulator driver, so it's not driver related. Hope to solve it soon to be able to test the whole thing...

Regards,

Jordi.
1 year 1 month ago #73153

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

  • Posts: 57
  • Thank you received: 1
Hello,

I have a problem with the latest driver.
With Kstars, I launch an automated session:
The telescope unparks.
The goto towards the star starts
The shots instantly before the telescope has reached the star.

The state of OnSTep.Status.Tracking:
Telescope parked:
[OK] LX200 OnStep.OnStep Status.Tracking=Idle
Unpark:
[OK] LX200 OnStep.OnStep Status.Tracking=Tracking
Start a goto:
[NOK] LX200 OnStep.OnStep Status.Tracking=Tracking
Start a goto on a second star:
[NOK] LX200 OnStep.OnStep Status.Tracking=Tracking
Start a park:
[OK] LX200 OnStep.OnStep Status.Tracking=Slewing
Telescope parked:
[OK] LX200 OnStep.OnStep Status.Tracking=Idle

 
1 year 1 month ago #73196

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

  • Posts: 57
  • Thank you received: 1
The state of : OnStep.OnStep Status.:GU# return seems OK:
Telescope parked:
nNPRza/ET250
Unpark:
NpRza~ET250
Start a goto:
pRza,ET250
End goto
NpRza~ET250
Start a goto on a second star:
pRza,ET250
End goto
NpRza~ET250
Start a park:
nIRza/ET250
Telescope parked:
nNPRza/ET250

 
1 year 1 month ago #73198

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

  • Posts: 155
  • Thank you received: 37
Argh! Unfortunately that's not new. Sounds like this isn't fixed (I haven't had the chance to test much and it hadn't happened when I did, so the bug got auto-closed):

bugs.kde.org/show_bug.cgi?id=410094

Can you try the branch own-goto from here: github.com/james-lan/indi/tree/own-goto ? Amusingly, I was working on that for checksum based stuff, and remembered that. That particular branch is the current version with that one change (plus version bump) so it doesn't have the checksum stuff yet.

For a mitigation, increase the polling time. That won't prevent it, and it's annoying, but will reduce the chance of it occurring.

Basically, When I looked at (Kstars has had some changes) It boiled down to a lack of a timer in Kstars, plus the driver relying on the lx200 functions, which set the switch to Slewing, even if the mount isn't yet, and when the status update comes which also sets the TrackState. Under bad combinations of timing: Move Issued and sent - Status update before OnStep changes state, OnStep reports Tracking, driver updates TrackState to Tracking - Kstars goes: Done! Start picture - next update, OnStep reports Slewing, driver updates to slewing, but the image is in progress.

On the other hand we could announce it as a new driver feature: Fastest way to do star trails. ;)
1 year 1 month ago #73214

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

  • Posts: 57
  • Thank you received: 1
Hello,
I just tested with the own-goto branch.
I just replaced indi_lx200generic.
The problem looks the same.
I am using Kstars 3.5.3
Goto towards a star, it systematically remains in tracking.
Park he systematically switches to Sleewing.
GU # is different depending on whether you go to a star or park the telescope:
Goto: pRza, ET250
Park: nIRza / ET250
Tracking: NpRza ~ ET250

In the meantime, I'll be doing star trails :-)
1 year 1 month ago #73223

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

  • Posts: 320
  • Thank you received: 41
Hi James,

I have same results
Parked nNPe/EW290
Unparked Npe/EW290
during Goto pe/EW290
Goto Completed Npe/EW290
Parking nIe/EW290

Debian VERSION="10 (buster)"
Kstars Version 3.5.4 Beta
OnStep 4.24.d
1 year 1 month ago #73224

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

  • Posts: 300
  • Thank you received: 24
Alain and Serge

Can I ask what version of INDI you are using?

I am using this on a laptop (64bit Intel CPU), and Jasem's PPA packages.

indi-bin 1.9.1~202106261410~ubuntu18.04.1
libindi-data 1.9.1~202106261410~ubuntu18.04.1

kstars-bleeding 6:3.5.3+202105061458~ubuntu18.04.1

I did not notice anything bad with OnStep 4.24f.

But I don't use Park/Unpark.

On startup: nNpHSzEo150
During Goto pSzET150
Goto complete: NpSzET150
During Return Home: npSzEW150
At home (same as startup above).
1 year 1 month ago #73229

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

  • Posts: 57
  • Thank you received: 1
Hello,

My PC: mini ITX board Intel 64 bits (J1900) 8GB RAM on Lubuntu 20.04
Kstars and indi drivers: "deb ppa.launchpad.net/mutlaqja/ppa/ubuntu focal main"

OnStep version: 4.24e (on ESP32)
Indi LX200 drivers version: 1.11
INDI Library: 1.9.1 Code 1.9.1-tgz. Protocol 1.7.
indi-bin 1.9.1~202106261417~ubuntu20.04.1 amd64
libindi-data 1.9.1~202106261417~ubuntu20.04.1 all
Kstars: 3.5.3 Stable (kstars-bleeding 6:3.5.3+202105061503~ubuntu20.04.1 amd64)
Last edit: 1 year 1 month ago by Serge CLAUS.
1 year 1 month ago #73231

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

  • Posts: 300
  • Thank you received: 24
Same repositories that I use, but I am on 18.04 still.

deb ppa.launchpad.net/mutlaqja/ppa/ubuntu bionic main

My indi-bin package has this timestamp in it:

indi-bin 1.9.1~202106261410~ubuntu18.04.1

So it was built on 2021-06-26.

I don't know what 1.9.1-tgz is in your case.
1 year 1 month ago #73232

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

  • Posts: 320
  • Thank you received: 41
Hi Khalid,

I forgot the indi version which is:
INDI Library: 1.9.1
Code v1.9.1-10-g9045b593. Protocol 1.7.

I am quite sure the current indi version distributed via ppa suffers this bug.
I made some tests even with TrackState = SCOPE_TRACKING disabled in the OnStep driver.
It must for sure be somewhere in indi or kstars, not in the driver itself ...
Still testing
1 year 1 month ago #73240

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

  • Posts: 300
  • Thank you received: 24
Thanks Alain,

If you want me to test something, let me know what sequence I should do, and what output to look for.

I can test everything except parking and focusers (don't use either).
1 year 1 month ago #73241

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

  • Posts: 155
  • Thank you received: 37
OK, I think I found it, and it's my bad.

For ref:
// [n]ot tracking
// [N]o goto

Trying to simplify things, I'd removed some parking code which also handled the :GU return in one case (not n or N). The own goto should be updated with that (and unrelated PEC, since the command (:QZ#) used no longer works on newer versions, but that should be good now.)

So:
General cases:
!n !N = SLEWING (tracking, goto) < Case I neglected, since it seems like you wouldn't be tracking while on a goto
n !N = SLEWING (not tracking, goto)
     (If also I (Parking n progress) = PARKING)
!n N = TRACKING (tracking, no goto)
n N = IDLE (not tracking, no goto)

Overriden by
P (Parked, also set parked true) PARKED

Related which only give Messages/not change trackstate:
p (sets parked false) (unparked)
F (sets parked false) (parking failed)
I (sets parked false, case handled above) (parking in progress)
H (messages only, combined with p/P)

Someone want to check my logic to make sure I didn't miss anything?
 
1 year 1 month ago #73244

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

Time to create page: 0.781 seconds