Slow RTT on Ping to ESP32 #1484

janneslr · 2018-06-11T18:03:49Z

Hi, is there any reason why I have such a slow Round Trip Time on a ping to my ESP32. It varies from 1ms to 700ms and sometime timeouts. Anyone else with this problem?
Reply from 10.168.3.181: bytes=32 time=119ms TTL=255
Reply from 10.168.3.181: bytes=32 time=25ms TTL=255
Reply from 10.168.3.181: bytes=32 time=67ms TTL=255
Reply from 10.168.3.181: bytes=32 time=87ms TTL=255
Reply from 10.168.3.181: bytes=32 time=103ms TTL=255
Reply from 10.168.3.181: bytes=32 time=102ms TTL=255
Reply from 10.168.3.181: bytes=32 time=115ms TTL=255
Reply from 10.168.3.181: bytes=32 time=24ms TTL=255
Reply from 10.168.3.181: bytes=32 time=43ms TTL=255
Reply from 10.168.3.181: bytes=32 time=49ms TTL=255
Reply from 10.168.3.181: bytes=32 time=63ms TTL=255
Reply from 10.168.3.181: bytes=32 time=84ms TTL=255
Reply from 10.168.3.181: bytes=32 time=112ms TTL=255
Reply from 10.168.3.181: bytes=32 time=94ms TTL=255
Reply from 10.168.3.181: bytes=32 time=142ms TTL=255
Reply from 10.168.3.181: bytes=32 time=21ms TTL=255

See the averages:
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 1037ms, Average = 64ms

If I compare to my ESP8266:
Reply from 10.168.3.114: bytes=32 time=4ms TTL=128
Reply from 10.168.3.114: bytes=32 time=13ms TTL=128
Reply from 10.168.3.114: bytes=32 time=6ms TTL=128
Reply from 10.168.3.114: bytes=32 time=3ms TTL=128
Reply from 10.168.3.114: bytes=32 time=3ms TTL=128
Reply from 10.168.3.114: bytes=32 time=4ms TTL=128
Reply from 10.168.3.114: bytes=32 time=8ms TTL=128
Reply from 10.168.3.114: bytes=32 time=5ms TTL=128
Reply from 10.168.3.114: bytes=32 time=17ms TTL=128
Reply from 10.168.3.114: bytes=32 time=4ms TTL=128

Approximate round trip times in milli-seconds:
Minimum = 3ms, Maximum = 17ms, Average = 6ms

enly1 · 2018-06-12T18:38:52Z

Just started playing with an ESP32 and have similar performance ( 50 cm from wifi router )

64 bytes from 192.168.1.97: icmp_seq=57 ttl=255 time=194 ms
64 bytes from 192.168.1.97: icmp_seq=58 ttl=255 time=115 ms
64 bytes from 192.168.1.97: icmp_seq=59 ttl=255 time=36.0 ms
64 bytes from 192.168.1.97: icmp_seq=60 ttl=255 time=266 ms
64 bytes from 192.168.1.97: icmp_seq=61 ttl=255 time=184 ms
64 bytes from 192.168.1.97: icmp_seq=62 ttl=255 time=102 ms
64 bytes from 192.168.1.97: icmp_seq=63 ttl=255 time=22.2 ms
64 bytes from 192.168.1.97: icmp_seq=64 ttl=255 time=250 ms
64 bytes from 192.168.1.97: icmp_seq=65 ttl=255 time=170 ms
64 bytes from 192.168.1.97: icmp_seq=66 ttl=255 time=89.6 ms
64 bytes from 192.168.1.97: icmp_seq=67 ttl=255 time=319 ms
64 bytes from 192.168.1.97: icmp_seq=68 ttl=255 time=245 ms
64 bytes from 192.168.1.97: icmp_seq=69 ttl=255 time=164 ms
64 bytes from 192.168.1.97: icmp_seq=70 ttl=255 time=81.0 ms
64 bytes from 192.168.1.97: icmp_seq=71 ttl=255 time=311 ms
64 bytes from 192.168.1.97: icmp_seq=72 ttl=255 time=230 ms
64 bytes from 192.168.1.97: icmp_seq=73 ttl=255 time=154 ms
64 bytes from 192.168.1.97: icmp_seq=74 ttl=255 time=71.6 ms
64 bytes from 192.168.1.97: icmp_seq=75 ttl=255 time=299 ms
64 bytes from 192.168.1.97: icmp_seq=76 ttl=255 time=220 ms
64 bytes from 192.168.1.97: icmp_seq=77 ttl=255 time=141 ms
64 bytes from 192.168.1.97: icmp_seq=78 ttl=255 time=62.3 ms
64 bytes from 192.168.1.97: icmp_seq=79 ttl=255 time=288 ms
64 bytes from 192.168.1.97: icmp_seq=80 ttl=255 time=209 ms
64 bytes from 192.168.1.97: icmp_seq=81 ttl=255 time=131

