> 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/scpi/requirements-features-and-limitations.md).

# Requirements, Features & Limitations

## Software requirements

The **SCPI** driver is included by default with RT-LAB and does not require any additional installation.

## Hardware requirements

SCPI operates over Ethernet (TCP/IP) using the simulator’s built-in LAN ports, **eliminating the need for additional hardware**. Standard Ethernet cables are required to establish these connections. For systems requiring extra network interfaces, SCPI can also operate over additional Ethernet ports provided by supported PCIe network cards.

## License requirements

### Simulator license

[Verify that an active RT-LAB license](https://www.opal-rt.com/docs/rt-lab/licensing-reference/simulator-license.md) with the following features is installed on the simulator to run simulations using the SCPI protocol:

| Feature Name | Required Status | Description                                                                         |
| ------------ | --------------- | ----------------------------------------------------------------------------------- |
| SCPI         | Enabled         | Enables the Standard Commands for Programmable Instruments (SCPI) generic interface |

### Workstation license

A workstation license is **not** required to run simulations in RT-LAB using the SCPI protocol.

## Supported features

* **Initial commands**: Commands sent at the start of the simulation to ensure the SCPI device is in the correct operating configuration.
* **Measurements**: Numeric measurement data can be collected from the SCPI device during runtime, either at a defined cyclic rate or based on a trigger data point.
* **Controls**: SCPI device parameters can be updated during runtime using values from the model; control commands may be sent at a defined cyclic rate or triggered by model events.
* **Reset commands**: Commands sent at model reset to place the device in the desired post‑simulation state.
* Support for controlling **multiple SCPI devices**.
* **Configurable TCP port** when operating in TCP mode.
* **Automatic reconnection** support if communication with one or more SCPI devices is lost.
* **Embedded support for a basic SCPI command set** for the Keysight RP79xx family.

## Limitations

* The question mark (`?`) suffix is supported only for measurement commands.
* Communication is limited to TCP mode.
* During runtime, only scalar measurement values are reported to the model. If a measurement command returns a non‑numerical response, it is not propagated to the model; instead, it is printed to the RT‑LAB console at model reset, and only when the model is running in exhaustive mode with the driver verbose mode enabled.


---

# 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/scpi/requirements-features-and-limitations.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.
