×

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

Bi-monthly release with minor bug fixes and improvements

Read More...

Driver OnStep (LX200 like) for INDI

  • Posts: 452
  • Thank you received: 71

Replied by Alain Zwingelstein on topic Driver OnStep (LX200 like) for INDI

Khalid,

so you would advise to abandon the "Addon" WiFi version and move to SamartWebServer?
I suppose 2.x is the main branch.
Bu I still wonder why I could not connect my phone(s) to the WiFi.

Good: I will make another trial with this version.

Can you please provide your Python scripts?
2 years 5 months ago #77623

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

  • Posts: 322
  • Thank you received: 31

Replied by Khalid on topic Driver OnStep (LX200 like) for INDI

If you want to reproduce the problem I am facing, then using SWS v 2.x (main branch) is needed. I say that because of the different timeout values that I pointed in the source.

Before James goes changing stuff in source, we need to be sure where the issue is, and if someone can reproduce it, that would help a lot. I think we should not change any code until we confirm the issue and that it is the SWS timeout values.

I don't know why you can't connect your phone. My experience earlier was that the SSID info was retained in the ESP8266, but for the last several months, it gets wiped when I flash a new version, and I have to connect to to the SSID ONSTEP/password and tell it to go into station mode and give it my router's SSID, ..etc.

Maybe check if there is now an ONSTEP SSID? That would explain what you are seeing.
2 years 5 months ago #77624

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

  • Posts: 452
  • Thank you received: 71

Replied by Alain Zwingelstein on topic Driver OnStep (LX200 like) for INDI

I succeeded to install Smart Web Server 2.01e (OnStep4.24m)
Before I had 1.x
But the symptoms are the same.
I see the ONSTEP ESSID enter password and nothing happens.
I will switch over to Station mode but before I would like to investigate this (do some other people have this issue?)

Will make some other trials.

And of course changing code when nobody has a clue on why this issues exists is not an option.

At lest I have something to do during this cloudy, foggy, wet period :-)

The right thing to do is to have at least the same set-up:

I now have:
MaxPCB Onstep version 4.24m
SWS version 2.01e
Indi Version last git (Commits on Nov 14, 2021 by James Lan)
kstars 3.5.6 Stable

Forgotten the Python Scripts?
2 years 5 months ago #77626

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

  • Posts: 161
  • Thank you received: 39

Replied by james_lan on topic Driver OnStep (LX200 like) for INDI

I use ESP-01s for some sensors, but I agree, the form factor sucks for the primary use. They are easy to solder the wakeup pin compared to some of the others (which may put other things on the pin.) Then to use with wire wrap. If you've got a 3.3V uart cable it's pretty trivial, and runs well off batteries.

As far as version, The reason it's on V3.16q is that STM32Duino seems to dislike everything (even 1.9) and the dislike is now mutual. (Too much of a headache to fix.) Interestingly it didn't seem to have an issue with the black pill I tried for testing, but I've only got the one blue pill that fits the stm32 kit layout. So it's gonna stay on that until I have some free time that I don't spend working on something else. I'll probably move to OnStepX on it, when I think that's ready.

Everything I've been chasing has had benefits/bugfixes so it's not been a waste. I should have another ESP in that form factor tomorrow or maybe the next day.

Though I did discover if one of you wants to check that apparently I did put the FI::UpdateProperties in place for disconnect. (I remember copying it there, but probably got lost when I tried to do different branches.)

My TODO with regards to this:
Wait for esp so I don't mess up current setup. Then play with SWS. (If you guys fix it before I get them, then yay.)
Fix the Focuser not disappearing on disconnect. (PR added)
Add a control to allow adjusting the timeout (Which will work well for letting people with networks adjust it as needed.)
The following user(s) said Thank You: Alain Zwingelstein
2 years 5 months ago #77627

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

  • Posts: 322
  • Thank you received: 31

Replied by Khalid on topic Driver OnStep (LX200 like) for INDI

I am on SWS 2.01d, so one patch level before the one you have.

The python script is attached.
It requires my OnStep Python API .

Place the script in the examples directory, rename it to .py, change to your IP address (or USB port name), and run it as ./examples/test-focuser-rotator.py
The following user(s) said Thank You: Alain Zwingelstein, james_lan
2 years 5 months ago #77628
Attachments:

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

  • Posts: 452
  • Thank you received: 71

Replied by Alain Zwingelstein on topic Driver OnStep (LX200 like) for INDI

Oups !!! no module names 'lx200'

guess something's left in the pipe :-)
2 years 5 months ago #77629

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

  • Posts: 322
  • Thank you received: 31

Replied by Khalid on topic Driver OnStep (LX200 like) for INDI

It is in my API.

Download the OnStep Python API that I linked to earlier.
Unzip it to a directory.

