adpon
commented
7 years ago I have this exact problem as well. I'm using Ubuntu 16.04, no virtual machine as well. Bebop 2 software version 4.0.6
Open ghost opened 7 years ago
adpon
commented
7 years ago I have this exact problem as well. I'm using Ubuntu 16.04, no virtual machine as well. Bebop 2 software version 4.0.6
thomas-bamford
commented
7 years ago Hello,
Does this problem persist when the IP address is set to the default value 192.168.42.1?
Looking at the terminal output you are pinging a different IP than you have set in the parameters of the launch file (/bebop/bebop_driver/bebop_ip: 192.168.42.1).
ghost
commented
7 years ago Thank you for helping me out here.
My bad, i3status gives the Bebop WIFI connection as 192.168.42.28.
Pinging the default 192.168.42.1 gives:
me@computer-xubuntu:~$ ping 192.168.42.1
PING 192.168.42.1 (192.168.42.1) 56(84) bytes of data.
64 bytes from 192.168.42.1: icmp_seq=1 ttl=64 time=1.80 ms
64 bytes from 192.168.42.1: icmp_seq=2 ttl=64 time=3.68 ms
64 bytes from 192.168.42.1: icmp_seq=3 ttl=64 time=1.94 ms
64 bytes from 192.168.42.1: icmp_seq=4 ttl=64 time=2.17 ms
64 bytes from 192.168.42.1: icmp_seq=5 ttl=64 time=1.75 ms
64 bytes from 192.168.42.1: icmp_seq=6 ttl=64 time=1.77 ms
64 bytes from 192.168.42.1: icmp_seq=7 ttl=64 time=4.61 ms
64 bytes from 192.168.42.1: icmp_seq=8 ttl=64 time=1.97 ms
64 bytes from 192.168.42.1: icmp_seq=9 ttl=64 time=13.0 ms
64 bytes from 192.168.42.1: icmp_seq=10 ttl=64 time=2.17 ms
^C
--- 192.168.42.1 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9013ms
rtt min/avg/max/mdev = 1.757/3.497/13.077/3.319 msThis also seems like a reasonable connection.
After pressing the Bebop's power button four times, I can telnet into 192.168.42.1 but not 192.168.42.28, so I believe the drone is on the former.
thomas-bamford
commented
7 years ago You're welcome. Does i3status provide you with the IP of your computer on the Bebop's network? I am not familiar with this software. The default network of the Bebop is 192.168.42.1.
Some ideas for the disconnecting issue:
Please let me know how this goes, I will try to help as best I can.
ghost
commented
7 years ago i3status is a Linux statusbar that displays some useful information, including internet connection. I wouldn't trust it too much though.
We also tried resetting the drone to get back to the older firmware. The issue happens less often now, but still regularly (>1/2 of attempts).
More detailed connection information:
General
Interface: 802.11 WiFi (wlp3s0)
Driver: wl
Speed: 65 Mb/s
Security: WPA/WPA2
IPv4
IP Address: 192.168.42.28
Broadcast Address: 192.168.42.255
Subnet Mask: 255.255.255.0
Default Route: 192.168.42.1
IPv6
IP Address: fe80::b78d:eb37:be29:bccd/64Note that the computer does not have IPv6
This and this forum posts refer to the same error message, but using only the Parrot SDK, and not the bebop_autonomy driver. Is it possible that this is an upstream issue?
Thank you again for all the help, it is very much appreciated.
thomas-bamford
commented
7 years ago Hi @Adam-JW-Casey, sorry for the delayed reply, thank you for your patience. Thanks for trying out my suggestions, its unfortunate that they haven't resulted in a solution. It is possible this is an upstream issue since the ARNETWORK_Sender errors are raised by the SDK.
geforcexfx
commented
5 years ago Hi. is this problem fixed? I am having the same error when trying to connect to bebop 2. If yes, can you please show me how? Thanks
When running the driver using the included launch file, ie.
~$ roslaunch bebop_driver bebop_node.launch, the driver will very often crash, giving the errorTimeout waiting for ack in buffer 11, among other things.This does not occur every time the driver is run (sometimes it runs successfully) but it is very frequent (1/5 to 3/4 of attempts depending on the day).
We have also tried running as a nodelet instead, using
~$ roslaunch bebop_tools bebop_nodelet_iv.launch, for example, but have the same issue.The system is ROS Kinetic running on Xubuntu 16.04 (no virtual machine). The same issue occurs on a different machine with the same setup.
The drone is a Bebop 2 that works perfectly with the Free Flight Pro app and/or Skycontroller. I believe it is running the latest firmware, as of 05/07/2017
bebop_autonomy, branch indigo_devel, up-to-date as of commit 8801830. We have checked out various older commits on git, all of which suffer from the same issue.
We have used the ardrone_autonomy package many times without this issue, also on branch indigo_devel.
Restarting the computer and/or terminal does not fix the problem.
stdout:
Pinging the Bebop
The wifi is connected and seems to be rock solid.