> 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/op8120/op8120-gen-1-modular-signal-conditioning-chassis-mscc-legacy/specifications.md).

# Specifications

<table data-search="false"><thead><tr><th width="241">Product name</th><th>OP8120 Modular Signal Conditioning Chassis</th></tr></thead><tbody><tr><td><strong>Part numbers</strong></td><td><ul><li>OP8120-A: MSCC Base chassis 3U for a mix of (OP8121-OP8122) - P/N: 429-0100</li><li>OP8120-B: MSCC Base chassis 3U for a mix of (OP8123-24-25) - P/N: 429-0101</li><li>OP8120-1: MSCC Deluxe chassis 3U for a mix of (OP8121-OP8122-OP8123-OP8124-OP8125) - P/N: 429-0068</li></ul></td></tr><tr><td><strong>Power supply</strong></td><td><ul><li>±5 Vdc screw terminal (preconnected)</li><li>Optional 12 Vdc or 24 Vdc screw terminal (preconnected)</li></ul></td></tr><tr><td><strong>I/O connectors</strong></td><td><ul><li>Screw terminal on the front of the conditioning modules</li><li>DB37 on the rear of the chassis</li></ul></td></tr><tr><td><strong>Modules per chassis</strong></td><td>Maximum of 8, depending on the module type</td></tr><tr><td><strong>Channels per module</strong></td><td>2 or 4</td></tr><tr><td><strong>Total number of channels</strong></td><td>2 to 32, depending on the modules installed</td></tr><tr><td><strong>Dimensions (HxWxD)</strong></td><td>36.5 × 44 × 13 cm (14.37” x 17.32” x 5.12“)</td></tr><tr><td><strong>Storage temperature</strong></td><td>-55 to 85 ºC (-67 to 185 ºF)</td></tr><tr><td><strong>Relative humidity</strong></td><td>10 to 90% non-condensing</td></tr><tr><td><strong>Maximum altitude</strong></td><td>2000 m (6562 ft.)</td></tr></tbody></table>


---

# 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/op8120/op8120-gen-1-modular-signal-conditioning-chassis-mscc-legacy/specifications.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.
