91Âþ»­

As the plane is closed we cannot download the dataflash logs anymore by removing the SD-Card from its slot.

Therefore a wireless method need to be found to get the data from the pixracer.

If not other noted, the baudrate is set to 115200.

1. Insert the ESP into the pixracer.
2. Download the latest Dailybuild from QGroundcontrol:
3. Download the latest firmware for mavesp:
4. Login into pixracer WIFI which is provided by the ESP
5. Open and flash the downloaded firmware
6. Optinal: Set Params
7. Optinal: Set WIFI Channel via (Here Channel 1 - At HS Augsburg least occupied Channel)
8. Optinal: Restart ESP as only then the new params will be used

Test 14.2.2020 - MAVEsp in AP Mode

1. Qgroundcontrol Dailybuild 14.2.2020
2. Mavesp Firmware 1.2.2
3. Login into pixracer WIFI which is provided by the ESP
4. Open QGroundcontrol and download dataflash Log
5. ⇒ Speed about 15-20kB/sec
6. Estimated Time to Download One Flight: Pixracer creates 3.4 MB/Min ⇒ 204MB/h = 204MB/Flight ⇒ 204MB / 0,020MB/sec = 10200 Sec = 170 Min = ~3h

Test 15.2.2020 - MAVEsp in Station Mode

1. Login into pixracer WIFI which is provided by the ESP
2. Set MAVEsp to Client / Station Mode: Mode = 1 . Be sure to type in the correct AP Name and Password. I tested by giving static IP
3. Set Params via HTTP Interface:
4. Start QGroundcontrol
5. Connection should be established automatically
6. Download dataflash Log
7. Speed about 18kB/sec

Idea is to download the dataflashlog via Serial Telemetry Link from the Pi from the Pixracer

1. Wire RX / TX with the PI
2. Install MAVProxy @ PI : sudo pip3 install mavproxy
3. Set Telemetry Speed (115200 / 921600) via QGroundcontrol
4. start pi↔pixracer connection : sudo mavproxy.py –master=/dev/ttyS0 –baudrate=921600
5. get log list : log list
6. download log: log download <logid> <filename>

Test 15.2.2020

1. log download 1 1.bin
2. ⇒ RTL> Finished downloading 1.bin (473553 bytes 48 seconds, 9.8 kbyte/sec 143 retries)

Test 20210529 CM4

1. mavproxy.py –master=/dev/ttyAMA0,1500000
2. Baudrate 1500000
3. Finished downloading log1.bin (232633 bytes 10 seconds, 21.7 kbyte/sec 0 retries)

Test 27.5.2021: CM4/Pi4

1. Finished downloading log3.bin (13292972 bytes 60 seconds, 219.2 kbyte/sec 0 retries)

Test 28.5.2021: Pi Zero

1. Added usb connector as described in

mavproxy.py –master=/dev/ttyACM0,115200

1. loads all modules of mavproxy ⇒ 100% idle cpu
2. Finished downloading log2.bin (462481 bytes 35 seconds, 13.1 kbyte/sec 0 retries)
3. Finished downloading log2.bin (462481 bytes 46 seconds, 10.0 kbyte/sec 0 retries)
4. Finished downloading log2.bin (462481 bytes 64 seconds, 7.1 kbyte/sec 0 retries)

mavproxy.py –master=/dev/ttyACM0,115200 –default-modules log

1. loads only log module of mavproxy ⇒ 60% idle cpu
2. Finished downloading log1.bin (232633 bytes 8 seconds, 26.9 kbyte/sec 0 retries)
3. Finished downloading log1.bin (232633 bytes 8 seconds, 26.9 kbyte/sec 0 retries)
4. Finished downloading log2.bin (462481 bytes 17 seconds, 26.9 kbyte/sec 0 retries)

Test 20210529: Pixracer @ Laptop mavproxy.py –master=/dev/ttyACM0,1500000 –default-modules log

1. loads only log module of mavproxy ⇒ 60% idle cpu
2. Finished downloading log3.bin (13292972 bytes 50 seconds, 264.3 kbyte/sec 0 retries)
3. Finished downloading log3.bin (13292972 bytes 49 seconds, 270.3 kbyte/sec 0 retries)

Test 20210529: Pixracer @ CM4 mavproxy.py –master=/dev/ttyACM0,1500000 –default-modules log

1. loads only log module of mavproxy ⇒ 60% idle cpu
2. Finished downloading log3.bin (13292972 bytes 53 seconds, 249.2 kbyte/sec 0 retries)
3. Finished downloading log3.bin (13292972 bytes 53 seconds, 249.3 kbyte/sec 0 retries)

Test 28.5.2021: QGC @ Laptop

1. ~250 kbyte/sec