A virtual sensor acts like a physical sensor in that it produces data, but is based on data from another sensor or sensors via a script. To create a new virtual sensor for your machine, you first need to define it.
Do this in the web application by selecting the machine from your machine list or map, and clicking on the menu option “Sensors.” If the sensor you wish to use isn’t already in the list, click the “Add sensor” button. If there is a sensor in the list which is similar to the one you wish to add, you can click on the sensor's options button and select "Duplicate sensor." Either way, you will be taken to the sensor definition page. Now work from top to bottom, filling out the necessary fields as follows:
Sensor kind: Choose “Virtual.”
Sensor name: Give your sensor a unique name. Keeping the name as short as possible will help ensure it fits within the sensor name space in various parts of the application. Note that a sensor name cannot start with "OEE_", "MTBF_", "MTTR_", "EE_", or "KPI_".
Sensor type: Here is a list of standard sensor types, which will pre-fill a number of advanced options. If this doesn’t suit your sensor, choose “Custom.”
Short description: Describe in as few words as possible what this sensor is going to do. This will help ensure you don’t get confused between different sensors.
Sensor group: Assign a group to the sensor. This will allow all the sensors to be categorized when displayed in innius insight for Android.
Data frequency: Select the frequency at which your sensor will produce data. Select this based on the lowest frequency used by the physical sensor or sensors you'll be using as input data in the script.
Data type: This will be pre-filled based on the sensor type, unless you’ve chosen “Custom.” It can be changed.
Value format: This will be pre-filled based on sensor type, unless you’ve chosen “Custom.” It can be changed.
Decimal places: This will be pre-filled based on sensor type, unless you’ve chosen “Custom.” It can be changed.
Visible: If you want to be able to monitor the sensor tile in innius insight for Android and innius admin, then tick this box. If the data isn’t worth monitoring, or you only want to use it as the basis for other virtual sensors, leave it unchecked.
For information about defining thresholds, refer to the article: How are thresholds used?.
With the above definitions you have enough information to create your virtual sensor, although to make it operational you will need to create a script. Refer to the article about the script editor.
If you now want to add another sensor of the same type to the same machine, tick the box “Add another sensor with these settings.” When you click “save,” you will be taken to another add sensor page, in which most of the definitions will be pre-filled.
If you have finished, click “save” to save your virtual sensor, and if you're not adding another, similar sensor, you will be taken back to the sensor list.