> 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/k-series-product-manual/k-series-product-manual/k-tc-logger-manual/connecting-and-powering-the-k-tcxx/enable-the-aux-power-setting-within-the-logger-configuration.md).
# Enable the AUX Power setting within the Logger Configuration
If you power it from the Logger, the Logger will need to be powered from the vehicle or an external power source
(NOT just via USB) and you will need to make sure the AUX power feature in the configuration is set to on. To do this, follow the Steps Below:
Right-click on the Project that you want to configure and select ‘Properties’; if you need to create a configuration, this is detailed in the ‘Loading the K-TCxx configuration into DiaLog’ section document.
Once the Edit Configuration window is displayed, click on the ‘Settings’ Tab and put a Checkmark in Aux Power On.
Click OK to set the Aux Power on Setting in the Configuration…
Send the configuration to the Logger by right-clicking on the project and choosing “Send Configuration to the Logger.”
If you have the CAN bus that the K-TCxx is connected to set to the right speed within your Project, you will see the Status Light on Solid Orange, and the CAN Light on Solid Green; if it is flashing green, the CAN bus is misconfigured, check the speed and termination.
---
# 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/k-series-product-manual/k-series-product-manual/k-tc-logger-manual/connecting-and-powering-the-k-tcxx/enable-the-aux-power-setting-within-the-logger-configuration.md?ask=&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.