Configuration - Revision history

Admin: /* Advanced Configuration Management using Presets */

2025-12-05T13:13:59Z

‎Advanced Configuration Management using Presets

Admin: /* Advanced Configuration Management using Presets */

2025-12-05T12:00:07Z

‎Advanced Configuration Management using Presets

Admin: /* Advanced Configuration Management using Presets */

2025-12-05T11:57:29Z

‎Advanced Configuration Management using Presets

Admin: /* Advanced Concepts */

2025-12-05T11:08:47Z

‎Advanced Concepts

Admin: /* Mortality detection */

2023-07-06T09:36:56Z

‎Mortality detection

Admin at 09:34, 6 July 2023

2023-07-06T09:34:33Z

Admin: /* Configuration Presets */

2021-10-14T07:26:07Z

‎Configuration Presets

Admin: /* Configuration Presets */

2021-10-14T07:10:33Z

‎Configuration Presets

Admin at 15:50, 4 October 2021

2021-10-04T15:50:45Z

Admin: /* Geofencing */

2021-10-04T09:28:52Z

‎Geofencing

@@ Line 316: / Line 316: @@
 == Advanced Configuration Management using Presets ==
-''[[presets| A detailed guide to the Configuration Presets and to Save and Load Preset functionality here]]''
-<br>
+=== About Configuration Presets  ===
-: This functionality allows saving the current device configuration (combination of parameters) into the "Configuration Preset" object.
 : Only the "user" values generally applicable are saved (device unique "admin" values, such as ID, mobile phone number or individual calibration values, are not included).
@@ Line 326: / Line 327: @@
 : Later, the application of the selected preset modifies only the values/sections previously saved in the preset. You can thus load and apply more independent presets step by step.
-=== Preset creation ===
+=== Preset creation flow ===
-:* use the „Save as preset“ button in the config screen
+:2b) Alternatively, you can pick another Device
-:* name the preset
+::* using "Find device" and using its current configuration the same way as for stored presets.
-=== Loading existing preset ===
+:3) Select the preset or device and review the displayed configuration contents on the right side of the screen.<br>
-:* use the „Load preset“ button
+:4) Press "Load values" to pass the config values back to the device config screen <br>''Note the preset application will modify all the parameters defined in the preset on top of your current configuration.''<br>[[File:Presets_Apply_preset.jpg|700px]]
-''[[presets| A detailed guide to the Configuration Presets and to Save and Load Preset functionality here]]''
+:5b) Note that the geofence presets need to be confirmed separately

@@ Line 343: / Line 343: @@
 :* load values back to the device config screen
 :* review if preset values loaded correctly (marked blue in the config screen)
-:* submit modified configuration & activate geofences created<br><br>[[File:Presets_Apply_preset.jpg|600px]] same as zou do for manual config changes
+:* submit modified configuration same as you do for manual config changes and activate geofences created by preset<br><br>[[File:Presets_Apply_preset.jpg|600px]]
 ''[[presets| A detailed guide to the Configuration Presets and to Save and Load Preset functionality here]]''

@@ Line 318: / Line 318: @@
 ''[[presets| A detailed guide to the Configuration Presets and to Save and Load Preset functionality here]]''
 <br>
-: This functionality allows saving the current device configuration (combination of parameters) into the "Configuration Preset" object
+: This functionality allows saving the current device configuration (combination of parameters) into the "Configuration Preset" object.
-: * only the "user" values generally applicable are saved ("admin" values unique to a particular device, such as mobile phone number or individual calibration values, are not included)
-: * a complete or just a subset of "user" configuration can be saved as a preset. Eg. you can save only communication settings in the first preset, data collection settings in another, and geofence settings in the third separate preset.
+: Only the "user" values generally applicable are saved (device unique "admin" values, such as ID, mobile phone number or individual calibration values, are not included).
-: * Later, the application of the selected preset modifies only the values/sections previously saved in the preset. You can thus load and apply more independent presets step by step.
 === Preset creation ===

@@ Line 315: / Line 315: @@
-== Advanced Concepts==
+== Advanced Configuration Management using Presets ==
+''[[presets| A detailed guide to the Configuration Presets and to Save and Load Preset functionality here]]''
 <br>
-: This functionality allows saving current device configuration (combination of parameters) into general "Configuration preset"
+: This functionality allows saving the current device configuration (combination of parameters) into the "Configuration Preset" object
-: * it can be later applied again at the same device or elsewhere
+=== Preset creation ===
 :* use the „Save as preset“ button in the config screen
 :* name the preset
-:* review the contents
+:* review and adjust the contents
 :* save when all done<br>[[File:Presets_Save_as_Preset.jpg|700px]]
+=== Loading existing preset ===
 :* use the „Load preset“ button
-:* look up the preset
+:* look up the stored preset
-:** using "Find preset"
+:** either using "Find preset"
-:** chosing from "My presets"
+:** or choosing from "My presets"
-:* highlight and review the contents
+:* alternatively, you can pick another device using "Find device" and use its current configuration the same way as for stored presets
 :* load values back to the device config screen
-:* review if preset applied correctly
+:* review if preset values loaded correctly (marked blue in the config screen)
-:* submit modified configuration & activate geofences created<br><br>[[File:Presets_Apply_preset.jpg|600px]]
+:* submit modified configuration & activate geofences created<br><br>[[File:Presets_Apply_preset.jpg|600px]] same as zou do for manual config changes
-: ''(for the complete information about Presets see detailed [[presets| guide to configuration presets]]'')
+''[[presets| A detailed guide to the Configuration Presets and to Save and Load Preset functionality here]]''

