> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/user/guide/devices-and-settings/vehicle-sensors/measurement-sensors.md). # Measurement sensors Measurement sensors turn a device's continuous inputs into meaningful values, such as fuel level, temperature, RPM, or voltage, with units and a calibration table that maps raw sensor readings (the unprocessed electrical signal the device sends) to real-world quantities. ## Availability Available when the device model has inputs. ## Adding a measurement sensor To add a measurement sensor, click ![Measurement sensor](https://www.navixy.com/wp-content/uploads/2021/10/add.png) and select **Measurement sensor** in the pop-up menu. Configure the required sensor parameters: * **Label**: Enter the sensor label as it appears in Navixy. It can be any name of your choice. * **Parameter**: Choose the input to which the sensor is connected (number and types of inputs available are determined by device model). * **Sensor type**: Choose the sensor type. * **Units**: Choose the measurement units. You can select available units from the drop-down list or specify custom ones. * **Additional parameters**: Only appear when the specific type of sensor is chosen. For example, for a fuel sensor, you can adjust the accuracy and threshold parameters for use in drain detection. ![](/files/jwGSYkRQasCLByt2qwY0) ## Adding calibration data After all parameters are set, you must enter the calibration data. Learn more about this process in the [Sensors setup and configuration guide](/docs/expert-center/vehicle-telematics-technology/fuel-management/fuel-control-in-navixy/sensors-setup-and-configuration.md). 1. First, create a corresponding list of raw values of the measuring sensor (e.g., volts) and the actual value that the sensor is measuring (e.g., liters). 2. Click ![Measurement sensor](https://www.navixy.com/wp-content/uploads/2021/10/add.png) to add rows to the table. 3. In the created line, fill in the **Sensor value** field with the obtained value and the **Quantity** field with the corresponding measured quantity. 4. Click ![Measurement sensor](https://www.navixy.com/wp-content/uploads/2021/10/del.png) to delete a row. ![](/files/IkQvBHOpzt0oKPHqomwC) 5. Click ![Measurement sensor](https://www.navixy.com/wp-content/uploads/2021/10/upload.png) to upload the calibration table file. ![](/files/H9cy3mF9JkD0MiX0RrPU) Click **Advanced settings** ![Measurement sensor](https://www.navixy.com/wp-content/uploads/2021/10/advanced_settings.png) to access additional settings, such as **Ignore values** and **Multiplier**. * **Ignore values:** Allows you to adjust a "valid" range of raw measurement values (the unprocessed signal from the device). Any values above and below the range are omitted. For example, this can be used for skipping the fuel sensor's zero values when the ignition is off. * **Multiplier:** Used to correct raw data values from the sensor by multiplying them by a fixed number (for example, 0.1 to scale millivolt readings down to volts). ### **Filtering order** Keep in mind that the **Less than** and **More than** restrictions are applied before the **Multiplier.** Navixy processes each incoming sensor value in this fixed order: 1. Ignore values (**Less than** and **More than**) 2. **Multiplier** 3. **Calibration table** For example, the incoming raw value from the device is 1000, the ignore-values boundaries are 100 (minimum) and 3000 (maximum), and the multiplier is 0.2. In this case, the value passes the min/max check, is multiplied by 0.2 and becomes 200. The calibration table then takes 200 as the source value and converts it into the final quantity shown in the platform. If an incoming value exceeds 3000, it is discarded at the boundary step and no multiplication or calibration applies. The numbers here are given as a sample. You may have other settings, but the principle remains. ### **Graph** As you enter data into the table, the graph is plotted. ![](/files/nHaOuYf9wXTxG32Ct9qS) To confirm your changes, click **Save**. ### **Raw sensor data storage** By default, raw sensor data is stored on the Navixy platform. This allows users to recalibrate the represented sensor data of the past device sensor history. Whenever the multiplier, maximum ("less than"), minimum ("more than"), or calibration table data are changed, the platform recalculates the history and represents the data according to the new settings. The advantage of this approach is that the user can always recalibrate the table, change the sensor settings, and build a report based on the recalculated data "on the fly". ![](/files/6GZaNfxdPJX2VgKWJfFS) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://navixy.com/docs/user/guide/devices-and-settings/vehicle-sensors/measurement-sensors.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.