×

INDI Library v2.0.7 is Released (01 Apr 2024)

Bi-monthly release with minor bug fixes and improvements

Driver OnStep (LX200 like) for INDI

  • Posts: 65
  • Thank you received: 4
Looks like tracking rates changed in SWS are not being picked up by INDI.

I will stop there as i want to make sure this is useful or not.

Chad
1 year 3 weeks ago #91479

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

  • Posts: 452
  • Thank you received: 71
But this does not explain why 1 degree in SWS is shown as 4 minutes in Indi.
In OnStep the parameter is divided by 4 (why and whan this changed ???) I will investigate.
1 year 3 weeks ago #91480

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

  • Posts: 322
  • Thank you received: 31

I think it may be that 1 degree is for angular distance, and 4 minutes is the measure of time.

So it is the same thing, but different units.
1 year 3 weeks ago #91481

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

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

In the meantime I found it but better I put a comment in the code otherwise next time I touch it ....
I'm getting older :-)
1 year 3 weeks ago #91482

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

  • Posts: 115
  • Thank you received: 17
Hi, Alain
I don't focus on the fact that I can't compile INDI because I spend my free time developing the client (it doesn't require INDI compilation)

PS:I use KUbuntu and always get cmake error:
Could NOT find Libev (missing: LIBEV_LIBRARY LIBEV_INCLUDE_DIR)
libev-dev is installed
I tried your script with same result
1 year 3 weeks ago #91493

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

  • Posts: 115
  • Thank you received: 17
Hm... It looks like strange behavior or bug of apt command. It doesn't install libev-dev if to write many packages after `sudo apt install` (as in your build script).
Separate `sudo apt install libev-dev` solved the problem
1 year 3 weeks ago #91494

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

  • Posts: 27
  • Thank you received: 3
Hi Alan,
Thanks for the amazing work you do...
The thing I want to fix is the "slew elevation limit" setting. In addition to not corresponding with the SWS settings, it resets to the values -30 and +89 at each restart. If I forget to change them (and it happens often...) this thing doesn't make the automatic meridian flip work. In fact, the mount stops even before crossing the meridian.
Also this value doesn't seem writable, i can't change it even with a script when starting the connection for example
1 year 3 weeks ago #91495

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

  • Posts: 115
  • Thank you received: 17
Alain, almost nothing has changed after I tried latest version (1.18):
1. Too much notifications about new properties for focuser and weater. Driver continues to spam in INDI console even if no clients are connected. I think there is something very wrong with focuser and weather properties in driver implementation
2. Focuser stops to work if to change focuser position frequently. I forget to inform you about it last time. It starts to work only after driver restarting

New issue:
Driver starts to span with INDI messages with text
[WARNING] Invalid response, check connection
[WARNING] Communication :Ft# error, check connection.
This was not the case in the previous version

Only empty properties issue is fixed in 1.18
Last edit: 1 year 3 weeks ago by Denis.
1 year 3 weeks ago #91496

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

  • Posts: 452
  • Thank you received: 71
From your logs I deduce you are using WiFi, no?
This is the only way I can reproduce these timeouts.
Unfortunately I have the same problem (broken pipe) when using scripts or minicom over WiFi.
I even sometimes need to re-initialize the connection.

There is definitively a WiFi issue but only for Linux user? I don't know.

When you mean only empty property issue is fixed, do you mean that properties still are updated each second (polling time)?
This is due to properties being updated each time values are polled which means every second if polling is set to this value.
but this has no influence on communication with firmware (OnStep)

The communication with firmware needs to poll each variable at regular period and once a second is not an issue.

On the other hand if we want to get rid of properties updates the polling should be rewritten entirely.
One should check for each property is value has changed and update only in this case.
This for each polled variable.
I am testing on this but it is not in my plan to make it an official release until it is proven to work.
It will take some time :-(

For now I try to fix the last known bugs related to discrepancies between Indi
1 year 3 weeks ago #91498

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

  • Posts: 115
  • Thank you received: 17
1. I don't use WiFi. OnStep device is connected via USB to my PC. I start indiserver for debugging locally on my PC by command
indiserver -vv indi_simulator_ccd indi_lx200_OnStep

2. Yes. Each second (or polling time) driver sends notifications about new properties of focus and weather and than notification about properties values
Last edit: 1 year 3 weeks ago by Denis.
1 year 3 weeks ago #91499

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

  • Posts: 452
  • Thank you received: 71
Via USB there shouldn't be issues but if you notice I have to look at this too.

here what I get periodically after connection

indi_getprop -w

LX200 OnStep.FOCUS_ABORT_MOTION.ABORT=Off
LX200 OnStep.WEATHER_UPDATE.PERIOD=60
LX200 OnStep.WEATHER_REFRESH.REFRESH=Off
LX200 OnStep.WEATHER_OVERRIDE.OVERRIDE=Off
LX200 OnStep.WEATHER_STATUS.WEATHER_TEMPERATURE=Ok
LX200 OnStep.WEATHER_PARAMETERS.WEATHER_TEMPERATURE=20.800000000000000711
LX200 OnStep.WEATHER_PARAMETERS.WEATHER_HUMIDITY=70
LX200 OnStep.WEATHER_PARAMETERS.WEATHER_BAROMETER=977.5
LX200 OnStep.WEATHER_PARAMETERS.WEATHER_DEWPOINT=14.800000000000000711
LX200 OnStep.WEATHER_PARAMETERS.WEATHER_CPU_TEMPERATURE=0
LX200 OnStep.WEATHER_TEMPERATURE.MIN_OK=-40
LX200 OnStep.WEATHER_TEMPERATURE.MAX_OK=85
LX200 OnStep.WEATHER_TEMPERATURE.PERC_WARN=15
LX200 OnStep.WEATHER_HUMIDITY.MIN_OK=0
LX200 OnStep.WEATHER_HUMIDITY.MAX_OK=100
LX200 OnStep.WEATHER_HUMIDITY.PERC_WARN=15
LX200 OnStep.WEATHER_BAROMETER.MIN_OK=0
LX200 OnStep.WEATHER_BAROMETER.MAX_OK=1500
LX200 OnStep.WEATHER_BAROMETER.PERC_WARN=15
LX200 OnStep.WEATHER_DEWPOINT.MIN_OK=0
LX200 OnStep.WEATHER_DEWPOINT.MAX_OK=100
LX200 OnStep.WEATHER_DEWPOINT.PERC_WARN=15
LX200 OnStep.WEATHER_CPU_TEMPERATURE.MIN_OK=-274
LX200 OnStep.WEATHER_CPU_TEMPERATURE.MAX_OK=200
LX200 OnStep.WEATHER_CPU_TEMPERATURE.PERC_WARN=-274
LX200 OnStep.FOCUS_MOTION.FOCUS_INWARD=On
LX200 OnStep.FOCUS_MOTION.FOCUS_OUTWARD=Off
LX200 OnStep.REL_FOCUS_POSITION.FOCUS_RELATIVE_POSITION=0
LX200 OnStep.ABS_FOCUS_POSITION.FOCUS_ABSOLUTE_POSITION=25000
LX200 OnStep.FOCUS_MAX.FOCUS_MAX_VALUE=100000
LX200 OnStep.FOCUS_ABORT_MOTION.ABORT=Off
1 year 3 weeks ago #91500

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

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

analysing logs and focuser function I found what is annoying and confusing:

look at the following code:
int ft_error = getCommandIntResponse(PortFD, &focus_T_int, focus_T, ":Ft#");
        if (ft_error > 0)
        {
            FocuserTN[0].value =  atof(focus_T);
            IDSetNumber(&FocuserTNP, nullptr);
            LOGF_DEBUG("focus T°: %s, %i fi_error: %i", focus_T, focus_T_int, ft_error);    //typo
        }
        else
we return ft_error with the descriptor ft_error which should be ft_nbcar (because in fact it show the number of characters returned by OnStep

so the code should be
int ft_error = getCommandIntResponse(PortFD, &focus_T_int, focus_T, ":Ft#");
        if (ft_error > 0)
        {
            FocuserTN[0].value =  atof(focus_T);
            IDSetNumber(&FocuserTNP, nullptr);
            LOGF_DEBUG("focus T°: %s, %i ft_nbcar: %i", focus_T, focus_T_int, ft_error);    //typo
        }
        else
and there was a typo in the Debug text as well

I will correct these but for sure there are no real errors simply it is a wrong debug information.

Concerning the focuser I cannot reproduce focuser hang-up even afte 4 hours of moving it every 5 seconds back and forth
1 year 3 weeks ago #91505

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

Time to create page: 0.875 seconds