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

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

I've never tried with a network cable, I'll try next week and see what happens.
Thanks.
Ettore

Good luck,

keep in touch

Sure.
Ettore

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

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

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

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.

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.



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.

Right now there is nothing in Indi that provides this functionality.
The Focuser interface does not include temperature.
Most probably it should be implemented in the driver and provide an option to the user to use or not the compensation and may be the choice for for sensor to use.
But since it is not implemented at Ekos level (may be I am wrong, needs to be checked deeper) it would be difficult to avoid compensation during shooting but this should not occur since temperature is not a quick changing parameter.

OK I will start to look about this topic but it will take some time I have some other eggs on my fire next weeks ...

Doublechecking what Alain said, since there's a proposal in the thread, to confirm there's no way to have the focuser interface output temperature.

I've created a branch here

github.com/james-lan/indi/tree/focus_temperature

This should report it in the weather interface, but it won't be the main temperature. It would be possible to test it, and see if it was a good thing. (I'm very suspicious, I haven't touched the code in a while, and it compiled without error the first time.) If you can test that, we can at least report it and I can see about adding a button to swap it.

OnStep (maybe X only?), If I recall correctly also does the temperature compensation automatically. (Or can) I need to double check that statement, and I probably need to get some new hardware to test...