|
|
 TrekBuddy
www.trekbuddy.net
Outdoor companion.
|
- bluetooth / serial / internal GPS, simulator
- offline raster maps (common grids and projections)
- smart GPX / raw NMEA logs
- waypoints and simple navigation
- ... and more
|
- MIDP and Symbian phones
- Blackberry
- Android
- Windows Mobile 5.x/6.x
- Windows Phone coming
|
|
Visit our wiki to see all features, guides and howtos.
Project tracker.
|
|
|
|
|
|
|
| View previous topic :: View next topic |
| Author |
Message |
Bas
Joined: 05 May 2009
Posts: 344
Location: Lodz, PL
|
|
| Back to top |
|
 |
kruch
Site Admin
Joined: 02 Jul 2006
Posts: 5085
|
 Posted: Sun Feb 12, 2012 9:38 am Post subject: |
 |
|
| @Bas But in trekbuddy.nmea there is indeed 20 sec no movement (no fix at all, 17:24:15-17:24:34)
|
|
| Back to top |
|
|
Bas
Joined: 05 May 2009
Posts: 344
Location: Lodz, PL
|
| Posted: Sun Feb 12, 2012 11:57 am Post subject: |
|
|
| kruch wrote: |
| @Bas But in trekbuddy.nmea there is indeed 20 sec no movement (no fix at all, 17:24:15-17:24:34) |
Yes and No 
There is no fix at all - it's true.
There is NO movement - its' FALSE.
TB nmea - Take a look at GGA and GPS quality indicator (0=invalid; 1=GPS fix; 2=Diff. GPS fix):
There is NO reason to start logging anything till 17:24:36.
Please, take a look at GpsBabel conversion to gpx - both nmea logs are converted and show beggining at 17:24:36
It's TRUE because I was "in motion" then.
I imagine another situation:
A) you are in motion
B) there is "no fix at all" some time
C) you stay - parking time
So, you can't calculate when is the point you stop moving in B section BUT in "our" example there is no fix at all at the beggining so we can decide not to include this short time to the log (like GpsBabel).
What do You think 
Important:
take a look at Pentagram nmea - it is original file. Log starts at 17:24:36.
So... the source device logs from this time. The "second" device (TB) shouldn't log gps signal from 17:24:15.
Pentagram nmea:
| Code: |
$GPGGA,172436.000,5202.110828,N,01913.071769,E,1,8,1.23,106.776,M,32.9,M,,*5B
$GPGGA,172438.000,5202.090331,N,01913.087197,E,1,8,1.27,106.815,M,32.9,M,,*5F
$GPGGA,172440.000,5202.070487,N,01913.102560,E,1,8,1.23,107.050,M,32.9,M,,*58
$GPGGA,172442.000,5202.050290,N,01913.118009,E,1,8,0.78,108.612,M,32.9,M,,*59
$GPGGA,172444.000,5202.029248,N,01913.133823,E,1,8,0.78,109.877,M,32.9,M,,*51
$GPGGA,172446.000,5202.008162,N,01913.149571,E,1,8,0.78,110.539,M,32.9,M,,*53
$GPGGA,172448.000,5201.987079,N,01913.165163,E,1,8,0.78,110.332,M,32.9,M,,*5F
$GPGGA,172450.000,5201.966276,N,01913.180547,E,1,8,0.78,110.596,M,32.9,M,,*55
|
|
|
| Back to top |
|
|
Ranger
Joined: 12 Dec 2006
Posts: 4718
|
| Posted: Sun Feb 12, 2012 1:06 pm Post subject: |
|
|
No fix state for app means no positions to know if user was moving or not. But time in total was gone.
It is probably possible to use {time} to eliminate no fix periods at start from total time if someone would.
When nmea log should start (or not) is just another think, I would to know how long receiver was fixed.
Such info can be easy filtered, if removed - means just no info.
|
|
| Back to top |
|
|
Bas
Joined: 05 May 2009
Posts: 344
Location: Lodz, PL
|
| Posted: Sun Feb 12, 2012 4:33 pm Post subject: |
|
|
| Ranger wrote: |
| No fix state for app means no positions to know if user was moving or not |
First things first.
No fix at the beggining of work with gps means - gps is not ready yet
Wait for a while...
TB log is premature - app generates log too early. Especially when original signal doesn't contain any information about position and GPS quality indicator in GGA section is 0.
Pictures from previous post:
TB nmea:
GpsBabel conversion nmea to gpx - start from 17:24:36:
|
|
| Back to top |
|
|
Ranger
Joined: 12 Dec 2006
Posts: 4718
|
| Posted: Sun Feb 12, 2012 4:56 pm Post subject: |
|
|
So what ? Total time starts when receiver was activated by user and counting begins.
Read variables defs first in wiki, total time means total, not time from first fix. No fix doesn't means no nmea sentences at all.
There is another variable in hecl to get what you would. Just try.
|
|
| Back to top |
|
|
Bas
Joined: 05 May 2009
Posts: 344
Location: Lodz, PL
|
| Posted: Sun Feb 12, 2012 6:57 pm Post subject: |
|
|
| Ranger wrote: |
| Total time starts when receiver was activated by user and counting begins. |
Big mistake
Total time should start when gps is ready to avoid strange counters readings.
When you are in motion TB should show it, not a parking, don't you think?
Read... your reality. Don't hoodwink your mind.
|
|
| Back to top |
|
|
Ranger
Joined: 12 Dec 2006
Posts: 4718
|
| Posted: Sun Feb 12, 2012 7:31 pm Post subject: |
|
|
Yes, big mistake, but yours 
Not available directly parameter like time from first fix (which you expect to have) is not a bug of total time, but just not available directly parameter. That's all.
|
|
| Back to top |
|
|
Bas
Joined: 05 May 2009
Posts: 344
Location: Lodz, PL
|
| Posted: Sun Feb 12, 2012 9:08 pm Post subject: |
|
|
| Ranger wrote: |
| Read variables defs first in wiki, total time means total |
Yes, you are right. So... total time should start when you turn on Trek Buddy even if you doesn't run gps because "total time means total"
You can watch how long TB works and you don't have to turn on gps - what for?
BUT
When you start gps just wait for it- it's not ready yet. Pentagram works this way, GpsBabel but in your opinion total time counter should start from the "tap" start button.
|
|
| Back to top |
|
|
Ranger
Joined: 12 Dec 2006
Posts: 4718
|
| Posted: Sun Feb 12, 2012 10:00 pm Post subject: |
|
|
Nope.
Total time works as was described, time represents nmea data if used.
Doesn't matter what you supposed about it or expected, or what you can find in P3106 or GPSBabel
|
|
| Back to top |
|
|
Bas
Joined: 05 May 2009
Posts: 344
Location: Lodz, PL
|
| Posted: Mon Feb 13, 2012 11:20 am Post subject: |
|
|
| Ranger wrote: |
| time represents nmea data if used. |
No, it isn't
There is no useful data before 17:24:36.
If you want to use gps (nmea) data just wait for it.
I you wanna drive you must get in the car, but the counters move when you move your car, not earlier. If you think different way you can live whole your trip at the garage without starting engine just playing with steering wheel.
I wait for Kruch's decision
|
|
| Back to top |
|
|
Ranger
Joined: 12 Dec 2006
Posts: 4718
|
| Posted: Mon Feb 13, 2012 11:41 am Post subject: |
|
|
@Bas
You are wrong.
Receiver just sends sentences with time, even if no fix (first or any other).
If connection is broken, there is no time or fix info from receiver at all.
It takes less time to do something like that
{total time}-{fix delay}={time from first fix}
if you have fix & time values.
For me is clear that you just would to have different parameter (time from first fix), but not total time.
So don't hurry what is a old bug of last one, but ... not yours
|
|
| Back to top |
|
|
Bas
Joined: 05 May 2009
Posts: 344
Location: Lodz, PL
|
| Posted: Mon Feb 13, 2012 12:52 pm Post subject: |
|
|
| Ranger wrote: |
It takes less time to do something like that
{total time}-{fix delay}={time from first fix}
if you have fix & time values. |
It is a backbreaking idea. What for? It's better start counting from the first fix, not first "technical" connection with gps.
If you want to use some data from gps-> you should wait until it's ready and has some information for you about position and other parameters -> just wait for the first fix or maybe 2-3 sec. longer to get better starting position.
It this situation all counters will work properly without hecl and others "external" adjustments.
I wait for Kruch's decision - I hope it will be better.
Last edited by Bas on Mon Feb 13, 2012 12:56 pm; edited 1 time in total |
|
| Back to top |
|
|
Ranger
Joined: 12 Dec 2006
Posts: 4718
|
| Posted: Mon Feb 13, 2012 12:55 pm Post subject: |
|
|
Nope, sometimes I just look how long receiver is fixing.
With your "solution" - no way or harder to see it.
So we have just different ideas
Main difference is that you can get what you would in current app state, but ... you probably wouldn't
|
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum
|
Powered by phpBB © 2001, 2005 phpBB Group
|
FAQ
Search
Register
Profile
Log in to check your private messages
Log in
