Overview
Sensors collect the data on the sensemetrics platform. This article will briefly cover:
- Sensors on the Network Page
- sensemetrics Hierarchy
- Sensor Status
- Sensor Functions
- Sensor Configuration
Network Page
The first step to visualizing data on the sensemetrics platform is to add a connection to a project, then attach subsequent devices and sensors. Every user with access to the project will be able view the sensors.
Note: Additional sensor permissions like adding, deleting, or configuring are dependent upon the project role.
After adding a sensor to an existing device, it will populate on the right-hand side the column of the Connectivity Module under 'Devices & Sensors'. Each Sensor will be associated back to a parent device and connection, which will transmit the collected data to the sensemetrics platform.
Workspace | Network |
Hierarchy
Within the sensemetric's hierarchal system, sensors are the bottom falling beneath connections and devices. This is because a sensor will not be able to connect without first adding a connection and device that will transmit the data to the sensemetrics platform. Sensors physically collect the data but also represent the data in sensemetrics. Select a sensor in any of the data analytic tabs to view data on a graph or in a table.
Note: Database connections like GeoMos and Spider will automatically populate the Sensor column with Prism or GPS data once they are added.
sensemetrics hierarchy |
In the above example, a single channel datalogger device has been added to a Thread. The sensor branch depicts the sensors that will be associated with that Thread and Datalogger. Since the datalogger has built in temperature and voltage sensors they are automatically populated. Meanwhile, the vibrating wire (VW 01) sensor was manually added. Rhese three different types of data will be represented as three different Sensors.
Note: Threads will automatically create diagnostic sensors like pressure, temperature, voltage, signal strength, battery and more.
Sensor Status
The Status of a sensor will always go red if its parent connection goes red. A sensor can also go red independently of the device due to sensor level issues.
Indicator | Description |
A green indicator represents the sensor is currently connected to the network | |
A red indicator will indicate the sensor is either powered down or not able to establish a connection | |
A blue indicator represents a sensor on a power schedule |
Sensor Functions
Icon | Description |
Click the arrow drop down next to a device to view associated sensors | |
Check the box next to any sensor to select it. Bulk editing or single editing options will populate at the top of the Devices & Sensors module | |
Trigger selected sensors to take a reading immediately | |
Graph selected sensors |
|
Show tabular data for selected sensors | |
Create a new alert with selected sensors | |
Sort devices and sensors by type, status, last activity and more | |
Hide devices and their associated sensors. You can hide by archived, offline, low power, and always on | |
Use the mass editor to edit any common parameters of the selected sensors. |
Sensor Configuration
Click on a sensor to enter the sensor details page for a summary of the sensor, any associated documents, sensor location, and the most recent readings.
Workspace | Network |
You can also edit sensor settings by clicking on the Edit Configuration tab in the side navigation menu. Some sensors will require additional parameters to be configured prior to collecting data. Please visit Sensor Configuration Overview to learn more about sensor configuration.
Comments
0 comments
Please sign in to leave a comment.