×

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: 130
  • Thank you received: 6
As it turnout, after doing alignment and press save to NV memory, I got this error message in INDI. I did not notice it before.

2023-10-26T12:27:44: [INFO] Getting Alignment Status: response Error, response = 1965>
2023-10-26T12:27:44: [INFO] Sending Command to Finish Alignment and write
I am trying to do a 5 stars alignment. If I try doing a 3 star alignment then the error code turns to 1963
4 months 1 week ago #96722

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

  • Posts: 65
  • Thank you received: 4
You would be best off posting to the OnStep group for OnStep errors and questions.
onstep.groups.io/g/main/topics
The following user(s) said Thank You: Nguyễn Trọng Minh
4 months 1 week ago #96723

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

  • Posts: 322
  • Thank you received: 31

Doing a reset causes OnStep to forget all alignment data.
That, and the NV save failure is probably why you see no improvement.
The following user(s) said Thank You: Nguyễn Trọng Minh
4 months 1 week ago #96725

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

  • Posts: 452
  • Thank you received: 71
I see what you mean:

in fact there are some changes in how OnStep replies to commands "AW#" and "!MP#"
before it was no return so we did use "sendOnStepCommandBlind" but OnStep returns n (0 ..9) that then is read by the following "A?#" command and shows this error message

I fixed it and code is available here : github.com/azwing/indi/tree/OnStep_Work

let(s confirm it works before issuing another pull request
The following user(s) said Thank You: Nguyễn Trọng Minh
4 months 1 week ago #96726

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

  • Posts: 130
  • Thank you received: 6
4 months 1 week ago #96727

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

  • Posts: 130
  • Thank you received: 6
2023-10-26T16:44:02: [INFO] Align Write Successfull 
2023-10-26T16:44:02: [INFO] Sending Command to Finish Alignment and write 
2023-10-26T16:43:39: [INFO] Alignment Done - May still be calculating
It worked! Thanks! The goto accuracy still show no improvement though. I tried 9 point align on Sky Planetarium and there are significant improvement of goto on RA. (always in the +_30 arcsec). Keeping the same model in INDI does not show that improvement.
The following user(s) said Thank You: Alain Zwingelstein
4 months 1 week ago #96729

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

  • Posts: 452
  • Thank you received: 71
The challenge with OnStep is to follow the little changes like this .... and I am always behind :-)

Your goto accuracy definitively is not Indi side (even before my changes the commands were send correctly, only the response was missinterpretated
Last edit: 4 months 1 week ago by Alain Zwingelstein.
4 months 1 week ago #96730

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

  • Posts: 452
  • Thank you received: 71
How do you run alignmenet with Ekos?

The process should be like this:
1) Start Ekos
2) Select number of stars in control panel
3) Start Alignment in control panel
3) open Ekos and select "Sync" as action after plate solving
4) open the mount model
5) select same number of stars as in (2)
6) generate stars (or choose your own)
7) start mount model
8) Ekos will now slew to each star, wait for "settle time" shoot a picture, plate solve and "Sync" to the solved coordinates
9) when Ekos has finished the sequence for all stars, the Align should be defined as Finished in the Control Panel
10) OnStep then calculates the delta and Indi show it in bottom of alignment tab
11) Then you have to click "Write Align to NVRAM / Flash" (this will ask OnStep to sore the model (not Ekos Model, the Model calculated by OnStep)

Indi Mount Model is "NEVER" written to OnStep, indi only initiates the sequence by telling OnStep
Number of stars (selector), validate the coordinates for each star the (issue align), confirms to OnStep that the model can be applied ( Write Align to NVRAM / Flash")

All the remaining is done by th OnStep firmware and indi just shows the status (Max Stars, Current Star, # of ligned Stars)

I am using OnStepX version: = 10.19.b and it works so far I cannot test it on the stars with the deluge we have currently

PS: there is a video for that
The following user(s) said Thank You: Nguyễn Trọng Minh
Last edit: 4 months 6 days ago by Alain Zwingelstein.
4 months 6 days ago #96740

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

  • Posts: 130
  • Thank you received: 6
I think you forgot let the mount return to home position, pointing to the NCP before press start align. I did exactly as your steps. After writing to NVRAM, the information does show, but after a reset, I do not see any sign of improvement on the goto accuracy. Anyway, do you have the problem of the mount do not remember the park position? I slew the mount to the parked position, press use current posstion as park then save in INDI, then go to the SWS interface, press save park position on the web interface. But everytime I resets, the pointing is reseted to the NCP, not the parked position, I have to manually slew out of the place then do a blind plate solve.
Also, there is a weird behaviour with my onstep. after I press parked in INDI and then unpark, the mount just refuses to slew. I issue goto command and the mount just won't slew. I have to do a power cycle to the Onstep controller, and then the mount slews ok again (but the pointing resets to NCP). This is really annoying since I am running everything remotely. Any thoughts on this?
P/S: cool avatar, I have always thought you used a Gandalf image as your avatar but today I use my laptop and see that it's not Gandalf :))
4 months 6 days ago #96741

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

  • Posts: 452
  • Thank you received: 71
Just for info,

I made some cosmetics changes to the Alignment and fixed a typo :GX02# > :GX03# (which displayed errors for both axes the same)
makes no changes in the process and verified that mount model is correctly written in NVRAM with the Write button.
Corrections stay after cold reboot of OnStep and therefore OnStep is aware of the mount model after alignment.

Any tests / reports are wellcome

Pull request issue and lates changes on github.com/azwing/indi/tree/OnStep_Work
4 months 6 days ago #96742

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

  • Posts: 452
  • Thank you received: 71
What do you mean by "After a Reset"?
For me when I have mount model errors they stay there even after cold reboot. (OnStepX 10.19.b)

Parking:
Before Parking one need to define the park position
this is done in control panel Site Management tab, bouton "Current" and "Write Data"
Then you can use the Park button and you slew to the park position and telescope takes the status "Parked".

Now since OnStepX something changed:

As long OnStep is not Unpowered , it remembers the Park Position and the Parked Status

If OnStep is Unpowered, it remembers the Park Position and the Status but when kstars sends Location/date it unparks and and takes "Idle" state with the telescope located at Park location since not tracking.
Before operation tracking must be manually initiated.

Before OnStepX I really had to Unpark and tracking started then.
The following user(s) said Thank You: Nguyễn Trọng Minh
4 months 6 days ago #96744

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

  • Posts: 322
  • Thank you received: 31
Nguyen ...

Doing a Reset is most likely the problem you are facing.

I am not sure about OnStepX, but in OnStep, when you do a Reset (:hF#), all the alignment correction data is zeroed out.

The only way to preserve the alignment data is to a) save it to NVRAM, and b) do a Park.

Next session you do Unpark, but never Reset.
You can verify that by checking the corrections in Azimuth and Altitude: they will have values that are not zero when you finish your alignment, and if you Park/Unpark. But if you reset, they will be zero.
The following user(s) said Thank You: Nguyễn Trọng Minh
4 months 6 days ago #96747

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

Time to create page: 0.990 seconds