HomeHardware


BU-353 Failure? LED status indicator is off.
t1d
I read a couple of threads on BU-353 failures and I don't see anything that I think addresses my issue...

History
Loaned a friend my BU-353 to do some testing on a Linux OS, because I had read that the receiver would run on Linux. He got it to work. Then, had him try my spare Pharos 500 and he got it to work. So, I gave him the Pharos 500 as a gift and retrieved my BU-353. Immediately upon hooking it back up to my laptop, it failed.

Symptoms
1) No power light - Solid red or blinking.
2) S&T can't see the receiver and no satellites are acquired.
3) XPort and Compass can see the receiver, but no satellites are acquired.

Attempted Resolutions
1) Uninstalled and reinstalled driver various times.
2) Checked configuration at Device Manager/Com Port/Prolific level and reset com port.
3) Used my Father's BU-353 to test my laptop. It works just fine.
4) Tested my BU-353 on my Father's laptop with S&T. No power light and can't see receiver.

Diagnoises
BU-353 is dying/dead. It is just a coincidence that it died in the transition from the Linux machine back to my laptop.

Do you concur? What else might I try?

Thanks!
tcassidy
Power light? Mine doesn't have one...blinking or otherwise.

I would suggest you check Device Manager to ensure there is no yellow exclamation mark next to a COM port entry with a Prolific identification. However, if xPort can see it, most likely you just need to leave it outside (while powered) to recover its almanac. It can take a while if the unit has lost it.

Aha...I just found the power light!!

Terry
tcassidy
Another thing to remember about the BU-353. Unlike the GPS500, it will be on a different COM port if you plug it into a different USB port. You can check which one it is using in Device Manager.

Terry
Attached Images
bu-353.jpg  
tcassidy
Another possibility is it was switched to SiRF mode. I found a thread on MP3Car about that and also a link to SiRFdemo. Use at your own risk if everything else fails!

BU-353 not detected & gibberish

Falcom: SiRF

Terry
Marvin Hlavac
LED status indicator
LED OFF - GPS receiver is off (no power)
LED ON (solid) - No fix, searching for GPS signals
LED FLASHING - Position fix established, and GPS signals are being received

Since you see no light at all, I suspect the BU-353 is faulty (the unit is not receiving power from the laptop's USB port).
tcassidy
While I agree with you Marvin would it show up in Device Manager if it was not getting power?

Terry
Marvin Hlavac
You are likely correct, Terry, chances are the Device Manager wouldn't show it.

Beside the documented and above mentioned three states of the red LED (On, Off, and Flashing), there actually is one more: Dim. So the question is: Is the LED off completelly, or is it simply very dim? Test it in the dark room, please. ;-)

If the red LED is dim, it may indicate the receiver is not in NMEA mode. It may be in SiRF mode, in which case you would need to switch it back to NMEA either by using SiRFdemo software, or by simply letting the internal rechargeable battery discharge. When the battery discharges, the unit should reset to factory settings (NMEA, etc). I think the battery should discharge if the unit is not plugged in a USB port for at least three days.

I believe the CD included with BU-353 contains a software utility which also allows for resetting to factory settings.
t1d
Quote:
Originally Posted by tcassidy
Another possibility is it was switched to SiRF mode. I found a thread on MP3Car about that and also a link to SiRFdemo. Use at your own risk if everything else fails!

BU-353 not detected & gibberish

Falcom: SiRF

Terry
Terry is the Winner, Winner, Chicken Dinner!!!

Downloaded SiRFDemo from the referenced link and installed.
The program did not initially see the BU-353 until I went to Action/Open Data Source.
Then, I followed the rest of the italicized instructions from the referenced thread:
Quote:
I set the com port settings to the standard 4800,8,n,1,n
I loaded SirfDemo and picked the right com port.
I then hit connect, but it kept giving me errors.
So I clicked Action -> Synchronize Protocol and Baud Rate
AND IT FOUND IT!!!
then I went to Action -> Switch to NMEA Protocol.
It is likely that, in my case, I did not need to do the synchronization step... But, it did not hurt anything... I did have to tell it to use 4800 baud... Can't remember if that was during the sync step or switching to NMEA... But, it was one of the two...

So, I think my friend not only used it on a Linux OS, but also change the protocol. He did not have the box and disk with him at the time we exchanged receivers... So, I will have to be sure to get that back, next chance I get...

Marvin, I did not see a dim light indicator for this condition.

Additionally, my unit had been sitting around for more than three days without use and had not reset to the default settings.

I have always been impressed with the generous experts on this forum... Y'all rock! Thank you so much for the help and saving me the $35 to buy a new one... But, now I don't have an excuse to buy a QStarz BT

Good thread! Did we rise to the lofty level of sticky-status?
tcassidy
Gotta watch out for those Linux types!!

Terry
laptopgpsworld.com About