> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/qna/using-navixy/how-to-copy-calibration-table-across-multiple-devices.md).
# How to copy calibration table across multiple devices
## **Question**
How to copy the calibration table across multiple devices?
## **Answer**
Although there is no dedicated feature for copying calibration tables yet, there are a couple of ways to do this using similar sensor functionality.
1. The Copy sensor settings button.
In the settings block, you can find the ‘Sensors and Buttons’ section, which can be used to copy (clone) a list of sensors from one device to a list of similar device models.
Here is the button itself:
If you click this button, you will see a list of compatible trackers for cloning all the sensors from the currently selected device to all the devices you check in the pop-up list:
If you select devices and click ‘Apply’, all sensor settings on the target devices will be overwritten. Please be careful not to overwrite the sensor settings of devices that have already been configured.
This is useful when you set up a new fleet, as you can configure a tracker once and clone all its sensor settings to other devices of the same model.
The downside of this approach is that all target device sensor settings will be overwritten with the source tracker sensor settings that you copy.
2. Calibration table import.
This function may suit your needs if you only need to import the calibration table for multiple devices. This approach is very useful if you have a large number of lines (records) in the calibration table.
To import the table, you first need to either extract an existing calibration table from the source device or create the table from scratch.
There is a template for such import right inside the calibration table import window:
{% columns %}
{% column width="66.66666666666666%" %}
{% endcolumn %}
{% column width="33.33333333333334%" %}
{% endcolumn %}
{% endcolumns %}
The template demonstrates the CSV file structure needed for the calibration table to be imported.
A CSV file is just a text file. Create a text file and fill it in according to your needs:
10;30\
13;35\
15.7; 43\
20.1; 47.7
Save the file as a CSV file. The extension should be .csv.
Import this file from your desktop:
Press ‘Save’.
3. If you need to automate the entire process, you can create an API script to update the calibration table settings via the API:
Here is the link to the API call that should be used in this case: [Link](/docs/navixy-api/user-api/backend-api/resources/tracking/tracker/sensor/calibration_data.md#update).
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://navixy.com/docs/qna/using-navixy/how-to-copy-calibration-table-across-multiple-devices.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.
