nmea - talkers - listeners and lessons learned.
 

Armond Perretta wrote:
Ansley W. Sawyer wrote:

...
I have almost the same set up as do you. I have installed a Brookhouse
multiplexer so that I do not have to switch NMEA talkers on and off.
The GPS(Furuno 7000), Autopilot(Simrad Robertson AP20 with 3000x
box), and the fathometer (Furuno RD30 with Airmar transducer) all
feed into the multiplexer. The multiplexer then feeds out to the GPS,
Radar Position (Furuno 1721M2), Radar Compass, Autopilot, & Depth and
the computer ...


I think I am getting somewhere now thanks to your explanation, but still a
few questions. Why first feed GPS info into the multiplexer, than out from
the multiplexer back to the GPS? To allow route and waypoint uploads to the
GPS?


... The AIS receiver(Milltech SR161 with antenna splitter)
I feed straight into the computer with the Cap'n software. The
computer get GPS data from the multiplexer and AIS data from the AIS
receiver. It all works great.


This is I believe the question I am trying to address. Are you saying that
by feeding GPS data and AIS data _separately_ into Capn 8.3, they are
combining in the Capn software to properly display AIS info on the chart?

That is correct. GPS data into COM1, AIS data into COM2. Is works great.
The same think for Coastal Explorer.

Hanz

nmea - talkers - listeners and lessons learned.
 

Armond,

I send GPS data to the multiplexer which then sends it to the computer and
to the radar and to the fathometer display (which is a multifunction
display). This gives me position, COG, SOG, and waypoint info wherever I
want it.

I have the AIS and GPS entering the computer on two different ports due to
the difference in baud rates and the data plots are great. My understanding
of the new Brookhouse multiplexer is that it will combine AIS data with
other data and send it all together.

Check out this: http://brookhouseonline.com/pdf%20files/Mux_AIS_C.pdf


Ansley Sawyer
SV Pacem

nmea - talkers - listeners and lessons learned.
 

"Peter Bennett" wrote in message
news.com...

Note that normal NMEA-0183 data is sent at 4800 baud, while AIS data
is normally sent at 38400 baud - they can't coexist on the same
circuit. My Raymarine C80 chartplotter/radar display can accept AIS
data at 38400 on its serial port, while the GPS and other NMEA-0183
data goes into the SeaTalk system via a Raymarine NMEA=SeaTalk
interface box.

Peter,

The SR161 can be used to consolidate incoming NMEA positional data from a
GPS with the AIS NMEA data into a combined high-speed data stream on a
single serial port.

In that scenario there is no need for any multiplexer.

nmea - talkers - listeners and lessons learned.
 

"claus" wrote in message
. ..

"Peter Bennett" wrote in message
news.com...

Note that normal NMEA-0183 data is sent at 4800 baud, while AIS data
is normally sent at 38400 baud - they can't coexist on the same
circuit. My Raymarine C80 chartplotter/radar display can accept AIS
data at 38400 on its serial port, while the GPS and other NMEA-0183
data goes into the SeaTalk system via a Raymarine NMEA=SeaTalk
interface box.

Peter,

The SR161 can be used to consolidate incoming NMEA positional data from a
GPS with the AIS NMEA data into a combined high-speed data stream on a
single serial port.

In that scenario there is no need for any multiplexer.

Forgot to add the link to the Wiring diagram for connecting a GPS into the
AIS receiver using a Single Serial Port on the Computer:

http://www.milltechmarine.com/images...ng-diagram.pdf

nmea - talkers - listeners and lessons learned.
 

On Jul 18, 11:24*am, "claus" wrote:
"Peter Bennett" wrote in message

news.com...

Note that normal NMEA-0183 data is sent at 4800 baud, while AIS data
is normally sent at 38400 baud - they can't coexist on the same
circuit. *My Raymarine C80 chartplotter/radar display can accept AIS
data at 38400 on its serial port, while the GPS and other NMEA-0183
data goes into the SeaTalk system via a Raymarine NMEA=SeaTalk
interface box.

Peter,

The SR161 can be used to consolidate incoming NMEA positional data from a
GPS with the AIS NMEA data into a combined high-speed data stream on a
single serial port.

