Integration With 3rd Party Cloud Software
Message Type | Definition | Value | |
POST Request | POST request can be transmitted by Satevis device to the cloud software, it contains : - Device profile at Startup, - Device current configuration - Diagnostic - Data Measurement When POST request is transmitted by Cloud software it contains: - New device settings ( ex: alarams thresholds, new measurement mode.....) - Initiate datalogger download | 0x01 | |
GET Reques | GET Request is transmitted by the cloud software to read the device status or currents settings, satevis device answers by a POST request | 0x02 | |
Message Type ID | Value | Request Transfer Method (Satevis device to cloud) | Request Transfer Method (cloud to satevis device) | FACTORY Lora Port ID |
Device Main Profile | 0x11 | POST | GET | 0x0F |
Sensor Profile | 0x12 | POST | GET | 0x0F |
System Diag Report | 0x21 | POST | GET | 0x10 |
‘Slow Monitoring’ Data Transmission message | 0x22 | POST | N.A. | 0x12 |
‘Alarm Event (part of ‘Alarm Monitoring’ mode) Transmission message | 0x23 | POST | N.A. | 0x12 |
Data Logs ‘Slow Monitoring’ Transmission message | 0x24 | POST | N.A. | 0x12 |
Data Logs ‘Alarm Monitoirng’ Transmission message | 0x25 | POST | N.A. | 0x12 |
Hello Data Transmission message | 0x26 | POST | GET | 0x12 |
Keep Alive (part of ‘Alarm Monitoring’ mode) Data Transmission | 0x27 | POST | N.A. | 0x12 |
LORA Stack Info | 0x30 | POST | GET | 0x13 |
MonitoringFull Config | 0x31 | POST | POST, GET | 0x13 |
Sensor Channel config | 0x32 | POST | POST, GET | 0x13 |
Monitoring Mode config | 0x33 | POST | POST, GET | 0x13 |
System Diag Settings | 0x34 | POST | POST, GET | 0x13 |
Hardware Reset Request | 0x35 | N.A. | POST | 0x13 |
Lora RejoinFrequ config | 0x36 | POST | GET, POST | 0x13 |
Lorawan com PORT config | 0x37 | POST | GET, POST | 0x13 |
Clock Source config | 0x38 | POST | GET, POST | 0x13 |
N.A. - for future applications | 0x39 to 0x4F | N.A. | N.A. | 0x13 |
DataLogger Config | 0x50 | N.A. | POST, GET | 0x11 |
DataLogger Status | 0x51 | POST | GET | 0x11 |
Sensor Zeroing config | 0x60 | N.A. | POST, GET | 0x13 |
Sensor Zeroing Results | 0x61 | POST | GET | 0x13 |
Inclino sensor config | 0x62 | POST | POST, GET | 0x13 |
Inclino sensor calib. Date | 0x63 | POST | GET | 0x13 |
Error Status | 0xFF | POST | N.A. | 0x13 |
Messages type transmitte by satevis devis durint the Init | Message Type related to data measurement and diag transmitted frequently ( user configurable) |
Message Type Posted during Init or on User Request(Push Button) | Message Transmitted during Init or frequently (user configurable) |
Remote config related to Inclino sensor (Sensor Type 0x31) | Remote device config. Transmitted only on GET request from cloud software |
Datalogger config & status | Error Message |
SATEVIS® DEVICE STARTUP : WHICH MESSAGES ARE TRANSMITTED ?
At device startup , the following messages are transmitted automatically to the cloud software:
• Main Profile: which contains the Satevis® Device ID, all the versions ID (Hardware, Firmware, Lora Stack), Lorawan® Settings and all the timing parameters related to the different monitoring modes
• Sensor Profile: which contains are the sensor channels profile connected to Satevis® Device, this will allow the user to create a database on the cloud software containing the Sensor Type, Conversion Method to the physical unit
Satevis® device will receive a clock synchronization message from LNS on PORT 202.
After sending all the profile information, Satevis® device starts to send Hello Message followed by System Diag Report, helping to make sure the device is working properly.
MESSAGES TRANSFER METHOD : GET AND POST
GET Request
GET Request is transmitted by the cloud software to read the device status or currents settings. If the GET request is well-formed , Satevis® device answers by a POST request containing all the status information related to the GET message.
POST Request
POST request can be transmitted by Satevis® device to the cloud software, it contains:
• Device profile at Startup.
• Device current configuration (as a response to a GET request).
• Diagnostic.
• Data Measurement.
When POST request is transmitted by Cloud software it contains:
• New device settings ( ex: alarms thresholds, new measurement mode.....)
• Initiate datalogger download
ERROR MESSAGE
How to extract the sensor profile ?
Hello message requested Remotely
User can also send a GET request to receive Hello Message:
SENSOR ZEROING
SENSOR ZEROING REQUESTED REMOTELY
Sensor zeroing can also be done remotely from cloud software, there is no need to send a technician on the monitoring to do this operation.
ALARM MODE
Three level of Alarm notifications can be transmitted to cloud software Alert /Action/Alarm .
Several settings are available for an accurate alarm configuration:
● Low or High Alarms Thresholds can be configured;
● For a real-time alarm tracking, the Monitoring refresh cycle can be accelerated when a threshold is reached,
● Alarms can be independently enabled/disabled on the measurement channels;
User can create ‘OR’ or ‘AND’ alarm notification rule between each measurement channel .
If the Alarm threshold is not reached:
● Satevis® device transmits frequently a Keep Alive Message to keep informed the user about the device operation.
● For each measurement channel, Max/Min/Average values and Latest measurement are encapsulated in the Keep Alive Message.
ALL THE TIMING VALUES IN ALARM MODE
• AMRR (Alarm Monitoring Refresh Rate) : In the case of AAA threshold is reached , the monitoring rate is accelerated to track closely the alarm evolution;
• MRR (Monitoring Refresh rate) : In the case if AAA threshold is not reached, the device monitors an alarm at a slower rate
ALARM THRESHOLDS
Three levels of alarms notifications are available allowing users to redirect the alarm notification to different emails or to activate a relay:
● Alert level: lowest level of alarm,
● Action level: medium level of alarm notification
● Alarm level: critical level , field intervention is requested
User can configure High/Level Thresholds alarms, explained hereafter.
High Threshold Alarms
High thresholds alarms can be used to trigger an alarm when a data measurement is rising. Example of temperature sensor:
Low Threshold Alarms
Low thresholds alarms can be used to trigger an alarm when a data measurement is falling. Example of Temperature sensor
Mixed High-Low Thresholds alarms
Mixed High-Low can be used for sensors used to track a structure/equipment moving to one direction and the opposite.
