> 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-box-product-manual/connecting-and-powering-the-k-box.md).
# Connecting and powering the K-Box
The K-Box is powered via the CAN and power connectors. It has been designed with CiA® 102 pinout for the CAN bus and power to connect the device as easily as possible.
Most commonly, it will be powered from a Rebel Logger using the Multi-Connect Cable, but you can also power it via pin 9 (4.5 to 36V) and pin-5 PowerGND of the nine-pin Sub-D connectors. If connected via the Multi-connect cable, the CAN 1 (MS) bus is also connected, allowing the logger to record the data transmitted from the K-Box.
#### a) Setup for interfacing ReXgen Device with K-Box
{% hint style="info" %}
#### Notes:
* When using a ReXgen Air device with K-Box device, be sure to get in touch with the technical support team at Influx.
{% endhint %}
#### b) Setup for interfacing Rebel Device with K-Box.
{% hint style="danger" %}
Warning:
* Several K-Boxes can be daisy chained via the additional DB9 Connector; however, they must have power supplied separately via power breakout in the Cable, not via the Logger. It can also be used to connect other devices, such as the Rebel Dash.
{% endhint %}
The pinout of the required Cable between the two K-Boxes is as follows:
---
# 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-box-product-manual/connecting-and-powering-the-k-box.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.
