charleslemaire0 / TeenAstro

an easy to build and use telescope controller
GNU General Public License v3.0
24 stars 22 forks source link

No TeenAstro responses by Wifi some hours later #74

Open MasterPIC opened 1 year ago

MasterPIC commented 1 year ago

Hi,

I'm having systematically no responses by Wifi some hours after connection has been established. If I try to reconnect by ASCOM I get no response or a brief connection after which the issue occurs again. If I reboot the WiFi module by SHC then connection can be established again.

Adding WiFi.setSleepMode(WiFiSleepType::WIFI_NONE_SLEEP); didn't help.

I'm using TeenAstro as a client connected to a router. The issue occurs on several routers. I'm tempted to think that as soon as a disconnection occurs it automatically reconnects but "not properly". In this case maybe an ESP reset could solve the issue.

MasterPIC commented 1 year ago

I'm making other tests.

MasterPIC commented 1 year ago

A simple ping makes it possible to reconnect by ASCOM without the need for an ESP reset. So as a workaround I think a periodic ping by any client on the lan should work. It should probably keep connection alive with no need to reconnect by ASCOM too. I'm going to check... Anyway I think something is to be fixed on the firmware side to solve the issue radically.

charleslemaire0 commented 1 year ago

Hi Armando, Great work please keep me informed if you find something!

MasterPIC commented 1 year ago

Hi Charles,

I confirm the issue can be solved by a periodic ping. I'm not at home but also by using a smartphone as hotspot, to connect TeenAstro to, I see after about 2 hours the controller doesn't answer to any command. I tried to add a periodic ping to the ASCOM driver and it seems to work. I mean to point out that the issue seems not occurring if the controller is set as an hotspot.

charleslemaire0 commented 9 months ago

Could you share your changes in the ASCOM driver

MasterPIC commented 9 months ago

Hi Charles,

with latest firmware I'm having no disconnection issues. But I'm currently testing it by a different router. And I see there are some parameters that can be involved (GTK rekeying and probably also station inactivity limit - both in seconds). I'm trying to reproduce the issue unsuccessfully. Anyway if you are currently able to reproduce the issue you can save the following lines in a bat file to execute it (by Windows) to periodically ping the device and check if it works also in your case. You should obviously edit the IP address.

@ECHO OFF
set IPADDRESS=192.168.0.2
set INTERVAL=300
:PINGINTERVAL
ping %IPADDRESS% -n 1
timeout %INTERVAL%
GOTO PINGINTERVAL

Please let me know the results.

CS Armando

MasterPIC commented 9 months ago

Hi Charles, feel free to close the issue if you also aren't able to reproduce the issue.

Thanks Armando