Community
cancel
Showing results for 
Search instead for 
Did you mean: 
DMadi
New Contributor I
2,258 Views

ping much slower

I've noticed that the ping time running the Intel Aero v1.3.1 O/S was about 1ms when pinging the drone from a PC. After upgrading to the Intel Aero v1.6 O/S, the ping times are now around 100ms. The new ping times are surprisingly slow. In fact, sometimes it fails to ping. Others at our company (at a different office) noticed the same change when upgrading to v1.6. Is this an expected change from v1.3.1 to v1.6? Our drone information is:

BIOS_VERSION = Aero-01.00.13

OS_VERSION = Poky Aero (Intel Aero Linux Distro) 1.6.0 (pyro)"

AIRMAP_VERSION = 1.8

Regards,

Dan

0 Kudos
7 Replies
idata
Community Manager
66 Views

Hi DanMadill,

 

 

I would like to run a test with a similar setup as yours. Are you using Aero as a access point or is the Aero drone connected to a router?

 

 

Also, we have released v1.6.1 with an updated iwlwifi firmware, are you seeing similar behavior as in 1.6.0?

 

https://downloadcenter.intel.com/download/27399/Intel-Aero-Platform-for-UAVs-Installation-Files?v=t

 

 

Regards,

 

Jesus
DMadi
New Contributor I
66 Views

Hello Jesus,

We are using the Aero connected to a router and it gets its IP address via DHCP. I updated to v1.6.1 so I'm using the latest O/S now:

BIOS_VERSION = Aero-01.00.13

OS_VERSION = Poky Aero (Intel Aero Linux Distro) 1.6.1 (pyro)"

AIRMAP_VERSION = 1.8

I also confirmed with an older unit running v1.3.1 that the ping times on that unit are fast in both directions.

Ping from PC to Aero:

Pinging 192.168.111.118 with 32 bytes of data:

Reply from 192.168.111.118: bytes=32 time=98ms TTL=64

Reply from 192.168.111.118: bytes=32 time=118ms TTL=64

Reply from 192.168.111.118: bytes=32 time=138ms TTL=64

Reply from 192.168.111.118: bytes=32 time=159ms TTL=64

Reply from 192.168.111.118: bytes=32 time=179ms TTL=64

Reply from 192.168.111.118: bytes=32 time=200ms TTL=64

Reply from 192.168.111.118: bytes=32 time=17ms TTL=64

Reply from 192.168.111.118: bytes=32 time=37ms TTL=64

Reply from 192.168.111.118: bytes=32 time=58ms TTL=64

Reply from 192.168.111.118: bytes=32 time=79ms TTL=64

Reply from 192.168.111.118: bytes=32 time=100ms TTL=64

Reply from 192.168.111.118: bytes=32 time<1ms TTL=64

Reply from 192.168.111.118: bytes=32 time=143ms TTL=64

Reply from 192.168.111.118: bytes=32 time=164ms TTL=64

Reply from 192.168.111.118: bytes=32 time=184ms TTL=64

Reply from 192.168.111.118: bytes=32 time=205ms TTL=64

Reply from 192.168.111.118: bytes=32 time=21ms TTL=64

Reply from 192.168.111.118: bytes=32 time=41ms TTL=64

Reply from 192.168.111.118: bytes=32 time=63ms TTL=64

Reply from 192.168.111.118: bytes=32 time=85ms TTL=64

Reply from 192.168.111.118: bytes=32 time=105ms TTL=64

Reply from 192.168.111.118: bytes=32 time=127ms TTL=64

Reply from 192.168.111.118: bytes=32 time=149ms TTL=64

Reply from 192.168.111.118: bytes=32 time=1ms TTL=64

Reply from 192.168.111.118: bytes=32 time=196ms TTL=64

Ping statistics for 192.168.111.118:

Packets: Sent = 25, Received = 25, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 205ms, Average = 106ms

Ping from Aero to PC:

root@intel-aero:~# ping 192.168.111.121

PING 192.168.111.121 (192.168.111.121) 56(84) bytes of data.

64 bytes from 192.168.111.121: icmp_seq=1 ttl=128 time=1.25 ms

