# Test Point Control

## What is a switching system

{% embed url="<https://www.youtube.com/watch?v=3j9Fa2T7JEs>" %}

Switching system is hardware that allows you to create connections between test equipment and the device under test.

Switching systems are needed because the test equipment channel count is often limited therefore one test equipment channel is used for multiple DUT test points

<figure><img src="/files/HKHevOT4bvOr9hUS1XPi" alt=""><figcaption></figcaption></figure>

Example of an application with a switching system

<figure><img src="/files/LOpPtfHLut9VTxseuYp5" alt=""><figcaption></figcaption></figure>

## Supported Switching System

**FunTEST Switching System Plugin**\
The most commonly used switching system with FunTEST is MX2400 (<https://www.funtestfpc.com/matrixbox>). How to use this plugin can be found here [Broken mention](broken://pages/2eF40t6GwB3Pi3mWu23f)

<figure><img src="/files/qnEb2m3KoYFfoJfYs0ak" alt=""><figcaption><p>MX2400</p></figcaption></figure>

## How to use the switching system within a test sequence

To implement a switching system into your test sequence you need to follow these three steps:

### Master Routing

This is to connect your test equipment to the backplane buses of MX2400

The easiest way to do this is to utilize the user interface of the plugin. Go to **admin>devices** and click on MX2400 Matrix. In the newly opened window click routing. The following screen should appear:

<figure><img src="/files/WpTB5Ejwe7QkMYPEaedA" alt="" width="375"><figcaption></figcaption></figure>

Here you can intuitively create your desired interconnection by simply clicking on the schematics. When you reach your desired state copy the equivalent command located under the schematic view.

This command can be used in your test sequence to set the switching system in you desired state. This can be repeated for any other configuration you need.

To use this command in a test sequence, enter the copied command to MX column at desired test step.

<figure><img src="/files/RdjAEtcRdnl8GN1PiN8P" alt=""><figcaption><p>Master routing within a test file</p></figcaption></figure>

### MX card routing

MX card routing follows the same logic as master routing. In this case, we're connecting cards with our test points to the back panel buses. To create the command we'll switch to the tab Test-points within the MX plugin.

<figure><img src="/files/50QkwIBYM6zgHuHsfC9C" alt="" width="375"><figcaption></figcaption></figure>

By clicking on the bottom schematics we can create our desired connection the same way as for the master routing and copy the equivalent command to our test sequence:

<figure><img src="/files/DxQfb94Eval77E7TEhnB" alt=""><figcaption></figcaption></figure>

### Test Point Control

Now that we have successfully routed both MX and Master Cards to the buses we can start controlling test points to connect the device under test and the test equipment.

To do that you can use&#x20;

* **set**\
  Example:\
  set:10:15\
  Leave currently connected TPs and connect moreover TP10 to LOW and TP15 to HIGH.
* **cset**\
  Example:\
  cset:10:15\
  Disconnect all TPs and connect TP10 to LOW and TP15 to HIGH bus
* **clr**\
  Example:\
  clr:10:15\
  Disconnect TP10 from LOW and TP15 from HIGH bus. Any other connected TP is leaved untouched.

{% hint style="info" %}
You can address test points directly by their automatically assigned number from the screenshot above but it's highly recommended to use aliases for test points to make your test sequence easy to read and maintain. Learn more [Test Station Setting](/funtest-documentation/test-station/test-station-setting.md)&#x20;
{% endhint %}

<figure><img src="/files/08Id27CrhI2fh1JAWhtw" alt=""><figcaption><p>Simple test sequence to measure voltage at two different test points</p></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://funtest-1.gitbook.io/funtest-documentation/creating-test-sequence/test-point-control.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
