01-13-16, 11:19 AM
Interfacing marine engines an Axiom/Axiom Pro/Axiom XL MFD or a/c/e/eS/gS-Series MFD
When operating with the latest software updates, the Axiom MFDs and a/c/e/eS/gS-Series MFDs are NMEA 2000 certified products. These products are compatible with engines systems (via an engine gateway), and some NMEA 2000 sensors (ex. fuel flow sensors). Raymarine does not maintain lists of NMEA 2000 engine makes/models and engine gateways, as this information is continuously changing and outside of the control of Raymarine. As such, it is recommended that one contact the engine manufacturer with the engine information (model, serial number, etc.) to determine whether the engine(s) features NMEA 2000 support or whether an engine gateway is available. When interfacing Raymarine equipment to a NMEA 2000 engine(s), the Raymarine equipment must not be interfaced directly to the engine manufacturer’s network backbone. Instead, the engine manufacturer's network backbone must be interfaced to a NMEA 2000 gateway (ex. Raymarine ECI-100 Engine Gateway, Volvo engine gateway, Yamaha engine gateway, Maretron J2K100, SmartCraft to NMEA 2000 Gateway, Fox Marine MEFI-1/2/3/4, Yacht Devices YDEG-04 (Volvo Penta, BRP Rotax and J1939 engines), Yacht Devices YDES-04 (engines with a J1708 serial interface), etc.). Third party analog engine to NMEA 2000 gateways (ex.
Actisense EMU-1, Noland RS11, etc.) are also available within the marine electronics industry to support the needs of those having older engines. The primary function of a NMEA 2000 engine gateway is control the flow of data between the engine system CAN backbone and the SeaTalkng/NMEA 2000 backbone used by the marine electronics. The second function of a NMEA 2000 engine gateway is to isolate the power on the engine system backbackbone from power on the marine electronics SeaTalkng/NMEA 2000 backbone. Raymarine’s ECI-100 presently supports integration with select Volvo, Yamaha, Yanmar, Honda, and Caterpillar marine engines.
To interface the engine(s), a powered and properly terminated SeaTalkng backbone must be installed onboard having SeaTalkng T-Pieces (SeaTalkng 5-way connectors may be substituted where NMEA 2000 devices are closely located) for each NMEA 2000 device (i.e. engines, sensors, data master MFD, etc.) which will be interfaced as a spur to the SeaTalkng Network backbone. A simple backbone may be constructed from the following components:
- A06064 SeaTalkng 5-Way Connector
- A06031 SeaTalkng Termination Plugs x 2
- A06049 SeaTalkng Power Cable
- a pair of SeaTalkng Spur Cables of appropriate length to interface the MFD and NMEA 2000 engine gateway to the SeaTalkng 5-Way Connector. An A06082 DeviceNet (F) to SeaTalkng (M) Adapter may be mated to a SeaTalkng Spur Cable to permit it to be mated the DeviceNet(M) socket of an Axiom/Axiom Pro/Axiom XL MFD.
As SeaTalkng/NMEA 2000 spurs are limited to 5m maximum length, should the cable routing distance between the MFD and NMEA 2000 engine system's backbone exceed 10m, then the 5-Way Connector listed above may be replaced with A06028 SeaTalkng T-Pieces which have been joined to one another using appropriate lengths of SeaTalkng Backbone Cable.More information concerning SeaTalkng/NMEA 2000 networking may be found here. Should the vessel not have an engine system backbone installed onboard, then it is recommended that the engine system manufacturer be contacted regarding the engine system manufacturer's components required to construct a backbone for the engine system.
The Data Master MFD will be interfaced to one of the spur sockets within the SeaTalkng backbone using an appropriate length of SeaTalkng Spur Cable ((400mm (A06038), 1m (A06039), 3m (A06040), 5m (A06041)). The chosen NMEA 2000 engine gateway(s) will also be interfaced to one onf the spur sockets within the SeaTalkng backbone. Raymarine offers SeaTalkng to DeviceNet Male (A06046) and SeaTalkng to DeviceNet Female adapter cables (A06045) as well as Stripped End Spur cables (A06044) to support interfacing third party NMEA 2000 devices as spurs to the SeaTalkng network backbone. Finally, the NMEA 2000 engine gateway(s) will be interfaced to the engine system per the NMEA 2000 engine gateway manufacturer's instructions.
The following engine data items are be supported when interfaced to a NMEA 2000 device supplying the corresponding data.
Battery 1/2 Amps/Temp/Voltage/% Charge
Engine 1/2/3/4/5:
- RPM
- Coolant Temp & Pressure
- Oil Temp & Pressure
- Transmission Oil Temp & Pressure
- Transmisson Gear
- Boost Pressure
- Fuel Pressure
- Fuel Flow Rate
- Fuel Flow Instantaneous
- Fuel Flow Average
- Engine Hours
- Engine Trim
- Alternator
- Engine Load
Fuel:
- Fuel Tank Levels 1/2/3/4/5
- Total Fuel Volume (Remaining)
- Fuel Flow Total
- Economy
- Est. Fuel Remaining
- Distance to Empty
- Time to Empty
- Fuel Used Trip
- Fuel Used (Season)
Tanks:
- Fresh Water %
- Grey Water %
- Black Water %
- Live Well
Note: When interfaced a third party engine gateway(s), it will be necessary to ensure that the vessel's engine(s) have been assigned a NMEA 2000 Device Instance Number(s) which is consistent with the NMEA 2000 convention of instancing when one or multiple engines, tanks, etc. have been installed onboard the vessel. Please click here to view a FAQ providing additional information on this subject. Failure of the engine system to comply with the instancing convention specified within the referenced FAQ will either prohibit data from all or some of the vessel's engines from being displayed by the MFD.
Should a compatible engine(s) be interfaced to the Raymarine system via a Raymarine ECI-100 Engine Gateway, then the MFD's Identify Engines feature must be used following installation to permit the MFDs to correctly display data from the ECI-100 compatible engines. The MFD's MFD's Identify Engines feature is only applicable to engines which have been interfaced to the system via an ECI-100 Engine Gateway. For all other engines systems, proper instancing must be adhered to as indicated above.
Note: Raymarine MFDs and instruments simply repeat data received from compatible NMEA 2000 devices which have been interfaced to the backbone. Raymarine MFDs and instruments do not support calibration and alignment of third party NMEA 2000 sensors. As such, calibration and/or alignment of interfaced NMEA 2000 sensors must be performed per the third party sensor manufacturer's instructions. Such third party sensor calibration and/or alignment may require interfacing a PC or third party manufacturer's display to the SeaTalkng backbone.
RAYFAQ#
When operating with the latest software updates, the Axiom MFDs and a/c/e/eS/gS-Series MFDs are NMEA 2000 certified products. These products are compatible with engines systems (via an engine gateway), and some NMEA 2000 sensors (ex. fuel flow sensors). Raymarine does not maintain lists of NMEA 2000 engine makes/models and engine gateways, as this information is continuously changing and outside of the control of Raymarine. As such, it is recommended that one contact the engine manufacturer with the engine information (model, serial number, etc.) to determine whether the engine(s) features NMEA 2000 support or whether an engine gateway is available. When interfacing Raymarine equipment to a NMEA 2000 engine(s), the Raymarine equipment must not be interfaced directly to the engine manufacturer’s network backbone. Instead, the engine manufacturer's network backbone must be interfaced to a NMEA 2000 gateway (ex. Raymarine ECI-100 Engine Gateway, Volvo engine gateway, Yamaha engine gateway, Maretron J2K100, SmartCraft to NMEA 2000 Gateway, Fox Marine MEFI-1/2/3/4, Yacht Devices YDEG-04 (Volvo Penta, BRP Rotax and J1939 engines), Yacht Devices YDES-04 (engines with a J1708 serial interface), etc.). Third party analog engine to NMEA 2000 gateways (ex.
Actisense EMU-1, Noland RS11, etc.) are also available within the marine electronics industry to support the needs of those having older engines. The primary function of a NMEA 2000 engine gateway is control the flow of data between the engine system CAN backbone and the SeaTalkng/NMEA 2000 backbone used by the marine electronics. The second function of a NMEA 2000 engine gateway is to isolate the power on the engine system backbackbone from power on the marine electronics SeaTalkng/NMEA 2000 backbone. Raymarine’s ECI-100 presently supports integration with select Volvo, Yamaha, Yanmar, Honda, and Caterpillar marine engines.
To interface the engine(s), a powered and properly terminated SeaTalkng backbone must be installed onboard having SeaTalkng T-Pieces (SeaTalkng 5-way connectors may be substituted where NMEA 2000 devices are closely located) for each NMEA 2000 device (i.e. engines, sensors, data master MFD, etc.) which will be interfaced as a spur to the SeaTalkng Network backbone. A simple backbone may be constructed from the following components:
- A06064 SeaTalkng 5-Way Connector
- A06031 SeaTalkng Termination Plugs x 2
- A06049 SeaTalkng Power Cable
- a pair of SeaTalkng Spur Cables of appropriate length to interface the MFD and NMEA 2000 engine gateway to the SeaTalkng 5-Way Connector. An A06082 DeviceNet (F) to SeaTalkng (M) Adapter may be mated to a SeaTalkng Spur Cable to permit it to be mated the DeviceNet(M) socket of an Axiom/Axiom Pro/Axiom XL MFD.
As SeaTalkng/NMEA 2000 spurs are limited to 5m maximum length, should the cable routing distance between the MFD and NMEA 2000 engine system's backbone exceed 10m, then the 5-Way Connector listed above may be replaced with A06028 SeaTalkng T-Pieces which have been joined to one another using appropriate lengths of SeaTalkng Backbone Cable.More information concerning SeaTalkng/NMEA 2000 networking may be found here. Should the vessel not have an engine system backbone installed onboard, then it is recommended that the engine system manufacturer be contacted regarding the engine system manufacturer's components required to construct a backbone for the engine system.
The Data Master MFD will be interfaced to one of the spur sockets within the SeaTalkng backbone using an appropriate length of SeaTalkng Spur Cable ((400mm (A06038), 1m (A06039), 3m (A06040), 5m (A06041)). The chosen NMEA 2000 engine gateway(s) will also be interfaced to one onf the spur sockets within the SeaTalkng backbone. Raymarine offers SeaTalkng to DeviceNet Male (A06046) and SeaTalkng to DeviceNet Female adapter cables (A06045) as well as Stripped End Spur cables (A06044) to support interfacing third party NMEA 2000 devices as spurs to the SeaTalkng network backbone. Finally, the NMEA 2000 engine gateway(s) will be interfaced to the engine system per the NMEA 2000 engine gateway manufacturer's instructions.
The following engine data items are be supported when interfaced to a NMEA 2000 device supplying the corresponding data.
Battery 1/2 Amps/Temp/Voltage/% Charge
Engine 1/2/3/4/5:
- RPM
- Coolant Temp & Pressure
- Oil Temp & Pressure
- Transmission Oil Temp & Pressure
- Transmisson Gear
- Boost Pressure
- Fuel Pressure
- Fuel Flow Rate
- Fuel Flow Instantaneous
- Fuel Flow Average
- Engine Hours
- Engine Trim
- Alternator
- Engine Load
Fuel:
- Fuel Tank Levels 1/2/3/4/5
- Total Fuel Volume (Remaining)
- Fuel Flow Total
- Economy
- Est. Fuel Remaining
- Distance to Empty
- Time to Empty
- Fuel Used Trip
- Fuel Used (Season)
Tanks:
- Fresh Water %
- Grey Water %
- Black Water %
- Live Well
Note: When interfaced a third party engine gateway(s), it will be necessary to ensure that the vessel's engine(s) have been assigned a NMEA 2000 Device Instance Number(s) which is consistent with the NMEA 2000 convention of instancing when one or multiple engines, tanks, etc. have been installed onboard the vessel. Please click here to view a FAQ providing additional information on this subject. Failure of the engine system to comply with the instancing convention specified within the referenced FAQ will either prohibit data from all or some of the vessel's engines from being displayed by the MFD.
Should a compatible engine(s) be interfaced to the Raymarine system via a Raymarine ECI-100 Engine Gateway, then the MFD's Identify Engines feature must be used following installation to permit the MFDs to correctly display data from the ECI-100 compatible engines. The MFD's MFD's Identify Engines feature is only applicable to engines which have been interfaced to the system via an ECI-100 Engine Gateway. For all other engines systems, proper instancing must be adhered to as indicated above.
Note: Raymarine MFDs and instruments simply repeat data received from compatible NMEA 2000 devices which have been interfaced to the backbone. Raymarine MFDs and instruments do not support calibration and alignment of third party NMEA 2000 sensors. As such, calibration and/or alignment of interfaced NMEA 2000 sensors must be performed per the third party sensor manufacturer's instructions. Such third party sensor calibration and/or alignment may require interfacing a PC or third party manufacturer's display to the SeaTalkng backbone.
RAYFAQ#