Difference between revisions of "Configuration"
(→Configuration delivery and application) |
|||
Line 10: | Line 10: | ||
== Configuration delivery and application == | == Configuration delivery and application == | ||
− | + | * configuration is applied whenever Device connects to communicate (send data) | |
− | + | * only modified config parameters are sent in order to optimize traffic | |
− | + | * by default the configuration is sent and delivered to the device via GPRS data | |
− | + | * an alternative delivery channel is SMS ("Send by SMS" button) | |
− | + | ** using SMS might help to deliver configuration in areas with poor data coverage but please note that using SMS has certain limitations | |
− | + | *** SMS delivery is not guaranteed which might cause inconsistency in device configuration temporarily | |
− | + | *** just part of the full configuration scope can be fit into single configuration SMS ("Sent by SMS" button is only available till all the modifications fit into one SMS message) | |
− | + | *** additional charges might be applied when using SMS | |
== Configuration structure == | == Configuration structure == |
Revision as of 07:08, 29 May 2019
Contents
General remarks
- Customer Owners/Admins of ANITRA devices can access and modify device configuration
Configuration delivery and application
- configuration is applied whenever Device connects to communicate (send data)
- only modified config parameters are sent in order to optimize traffic
- by default the configuration is sent and delivered to the device via GPRS data
- an alternative delivery channel is SMS ("Send by SMS" button)
- using SMS might help to deliver configuration in areas with poor data coverage but please note that using SMS has certain limitations
- SMS delivery is not guaranteed which might cause inconsistency in device configuration temporarily
- just part of the full configuration scope can be fit into single configuration SMS ("Sent by SMS" button is only available till all the modifications fit into one SMS message)
- additional charges might be applied when using SMS
- using SMS might help to deliver configuration in areas with poor data coverage but please note that using SMS has certain limitations
Configuration structure
- User configuration covers the following aspects of device behavior
- Data collection settings (GPS/sensor frequencies, activity, mortality, geofencing, bursts etc)
- Communication settings
- Storage mode (sleep, power off)
- Admin Configuration - a range of additional admin parameters which control basic device behavior
Features
- Configuration for ANITRA loggers covers the following main areas and features
- Data collection settings
- GPS/sensor sampling
- configurable based on both solar or human time)
- comfortable day/night transition set up
- Data collection triggered by activity
- Continuous Activity Estimation
- Dedicated Mortality detection functionality
- Adjustment of basic data collection cycles based on location (Geofencing using Points of Interest (POIs))
- Communication schedules
- GPS/sensor sampling
- Communication schedules
- "Fixed times" - four fixed time slots a day
- "Alternative schedules" - three additional comfortable data delivery planners
- Human time: cyclic frequency + adjustable cycle sync start
- Solar time: option of different communication timer during day and night
- Data: communication can be launched whenever a defined number of records collected by the logger
- One-off schedule: allows scheduling a single communication at particular date and time (e.g. data to be pushed to the server while performing a field check)
- Storage mode management: allows to power off devices and configure timeslot for regular device/battery state notification only (i.e. device wakes up only to report battery state at predefined day hour each X days)
- Data collection settings
- for more details see the complete configuration guide