> 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/appendix-1/protocol-priorities.md).

# Protocol Priorities

This section details the working priorities within a Configuration Structure regarding CCP and Diagnostic protocols. If either of these protocols is present in the structure by itself, there are no priorities. However, if both protocols are present, then in a single configuration, the priority needs to be considered by users.

In both CCP and Diagnostic protocols running, the CCP protocol has the priority, as shown below:

* When the logger is powered up, it will first attempt to communicate via CCP to establish the connection.
* Once the CCP/XCP connection has been established, the module will communicate via the Diagnostic protocol.
* If no CCP connection can be established, the logger will not communicate via the Diagnostic protocol.

This means that the CCP module is the master and has priority. Therefore, users must establish this connection if a structure is configured with a CCP protocol.

This priority is established to stop any unwanted waking of modules by Diagnostic polling. Diagnostic polling will be possible only when the vehicle is awake, allowing CCP/XCP communication.


---

# 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/appendix-1/protocol-priorities.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.