×

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: 60
  • Thank you received: 2
I'm confused, autoflip should be set to off when you want Ekos to control the flip no?
2 years 1 month ago #80130

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

  • Posts: 144
  • Thank you received: 7
Thanks Alain.
Ettore
2 years 1 month ago #80131

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

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

Meridian Flip e un Casino infernale :-)

There is a lot of confusion with Autoflip.
In fact there is no command to issue Autoflip.
There are only limits that define a windows (between limiot East and limit West) where Onstep executes a flip when a goto is issued in this window and only if Autoflip is set to ON.
Otherwise when you reach the meridian cross Onstep will stop track or slew.
Ekos simply issues a goto when the HA is reached.

Maybe It is still not clear see references:
onstep.groups.io/g/main/wiki/5650
docs.google.com/document/d/11NlWvWyI5RxN...ekqkZmgQoIBw91M/edit
ma in Tedesco!
www.astrotreff.de/forum/index.php?thread...ian-flip-verhindern/
2 years 1 month ago #80132

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

  • Posts: 174
  • Thank you received: 27
I updated INDI to latest from PPA (1.9.5) and OnStep to 4.24 and now getting error upon connecting to the mount:
"Error setting UTC Offset"
I have "Time & Location Updates" enabled in INDI settings tab of Kstars.
I am getting same error even if I am using INDI settings window for changing UTC offset.
Given that UTC is not set correctly, the mount is totally lost.
Any thoughts on what is causing this issue?
2 years 1 week ago #81491

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

  • Posts: 60
  • Thank you received: 2
Yes i have the same problem!
2 years 1 week ago #81498

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

  • Posts: 276
  • Thank you received: 52
A while ago there was an update to the lx200 driver to remove some extra space in commands sent.
The offending area may be here
lx200driver.cpp

OLD = snprintf(read_buffer, sizeof(read_buffer), ":SG %+03d#", static_cast<int>;(hours));
// Meade Telescope Serial Command Protocol Revision 2010.10
// :SGsHH.H#
// Set the number of hours added to local time to yield UTC
// Returns:
// 0 – Invalid
// 1 - Valid
NEW = snprintf(read_buffer, sizeof(read_buffer), ":SG%+04.01lf#", hours);

return (setStandardProcedure(fd, read_buffer));
}

The lx200 2010 manual has:
:SGsHH.H# Set the number of hours added to local time to yield UTC Returns: 0 – Invalid 1 - Valid

The Command.ino of OnStep shows this
github.com/hjd1964/OnStep/blob/release-4.24/Command.ino

//  :SG[sHH]# or :SG[sHH:MM]# (where MM is 30 or 45)^M
//            Set the number of hours added to local time to yield UTC^M
//            Return: 0 on failure^M
//  
The following user(s) said Thank You: Alex Varakin
2 years 1 week ago #81504

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

  • Posts: 174
  • Thank you received: 27
Thank you so much, Gene, for pointers!
Isue is that OnStep is not able to parse the dot as part of the number sent from INDI, e.g.  -5.0
I think the correct fix is to implement override method as part of OnStep driver, as opposed to relying on the method of the generic LX200 driver.
As a quick fix, I worked around the problem by changing Command.ino of OnStep as shown below:

//  :SG[sHH]# or :SG[sHH:MM]# (where MM is 30 or 45)
//            Set the number of hours added to local time to yield UTC
//            Return: 0 on failure
//                    1 on success
      if (command[1] == 'G')  { 
        if (strlen(parameter) < 7) {
          double f=0.0;
          char *temp=strchr(parameter,'.');
          if (temp) {
            if (temp[0] == '.' && temp[1] == '4' && temp[2] == '5') { temp[0]=0; f=0.75; } else
            if (temp[0] == '.' && temp[1] == '3' ) { temp[0]=0; f=0.5; } else 
            if (temp[0] == '.' && temp[1] == '0' ) { temp[0]=0; f=0.0; } else { i=-999; } // force error if not :00 or :30 or :45
          }

 
2 years 1 week ago #81516

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

An override is the best way to go IMO so that it works with existing firmware.
2 years 1 week ago #81523

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

  • Posts: 276
  • Thank you received: 52
Alex, glad the info helped!

Jasem, Ok! I closed issue #1643 but did not open one against OnStep for the issue

Gene

BTW: Forum seems to be getting worse, no response yesterday in browser over periods of time and after trying to post this same response earlier today, and post did not make it.
2 years 1 week ago #81524

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

  • Posts: 452
  • Thank you received: 71
@alex, @gene,

I pushed a fix to github.com/azwing/indi master

Can somebody test before I submit a pull request?
2 years 1 week ago #81533

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

  • Posts: 276
  • Thank you received: 52
@Alain,
Just a comment

The original lx200driver did not support non whole integer offsets (%03d), this was corrected in the base driver update (%+04.01lf).

The main GIT OnStep Command.ino also supports non whole integer offsets but limits what it will accept to :00, :30 and :45
It requires the exact strings if the ':' is included, e.g. ":00", ":30" and not :0 or :3

Now Meade command set does not cover the :45 offset directly only closely

en.wikipedia.org/wiki/List_of_UTC_time_offsets

What would be chance of adding the :00/:30/:45 capability in the OnStep overrides driver?

Disclaimer: I am not an OnStep user

Observation: Until issue 1604 the indilib community did not seem to suffer from the whole integer only offsets but if you are inside OnStep code :-)

Gene
The following user(s) said Thank You: Alain Zwingelstein
2 years 1 week ago #81548

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

  • Posts: 452
  • Thank you received: 71
@gene,

it is possible and I checked in Kstars "Settings/Geographic" and effectively there are Countries having offsets of 30' or 45'
At least I learned something today! I didn't remember Nepal having +05:45 or Western Australia +08:45 ... and I visited both countries !!!
Time modifying, doing testing and then push for review!
2 years 1 week ago #81550

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

Time to create page: 1.511 seconds