Thread: BU-353 cuts out unexpectedly

I ditched xport, even the newest one had problems. So no gps sharing for me. I was only sharing it to the front end for auto volume adjust by speed, which was nice but I can live without it. More important that my gps program is accurate and reliable.

I am having the same issues with Xport and bu-353... It cuts off suddenly then it shows no sats..and speed jumps to 220km/hr or more for a second then zero..this is strange,,,all things show it is an Xport issue.. closing and restarting Xport fixes it..

i am using:
xport 1.46 latest
windows 7
zotac h55 mobo
i3 530 CPU
bu-353 gps direct on the Mobo not on a hub
the thing is that it would work OK for days then suddenly on the road it would just happen, and Xport continues to show data coming in and going out!!

Quote:

"all things show it is an Xport issue
closing and restarting Xport fixes it"

Instead of restarting Xport, try unplugging & plugging the BU-353. If that corrects the problem, it may then not necessarily be an Xport issue.

__________________
Laptop GPS World

Originally Posted by Marvin Hlavac

Quote:

"all things show it is an Xport issue
closing and restarting Xport fixes it"

Instead of restarting Xport, try unplugging & plugging the BU-353. If that corrects the problem, it may then not necessarily be an Xport issue.

__________________
Laptop GPS World

that would not mean it is a bu353 problem for sure.. in fact using gpsgate for a couple of weeks will.. i will try to use an older version of xport aswell 1.41 or 1.44 (those i have) and we will see

Yes, that would not mean it is a BU-353 problem for sure, it would simply mean that it may not necessarily be an Xport issue.

__________________
Laptop GPS World

Closing and restarting xport also means you're closing and restarting other software attached to it. The pausing and jumping would mean the xport process is losing a lot of processor time. At those points you'll most likely notice your CPU at 100% where a foreground process is being prioritized. Try setting the xport process priority to high and see if that helps. You may only see XPort at 0-1%, but it still needs the speed while it's in the background.

i havent had any issues with xport in months... its been flawless.

Originally Posted by Curiosity

Closing and restarting xport also means you're closing and restarting other software attached to it. The pausing and jumping would mean the xport process is losing a lot of processor time. At those points you'll most likely notice your CPU at 100% where a foreground process is being prioritized. Try setting the xport process priority to high and see if that helps. You may only see XPort at 0-1%, but it still needs the speed while it's in the background.

curiosity when this happens, i close all sodtware attached to Xport and just open GPSINFO to check out, it would just get stuck in that situation where it would show ZERO sats, and speed momentarily jumps to over 300km/h..and sats would be 40 for a split second or something...then back to zero.

My cpu is a brand new i530... I never had an issue when i used my old AMD sempron along with winXP... changed so many hardware & software, it is hard to trace it now..as it only happens once in while as i said..Is there a way to prioritize Xport for ever,? or do i need to change it everytime?

EDIT: just came back from a ride.. it did the same thing..i turned gpsinfo to see, and all the lined coming out were red.. i have not seen this before.. I checked CPU and it was 15% as always.. no change tried to increase the priority..nothing... only closing and restarting Xport would solve this.
I am using the 2009 prolific driver.. i changed it to the 2005 now and i will see how this would help

It sounds like it wouldn't help to bump the priority of xport then. Having to restart Xport means that it's receiving data in a timely fashion (not idle for more than 7.5 seconds). Yes, I know that's a long time, but most offten the problem is that it just stops. In your case it's either coming in bursts or corrupt. I can't tell without a log. If it's corrupt, you can try the NMEA filter option which can reopen the port if the data is corrupt.

But if it works continuously direct without xport, then xport isn't doing the job.