@@ Line 193: / Line 193: @@
 : 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"  or vice versa (i.e. status changes from "mortality" to "alive") the device records and additional record.
+: As soon as the status changes to "mortality detected"  or vice versa (i.e. from "mortality" to "alive") the device automaticaly runs additional measurement (GPS+data) and stores this additional record into memory.
 : Config parameter "run extra comm session.." proactively launches extra communication and notify of the mortality event immediately.
@@ Line 203: / Line 204: @@
 :[[File:config_mortality.JPG|800px]]
 ==== Geofencing ====

@@ Line 332: / Line 332: @@
 :* name the preset
 :* review the contents
-:* Save when all done<br>[[File:Presets_Save_as_Preset.jpg|900px]]
+:* save when all done<br>[[File:Presets_Save_as_Preset.jpg|900px]]
 : '''Using preset / Load existing preset'''
-:* Use the „Load preset“ button
+:* use the „Load preset“ button
-:* Look up the preset
+:* look up the preset
-:* Highlight and review the contents
+:* highlight and review the contents
-:* Load values back to the device config screen
+:* load values back to the device config screen
-:* Review if preset applied correctly
+:* review if preset applied correctly
-:* Submit modified configuration & activate geofences created<br><br>[[File:Presets_Apply_preset.jpg|600px]]
+:* submit modified configuration & activate geofences created<br><br>[[File:Presets_Apply_preset.jpg|600px]]
 : ''(for the complete information about Presets see detailed [[presets| guide to configuration presets]]'')

@@ Line 1: / Line 1: @@
-{{DISPLAYTITLE:CONFIGURATION}}
+{{DISPLAYTITLE: CONFIGURATION}}
 ==Overview & Basic Concepts==
@@ Line 54: / Line 54: @@
 : The configuration screen shows only
-:* the settings relevant to a particular hardware model, firmware version, etc.
+:* the settings relevant to a particular hardware model, firmware version, etc. are available
-:* the options relevant to the context of previous selections (unrelated or conflicting options are hidden)
+:* the options relevant to the context of previous selections are available (unrelated or conflicting options are hidden)
@@ Line 157: / Line 157: @@
 : [[File:config_data_burst_wait.JPG|500px]]
 : [[File:config_data_burst_wait_off.JPG|500px]]
@@ Line 167: / Line 166: @@
 : Currently implemented triggers
 :* "wake up from accelerometer" - based on sudden movement - e.g. can be used to detect take off / landing
@@ Line 209: / Line 209: @@
 :Modifies standard device behavior based on the geographic location
-:Specifics of Anitra geofencing
+: Specifics of Anitra geofencing
 :* tailored for very advanced geofencing tasks on top of POI databases with even many thousands of items (e.g. database of past poisoning places, wind turbines, dangerous power pylons, etc)
 :* a dynamic geofence synchronization (when moving the tag synchronizes 100 closest geofence instances)
@@ Line 216: / Line 216: @@
 :** altitude definition enables 3D geofencing (when higher it is considered as outside of geofence)
-:Geofences are created and managed in the Geofence dialog listing all the device geofences and showing them on the map
+: Geofences are created and managed in the Geofence dialog listing all the device geofences and showing them on the map
 :[[File:GF_map_definition.JPG|900px]]
-:A modified geofence behavior is defined in the Geofence behavior screen. A subset of configuration parameters can be overridden within the geofence
+: A modified geofence behavior is defined in the Geofence behavior screen. A subset of configuration parameters can be overridden within the geofence
 :* day/night data collection interval
 :* activity and speed triggering
@@ Line 252: / Line 252: @@
 :** 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
+:** any hours intervals are allowed in this case (i.e. 1,2,3,4,5,6,7 hours) which might result in different communication times from one day to another
 : [[File:config_comm_interval_nosync.JPG|400px]]
@@ Line 286: / Line 286: @@
 : [[File:config_comm_poweroff.JPG|400px]]
-:* mortality detection functionality can be configured to sent data when mortality reliably confirmed
+:* mortality detection functionality can be configured to sent data when mortality is reliably confirmed
 : [[File:config_comm_mortality.JPG|400px]]
@@ Line 302: / Line 302: @@
 === 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)
+: Bottom-right section concentrates all the remaining user controls (Communication Channels preference, Storage mode configuration, appended radio buoy or release trigger control, etc)
 : [[File:config_other_settings.jpg|700px.JPG]]
@@ Line 311: / Line 311: @@
 * 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)
-[[File:config_poweroff.JPG|500px]]
+: * it can be later applied again at the same device or elsewhere

@@ Line 205: / Line 205: @@
 ==== Geofencing ====
-: ''(For the complete information about geofencing see dedicated [[geofencing| geofencing configuration guide ]]'')
+: ''(for the complete information about geofencing see detailed [[geofencing| geofencing configuration guide ]]'')
 <br>
 :Modifies standard device behavior based on the geographic location
@@ Line 226: / Line 226: @@
 :[[File:GF_behavior.JPG|900px]]
-: ''(For the complete information about geofencing see dedicated [[geofencing| geofencing configuration guide ]])''
+: ''(for the complete information about geofencing see detailed[[geofencing| geofencing configuration guide ]])''
 === Communication schedules ===