In that scenario there is no need for any multiplexer.

Right - just to clarify a couple of things:
1. AIS Receivers do not need GPS signals to output AIS sentences. They
work independent of GPS.
2. With the SR161/SR162, you can feed GPS (or any other NMEA data)
into the AIS receiver at 4800 baud on pin 3 and the receiver will
combine the data with the AIS sentences and output the combined
datastream out the single serial port at 38400 baud on pin 2 with a
common ground on pin 5. We sell a cable to do this and also include
the wiring diagram to build your own. See:
http://www.milltechmarine.com/images...ng-diagram.pdf


Doug Miller
Milltech Marine

nmea - talkers - listeners and lessons learned.
 

On Jul 18, 11:48*am, Doug Miller wrote:
...
Right - just to clarify a couple of things:
1. AIS Receivers do not need GPS signals to output AIS sentences. They
work independent of GPS.
2. With the SR161/SR162, you can feed GPS (or any other NMEA data)
into the AIS receiver at 4800 baud on pin 3 and the receiver will
combine the data with the AIS sentences and output the combined
datastream out the single serial port at 38400 baud on pin 2 with a
common ground on pin 5. We sell a cable to do this and also include
the wiring diagram to build your own. See:http://www.milltechmarine.com/images...ng-diagram.pdf

Doug Miller
Milltech Marine

Cool. I'm in the market for an SR 161. Does it help the unit any to
have a GPS feed or does it just pass the data through. I can imagine
how the unit might take advantage of knowing the packet timing, but I
don't know if does.

-- Tom.

nmea - talkers - listeners and lessons learned.
 

Doug Miller wrote in news:f31faed5-6a54-4b92-999a-
:

http://www.milltechmarine.com/images...ng-diagram.pdf

Thank you. I didn't know it did that....

nmea - talkers - listeners and lessons learned.
 

The SR161 can be used to consolidate incoming NMEA positional data from a
GPS with the AIS NMEA data into a combined high-speed data stream on a
single serial port.

In that scenario there is no need for any multiplexer.


but how does it talk to other non-high speed nmea devices then?

nmea - talkers - listeners and lessons learned.
 

"Josh Assing" wrote in message
...
The SR161 can be used to consolidate incoming NMEA positional data from a
GPS with the AIS NMEA data into a combined high-speed data stream on a
single serial port.

In that scenario there is no need for any multiplexer.


but how does it talk to other non-high speed nmea devices then?

The AIS only "talks" with either
a)a PC with chart plotting software that can show AIS or
b) directly to a chartplotter that can show AIS.

For example, on our boat the SR161's combined output goes to a PC with
Coastal Explorer software. In turn, Coastal Explorer and the PC outputs NMEA
(4800 Baud) to our Raynav Chartplotter and from there to all other
instrumentation onboard via RayMarine's proprietary Seatalk network.

Hope this helps. If I could I would send you a diagram - but I don't have a
scanner.... :-(

nmea - talkers - listeners and lessons learned.
 

On Jul 18, 6:30*pm, " wrote:
On Jul 18, 11:48*am, Doug Miller wrote:
...

Right - just to clarify a couple of things:
1. AIS Receivers do not need GPS signals to output AIS sentences. They
work independent of GPS.
2. With the SR161/SR162, you can feed GPS (or any other NMEA data)
into the AIS receiver at 4800 baud on pin 3 and the receiver will
combine the data with the AIS sentences and output the combined
datastream out the single serial port at 38400 baud on pin 2 with a
common ground on pin 5. We sell a cable to do this and also include
the wiring diagram to build your own. See:http://www.milltechmarine.com/images...ng-diagram.pdf

Doug Miller
Milltech Marine

Cool. *I'm in the market for an SR 161. *Does it help the unit any to
have a GPS feed or does it just pass the data through. *I can imagine
how the unit might take advantage of knowing the packet timing, but I
don't know if does.

-- Tom.

GPS does affect AIS perfofrmance but of course you'll need a GPS for
your nav package in order to calculate collision information (e.g.
distance from you, closest point of approach and time to closest point
of approach).