Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Home
  • Knowledge base
  • Contact Us
  • Home
  • Connectors
  • Virtual

Virtual - Connector setup

Using the Virtual Connector

Written by Ioannis Panteleakis

Updated at August 30th, 2021

Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Installation & Technical information
    Introduction SIA Connect Standalone SIA Connect ANY-Ware Cellular & WiFi connectivity
  • Configuration in the Web UI
    Getting started with the UI Connectors Instances Items Mapping Data System Network Tools & Add-ons DigiCert IoT Trust Manager
  • Connectors
    Siemens S7 Azure IoT Ethernet/IP Mitsubishi MELSEC OPC-UA Server SQL MQTT Omron Host Link REST API Omron FINS Keyence Beckhoff TwinCAT BACnet Virtual OPC-UA Client MS SQL File M-Bus Modbus
  • Scripting & Variables
    Data formatting
  • Developers
    API documentation Shadow API
  • Tutorials & Guides
    InfluxDB AWS IoT Core - Amazon Web Services Microsoft Power BI KaaIoT Siemens S7 AVEVA Insight SIA Connect Demo Rack Grafana Azure
  • General
+ More

Table of Contents

ParametersUse casesAdditional internal information

The Virtual connector is meant to be used primarily as a middleware connector and can be thought of as a data container.

Delete

Only the Read Interval in the parameters inside the Virtual connectors is used. The rest of the parameters are ignored.


Parameters

The Virtual Connector is meant to be as abstract and simple as possible and it doesn't have any extra parameters.

Use cases

  1. As a container for different values
    Multiple items values from different connectors could be grouped and listed into a single item in the Virtual connector.
    This allows the flexibility to have only one common place where the formatting of the data happens (no need to modify values for each original item).
    Then the value of the virtual item could be used in a mapping as master to be finally published to an MQTT broker / topic.
  2. Do calculations in post processing
    The Post Processing functionality in an item field allows to re-format the read value of that item.
    That value will be saved in the SIA database. Sometimes it might be desirable for this value to also be reflected on the physical Instance (eg. a PLC).
    A virtual item could then read the original value, and apply some post-processing on it (e.g. a mathematical expression).
    A mapping could then be created from this virtual item (acting as master) to a PLC (acting as slave) triggering a writing to it.
  3. As a converter
    Read a value from an item on PLC1 (for example, the temperature in degrees Celsius). A virtual item then makes a conversion to Fahrenheit (using post-processing). This is then used in a mapping to write the converted value on PLC2, keeping the original value on PLC1's item.
  4. As a testing bed
    Create a virtual item that is then used as master in a mapping. The slave side of a mapping can be a remote HTTP server or an MQTT broker.
    Manually setting a value on the virtual item, will trigger on demand an HTTP request or publish a message on the other end.



Was this article helpful?

Yes
No
Give feedback about this article

Related Articles

  • Bulking multiple data items into a JSON message

0
0
Expand