> For the complete documentation index, see [llms.txt](https://doc.realvirtual.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.realvirtual.io/components-and-scripts/interfaces/interface-tools/signal-importer-exporter.md).

# Signal Importer Exporter

Standard Signal Import and Export Interface

The Signal Importer Exporter is a tool that enables the import and export of signals in a standardized neutral format to facilitate seamless integration between different systems requiring signal interfaces. It stores the data in a JSON file, making it easy to exchange information between applications, controllers, and automation environments.

The Signal Importer Exporter can be attached to any GameObject that represents an interface in realvirtual.io. It automatically detects and imports/exports all signals located underneath that GameObject in the hierarchy.

{% file src="/files/8rc8Be4DzrDseJe3MKPm" %}

### **Properties**

#### **Signal Paths**

* **Signal Import List File Path**: Specifies the location of the import file.
* **Signal Export File Path**: Defines the folder where exported signals will be saved.
* **Signal Export Filename**: Name of the JSON file for exported signals (e.g., `SignalExport.json`).

#### **Action Buttons**

* **Import Signals**: Loads signals from the defined **import file**.
* **Export Signals**: Saves the current signals to the **specified export file**.
* **Select Signal Import File**: Allows the user to choose an import file.
* **Select Signal Export Folder**: Enables selection of an export folder.

### **Example Signal Export File**

Here’s a sample exported JSON structure showing how signals are organized:

```json
{
    "Signals": [
        {
            "Name": "IO.Input.Robot.bStatusLoading",
            "Symbolname": "",
            "Comment": "",
            "Type": "BOOL",
            "Direction": "INPUT",
            "Folder": "--- Robot Overall Status ----"
        },
        {
            "Name": "IO.Input.Robot.bStatusUnloading",
            "Symbolname": "",
            "Comment": "",
            "Type": "BOOL",
            "Direction": "INPUT",
            "Folder": "--- Robot Overall Status ----"
        },
        {
            "Name": "IO.Output.Robot.bStartLoading",
            "Symbolname": "",
            "Comment": "",
            "Type": "BOOL",
            "Direction": "OUTPUT",
            "Folder": "--- Start Robot Programms ---"
        },
```

#### **Key Properties in the JSON File**

| **Property**   | **Description**                                                                                                                                                                                                                                                                                                                                                                                     |
| -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Name**       | *(Optional - Name or Symbolname must be filled)* The readable name of the signal. If no `Symbolname` is provided, this value is also used as the **unique ID (symbol name)** of the signal. If a `Symbolname` is defined, this name is used only for display in **realvirtual.io**.                                                                                                                 |
| **Symbolname** | *(Optional - Name or Symbolname must be filled)* The actual **symbol name (ID)** of the signal. If left empty, the `Name` field is used as the symbol name.                                                                                                                                                                                                                                         |
| **Comment**    | *(Optional)* A description or note about the signal, useful for documentation. Can be empty.                                                                                                                                                                                                                                                                                                        |
| **Type**       | The **data type** of the signal. Possible values: `"INT"`, `"BOOL"`, `"FLOAT"`, `"TEXT"`.                                                                                                                                                                                                                                                                                                           |
| **Direction**  | <p>The <strong>signal direction</strong>, indicating whether it is an <strong>input or output</strong>. Possible values: <code>"INPUT"</code> or <code>"OUTPUT"</code>.<br>- <strong>INPUT</strong>: The signal is <strong>received</strong> from an external source (e.g., a PLC or hardware system).<br>- <strong>OUTPUT</strong>: The signal is <strong>sent</strong> to an external system.</p> |
| **Folder**     | *(Optional)* Defines a **grouping folder** for organizing signals in **realvirtual.io**. This allows signals to be structured under **empty GameObjects** in Unity for better organization.                                                                                                                                                                                                         |


---

# 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://doc.realvirtual.io/components-and-scripts/interfaces/interface-tools/signal-importer-exporter.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.