Can't See any Satellites

[italy333333]

I have a Holux CF GM-270, and I have been using it for about a year now. I put it away for about one month and decided to break it out again. The problem is now I can't see a single sat, even though I allow the gps to have a clear view of the sky for over 5 hours. I tried to factory reset the device, and cold start it. I emailed the company, but I received no answer. Should I buy a new unit? There is abosultely no physical abuse, what could it be?

[alix776]

i have similar problems with my pretec cf card its likely the almanac has been lost so it will have to reaquire that but it shouldnt take that long
have you changed cars if not are the comport settings correct for software and device you have
_________________
currently using aponia truck navigation on windows phone. Good bye IOS don't let the door hit you on the way out .

Oh the joys of being a courier.
device Lumia 950 xl

[italy333333]

I have tried to aquire the almanac from out side with a clear line of sight, but no luck. My com port is set exactly the same as it used to be, Com 5 4800 Baud rate. It is the strangest thing. The unit flashes, but no sattelites are ever seen. Anyone have a fix for this?

[Dave]

Having left it on for 5 hours should suffice, however first I would make sure you don't have an athermic UV coated windscreen and try it outside of the car just in case.

I would also use WinFast Navigator to watch the NMEA data coming through the GPS Receiver to make sure you have the correct COM port available, it maybe that you've installed something since like TomTom and there's a new TomTom ~ GPS driver that's blocking communication.

Almanac and Ephemeris (complete data) requires about 12.5 mins to download first time, so giving it 15-20 mins should suffice in getting a full 3D fix unless you have an athermic UV coated windscreen or a bad view of the sky.

[italy333333]

I hoked up the gps outside the car for another try, I also used the program in question. All I got was as output was this

$Baud rate: 4800 System clock: 12.277MHz
$HW Type: S2AR
$GPGGA,235948.000,0000.0000,N,00000.0000,E,0,00,50.0,0.0,M,,,,0000*3A
$GPGSA,A,1,,,,,,,,,,,,,50.0,50.0,50.0*05
$GPRMC,235948.000,V,0000.0000,N,00000.0000,E,,,260102,,*12
Comm: Unknown chars: 24 47 50 24
Comm: Unknown char: 56
Comm: Unknown char: 65
Comm: Unknown char: 72
Comm: Unknown char: 73
Comm: Unknown char: 69
Comm: Unknown char: 6F
Comm: Unknown char: 6E
Comm: Unknown char: 20
Comm: Unknown char: 32
Comm: Unknown char: 32
Comm: Unknown char: 30
Comm: Unknown char: 2E
Comm: Unknown char: 30
Comm: Unknown char: 30
Comm: Unknown char: 36
Comm: Unknown char: 2E
Comm: Unknown char: 30
Comm: Unknown char: 30
Comm: Unknown char: 30
Comm: Unknown char: 45
Comm: Unknown char: 53
Comm: Unknown char: 0D
Comm: Unknown char: 0A
$Version user GM-270WAAS
$TOW: 0
$WK: 1151
$POS: 6378137 0 0
$CLK: 96000
Comm: Unknown chars: 24 43 48 4E 4C 3A 31 32 0A
Comm: Unknown char: 0D
Comm: Unknown char: 0A

over and over again with no fix, and zero sats. Are these unknown chars because I am using a protical that my unit does not support?[/img]

[lbendlin]

Uh-uh - it looks like the serial interface has serious troubles. This looks like bit errors (ones corrupt into zeroes.)

This is not a GPS problem - this is a RS232 problem, either in the receiver, the cable, or the Pocket PC .

Any visible damage on the cable or the connectors?
_________________
Lutz

Report Map Errors here:
TomTom/TeleAtlas NAVTEQ

[Dave]

Also check that all pins are facing upwards in the CF slot in the Pocket PC, you may have some bent pins.

[HOLUX UK Tech]

I would second Dave's point on this.......

Looking at the scrolling data again it looks at though the GM-270 is trying to continually re-boot, hence you wont attain a signal lock. If your GM-270 is still under warrenty conditions I would suggest returning it to your supplier for testing.

We see you’re using an ad-blocker. We’re fine with that and won’t stop you visiting the site.
Have you considered making a donation towards website running costs?.
Or you could disable your ad-blocker for this site. We think you’ll find our adverts are not overbearing!