CONFIGURATION (OLD)

From AnitraWiki
Jump to: navigation, search


General notes

  • User customers and Admins of ANITRA loggers can access their configuration and are able to modify it
    • Through Device List
      Config devicelist.JPG
    • Through Device Profile
      Config profile.JPG
  • 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)
  • 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

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 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
        Config12 dc solar.JPG
    • "human time"
      • 24hours cyclic GPS/sensor frequency setting (day/night ignored)
      • the cycle starts at the pre-defined hour (UTC)
        900px.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 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 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
    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 a 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