> 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/vehicle-telematics-technology/fuel-management/fuel-control-in-navixy/analyzing-fuel-data/fuel-related-widgets.md).

# Fuel related widgets

Device info panel widgets in Navixy display CAN/OBD2 fuel data including consumption rates, tank levels, and engine fault codes.

To access the device control panel, simply press the "info" button or double-click on the desired device in the Object list. The control panel, prominently displayed in the central area, provides comprehensive information about the selected object, such as its current status, location, and telemetry data. Furthermore, it offers a variety of tools for effective operational management.

The widget list offers easy customization options. To personalize all widgets, there are three buttons at your disposal.

By clicking on "show all," you can expand all widgets and access the information within them. Conversely, clicking on "hide all" collapses the widgets for a more compact view.

Additionally, the "change the order" feature allows you to rearrange the widgets. Simply select a widget and drag it to a more convenient position in the list.

Lastly, the "gear" button opens a list of available widgets. You can deselect unnecessary widgets by unchecking the corresponding boxes.

![Device info and widgets](https://3650643549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIgDb43gtyXcm1Av4h1np%2Fuploads%2Fgit-blob-33889b2191a908e246063eefe9f431f5e1870d09%2Fgeneral_view_600-1.png?alt=media)

If the device is connected to the CAN bus or OBD2 connector, the widget will display all available information from the vehicle. Fuel level and consumption, engine speed, coolant temperature, malfunction lamp (MIL), error codes (DTC), engine load, axle load, etc. To display the sensors, they [must be added](/docs/user/guide/devices-and-settings.md) to in the device settings menu.

![OBDII and CAN information](https://3650643549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIgDb43gtyXcm1Av4h1np%2Fuploads%2Fgit-blob-a7f9f00d164d16383ff1fb8ea07ce0a14d4a350c%2Fobdwidgeten.png?alt=media)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://navixy.com/docs/expert-center/vehicle-telematics-technology/fuel-management/fuel-control-in-navixy/analyzing-fuel-data/fuel-related-widgets.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.