> For the complete documentation index, see [llms.txt](https://docs.influxtechnology.com/support_guides/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.influxtechnology.com/support_guides/dialog-user-guide/dialog-software-manual/getting-started/software-introduction/navigation-bar/advanced-configuration-menu.md).

# Advanced Configuration Menu

<figure><img src="https://3979528544-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFiflr3JdTVky5EaTMlxu%2Fuploads%2FqlVISIICemj424HNHTIy%2Fimage.png?alt=media&amp;token=f151f5c3-f550-4f54-b360-3729bae6ce53" alt=""><figcaption></figcaption></figure>

* **New/Edit Triggers**— allows Triggers to be added to a configuration to enable the Logger to react to events.
* **New/Edit Output Signal**— allows Messages to be created to output to Control Units, Instrumentation, Displays or other tools.
* **New/Edit Conversion Table**— allows look-up tables to calibrate non-linear sensors to show true input values.
* **Message Constructor**—  allows users to transmit periodic/triggered CAN messages from the logger.
* **Configuration Report**— allows a user to generate a report that details some or all of the following information: Vehicle Information, Triggers, Bus and Protocol Information, PIDs, Diagnostic Addresses, CCP Addresses, Event Lists, CAN Signals, Instrumentation Channels and Digital Channels.


---

# 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://docs.influxtechnology.com/support_guides/dialog-user-guide/dialog-software-manual/getting-started/software-introduction/navigation-bar/advanced-configuration-menu.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.
