Configuration

Overview & Basic Concepts

Users with admin rights (device owners/admins) can access the configuration from the lists and profiles using cogwheel icons.

Note the configuration functionality is available for Anitra devices only.

User configuration screen is structured into three main areas

• Data collection settings
• Communication schedules
• Other settings

Note many more advanced settings are possibly available to adjust device behavior upon request/need (device maintenance, troubleshooting, firmware upgrades, custom configuration/behavior - such as GPS accuracy etc)

Any changes made are visualized by blue and red symbols close to the modified setting and in the top right corner of each modified section

• symbols ("pen", "clock" and "check") show the status of each configuration (edited (=blue "pen") >> pending (=red "clock") >> confirmed (=green "check"))

New modifications (not yet submitted) are highlighted by blue color

• these modifications can be reverted to saved values simply by closing the config screen or by clicking on the blue "pen" (for a particular parameter or on the section level)
• in order to submit the modified parameters, click the "Send" button below

Submitted values are highlighted by red color

• >> all the blue "pen" icons change to red "clock" icons indicating the value is waiting for the device to apply it
• note the configuration changes apply whenever the tag connects to communicate/send data

Until the values ​​are confirmed by the device the pending changes can be modified or canceled

• by clicking on the particular "clock" icon - for a particular parameter or on the section level
• by clicking on the "Discard all pending changes" button below - for canceling all

Once the pending parameters are received, accepted, and confirmed successfully by the device the status is changed from red "clock" to green "check"

• note by default the configuration is sent and delivered to the device via GPRS data
• as a supplementary delivery channel SMS can be used ("Send by SMS" button)

Using SMS might help to deliver configuration mainly in certain areas with poor GPRS data coverage however please note using SMS has certain limitations

• SMS delivery is not a guaranteed channel (if not delivered SMS disappears from the network in a couple of hours) - this might cause inconsistency in device configuration temporarily
• just a small subset of the full configuration scope can be fit into one single SMS (therefore the "Sent by SMS" button is only available till the modifications made fit into one SMS message)
• also note additional charges might be applied when using SMS excessively

Configuration areas / Device features

The configuration screen shows only

• the settings relevant to a particular hardware model, firmware version, etc.
• the options relevant to the context of previous selections (unrelated or conflicting options are hidden)

Data collection settings

Left-side "Data collection" section concentrates all the controls related to data sampling

Scheduled GPS/sensor sampling

Defines type and structure of data triggered by the scheduler and the actual schedules

Data scheduler offers two distinct modes

• defined as separate cycles or day and night
• defined as an interval (ignoring both human clock and day and night transitions)

Different day & night cycles (night saving)

Day/night and night/day transition is configured by sun angles (either typing in the angle form or comfortably using the slider below day/night graphic)

Measurement intervals within each daypart use

• "human time" (UTC clock) - intervals synchronized around defined UTC time (by default around UTC midnight)

• "solar time" (i.e the local solar time for actual GPS position)

By default, the sampling interval is restarted with each day/night and night/day transition (i.e. the first position is collected with the day/night transition)

Alternatively, the interval can be synchronized around solar midnight/noon (positions are evenly distributed around solar noon/midnight)

Schedules defined as Interval

Useful in situations when different day and night interval is not needed or when intensive energy saving needs to be achieved (data sampling within many hours or even days)

• In the first option, the interval is synchronized to the human UTC clock

intervals matching 24 hours cycle need to be used

• any interval below 4 hours
• 6,8,12,24 hours
• multiples of 24 hours: 24,48,72 ... 240 etc

• The second option allows defining the floating interval unrelated to the human UTC clock

in this case, any intervals can be used (not anyhow restricted)

GPS/data measurements vs GS/data bursts

The scheduler can trigger both - single GPS/data measurements and/or GPS/data bursts. In default, single measurements are triggered.

When the burst launching is activated, an additional configuration section is displayed to specify burst behavior

Note the following about measurements and bursts:

GPS/data measurement

• Is a single planned (or activity-triggered) measurement event saving data from available/active sensors

• The full dataset structure contains GPS data (latitude, longitude, altitude, direction, speed, and GNSS quality metrics), solar and battery voltage/percent, 3ax-sensors data (accelerometer, magnetometer, gyroscope), temperature. barometric pressure, and some more value-added calculated measures)

• For sake of energy saving some measurements might be scheduled to run without activating the GNSS module and without waiting for GPS fix - i.e. interlacing GPS records with a sensor only records in data delivered into database

By default, GPS is turned on for every measurement:

GPS interlacing can be configured here (1 GPS position + 4 non GPS records taken):

GPS can be turned off completely like this

Note these settings are ignored when mortality is detected.

GPS/data burst

• a time-limited (by "burst length") continuous series of measurements at a defined sampling rate/interval (even down to 50Hz = 50 records/second)

