Gravio can be installed and operated on cloud services such as AWS, Azure, GCP, etc. (hereinafter described as “cloud”) starting from version 5 . Gravio can now be installed and operated on these services as well.
A node on which the Gravio HubKit is installed is called a “Node hub” or “node” starting with Gravio version 5.
By installing the Gravio HubKit package on the cloud service, this server can be used as a Node hub server to aggregate data .
This Node hub server is referred to as the “Main server”.
Note: To operate a Main server, you need a “Main License” granted by your Gravio Business or Bussiness Pro service contract.
Gravio Business/Bussiness Pro customers can also use the Gravio Cloud servers we provide.
Modules running on Gravio Main server
The following modules included in the HubKit package reside on the Gravio Main server as a server.
|Gravio Coordinator||encompasses the management of the Node hub and the aggregate database of sensor data.|
|Gravio HubKit||a set of modules for collecting and managing sensor data and other data, including action engines|
|Gravio Configuration Manager||Provides HubKit settings and initial configuration functions for Gravio coordinators.|
modules that work with the Gravio Node Hub
The following modules included in the HubKit package reside as servers in the Gravio Node Hub.
|Gravio HubKit||A set of modules for collecting and managing sensor data and other data, including action engines|
|Gravio Configuration Manager||Provides HubKit settings and initial configuration functions for Gravio Coordinators, etc.|
HubKit configuration and Action Flow editing tools
In Gravio, “Action Flows” (or “Actions” ) You can run a user-created data flow program called (marker-blue) on HubKit.
A GUI application called “Gravio Studio” is available for Windows and Mac as a tool for editing HubKit settings and action flows.
|Gravio Studio||HubKit configuration and action flow editing tool|
Gravio Studio can be used to manage and configure the following
*Setup of physical sensor devices. Mapping of where they are located within the physical space.
*Management, monitoring and maintenance of sensors.
*Creating and configuring actions triggered by the sensor network.
*Creating and editing action flows.
*Data display of raw sensor data.
There is a portal site for viewing and managing your Gravio subscription information and license usage.
When you log in to Gravio.com from Gravio Studio, you can use various file backup services from Gravio Studio’s configuration panel to gravio.com.
Gravio HubKit consists of several server modules.
|Gravio Control Manager||Server that controls communication with Gravio Studio|
|Gravio Trigger Manager||A server that receives various sensor data from each device management manager server (Serial Port, Bluetooth, Video, etc.) and saves the sensor data. It also checks incoming data values for conditions specified in the trigger settings and, if applicable, requests the Gravio Action Manager to execute them.|
|Gravio Action Manager||Server that executes the action and saves the sensor data.|
|Gravio Serial Port Manager||Responsible for managing the connection with physical sensors via serial ports and sending data acquired from sensors to Gravio Trigger Manager.|
|Gravio Bluetooth Manager||Manages connections with physical sensors connected via Bluetooth and sends data acquired from sensors to Gravio Trigger Manager.|
|Gravio Video Service||This service manages the connection to the Onvif Camera, stores images/video from the camera, and sends data acquired from image inference to the Gravio Trigger Manager.|
|Gravio MQTT Service||Responsible for sending data acquired from MQTT to Gravio Trigger Manager.|
|Gravio Image Processing Manager||Responsible for sending data acquired from image processing servers such as IVAR to Gravio Trigger Manager.|
|Gravio App Service||A server with auxiliary functions for executing components|
Need more help with this?
Join our slack community for help