AR.Drone problems

PX4 Autopilot Flight Controllers 💻
1

hi,
i am struggling getting my ar.drone working.
i cleared the mtd data using: mtd erase
the nsh shell works but not mavlink.

after updating the firmware i get the following error msg:

  • change of parameter SYS_AUTOSTART requires a vehicle reboot to take effect.

bow i am unable to calibrate the imu - just nothing happens.
in contrast, the pixhawk works.

any idea?

  • robert
2

no one !?! …

3

I don’t think a lot of these are actively used still. Is it feasible for you to connect a console and share the debug log?

4

thanks!
here bootlog.txt content:
ERROR [init] PX4IO update failed
ERROR [init] PX4IO not found
ERROR:[init] Could not load mixer: /etc/mixers/quad_x.main.mix
ERROR [init] PX4IO update failed
ERROR [init] PX4IO not found
ERROR:[init] Could not load mixer: /etc/mixers/quad_x.main.mix
ERROR [init] PX4IO update failed
ERROR [init] PX4IO not found
ERROR:[init] Could not load mixer: /etc/mixers/quad_x.main.mix
ERROR [init] PX4IO update failed
ERROR [init] PX4IO not found
ERROR:[init] Could not load mixer: /etc/mixers/quad_x.main.mix
ERROR [init] PX4IO update failed
ERROR [init] PX4IO not found
ERROR:[init] Could not load mixer: /etc/mixers/quad_x.main.mix
ERROR [init] PX4IO update failed
ERROR [init] PX4IO not found
ERROR:[init] Could not load mixer: /etc/mixers/quad_x.main.mix
ERROR [init] PX4IO update failed
ERROR [init] PX4IO not found
ERROR:[init] Could not load mixer: /etc/mixers/quad_x.main.mix

the rest a bit later.

  • robert
5

here the boot log when connecting my ftdi cable:

[boot] Enabling IN12/13 instead of SPI2
sercon: Registering CDC/ACM serial driver
sercon: Successfully registered the CDC/ACM serial driver
nsh: mount: mount failed: No such device
nsh: mkfatfs: mkfatfs failed: I/O error
WARN [param] selected parameter default file /fs/mtd_params
WARN [rgbled] no RGB led on bus #3
WARN [blinkm] I2C init failed
WARN [blinkm] init failed
WARN [dataman] Could not open data manager file /fs/microsd/dataman
ERROR [dataman] dataman start failed
INFO [ver] match: PX4FMU_V1
MS5611_I2C on I2C bus 2 at 0x76 (bus: 100 KHz, max: 400 KHz)
WARN [ms5611] no device on bus 2
INFO [ver] match: PX4FMU_V1
MPU6000 on SPI bus 1 at 3 (1000 KHz)
L3GD20 on SPI bus 1 at 1 (11000 KHz)
WARN [hmc5883] no device on bus 2
HMC5883_I2C on I2C bus 2 at 0x1e (bus: 100 KHz, max: 400 KHz)
ERROR [meas_airspeed] no MS4525 airspeed sensor connected
ERROR [ets_airspeed] no ETS airspeed sensor connected
ERROR [ets_airspeed] no ETS airspeed sensor connected
nsh: sf1xx: command not found
WARN [commander] No RGB LED found at /dev/rgbled0
WARN [param] Error: Parameter UAVCAN_ENABLE not found.
INFO [ver] match: PX4FMU_V1
INFO [mavlink] mode: Normal, data rate: 1200 B/s on /dev/ttyS0 @ 57600B
WARN [mavlink] hardware flow control not supported
INFO [ver] match: PX4FMU_V1
WARN [param] Error: Parameter UAVCAN_ENABLE not found.
WARN [param] Error: Parameter UAVCAN_ENABLE not found.
nshterm [141:70]
INFO [ver] match: PX4FMU_V1
WARN [sdlog2] ERR: statfs
WARN [sdlog2] ERR: MicroSD almost full
INFO [init] Multicopter
INFO [ver] match: PX4FMU_V1
WARN [local_position_estimator] starting
INFO [init] NSH exit

=== with sd-card inserted ===
sercon: Registering CDC/ACM serial driver
serconþ[boot] Enabling IN12/13 instead of SPI2
sercon: Registering CDC/ACM serial driver
sercon: Successfully registered the CDC/ACM serial driver
WARN [param] selected parameter default file /fs/mtd_params
WARN [rgbled] no RGB led on bus #3
WARN [blinkm] I2C init failed
WARN [blinkm] init failed
INFO [dataman] Unkown restart, data manager file ‘/fs/microsd/dataman’ size is 103090 bytes
INFO [ver] match: PX4FMU_V1
MS5611_I2C on I2C bus 2 at 0x76 (bus: 100 KHz, max: 400 KHz)
WARN [ms5611] no device on bus 2
INFO [ver] match: PX4FMU_V1
MPU6000 on SPI bus 1 at 3 (1000 KHz)
L3GD20 on SPI bus 1 at 1 (11000 KHz)
WARN [hmc5883] no device on bus 2
HMC5883_I2C on I2C bus 2 at 0x1e (bus: 100 KHz, max: 400 KHz)
ERROR [meas_airspeed] no MS4525 airspeed sensor connected
ERROR [ets_airspeed] no ETS airspeed sensor connected
ERROR [ets_airspeed] no ETS airspeed sensor connected
nsh: sf1xx: command not found
WARN [commander] No RGB LED found at /dev/rgbled0
WARN [param] Error: Parameter UAVCAN_ENABLE not found.
INFO [ver] match: PX4FMU_V1
INFO [mavlink] mode: Normal, data rate: 1200 B/s on /dev/ttyS0 @ 57600B
WARN [mavlink] hardware flow control not supported
INFO [ver] match: PX4FMU_V1
WARN [param] Error: Parameter UAVCAN_ENABLE not found.
WARN [param] Error: Parameter UAVCAN_ENABLE not found.
INFO [mavlink] mode: Config, data rate: 800000 B/s on /dev/ttyACM0 @ 57600B
INFO [ver] match: PX4FMU_V1
INFO [init] Multicopter
INFO [ver] match: PX4FMU_V1
WARN [local_position_estimator] starting
INFO [init] NSH exit

i am shure to have the ar.drone selected as flying vehicle.

  • robert
6

any news, or just too busy with new hw?

7

We do not have that hardware any more in operation and so we can’t really assist much with debugging it. It is out of production for a very long time. What you can try is to see if you ran out of free ram (with free). Other than that you would need to debug the boot process step by step. I can try to handhold that remotely but the logs you shared didn’t turn up anything that would be defined enough yet to give you any good pointers.