BU-353 Problem - Page 2

tracker64 · 07-12-2007, 06:59 PM

oops sorry, you are right at 4800, it was late that night i was half out lol

kelmk · 12-31-2007, 01:59 PM

This thing is driving me crazy. I'm ready to toss it out the window.
Everytime I reboot the bu-353 stops working. The port COM3 is there and it's set to 4800 but gpsinfo or xport won't detect it.
The only way I can get it to work sometimes is to uninstall it and rescan for hardware and sometimes it will work and usually not. unplugging and plugging does the same thing. Once it is working it will usually survive a suspend/restore but once I reboot it's busted again.
I have tried different usb ports and com ports but I get the same behavior no matter what. This is my second bu-353 btw and the first had the same problem.
Are there any drivers newer than 2004 for this thing?
I'm using XP Pro

DarquePervert · 12-31-2007, 02:16 PM

Try disabling power saving for the Prolific device in the device manager, as well as all your USB root hubs.

kelmk · 12-31-2007, 04:41 PM

That didn't help. If I check the power status of the bu-335 in device manager it says D0.

linkyone · 12-31-2007, 05:05 PM

Im not too familiar with this device but my older one has a red LED on it. Does this one? if so does it light up? Everyone else has trouble shot everything that i can think of besides power. How do you all have it connected? USB hub, right off the computer? laptop or desktop? how long is the usb cord from the plug to the device? since we are working with DC power, the longer the wire the least ammount of available voltage thus the device is not to be found.

kelmk · 12-31-2007, 05:09 PM

Yes it has a red LED. Mine is lit up. I have tried with a hub and without. It doesn't really make any difference.

BLK MAJK · 01-27-2008, 08:25 AM

same for me. When I boot up the computer it is like it doesnt exist, yet it worked fine for about a year. Sometimes if I unplug and replug it in, it will work.....yarg we need to find a fix...

parksgm · 01-29-2008, 08:24 PM

Quote: Originally Posted by tracker64

if you don't set the BU-353 at 9600 baud you WILL NOT get any output and it will not work at all until you set it at 9600 baud, in port properties and in GPS application software...

Actually, it depends on the unit. My unit works only at 4800 baud (unit and COM port settings), others have reported it working at 38400 (or whatever is close to 38000).

kelmk · 01-29-2008, 08:29 PM

I fixed this issue. Its pretty simple really. Download devcon.exe and write a batch file to disconnect your bu-335 and then rescan for devices. This is essentially the same as replugging in the gps. Put the batch file in your startup.
mine works flawlessly now.

"c:\devcon.exe" -remove *VID_067B*
"c:\devcon.exe" rescan

parksgm · 01-29-2008, 09:31 PM

Quote: Originally Posted by kelmk

I fixed this issue. Its pretty simple really. Download devcon.exe and write a batch file to disconnect your bu-335 and then rescan for devices. This is essentially the same as replugging in the gps. Put the batch file in your startup.
mine works flawlessly now.

"c:\devcon.exe" -remove *VID_067B*
"c:\devcon.exe" rescan

Xport, which is freeware and available on the forums, also claims to disable and reenable devices on startup/shutdown/hibernate/resume, but doesn't require a batch...just a check box (for those who might not want to use devcon).

kelmk · 01-29-2008, 09:42 PM

xport never fixed anything for me. I actually switched to gpsgate and devcon and no more problems.

nasa · 03-18-2008, 06:21 PM

Hi,

For those of you for which the bu-353 wasn't showing up as any device -- did you ever solve it? I am having the same issue and am wondering if it's dead....

RipplingHurst · 03-20-2008, 01:48 AM

I am having similar issues, but with the Garmin 18...I think it's a driver issue, nothing to do with the device itself. It all started when I plugged in a different USB port than the one I first tested/installed it. Since then it works if I unplug, uninstall everything, then installing it back again. But when I reboot, gone. Undetected. I think what I will do is to remove all traces of it from the registry, etc. and see what happens.