Running Simple Wifi Server example sketch on Arduino.

1163167506 · 2018-06-13T03:54:51Z

ye
You and I have the same problem.

I and espressif official trench admit that esp32 has this problem through them.

But I don't have time to wait for the official solution.

Can anyone offer good advice

1163167506 · 2018-06-19T03:27:38Z

I solved this problem
Because esp32 enters the power saving mode by default, just set it up.

WiFi.mode (WIFI_STA);

Esp_wifi_set_ps (WIFI_PS_NONE);

WiFi.begin (ssid3, password3);

janneslr · 2018-06-19T06:27:09Z

I can confirm adding the Esp_wifi_set_ps (WIFI_PS_NONE); line of code worked. Thanks!!!

lbernstone · 2018-06-21T18:51:33Z

If it is fixed, please close the issue.

me-no-dev · 2018-06-21T20:31:07Z

it worked but it consumes more power ;) in essence you are keeping the esp awake and wifi on all of the time

SteveAmor · 2018-07-29T15:26:42Z

To use esp_wifi_set_ps (WIFI_PS_NONE); you also need #include "esp_wifi.h" (worked for me in Arduino IDE).

lbernstone · 2018-07-29T17:14:25Z

If you use WiFi.setSleep(false), you will need no additional libraries.

Uksa007 · 2018-07-31T02:14:38Z

I noticed I have this issue also, confirmed that turning off the power save fixes the issue, but it seems like a bit of a hack.

I note that on my ESP8266 the Wifi power save is automatically turned off when the ESP8266 is communitcing over the WIFI and then turned back on again, which make sense to me, and is how most Wifi devices work.
Why does the ESP32 WIFI not fuction in this way?

vinot · 2019-07-12T10:02:30Z

Hi all,

thank you a lot for the solution, was frustrating those 200ms ping...

yrs

toni

dao89 · 2019-07-13T20:48:38Z

I noticed I have this issue also, confirmed that turning off the power save fixes the issue, but it seems like a bit of a hack.

I note that on my ESP8266 the Wifi power save is automatically turned off when the ESP8266 is communitcing over the WIFI and then turned back on again, which make sense to me, and is how most Wifi devices work.
Why does the ESP32 WIFI not fuction in this way?

One year past, but ESP32 still very slow when power saving not disabled. When disabled, it consumes twice more power! esp8266 doesn't have such problem... It is very sad.
Maybe there is some solution?

stale · 2019-09-11T21:23:50Z

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions.

stale · 2019-09-25T22:14:39Z

[STALE_DEL] This stale issue has been automatically closed. Thank you for your contributions.

YordanYanakiev · 2020-01-13T23:09:28Z

It turns out that this resoled actually ALL of the issues connected to the WebServer random connection drops. So - link this topic to all of such issues. It most likely if not solve totally it will at lease easy the problem.

