I purchased an HP Stream 8 tablet and one of the reasons I
got it was it has a built-in Broadcom GPS. I have Open
CPN installed on my Toshiba laptop and it works great in
conjunction with my GlobalSat BU-353S4.

The laptop is Windows 8.1 and so is the Stream 8 tablet.
OpenCPN installed perfectly on the Stream as it did on
the laptop. It found and configured all the charts when
I pointed it to the chart folder.

However, OpenCPN can't seem to *find* the built-in
Broadcom GPS although it finds and works just great with
the BU-353S4, The Broadcom internal GPS connects via
COM1 serial port while the BU-353S4 creates a virtual
com port it calls COM3. The only difference I can see
is COM3 defaults to 4800 baud while COM 1 defaults to
9600. But, even if I change it from 96000 to 48000 it
still won't connect.

Anybody know why not?

As a workaround I have just ordered a microUSB thumb
drive GPS which has drivers for both Windows and Android
devices so if I can't get the OpenCPN software to
recognize the Stream's internal GPS, I'll be able
to plug in the thumb drive and it will then create
a virtual Com3 port there so the Open CPN will be
able to enjoy the benefits of GPS.

Here is the Micro USB thumb drive GPS-

http://www.amazon.com/gp/product/B00...?ie=UTF8&psc=1

Notice the price. Cheap, huh?

Oh, the internal Broadcom GPS on the Stream tablet does work
because I downloaded and installed a car GPS navigator and it
manages to see and connect to the built-in GPS.

--
Sir Gregory

On Sat, 10 Jan 2015 17:01:48 -0500, "Sir Gregory Hall, Esq."
wrote:



I purchased an HP Stream 8 tablet and one of the reasons I
got it was it has a built-in Broadcom GPS. I have Open
CPN installed on my Toshiba laptop and it works great in
conjunction with my GlobalSat BU-353S4.

The laptop is Windows 8.1 and so is the Stream 8 tablet.
OpenCPN installed perfectly on the Stream as it did on
the laptop. It found and configured all the charts when
I pointed it to the chart folder.

However, OpenCPN can't seem to *find* the built-in
Broadcom GPS although it finds and works just great with
the BU-353S4, The Broadcom internal GPS connects via
COM1 serial port while the BU-353S4 creates a virtual
com port it calls COM3. The only difference I can see
is COM3 defaults to 4800 baud while COM 1 defaults to
9600. But, even if I change it from 96000 to 48000 it
still won't connect.

Anybody know why not?

As a workaround I have just ordered a microUSB thumb
drive GPS which has drivers for both Windows and Android
devices so if I can't get the OpenCPN software to
recognize the Stream's internal GPS, I'll be able
to plug in the thumb drive and it will then create
a virtual Com3 port there so the Open CPN will be
able to enjoy the benefits of GPS.

Here is the Micro USB thumb drive GPS-

http://www.amazon.com/gp/product/B00...?ie=UTF8&psc=1

Notice the price. Cheap, huh?

Oh, the internal Broadcom GPS on the Stream tablet does work
because I downloaded and installed a car GPS navigator and it
manages to see and connect to the built-in GPS.

===

Have you asked on the OpenCPN forum he

http://www.cruisersforum.com/forums/f134/

There are a bunch of world wide experts on there as well as some of
the software authors.

On Sun, 11 Jan 2015 15:49:04 -0500, Wayne.B
wrote:

On Sat, 10 Jan 2015 17:01:48 -0500, "Sir Gregory Hall, Esq."
wrote:



I purchased an HP Stream 8 tablet and one of the reasons I
got it was it has a built-in Broadcom GPS. I have Open
CPN installed on my Toshiba laptop and it works great in
conjunction with my GlobalSat BU-353S4.

The laptop is Windows 8.1 and so is the Stream 8 tablet.
OpenCPN installed perfectly on the Stream as it did on
the laptop. It found and configured all the charts when
I pointed it to the chart folder.

However, OpenCPN can't seem to *find* the built-in
Broadcom GPS although it finds and works just great with
the BU-353S4, The Broadcom internal GPS connects via
COM1 serial port while the BU-353S4 creates a virtual
com port it calls COM3. The only difference I can see
is COM3 defaults to 4800 baud while COM 1 defaults to
9600. But, even if I change it from 96000 to 48000 it
still won't connect.

Anybody know why not?

