Configuring ERM Efuel Dome Sensor on Navixy
This document introduces the ERM eFuel DOME sensor, a device engineered for advanced and non-invasive fuel level monitoring across a wide range of vehicles. This innovative sensor provides real-time data analysis, automatic calibration, and intelligent alerts for theft and refueling events. A key technical advantage is its wireless, autonomous, and plug-in design, eliminating the requirement for fuel tank drilling, thereby preserving the vehicle's warranty and structural integrity.
Leveraging the principles of hydrostatics to accurately determine fuel volume based on liquid height, the eFuel DOME sensor offers a distinct advantage over conventional fuel sensing technologies. Once installed externally beneath the fuel tank, it seamlessly transmits data to compatible Starlink devices.
Specifically designed for integration with the Navixy platform via Starlink devices, this solution provides users with comprehensive vehicle insights, extending beyond location tracking to include critical sensor data such as fuel level, height, voltage, pressure, and signal strength.
The subsequent sections of this guide detail the configuration process for the eFuel DOME sensor, model version 1, within the Navixy platform.
Steps Prior to Platform Visualization
Before proceeding with the Navixy platform configuration, it is essential to verify the physical connection between the eFuel DOME sensor and the HUB (antenna) using the BLE_FuelHub_Monitor configurator tool, this tool is provided from ERM tech support. Successful communication is indicated by a solid green LED on the HUB. Please note that newly delivered sensors from the factory may require initial activation by briefly passing a magnet over them. Once activated, the sensors will establish full communication with the antenna.
To achieve the best sensor performance on the platform, it is necessary to properly configure the following parameters:
Centimeters Liquid Pressure
Low Fuel Level Alert #1
Low Fuel Level Alert #2
Refuel Event Minimal Difference
Fuel Theft Event Minimal Value
Ignition ON/OFF report time
Fuel tank height
Once the sensor is activated and data is successfully displayed within the "Get Diagnostic" tab of the BLE_FuelHub_Monitor tool, proceed to fill the vehicle's fuel tank to its full, desired capacity. The corresponding liquid height, measured by the sensor, will be displayed under the "Fuel Total Centimeters" parameter. This "Fuel Total Centimeters" value is critical as it serves as the 100% reference point for the system's percentage-based fuel level calculations. Therefore, this exact value must be entered into the "Fuel Tank Height Centimeters" field within the BLE Monitor tool sensor settings.
With successful sensor activation and data verification via the configurator tool, we can now proceed to map these sensors within the Navixy platform.
Device activation on Navixy
Device activation on Navixy requires the Serial Number located on the device's information label. This serial number, which will range from 4 to 8 digits depending on the specific device model, must be entered as the Device ID during the activation process in Navixy.
Mapping the eFuel sensor on Bluetooth sensor widget.
Once the device is activated and reporting on the platform, go to Device and Settings tab, select the device and go to the Bluetooth sensors widget.
In this tab, you will need to enter the device's number followed by the sensor's MAC address. This combined information is crucial for the system to correctly decode and interpret the incoming data packages from the eFuel DOME sensor. Ensure accurate entry of both the number and the MAC address to establish proper data processing. Furthermore, it's important to note that the Bluetooth sensor widget within the platform has the capability to handle data from up to four individual eFuel Dome sensors simultaneously.
Creating measurement sensors on Sensor and Buttons widget.
To visualize the data parameters transmitted by the eFuel Dome sensor, a measurement sensor must be created. During this mapping process, it is important to associate each parameter with the corresponding input number. For instance, if the first eFuel DOME sensor is identified with index 1, then all data values you wish to retrieve from this specific sensor (such as fuel level, height, voltage, etc.) must be configured to utilize input 1. This indexing ensures the platform correctly interprets and displays the data originating from the intended sensor.
The parameters that can be obtained from the sensor are as follows:
Ble_lls_level_n (Reported fuel value)
Ble_lls_height_n
Ble_lls_level_raw_n (Original fuel value)
Ble_lls_pressure_n
Ble_signal_strength_n (RSSI)
Ble_battery_voltage_n
It is important to note that the lls_level and lls_height parameters are inherently included within the data package transmitted by the device at the regular reporting interval. Conversely, other parameters such as voltage and pressure will be obtained with less frequency or specifically requested via the sensor's status command. This deliberate approach optimizes battery life, as transmitting a greater number of parameters more frequently would lead to a faster decrease of the sensor's voltage. Therefore, to ensure longevity and focus on the most critical information for continuous monitoring, parameters beyond the essential real-time fuel level are accessed less frequently.
Events and sub-events from the e-fuel sensor have been integrated following the structure 45_XX, where XX is the sub-event number shown below:
155 Fuel theft incident
156 Tank filling
157 Hub device awakened (after being connected)
158 Sensor connected to the Hub
159 Sensor disconnected from the Hub
160 Sensor missing
161 Fuel alert level #1
162 Fuel alert level #2
163 Incident report (filling/theft)
Go to Set rules on Alert tab and look for the Starlink device. Once the starlink device is selected, choose the State field value alert type, add a name for the alert.
So on, select the sub_event_code and put the expected value with the sub event of the alert it is required. For instance, if it requires the Efuel theft incident, then the expected sub_event code would be 45_155 as shown below.
Proceed to finish the alert configuration in Notifications and Schedule.
With the sensor successfully configured and its parameters mapped within the Navixy platform, the fuel level monitoring process is now complete and ready for real-time observation and analysis through your Navixy interface.
Final Thoughts
In conclusion, the ERM eFuel DOME sensor, with its advanced, non-invasive hydrostatic technology and wireless design, offers a significant advantage for accurate and reliable fuel level monitoring across diverse vehicle fleets. Its seamless integration with the Navixy platform via compatible Starlink devices provides a comprehensive solution, delivering not only precise fuel level data but also additional valuable parameters. The ability to map sensor parameters within Navixy and configure alerts empowers users with real-time insights for optimized fuel management, theft prevention, and enhanced operational efficiency. This integration provides a powerful and user-friendly tool for effectively monitoring and managing fuel consumption within any connected fleet.