Post Reply 
 
Thread Rating:
  • 1 Vote(s) - 5 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Merc Gateway PNG Conflict - NEW SOFTWARE REQUESTED
05-09-16, 08:57 AM
Post: #1
Merc Gateway PNG Conflict - NEW SOFTWARE REQUESTED
Hello Raymarine,

I'm using the E95 running latest software.
Attached to the Seatalk NG (NMEA2000):
- Merc Gateway (engine data)
- Lenco AutoGlide

Both devices are reporting on PNG 130576
Merc is transmitting 0 (No Trimtab connected to the engine)
Lenco is reporting the proper Trimtab position

So the problem is when the engines are turn ON, both devices (Lenco & Merc Gateway) are reporting the Trimtabs position. Because both device are reporting different value, the E95 is just flashing between the values.

The "Data Source" feature has been add for other sensors such as Depth, Water Temp... It appear the TrimTabs has been forgotten.

Would it be possible to add in the next software upgrade a "Data Source" for the Trimtab feature ?

Thanks in advance
David
Find all posts by this user
Quote this message in a reply
05-09-16, 11:10 AM
Post: #2
RE: Merc Gateway PNG Conflict - NEW SOFTWARE REQUESTED
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.
Visit this user's website Find all posts by this user
Quote this message in a reply
05-09-16, 12:50 PM
Post: #3
RE: Merc Gateway PNG Conflict - NEW SOFTWARE REQUESTED
Hello Chuck,
Many thanks for your prompt answer.
I already contacted Mercury and unfortunately there is no software upgrade possible to their gateway. The product management group have confirmed the situation. The PNG list will be broadcast with or without the equipment connected in their input.

They mentioned there is some trimtabs (racing product) that will be interfacing directly with the engine and this is the only reason why this specific PNG is broadcast. They said it is the MFD responsibility to provide option to the end-user to choose and pick to appropriate PNG stream.

This problem has been observed in the past with different sensor such as Depth and Water Temp. The path that Raymarine took by creating and developing "Data Source" menu is a quick and easy fix for all those conflict.

Is there any possibility to see this as a new feature in the next release ?

Thanks again for your support.
David
Find all posts by this user
Quote this message in a reply
05-09-16, 01:26 PM
Post: #4
RE: Merc Gateway PNG Conflict - NEW SOFTWARE REQUESTED
Dan,

Contrary to what has been stated by Mercury Marine, it is indeed technically possible for Mercury Marine to implement the specified solution, but have chosen not to. With respect to marine industry communications interfaces, it is Raymarine's policy to design to the industry specification (in this case the NMEA 2000 specification), not work around errors within third party implementations.

The Data source selection was not implemented as such a workaround, but rather to support multiple instances of data sources, each having unique instances. In this case, the Mercury gateway is generating the same instance numbers are the trim tabs. Under similar circumstances, the one of these would be re-programmed using tools provided by the device manufacturer to have differing instance numbers. It is recommended that you continue lobbying Mercury Marine accordingly.

Your feature request has been logged accordingly to be considered for inclusion within a future a/c/e/eS/gS-Series MFD software updates as well as well as within future MFD designs.

Please click here more information concerning product and feature suggestions.
Visit this user's website Find all posts by this user
Quote this message in a reply
Post Reply 


Forum Jump:


User(s) browsing this thread: 1 Guest(s)

Contact Us