AutonomyLab/ardrone_autonomy

Stuck at "Getting ARDrone.Version"

Closed this issue · 10 comments

Hi

I am running code on ARDrone 2.0. I am able to test fine with a compiled ardrone SDK, but when I test ROS, the code gets stuck at "Getting ARDrone.Version." I have tried looking in to the issue.
Any advice on how to debug this?

Can you paste all you got in the console?

  1. Can you ping/telnet to your AR-Drone from the command line:
$ ping 192.168.1.1
$ telnet 192.168.1.1
  1. Is your computer connected to multiple networks with the same IP range
    as the drone (192.168.1.x)?
    On Mar 3, 2016 3:36 AM, "Riccardo Polvara" notifications@github.com wrote:

Can you paste all you got in the console?


Reply to this email directly or view it on GitHub
#178 (comment)
.

I am able to do ping the drone - yes. Even control it with Linux SDK that comes with the AR drone. Just ROS doesn't work

@achowdhery How about telnet? Does it work? Could you please paste the output of ifconfig command on your machine? (Please remove any public IP information before pasting)

Having the same issue here on one Ubuntu machine. We can connect via. telnet and get the busybox prompt. We are able to connect from other machines, even Ubuntu/Xubuntu too.

Update: We could suddenly connect after trying with telnet 192.168.1.1 and pinging ? Not sure what make the difference ?

Update: We could suddenly connect after trying with telnet 192.168.1.1 and pinging ? Not sure what make the difference ?

Is this computer connected to multiple networks?

Closing this issue due to inactivity. Please feel free to re-open it in case you have any new update,

Hi, I'm having the same problem!! I disconnected my wired connection and still get the message "Getting AR.Drone Version ...". I don't quite know what to do next.

@lilyospina What is the output of ifconfig on your machine? (Please remove any public IP information from the output before sharing it here). Can you ping 192.168.1.1 successfully?

Hi I am also getting this issue (running on ARDrone 1.0):

  • I can ping 192.168.1.1 successfully
  • I cannot telnet (terminal asks me for a password)
  • This is the output of running ip:
    3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 00:1b:21:5b:ef:d1 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.10/24 brd 192.168.1.255 scope global eth1
    valid_lft forever preferred_lft forever
    inet6 fe80::21b:21ff:fe5b:efd1/64 scope link
    valid_lft forever preferred_lft forever