Then follow the instructions I included in my last message.
2 years 5 months ago #77630

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

  • Posts: 322
  • Thank you received: 31

Replied by Khalid on topic Driver OnStep (LX200 like) for INDI

Alain,

You don't need the script that I attached earlier.
A version of it is included in the OnStep Python API git project.
It is called test-timeouts.py

So just download/update the OnStep Python API again, and run it.
2 years 5 months ago #77631

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

  • Posts: 452
  • Thank you received: 71

Replied by Alain Zwingelstein on topic Driver OnStep (LX200 like) for INDI

Khalid,

I make a python crash course :-) ...
I modified slightly your script base on a log of all commands as issued by a working OnStep over USB so that I can simulate a sort of "real situation"

by the end I see that there is no real delay "command/response"
So at least we can exclude the WiFi side I would say and concentrate on why Indi has issues.
By the way we also can deduce that "chatty" or not we are far from having a bottleneck in the communication. (Init takes 1,2s, Polling only 0,2s)
0.008 Ack P
0.009 :GR# 10:37:00#
0.005 Ack P
0.007 :Gc# 24#
0.007 :GM# Schoenau#
0.008 :GT# 0.00000#
0.008 :Gt# +48*13#
0.008 :Gg# -007*38#
0.007 :GG# -01#
0.007 :GL# 13:23:14#
0.008 :GC# 11/16/21#
0.010 :GVD# Nov 15 2021#
0.007 :GVT# 12:53:44#
0.008 :GVN# 4.24m#
0.008 :GVP# On-Step#
0.006 :FA# 0
0.006 :fA# 0
0.008 :F1A# 0
0.007 :F2A# 0
0.006 :F3A# 0
0.007 :F4A# 0
0.006 :F5A# 0
0.007 :F6A# 0
0.206 :F7A# 0
0.206 :F8A# 0
0.205 :F9A# 0
0.205 :rG# 0
0.008 :GXY0# 11111110#
0.007 :GXY1# FAN 0,1#
0.009 :GXY2# FAN 1,2#
0.007 :GXY3# FAN 2,2#
0.009 :GXY4# Chauf 0,3#
0.007 :GXY5# Chauf 1,3#
0.008 :GXY6# Chauf 2,3#
0.008 :GXY7# Chauf 3,3#
0.008 :SG-01# 1
0.010 :SL13:09:52# 1
0.008 :SC11/16/21# 1
0.009 :Sg352:21:9.00# 1
0.010 :St+48:13:29.00# 1
0.009 :GR# 10:23:36#
0.008 :GD# +90*00:00#
0.009 :GU# nNPHz/Eo260#
0.007 :GR# 10:23:36#
0.005 Ack P
0.008 :GM# Schoenau#
0.007 :GT# 0.00000#
0.010 :GtH# +48*13:29.000#
0.009 :GgH# -007*38:51.000#
0.006 :GG# -01#
0.008 :GL# 13:09:52#
0.009 :GC# 11/16/21#
0.008 :GVD# Nov 15 2021#
0.008 :GVT# 12:53:44#
0.008 :GVN# 4.24m#
0.010 :GVP# On-Step#
0.006 :FA# 0
0.006 :fA# 0
0.007 :F1A# 0
0.006 :F2A# 0
0.006 :F3A# 0
0.006 :F4A# 0
0.008 :F5A# 0
0.007 :F6A# 0
0.204 :F7A# 0
0.206 :F8A# 0
0.205 :F9A# 0
0.205 :rG# 0
0.008 :GXY0# 11111110#
0.008 :GXY1# FAN 0,1#
0.007 :GXY2# FAN 1,2#
0.008 :GXY3# FAN 2,2#
0.008 :GXY4# Chauf 0,3#
0.008 :GXY5# Chauf 1,3#
0.008 :GXY6# Chauf 2,3#
0.009 :GXY7# Chauf 3,3#
0.008 :GR# 10:23:37#
0.005 Ack P
0.007 :GM# Schoenau#
0.006 :GT# 0.00000#
0.008 :GtH# +48*13:29.000#
0.010 :GgH# -007*38:51.000#
0.006 :GG# -01#
0.007 :GL# 13:09:54#
0.008 :GC# 11/16/21#
0.008 :GVD# Nov 15 2021#
0.007 :GVT# 12:53:44#
0.007 :GVN# 4.24m#
0.007 :GVP# On-Step#
0.008 :FA# 0
0.006 :fA# 0
0.006 :F1A# 0
0.006 :F2A# 0
0.006 :F3A# 0
0.006 :F4A# 0
0.006 :F5A# 0
0.007 :F6A# 0
0.204 :F7A# 0
0.205 :F8A# 0
0.206 :F9A# 0
0.205 :rG# 0
0.008 :GXY0# 11111110#
0.008 :GXY1# FAN 0,1#
0.009 :GXY2# FAN 1,2#
0.008 :GXY3# FAN 2,2#
0.008 :GXY4# Chauf 0,3#
0.008 :GXY5# Chauf 1,3#
0.009 :GXY6# Chauf 2,3#
0.008 :GXY7# Chauf 3,3#
0.006 :%BD# 0#
0.006 :%BR# 0#
0.008 :GX90# 1.00#
0.008 :GX95# 0#
0.006 :GX96# B#
0.007 :GXE9# 32#
0.007 :GXEA# 32#
0.007 :GX9A# 10.0#
0.007 :GX9C# 70.0#
0.008 :GX9B# 1010.0#
0.007 :GX9E# 4.0#
0.007 :GX9F# 177#
0.007 :GXU1# ,,,,,,#
0.008 :GXU2# ,,,,,,#
0.007 :A?# 900#
0.006 :GX02# 0#
0.007 :GX03# 0#
0.008 :GR# 10:23:39#
0.007 :GD# +90*00:00#
0.008 :GU# nNPHz/Eo260#
0.007 :%BD# 0#
0.006 :%BR# 0#
0.007 :GX90# 1.00#
0.009 :GX95# 0#
0.008 :GX96# B#
0.009 :GXE9# 32#
0.008 :GXEA# 32#
0.008 :GX9A# 10.0#
0.009 :GX9C# 70.0#
0.009 :GX9B# 1010.0#
0.009 :GX9E# 4.0#
0.009 :GXU1# ,,,,,,#
0.008 :GXU2# ,,,,,,#
0.008 :A?# 900#
0.010 :GX02# 0#
0.008 :GX03# 0#
0.008 :GR# 10:23:39#
0.008 :GD# +90*00:00#
0.007 :GU# nNPHz/Eo260#
0.006 :%BD# 0#
0.006 :%BR# 0#
0.007 :GX90# 1.00#
0.008 :GX95# 0#
0.007 :GX96# B#
0.007 :GXE9# 32#
0.006 :GXEA# 32#
0.007 :GX9A# 10.0#
0.008 :GX9C# 70.0#
0.007 :GX9B# 1010.0#
0.006 :GX9E# 4.0#
0.009 :GXU1# ,,,,,,#
0.007 :GXU2# ,,,,,,#
0.007 :A?# 900#
0.007 :GX02# 0#
0.007 :GX03# 0#
[code]
[/code]
Last edit: 2 years 5 months ago by Alain Zwingelstein.
2 years 5 months ago #77646
Attachments:

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

  • Posts: 322
  • Thank you received: 31