• while running bursts the device is switched to data and energy-intensive mode - a minimum battery level restriction should be maintained at a safe level

• each of the sensor types used has a different "maximum resolution" - therefore in the case of running fast burst, we distinguish between
  • "slow" data (GPS data, temperature, battery voltage, or barometric pressure) - these are only present in one-second data or slower and
  • "fast" data (accelerometer, magnetometer, gyroscope) which can be sampled at a much higher frequency (e.g. up to 50hz) and saved in every record (e.g 50x per second)

• for sake of energy-saving the busts can be also run without activating GNSS and storing GPS data at all.

• for limiting data volume generated by fast bursts "acc only" mode is available (only accelerometer data are stored - not magnetometer and gyroscope data)

• Starting of the GNSS module and acquiring GPS position typically lasts a couple of seconds - the following options allow adjusting the burst start behavior the way needed

Activity triggered data collection

Range of triggers that can activate/wake up of the device when a certain activity event is detected by the hardware sensors

Currently implemented triggers

• "wake up from accelerometer" - based on sudden movement - e.g. can be used to detect take off / landing
• "wake up from altimeter" - based on height change in meters

Upon activation, the selected trigger can launch either a single measurement or burst

In case of using triggers for burst an additional burst configuration screen is opened (similar to bursts triggered by schedule)

Mortality detection

Dedicated Anitra proprietary algorithm based on accelerometer and gyroscope evaluation. Comparing to the older version the new version is much more sensitive and accurate.

When enabled, the mortality status is continuously evaluated and logged (note the device consumes additional energy).

As soon as the status changes to "mortality detected" the device can proactively launch communication and notify of the mortality event immediately.

Actual mortality state (in mortality/not in mortality) is stored in each dataset and usable for calibration for particular species or even individual/deployment.

Note the default configuration options are adjusted to detect while the tag is deployed as a backpack (best tested for raptors)

Calibration parameters are detection interval, number of confirmation cycles before the mortality warning is raised, and detection sensitivity

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)
  

Communication schedules

Right-side "Communication plans" section concentrates all the controls related to communications schedules/data delivery

Anitra devices offer a very wide range of communication setups to match best any particular field situation. Users can combine the following options in order to achieve desired behavior and data delivery timing

• Communication defined by intervals
• Communication defined by fixed UTC timeslots
• Communication based on number of records collected
• One-time communication UTC timeslots
• Additional options

Communication defined by intervals

This communication plan allows programming the tag to sent data regularly within defined cycles/intervals. The plans can be set up

• synchronized to human clock
  • the interval is repeated within 24 hours and restarted at a defined sync time
  • because of that only intervals matching 24 hours are allowed here (i.e. intervals of 1,2,3,4,6,12 hours)

• or floating (not synchronized to the clock)
  • the interval is repeated independently of human clock hours
  • the cycle is restarted with the applied change of the cycle (or when the device is completely discharged)
  • any hours intervals are allowed in this case (i.e. 1,2,3,4,5,6,7 hours) which might result in different communication time from one day to another

Note this schedule can not be completely turned off as it also acts as an "emergency" schedule (i.e. in case of accidentally turning off all other plans)

Even when turned off by a user the schedule is still triggered every 648 hours (27 days)

Communication defined by fixed UTC timeslots

This functionality offers up to four "fixed" time slots

• fixed to a particular UTC day hour
• and run every X days defined per slot

Communication based on number of records collected

Communication is relaunched whenever a defined number of records is collected by the tag

This setting might be particularly beneficial in case of the use of dynamic, unpredictable, or data-intensive sampling modes (such as data/burst triggered by activity or speed triggers)

One-time communication UTC timeslots

In this case, the tag enforces GPS position taking before running communication

A typical use case is planning the one-time session at the time of the planned field check (e.i. the tag delivers a fresh GPS position)

Allows parallel scheduling of up to four one-time communication sessions defined at a particular UTC date/time

Other communication-triggering events

Note the communication can also be triggered in some other situations

• device notifies its state in Power-off / Storage mode

• mortality detection functionality can be configured to sent data when mortality reliably confirmed

• POI/geofencing can also be configured to trigger communication (when entering POI)

• Finally a special SM communication session is trigger when regular data schedules fail cor certain number of days

Taking into account above mentioned various communication sources the predictability of the next communication session is limited

The "Next schedule" prediction only factors schedules planned to UTC clock

Other user settings

Bottom-right section concentrates all the remaining user controls (Communication Channels preference, Storage mode configuration, appended radio buoy or release trigger control etc)

Storage mode

• allows bringing the device to low energy consumption mode
• the device is powered off most of the time and only wakes up at 00:00 UTC in a specified day interval to send tag status (one dataset - GPS, battery level, etc.)
• the communication interval can be set between 1 and 32 days
• using storage mode is useful for long-distance transport and for storing undeployed devices longer time (e.g. when solar charging or GPS signal is unavailable longterm)