Servers by jDrones

New dataflash log for each flight?

(Anthony Short) #1

I’m comparing the dataflash logs on the SD card in the PH2.1 with the logs created in the ~/dflogger/dataflash folder on the r.pi running APsync. If I do arm-takeoff-land-disarm then repeat that without powering down the aircraft, I get one .BIN file on the PH covering both flights, and two .BIN files on the r.pi, one for each flight.

Is there a good reason this is different? Is there a parameter somewhere to select the desired behavior? It would be nice to have it be the same in both places.

(Luís Vale Gonçalves) #2

Can this http://ardupilot.org/copter/docs/parameters.html#log-file-dsrmrot-stop-logging-to-current-file-on-disarm

be useful ?

(Anthony Short) #3

That’s what I needed - thank you.

(peterbarker) #4

The behaviour SD-card style logs (“DataFlash File”) is based on the
"LOG_FILE_DSRMROT" parameter.

DataFlash-over-MAVLink doesn’t have this concept. It could be
probably implemented on either side of the equation, but probably better
done on the client side. I’d have to look at the various client
implementations to be sure.

(yepzhang) #5

How can you get the dataflash logs in the APsync(raspberry)? I would really appreicate it if you can help me?