Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Digital Matter Site
  • Contact Us

Hawk Operation - Task Schedules

Written by Matthew Clark-Massera

Updated at May 8th, 2025

Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Contact Support
  • Home
  • Devices
  • Cellular
  • Data Loggers
  • Hawk IoT Datalogger
  • Configuring Tasks

Table of Contents

Maximum Upload Frequency Task Parameters Example Task Configurations Read and report temp/hum every 10 minutes Sample 4-20mA tank level sensor every 10 min, uploading hourly, disable GPS Read Temperature every 10 min, Soil Moisture Probe hourly Sample every 15 min during day, every 6hrs at night Run Task only in response to an event Task Detail

Maximum Upload Frequency

The most the Hawk can upload is once every 2 minutes.

The device can sample sensors more frequently.

If you require lower latency on sensor data being uploaded you can set the device to “Stay Connected”:

  • Upload Settings
 

The Hawk's operation centres around the concept of a "Task" - which is a selection of actions, performed on a schedule, or in response to an event (like a Digital Input Change or Analogue threshold). Up to Four tasks can be configured, with up to 5 actions each. 

If we don't configure a task, the Hawk by default will do nothing but heartbeat once daily. 

We may also need to configure our sensors separately, on other parameter tabs to ensure the setup is correct for when the task runs. 

Task Parameters

Period Unit + Schedule Period Set how often the task (and actions) occur - i.e. how often we sample sensors
Log Multiplier (L) Log every L times the task occurs.
Upload Multiplier Upload every N tasks
GPS Multiplier If the asset is stationary, or moves infrequently, we might disable GPS completely (set to 0) - or set the multiplier to a large number so fixes occur less often. This conserves energy and extends battery life. 
Start/End Period We might only want to run the task during a certain time (i.e. during day). Or we might want it to run every 10 min during 6am -> 6pm, and hourly outside that - in which case we can set up 2 tasks to achieve this.
Action

Actions are typically which sensor readings we want to take, or setting an output, e.g: 

Example Task Configurations

Some examples are given below. These serve to illustrate how to configure tasks, generally we need to configure additional parameters specific to the sensor type and individual sensor.

Read and report temp/hum every 10 minutes

  1. Run the task (take a sensor reading) every 10 min, and log it
  2. Upload every single task - so we sample and upload every 10 min
  3. Run I2C Action 1

We configure I2C action 1 to sample the sensor type we have connected - DM Ambient (Temp/Hum) Sensor

 
 

Sample 4-20mA tank level sensor every 10 min, uploading hourly, disable GPS

  1. Read value every 10 min and log
  2. GPS Multiplier = 0 to disable GPS - the Hawk is mounted in a stationary location so we don't care about GPS position
  3. We upload every 6 tasks - so every 6 x 10 min = hourly
  4. Sample the 4-20mA sensor

For the 4-20mA sensor, we configure a power on delay and which analogue the value should be placed in the Hawk's payload.

 
 

Read Temperature every 10 min, Soil Moisture Probe hourly

Task 1 - read temp every 10 min..   
We set the upload multiplier to 0 to not upload due to this task - the readings will be logged and uploaded together with the task 2 upload.

Task 2 the soil moisture reading (via SDI-12 probe) hourly, and upload.

 
 

Sample every 15 min during day, every 6hrs at night

To save power we may only require aggressive monitoring during working hours.

  1. Set timezone  
  2. Run task 1 (15 min sample + upload from 0600 → 1800  
  3. Run task 2 (6 hour sample + upload) from 1800 → 0600  
 
 

Run Task only in response to an event

We may use this kind of set up to cause the task to turn on an output in response to an event.

E.g. Hawk On-Board Control - Turn on Pump when tank level is too low

 
 

Task Detail

It may be useful to know how the Hawk processes tasks. When a task runs, the following occurs:

  1. Start Task 
  2. GPS started if requested 
  3. Action 1 
  4. Action 2 
  5. Action 3
  6. Action 4
  7. Action 5
  8. Wait for GPS to finish 
  9. Pack readings + results up into a record and log
  10. Upload if necessary
timetable mission plans

Was this article helpful?

Yes
No
Give feedback about this article

Related Articles

  • Hawk - GPS Settings

Subscribe to Partner News

Subscribe to our mailing list to receive Digital Matter news, product and tehnical updates, and more.

Subscribe

Copyright © Digital Matter . All Rights Reserved.

Privacy Contact Support

Knowledge Base Software powered by Helpjuice

Expand