Difference between revisions of "Configuration"

From Anitra Support
Jump to: navigation, search
Line 54: Line 54:
 
*** comfortable day/night transition set up (sun angles above the horizon). Visual control over the settings
 
*** 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
 
*** sampling frequency for day/night entered parallel in seconds, minutes or hours
*** easy synchronization between various animals  
+
*** easy synchronization between various animals <br>[[File:Config12_dc_solar.JPG|900px]]
 
** "human time"
 
** "human time"
 
*** 24hours cyclic GPS/sensor frequency setting (day/night ignored)
 
*** 24hours cyclic GPS/sensor frequency setting (day/night ignored)
*** the cycle starts at the pre-defined hour (UTC)
+
*** the cycle starts at the pre-defined hour (UTC) <br>[[File:Config12_dc_human.JPG|900px]]
  
 
==== Activity triggered data collection  ====
 
==== Activity triggered data collection  ====
Line 63: Line 63:
 
* 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 the trigger no.2
 
* 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 the trigger no.2
* a sensitivity range for each of the algorithms available
+
* 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 construction of 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
+
* 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]]
  
 
==== Mortality detection  ====
 
==== Mortality detection  ====
Line 77: Line 77:
 
** the detection sensitivity level  
 
** the detection sensitivity level  
 
** the number of confirmation cycles (interval of 30 seconds) before the mortality warning is raised
 
** the number of confirmation cycles (interval of 30 seconds) before the mortality warning is raised
* when turned on, the functionality consumes some extra energy
+
* when turned on, the functionality consumes some extra energy<br>[[File:Config12_dc_mortality.JPG|900px]]
  
 
==== Geofencing using POIs ====
 
==== Geofencing using POIs ====
* Adjustment of basic data collection cycles based on location (Geofencing using Points of Interest (POIs))
+
* an adjustment of basic data collection cycles based on geographic location  
* definition consists of  
+
* the definition consists of  
** GPS position of the center of POI  
+
** GPS position of the center of POI + radius/range from the center of the circle
** radius/range from the center of the circle
 
 
** 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
* mapping to the database of Nests, 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)
+
* ready for dynamic POIs synchronization (the tag downloads definition for 20 geographically closest POIs)<br>[[File:Config12_dc_POIs_geofencing.JPG|900px]]
  
 
==== GPS/sensor bursts ====
 
==== GPS/sensor bursts ====
* detaild
+
* 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 ===
 
=== Communication schedules ===
  
 
==== Fixed times ====
 
==== Fixed times ====
* four fixed time slots a day
+
* four fixed time slots a day<br>[[File:Config13_comm_fixed.JPG|900px]]
  
 
==== Alternative schedules ====
 
==== Alternative schedules ====
 
* three additional comfortable data delivery schedules
 
* three additional comfortable data delivery schedules
** Human time: cyclic frequency + adjustable cycle sync start
+
** Human time: cyclic frequency + adjustable cycle sync start<br>[[File:Config13_comm_alt_human.JPG|900px]]
** Solar time: option of different communication timer during day and night
+
** Solar time: option of different communication timer during day and night<br>[[File:Config13_comm_alt_solar.JPG|900px]]
** Data: communication can be launched whenever a defined number of records collected by the logger
+
** Data: communication launched whenever a defined number of records collected by the logger<br>[[File:Config13_comm_alt_data.JPG|900px]]
  
 
==== 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)
+
* 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|900px]]
 
 
 
 
  
 
=== 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 02:04, 2 June 2019


General remarks

  • Customer Owners/Admins of ANITRA devices can access and modify device configuration
    • from Device List
      Config devicelist.JPG
    • from Device Profile
      Config profile.JPG
  • Configuration is managed in the dedicated application screen

Orientation and context

  • changes done by users are visualized by blue and red icons
    • unsaved modifications in the configuration are visualized by blue (see no.1)
      • a tooltip hint shows saved vs modified value (see no.5)
      • you can revert to the original value by clicking the particular "pen" icon (at the particular value or group level)
      • closing the screen removes all the unsaved (blue) modifications
    • for applying the modified parameters press the "Save and send" button (see no.3)
      • by doing so, all the blue "pens" will turn to the (waiting) red "clock" icons (see no.2)
      • until the values are not confirmed by the device
        • you can discard the pending value by clicking the particular "clock" icon (at the particular value or group level)
        • you can discard all pending changes by clicking "Discard pending changes" button (see no.4)
  • icons (see no. 6) indicate the workflow status of each value (edited >> waiting >> confirmed)
  • question mark icon (see no.7) displays in the tooltip hint the default value for each parameter

Config11 orientation.JPG

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

Configuration structure/areas

  • Admin Configuration
    • not available to users
    • a range of admin parameters which controls 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
        Config12 dc solar.JPG
    • "human time"
      • 24hours cyclic GPS/sensor frequency setting (day/night ignored)
      • the cycle starts at the pre-defined hour (UTC)
        Config12 dc human.JPG

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 the trigger no.2
  • a sensitivity range for each of the algorithms available
    Config12 dc activitytrigger.JPG

Activity Estimation

  • a checkbox to switch on continuous activity estimation
  • activity is measured twice a minute which allows construction of 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
    Config12 dc activity.JPG

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
    Config12 dc mortality.JPG

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)
    Config12 dc POIs geofencing.JPG

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

  • four fixed time slots a day
    Config13 comm fixed.JPG

Alternative schedules

  • three additional comfortable data delivery schedules
    • Human time: cyclic frequency + adjustable cycle sync start
      Config13 comm alt human.JPG
    • Solar time: option of different communication timer during day and night
      Config13 comm alt solar.JPG
    • Data: communication launched whenever a defined number of records collected by the logger
      Config13 comm alt data.JPG

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)
    Config13 comm oneoff.JPG

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)
    Config04 storagemode.JPG