I am using an Asus MyPal A696 to display Anquet maps (Ordnance Survey).
Sometimes the position shown on the map is "lagged" by up to 100 metres.
When I switch the machine off and then on again quickly, the position
indicator quickly shows my correct position.
Has any one experienced anything similar?

On 14 Dec, 16:54, "Terry Metcalfe" <terrymetca...@btinternet.com>
wrote:
> I am using an Asus MyPal A696 to display Anquet maps (Ordnance Survey).
> Sometimes the position shown on the map is "lagged" by up to 100 metres.
> When I switch the machine off and then on again quickly, *the position
> indicator quickly shows my correct position.
> Has any one experienced anything similar?

Whenever I read about GPS, mapping and errors of about a hundred
metres it suggests to me a possible problem in converting from WGS84
to OSGB36. The WGS84 prime meridian is about 100 metres adrift from
the Ordnance Survey prime meridian.

Regards,
N.

Thanks Nick. But the problem is intermittent. For much of the time the
position indicator is "spot on"

My concern is why after my position becomes lagged should turning the PDA
off and then on again give me a correct position? If that "cures" the
problem why doesn't the mapping software emulate turning the PDA off and on
again!! I'm sure I'm being simplistic but I hope someone out there might
have had a similar problem and be able to help.

Terry Metcalfe


"Nick" <(E-Mail Removed)> wrote in message
news:74cc2ce5-178f-433f-ae98-(E-Mail Removed)...
On 14 Dec, 16:54, "Terry Metcalfe" <terrymetca...@btinternet.com>
wrote:
> I am using an Asus MyPal A696 to display Anquet maps (Ordnance Survey).
> Sometimes the position shown on the map is "lagged" by up to 100 metres.
> When I switch the machine off and then on again quickly, the position
> indicator quickly shows my correct position.
> Has any one experienced anything similar?

Whenever I read about GPS, mapping and errors of about a hundred
metres it suggests to me a possible problem in converting from WGS84
to OSGB36. The WGS84 prime meridian is about 100 metres adrift from
the Ordnance Survey prime meridian.

Regards,
N.

Terry Metcalfe wrote:
> Thanks Nick. But the problem is intermittent. For much of the time the
> position indicator is "spot on"
>
> My concern is why after my position becomes lagged should turning the PDA
> off and then on again give me a correct position? If that "cures" the
> problem why doesn't the mapping software emulate turning the PDA off and on
> again!! I'm sure I'm being simplistic but I hope someone out there might
> have had a similar problem and be able to help.
>
Cynic that I am, when I have similar problems with both my PDA based GPS
units, (One running Tomtom, the other running Navigon MN6) I just put it
down to them running Windows, which is normally running quite a few
tasks in the background, even on a PDA.

For what it's worth, the screen usually shows where I was about a second
ago, even when it's working right.

--
Tciao for Now!

John.

"Terry Metcalfe" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Thanks Nick. But the problem is intermittent. For much of the time the
> position indicator is "spot on"
>
> My concern is why after my position becomes lagged should turning the PDA
> off and then on again give me a correct position? If that "cures" the
> problem why doesn't the mapping software emulate turning the PDA off and on
> again!! I'm sure I'm being simplistic but I hope someone out there might
> have had a similar problem and be able to help.

I don't use the ASUS, mine is a MIO P350 and it works fine, but I wonder; it's
nothing to do with the Live Track "Tracklog trackpoint interval" distance, is
it? Under GPS configure? The default setting is to update the tracklog every
30 seconds, but it can be set to a user-defined distance. I just wondered if
your was set differently.

--
Arecibo

"John Williamson" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Terry Metcalfe wrote:
>> Thanks Nick. But the problem is intermittent. For much of the time
>> the position indicator is "spot on"
>>
>> My concern is why after my position becomes lagged should turning the PDA
>> off and then on again give me a correct position? If that "cures" the
>> problem why doesn't the mapping software emulate turning the PDA off and
>> on again!! I'm sure I'm being simplistic but I hope someone out there
>> might have had a similar problem and be able to help.
>>
> Cynic that I am, when I have similar problems with both my PDA based GPS
> units, (One running Tomtom, the other running Navigon MN6) I just put it
> down to them running Windows, which is normally running quite a few tasks
> in the background, even on a PDA.
>
> For what it's worth, the screen usually shows where I was about a second
> ago, even when it's working right.
>
> --
> Tciao for Now!
>
> John.
I was reading the manual for my ipaq/tomtom and it suggested a soft reset as
the cure for lag sounds like memory fragmentation problems.
http://www.softmaker.com/forum/viewtopic.php?f=1&t=2158
DerekW

Derek wrote:
> "John Williamson" <(E-Mail Removed)> wrote in message

>> Cynic that I am, when I have similar problems with both my PDA based GPS
>> units, (One running Tomtom, the other running Navigon MN6) I just put it
>> down to them running Windows, which is normally running quite a few tasks
>> in the background, even on a PDA.
>>
>> For what it's worth, the screen usually shows where I was about a second
>> ago, even when it's working right.
>>

> I was reading the manual for my ipaq/tomtom and it suggested a soft reset as
> the cure for lag sounds like memory fragmentation problems.
> http://www.softmaker.com/forum/viewtopic.php?f=1&t=2158
>