before: ``` $ ping 192.168.1.17 PING 192.168.1.17 (192.168.1.17) 56(84) bytes of data. 64 bytes from 192.168.1.17: icmp_seq=1 ttl=255 time=82.1 ms 64 bytes from 192.168.1.17: icmp_seq=3 ttl=255 time=81.0 ms 64 bytes from 192.168.1.17: icmp_seq=5 ttl=255 time=1410 ms 64 bytes from 192.168.1.17: icmp_seq=6 ttl=255 time=386 ms ``` after: ``` $ ping 192.168.1.17 PING 192.168.1.17 (192.168.1.17) 56(84) bytes of data. 64 bytes from 192.168.1.17: icmp_seq=1 ttl=255 time=159 ms 64 bytes from 192.168.1.17: icmp_seq=2 ttl=255 time=9.77 ms 64 bytes from 192.168.1.17: icmp_seq=3 ttl=255 time=5.81 ms 64 bytes from 192.168.1.17: icmp_seq=4 ttl=255 time=48.0 ms 64 bytes from 192.168.1.17: icmp_seq=5 ttl=255 time=6.70 ms 64 bytes from 192.168.1.17: icmp_seq=6 ttl=255 time=6.36 ms ``` see also: espressif/arduino-esp32#1484

LockonS · 2021-09-03T20:01:26Z

If you use WiFi.setSleep(false), you will need no additional libraries.

WORKS LIKE A CHARM! Thannk you so much.

mbratch · 2022-03-29T12:19:20Z

The ping response on my ESP32 running with ESP-IDF 4.4 seems to be relatively long and vary quite a bit. Unclear why this is the case.

gonzabrusco · 2022-04-29T18:12:44Z

The correct way to do this is WiFi.setSleep(WIFI_PS_NONE);

The wifi energy saving options are:

 WIFI_PS_NONE,        /**< No power save */
 WIFI_PS_MIN_MODEM,   /**< Minimum modem power saving. In this mode, station wakes up to receive beacon every DTIM period */
 WIFI_PS_MAX_MODEM,   /**< Maximum modem power saving. In this mode, interval to receive beacons is determined by the listen_interval parameter in wifi_sta_config_t */

mbratch · 2022-04-29T19:16:37Z

The correct way to do this is WiFi.setSleep(WIFI_PS_NONE);

That's using the Arduino WiFi library. I am not using Arduino, but rather ESP-IDF.

For ESP-IDF, the correct call is esp_wifi_set_ps(WIFI_PS_NONE); This is what I am using and I still observe slower ping responses than I would have expected.

gonzabrusco · 2022-04-30T14:59:45Z

The correct way to do this is WiFi.setSleep(WIFI_PS_NONE);

That's using the Arduino WiFi library. I am not using Arduino, but rather ESP-IDF.

For ESP-IDF, the correct call is esp_wifi_set_ps(WIFI_PS_NONE); This is what I am using and I still observe slower ping responses than I would have expected.

