×

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: 144
  • Thank you received: 7
Yes i use wifi of raspberry
1 year 2 months ago #90481

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

  • Posts: 452
  • Thank you received: 71
OK.

So I suppose Raspberry is running Indiserver and Kstars!
OnStep is connected to Raspberry over WiFi.
Do you also connect remotely to Raspberry via WiFi with VNC?
1 year 2 months ago #90482

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

  • Posts: 144
  • Thank you received: 7
Yes running Indi e kstars but now i'm trying indiweb manager.
Onstep is connected to raspberry over wifi.
For connection remotely i use vnc 64 bit.
Ettore
1 year 2 months ago #90484

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

  • Posts: 452
  • Thank you received: 71
This is most probably one of the cause of your network issue.
The Raspberry pi must route OnStep and VNC traffic which is not huge I agree, theoretically should be largely enough but by experience Raspberry Pi WiFi is not one of the best for that.
This is the reason Why I decide to go over Optical fiber finally.

I got this kind of problems in two scenarii:
Raspberry running IdI/Kstars and VNC for remote connection
and later
I tried Raspberry as a USB over IP server so taht I could remotely connect all devices as if they are connected to my remote machine.

In both case I got this WiFi Bottleneck .

Di you ever try wit an Ethernet cable for the remote VNC connection?

I know it is not a solution to your WiFi but a test to see if the problem remains
Last edit: 1 year 2 months ago by Alain Zwingelstein.
1 year 2 months ago #90485

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

  • Posts: 144
  • Thank you received: 7
I've never tried with a network cable, I'll try next week and see what happens.
Thanks.
Ettore
1 year 2 months ago #90486

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

  • Posts: 452
  • Thank you received: 71
Good luck,

keep in touch
1 year 2 months ago #90487

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

  • Posts: 144
  • Thank you received: 7
Sure.
Ettore
1 year 2 months ago #90488

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

  • Posts: 23
  • Thank you received: 2
Hello,

I have noticed INDI uses weather temperature for focusing control even though you have a separate telescope temperature sensor.
My OnStep web server shows those two different values in a right way - telescope temperature in the focuser section.
Also the ASCOM OnStep focuser driver seems to pass the right value.
Would it be possible to have it in INDI as well? Many thanks in advance.

Best regards,
Wieslaw
The following user(s) said Thank You: Alan Archer
1 year 1 month ago #90867

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

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

There is a weather tab in Onstep where temperature is displayed but I think it is the value of the BME280 sensor.
The values of the Auxiliary are all displayed in the Output tab if configured.
In principle everything is possible but for developing the specific needs one need the specific hardware, so I need to know what exactly your config is to understand and investigate.

Regards
1 year 1 month ago #90868

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

  • Posts: 23
  • Thank you received: 2
Hi Alain,

Thank you for your prompt response.
I wouldn't request any special stuff - my DS18B20 sensor is a standard for telescope temperature, I guess.

// FOCUSER TEMPERATURE
see onstep.groups.io/g/developer/wiki/Configuration_Rotator_Focuser
#define FOCUSER_TEMPERATURE DS18B20 // OFF, THERMISTOR or n. Where n is the ds18b20 s/n for focuser temp.

I have one MaxESP3 with BME280 weather sensor and DS18B20 telescope temp sensor and a custom board equipped with DS18B20 .

For both it would be great to havre the telescope temperature value in INDI.

If I could be of any help, let me know, please.
But unfortunately I have little experience with coding...

Best regards,
Wieslaw
Last edit: 1 year 1 month ago by Wieslaw Stawiski.
1 year 1 month ago #90870

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

  • Posts: 452
  • Thank you received: 71
Ok I see.

is this related to your question? indilib.org/forum/wish-list/11484-adding...ion-on-focusers.html
When I said specific I didn't mean something very special, just what type of hardware you have (sorry for my Frenglish :-)

I will have to set-up such a config, don't have a bme280 by hands ...
I hope my BluePill will accept the options , I am really at top of the available memory with my current config ...
At a first glance I would say you should find these values in the weather tab.
But I don't know is Ekos is aware of those values ...
As soon I can have a correct set-up ready I will check.
After I need to understand how Ekos is supposed to manage this stuff.
Last edit: 1 year 1 month ago by Alain Zwingelstein.
1 year 1 month ago #90872

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

  • Posts: 23
  • Thank you received: 2

Your English is just perfect, no worries :)

It is somehow related,
but for the focuser temperature compensation you can use either weather sensor (BME280) or telescope temp sensor (DS18B20) data.
My problem is that there is no way for the latter to be used, no matter if a weather sensor is present.

The expected behaviour: when there is a telescope temperature sensor, in the focuser context its data should be used.
(falling back to the weather sensor temp data, when there is no telescope temp sensor at hand would be also great).

When you like me to do some testing, just reach out to me. :)

Attachment not found



When there is no weather sensor the temperature value is nan.
Expected behaviour: when there is a telescope temp sensor its temperature value should be used in the focuser context.
1 year 1 month ago #90876

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

Time to create page: 0.601 seconds