> For the complete documentation index, see [llms.txt](https://www.opal-rt.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.opal-rt.com/docs/rt-lab/configure-ios/communication-protocol-ios/pickering-driver.md).

# Pickering Driver

## Introduction to Pickering programmable resistor modules

The Pickering driver provides support for the most common features of **Pickering Programmable Resistor** and **Programmable Precision Resistor** modules. Its design follows a generic and extensible approach, with the objective of supporting a wide range of Pickering cards without requiring driver modification or recompilation.

A **Pickering Programmable Resistor Module** allows software‑controlled programming of a specific resistance value. During runtime, the simulation model directly drives the resistance setpoint, enabling automated and repeatable testing scenarios. These modules are commonly deployed as **PXI cards** inserted into a PXI chassis.

Pickering also offers **Programmable Precision Resistor Modules**, which extend the same concept while providing higher resolution and improved accuracy. These modules are designed for applications that require fine‑grained resistance control or tighter tolerance on resistance values.

## Example applications

* **Sensor simulation**\
  Emulating resistive sensors such as RTDs, thermistors, potentiometers, or strain gauges by dynamically adjusting resistance values based on simulation outputs.
* **Hardware‑in‑the‑Loop (HIL) testing**\
  Injecting controlled resistance values into ECUs or embedded controllers to validate input conditioning, fault detection logic, and calibration under realistic operating conditions.
* **Automated test systems (ATE)**\
  Performing automated production or validation tests where resistance needs to be swept, stepped, or precisely set without manual intervention.
* **Fault injection and robustness testing**\
  Simulating open circuits, short circuits, drift, or out‑of‑range resistance values to assess system robustness and diagnostic coverage.
* **Calibration and characterization**\
  Supporting calibration routines by applying accurate and repeatable resistance values when characterizing measurement chains or control algorithms.
* **Model‑driven resistance control**\
  Driving hardware resistance values directly from a real‑time simulation model to represent dynamic physical phenomena such as temperature‑dependent wiring losses or aging effects.


---

# 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://www.opal-rt.com/docs/rt-lab/configure-ios/communication-protocol-ios/pickering-driver.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.