As a workaround I have just ordered a microUSB thumb
drive GPS which has drivers for both Windows and Android
devices so if I can't get the OpenCPN software to
recognize the Stream's internal GPS, I'll be able
to plug in the thumb drive and it will then create
a virtual Com3 port there so the Open CPN will be
able to enjoy the benefits of GPS.

Here is the Micro USB thumb drive GPS-

http://www.amazon.com/gp/product/B00...?ie=UTF8&psc=1

Notice the price. Cheap, huh?

Oh, the internal Broadcom GPS on the Stream tablet does work
because I downloaded and installed a car GPS navigator and it
manages to see and connect to the built-in GPS.

===

Have you asked on the OpenCPN forum he

http://www.cruisersforum.com/forums/f134/

There are a bunch of world wide experts on there as well as some of
the software authors.

I'm a bit embarrassed to ask, but did you "read the f--king manual"? I
ask as the manual does have a section concerning setting up a GPS
which includes instructions for CPN to work with "strange" GPS',
including a source for some drives such as a "Port Splitter" to allow
(example) port 10.
--
Cheers,

Bruce in Bangkok

In article ,
, Sir Gregory Hall, Esq. says...

I purchased an HP Stream 8 tablet and one of the reasons I
got it was it has a built-in Broadcom GPS. I have Open
CPN installed on my Toshiba laptop and it works great in
conjunction with my GlobalSat BU-353S4.

The laptop is Windows 8.1 and so is the Stream 8 tablet.
OpenCPN installed perfectly on the Stream as it did on
the laptop. It found and configured all the charts when
I pointed it to the chart folder.

However, OpenCPN can't seem to *find* the built-in
Broadcom GPS although it finds and works just great with
the BU-353S4, The Broadcom internal GPS connects via
COM1 serial port while the BU-353S4 creates a virtual
com port it calls COM3. The only difference I can see
is COM3 defaults to 4800 baud while COM 1 defaults to
9600. But, even if I change it from 96000 to 48000 it
still won't connect.

Anybody know why not?

As a workaround I have just ordered a microUSB thumb
drive GPS which has drivers for both Windows and Android
devices so if I can't get the OpenCPN software to
recognize the Stream's internal GPS, I'll be able
to plug in the thumb drive and it will then create
a virtual Com3 port there so the Open CPN will be
able to enjoy the benefits of GPS.

Here is the Micro USB thumb drive GPS-

http://www.amazon.com/gp/product/B00...?ie=UTF8&psc=1

Notice the price. Cheap, huh?

Oh, the internal Broadcom GPS on the Stream tablet does work
because I downloaded and installed a car GPS navigator and it
manages to see and connect to the built-in GPS.

Your workaround is what I do with OpenCPN. Never had a problem with the
virtual com port method - but make sure it's supported for the OS (ie
Windows 8). I'm running it just fine on Windows 7.

And note also (thought I doubt it will help) that OpenCPN just came out
with a new major release - V4...

http://opencpn.org/ocpn/download

--
Duncan.

On Mon, 12 Jan 2015 06:31:37 +0700, wrote:

On Sun, 11 Jan 2015 15:49:04 -0500, Wayne.B
wrote:

On Sat, 10 Jan 2015 17:01:48 -0500, "Sir Gregory Hall, Esq."
wrote:



I purchased an HP Stream 8 tablet and one of the reasons I
got it was it has a built-in Broadcom GPS. I have Open
CPN installed on my Toshiba laptop and it works great in
conjunction with my GlobalSat BU-353S4.

The laptop is Windows 8.1 and so is the Stream 8 tablet.
OpenCPN installed perfectly on the Stream as it did on
the laptop. It found and configured all the charts when
I pointed it to the chart folder.

However, OpenCPN can't seem to *find* the built-in
Broadcom GPS although it finds and works just great with
the BU-353S4, The Broadcom internal GPS connects via
COM1 serial port while the BU-353S4 creates a virtual
com port it calls COM3. The only difference I can see
is COM3 defaults to 4800 baud while COM 1 defaults to
9600. But, even if I change it from 96000 to 48000 it
still won't connect.

Anybody know why not?

As a workaround I have just ordered a microUSB thumb
drive GPS which has drivers for both Windows and Android
devices so if I can't get the OpenCPN software to
recognize the Stream's internal GPS, I'll be able
to plug in the thumb drive and it will then create
a virtual Com3 port there so the Open CPN will be
able to enjoy the benefits of GPS.

