Servers by jDrones

Mavproxy and dataflash log


(Corrado Steri) #1

Hello i am using Apsync on my companion and use mavproxy to stream from cube 2.1 to groundstation (trough an ethernet link).

I wanted to start logging on my companion computer too and i set logging backend to 3 as adviced and uncommented the dflogger line in rc.local.

I get a bad logging error on mission planner.

Do i have to add anything more to the mavproxy starting line for dflogger to work? do i need another stream when mavproxy starts to some port to be used by dflogger?

thanks in advance.


(Corrado Steri) #2

No one? Please if anyone could be of any help i would appreciate it very very much.

Corrado


(Corrado Steri) #3

Please please please :slight_smile:


(Corrado Steri) #4

Can anybody please give me a little help? I need to write dataflash logs on my companion and i use mavproxy on it. Please any help would be greatly appreciated.

Corrado


(peterbarker) #5

Can anybody please give me a little help? I need to write dataflash logs on my companion and i use mavproxy on it. Please any help would be greatly
appreciated.

module load dataflash_logger

Corrado

Peter


(Corrado Steri) #6

Hello Peter i put the following lines in mavinit.scr

module load dataflash_logger
dataflash_logger start

I selected backend type 3 but i still get bad logging in mission planner.
I looked at mavproxy and it loads the module.
Really don’t know what i am missing.


(peterbarker) #7

Please type those at the MAVProxy command prompt and paste the output.

Also try “dataflash_logger set verbose 1”


(Corrado Steri) #8

something like:

mavproxy.py --master=/dev/ttyAMA0 --cmd=“module load dataflash_logger; dataflash_logger start; dataflash_logger set verbose 1;”


(Corrado Steri) #9

Ok done it, still getting bad logging. In mavproxy i keep getting message

DFLogger: Sending start packet