64 bytes from 192.168.111.121: icmp_seq=2 ttl=128 time=3.02 ms

64 bytes from 192.168.111.121: icmp_seq=3 ttl=128 time=1.90 ms

64 bytes from 192.168.111.121: icmp_seq=4 ttl=128 time=2.67 ms

64 bytes from 192.168.111.121: icmp_seq=5 ttl=128 time=2.61 ms

64 bytes from 192.168.111.121: icmp_seq=6 ttl=128 time=2.87 ms

64 bytes from 192.168.111.121: icmp_seq=7 ttl=128 time=2.22 ms

64 bytes from 192.168.111.121: icmp_seq=8 ttl=128 time=2.69 ms

64 bytes from 192.168.111.121: icmp_seq=9 ttl=128 time=1.22 ms

64 bytes from 192.168.111.121: icmp_seq=10 ttl=128 time=1.90 ms

64 bytes from 192.168.111.121: icmp_seq=11 ttl=128 time=2.77 ms

64 bytes from 192.168.111.121: icmp_seq=12 ttl=128 time=2.06 ms

64 bytes from 192.168.111.121: icmp_seq=13 ttl=128 time=3.32 ms

64 bytes from 192.168.111.121: icmp_seq=14 ttl=128 time=10.0 ms

64 bytes from 192.168.111.121: icmp_seq=15 ttl=128 time=3.23 ms

64 bytes from 192.168.111.121: icmp_seq=16 ttl=128 time=2.31 ms

64 bytes from 192.168.111.121: icmp_seq=17 ttl=128 time=3.17 ms

^C

--- 192.168.111.121 ping statistics ---

17 packets transmitted, 17 received, 0% packet loss, time 16027ms

rtt min/avg/max/mdev = 1.221/2.903/10.070/1.894 ms

Regards,

Dan

idata
Community Manager
66 Views

Hi Dan,

 

 

I did a quick test from my end and I obtained about 3-4 ms average ping time both ways. I'm not sure if this is specific to your network setup. I did the test with two different Aero RTF Drones.

 

 

Regards,

 

Jesus
DMadi
New Contributor I
66 Views

Hi Jesus,

Thank you for doing the test. The odd thing is that an Intel Aero Compute board running v1.3.1 obtains a fast ping time both ways and one running v1.6.1 does not, and both are on the same network, so I thought that ruled out the network setup. We've also seen the same issue on more than one network. Anyways, thanks for trying. If you happen to think of anything in a network setup that might cause this, please let me know.

Best regards,

Dan

idata
Community Manager
66 Views

Hi Dan,

 

 

My other suggestion would be to test your network using iperf instead of ping. iperf should give you a more accurate measurement. Although, iperf is not included in software release and you may need to build it from source.

 

 

Regards,

 

Jesus
DMadi
New Contributor I
66 Views

Hi Jesus,

Here are the results from iperf3.1.3:

Windows PC Side:

PS K:\Users\dmadill\Downloads\Applications\Open-Source\IPerf3\iperf-3.1.3-win64> .\iperf3.exe --server --port 18000

-----------------------------------------------------------

Server listening on 18000

-----------------------------------------------------------

Accepted connection from 192.168.111.118, port 33868

[ 5] local 192.168.111.121 port 18000 connected to 192.168.111.118 port 33870

[ ID] Interval Transfer Bandwidth

[ 5] 0.00-1.00 sec 6.83 MBytes 57.3 Mbits/sec

[ 5] 1.00-2.00 sec 8.25 MBytes 69.2 Mbits/sec

[ 5] 2.00-3.00 sec 8.12 MBytes 68.2 Mbits/sec

[ 5] 3.00-4.00 sec 8.27 MBytes 69.4 Mbits/sec

[ 5] 4.00-5.00 sec 8.45 MBytes 70.9 Mbits/sec

[ 5] 5.00-6.00 sec 8.69 MBytes 72.9 Mbits/sec

[ 5] 6.00-7.00 sec 8.85 MBytes 74.2 Mbits/sec

[ 5] 7.00-8.00 sec 9.99 MBytes 83.8 Mbits/sec

