Difference between revisions of "Configuration"
Line 11: | Line 11: | ||
== Orientation and Context== | == Orientation and Context== | ||
− | * The changes made by users are | + | * The changes made by users are visualized by blue and red icons |
** Changes, which are not saved are highlighted by blue color (see nr.1) | ** Changes, which are not saved are highlighted by blue color (see nr.1) | ||
*** The Tooltip hint shows saved vs. modified value (see nr.5) | *** The Tooltip hint shows saved vs. modified value (see nr.5) | ||
Line 39: | Line 39: | ||
* Admin Configuration | * Admin Configuration | ||
** not available to users | ** not available to users | ||
− | ** a range of admin parameters | + | ** a range of admin parameters that control basic device behavior, allows remote troubleshooting, firmware upgrades, etc. |
* User configuration: covers the following aspects of device behavior | * User configuration: covers the following aspects of device behavior | ||
Line 62: | Line 62: | ||
* checkboxes for two different algorithms detecting movement | * checkboxes for two different algorithms detecting movement | ||
* trigger 1: a slot fixed for a generic algorithm detecting movement from the accelerometer | * trigger 1: a slot fixed for a generic algorithm detecting movement from the accelerometer | ||
− | * trigger 2: a slot ready for other customized movement detection algorithm(s). Up to 12 variable algorithms can be implemented on request and assigned to | + | * trigger 2: a slot ready for other customized movement detection algorithm(s). Up to 12 variable algorithms can be implemented on request and assigned to trigger no.2 |
* a sensitivity range for each of the algorithms available <br>[[File:Config12_dc_activitytrigger.JPG|900px]] | * a sensitivity range for each of the algorithms available <br>[[File:Config12_dc_activitytrigger.JPG|900px]] | ||
==== Activity Estimation ==== | ==== Activity Estimation ==== | ||
* a checkbox to switch on continuous activity estimation | * a checkbox to switch on continuous activity estimation | ||
− | * activity is measured twice a minute which allows construction of very detailed activity journal | + | * activity is measured twice a minute which allows the construction of a very detailed activity journal |
* note: this functionality is not data intensive (no additional data costs) but it consumes some energy on top of regular GPS/communication cycles<br>[[File:Config12_dc_activity.JPG|900px]] | * note: this functionality is not data intensive (no additional data costs) but it consumes some energy on top of regular GPS/communication cycles<br>[[File:Config12_dc_activity.JPG|900px]] | ||
Line 85: | Line 85: | ||
** modified day/night data collection interval | ** modified day/night data collection interval | ||
* up to 20 static POIs with different configurations can be defined for each device | * up to 20 static POIs with different configurations can be defined for each device | ||
− | * flexible mapping to the database of Nests, favorite perches, Pylons or other POIs | + | * flexible mapping to the database of Nests, favorite perches, Pylons, or other POIs |
* ready for dynamic POIs synchronization (the tag downloads definition for 20 geographically closest POIs)<br>[[File:Config12_dc_POIs_geofencing.JPG|900px]] | * ready for dynamic POIs synchronization (the tag downloads definition for 20 geographically closest POIs)<br>[[File:Config12_dc_POIs_geofencing.JPG|900px]] | ||
Line 107: | Line 107: | ||
==== One-off schedule ==== | ==== 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)<br>[[File:Config13_comm_oneoff.JPG|400px]] | + | * allows scheduling a single communication at a particular date and time (e.g. data to be pushed to the server while performing a field check)<br>[[File:Config13_comm_oneoff.JPG|400px]] |
=== Storage mode === | === Storage mode === | ||
* 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) <br>[[File:Config04_storagemode.JPG|900px]] | * 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) <br>[[File:Config04_storagemode.JPG|900px]] |
Revision as of 21:25, 2 March 2021
Contents
General notes
- User customers and Admins of ANITRA loggers can access their configuration and are able to modify it
- The configuration can be modified in the particular application screen
Orientation and Context
- The changes made by users are visualized by blue and red icons
- Changes, which are not saved are highlighted by blue color (see nr.1)
- The Tooltip hint shows saved vs. modified value (see nr.5)
- You can go back to the original value by clicking on the blue "pen" icon (in the particular value or on the group level)
- Closing the screen disappears all unsaved (blue) modifications
- To apply the modified parameters, click the "Save and Send" button" (see nr.3)
- All blue "pen" icons change to red (indicating waiting) "clock" icons (see nr.2)
- Until values are confirmed by the device
- Pending changes can be canceled by clicking on the particular "clock" icon (always for a specific value or group level)
- All pending changes can be canceled by clicking on the button "Discard all pending changes" (see nr.4)
- Changes, which are not saved are highlighted by blue color (see nr.1)
- Icons (see nr.6) show the working status of each value (edited >> pending >> confirmed)
- Question mark icon (see no.7) displays in the tooltip hint the default value for each parameter
Configuration delivery and application
- configuration is applied whenever Device connects to communicate (sending data)
- only the modified configuration parameters are sent in order to optimize the 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/areas
- Admin Configuration
- not available to users
- a range of admin parameters that control basic device behavior, allows remote troubleshooting, firmware upgrades, etc.
- User configuration: covers the following aspects of device behavior
- Data collection settings (GPS/sensor frequencies, activity, mortality, geofencing, data bursts, etc)
- Communication settings
- Storage mode (sleep, power off)
Data collection settings
GPS/sensor sampling
- configurable using solar or human time
- "solar time"
- the device synchronizes the data collection to local GPS time based on GPS.
- comfortable day/night transition set up (sun angles above the horizon). Visual control over the settings
- sampling frequency for day/night entered parallel in seconds, minutes or hours
- easy synchronization between various animals
- "human time"
- 24hours cyclic GPS/sensor frequency setting (day/night ignored)
- the cycle starts at the pre-defined hour (UTC)
900px.JPG
- "solar time"
Activity triggered data collection
- checkboxes for two different algorithms detecting movement
- trigger 1: a slot fixed for a generic algorithm detecting movement from the accelerometer
- trigger 2: a slot ready for other customized movement detection algorithm(s). Up to 12 variable algorithms can be implemented on request and assigned to trigger no.2
- a sensitivity range for each of the algorithms available
Activity Estimation
- a checkbox to switch on continuous activity estimation
- activity is measured twice a minute which allows the construction of a very detailed activity journal
- note: this functionality is not data intensive (no additional data costs) but it consumes some energy on top of regular GPS/communication cycles
Mortality detection
- a dedicated mortality detection functionality
- allows detecting mortality of the tracked individual very quickly and reliably
- species (or even individual) calibration of the detection sensitivity possible
- calibration parameters are
- the detection sensitivity level
- the number of confirmation cycles (interval of 30 seconds) before the mortality warning is raised
- when turned on, the functionality consumes some extra energy
Geofencing using POIs
- an adjustment of basic data collection cycles based on geographic location
- the definition consists of
- GPS position of the center of POI + radius/range from the center of the circle
- modified day/night data collection interval
- up to 20 static POIs with different configurations can be defined for each device
- flexible mapping to the database of Nests, favorite perches, Pylons, or other POIs
- ready for dynamic POIs synchronization (the tag downloads definition for 20 geographically closest POIs)
GPS/sensor bursts
- switching device to collect the raw GPS/sensor data
- energy and data-intensive mode
- maximum frequency of 250HZ
- data bursts can be triggered with or without GPS fixing
- minimum battery level restriction to trigger the burst
Communication schedules
Fixed times
Alternative schedules
- three additional comfortable data delivery schedules
One-off schedule
- allows scheduling a single communication at a particular date and time (e.g. data to be pushed to the server while performing a field check)