Not exactly a practical solution when I'm doing 60 along a motorway,
though. The problem persists after a soft reset, too, even if I make
sure nothing is running apart from the Satnav program.

I'd assumed it's because the program only updates the position from the
GPS receiver once a second, as it happens on two (slightly) different
operating systems and using two totally different programs, as well as
with both bluetooth and wired receivers.

--
Tciao for Now!

John.

Thanks for all your comments.

What bugs me is that when I get lagged I can switch the Asus off and then on
again (I guess this is what one of you meant by a soft reset) and within two
or three seconds of the map appearing on the screen I have a correct
position (or as near as doesn't matter).

I have emailed Asus on exactly this point and await their comments with
interest.

Any further comments will be welcome. Someone somewhere has the answer to
this.


Regards

Terry

"John Williamson" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Derek wrote:
>> "John Williamson" <(E-Mail Removed)> wrote in message
>
>>> Cynic that I am, when I have similar problems with both my PDA based GPS
>>> units, (One running Tomtom, the other running Navigon MN6) I just put it
>>> down to them running Windows, which is normally running quite a few
>>> tasks in the background, even on a PDA.
>>>
>>> For what it's worth, the screen usually shows where I was about a second
>>> ago, even when it's working right.
>>>
>
>> I was reading the manual for my ipaq/tomtom and it suggested a soft reset
>> as the cure for lag sounds like memory fragmentation problems.
>> http://www.softmaker.com/forum/viewtopic.php?f=1&t=2158
>>
>
> Not exactly a practical solution when I'm doing 60 along a motorway,
> though. The problem persists after a soft reset, too, even if I make sure
> nothing is running apart from the Satnav program.
>
> I'd assumed it's because the program only updates the position from the
> GPS receiver once a second, as it happens on two (slightly) different
> operating systems and using two totally different programs, as well as
> with both bluetooth and wired receivers.
>
> --
> Tciao for Now!
>
> John.

Sounds a total PITA I had a Navman Pin 570 like that and it would lock up on
any longer journey 5 times on manchester to Preswick! Which when you are
running a tacho and need to know whether you can get to the destination
without running over hours and facing prosecution was a total waste of time.
Small things would cause it like changing mode to see how far the next
motorway turn off was or a reroute even changing screensize. I think part of
it is due to the poor way windows manages memory there has to be a better
solution than resetting.That said I have a Bluemedia running a cut down
windows and Navigon and it rarely gives a problem even on trips over 200
miles each way.It does however need a reboot every few weeks to keep it
running smoothly I'll be hanging on to it until I am happy the Ipaq is
reliable.
Cheers
Derek

Derek wrote:
> "John Williamson" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> Derek wrote:
>>> "John Williamson" <(E-Mail Removed)> wrote in message
>>>> Cynic that I am, when I have similar problems with both my PDA based GPS
>>>> units, (One running Tomtom, the other running Navigon MN6) I just put it
>>>> down to them running Windows, which is normally running quite a few
>>>> tasks in the background, even on a PDA.
>>>>
>>>> For what it's worth, the screen usually shows where I was about a second
>>>> ago, even when it's working right.
>>>>
>>> I was reading the manual for my ipaq/tomtom and it suggested a soft reset
>>> as the cure for lag sounds like memory fragmentation problems.
>>> http://www.softmaker.com/forum/viewtopic.php?f=1&t=2158
>>>
>> Not exactly a practical solution when I'm doing 60 along a motorway,
>> though. The problem persists after a soft reset, too, even if I make sure
>> nothing is running apart from the Satnav program.
>>
>> I'd assumed it's because the program only updates the position from the
>> GPS receiver once a second, as it happens on two (slightly) different
>> operating systems and using two totally different programs, as well as
>> with both bluetooth and wired receivers.
>>
>> --
>> Tciao for Now!
>>
>> John.
>
> Sounds a total PITA I had a Navman Pin 570 like that and it would lock up on
> any longer journey 5 times on manchester to Preswick! Which when you are
> running a tacho and need to know whether you can get to the destination
> without running over hours and facing prosecution was a total waste of time.
> Small things would cause it like changing mode to see how far the next
> motorway turn off was or a reroute even changing screensize. I think part of
> it is due to the poor way windows manages memory there has to be a better
> solution than resetting.That said I have a Bluemedia running a cut down
> windows and Navigon and it rarely gives a problem even on trips over 200
> miles each way.It does however need a reboot every few weeks to keep it
> running smoothly I'll be hanging on to it until I am happy the Ipaq is
> reliable.

Well, a second behind is acceptable for me, I only really notice it when
I'm looking for it. I just need to be aware of it on some of the more
complicated junctions. Both of the units I use freeze from time to time
though, which causes problems, as it always seems to happen when I'm
approaching a really complex junction in an area I don't know well.

I run an iPaq 6515 Messenger, and that has known problems with a couple
of files that TomTom installs relating to the bluetooth connection.
Rename these and it's a lot more stable.

With the right support from the makers, the best way to avoid these
problems would be to avoid Windows....

--
Tciao for Now!

JOhn.