Replied by Khalid on topic Driver OnStep (LX200 like) for INDI

There is no delay over USB, because it is a low latency connection.

Can you try it over WiFi (SWS) AND include :rX commands for the rotator?

Alain/James,
See what Howard says here

onstep.groups.io/g/developer/message/2454
2 years 5 months ago #77647

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

  • Posts: 452
  • Thank you received: 71

Replied by Alain Zwingelstein on topic Driver OnStep (LX200 like) for INDI

Khalid,

My English must really be crap:
This is what I tried to say:
1) Make a diump of a working OnStep over USB
2) Used this dupm to send the same set of commands but over WiFi
then show the result.


the results I show are over WiFi, but with your script.
This is why I says WiFi is not the problem (meaning SMW).
The issue is definitively inside Indi

which ":rb" commands should we test?
Last edit: 2 years 5 months ago by Alain Zwingelstein. Reason: Tried to make miself more understandable
2 years 5 months ago #77648

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

  • Posts: 322
  • Thank you received: 31

Replied by Khalid on topic Driver OnStep (LX200 like) for INDI

So you got SWS working? That is good.

Here is a partial output in my case for the devices that do not exist.

0.050 :FA# 0
0.050 :fA# 0
0.070 :F1A# 0
0.050 :F2A# 0
0.050 :F3A# 0
0.069 :F4A# 0
0.267 :F5A# 0
0.153 :F6A# 0
0.169 :F7A# 0
0.233 :F8A# 0
0.147 :F9A# 0
0.267 :rG# 0
0.053 :GXY0# 10000000#
0.050 :GXY1# Dew 1,2#
0.152 :GXY2# 0
0.287 :GXY3# 0
0.150 :GXY4# 0
0.149 :GXY5# 0
0.170 :GXY6# 0
0.216 :GXY7# 0

You can see that the base line is 0.05 seconds, and not as fast as what you are seeing. Maybe it is my network? But that is not important.

What is important is that we have 0.2 or more seconds on some commands.

Basically Howard says:

:GX98# is for rotator detection.
Returns:

R# for a rotator
D# for a rotator and derotator
N# if disabled

So that should be the probe.

He also talks about timeouts and boolean returns for devices that do not exist. Please review.
2 years 5 months ago #77649

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

Time to create page: 0.734 seconds