> For the complete documentation index, see [llms.txt](https://docs.efento.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.efento.io/nb-iot-loggers/configuration/sensor-specific-settings/low-high-temperature-pt-probes.md).

# Low / high temperature - PT probes

Efento low- and high-temperature loggers are designed for measuring temperatures outside the standard range, from **-200°C to 600°C**. The supported measurement range depends on the external RTD probe connected to the logger.

The main difference between low- and high-temperature probes is the cable insulation material, which determines the temperature range in which the probe can be safely used.

Efento low- and high-temperature loggers supplied with Efento RTD probes are pre-calibrated and do not require initial calibration.

The parameters described below allow you to configure RTD probes connected to the Efento logger. Correct configuration of the sensor type, characteristic curve, excitation current, and optional stabilization delay is required to ensure accurate temperature measurements.

## **Configurable parameters**

| Parameter              | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | Configuration Options                                              |
| ---------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------ |
| **PT Sensor Type**     | Specifies the RTD sensor variant connected to the device.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | PT10, PT50, PT100, PT200, PT500, PT1000                            |
| **Curve Type**         | Defines the mathematical equation describing the relationship between resistance (R) and temperature (T). The curve depends on the manufacturing standard and material purity of the platinum sensing element.                                                                                                                                                                                                                                                                                                                                        | European standard, American, Japanese, ITS-90                      |
| **Excitation Current** | <p>Sets the measurement current supplied to the RTD sensor. For <strong>PT1000 probes</strong>, the recommended excitation current depends on the wiring method:<br>• <strong>2-wire and 4-wire probes:</strong> 100 µA<br>• <strong>3-wire probes:</strong> 50 µA<br><em>(Note: For PT100 probes, a higher current such as 500 µA or 1 mA is typically recommended).</em><br><em>After adjusting the excitation current, verify readings in the Efento app. If a measurement error occurs, decrease the current by one step and test again.</em></p> | 5 µA, 10 µA, 25 µA, 50 µA, 100 µA, 250 µA, 500 µA, 1 mA            |
| **Extra Delay**        | Adds a settling delay (in 100 µs steps) between powering the connected probe and taking the measurement. This compensates for additional line capacitance introduced by long extension leads or shielded probe cables.                                                                                                                                                                                                                                                                                                                                | <p>0 to 255 (0 to 25,500 µs)<br><em>Default: 0 (no delay)</em></p> |

## **Configuration using the Efento mobile application**

All parameters described above can be configured using the Efento mobile application in the **Nearby Devices** section.

Connect to the logger, tap the gear icon, open **Channel settings**, and select **Settings** for the required channel.


---

# 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.efento.io/nb-iot-loggers/configuration/sensor-specific-settings/low-high-temperature-pt-probes.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.
