×

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
[quote="azwing" post=29293
In the meantime I should receive STM32 and rest of the hardware so I could be in position to test Teensy/STM32 and Arduino.[/quote]

The STM32 is equivalent in speed and features to the Teensy 3.2 and the MiniPCB. So if you have one, you don't need the other.

In case you have not seen it, there is a PCB for the STM32 now, which makes the build much easier.

I look forward for you sharing the STM32 build details on the group. Many will benefit from seeing others build it.

[/quote]Did you succeed to have your OnStep mount ready for testing?[/quote]

Not yet. I am waiting for the belts before I have a friend help me with drilling holes to mount the motors.

But he (Dave) has a CG5 type mount that runs OnStep with the STM32.
5 years 6 months ago #29296

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

  • Posts: 174
  • Thank you received: 27
I posted the following message on Onstep forum:

Here is the responce I received from Khalid:

Alain et al,
Do you have any thoughts on this issue?

Alex
5 years 6 months ago #29304

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

  • Posts: 257
  • Thank you received: 22
--had we done the slew patch at that time, a month ago?

I've also encountered this while in use but haven't had time to look into it nor have I reported it as I've had my hands full recently and couldn't narrow that AND get the other work done in the short times I've had in the field. It did not effect the recent alignment test.

Khalid's remarks sound right. I would add that it has worked properly in the past.

As a temporary workaround, I've been using solve & sync instead of solve & slew, and then hitting the slew button with good results. This could also be a clue to where the problem lies since each routine runs okay standalone. This also works for manual 3 star alignment.

My mount is currently in the shop for either an RTC or GPS addon to correct timing issues. I'm not sure which I'm doing yet.
5 years 6 months ago #29317

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

  • Posts: 452
  • Thank you received: 71
@ Blueshawk
Nothing except patches because of variable overflow was done since March ... I was really lazy last few months :)

@ Khalid
yes you are right, OnStep uses ":GU" return codes to update tescope status so it reflects exactly the Firmware Status.
The Status is refreshed in the tab each time there is a change in the return code.

In the doubt, I checked some very little slews (1', 2', 10') both RA and DEC via terminal and status behaves normal
Did the same via Indi Control panel and same results.
2018-09-06T11:22:31: [INFO] Slewing to RA: 10:10:09 - DEC: -0:29:09
2018-09-06T11:22:26: [INFO] Slewing to RA: 10:10:09 - DEC: -0:29:10
2018-09-06T11:22:17: [INFO] Slewing to RA: 10:10:10 - DEC: -0:29:10
2018-09-06T11:22:13: [INFO] Slewing to RA: 10:10:10 - DEC: -0:29:03
2018-09-06T11:22:08: [INFO] Slewing to RA: 10:10:03 - DEC: -0:29:03
2018-09-06T11:22:02: [INFO] Slewing to RA: 10:10:03 - DEC: -0:29:02
2018-09-06T11:21:49: [INFO] Slewing to RA: 10:10:02 - DEC: -0:29:02
2018-09-06T11:21:37: [INFO] Slewing to RA: 10:10:00 - DEC: -0:29:00

@ avarakin
First of all, thanks for your time passed on testing and reporting.
Are you using version 1.3 or 1.4?

Do I understand well: You try to slew some second and the sleew starts but never ends!
Does the ":GU#" return change in the "ONStep Status" tab?
Do you have logs for this situation.

I did a test on bench (cannot do it in real situation, my hardware is not mounted)
I was not able to reproduce this problem when asking slews for 1' or 2' and I saw the status changing from Tracking to Slewing and Tracking again,
This status change cannot be seen in the control panel because sometimes it is too quick, but it really happens

Since in the driver code Scope status if set only once based on Status query it is unlikely that Scope Status is set to Slewing and vever reste to Tracking due to polling issues and missed state changes.
I also check is it is not Ekos setting TrackState=SCOPE_SLEWING, it is not the case.

I am sorry not to be in position to help here.
I will check further but if in the meantime you could take logs of the situation would help.
5 years 6 months ago #29331

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

  • Posts: 257
  • Thank you received: 22
@Azwing. Sorry for my unclear statement. And we all know about your recent troubles. Sick is not lazy. :P

I also encountered the never ending slew. It only happens when using plate solving with "slew to target" selected.
If you hit stop it completes and you find it actually did slew to target.
Using "sync" and then manually slewing to target completes slew okay.
Slewing away a bit and hitting slew to target for short changes also completes on mine.

I'm just speculating but this seems like it could be in the Ekos plate solving routine, but if it is it probably should show up for other mount drivers as well.
5 years 6 months ago #29360

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

  • Posts: 174
  • Thank you received: 27
I will capture the logs next time I do imaging and see this issue. Also I will try other plate solving software - CCDCiel and see if the same issue is present there.
Easy way to reproduce it is to set the tolerance of pointing to some very low value, less than 1'. In this case most of the time you end up with a precision slew and it gets stuck.
The following user(s) said Thank You: Alain Zwingelstein
5 years 6 months ago #29363

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

  • Posts: 452
  • Thank you received: 71
@Blueshawk and Avarakin

Thanks for the more precise description.
I really need to speed-up my setup to start testing in real situation.

I will make a trial with my EQ6-R mount and EQmod driver, could be interesting.
5 years 6 months ago #29365

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

  • Posts: 322
  • Thank you received: 31
Did anyone diagnose what the source for the precision slew never ending problem is? Or at least what conditions trigger it?

For example: Could it be when the backlash compensation setting is more than the required precision?

I have seen it several times, but can't seem to get a pattern of when it would happen.
5 years 5 months ago #30340

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

  • Posts: 452
  • Thank you received: 71
Khalid,

seems the season is not good for testing :(

Unfortunately more patience is needed on my side before I can start serious testing in rteal conditions.
Most probably begining November if the weather play whith.

Some more patience, I'm sorry
5 years 5 months ago #30503

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

  • Posts: 161
  • Thank you received: 39

So far I haven't found it. Though I give my mount a bit to settle (I have a bit of backlash which I haven't taken the time to properly setup. So that could be a possibility...)

Also, can you check if it's got Pulse Guiding set to ON (Main tab, I think)


I just pushed some changes to enable the outputs, and hopefully satellite tracking (Not 100% sure that it will work yet.) to azwing.

I've only been able to get outside one time when it wasn't cloudy, so I haven't been able to test, unfortunately.

There's also this checksumming which I think is good. Might resolve some problems, but does mean that we'll have to re-implement some of the LX200 stuff (or we could restrict that to just things like guiding/moving and see if that resolves the issues?

Quoting Howard on the list:
Last edit: 5 years 5 months ago by james_lan.
5 years 5 months ago #30615

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

  • Posts: 322
  • Thank you received: 31

I have 'Use Pulse Cmd' set to On, which is I think is the default, since I did not mess with it, nor use the ST4 port in anyway.

Yes, I think this requires reimplementing everything. So it is a parallel set of commands with the same functionality, but return codes on some that have no return codes in the LX200.

It can be implemented with some effort, but it may be the case that the OnStep telescope driver in INDI to be totally separate from the underlying LX200 class, with everything implemented with the new command set.

Also, it means that OnStep users have to use Alpha only?
5 years 5 months ago #30616

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

  • Posts: 322
  • Thank you received: 31
I should also mention that I did one precision slew tonight (it is clear, but with a bright moon), and it worked without a problem. It does not happen in every case. Not sure what triggers it.
5 years 5 months ago #30617

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

Time to create page: 1.114 seconds