Here is the Micro USB thumb drive GPS-

http://www.amazon.com/gp/product/B00...?ie=UTF8&psc=1

Notice the price. Cheap, huh?

Oh, the internal Broadcom GPS on the Stream tablet does work
because I downloaded and installed a car GPS navigator and it
manages to see and connect to the built-in GPS.

===

Have you asked on the OpenCPN forum he

http://www.cruisersforum.com/forums/f134/

There are a bunch of world wide experts on there as well as some of
the software authors.

I'm a bit embarrassed to ask, but did you "read the f--king manual"? I
ask as the manual does have a section concerning setting up a GPS
which includes instructions for CPN to work with "strange" GPS',
including a source for some drives such as a "Port Splitter" to allow
(example) port 10.


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.

--
Sir Gregory

On Mon, 12 Jan 2015 13:45:02 +1300, Duncan McCormack
wrote:

In article ,
, Sir Gregory Hall, Esq. says...

I purchased an HP Stream 8 tablet and one of the reasons I
got it was it has a built-in Broadcom GPS. I have Open
CPN installed on my Toshiba laptop and it works great in
conjunction with my GlobalSat BU-353S4.

The laptop is Windows 8.1 and so is the Stream 8 tablet.
OpenCPN installed perfectly on the Stream as it did on
the laptop. It found and configured all the charts when
I pointed it to the chart folder.

However, OpenCPN can't seem to *find* the built-in
Broadcom GPS although it finds and works just great with
the BU-353S4, The Broadcom internal GPS connects via
COM1 serial port while the BU-353S4 creates a virtual
com port it calls COM3. The only difference I can see
is COM3 defaults to 4800 baud while COM 1 defaults to
9600. But, even if I change it from 96000 to 48000 it
still won't connect.

Anybody know why not?

As a workaround I have just ordered a microUSB thumb
drive GPS which has drivers for both Windows and Android
devices so if I can't get the OpenCPN software to
recognize the Stream's internal GPS, I'll be able
to plug in the thumb drive and it will then create
a virtual Com3 port there so the Open CPN will be
able to enjoy the benefits of GPS.

Here is the Micro USB thumb drive GPS-

http://www.amazon.com/gp/product/B00...?ie=UTF8&psc=1

Notice the price. Cheap, huh?

Oh, the internal Broadcom GPS on the Stream tablet does work
because I downloaded and installed a car GPS navigator and it
manages to see and connect to the built-in GPS.

Your workaround is what I do with OpenCPN. Never had a problem with the
virtual com port method - but make sure it's supported for the OS (ie
Windows 8). I'm running it just fine on Windows 7.

It works just fine on my Win 8.1 laptop using the COM3 port
the drivers for the GlobalSat Bu-352S4. It also works just
great on the Stream 8 Windows 8.1 tablet.

I was hoping to avoid having something stuck into the miniUSB
port since the Stream 8 has a built-in GPS but it's beginning
to look as if there is no other way at this time. As least the
mini USB GPS is quite small but if it gets dropped on it probably
it will ruin the mini port itself - bend it or break it.

And note also (thought I doubt it will help) that OpenCPN just came out
with a new major release - V4...

http://opencpn.org/ocpn/download

I doubt they did anything different concerning internal
device USB implementation recognition. The problem seems
to be too new.

The road navigation program I installed has no trouble finding
and configuring itself to use the internal Broadcom GPS. It
must include some subroutine that knows how to connect to
COM1 which is what the Broadcom internal GPS is using.

The good coders at OpenCPN need to copy and include that
subroutine as tablets with internal Broadcom GPS are
certainly not a scarce commodity.

On Sun, 11 Jan 2015 15:49:04 -0500, Wayne.B
wrote:

On Sat, 10 Jan 2015 17:01:48 -0500, "Sir Gregory Hall, Esq."
wrote:



I purchased an HP Stream 8 tablet and one of the reasons I
got it was it has a built-in Broadcom GPS. I have Open
CPN installed on my Toshiba laptop and it works great in
conjunction with my GlobalSat BU-353S4.

The laptop is Windows 8.1 and so is the Stream 8 tablet.
OpenCPN installed perfectly on the Stream as it did on
the laptop. It found and configured all the charts when
I pointed it to the chart folder.

