> For the complete documentation index, see [llms.txt](https://docs.didge.io/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.didge.io/home/foodcore-sensors/admin/calibration/target-calibration.md).

# Target Calibration

#### Overview

This documentation outlines the process for conducting a calibration on temperature sensors within the MFC wireless monitoring system. Calibration ensures that sensor readings are accurate and aligned with verified master units. This is critical to maintaining reliable environmental monitoring in controlled storage environments.

***

#### Prerequisites

Before initiating the calibration process:

* **Master Unit**: Must have a pre-calibrated and verified accurate temperature sensor.
* **Send Rate Configuration**: Both the master and target units must be configured to transmit data at 1-minute intervals.
  * This must be verified by confirming 1-minute spaced data records from both units.

***

#### Key Terms

* **Master Device**: A pre-calibrated unit that serves as the reference.
* **Target Device**: The unit being calibrated.
* **Tolerance**: The acceptable variance (e.g., ± 1°C) between master and target readings.
* **Success Threshold**: Number of consecutive in-range readings required to pass (typically 5).

***

#### Calibration Procedure

1. **Initiate Calibration**:
   * Select the target sensor within the system dashboard.
   * Click on the "Calibrate" button to open the calibration module.
2. **Assign Master Device**:
   * Scan the QR code of the master device or manually select from available devices.
   * The selected master will be used for comparison.
3. **Configure Parameters**:
   * **Tolerance**: Choose from preset values (±0.1, ±0.2, ±0.5, ±1, ±2 °C) depending on accuracy requirements.
   * **Success Threshold**: Typically set to 5.
   * **Interval**: Set to 1 minute.
   * **Sensor Mode**: Select whether to calibrate:
     * Ambient only
     * Probe only
     * Both (requires more robust alignment)
4. **Start Calibration**:
   * Click "Start Calibration".
   * Data will begin recording every minute.
   * The system evaluates if target values fall within the defined tolerance range against the master.

<figure><img src="https://2675140142-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPnSdrHOYeIaTHbt8Z0Qc%2Fuploads%2Fx6bUVnnRMILEIpM9gXNQ%2FScreenshot%202025-04-19%20at%207.24.11%E2%80%AFpm.png?alt=media&amp;token=5608835b-5c43-48e4-add2-98f4337e39e0" alt=""><figcaption></figcaption></figure>

***

#### Environmental Considerations

* Ensure stable environmental conditions during calibration:
  * **Fridge or Freezer**: Recommended that doors remain closed.
  * **Room Temperature**: Both devices must be exposed to the same conditions.
* Avoid environmental disruptions (e.g., frequent door openings).

***

#### Calibration Outcomes

* **Pass**:
  * Five consecutive target readings fall within tolerance of the master.
  * Calibration report is automatically generated.
  * Sensor exits maintenance mode.
* **Fail**:
  * No valid reading set within 2 hours.
  * Event is closed by the system.
  * Recommended Action: **Replace sensor** (especially for digital probe sensors).

***

#### Post-Calibration

* A calibration report is logged and includes:
  * Master and Target device info
  * Time and result (PASS/FAIL)
  * Graph of data records and deviation
  * Calibration log with each interval's comparison and result
* Sensors exiting calibration return to operational status.

<figure><img src="https://2675140142-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPnSdrHOYeIaTHbt8Z0Qc%2Fuploads%2FQIJJNMie7hmx8S9Foxp5%2FScreenshot%202025-04-19%20at%207.41.22%E2%80%AFpm.png?alt=media&amp;token=1d1fcb71-1182-4181-bc25-f469283ca4d8" alt=""><figcaption></figcaption></figure>

<figure><img src="https://2675140142-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPnSdrHOYeIaTHbt8Z0Qc%2Fuploads%2FXYo4tXixDtMDakIIZU5R%2FScreenshot%202025-04-19%20at%207.41.00%E2%80%AFpm.png?alt=media&amp;token=26d3ea32-5103-499b-8c6b-97353b58ef27" alt=""><figcaption></figcaption></figure>

<figure><img src="https://2675140142-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPnSdrHOYeIaTHbt8Z0Qc%2Fuploads%2FSPQebxfTZgc9De2Ap277%2FScreenshot%202025-04-19%20at%207.41.14%E2%80%AFpm.png?alt=media&amp;token=cbbd9ba3-7390-40a6-927a-257c2e8cae7b" alt=""><figcaption></figcaption></figure>

***

#### Additional Notes

* This method is known as a reference or comparison calibration.
* Master and Target units must be placed in close proximity.
* Manual calibration methods (e.g., boiling or freezing point) are available as alternative options but should follow similar evaluation principles.

***

#### Corrective Action for Failures

* Replace sensors that do not meet calibration standards.
* Potential causes for failure: moisture damage, aging, or physical degradation of components.


---

# 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.didge.io/home/foodcore-sensors/admin/calibration/target-calibration.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.