[ 5] 8.00-9.00 sec 10.3 MBytes 86.0 Mbits/sec

[ 5] 9.00-10.00 sec 9.94 MBytes 83.3 Mbits/sec

[ 5] 10.00-11.00 sec 9.98 MBytes 83.7 Mbits/sec

[ 5] 11.00-12.00 sec 9.88 MBytes 82.8 Mbits/sec

[ 5] 12.00-13.00 sec 10.1 MBytes 84.4 Mbits/sec

[ 5] 13.00-14.00 sec 10.2 MBytes 85.3 Mbits/sec

[ 5] 14.00-15.00 sec 10.7 MBytes 89.5 Mbits/sec

[ 5] 15.00-16.00 sec 10.3 MBytes 86.6 Mbits/sec

[ 5] 16.00-17.00 sec 10.7 MBytes 90.0 Mbits/sec

[ 5] 17.00-18.00 sec 10.4 MBytes 87.1 Mbits/sec

[ 5] 18.00-19.00 sec 10.2 MBytes 85.7 Mbits/sec

[ 5] 19.00-20.00 sec 10.3 MBytes 86.0 Mbits/sec

[ 5] 20.00-20.03 sec 368 KBytes 86.6 Mbits/sec

- - - - - - - - - - - - - - - - - - - - - - - - -

[ ID] Interval Transfer Bandwidth

[ 5] 0.00-20.03 sec 0.00 Bytes 0.00 bits/sec sender

[ 5] 0.00-20.03 sec 191 MBytes 79.8 Mbits/sec receiver

-----------------------------------------------------------

Server listening on 18000

-----------------------------------------------------------

iperf3: interrupt - the server has terminated

PS K:\Users\dmadill\Downloads\Applications\Open-Source\IPerf3\iperf-3.1.3-win64> .\iperf3.exe --client 192.168.111.118 -

-port 18000 --time 20

Connecting to host 192.168.111.118, port 18000

[ 4] local 192.168.111.121 port 51203 connected to 192.168.111.118 port 18000

[ ID] Interval Transfer Bandwidth

[ 4] 0.00-1.00 sec 28.1 MBytes 236 Mbits/sec

[ 4] 1.00-2.00 sec 31.8 MBytes 266 Mbits/sec

[ 4] 2.00-3.00 sec 29.1 MBytes 244 Mbits/sec

[ 4] 3.00-4.00 sec 31.1 MBytes 261 Mbits/sec

[ 4] 4.00-5.00 sec 28.0 MBytes 235 Mbits/sec

[ 4] 5.00-6.00 sec 26.1 MBytes 219 Mbits/sec

[ 4] 6.00-7.00 sec 29.5 MBytes 247 Mbits/sec

[ 4] 7.00-8.00 sec 32.4 MBytes 272 Mbits/sec

[ 4] 8.00-9.00 sec 25.9 MBytes 217 Mbits/sec

[ 4] 9.00-10.00 sec 9.50 MBytes 79.7 Mbits/sec

[ 4] 10.00-11.00 sec 27.6 MBytes 232 Mbits/sec

[ 4] 11.00-12.00 sec 30.6 MBytes 257 Mbits/sec

[ 4] 12.00-13.00 sec 31.5 MBytes 264 Mbits/sec

[ 4] 13.00-14.00 sec 32.1 MBytes 270 Mbits/sec

[ 4] 14.00-15.00 sec 22.0 MBytes 185 Mbits/sec

[ 4] 15.00-16.00 sec 30.1 MBytes 253 Mbits/sec

[ 4] 16.00-17.00 sec 31.6 MBytes 265 Mbits/sec

[ 4] 17.00-18.00 sec 27.5 MBytes 231 Mbits/sec

[ 4] 18.00-19.00 sec 25.6 MBytes 215 Mbits/sec

[ 4] 19.00-20.00 sec 26.6 MBytes 223 Mbits/sec

- - - - - - - - - - - - - - - - - - - - - - - - -

[ ID] Interval Transfer Bandwidth

[ 4] 0.00-20.00 sec 557 MBytes 234 Mbits/sec sender

[ 4] 0.00-20.00 sec 557 MBytes 234 Mbits/sec receiver

