+- Raymarine forum (http://forum.raymarine.com)
+-- Forum: Raymarine Forums (/forumdisplay.php?fid=1)
+--- Forum: Multifunction Displays (/forumdisplay.php?fid=120)
+--- Thread: Fuel tank level data is not being populated within an a/c/e/eS/gS-Series MFD (/showthread.php?tid=2543)
Fuel tank level data is not being populated within an a/c/e/eS/gS-Series MFD - Chuck - Raymarine - Moderator - 02-17-17 02:22 PM
Within a MFD, fluid levels (fuel, fresh water, black water, etc.) will only be reported for tanks which have been fitted with a NMEA 2000 fluid level sensor. NMEA 2000 fluid level senders transmit fuel level within NMEA 2000 PGN 127505. The first action of such troubleshooting would be to interface a NMEA 2000 analyzer (ex. Actisense NGT-1, etc.) to the system's powered and properly terminated SeaTalkng / NMEA 2000 backbone to verify that these PGNs are present on the backbone. Fluid levels are exclusively expressed as a percentage of full by Raymarine MFDs. Each NMEA 2000 fluid level sensor will need to be programmed with an Instance Number and Fluid Type per procedures and/or programming equipment / software specified by the NMEA 2000 Tank Level Sensor's manufacturer. Raymarine products follow the NMEA 2000 convention that should a single instance of a device (ex. fluid level sensor, fuel rate sensor, engine, etc.) be present within a system, that its instance number will be 0. For items such as engines, fuel tanks, water tanks, where more than one such device may be installed, Raymarine's MFDs follow the NMEA 2000 convention that instance 0 will be assigned to the device within the same set of devices (ex. engines, fuel tanks, water tanks, etc.) which has been installed farthest to port onboard vessel. Device instance numbers would then increment with each additional device of the same type when progressing from port to starboard. As such, should a vessel feature three engines, the port engine would need to be assigned instance 0, the center engine would need to be assigned instance 1, and the starboard engine would need to be assigned instance 2. One of the features engines interfaced via an ECI-100, is that a/c/e/eS/gS-Series MFDs and Axiom / Axiom Pro MFDs would then support engine identification to address engines having instance numbers deviating from this convention. In the absence of an ECI-100, it would be necessary to re-assign instance numbers of the engines according to procedures provided by the engine manufacturer. This applies only to engines.
Example: Should a vessel feature three fuel tanks and a fresh water tank, then
- the Fluid Type configuration setting for all three fuel tank fluid level sensors would need to be configured to "Fuel", and
- the Fluid Type configuration setting for the fresh water tank fuel level sensor would need be configured to "Fresh Water", and
- the fresh water tank fluid levels sensor would need to be assigned instance 0, and
- the port fuel tank fluid level sensor would need to be assigned instance 0, the center engine would need to be assigned instance 1, and the starboard engine would need to be assigned instance 2.
Please see the attached PDF file providing additional information on this subject.
Should a vessel not be fitted with NMEA 2000 fluid level sensors, then the MFDs would be unable to report tank fluid levels for individual tanks. However, should the vessel be fitted with a NMEA 2000 fuel flow sensor(s) or a NMEA 2000 engine gateway(s) reporting fuel flow rate, then the Fuel Manager feature of the a/c/e/eS/gS-Series MFDs would then be able to populate the Est. Fuel Remaining data item, which is indicative of the estimated total fuel fuel remaining within the vessel's tanks. The Total Fuel Capacity as well as full and partial fuel fill data is configured within the MFD's Fuel Manager (HOME->SET-UP->FUEL MANAGER) feature.
RAYFAQ#