On Sun, 11 Jan 2015 20:13:14 -0500, "Sir Gregory Hall, Esq."
wrote:



Bruce, of course I read the freaking manual. And it was no help.

Here's proof from the forum WayneB kindly provided. It seems
like I'm not the only one having the same problem.

http://www.cruisersforum.com/forums/...-a-139272.html

I've even installed that same stupid TCP locator app but it's wildly
inaccurate and only updates every 30 seconds or so. It is relying
on any Wi-fi signals it manages to pick up. That's going to do
NO GOOD AT ALL out on the ocean where there are no wi-fi signals.

Duh.

What's needed is for Broadcom to get off their stupid asses
and provide device and bus drivers that output NMEA sentences
the lack of which I have concluded is the problem.

Either that or OpenCPN coders need to emulate how android
apps and at least a few windows apps manage to connect to
the Broadcom GPS and derive all the satellite information
therefrom thus managing to use the GPS without the benefit
of these NMEA sentences.


Guess what. In settings I turned off the wi-fi, the telephone
broadband and the blue tooth OFF.

I turned off the GNSS (GPS).

Then I opened the TCP utility. It sat there and nothing happened.
It couldn't find squat.

Then I turned on ONLY THE GNSS and it didn't work for about
a minute. It just said *initializing*. Well I let it set
and after about 30 more seconds it displayed the position
information meaning it had managed to interface with the
built in GPS and it could be connecting to nothing else
but because I'd turned off all the other radios.

I opened OpenCPN and VOILA. There was the red ship in the
right position - the exact right position whereas when
the wi-fi was on yesterday ALL it used was the wi-fi
or the wi-fi combined with the GNSS to give a bad position.

So that stupid little utility ACTUALLY WORKS.

One must start it first, let it initialize and get
a fix. One must have in included and configured
correctly in the connections on OpenCPN and
it gets recognized and use.

AMAZING!

--
Sir Gregory