iperf Done.

PS K:\Users\dmadill\Downloads\Applications\Open-Source\IPerf3\iperf-3.1.3-win64>

Intel Aero Side:

root@dan-aero1:~/tools# iperf3 --client 192.168.111.121 --port 18000 --time 20

Connecting to host 192.168.111.121, port 18000

[ 4] local 192.168.111.118 port 33870 connected to 192.168.111.121 port 18000

[ ID] Interval Transfer Bandwidth Retr Cwnd

[ 4] 0.00-1.00 sec 7.28 MBytes 61.0 Mbits/sec 0 82.7 KBytes

[ 4] 1.00-2.00 sec 8.25 MBytes 69.2 Mbits/sec 0 101 KBytes

[ 4] 2.00-3.00 sec 8.19 MBytes 68.7 Mbits/sec 0 118 KBytes

[ 4] 3.00-4.00 sec 8.28 MBytes 69.5 Mbits/sec 0 137 KBytes

[ 4] 4.00-5.00 sec 8.54 MBytes 71.7 Mbits/sec 0 151 KBytes

[ 4] 5.00-6.00 sec 8.70 MBytes 73.0 Mbits/sec 0 151 KBytes

[ 4] 6.00-7.00 sec 8.79 MBytes 73.8 Mbits/sec 0 151 KBytes

[ 4] 7.00-8.00 sec 10.2 MBytes 85.3 Mbits/sec 0 221 KBytes

[ 4] 8.00-9.00 sec 10.2 MBytes 85.8 Mbits/sec 0 221 KBytes

[ 4] 9.00-10.00 sec 9.96 MBytes 83.6 Mbits/sec 0 221 KBytes

[ 4] 10.00-11.00 sec 9.97 MBytes 83.6 Mbits/sec 0 221 KBytes

[ 4] 11.00-12.00 sec 9.89 MBytes 83.0 Mbits/sec 0 221 KBytes

[ 4] 12.00-13.00 sec 10.1 MBytes 84.5 Mbits/sec 0 221 KBytes

[ 4] 13.00-14.00 sec 10.2 MBytes 85.6 Mbits/sec 0 221 KBytes

[ 4] 14.00-15.00 sec 10.7 MBytes 89.4 Mbits/sec 0 221 KBytes

[ 4] 15.00-16.00 sec 10.3 MBytes 86.2 Mbits/sec 0 221 KBytes

[ 4] 16.00-17.00 sec 10.6 MBytes 89.3 Mbits/sec 0 221 KBytes

[ 4] 17.00-18.00 sec 10.5 MBytes 88.3 Mbits/sec 0 221 KBytes

[ 4] 18.00-19.00 sec 10.2 MBytes 85.2 Mbits/sec 0 221 KBytes

[ 4] 19.00-20.00 sec 10.3 MBytes 86.2 Mbits/sec 0 221 KBytes

- - - - - - - - - - - - - - - - - - - - - - - - -

[ ID] Interval Transfer Bandwidth Retr

[ 4] 0.00-20.00 sec 191 MBytes 80.1 Mbits/sec 0 sender

[ 4] 0.00-20.00 sec 191 MBytes 80.0 Mbits/sec receiver

iperf Done.

root@dan-aero1:~/tools# iperf3 --server --port 18000

-----------------------------------------------------------

Server listening on 18000

-----------------------------------------------------------

Accepted connection from 192.168.111.121, port 51202

[ 5] local 192.168.111.118 port 18000 connected to 192.168.111.121 port 51203

[ ID] Interval Transfer Bandwidth

[ 5] 0.00-1.00 sec 27.1 MBytes 228 Mbits/sec

[ 5] 1.00-2.00 sec 31.7 MBytes 266 Mbits/sec

[ 5] 2.00-3.00 sec 29.1 MBytes 244 Mbi...

idata
Community Manager
66 Views

Hi Dan,

 

 

It may be a setting on Windows as I did a test and got ~200 MBits/sec when Aero is the client and ~170 MBits/sec when Aero is the server. I'm glad you are getting better measurements using iperf. Let me know if you have additional question regarding this topic.

 

 

Regards,

 

Jesus
Reply