Quote:
Originally Posted by Kelkara
Does the H102 even have a display?
Or are you asking whether the AIS receiver will send to your plotter the info that the signal originated from a MOB1 and not a ship? The answer to this is "yes", it is treated like a class A signal, but with an MMSI that starts 972 (MOB code, rather than a country code), and a navigation status as SART (rather than underway/anchored/etc) ... as long as the message gets through to the plotter, that info will be there.
But then you need to ask, what will your plotter display?
|
I am asking if the h102 receives the signal from the MOB1 properly, means as you described with 972 and if it’s is able to put this on the
NMEA 0183 Network.
You are sure and own a H102 or know someone who does or just in theory? That’s standard and works with all from 2015 on, but how old is the h102
hardware and software in reality...0183 is long before 2015,why doesn’t it have n2k...
I have old Seatalk/NMEA 183 with
Raymarine c70 plotter and
Seatalk NG/Nmea2000 with
Raymarine eHybridtouch/lighthouse 2 plotter on board.
As in another thread a H102 owner connected successfully the h102 with a
B&G Zeus2 plotter via
NMEA 0183 and all works fine, I don‘t see an issue there as it connects via NMEA0183 with 36400bauds what both of my plotters can
work with too. Via the
seatalk old to new adapter it also gets translated to n2k and the YachtDevices
nmea WiFi dongle puts all Nmea0183 and n2k data on the
boat WiFi so I can use it via ISailor on my 12.9 Ipadpro too.
I often have inexperience crew or guest on my cat and the MOB1 is in every lifevest installed so my AIS need to be able to receive it properly.