However, OpenCPN can't seem to *find* the built-in
Broadcom GPS although it finds and works just great with
the BU-353S4, The Broadcom internal GPS connects via
COM1 serial port while the BU-353S4 creates a virtual
com port it calls COM3. The only difference I can see
is COM3 defaults to 4800 baud while COM 1 defaults to
9600. But, even if I change it from 96000 to 48000 it
still won't connect.

Anybody know why not?

As a workaround I have just ordered a microUSB thumb
drive GPS which has drivers for both Windows and Android
devices so if I can't get the OpenCPN software to
recognize the Stream's internal GPS, I'll be able
to plug in the thumb drive and it will then create
a virtual Com3 port there so the Open CPN will be
able to enjoy the benefits of GPS.

Here is the Micro USB thumb drive GPS-

http://www.amazon.com/gp/product/B00...?ie=UTF8&psc=1

Notice the price. Cheap, huh?

Oh, the internal Broadcom GPS on the Stream tablet does work
because I downloaded and installed a car GPS navigator and it
manages to see and connect to the built-in GPS.

===

Have you asked on the OpenCPN forum he

http://www.cruisersforum.com/forums/f134/

There are a bunch of world wide experts on there as well as some of
the software authors.

Thanks for the suggestion, Wayne. But no joy so far.

See the link I posted in response to Bruce's slur!

--
Sir Gregory

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

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

On Mon, 12 Jan 2015 06:31:37 +0700, wrote:

On Sun, 11 Jan 2015 15:49:04 -0500, Wayne.B
wrote:

On Sat, 10 Jan 2015 17:01:48 -0500, "Sir Gregory Hall, Esq."
wrote:



I purchased an HP Stream 8 tablet and one of the reasons I
got it was it has a built-in Broadcom GPS. I have Open
CPN installed on my Toshiba laptop and it works great in
conjunction with my GlobalSat BU-353S4.

The laptop is Windows 8.1 and so is the Stream 8 tablet.
OpenCPN installed perfectly on the Stream as it did on
the laptop. It found and configured all the charts when
I pointed it to the chart folder.

However, OpenCPN can't seem to *find* the built-in
Broadcom GPS although it finds and works just great with
the BU-353S4, The Broadcom internal GPS connects via
COM1 serial port while the BU-353S4 creates a virtual
com port it calls COM3. The only difference I can see
is COM3 defaults to 4800 baud while COM 1 defaults to
9600. But, even if I change it from 96000 to 48000 it
still won't connect.

Anybody know why not?

As a workaround I have just ordered a microUSB thumb
drive GPS which has drivers for both Windows and Android
devices so if I can't get the OpenCPN software to
recognize the Stream's internal GPS, I'll be able
to plug in the thumb drive and it will then create
a virtual Com3 port there so the Open CPN will be
able to enjoy the benefits of GPS.

Here is the Micro USB thumb drive GPS-

http://www.amazon.com/gp/product/B00...?ie=UTF8&psc=1

Notice the price. Cheap, huh?

Oh, the internal Broadcom GPS on the Stream tablet does work
because I downloaded and installed a car GPS navigator and it
manages to see and connect to the built-in GPS.

===

Have you asked on the OpenCPN forum he

http://www.cruisersforum.com/forums/f134/

There are a bunch of world wide experts on there as well as some of
the software authors.

I'm a bit embarrassed to ask, but did you "read the f--king manual"? I
ask as the manual does have a section concerning setting up a GPS
which includes instructions for CPN to work with "strange" GPS',
including a source for some drives such as a "Port Splitter" to allow
(example) port 10.


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.

Well, good luck.

I ran CPN for about two years plugged into a little USB GPS gizmo. I
don't remember the cost but it was pocket change as I remember. But,
of course, I had it connected to a lap-top.

But after re-reading your post I doubt that you don't have a real GPS
in that tablet as from what you say it only works with wi-fi. Called
AGPS or some such thing.

Strange you know. Every hand-phone I've had that had a GPS worked with
or without wi-fi.
--
Cheers,

Bruce in Bangkok

On Sun, 11 Jan 2015 21:47:46 -0500, "Sir Gregory Hall, Esq."
wrote:

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!


I had a similar problem with a Cheap Chinese hand phone. Set off on my
bicycle and got lost. Finally had to get a taxi to get me home
(cursing the hand phone all the way). after I got home I was looking
at the phone and goodness! There was a button to "Initialize GPS"
which required you to go outside and turn the phone around several
times or some such shenanigans and it has worked ever since :-)
--
Cheers,

Bruce in Bangkok