Well, this is the arduino-esp32 repository, thus my comment is directed to Arduino users. If you have a problem with IDF, you better submit an issue in the IDF repository (https://github.com/espressif/esp-idf)

mbratch · 2022-04-30T15:05:46Z

@gonzabrusco ha indeed. I've been working with several esp32 related repositories lately and got my wires crossed a little! My apologies.

Under the hood, as it were, the Arduino library probably calls the esp-idf API. Definitely not an Arduino specific issue

gonzabrusco · 2022-04-30T15:53:05Z

@gonzabrusco ha indeed. I've been working with several esp32 related repositories lately and got my wires crossed a little! My apologies.

Under the hood, as it were, the Arduino library probably calls the esp-idf API. Definitely not an Arduino specific issue

No need to apologize! Yes, actually Arduino calls the IDF function you menctioned.

arduino-esp32/libraries/WiFi/src/WiFiGeneric.cpp

Line 1162 in ce2cd11

if(esp_wifi_set_ps(_sleepEnabled) != ESP_OK){

But now that I see, the function that accepts a boolean (as mentioned previously) actually exists too!

arduino-esp32/libraries/WiFi/src/WiFiGeneric.cpp

Line 1148 in ce2cd11

bool WiFiGenericClass::setSleep(bool enabled){

But it let's you only chose between two types of energy savings (off or minimal).

hapklaar mentioned this issue Mar 22, 2019

ESP32 wifi power save shmuelzon/esp32-ble2mqtt#29

Closed

vinot mentioned this issue Jul 12, 2019

Slow ping on ESP32 me-no-dev/ESPAsyncWebServer#548

Closed

vinot mentioned this issue Jul 16, 2019

Is there a fix to "This site can’t be reached" ? me-no-dev/ESPAsyncWebServer#536

Closed

stale bot added the Status: Stale Issue is stale stage (outdated/stuck) label Sep 11, 2019

stale bot closed this as completed Sep 25, 2019

tschundler mentioned this issue Dec 19, 2020

Disable WiFi power savings for more responsiveness bdring/Grbl_Esp32#713

Open

easytarget mentioned this issue Jun 8, 2021

Disable WiFi Powersave for better responsiveness easytarget/esp32-cam-webserver#123

Merged

DesertCat mentioned this issue Oct 17, 2021

High RTT (ping) on ESP32-based device arendst/Tasmota#13391

Closed

14 tasks

thomastech mentioned this issue Jan 9, 2022

Need Advice on Reducing Control Latency (improve response times) s00500/ESPUI#146

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Slow RTT on Ping to ESP32 #1484

Slow RTT on Ping to ESP32 #1484

janneslr commented Jun 11, 2018

enly1 commented Jun 12, 2018

1163167506 commented Jun 13, 2018

1163167506 commented Jun 19, 2018

janneslr commented Jun 19, 2018

lbernstone commented Jun 21, 2018

me-no-dev commented Jun 21, 2018

SteveAmor commented Jul 29, 2018 •

edited

Loading

lbernstone commented Jul 29, 2018

Uksa007 commented Jul 31, 2018

vinot commented Jul 12, 2019

dao89 commented Jul 13, 2019 •

edited

Loading

stale bot commented Sep 11, 2019

stale bot commented Sep 25, 2019

YordanYanakiev commented Jan 13, 2020

LockonS commented Sep 3, 2021

mbratch commented Mar 29, 2022 •

edited

Loading

gonzabrusco commented Apr 29, 2022

mbratch commented Apr 29, 2022

gonzabrusco commented Apr 30, 2022

mbratch commented Apr 30, 2022 •

edited

Loading

gonzabrusco commented Apr 30, 2022

Slow RTT on Ping to ESP32 #1484

Slow RTT on Ping to ESP32 #1484

Comments

janneslr commented Jun 11, 2018

enly1 commented Jun 12, 2018

1163167506 commented Jun 13, 2018

1163167506 commented Jun 19, 2018

janneslr commented Jun 19, 2018

lbernstone commented Jun 21, 2018

me-no-dev commented Jun 21, 2018

SteveAmor commented Jul 29, 2018 • edited Loading

lbernstone commented Jul 29, 2018

Uksa007 commented Jul 31, 2018

vinot commented Jul 12, 2019

dao89 commented Jul 13, 2019 • edited Loading

stale bot commented Sep 11, 2019

stale bot commented Sep 25, 2019

YordanYanakiev commented Jan 13, 2020

LockonS commented Sep 3, 2021

mbratch commented Mar 29, 2022 • edited Loading

gonzabrusco commented Apr 29, 2022

mbratch commented Apr 29, 2022

gonzabrusco commented Apr 30, 2022

mbratch commented Apr 30, 2022 • edited Loading

gonzabrusco commented Apr 30, 2022

SteveAmor commented Jul 29, 2018 •

edited

Loading

dao89 commented Jul 13, 2019 •

edited

Loading

mbratch commented Mar 29, 2022 •

edited

Loading

mbratch commented Apr 30, 2022 •

edited

Loading