getopenlog export issues

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

getopenlog export issues

Mitchell SLOWER
Dear all,

I have an OpenLog connected to a Lisa/M for onboard data logging.
I have added the OpenLog module to the airframe config file, the files are well created on the sdcard, but the export rarely works.

Here is below two exports tries: the first one is successful, and the second one is not. 
This was with the same setup, the difference is that on the first log the plane was not flying, but on the bench only.

First try (successful):
$ sw/logalizer/getopenlog ../data/logs/LOG00118.TXT 
now converting ../data/logs/LOG00118.TXT to ../data/logs/LOG00118.TXT.tlm
The conversion from the logfile from the SD to TLM seems to be successful, 1271 have been converted, 1 packages have been broken
Renaming produced file ...
Warning: not time found in GPS messages; using current date
13_04_23__15_46_59_SD_no_GPS.data file produced
Looking for d549a93093dd9d6cf5dba0c750b0ff5e conf...
13_04_23__15_46_59_SD_no_GPS.log file produced
13_04_23__15_46_59_SD_no_GPS.tlm file saved

Second try (unsuccessful):
$ sw/logalizer/getopenlog ../data/logs/data_helsinki.txt 
now converting ../data/logs/data_helsinki.txt to ../data/logs/data_helsinki.txt.tlm
The conversion from the logfile from the SD to TLM seems to be successful, 12063 have been converted, 0 packages have been broken
Fatal error: exception Failure("Pprz.values_of_payload, too many bytes: 11 03 66 05 00 00 00 00 00 00 00 00 80 25 24 39 99 0e 03 39 1a f5 00 00 00 00 00 00 59 3c 99 0e 03 2a 00 00 00 00 00 00 00 00 3b 32 99 11 03 69 05 e8 03 fa 05 be 05 dc 05 d0 07 e7 09 99 0e 03 39 71 9d 00 00

Do you have any idea of where I should look at in order to sort out that problem ?
Thanks.

Regards,
Mitchell



_______________________________________________
Paparazzi-devel mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/paparazzi-devel
Reply | Threaded
Open this post in threaded view
|

Re: getopenlog export issues

agressiva
What logger are you using ?
i get the same problem some time ago.


Date: Tue, 23 Apr 2013 16:19:47 +0200
From: [hidden email]
To: [hidden email]
Subject: [Paparazzi-devel] getopenlog export issues

Dear all,

I have an OpenLog connected to a Lisa/M for onboard data logging.
I have added the OpenLog module to the airframe config file, the files are well created on the sdcard, but the export rarely works.

Here is below two exports tries: the first one is successful, and the second one is not. 
This was with the same setup, the difference is that on the first log the plane was not flying, but on the bench only.

First try (successful):
$ sw/logalizer/getopenlog ../data/logs/LOG00118.TXT 
now converting ../data/logs/LOG00118.TXT to ../data/logs/LOG00118.TXT.tlm
The conversion from the logfile from the SD to TLM seems to be successful, 1271 have been converted, 1 packages have been broken
Renaming produced file ...
Warning: not time found in GPS messages; using current date
13_04_23__15_46_59_SD_no_GPS.data file produced
Looking for d549a93093dd9d6cf5dba0c750b0ff5e conf...
13_04_23__15_46_59_SD_no_GPS.log file produced
13_04_23__15_46_59_SD_no_GPS.tlm file saved

Second try (unsuccessful):
$ sw/logalizer/getopenlog ../data/logs/data_helsinki.txt 
now converting ../data/logs/data_helsinki.txt to ../data/logs/data_helsinki.txt.tlm
The conversion from the logfile from the SD to TLM seems to be successful, 12063 have been converted, 0 packages have been broken
Fatal error: exception Failure("Pprz.values_of_payload, too many bytes: 11 03 66 05 00 00 00 00 00 00 00 00 80 25 24 39 99 0e 03 39 1a f5 00 00 00 00 00 00 59 3c 99 0e 03 2a 00 00 00 00 00 00 00 00 3b 32 99 11 03 69 05 e8 03 fa 05 be 05 dc 05 d0 07 e7 09 99 0e 03 39 71 9d 00 00

Do you have any idea of where I should look at in order to sort out that problem ?
Thanks.

Regards,
Mitchell



_______________________________________________ Paparazzi-devel mailing list [hidden email] https://lists.nongnu.org/mailman/listinfo/paparazzi-devel

_______________________________________________
Paparazzi-devel mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/paparazzi-devel
Reply | Threaded
Open this post in threaded view
|

Re: getopenlog export issues

Mitchell SLOWER

I am using OpenLog from SparkFun Electronics. How did you manage to get rid of that problem ?

Mitchell.

Le 23 avr. 2013 16:30, "Eduardo lavratti" <[hidden email]> a écrit :
What logger are you using ?
i get the same problem some time ago.


Date: Tue, 23 Apr 2013 16:19:47 +0200
From: [hidden email]
To: [hidden email]
Subject: [Paparazzi-devel] getopenlog export issues

Dear all,

I have an OpenLog connected to a Lisa/M for onboard data logging.
I have added the OpenLog module to the airframe config file, the files are well created on the sdcard, but the export rarely works.

Here is below two exports tries: the first one is successful, and the second one is not. 
This was with the same setup, the difference is that on the first log the plane was not flying, but on the bench only.

First try (successful):
$ sw/logalizer/getopenlog ../data/logs/LOG00118.TXT 
now converting ../data/logs/LOG00118.TXT to ../data/logs/LOG00118.TXT.tlm
The conversion from the logfile from the SD to TLM seems to be successful, 1271 have been converted, 1 packages have been broken
Renaming produced file ...
Warning: not time found in GPS messages; using current date
13_04_23__15_46_59_SD_no_GPS.data file produced
Looking for d549a93093dd9d6cf5dba0c750b0ff5e conf...
13_04_23__15_46_59_SD_no_GPS.log file produced
13_04_23__15_46_59_SD_no_GPS.tlm file saved

Second try (unsuccessful):
$ sw/logalizer/getopenlog ../data/logs/data_helsinki.txt 
now converting ../data/logs/data_helsinki.txt to ../data/logs/data_helsinki.txt.tlm
The conversion from the logfile from the SD to TLM seems to be successful, 12063 have been converted, 0 packages have been broken
Fatal error: exception Failure("Pprz.values_of_payload, too many bytes: 11 03 66 05 00 00 00 00 00 00 00 00 80 25 24 39 99 0e 03 39 1a f5 00 00 00 00 00 00 59 3c 99 0e 03 2a 00 00 00 00 00 00 00 00 3b 32 99 11 03 69 05 e8 03 fa 05 be 05 dc 05 d0 07 e7 09 99 0e 03 39 71 9d 00 00

Do you have any idea of where I should look at in order to sort out that problem ?
Thanks.

Regards,
Mitchell



_______________________________________________ Paparazzi-devel mailing list [hidden email] https://lists.nongnu.org/mailman/listinfo/paparazzi-devel

_______________________________________________
Paparazzi-devel mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/paparazzi-devel


_______________________________________________
Paparazzi-devel mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/paparazzi-devel
Reply | Threaded
Open this post in threaded view
|

Re: getopenlog export issues

agressiva
You need to use a special firmware .
I made some modifications on my openlog SOURCE.
The problem is that some time the PPZ send the special caracter that put openlog terminal mode.

i will share the code.




Date: Tue, 23 Apr 2013 20:13:25 +0200
From: [hidden email]
To: [hidden email]
Subject: Re: [Paparazzi-devel] getopenlog export issues

I am using OpenLog from SparkFun Electronics. How did you manage to get rid of that problem ?
Mitchell.

Le 23 avr. 2013 16:30, "Eduardo lavratti" <[hidden email]> a écrit :
What logger are you using ?
i get the same problem some time ago.


Date: Tue, 23 Apr 2013 16:19:47 +0200
From: [hidden email]
To: [hidden email]
Subject: [Paparazzi-devel] getopenlog export issues

Dear all,

I have an OpenLog connected to a Lisa/M for onboard data logging.
I have added the OpenLog module to the airframe config file, the files are well created on the sdcard, but the export rarely works.

Here is below two exports tries: the first one is successful, and the second one is not. 
This was with the same setup, the difference is that on the first log the plane was not flying, but on the bench only.

First try (successful):
$ sw/logalizer/getopenlog ../data/logs/LOG00118.TXT 
now converting ../data/logs/LOG00118.TXT to ../data/logs/LOG00118.TXT.tlm
The conversion from the logfile from the SD to TLM seems to be successful, 1271 have been converted, 1 packages have been broken
Renaming produced file ...
Warning: not time found in GPS messages; using current date
13_04_23__15_46_59_SD_no_GPS.data file produced
Looking for d549a93093dd9d6cf5dba0c750b0ff5e conf...
13_04_23__15_46_59_SD_no_GPS.log file produced
13_04_23__15_46_59_SD_no_GPS.tlm file saved

Second try (unsuccessful):
$ sw/logalizer/getopenlog ../data/logs/data_helsinki.txt 
now converting ../data/logs/data_helsinki.txt to ../data/logs/data_helsinki.txt.tlm
The conversion from the logfile from the SD to TLM seems to be successful, 12063 have been converted, 0 packages have been broken
Fatal error: exception Failure("Pprz.values_of_payload, too many bytes: 11 03 66 05 00 00 00 00 00 00 00 00 80 25 24 39 99 0e 03 39 1a f5 00 00 00 00 00 00 59 3c 99 0e 03 2a 00 00 00 00 00 00 00 00 3b 32 99 11 03 69 05 e8 03 fa 05 be 05 dc 05 d0 07 e7 09 99 0e 03 39 71 9d 00 00

Do you have any idea of where I should look at in order to sort out that problem ?
Thanks.

Regards,
Mitchell



_______________________________________________ Paparazzi-devel mailing list [hidden email] https://lists.nongnu.org/mailman/listinfo/paparazzi-devel

_______________________________________________
Paparazzi-devel mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/paparazzi-devel


_______________________________________________ Paparazzi-devel mailing list [hidden email] https://lists.nongnu.org/mailman/listinfo/paparazzi-devel

_______________________________________________
Paparazzi-devel mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/paparazzi-devel
Reply | Threaded
Open this post in threaded view
|

Re: getopenlog export issues

Mitchell SLOWER
In reply to this post by Mitchell SLOWER
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 <[hidden email]>
Dear all,

I have an OpenLog connected to a Lisa/M for onboard data logging.
I have added the OpenLog module to the airframe config file, the files are well created on the sdcard, but the export rarely works.

Here is below two exports tries: the first one is successful, and the second one is not. 
This was with the same setup, the difference is that on the first log the plane was not flying, but on the bench only.

First try (successful):
$ sw/logalizer/getopenlog ../data/logs/LOG00118.TXT 
now converting ../data/logs/LOG00118.TXT to ../data/logs/LOG00118.TXT.tlm
The conversion from the logfile from the SD to TLM seems to be successful, 1271 have been converted, 1 packages have been broken
Renaming produced file ...
Warning: not time found in GPS messages; using current date
13_04_23__15_46_59_SD_no_GPS.data file produced
Looking for d549a93093dd9d6cf5dba0c750b0ff5e conf...
13_04_23__15_46_59_SD_no_GPS.log file produced
13_04_23__15_46_59_SD_no_GPS.tlm file saved

Second try (unsuccessful):
$ sw/logalizer/getopenlog ../data/logs/data_helsinki.txt 
now converting ../data/logs/data_helsinki.txt to ../data/logs/data_helsinki.txt.tlm
The conversion from the logfile from the SD to TLM seems to be successful, 12063 have been converted, 0 packages have been broken
Fatal error: exception Failure("Pprz.values_of_payload, too many bytes: 11 03 66 05 00 00 00 00 00 00 00 00 80 25 24 39 99 0e 03 39 1a f5 00 00 00 00 00 00 59 3c 99 0e 03 2a 00 00 00 00 00 00 00 00 3b 32 99 11 03 69 05 e8 03 fa 05 be 05 dc 05 d0 07 e7 09 99 0e 03 39 71 9d 00 00

Do you have any idea of where I should look at in order to sort out that problem ?
Thanks.

Regards,
Mitchell




_______________________________________________
Paparazzi-devel mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/paparazzi-devel
Reply | Threaded
Open this post in threaded view
|

Re: getopenlog export issues

agressiva
I use AIRSPEED_ETS and openlog workfine.


Date: Mon, 29 Apr 2013 22:52:05 +0200
From: [hidden email]
To: [hidden email]
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 <[hidden email]>
Dear all,

I have an OpenLog connected to a Lisa/M for onboard data logging.
I have added the OpenLog module to the airframe config file, the files are well created on the sdcard, but the export rarely works.

Here is below two exports tries: the first one is successful, and the second one is not. 
This was with the same setup, the difference is that on the first log the plane was not flying, but on the bench only.

First try (successful):
$ sw/logalizer/getopenlog ../data/logs/LOG00118.TXT 
now converting ../data/logs/LOG00118.TXT to ../data/logs/LOG00118.TXT.tlm
The conversion from the logfile from the SD to TLM seems to be successful, 1271 have been converted, 1 packages have been broken
Renaming produced file ...
Warning: not time found in GPS messages; using current date
13_04_23__15_46_59_SD_no_GPS.data file produced
Looking for d549a93093dd9d6cf5dba0c750b0ff5e conf...
13_04_23__15_46_59_SD_no_GPS.log file produced
13_04_23__15_46_59_SD_no_GPS.tlm file saved

Second try (unsuccessful):
$ sw/logalizer/getopenlog ../data/logs/data_helsinki.txt 
now converting ../data/logs/data_helsinki.txt to ../data/logs/data_helsinki.txt.tlm
The conversion from the logfile from the SD to TLM seems to be successful, 12063 have been converted, 0 packages have been broken
Fatal error: exception Failure("Pprz.values_of_payload, too many bytes: 11 03 66 05 00 00 00 00 00 00 00 00 80 25 24 39 99 0e 03 39 1a f5 00 00 00 00 00 00 59 3c 99 0e 03 2a 00 00 00 00 00 00 00 00 3b 32 99 11 03 69 05 e8 03 fa 05 be 05 dc 05 d0 07 e7 09 99 0e 03 39 71 9d 00 00

Do you have any idea of where I should look at in order to sort out that problem ?
Thanks.

Regards,
Mitchell




_______________________________________________ Paparazzi-devel mailing list [hidden email] https://lists.nongnu.org/mailman/listinfo/paparazzi-devel

_______________________________________________
Paparazzi-devel mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/paparazzi-devel
Reply | Threaded
Open this post in threaded view
|

Re: getopenlog export issues

woeileong1104
This post has NOT been accepted by the mailing list yet.
This post was updated on .
In reply to this post by Mitchell SLOWER
Hi Guys,

I am struggling to make OpenLog works on my Lisa/S. I am not even sure if I did everything right. I added the followings in my airframe file:

...
<modules>
   <load name="openlog.xml"             />
 </modules>

<define name="USE_BAROMETER" value="TRUE"/>

  <firmware name="rotorcraft">
    <target name="ap" board="lisa_s_1.0">
      <subsystem name="radio_control" type="superbitrf_rc">
        <define name="RADIO_MODE" value="RADIO_GEAR"/>
        <define name="RADIO_AUTO_MODE" value="RADIO_FLAP"/>
      </subsystem>

      <configure name="AHRS_PROPAGATE_FREQUENCY" value="500"/>
     
      <configure name="LOG_MSG_FMT" value="LOG_PPRZ"/>
      <configure name="SPI_CHANNEL" value="1"       />
      <configure name="UART0_BAUD"  value="B57600"  />
      <configure name="UART1_BAUD"  value="B57600"  />
...

But when I hooked the TX on the oscilloscope, there is nothing. I need to get this part working first, then I will deal with the firmware of OpenLog.

Appreciate your help. Thanks.

Regards,
WL Chan