Revision history [back]

I don't know about tum_simulator, but with actual ARDrones the issue may be with duplicate IP addresses between the two drones. I don't have two drones to mess around with though, so I can't test or confirm any of this.

The ARDrone SDK says the following:

The AR.Drone 2.0 can be controlled from any client device supporting Wifi. The following process is followed :

1. the AR.Drone creates a WIFI network with an ESSID usually called adrone2_xxx (ardrone_xxx for AR.Drone 1.0 ) and self allocates a free, odd IP address (typically 192.168.1.1).
2. the user connects the client device to this ESSID network.
3. the client device requests an IP address from the drone DHCP server.

4. the AR.Drone DHCP server grants the client with an IP address which is:

   the drone own IP address plus 1 (for AR.Drone 1.0 prior to version 1.1.3)

   the drone own IP address plus a number between 1 and 4 (for AR.Drone 2.0 and AR.Drone 1.0 after 1.1.3 version)

5. the client device can start sending requests the AR.Drone IP address and its services ports