> 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/product-tutorial-videos/k-tc-and-k-cal/k-tc-tutorial-videos/how-to-interface-k-tc-to-k-cal-and-export-dbc.md).

# How to Interface K Tc to K Cal and export DBC

{% embed url="<https://youtu.be/e1Bhp0UyAkc>" %}

The K-TC modules belong to the Influx K-series instrumentation range for CAN applications. The stackable K-TC is ideal for applications that require a large number of thermocouples, such as vehicle durability and winter and summer testing.&#x20;

The K-TC module's CAN Bus settings, calibration, and sampling rates are all easily configurable and stored in the K-TC module even when not powered. The K-TC modules can function as standalone temperature loggers with inbuilt Micro SDHC storage, and the data will be logged with a real timestamp using the internal RTC.&#x20;

The input calibration and set-up of the K-TC module are easily configurable via Influx K-Cal software, a freely distributable Windows pc application.


---

# 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/product-tutorial-videos/k-tc-and-k-cal/k-tc-tutorial-videos/how-to-interface-k-tc-to-k-cal-and-export-dbc.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.