GPSStatusLock
Posted: 10 February 2010 04:18 PM   [ Ignore ]
Jr. Member
RankRank
Total Posts:  34
Joined  2009-04-09

Are the following scenarios correct?:
1.    If GPSStatusLock =1, then we can assume that the device reported an accurate GPS position and an up to date Time Stamp
2.    If GPSStatusLock = 0 then the GPS position WILL be accurate, but the timestamp sent will be inaccurate?

Profile
 
 
Posted: 10 February 2010 04:33 PM   [ Ignore ]   [ # 1 ]
Administrator
RankRankRank
Total Posts:  55
Joined  2009-01-30

1.  Yes.
2.  No.  Timestamp is a function of GPS.  If a reading is reported with GPSStatusLock=0, it means the GPS info including timestamp that has been included in this message are out of date.  Out of date could mean 30 seconds, it could also mean 10 hours.

Profile
 
 
Posted: 08 June 2010 08:29 AM   [ Ignore ]   [ # 2 ]
Member
RankRankRank
Total Posts:  66
Joined  2009-10-24

We have had this occur a lot more lately.  An example of when a vehicle gets a correct “engine off” reading at 9:15pm and then receives as many as 40 more readings until the vehicles moves about 10 hours later.

My question is, we have the devices set to get a reading every 30 minutes when the engine is off, which would be 20 readings, so why would we receive as many as twice that many during that 10 hour period?  When the device doesn’t get an accurate reading, does it just keep trying to every minute or five minutes?  We usually, when in a garage, we just stop receiving readings altogether so I wonder what the difference would be?

Profile
 
 
Posted: 31 October 2010 07:19 PM   [ Ignore ]   [ # 3 ]
Newbie
Rank
Total Posts:  2
Joined  2010-10-31

HaHA! I have already seen the great thing!!!

 

 

 

 

 

——————————————————————————————————————————
I dont runescape accounts and wedding dresses and uggs sale

Profile
 
 
   
 
 
‹‹ UTC at time of trigger      Device Problems ››