Merc Gateway PNG Conflict - NEW SOFTWARE REQUESTED

[Chuck - Raymarine - Moderator]

Welcome to the Raymarine Forum David,

It would appear that the root cause of the issue is that the Mercury system is transmitting NMEA 2000 trim tab data when in fact the Mercury system has not been interfaced to a source of trim tab data (i.e. Mercury gauges are not reporting trim tab data). Please note that Raymarine's a/c/e/eS/gS-Series MFDs are designed to default to using the lowest NMEA 2000 instance number when more than one device within the system is transmitting the same PGN(s). Compounding the problem is that it appears that Mercury system is producing NMEA 2000 PGNs featuring the same instance number as the LENCO tabs, resulting in the dithering of data that you have specified. This may be verified by interfacing a NMEA 2000 CAN bus analyzer (ex. Actisense NGT-1-USB w/NMEA Reader PC software, etc.) to monitor traffic on the NMEA 2000 bus. If found to be so, then the correct path to resolving this issue recommend that Mercury Marine be contacted to seek an update to its SmartCraft to NMEA 2000 data bridging device to NOT transmit the NMEA 2000 PGN 130576 unless interfaced to a source of trim tab data.