Re: [Paparazzi-devel] Which message carries the GPS reception bars information?

[Felix Ruess]

Hi Simon,

this is actually done on purpose (to save bandwidth once you have a fix).
The idea was to send SVINFO for all satellites while no GPS fix and after a fix only send svinfo if there is new information.

Basically send_svinfo_available is called if you registered GPS or GPS_INT messages (which you usually have in your telemetry xml file).

You can additionally add the SVINFO message to your telemetry xml file and it will always send this message with specified freq.

Cheers, Felix

On Sat, Oct 3, 2015 at 1:35 PM, Simon Liebold <address@hidden> wrote:

Follow-up question: Are SVINFO messages only sent during the first minute?

I can see messages using the M8N GPS during roughly the first minute after powering on. Then they suddenly stop while the copter was still on the ground. No telemetry configuration changed.

$ grep SVINFO 15_09_29__19_05_00.data|tail -n1
57.253 2 SVINFO 14 71 13 7 44 53 46
$ tail -n 1 15_09_29__19_05_00.data|cut -f1 -d ' '
149.998

Using the older LEA-6H I can see the SVINFO messages throughout the flight:

$ ack-grep SVINFO 15_09_24__18_57_23.data|tail -n1
228.376 2 SVINFO 6 11 13 4 24 33 160
$ tail -n1 15_09_24__18_57_23.data|cut -f1 -d ' '
229.124

It seems to be related to the number of satellites it locked onto. When the copter was powered on for some time and it already acquired a very good position fix there are no SVINFO messages from the start. Again, that never happens with the LEA-6H.

All SVINFO messages from the M8N:

1.255 2 SVINFO 14 71 13 7 43 54 46
2.004 2 SVINFO 1 3 13 7 31 76 61
2.254 2 SVINFO 2 4 69 7 29 15 140
2.754 2 SVINFO 4 11 13 7 28 22 161
3.510 2 SVINFO 7 32 13 7 32 35 80
5.266 2 SVINFO 14 71 13 7 44 54 46
6.259 2 SVINFO 2 4 13 7 28 15 140
9.256 2 SVINFO 14 71 13 7 43 54 46
9.509 2 SVINFO 15 72 13 7 39 61 281
9.761 2 SVINFO 0 1 13 7 32 42 146
10.005 2 SVINFO 1 3 13 7 32 76 61
10.504 2 SVINFO 3 6 69 6 27 20 309
10.767 2 SVINFO 4 11 13 7 29 22 161
13.504 2 SVINFO 15 72 13 7 40 61 281
13.754 2 SVINFO 0 1 13 7 33 42 146
14.005 2 SVINFO 1 3 13 7 31 76 61
14.504 2 SVINFO 3 6 69 6 26 20 309
14.754 2 SVINFO 4 11 13 7 28 22 161
15.510 2 SVINFO 7 32 13 7 33 35 80
54.002 2 SVINFO 1 3 13 7 30 75 62
54.254 2 SVINFO 2 4 13 7 27 15 140
54.753 2 SVINFO 4 11 13 7 27 21 161
55.003 2 SVINFO 5 12 4 1 0 3 341
55.254 2 SVINFO 6 23 13 7 33 65 187
55.507 2 SVINFO 7 31 13 7 35 25 56
55.753 2 SVINFO 8 32 13 7 34 35 80
56.753 2 SVINFO 12 65 4 4 25 13 256
57.004 2 SVINFO 13 70 4 4 19 6 66
57.253 2 SVINFO 14 71 13 7 44 53 46

Not that it creates a real issue. It is just odd. Has anyone seen this before?

Simon

Am 27.09.2015 um 10:53 schrieb Simon Liebold:

Am 26.09.2015 um 14:50 schrieb Felix Ruess:

This is sent in the SVINFO message.

Thanks Felix. Sent one satellite after another. Got it.

Simon

_______________________________________________
Paparazzi-devel mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/paparazzi-devel