My questions is: Only one input would be provided to the Wi-Fi bridge (from the termination of the daisy chain) and I am wondering whether Seatalk 1 and Seatalk NG would be available within that. If not could I use a SPUR and feed the Seatlak 1 input and NEMA 2000 input (for Seatalk ng)?
Your help is much appreciated!
]]>Thanks
Dave
The AIS unit I discovered the issue with is a B&G NAIS500. I'm sure all Navico units would be the same. As far as I can tell, the actual manufacturer for Navico units is Alltech Marine Electronics Corp (AMEC). I would also presume all AMEC units regardless of whose name is on it would present the same issue. The MFDs I'm aware of that play an integral part in this issue are Standard Horizon (model CP300I) and Garmin (model 740S).
The issue occurs when the suspect AIS measures a low or zero SOG, whereupon it sets COG as invalid. The suspect MFDs do not display an icon without a valid COG. However, the AIS vessel is listed in the AIS List. So the MFD knows the vessel's location but does not display the icon on the chart. When the AIS vessel's SOG increases, the COG becomes valid and the icon is then displayed on the chart.
Looking further into this issue I found other AIS units set COG as valid when SOG is low or zero. So these AIS units' icon will be displayed on the suspected MFDs. Also, other MFDs (verified on B&G Zeus Touch and Raymarine A series) will display an icon even when COG is invalid.
For my setup, I also found that if Heading is sent to the NAIS500 it will transmit this parameter in AIS Message 18 and the suspected MFDs will then display an icon. This lead me to conclude that the suspected MFDs need at minimum either a valid COG or valid Heading to display the icon. If both are invalid then the icon is not displayed. Heading can be sent via NMEA0183 or NMEA2000, I tested both with success.
If you have a suspected AIS and want to be seen on all MFDs but do not want to wait for firmware updates, then look into sending Heading to your AIS.
Has anyone else noticed this issue? Was a particular vessel's icon display sometimes and not at other times? Could this difference be attributed to being underway versus anchored or moored? Do you have a Navico, McMurdo, or AMEC AIS and someone didn't see you on their MFD? Do you have a Garmin, Standard Horizon, or other MFD and didn't see a known AIS vessel on your MFD? If known, who produced the AIS that wasn't displayed?
]]>Also, what converter do you recommend to use the old Autohelm depth sender to the new Garmin?
Last question, how to feed the new Garmin data to an ST7000 autopilot.
Thank you!!
I have a Catalina 34 with 25+ year electronics that I am replacing with NMEA 2000. I don't race, but I do like to sail efficiently. So far, I have an Evolution autopilot with a P70 that is awaiting installation. I've removed my old depth and speed transducers, patched one of the holes and installed an Airmar DST800.
For an MFD, I am looking towards either a B&G Zeus3 or a Raymarine Axiom. I have been told the B&G will control the Evolution (sail to apparent wind angle) and I have been told it will not. I understand I do need to use the P70 for calibration and I'm fine with that. My issue becomes getting wind data- both true and apparent.
I am told the Raymarine wind sensor will need to go through an ITC-5 and also an I70 (or similar) in order to generate N2K true data. I don't want added complexity and more gauges. Ah hah! Why not use a B&G 608 masthead sensor that will natively produce N2K data! I am told this will work, but it will only give apparent speed and angle. How do I get the true readings? Will the Evolution generate true wind? Will the Axiom? Will the Zeus? Answers are all over the place. Which piece of hardware will actually perform the calculations?
Then I thought maybe the way to go is with an Airmar 220 wind sensor which includes the GPS and can deliver native true and apparent data. I think this would eliminate any guess work. Until I came across this article
http://www.cruisersforum.com/forums/f13/masthead-wind-instruments-nmea-2000-or-0183-a-161493.html
which argues that there can be only one source of GPS and that the GPS on the Airmar would essentially shut down. Is this true or would it still function to determine true readings, just not report GPS on the N2k network (since the GPS is coming from the Axiom or Zeus anyway)? In this kind of situation is an Airmar 220 no better than a 120 without GPS?
To complicate matters further, has anyone ever heard of the LJ Capteurs wind sensors referenced in the above forum thread? It is currently listed for sale at the Fugawi website. While I could get apparent data from this unit I am still back at square one as to what piece of hardware will generate the true speed and true direction data.
I am not married to either Raymarine or B&G (except to the autopilot at this point) so whichever MFD would be the better fit is how I am going to proceed. From a sailing perspective (dynamic lay lines, polar data, etc.) any thoughts here?
Your time, advice and guidance is very much appreciated. Thank you!
Tim Weber,
Wheaton, IL
I'm having an issue getting the Simrad radar via the Ri10 box to pick up and use the heading from the Raymarine EV1 heading sensor/compass.
I have a Simnet to devicenet female connector running from the Ri10 box. And rather than cut the end off and attached it to a SeatalkNG spur end, I have connected it to a male devicenet to SeatalkNG cable, then plugged it into the network.
In theory it could work as the pin out from the male and female ends are compatible, but the Radar doesn't seem to be able to find the EV1 on the network. The MFD can no problem, but not the radar.
That to me suggests either a problem trying to link to the network like this, or an issue with my box. I'm guessing the former.
Without cutting up expensive cables, is there an alternate way to join the Simnet Ri10 to a SeatalkNg backbone?
]]>Will
]]>