| Author |
 Topic  |
|
davesalmon
Pterodattilo
United Kingdom
1620 Posts |
 Posted - 22/04/2015 : 09:23:30
|
I have had both cruise and circling time step intervals set at 1 sec for years, and it is not something I have checked on for a long time.
However for a flight yesterday I was looking for some specific information, and found that logging was at 2 sec intervals. I checked in Config-Eng Menu 2, and both settings are 1 sec. I have also noticed that when circling the glider icon seems to move at nearer 2 second intervals than 1 sec.
Due to the weather I've not done a lot of flying this year so I've checked back. Flights in Feb and March were logged at I sec, 5 subsequent flights are logged at 2 secs. 5.0a of course on a V2.
Any ideas please?
|
|
|
Coolwind
Moderator
Italy
8957 Posts |
Posted - 22/04/2015 : 12:21:41
|
Yes, your gps is sending position data at 0.5Hz, that is once every two seconds.
Best guess, you have run a car navigation software on it, without restarting the unit after.
|
 |
|
|
davesalmon
Pterodattilo
United Kingdom
1620 Posts |
Posted - 22/04/2015 : 13:50:07
|
| No, it's not that, it is used exclusively for gliding, it doesn't have any car nav software installed. It receives gps data from a Garmin (1 hz) through an Ilec SN10 and a GG interface cable, and that hasn't changed for 18 months. However my partner also has a V2 set exactly as mine, and I've just checked one of his recent logs and he is also logging at 2 secs. This points to input, yet the Garmin cannot be changed from it's 1 sec update, and the SN10 just passes on what it receives. I also happen to have one of my partner's log files from a few months ago, and then he was logging at 1 sec. I'm baffled |
|
|
|
Coolwind
Moderator
Italy
8957 Posts |
Posted - 22/04/2015 : 16:13:37
|
| Then we should have a look at what the serial is passing. Do an NMEA log of a few seconds, and we are done. |
|
|
|
davesalmon
Pterodattilo
United Kingdom
1620 Posts |
Posted - 22/04/2015 : 17:00:08
|
| Have just done a short logger file at home, which uses the internal gps. That has logged at 1 sec. I have sent a query to Garmin, to ask if anything could change the 1Hz update rate. |
|
|
|
Coolwind
Moderator
Italy
8957 Posts |
Posted - 22/04/2015 : 17:23:39
|
Are you sure that the same setup was working fine previously? at 1hz I mean.
I would first look at what is going on with the Ilec.
|
|
|
|
davesalmon
Pterodattilo
United Kingdom
1620 Posts |
Posted - 22/04/2015 : 17:57:07
|
| It has worked perfectly for 18 months, logging at 1 sec. I have checked logger files. It changed between a flight on 10th March, and the next one on 25th March. I have emailed Dave Nadler to see if there is any way the SN10 could alter the refresh rate of it's output, but in any case we haven't changed anything in the setup. |
|
|
|
davesalmon
Pterodattilo
United Kingdom
1620 Posts |
Posted - 27/04/2015 : 18:25:16
|
I flew today and got a NMEA log as well as the igc file. The latter still shows logging at 2 secs, though there are regular duplicate time stamps. We've talkes about that before. I also noticed that in thermal mode the glider icon is again very slow to move at times, then maks a big jump, the circle used to be smooth, now it is a polygon. Also running in to a TP with Auto Zoom, the glider icon froze for several seconds. Anyway here are samples of both files, I've plenty more if needed.
$GPGSV,3,2,11,18,19,316,37,19,04,008,30,20,11,179,40,21,08,283,30*76
$GPGSV,3,3,11,24,22,249,42,28,51,077,41,30,21,067,30,,,,*4F
$PGRME,5.0,M,6.9,M,8.5,M*29
$PGRMM,WGS 84*06
$GPRTE,1,1,c,0,CPH*70
$GPWPL,5318.303,N,00143.746,W,CPH*0E
$GPRMC,105118,A,5318.623,N,00143.776,W,000.0,360.0,270415,005.1,W*76
$PILC,PDA1,473,-0.01,52,12,71*72
$GPRMB,A,,,,,,,,,,,,V*71
$GPGGA,105119,5318.623,N,00143.776,W,1,07,1.3,425.4,M,49.0,M,,*5A
$GPGSA,A,3,05,13,15,,18,,20,,24,28,,,2.2,1.3,1.8*3D
$GPGSV,3,1,11,05,25,186,42,13,75,116,42,15,64,283,30,17,03,118,41*74
$GPGSV,3,2,11,18,19,316,37,19,04,008,30,20,11,179,40,21,08,283,30*76
$GPGSV,3,3,11,24,22,249,41,28,51,077,42,30,21,067,30,,,,*4F
$PGRME,4.9,M,6.7,M,8.3,M*29
$PGRMM,WGS 84*06
$GPRTE,1,1,c,0,CPH*70
$GPWPL,5318.303,N,00143.746,W,CPH*0E
$GPRMC,105120,A,5318.623,N,00143.776,W,000.0,360.0,270415,005.1,W*7D
$GPRMB,A,,,,,,,,,,,,V*71
$GPGGA,105121,5318.623,N,00143.776,W,1,07,1.3,425.3,M,49.0,M,,*56
$PILC,PDA1,473,0.15,52,12,71*5A
$GPGSA,A,3,05,13,15,,18,,20,,24,28,,,2.2,1.3,1.8*3D
$GPGSV,3,1,11,05,25,186,43,13,75,116,43,15,64,283,30,17,03,118,40*75
$GPGSV,3,2,11,18,19,316,37,19,04,008,30,20,11,179,39,21,08,283,30*78
$GPGSV,3,3,11,24,22,249,41,28,51,077,42,30,21,067,32,,,,*4D
$PGRME,5.0,M,6.9,M,8.5,M*29
$PGRMM,WGS 84*06
$GPRTE,1,1,c,0,CPH*70
$GPWPL,5318.303,N,00143.746,W,CPH*0E
$GPRMC,105122,A,5318.623,N,00143.776,W,000.0,360.0,270415,005.1,W*7F
$GPRMB,A,,,,,,,,,,,,V*71
$GPGGA,105123,5318.623,N,00143.776,W,1,07,1.3,425.1,M,49.0,M,,*56
$GPGSA,A,3,05,13,15,,18,,20,,24,28,,,2.2,1.3,1.8*3D
$GPGSV,3,1,11,05,25,186,43,13,75,116,44,15,64,283,31,17,03,118,39*7D
$PILC,PDA1,474,0.40,52,12,71*5D
$GPGSV,3,2,11,18,19,316,36,19,04,008,00,20,11,179,39,21,08,283,30*7A
$GPGSV,3,3,11,24,22,249,40,28,51,077,42,30,21,067,34,,,,*4A
$PGRME,4.9,M,6.7,M,8.3,M*29
$PGRMM,WGS 84*06
B1101045318626N00143775WA0046900423
B1101065318625N00143775WA0046900423
B1101065318625N00143775WA0047000423
B1101085318625N00143775WA0047000423
B1101105318625N00143775WA0047000423
B1101125318625N00143775WA0046900423
B1101125318625N00143775WA0046900423
B1101145318625N00143775WA0046900424
B1101165318624N00143775WA0046900424
B1101185318624N00143775WA0046900425
B1101205318624N00143774WA0046900425
B1101225318624N00143774WA0046900425
B1101245318624N00143774WA0047000425
B1101265318624N00143774WA0046900425
B1101285318624N00143774WA0046900424
B1101305318624N00143774WA0046900424
B1101305318624N00143774WA0046900424
B1101325318624N00143774WA0046900424
B1101345318624N00143774WA0046900424
B1101365318624N00143774WA0046900425
B1101385318624N00143774WA0046900425
B1101405318624N00143774WA0047000424
B1101425318624N00143774WA0046900424
B1101425318624N00143774WA0046900424
B1101445318624N00143774WA0046900424
B1101465318624N00143774WA0046900424
B1101485318625N00143774WA0046900423
B1101485318625N00143774WA0046900423
B1101505318625N00143773WA0046900423
B1101525318625N00143773WA0046900423
B1101545318625N00143773WA0046900422
B1101545318625N00143773WA0046900422
B1101565318625N00143773WA0046900423
B1101585318625N00143773WA0046900423
B1102005318625N00143773WA0046900422
B1102005318625N00143773WA0046900422
B1102025318625N00143773WA0046900422
B1102045318625N00143773WA0046900422
B1102065318625N00143773WA0047000422 |
|
|
|
davesalmon
Pterodattilo
United Kingdom
1620 Posts |
Posted - 27/04/2015 : 18:33:15
|
| BTW, I use Flightmap as a flight analysis program and logbook. It will not accept the logger file, too many duplicate time stamps. |
|
|
|
Coolwind
Moderator
Italy
8957 Posts |
Posted - 27/04/2015 : 23:26:16
|
| GGA and RMC non consistent. Totally random. |
|
|
|
davesalmon
Pterodattilo
United Kingdom
1620 Posts |
Posted - 28/04/2015 : 08:47:30
|
OK but what does that mean? Has the gps developed a fault and needs replacing?
Are both sentences used for time stamps, in which case they do appear to be alternatively at 1 sec intervals.
RMC 105118
GGA 105119
RMC 105120
GGA 105121
RMC 105122
GGA 105123
Is this causing the sudden duplication of hundreds of B records? BTW I have found a simple way, on line, to remove the duplicates and make the file useable. |
|
|
|
brunotl
Pterodattilo
France
1095 Posts |
Posted - 28/04/2015 : 12:55:57
|
| maybe 2 GPS source SN10 & Garmin are mixed ... |
|
|
|
davesalmon
Pterodattilo
United Kingdom
1620 Posts |
Posted - 28/04/2015 : 14:16:34
|
| SN10 has no gps source, it receives gps data from the Garmin, adds baro altitude and wind, and passes it through to LK8000. In any case the setup has worked faultlessly for 18 months, started the 2 sec logging 5 weeks ago, and only the last logger file has the hundreds of duplicate B records. I can only think the Garmin has become faulty, so will try another gps. |
|
|
|
Coolwind
Moderator
Italy
8957 Posts |
Posted - 28/04/2015 : 14:58:36
|
Well SN10 is in the middle, and may as well be the cause by filtering rmc or gga or more.
So it is quite easy: connect the garmin to a PC and see what it is sending (or to LK directly).
If it is missing sentences, then try to reconfigure it. If all sentences are there, look at the SN10. |
|
|
|
davesalmon
Pterodattilo
United Kingdom
1620 Posts |
Posted - 04/05/2015 : 17:31:53
|
I have now flown with a different Garmin, and LK is still logging at 2 sec intervals. However with the original Garmin the RMC and GGA sentences were alternatively at 1 sec intervals, with the "new" Garmin, they are in pairs with the same time stamp. Not only that, but the glider symbol still moves round a circle seemingly at irregular interval, so that sometimes you get a fairly smooth circle, at other times a distinct polygon.
I take your point about the SN10, but Dave Nadler is quite clear that it cannot do anything to the data stream, it just passes it through, and it did nothing for the first 18 months of this setup. |
|
|
|
Coolwind
Moderator
Italy
8957 Posts |
Posted - 04/05/2015 : 21:23:49
|
So lets see the new NMEA log with the new garmin, first. I am curious!
|
|
|
|
Topic |
|
|
|
Time step interval