> 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/expert-center/faq-and-troubleshooting/sensors/manage-sensors.md). # Manage Sensors First of all, be advised that there is no possibility to affect the sensor from the Navixy platform. The sensor just sends data to the GPS device, then this data is just parsed on the server. Also if you have done the following recommendations, and the issue has not been resolved, contact our support team. Navixy is doing its best to make the platform more comfortable for you. ## No data from the sensor If there is no data received from the sensor on the platform, follow next steps. 1. First of all, make sure that sensor has enough power supply and works correctly 2. Sensor is connected to the device according to the user manuals 3. Sensor is added and [configured](/docs/user/guide/devices-and-settings.md) in the device settings section on the platform 4. Check that data is parsed and shown in the [air console](/docs/admin/devices/air-console.md), if there is no data from the device in the gprs-terminal, it means that currently device is not sending any data 5. Input number in the device settings and the device's input number, which is used for this sensor, should be same ## No data from the OBDII/CAN interface This section is for the cases when your device uses OBDII/CAN interface for the vehicle data transmitting 1. Check that device supports OBDII/CAN data transmitting and your vehicle model is supported too. You can get this information from the manufacturer support team. 2. OBDII/CAN sensors should be added in the device settings section on the platform 3. OBDII/CAN data transmitting should be enabled in the device settings. You can check it in the device configurator ## Incorrect units of measure This section is for the cases, when the real units of measure and the units received from the sensor data are different 1. Make sure that sensor is configured correctly and [calibration table is filled](/docs/user/guide/devices-and-settings/vehicle-sensors/measurement-sensors.md) (if needed) 2. Follow through the all recommendations from the user manuals. Be advised that some cases require using dividers. ![Sensors management](/files/Yp0vAAhI9y0BJljkLX02) ## Discrepancies between the real values and sensor values This sections is for the cases, when the values received from the sensor does not match to the real values. Be informed that when fuel tank is inclined, fuel sensor might send incorrect values ![](/files/wzL2vNMJJj9cEmMmkuOS) 1. Check that data is parsed and shown in the [air console](/docs/admin/devices/air-console.md), if there is no data from the device in the gprs-terminal, it means that currently device is not sending any data 2. [Calibration table](/docs/user/guide/devices-and-settings/vehicle-sensors/measurement-sensors.md) should be filled correctly according to the sensor user manual (if needed), also "drains" detection parameters should be specified correctly ![](/files/KeIJjHAQFqmklUhThGiJ) ![](/files/wHsxh2mda9ZZT6J5qv32) ## There is no sensor in sensor list for your device If the data that was received from the sensor appears in [Air Console](/docs/admin/devices/air-console.md), but the appropriate sensor itself isn't available for selection in the sensor list, contact our support team. ![There is no sensor in sensor list for your device](/files/5pn7hc7t4i3EJ4QDjDBl) ## Add a fuel sensor To add a fuel sensor, first make sure it is properly connected and GPS device itself is online. In the Navixy platform, go to the **Devices and settings** module and pick a GPS device that you want to add the fuel sensor to. Select **Sensors and buttons** block, click the plus button, and pick **Measurement sensor**: ![Add a fuel sensor](/files/JdaXYIa7BG5uyO0lGSt9) A window will pop up where you will be able to set all required parameters. Pick the input to which your fuel sensor is connected: **Sensor type** should be set to **Fuel**. Don't forget to specify units. ![Add a fuel sensor](/files/6awc7mPNWQGLhX9MRb4I) ## Calibrate a fuel sensor Different GPS devices process and report fuel sensor data in different ways. For example, CAN sensors typically require a simpler calibration. If GPS device reports in percentages and you need to see the amount of fuel in liters, record the fuel volume at 0 and 100 percent and enter those values into the table. The rest of calculation will be done automatically. ![Calibrate a fuel sensor](/files/WFAhjan4CXpVY7mAfc6y) Other sensors might return voltage instead of percents or direct volume. In such cases, more detailed calibration is required. To fill out a calibration table, you will need to measure sensor's values at different fuel levels in the tank and then input results into the table. In case some unrelevant values may be received by the sensor, you're able to set Ignore values parameter to get them filtered. ![Calibrate a fuel sensor](/files/4nGWYTm4mCzvRJpcQK6z) --- # 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/expert-center/faq-and-troubleshooting/sensors/manage-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.