|
From: | Eduardo lavratti |
Subject: | Re: [Paparazzi-devel] getopenlog export issues |
Date: | Mon, 29 Apr 2013 18:44:22 -0300 |
I use AIRSPEED_ETS and openlog workfine.
Date: Mon, 29 Apr 2013 22:52:05 +0200 From: address@hidden To: address@hidden Subject: Re: [Paparazzi-devel] getopenlog export issues Dear all, I finally managed to get the OpenLog telemetry export always working (or not !). It seems that the ETS Airspeed sensor is the source of the problem.
Without the ETS Airspeed sensor connected the exports are always ok, with the ETS connected, exports always fail. With the ETS connected, if I disable the AIRSPEED_ETS telemetry message, then the export works.
File sw/airborne/modules/sensors/airspeed_ets.c: #DOWNLINK_SEND_AIRSPEED_ETS (DefaultChannel, DefaultDevice, &airspeed_ets_raw, &airspeed_ets_offset, &airspeed_ets); If I leave the AIRSPEED_ETS telemetry message, I got "Fatal error: exception Failure("Pprz.values_of_payload, too many bytes: 11 03...." when executing getopenlog. I tried to set &airspeed_ets_raw, &airspeed_ets_offset, &airspeed_ets to 0, but the same problem occurs. There is something with the telemetry message format / parsing.
Of course, I did a make clean; make of paparazzi. Do anyone experienced the same problem ? Regards, Mitchell 2013/4/23 Mitchell SLOWER <address@hidden> Dear all, _______________________________________________ Paparazzi-devel mailing list address@hidden https://lists.nongnu.org/mailman/listinfo/paparazzi-devel |
[Prev in Thread] | Current Thread | [Next in Thread] |