Motus Docs
  • Motus Docs
  • About Motus
    • Introduction and overview
    • Automated Radio Telemetry
    • Collaborate
      • Host a Station
      • Adopt a station
      • Coordination Groups
    • Donate
    • How to Join Motus
    • Collaboration Policy
    • Discussion Group
    • Partners and Supporters
    • How Data are Processed
      • Tag Finder
      • False Detections
      • Public Data Filters
      • Reprocessing receiver data
    • Quick Reference
      • Tag Deployment
      • Station Deployment
      • Definitions
  • Get Involved
  • Project Management
    • Getting Started
    • Data Access
    • Collaborators
    • Institutions
    • Citations
    • Station Management
      • Detection timelines
    • Tag Management
      • Tag Registration
      • Tag Metadata
      • Move tags to another project
  • Stations
    • Introduction
    • Station Placement
    • Station Structures
    • Station Equipment
      • Receivers
      • Antennas, Cables, and Dongles
      • Power
      • Parts list and suppliers
    • Installation guide
      • Antenna and Coax Assembly
        • Laird Yagi
        • Intermod/Maple Leaf Yagi
        • Intermod Omni
      • Solar Power
      • Building-bracketed Lattice Tower
      • Rock Anchored Lattice Tower
      • Tripod and Pop-up Mast
      • Grounding Antennas
      • Storage Container
    • Downloading Data
    • Station Inspection
      • Antenna Inspection
      • Up time and detectability
      • Parts description
      • Noisy Stations
      • Testing Receiver Antenna Ranges Using a Tag
    • General tips
    • Appendix
      • Receiver power consumption table
      • Tool descriptions
      • Part descriptions
  • Tags
    • Tag Basics
    • How Tags Work
    • Selecting and Purchasing Tags
    • Tag Deployment
      • Instructional Videos
    • Ambiguous Tags
    • Tag Aliasing
    • Tag Storage
    • Appendix
      • Tag Harness Sizes
      • Retrieving lost tags
  • Exploring Motus Data
    • Introduction
    • Data dashboard
    • Detection Timelines
    • Station Status
  • Receivers
    • SensorGnome User Guides
    • Lotek SRX 800 User Guide
    • CTT SensorStation User Guide
    • CTT User Guide Directory
  • Glossary
Powered by GitBook

Support

  • For support and more info visit the Motus Community Forum
On this page
  • Introduction
  • Reboot Odometer
  • GPS Hits
  • Antenna Pulses
  • Combining data to assess station operation

Was this helpful?

Export as PDF
  1. Stations
  2. Station Inspection

Up time and detectability

This section describes how to identify when your station was powered on and able to detect tags.

PreviousAntenna InspectionNextParts description

Last updated 2 years ago

Was this helpful?

Introduction

There is currently no single way to determine when a station was operational. This is because if there are no tags present, there will be no clear way to say tags could have been detected. However, it's possible to come up with a proxy for when a station could have detected tags based on when environmental noise was recorded or when other scheduled operations on the receiver were logged.

Reboot Odometer

SensorGnomes and SensorStations will record each time the device has booted up. While this doesn't tell you when the station was last powered down, that can be inferred based on when data was last collected. It is also important to understand that even when the station is powered on, it may not be able to collect data, therefore it's helpful to check if GPS hits or antenna pulses exist.

This metric is not available for download at this time, but can be found on the top of the and can be helpful in diagnosing power issues stations.

GPS Hits

Motus receivers are programmed to log a GPS hit every 5 minutes by default (should be more frequent for mobile receivers), but sometimes the GPS can miss a hit or two if few satellites are visible overhead. In addition, early GPS units (USB GPS) had a bug which caused the GPS to malfunction and stop collecting data, resulting in missing GPS hits for extended periods of time. Therefore, these data should be used in combination with other logs to determine when the station was operational rather than on its own, unless you know the GPS was not of the USB type.

GPS hits appear as the second line on , on , and on. It can also be downloaded from .

Antenna Pulses

Antenna pulses are a reflection of environmental noise and consist of radio pulses at the nominal listening frequency (e.g.; 166.38 MHz) which did not correspond to a known tag signature. Environmental noise is common and in some instances can be problematic, resulting in large numbers of false detections and/or expensive cellular data bills. In addition, large volumes of noise can make it less likely for real tags to be detected. You can read more about

The amount of noise received by any given antenna depends on a number of factors and varies widely by climate, location, time of day, and day of year. Some environments can have very low noise levels, while others are extremely high. In some cases, damaged or defective equipment can also result in low or high noise levels making it difficult to assess an individual antenna is functioning correctly based on this metric alone.

Antenna pulses appear after the GPS hits on , on , and on. It can also be downloaded from

Combining data to assess station operation

Based on the information above, GPS hits and antenna pulses can be used together to make a general assessment on when stations were operational. Hourly summaries of GPS hits and antenna pulses can be combined to determine if a station collected any data during each hour.

the 'GPS' table from the Motus database downloaded through the Motus R Package
antenna noise here.
Information on assessing antenna equipment can be found here.
the 'pulseCounts' table from the Motus database downloaded through the Motus R Package.
deployment timeline
deployment timelines
receiver timelines
the data dashboard
deployment timelines
receiver timelines
the data dashboard