Automated radio telemetry uses receivers that automatically record signals from radio transmitters. It is used in a wide variety of ecological applications particularly for tracking migration of small animals, or determining fine scale temporal information about movement or behaviour. It is particularly well suited for studies of aquatic organisms and small flying animals.

Collaborative automated radio telemetry uses coordinated arrays of automated stations that are all monitoring the same frequency to detect tagged animals over broader spatial scales, and maximize the use of equipment operated by many researchers that traditionally may have not had the opportunity to collaborate. Tagged animals are detected on their local array, as well as any other station in the network. Automated radio telemetry harnesses the collective resources of many independent researchers into a much larger collaborative effort that expands the scale and scope of everyone’s work while maximizing scarce research and conservation dollars.

Motus is the world’s largest collaborative automated radio telemetry array. Motus is the central hub for detection data from more than 750 receiving stations as well as metadata from stations (e.g. location, deployment dates, height, antenna bearing) and tags (e.g. species, location and date deployed). Data from across the network is then provided to researchers and a condensed version shared with the public.

How to contribute to Motus

There are many ways you can get involved in Motus. Researchers can develop their own projects in order to use the technology and tools of this collaborative network. Landowners or institutions can also install and/or host receiving station on their properties, and anyone can support this project through philanthropic contributions to Birds Canada or other non-profit collaborators.

Become a collaborator

Motus relies on an assemblage of individuals, researchers, companies, government, non-government organizations, and academic institutions working together to maximize the efficacy of everyone’s effort and data. The central philosophy behind Motus is that we should all be working together, and all Motus collaborators agree to share their data, experiences, and successes with other collaborators and the public.

The value of the Motus network grows as the spatial coverage of stations and number of partners and collaborators increases. With continued expansion and support, Motus is providing a framework for global collaboration, and a coordinated approach to solving some of the most complex problems in movement biology and ecology.

If you are interested in contributing to Motus, you can view complete details in the Motus Collaboration Policy. Technical details about tags, stations and data analysis can be found in Motus Resources.

To become a Motus collaborator, you must first register with Motus. Once registered, you can create or join one or more projects.

When tracking wildlife with automated radio telemetry over vast distances, the challenge of deploying enough receivers to get detections grows exponentially. To remedy this, data can be shared between all researchers so that essentially everyone is sharing receivers. This greatly expands the potential for this technology, but it comes with the added responsibility of coordinating projects, detection data and metadata – that’s where Motus comes in.

What is Motus?

The Motus Wildlife Tracking System is an international collaborative network of researchers that use automated radio telemetry to simultaneously track hundreds of individuals of numerous species of birds, bats, and insects. The system enables a community of researchers, educators, organizations, and citizens to undertake impactful research and education on the ecology and conservation of migratory animals. When compared to other technologies, automated radio telemetry currently allows researchers to track the smallest animals possible, with high temporal and geographic precision, over great distances.

How does Motus work?

The philosophy behind Motus is that we’re all working together. At its core, Motus is community science. A community of researchers around the world conducting research on animals that are tracked by a network of coordinated receiving stations. These stations are maintained by a community of researchers, organizations, non-profits, governments, and individuals. In order for this concept to work, the system requires a centralized database and management system that all participants use. Most importantly, in order for your tags to be detected on any other station in the network, or for other project tags to be detected elsewhere, projects, receivers and tags need to be registered with, and have data processed by Motus. While any automated telemetry project can operate in isolation, operating as a Motus project combines the collective impact of local, regional, and even hemispheric projects into one massive collaborative effort that expands the scale and scope of everyone’s work and maximizes the use of scarce research dollars. It also makes data available and more useful for future projects, collaborative endeavors and large-scale meta analyses.

What does Motus cost?

It's FREE to register your project and receivers to the Motus network, contribute data from those receivers, and use the resources on the website. In order for transmitters to be detected by the network, they must be reregistered with Motus and are charged a nominal fee to support data processing and ongoing maintenance and development of the research software platform. See the collaboration policy and fee schedule for more information.

Data ownership and privacy

The collaborative nature of Motus relies on a certain level of transparency with respect to data. While basic project and tag summary information is made publicly available, researchers have the ability to customize data accessibility and keep their project and data private if necessary. See the collaboration policy for more information.

What does Motus provide?

Collaboration and community

• Coordinated global network of automated radio telemetry receivers. See Motus by the numbers.

• Become part of a global research and conservation community.

• Collaborators have full control over data access.

• Projects can be designed based on the placement of third-party stations.

• Tagging data from multiple projects can be utilized in large-scale studies.

• Communication, troubleshooting, and consultation from other researchers in the community, Motus staff and technology partners via the Motus discussion group.

Data archive and management

• One centralized data hub at Birds Canada National Data Centre

• Standardized data format across all projects

• Permanent archive of data

• Access to the research software platform data visualization and management tools

• Metadata management platform

• Combined data from multiple stations into one simple-to-use database accessible through R

• Facilitated import to Movebank to access their tools and services

Data access

• Data is available from all stations in the network as soon as it’s uploaded to motus.org

• Receiver and data management tools

• Automatic data streaming from the receiver to Motus.org for stations with internet connectivity

• Public access to station and tag summary data, tracks, and maps via motus.org.

Data Analysis and Tools

• All data is automatically packaged and available in real-time through the Motus R Package

• Opportunities to Join a community of scientists developing new code for data processing, modelling, and manipulation

• Motus Research Software Platform visualization tools

Technology

• Draws on community supported options for local-to-hemispheric tracking infrastructure

• Partnerships with multiple technology firms for receivers and tags across numerous cutting-edge technologies

• Open-source hardware and software solutions via sensorgnome.org

Motus is Advancing

Multi-disciplinary Science

• Movement, migration, and population ecology

• Animal behavior and physiology

• Environmental management

Conservation

• Population, survival, and species dynamics

• Stopover, site-based, and full life-cycle knowledge

• Informing use of flyways and landscapes

Education

• Undergraduate through postgraduate studies

• Open framework for development, code, and analysis sharing

• Grade 7-12 STEM curricula (science, technology, engineering, math)

• Public engagement and storytelling

• Visit Motus Education

Because Motus manages and shares data across numerous projects and jurisdictions, a Collaboration Policy has been developed to ensure that all researchers know what to expect when joining Motus. There is currently no formal agreement in place, but by registering tags or receivers with Motus, you are agreeing to the terms of the policy.

Motus has also developed a basic fee structure to help cover core data handling and management costs associated with the system. Fees are described within Section 3.5 Motus Data Services Fees of the Collaboration Policy.

Tag finder is a complex algorithm used to decode IDs of Lotek tags from the raw data collected by SensorGnomes and SensorStations. It was originally developed by John Brustowski and Phil Taylor at Acadia University.

This chapter is intended to provided an overview of how tag finder works and where issues may arise. For a complete, in depth look at the algorithm and its code, see the find_tags github repository.

Overview

Tag finder takes in a series of time-stamped radio pulses and decodes them by matching them to a list of known Motus Tag IDs. A Lotek tag ID consists of a "burst" of four pulses which are precisely spaced apart such that every tag ID has three unique pulse gaps. Motus extends these IDs by using the interval between bursts as a fourth unique pulse gap. Tag finder is capable of decoding IDs of tags that have overlapping bursts using a technique described below.

How it works

Tag finder uses a computer science concept called Deterministic Finite Automata (DFAs) to associate a series of time-stamped pulses with known Motus Tag IDs. For any given set of pulses, it looks at the first pulse gap and creates a list of 'tag candidates' which the gap could be associated with. It then continues to the next pulse gaps one at a time, narrowing down the list of candidates until just one candidate is left - those pulses are then 'reserved' for that tag and cannot be associated with another tag. During this process, many pulses will be skipped if the gaps don't match any known tag IDs. The first skipped pulse will become the starting point for the next DFA, making it possible to separate out pulses from overlapping bursts.

Tag finder must identify at least two bursts in order to associate pulses with a tag candidate, but often the second burst will be missed due to poor signal. To maximize the possibility of getting a Motus Tag ID, tag finder will continue searching for another burst which matches the candidate tag(s) for up to 20 skipped bursts.

The list of tag candidates is based on all Motus Tag IDs that known to be deployed when the pulses occurred. This means it's not possible for tag finder to identify tags if they aren't registered to Motus with a deployment.

Parameters

There are a series of parameters that tag finder uses to associate a pulse gap with a Motus Tag ID. It uses empirically-based cutoffs for associating pulses with a tag as well as parameters of the tag that were measured when it was first registered to Motus.

For pulses to be grouped together, they must share a similar signal strength, frequency offset, and the pulse gaps must match the expected pulse gaps of the tag within 2 milliseconds. Burst intervals are allowed to vary by up to 4 milliseconds and it will also increase this variation by 1 millisecond for every burst that is skipped.

See our documentation on the parameters for tag finder here.

What you will find in this guide

This guide covers various aspects of the Motus Wildlife Tracking System including;

• About Motus, how it works, and how to be involved.

• All about Motus projects and metadata management.

• Selection, installation, and maintenance of Motus Stations.

• Selection and deployment of Radio Tags.

What you won't find in this guide

• How to access and analyze detection data using the Motus R Package.

  • Please refer to the Motus R Book.

• How to use specific models of Motus receivers. These are located in separate guides by manufacturer:

  • SensorGnome User Guide

  • Sensorgnome V2 Guide

  • CTT SensorStation User Guide

  • Lotek SRX 800 User Guide

Additional Resources

Volunteers are an essential part of the Motus network and are needed in order to help researchers maintain stations and download data. If you are interested in assisting researchers by sponsoring or maintaining a station near you, find the owner of a Motus station near you using our receiver map and contact Motus for more information.

Individuals, researchers, or organizations can setup and maintain a station to contribute to the Motus network whether or not they choose to deploy tags on wildlife. As a collaborative automated radio telemetry network, Motus is strengthened by support and collaboration across the hemisphere from individuals or groups that are willing to commit time and resources to maintaining their own receiver infrastructure.

If you are interested in setting up and hosting a Motus receiver station, the guide below can provide you with important information to get you started. Full details on data sharing policies and registration fees can be found in the Motus Collaboration Policy, further details on project initiation and technical information on station setup can be found in the resources section.

Why reprocess receiver data

Detection data is regularly reprocessed (also referred to as "rerun") following the initial upload and processing. This is primarily required to account for changes in metadata. As described here, proper metadata management is essential for identifying tags, in particular Lotek tags.

Put simply, if a tag does not does have an active deployment at the time the receiver data was originally processed that covers the period of the detection, that tag will not be among the candidate tags that the tagfinder algorithm has at its disposal when attempting to match raw data with known tags. In other words, your tag will not be detected.

Sometimes even despite best efforts, tag metadata is either not present or not correct when detection data is first processed. This makes repeated reprocessing of receiver data a necessity.

There is no fixed schedule as to how often receivers are rerun, but typically it is within the first 1-2 months of first upload, then roughly every 3 months to 6 months after that, decreasing in frequency as more time has elapsed since when it was first recorded and processed

How to check the most recent rerun date

There are two methods of checking the recent rerun status, described in the tabs below.

Why detections can sometimes appear or change after reprocessing

Though receiver reprocessing is unavoidable given the constraints of the current technology, it can lead to some surprising results, primarily when detections that were previously seen disappear entirely, or are changed to different tags.

Detections don't appear after first upload but do appear after reprocessing

This is the most common and straightforward case. Usually it is a matter of researchers forgetting to update their tag metadata prior to uploading a station's data. It's also more likely to occur when deploying tags near internet-connected stations, as they often upload data before the updated metadata is present in the system.

This is the most common answer to the question of why no detections are showing up despite having tagged in the near vicinity of an active station.

Detections change to different tags after reprocessing

In this case, rather than there being no candidate tags whatsoever that might match the raw data, as in the previous case, there are tags with active deployments that are potential candidate tags. Due to the allowed tolerance of tag signal properties, sometimes a less suitable candidate tag is selected by tagfinder if the more suitable one is unavailable. Once the proper tag metadata has been updated and the receiver reprocessed, it will resolve to the correct tag.

Detections that did appear then later disappear

This is not directly related to receiver reprocessing, but worth describing here along with the other cases. This is when detections are later identified as false positives, either related to aliasing or a noise event, and are flagged in the database. Flagging them will remove them from all the the detection summaries on Motus.org, but not the complete data downloaded with the R package, where the runs and hits will be assigned the value of motusFilter == 1 . Read more about that here.

How do false detections occur

In Motus, there are multiple ways in which false detections can occur. The three main methods are:

• Environmental noise: this can be anthropogenic or natural (from space!).

• Bad metadata: researchers haven't entered deployment information for their tags so our system doesn't know they are deployed. Because there Detections of the tags are therefore interpreted as a different (false) tag.

• : a large number of tags (10+) are all deployed at the same location and time and their signals overlap. Their close physical proximity means the signals emitted by the tags appear very similar to the receiver, making it hard to tell them apart. This can result in the mixing of multiple tag signals which may be mis-interpreted as another tag that is not actually present.

How are false detections dealt with?

Public data has been processed using broad filters based on theoretical flight speeds, logical geographic/time sequences, and at least 3 consecutive tag bursts at a single station. Most tracks have not been inspected individually for accuracy. However, we do apply manual filters for known cases of false detections.

Motus R Book

Researchers inspect and filter their data based on .

Identifying False Detections

There are several methods we use to identify false positives, but for most the first indicator will be intuition. That is, the context of a detection can sometimes provide the most clues, or at least indicate that certain data should be further scrutinized. Typically, certain stations will be particularly susceptible to producing false positives which results in a cluster of detections by different animals at that location.

Examples of false positives in data

Tracks Map

Tracks are most obviously false when there are long distance East-West movements, or during the non-migratory period, North-South movements. Some false detections occur at certain stations multiple times, creating a back-and-forth movement which looks false. In other instances, the animal has merely moved out of range and is likely false – that is, unless the animal was tagged as part of a vagrant study (in which case we don't expect them to be in range!).

Detection timelines

Detection timelines are a very useful tool for determining when stations are functional as well as when they are experiencing a noise event. These show exactly when detections occur as well as the general level noise in the radio environment.

Detection timelines can also provide an indication as to whether a false detection has occurred as a result of environmental noise or whether it was caused by tag aliasing:

• Environmental noise will look like a spike in tag detections, where several tags that were never detected before are all detected at the same moment and then are usually never detected again. It is common for a noise event occur when no other tags are being detected, making them stand out.

• Tag aliasing will only occur when multiple other real tags are present and being detected. This is because aliasing is a result of a mis-interpreted tag signal. Aliasing usually looks like one to a few tags which are detected at the same time as other tags which are known to be present (i.e., were deployed nearby). Detections of aliased tags always occur less frequently than detections of real tags, but they can still sometimes be detected repeatedly over several days.

Reporting

For reporting, send us an email with a table (or a list) that includes the following information about each false detection:

• Tag deployment ID

• Station deployment ID

• Justification for removal

• Suspected cause of false detection.

• The date the false detection was found

• Observer name

• Any additional comments

Overview

There are multiple data sets available from Motus which are each processed differently based on the type of receiver they were collected from as well as the type of transmitter that is being listened for (Lotek or CTT). A diagram of how these data are processed can be seen in the .

After processing, data are stored in the Motus Database. Public dataset available on the Motus website have to help limit the number of false positives, while unfiltered data can be access through the . Some unfiltered data can also be viewed on the Motus website in the and the .

Lotek detection data

Lotek tags emit an OOK-modulated signal (see ) which is recorded as a collection of time-stamped "pulses" on SensorGnome and CTT SensorStation receivers. A large list of these pulses are then processed by the algorithm which essentially looks at the timing between individual pulses ("pulse intervals") and matches them to a list of known Lotek tag IDs. Lotek receivers do not record individual pulses, but actually decode the Lotek Tag IDs internally and record the timing and ID of the tag detection. At this time, the Motus is able to decode tag IDs using tag finder on Motus servers due to an existing NDA between Birds Canada and Lotek, but otherwise this codeset is kept confidential. This is why on-board decoding of Lotek tag IDs can only occur on Lotek receivers at this time.

CTT detection data

CTT Tags emit an binary FSK-modulated signal (see ) which is recorded as the tag's ID, consisting of 8 hexidecimal characters (E.g.; "1A2B3C4D"). These data are processed on CTT's server to remove false detections using a reference list of known IDs which includes all tag IDs that have been manufactured. The tag finder algorithm is not required to decode the IDs of CTT tags because the hexidecimal ID can be directly decoded from the binary FSK signal without the need of mapping it to a list of known Tag IDs. Decoding is handled by the 434 MHz radios in the Motus receiver before it's stored on the computer.

Tracks

How public track data is calculated

Tracks are based on the shortest possible paths between detections, and thus are unlikely to represent the true path unless the estimated speed is fairly high. Distance between detections is based on the location of the receivers, which doesn't take into account the detection ranges of the antennas (as much as 20km when conditions are good). Therefore, the estimated distance between detections may be too large by as much as 40km (when two unobstructed antennas are pointed directly at each other), and thus when the receivers are less than 100km apart the estimated minimum speed may be unrealistically high. Speed estimates for receivers more than 100km apart seem to be reasonably accurate. False detections happen sometimes (especially when equipment is faulty, a receiver is near a radio source, or a tag pulse pattern is ambiguous), but rarely last even a second. Very short detections can be filtered out (or not) in the settings.

Data Processing Pipeline

Data are processed differently depending on the type of receiver and tag. Data received from Lotek tags are processed on the Motus server where it matches the ID and burst intervals to known tags within the system. Similarly, CTT tag data are processed on CTT's servers where it can be validated against its own list of tag IDs which have been manufactured. Due to these differences in data processing, data uploaded to Motus - either manual or automated - need to be routed to the correct server based on its contents.

2. Create your Project: Once registered with Motus you can join an existing project, or if registered as a Principal Investigator, you can create your own project. Manage landowners, users, data access levels, and project descriptions.

3. Enter and update important metadata about your receiver and station configuration, and upload data.

4. and/or

5. Enter and update important metadata about your tags and animals.

6. Use our online resources to explore your data, or download and begin to analyze your data using the .

What is Motus?

The (hereafter Motus: Latin for movement or motion) is an international collaborative research network that uses cooperative automated radio telemetry to track small flying organisms (birds, bats, and insects). The system enables the conservation science community to undertake cost-effective, impactful research and education on the ecology and conservation of hundreds of species simultaneously. Motus is a program of Birds Canada in collaboration with a wide network of researchers and organizations. Motus collaborators deploy small radio transmitters that are detected by Motus stations placed at strategic locations throughout the landscape which can detect tags up to 20 km away. Depending on the configuration of a receiver array, tags can be monitored continuously, or as they occupy space monitored by other stations in the landscape. From the outset the philosophy behind Motus has been that we should all be working together. Motus harnesses the collective power of individuals and organizations into a coordinated coalition that expands the scale and amplifies the impact of everyone’s work, and optimizes scarce research and conservation dollars.

Motus collaborators currently maintain more than . More than have deployed over 30,000 tags on more than 250 species of birds, bats, and insects. These data have contributed to covering a wide range of disciplines such as breeding and post-breeding dispersal, stopover and migration behavior, habitat use, and overwintering ecology. Data collected by Motus is revolutionizing our understanding of migratory animals and is being used in conservation planning for species and sites, status assessments and recovery plans for species at risk, environmental assessment and mitigation planning for development projects, and contributing to numerous continental conservation efforts.

How to get involved in station network development

Tagged animals can only be detected if they pass within range of a Motus station, so ensuring that stations are strategically positioned across the landscape is important to allow for tracking throughout as much of their life cycle as possible.

There are two primary ways to participate in building and maintaining the Motus station network:

2. Support a Motus Station

1) Host a Station

Each new station increases the area across which tagged animals can be tracked. However, not every location is a great candidate for a Motus station.

What makes a site suitable for a Motus station?

The most important factor is that the antennas have an unobstructed view in the direction they are facing. For this reason, the highest point on the surrounding landscape (within 5-10 km) is usually preferred. This may be a hill or other prominent feature, shoreline, a station attached to an existing building, or a standalone station that exceeds the height of any nearby trees or features.

Along with the strictly necessary, there are some other features that make some sites better than others:

• Unobstructed line-of-sight for the antennas is essential

• AC power adds reliability and reduces cost compared to solar and battery setup

• Internet (WiFi or hard wired) allows regular data uploads and quicker identification of issues

• Existing structures to attach the antennas to (like an unused TV or communications tower) can lower the cost of installation and increase long term durability

• Ease of access keeps time and travel costs down for installation and maintenance

Examples of stations

Motus stations come in many shapes and sizes, but at minimum each one consists of a radio receiver, one or more antennas, and a power supply. The exact configuration depends on the specific site, but a handful of examples are pictured below.

PHOTOS TO BE ADDED

Commitment, Liability, and Cost

When installing a new station, we prefer to aim for at least a 5-10-year commitment from the landowner to host the station. However, these agreements are non-binding, and if a landowner requests the station be removed prior to this time, this can be accommodated.

Birds Canada holds $5 million public liability insurance to cover staff and volunteers during the installation of the equipment, as well as all public and private landowners from liability created by installed equipment throughout the duration of the project. If embarking on an independent station installation you will want to confirm your own insurance requirements. In most cases the costs for station equipment, installation, and maintenance is covered by the Motus collaborator requesting to setup the station. There are no annual fees to station hosts and landowners.

Benefits to the Host

• Supporting one of the largest collaborative migratory animal conservation science and research initiatives in the world

• Access to visualizations of animal movement data collected from yours and other stations

• Educational opportunities using the infrastructure, data, or technology

• Opportunity to actively participate in ongoing research and monitoring projects

• Opportunities for mutual outreach, promotion and community engagement

• Conversation starter/piece and decorative landscape art

2) Support a Motus Station

One of the largest obstacles to station setup and maintenance is funding. Even if a perfect site is available, a lack of suitable funding can prevent a station from coming together.

What does a station cost?

The cost of a station varies widely depending on the configuration of the station, number of antennas, needs for power, ease of access of the station, etc. We generally offer an estimate of roughly $7.5k as a ballpark for the purchase, installation, and maintenance of a “typical” station. In some cases, where existing infrastructure is already in place and can be used, the cost can be significantly lower. For installations in remote areas, or which require specialized contactors to install, the cost could be higher. See Table 1. for an estimate of station costs.

Table 1. Estimates of Motus station equipment, setup, and maintenance costs.

* Procurement, setup, and annual maintenance costs can vary substantially depending on the specifics of each installation.

What next?

Motus provides:

• The widest variety of animals to be monitored over the greatest distance with relatively high geographic precision, and incredible temporal precision

• Centralized, public data portal for automated radio telemetry projects globally

• Metadata management services – project, station and tag metadata management system.

• Data management services – access, clean, and explore your data through the Motus R package.

• Explore Data – see what’s been detected at your and other stations around the world.

• Shared local-to-hemispheric tracking infrastructure.

• Innovative, affordable, open-source hardware and software.

• Compatibility across numerous cutting-edge technology providers.

• A large international collaborative community. Scientific altruism at its best.

Motus is helping to advance:

• Animal and Migration Science:

  • Open framework for development, code, and analysis sharing

  • Movement, migration, and population ecology

  • Animal behavior and physiology

  • Environmental impact assessment and management

• Conservation:

  • Populations, survival, and species dynamics

  • Stopover, site-based, and full life-cycle knowledge

  • Improving knowledge of how animals use flyways and landscapes

• Education and Training:

  • Undergraduate through postgraduate studies

  • Grade X-12 STEM curriculum links

  • Public engagement and storytelling.

Overview

Some filters are applied to Motus data that can be accessed by the public in order to limit the number of false detections that are presented. These filters are also available to collaborators who download their data from the . This chapter goes over each of these filters and how they are applied.

Motus filter

This filter was the first one to be applied to the public dataset and is the most generalised of the filters. It uses cutoffs for a set of parameters based on an empirical examination of the data. These include:

• For 'noisy' sites, minimum of 5 consecutive detections

• For 'quiet' sites, minimum of 4 consecutive detections

Manual filters

There are several edge-cases where the above Motus filter above does not remove false detections which can be problematic to present to the public. Manual filters use tag deployment ID and station ID pairs to remove these bad detections. That is, for every entry in the filter it will remove all detections of the tag deployment from that station.

Station Filters

Certain stations are especially problematic, usually because there are large numbers of tags deployed nearby the station which are all present at once (see ), but it can also be due to excessively noisy sites producing false detections (see ). They produce false detections regularly enough that we can't keep up with the manual filters.To remedy this, certain stations are flagged as 'problematic' and all detections of non-local tags are removed from public view on the Motus Dashboard only. Non-local tags are considered to be any tag that was deployed further than 10 km from the station.

A Motus project contains all the transmitters and stations used for your studies. It helps you organise your projects metadata and access permissions.

Creating an account

Account types

• Principal Investigator: usually the lead researcher. This account type is required if you will be within Motus. Your account will need to be approved by an administrator if you select this type.

• Collaborator: all accounts that don't require creating a new project. You will need to request to after creating your account.

Join a project

Joining a Motus project requires a member of that project to If you don't know who to contact to gain permission, follow these steps:

1. Log in to Motus.

2. Go to and click on the name of the project that you wish to join.

3. Click on the name of the researcher under Project contact to find their contact information. Keep in mind you must be logged in to see this informaton.

4. Clicking on any name under the project will also provide you with the contact information for that individual, should you need it.

Add a new project

3. Fill in the form as best as possible. A description of the fields is below:

   • Project name: the full name of the project. Please keep this tidy yet descriptive.

   • Short name: this is a sort of 'code' name that is prefixed to tag detections in data summary plots.

   • Short description: a brief description of the project, to be visible in project overviews.

   • Description: a detailed description of the project which will be visible in the projects public profile.

4. Click on Save to finish creating the project.

Now that you've created a project, you can now move on to manage your stations or manage your tags!

Motus supports two types of uniquely coded radio transmitters: NanoTags™ manufactured by Lotek Wireless Inc, operating on frequencies 166.380 MHz (Western Hemisphere), 150.100 MHz (Europe), and 151.500 MHz (Australia), and LifeTag™ and PowerTags™ manufactured by Cellular Tracking Technologies (CTT) operating on 434 MHz globally. The two tags use fundamentally different transmission and coding systems.

Tags range in size from ~0.2 g to ~2.6 g, and lifespans vary from 20 days to infinity, depending on the model. It is important to check the Motus Receiver Map to confirm which frequency other stations/antennas are operating on throughout the network. When communicating with Lotek or CTT, be sure to explicitly state that you want your tags/system to be compatible with Motus. Be sure to review our Motus Tag Guide in detail. Please contact Motus, or the tag providers above for more information.

Steps

1. Register a Motus user. Collaborators wishing to deploy tags must first register with Motus.

2. Join or create a project. A Motus project is required before purchasing and registering Motus tags. In order for tags to be detected using the Motus network, they must be registered to a Motus project.

3. Purchase and Register Tags: When ordering tags, provide the manufacturer with your Motus project ID.

4. Register an anticipated tag deployment: this is a required for battery-powered tags to be detected by our system. You can add multiple tag deployments by using our Tag Deployment Bulk Editor. For more information about tag metadata and how deployments are used to detect tags, see Tag Metadata. Data from these tags will not be processed without a deployment.

5. Deploy tags. Several techniques exist to deploy Motus tags and more are being developed and tested. This document provides instructions for affixing tags to a variety of species. If your group uses different methods, or have any additional information, please contact Motus.

The technology behind Motus is relatively inexpensive and highly customizable. The sections below provide resources for building and deploying receiving stations. For more information about station deployment, see our Motus Station Guide.

For assistance with the setup of your project please see our Discussion Group, Troubleshooting Guide or contact us.

Contact Motus for a list of potential suppliers near you.

Steps

1. Register a Motus user. Collaborators wishing to deploy tags must first register with Motus.

2. Join or create a project. In order to manage stations in the Motus network, a project must be created.

3. Purchase equipment. Make sure you get the right equipment for the types of tags you wish to detect

4. Install the station.

5. Register the station.

6. Upload data to Motus. Depending on the location and type of receiver, it may be possible to upload data to Motus automatically.

All tags used with Motus must first be registered before any data can be acquired from Motus stations.

Automatic Registrations

With some exceptions, all tags purchased from Lotek or CTT are registered automatically to a Motus project upon shipment. This means you must provide the tag manufacturer with your Motus project ID when ordering your tags.

1. Register with Motus

2. Create or join a project

3. Provide the manufacturer (CTT or Lotek) with your project ID when purchasing tags.

Manual Registrations

In some specific instances, it may be necessary for you to register your tags manually. Only do this if you have been instructed by Motus.

1. Register with Motus

2. Register your tags: Instructions on registering tags can be found here. To register a tag, you need to make a short recording of its output using a funcubedongle attached to a PC. Tag Registration Kits can be purchased from Motus. Each kit includes a funcube, whip antenna, and tag activator. We strongly encourage you to test and register all tags immediately after receiving them to ensure they’re ready for deployment. Always check your Manage Tags page after registration to ensure they have all been uploaded correctly.

3. Upload tag registrations: Send us your completed tag registrations from step 2 here using your Motus login information.

Tag Fees

Your project will be invoiced based on the number of tags registered following the Motus Collaboration Policy and Fee Schedule.

Please contact us if you have any questions regarding tag fees.

A Motus station consists of three main components:

• Receiver: this is the computer which records and stores the radio data

• Antennas: there are several types of antenna designs. They are 'tuned' to listen to a narrow range of frequencies. Each antenna gets its own coaxial cable and depending on the receiver type and listening frequency, it's own 'dongle', or USB devices which listen to a specified frequency range (i.e., software defined radio).

• Power supply: this provides power to the receiver. Most off-grid stations us solar power, but AC power is most reliable. The number one reason for a station to malfunction is a power failure.

Adding a new collaborator to a project

1. Go to Manage Collaborators, Institutions, and Citations

2. Below the table of collaborators, use the input field under Add new collaborators to search for the collaborator's name, username or email.

3. In the search results, click on the name of the collaborator you wish to add to your project.

Citations

See Project Citations.

Project collaborator permissions

• Go to Manage Collaborators, Institutions, and Citations

• Find the user you wish to revise in the collaborators table and then use the select options to modify their permissions. Permissions have three tiers -- 'update' (view and edit), 'read' (view only), and 'none' -- and include the following categories:

• Project: Anything related to project metadata (description, billing contact, etc.) and collaborator/citation management.

• Tags: tag deployment metadata.

• Stations: anything relating to station management including station deployment and landowner information.

• Data: access to detection data (via Motus R package).

Removing a collaborator from a project

1. Go to Manage Collaborators, Institutions, and Citations

Not all stations are created equal. Some will primarily achieve local objectives, others are part of regional networks, and others strategically placed at migration, or movement hotspots serve the collective needs of the entire network. At the end of the day, all stations work together to make up the Motus network and provide data to far more projects than your own. Motus is the ultimate, hands-on, community science project.

Site Selection

Before deploying any stations, you need to know what the primary purpose of the station is. What works best for your region based on migratory flyways, topography and local infrastructure available, foraging locations, your goals, funding, the location of nearby stations.

Ideally, adjacent stations will complement one another; that is, they operate on similar frequencies and have antennas which point towards one another to provide detections of tagged animals as they pass between the stations. Multiple receivers can be employed to build a receiver ‘fence’ to detect any animals that may pass over a geographic area. Examples of these can be seen in the North-eastern US and along the North Sea of Europe. In Ontario, where many more stations are available, there is a grid of stations (or series of fences) to allow for better spatial resolution of movements. On study sites like Sable Island and Bon Portage Islands in Nova Scotia very small grids have been used to study local movements.

When selecting a site, it’s important to consider how the landscape features will affect the range of your antennas. Generally, higher stations have a greater range and detection probability of passing animals, but have a more limited probability of detecting local movements (depending on the type of antenna that is attached). In most instances, stations should be placed in the highest elevation possible within the area of interest, ensuring there is a clear line of sight in each direction you wish to point the antennas. It’s also important to ensure there aren’t any obstructions immediately behind the antennas (within a few meters), especially metal surfaces like roofing.

CTT Nodes work in a similar fashion to other Motus stations, but at a much smaller scale. These devices are best suited for fine-scale studies. Read more about CTT Nodes here: CTT Nodes

Antenna Interference

Antennas can receive interference if placed too close to metal objects or other antennas, or sources of electromagnetic noise (even air conditioners, generators, lawn mowers). Depending on frequency and location, radio interference from third-party broadcasters and cellular can also be problematic. Some online tools exist to locate licensed radio broadcasters by location (click here for Canadian stations).

Testing for antenna interference

One can conduct tests at a site prior to station setup, but none have been well tested. Below are some guidelines which may help identify noisy sites.

Measuring the noise floor

1. Download SDR Console from their website

2. Plug the FUNcube dongle into your computer and run the SDR Console software.

3. Select the FUNcube dongle from the list of devices and tune it to the desired frequency.

4. Plug in an antenna and take measurements in all directions at or near the height where the antennas will be when the station is installed.

5. If you measure anything above XX dB, there may be a problematic noise source in that direction.

Measuring with a Motus receiver

1. Power on your receiver and plug in an antenna.

2. Point the antenna all direction at or near the height where the antennas will be when the station is installed, moving in a circle over a 5-minute period.

3. Download the data you just collected from your Motus receiver.

4. Open R and run the script provided here: [ LINK TO A SCRIPT ]

5. If you're given a probability of less than 5%, you're good to go!

Institutions are organisations that are credited for their involvement with the Motus project as a lead, partner, or funder.

Add a new institution

1. Go to Manage Collaborators, Institutions, and Citations

2. Below the table of collaborators there is a table with the header 'Affiliated Institutions'. This is usually empty for new projects.

3. Use the dropdown menu below the table to select the institution you wish to add.

4. Select one or more 'institution type'.

5. Click on 'Affiliate this institution with this project' to add it to the table.

Removing an institution

1. Go to Manage Collaborators, Institutions, and Citations

2. Below the table of collaborators there is a table with the header 'Affiliated Institutions'.

3. In the second column of the table, click the red 'X' in the row that you want to delete.

This section pertains to the management of station metadata: i.e., the registration of stations and their deployments. To learn more about station equipment and how to deploy them, see our chapter on stations:

In this chapter you will find:

• Definition of Stations, Station Deployments, and Receivers

• How to Manage Stations

Definitions

Stations

A Motus station is a single location where Motus receiver and antenna equipment is or has been deployed. A station ties together all the different deployments (i.e., 'configurations') that a location might have had. For instance, if a new antenna was added to a station that was already deployed or if that station had a new receiver installed, it will all be recorded under the same location and name. Not only does this help us better organise the database, it also makes metadata management much more efficient and intuitive for Motus collaborators.

Station deployment

A station deployment is a single configuration of a station which includes dates of deployment (start and end), receiver ID, antenna information (type, direction, height), and the antenna mounting structure (building, pop-up tower, etc.).

Receivers

The physical computer that antennas plug into and collects tag detection data. Receivers are linked to stations with station deployments.

What's new in the December 2021 Update?

If you're already familiar with Motus this won’t be much of a change for you. Most importantly, your R scripts won’t need to change since we're keeping the ‘site’ variables for the time being.

Prior to December 2021, 'sites' were used as a general term with no restriction on geographic area or number of active Motus deployments. The December 2021 update converts this into a single 'station' which can only be in one location (unless mobile). Each station can only have a single active deployment at a time. In addition, 'receiver deployments' are now 'station deployments'. The coordinates and landowner information will also be associated with stations rather than deployments.

Previously, most Motus collaborators used sites for the same purpose we intend to use stations anyways and landowners are already associated with sites. For this reason, we do not anticipate any major disruptions as a result of this change.

Motus R Package Update

In the Motus R package, we will keep all the previous variables, but we will also introducing 2 new variables (stationID and stationName). This means you need to update your R package to version 4.0 to download new data. The variables siteName and siteID may be deprecated in a future release of the Motus R Package.

Why stations?

The Motus database was first organised from the perspective of data processing. That is, to store detections based on the serial number of the computer (i.e., "receiver") that collected those data. However, it was also important to keep track of different station configurations, hence "receiver deployments" were born. However, whenever a receiver was switched between two locations it always presented a bit of a problem to link the deployments of a single location together. Previously, researchers would have to use the station's name to link together data from multiple receivers which could be frustrating, especially when names were not consistent between deployments or when two locations had similar names. As Motus has grown, receiver management has become more and more cumbersome making it clear we would need to introduce a new system of organisation at the station level.

The concept of ‘sites’ was introduced back in 2018 as a way for collaborators to group together the deployments for any number of locations. However, we found most collaborators were using the feature to identify a single location. At the same time, new data explorations tool require a clearer way to link together Motus receiver deployments at a single location. By introducing stations, we're now able to string together deployments across multiple receivers based on where they were deployed in a consistent manner.

Managing Stations

Every location where a Motus receiver is deployed needs to be recorded as a 'station' in the database.

This section covers the following topics:

• View project stations

• Filter stations

• View station deployments

• Add a new station

• Modify a station

• Terminate a deployment

• Add a new deployment

The video below covers all topics in this section:

View project stations

To view a map or table of stations associated with your project(s), go to Manage Data > Manage Stations.

You can toggle your view between a map and table by clicking on the tabs above the map/table.

Filter stations

By default, only active stations will be displayed. To view inactive stations or all stations together, click on the appropriate link above the table or map.

You can also filter stations by name or ID using the text input above the map.

View station deployments

Using the map, you can click on any station to see it's deployments. When viewing a table, click on a row to see it's deployments.

After clicking on a station, its details will appear in the panel on the right. This includes details about the station (status, location, and landowner) as well as the current and past deployments.

Add a new station

Click on the button labelled 'Add a new station'. This will open a dialog box with the following required fields:

1. Name: the name of the station. It's most helpful if this based on a local name.

2. Prospective start date: if the station is or was already deployed, enter a current or past date. If the station hasn't yet been deployed, enter the date you estimate to have it installed. If you do not have active plans to deploy a station here, leave this field blank.

3. Location: drag the pin around on the map to specify the location of this station, or use the latitude/longitude field below the map. Mobile stations should have their location as the start/end point of their 'typical' track.

4. Comments: this is helpful for entering access notes or if the stations is not yet installed you may describe the plans to install and the location here.

5. Landowners: you may select one or more landowner in this list. If the landowner is not present in the list, click the button labelled 'Manage your project landowners' to add a new one.

Modify a station

To modify a station, first select a station from the map or table and then click on 'Modify properties' from the panel on the right. See Add a new station for information about the options present here.

Terminate a deployment

With a station selected, click on the button labelled 'Terminate this deployment' in the right panel just above the deployment history.

You will be asked to provide the date and time that the deployment was terminated.

Add a deployment

Step 1: Click on 'Create a new deployment'

With a station selected, click on the button labelled 'Create a new deployment' in the right panel just above the deployment history.

Step 2: Enter start date

You will be presented with a dialog box asking for the deployment start date and time as well as a couple check boxes which allow you to choose whether to copy metadata from the previous deployment.

Step 3: Select a receiver

If you choose to select a new receiver (by unchecking the box labelled 'Use most recent receiver' in previous step), you will be presented with a table of all receivers registered to the project.

To select a receiver, click on the button 'Deploy this receiver' in the row corresponding to the receiver serial number. This button will not be visible on rows with receivers that are actively deployed.

You can click on a row to view further details about the receiver, such as its deployment history.

Click on 'Add a receiver' above the table to add a new receiver if it's not present.

Step 4: Enter deployment configuration

Regardless of whether you have a new antenna configuration, it is helpful to enter notes at this step using the provided text area.

If you are entering a new antenna configuration, you will also need to select the mounting structure (i.e. "type").

To enter antenna information, use the form at the bottom of the page and enter antennas one row at a time. The following columns are required:

• Dongle type: this is the radio device plugged into USB ports on certain receivers. There is one for each antenna. If you are using built-in 434 MHz radios on the CTT SensorStation, please select "Integrated (CTT SensorStation). If you are using a Lotek SRX- series receiver, please select "Integrated (Lotek SRX)".

• Port: this is either the USB or radio port that the antenna is plugged in to. This is very important to keep accurate since it will be used to correlate antenna directions to tag hits. Keep in mind that for CTT SensorStations, the built-in 434 MHz radios are labelled with the "L" prefix.

• Frequency: the antenna frequency. This is usually selected for you.

• Type: the antenna type. This is helpful for keeping track of antenna ranges as well as differences between equipment manufactures.

• Magnetic OR true bearing: the direction the antenna is facing. We tend to recommend magnetic bearing since not all compasses show declination. A phone compass typically displays the magentic declination unless otherwise specified. This field can be blank for antennas pointing vertically (e.g.; omni antennas).

• Angle: this is only required for non-horizontal antennas (e.g.; omni antennas). This option can be found under the 'advanced antenna properties' tab.

After entering your antenna information, you can verify the directions are correct by clicking on the button labelled 'View antenna map,' located just below the antenna table.

Step 5: Click 'Save and exit'

Once you are finished entering data, verify all the information is accurate and then click 'Save' or 'Save and exit'. You're done!

Manage Data Access Permissions

You can manage data access permissions for your project using the options found in Manage Project at the bottom of the page. This will affect how the public sees your data. Regardless of the permissions you set, each time data from your project are downloaded it is logged in your Data Access Log.

Data Access Log

Accessed from the Manage Data landing page, the data access log includes an entry for each time data from the project was downloaded. This includes a date/time of download and the user who downloaded these data.

Citations ensure accurate acknowledgement of an individual’s or organization’s role in a project. Citations are to be used wherever project summary data is reproduced, used in a collaborative research project, presentation, or website.

Citation Format

Citations can be formatted based on institutions or collaborators listed in the project. By default, the format will be based on the project's institutions, but if none are listed it will be based on the projects collaborators.

• To edit your project's institutions, see Institutions

• To edit your project's collaborators, see Collaborators

• To edit your project's citation format, go to Manage Collaborators, Institutions, and Citations and scroll to the bottom of the page.

Institution Citations

To select which institutions appear in your project citations and in which order:

1. Go to Manage Collaborators, Institutions, and Citations

2. In the Affiliated Institutions table below the collaborators table, use the input fields in the 'Rank in citations' column to rank the order in which names are to appear, beginning with the number 1.

3. Leave the field blank to exclude collaborators from the citation.

4. Once finished, click the 'Update the institution citation rank' button.

Collaborator Citations

To select which collaborators appear in your project citations and in which order:

1. Go to Manage Collaborators, Institutions, and Citations

2. In the collaborators table at the top of the page, use the input fields in the 'Rank in citations' column to rank the order in which names are to appear, beginning with the number 1.

3. Leave the field blank to exclude collaborators from the citation.

4. Once finished, click the 'Save changes' or 'Save and exit' button.

This section pertains to the management of tag metadata: i.e., the registration of tags and their deployments. To learn more about tags models and how to deploy them, see our chapter on tags:

In this chapter you will find:

• Definition of Tags and Tag Deployments

• How to Manage Tags

• Tag Registration

• Tag Metadata

Definitions

Tags

Tags are the individual radio transmitters compatible with Motus which are manufactured by either CTT or Lotek. They each have a digitally encoded ID (manufacturer ID), a burst rate (a.k.a., 'burst interval' or 'period'), and a model.

Tag deployments

A deployment is considered to be each instance when a tag was attached to animal and then released. Most tags are never recovered therefore most tags have only one deployment. Tag deployments record all the information regarding the animal that it was attached to, including: date/time of release, location of deployment, species, age, sex, weight, and any other metrics that can be provided.

Managing Tags

Every time a Motus tag is deployed, this needs to be recorded in our database, otherwise there may be missing detections. This section covers the following topics:

• Tag Registration

• Tag Deployments

  • Anticipated deployments

  • Test deployments

  • Tag Deployment Bulk Editor

Tag Registration

All tags are automatically registered to your Motus project before shipment, regardless of the manufacturer (CTT or Lotek). However, you must tell the manufacturer the Motus project ID for them to register the tag to the correct project. For more information, see Tag Registration.

Tag Deployments

A deployment is a single instance where a tag was attached to an animal (or was used in a "tag test"). The deployment begins when the animal is released. The deployment ends either: automatically (Motus calculates when the tag is expected to expire based on the tag model); or manually (when a collaborator recovers the tag from the animal).

Deployments are a necessary way for Motus to efficiently search for tag IDs within radio data. Without tag deployments, data will be missing.

Anticipated deployments

While tag deployments are necessary for detections to occur, it is impractical to register deployments immediately after each one is deployed. Anticipated deployments are essentially placeholders for real deployments and begin on the earliest date which tags are expected to be deployed.

Test deployments

Tags can be used to test whether a receiver or specific antennas are functioning as expected. However, we don't want these data to be included in analyses of animal movements, nor do we want them presented to the public since it can be confusing. To flag these deployments as tests, check the box reading 'make this a test deployment' while registering your tag deployment and leave the 'Species' field blank.

Tag deployment bulk editor

Multiple tag deployments can be registered and/or modified at once using the tag deployment bulk editor. This can be found by clicking on "Upload tag deployments" under Tag Management. Follow the instructions on the page to upload tag deployments.

Power Sources

Receivers can be powered by either AC or DC. AC power supplied by mains should be used whenever possible as it is generally a more reliable and cheaper power supply than DC. DC supplies usually come in the form of Deep Cycle batteries and require regular charging via solar or another method to maintain power. Also keep in mind that since DC typically requires a solar panel and battery it is a more attractive target for thieves.

AC Supply

If using mains AC power from a typical wall outlet, ensure you use a good quality power adaptor that is rated for the mains power of that region (e.g.: North America is 120 Vrms @ 60 Hz; South America is , 115-230 Vrms @ 50 or 60 Hz). A good quality adaptor can tolerate this variation in mains voltage which makes them more versatile for projects across multiple countries. A poor quality adaptor will produce an unstable voltage which can damage a receiver or not produce enough power to keep it operational. You may also want to connect your station through a proper surge protector.

The type of adaptor required will depend on the type of receiver being used. For CTT SensorStations and Lotek SRX receivers, these power supplies are usually included with the receiver. SensorGnomes will also be shipped with an AC power supply when ordered through Compudata or RFS Scientific.

If you do not have a power adaptor for your SensorGnome receiver, you can use a standard USB power supply for your phone (“fast charger” or minimum of 2.5 Amps) with a USB cable. For CTT or Lotek receivers, contact your supplier to purchase an adaptor.

If mains power is unreliable and 24/7 coverage is needed, then you may wish wish to connect your station through a battery powered backup power supply.

DC Supply

Powering electronics directly from DC is more complicated since there is no single setup for all stations. Instead, the type and amount of power required will depend largely on region and available resources. In order for a station to be compatible with a DC power supply, it must have a method for converting the voltage of a battery - usually 12 volts - to something the receiver can handle, which ranges from 5 to 18 volts, depending on the model.

• CTT SensorStations have built-in voltage converters, allowing them to accept a direct connection to the battery; however, in practice NEVER connect your receiver directly to the battery without a to protect your battery.

• SensorGnomes require a DC buck converter to lower the voltage down to 5 volts. This component is standard when purchasing from Compudata. Buck converters are only provided in SensorGnomes if requested by RFS Scientific.

• Contact Lotek or see your receivers user manual for more information on SRX series receivers.

Battery

Type

Lead-acid batteries are based on very old technology, but still provide the cheapest, non-volatile power storage for electronics. Lithium-based batteries offer the highest energy density of any commercially available battery, yet they are far more expensive relative to the power they store. In addition, Lithium-based batteries are typically far more volatile, risking chemical spills and fire if they are charged/discharged too quickly, if their temperature is too high or if they are punctured. For these reasons we do not recommend Lithium-based batteries unless space and weight is very limited. Since lithium-based batteries are used so rarely in the Motus network, they will not be discussed further here.

Most people refer to 12-volt lead-acid batteries as “car batteries,” but in this instance you might get the wrong type if that’s what you ask for. This is because car batteries are not designed to be discharged over long periods of time and require constant top-ups, such as from a car’s alternator. In a Motus station, batteries must be able to go down to voltages as low as 10-11 volts each night without losing much capacity - this would ruin the typical car battery in no time!

This is why we use deep-cycle batteries which allow a deep discharge during each charging cycle. Most deep-cycle batteries that are readily available are marine grade (a.k.a.: “marine battery”) which are designed around offering high cranking amps to start up large boat motors, but this is not anything we need in a radio station. Nonetheless, in remote locations with nothing else available, a marine battery will do. While more expensive, specialize solar deep-cycle batteries are also available that are designed provide small amounts of power continuously and varying degress of recharging.

You may also notice there are flooded and sealed lead-acid (SLA) batteries that exist. This refers to whether the internal chemistry can offgas externally. Flooded lead-acid batteries are well known for producing highly flammable hydrogen gas and can be extremely hazardous if not stored in a well-ventilated area. We usually store batteries in a closed tupperware bin which increases the potential of this hazard which is why we recommend SLA batteries. Even so, batteries should be handled with care so as to not puncture the battery casing, potentially allowing the slow release of hydrogen gas over time.

We recommend the following batteries, depending on application:

Capacity

When shopping for batteries, we recommend a 50 Ah battery for day lengths greater than 12 hours and a 75 Ah for day lengths under 12 hours.

Cold weather

For cold weather conditions, we recommend self-heating Lithium iron phosphate batteries, however there are some risks involved with deploying this type of battery. While the chemistry is stable and unlikely to combust like typical Lithium-ion batteries, they will be damaged if they are charged when below 0 C (32 F). Self-heated batteries are rated to temperatures as low as -20 C and have protective circuits to prevent them from damaging themselves. Batteries can be charged at even lower temperatures if they are stored in an insulated box. More information about storage and use of Lithium iron phosphate batteries can be found in the PDF below.

Undervoltage Protection

We recommend Sunsaver charge controllers with low-voltage cut-off - minimum 10L (depends on size of solar panel), Specifically XXX, and any solar panel (minimum 90 watt).

Solar Power

Type

Just like batteries, choosing the right solar panel for your setup can be a daunting task considering the number and types of panels available, but usually your local wholesale retailer of solar panels can help you with picking one out. There are a few different types of solar panels, but the two main ones we deal with are monocrystalline and polycrystalline. The main difference between the two is that monocrystalline cells are on average more expensive, but provide more efficiency and have greater heat tolerance; however, performance appears to vary considerably by manufacturer. Panel efficiency is not necessarily important considering the relatively small panels that we use to begin with. Heat tolerance may be an important consideration in more southern latitudes; we recommend speaking to local suppliers for their recommendation. We generally recommend polycrystalline solar panels to save on costs.

Wattage

The amount of power your panel needs to produce depends on the amount of sun exposure you expect on the shortest day of the year. In Canada, 80 Watt panels have been effective for ¾ of the year, but do not produce enough for continuous operation in the winter. For continuous winter operation, we have been recommending at least 150 Watts by industry experts. In the summer, 50 Watt panels have been sufficient.

Charge Controller

Power Outages

The main issue is that if the power happens to cut out when the receiver is writing to its storage, it could corrupt the storage and prevent the receiver from ever booting back up.

AC Power

Some sites have AC power available, but there may be problematic power outages. To get around this, you will need an uninterruptible power supply -- or UPS. They come in various shapes and sizes, based on the device being used and the amount of power you intend on drawing.

A generic UPS is commonly available at local electronics stores as they are often used to protect databases and servers. The ratings of UPS can be difficult to interpret, so its important to look at the spec sheet to identify how long it lasts while under load. Usually, it's reported as the number of minutes under full and half load which can be used to calculated the length of time the receiver will last based on the expected load of the receiver. Motus receivers use very little power (usually less than 5 Watts) so you can expect it to last much longer than what is typically advertised.

The nice thing about getting a generic UPS is that nearly all of them also have surge protectors which is important when you have an unreliable AC power supply. However, it's a good idea to test any system if the battery capacity is an important factor in your purchasing decision.

Raspberry-pi based SensorGnomes can use a UPS HAT, but these systems have not been adequately tested so aren't recommended for regular deployments.

Solar Power

The Motus Network mostly consists of stationary automated radio telemetry stations which continuously record incoming radio pulses. Mobile stations also exist, either affixed to a moving vehicle, boat, or in a backpack on foot. Other receivers are used for manual tracking so that wildlife can be located in and observed in-person for more precise location data.

Automated Telemetry Receivers

There are three types of receivers compatible with Motus that can be purchased, or built yourself in some cases: Lotek Wireles Inc (SRX600, 800 and D-series receivers), CTT Sensorstation and Nodes, and the open-source SensorGnome.

Sensorgnomes can be purchased from or or built with the . Note these instructions are very outdated and require revision. New instructions will be posted in the near future.

(1) Price does not include cost of: Wi-Fi module; cellular module; data plans; case; power supply; bulkheads (1 required per antenna); or testing time.

(2) CTT charges $5/month base plus data costs for cellular data plans and an additional $5/month for station health reports. Contact CTT for more details.

Manual Telemetry Receivers

For manual telemetry, we need a portable receiver that can decode tag IDs in real time.

Metadata informs Motus when to look for tags in raw detection data, when tag codes can be reissued, helps ensure that the permanent data archive is accurate and complete, and makes data presentable to the public.

Required tag metadata

Tag registration

All tags used with Motus

Tag deployments

The table below outlines the minimum requirements for tag metadata to acquire detections from Motus.

Entering Metadata

Why metadata is so important

Metadata is a critical part of the Motus infrastructure. Not only does it inform our algorithms which search for tag detections on when to look for specific tags, it also helps make sense of data that are presented to the public. As the Motus community grows, the importance of accurate and up to date metadata grows exponentially.

How metadata is used to detect tags

To improve the performance and accuracy of tag finder, Motus only search for tags that are known to be active at any given time. To accomplish this, tag finder references a master list of all registered tags along with the dates when they were active (‘deployments’). Occasionally, some tag detections are missed because _tag finder _doesn't know that certain tags are active, usually because of missing or inaccurate metadata in our system.

How does Motus know when tags are active?

Most tags are deployed on animals and never seen again, so most tag deployments will have a start date, but no end date. This is the correct way to enter deployment metadata if a tag is not retrieved again after deployment as it allows our system to calculate the end date on its own. This end date is calculated as the predicted lifespan (provided to us by the manufacturer) plus an additional 50% to account for unusually long-lasting tags. This predicted lifespan is calculated based on the tag model number, so it’s important to ensure that information is correct as well. The examples below use a theoretical tag with a predicted lifespan of 60 days.

Default deployment date

In reality, it’s impractical to enter tag deployment metadata immediately upon releasing each animal, so we have built in a couple safe guards to help mitigate this issue. The first is that tags will be searched for by Motus immediately upon registration if no deployment exists for those tags. The registration date has historically been recorded as the quarter-annum, so tag finder will act as though each tag was deployed on the first day of that quarter-annum. Not desirable, but better than nothing.

Anticipated deployment date

Default deployment dates are only present as a backup in case the researcher has forgotten to include their earliest anticipated start date during tag registration. An anticipated start date is basically the earliest day on which the researcher plans to deploy tags. This should provide ample time to update the tag metadata after the field season is over.

Deployed tags

Once a tag has been deployed, it's deployment metadata should be updated to reflect the real deployment date. Otherwise, tag finder might think the tag expired too early.

Undeployed tags

Because of the limited number of tag code / burst interval combinations, tags with these properties may be reissued to other projects if the tags are presumed to be dead or inactive. Tags that were not deployed during the expected tagging period should be given placeholder deployment recorders well into the future. This will ensure that they remain on the "active tags" list and are not reissued.

Example: You had 20 tags you expected to deploy in June 2023 and for which you made placeholder deployment record with anticipated start dates (as described above). However you were only able to deploy 18 of the tags and want to retain the remaining two tags for next year. You would modify the deployment record for the two undeployed tags and change the start date to some date in the future -- say July 1, 2024. This will ensure that the tag codes will not be reissued to another project. After you do finally deploy them, update the tag deployment metadata to reflect the actual deployments.

Consequences of bad metadata

Bad metadata to be information related to deployments which is either missing or inaccurate. We can use the example scenario above to predict what might happen when metadata isn't kept up to date.

• If there is no deployment data for a tag, tag finder will assume the tag has expired and will stop searching for it long before it should. In our example, the default deployment period has no overlap with the actual active period, meaning it will only search for the tag before it was actually ever deployed. Therefore, no detections would exist for this tag.

• If only an anticipated deployment date exists, there may be some overlap with the actual deployment period, but there could still be a lot of data missing from the end of the tag lifespan.

• If there are left over tags after the field season or if a tag is recovered and the existing deployments aren't terminated, manufacturers might reissue the tags which can result in ambiguous detections. That means there could be two tags deployed at the same time that appear identical to each other deployed at the same time, making it difficult or impossible to accurately identify the individual.

Several varieties of antennas exist of which only a few will be covered here. All antennas should come with their own assembly instructions which are more or less easy to follow so we will not go into great detail here. Please see for more details on parts.

Recommended accessories

• Coax seal. This is a type of soft rubber or silicone which is used to seal antenna connections. This is typically purchased separately from the antenna. Marine Goop (with UV protectant (link), and electrician, or plumbers puddy (with link).

• Coloured electrical tape or markers. It can be difficult to keep track of which antenna corresponds with which cable once a station has been set up. Bring a few colours of electrical tape so you can colour code the antennas and coaxial cables.

• Zip ties, cable ties, zap straps. These are indispensable for coaxial cable organisation. Used to support the coax cable along the antenna boom and mast.

• Hex nuts and bolts. We use ¼” x 2” bolts for tripod assembly and ¼” x 1” bolts for affixing solar panels to the tripod**.** Use zinc-plates steel unless the station is deployed in a marine area where stainless steel should be used.

Antenna mount

Antennas are usually attached to a metal pipe or mast using a type of mounting bracket. Small antennas, like 434 MHz Yagis, all omni antennas, and 3- to 5- element Yagis for the 150-166 MHz band can be butt-mounted using a bracket which fits onto one end of the boom. Large antennas, like 6- to 9-element Yagis for the 150-166 MHz band need to be mounted along their mid-point to even out the lateral force on the mast. Larger antenna can be butt-mounted, but usually require support wires attached to the mid or end point of the antenna.

Nearly all antenna mounts use a metal plate with 4 u-bolts; 2 for the antenna boom and 2 for the mast. For most antennas, the boom is mounted perpendicular to the mast, but omni antennas will often be mounted pointing straight up, meaning both the antenna and mast will be in the same orientation.

Coax connector

Most antennas will have a connector on the driven element for the coax cable to be connected. The driven element and this connector are the most sensitive parts of a Yagi antenna; pay special attention to these parts so they are not impacted by anything. Damage to the driven element may cause the antenna to no longer be tuned to the desired frequency.

Antenna orientation

The orientation of an antenna changes the horizontal range relative to the vertical range. For instance, an omni antenna can be oriented straight upwards to have a uniform detectability along the horizontal and vertical axes, or it could be pointed horizontally to create a more restricted, lateral detection area. Similarly, Yagi antennas can be rotated along the boom to select a wider horizontal or vertical beamwidth.

Antenna spacing

Most Motus stations will host multiple antennas, but this may pose an issue depending on the types and position of the antennas.

Simple modeling by Bob Morton at Maple Leaf Communications suggests there is a significant dropoff in the detection range of Yagi antennas when they are stacked too close together.

We have developed the following guidelines based on these models:

• Antennas that facing opposite directions should be the furthest apart from one-another: at least 1/2 a wavelength (~1 meter for 166.38 MHz).

• Antennas that are facing perpendicular directions should be at least a 1/4 wavelength apart (~1/2 meter).

There are countless ways to install a Motus station and it’s not always clear which is best. For the most part, your station will depend on the structure you have to install the antennas on. Here are a number of different installation methods used across the Motus network to help you decide which setup suits your location best. For any inquiries, please for additional support.

Overview

Motus stations have been built on just about anything – lighthouses, towers, trees, cars, drones, planes, ships, buoys, bamboo masts, and just about every type of building you can dream of.

The actual structure doesn’t necessarily matter as long as it’s strong and elevated enough to provide a clear line-of-sight, and the antennas are not mounted close to sheet metal or other antennas (see above). The easiest and often the cheapest method is to use a pre-existing building or structure upon which masts or antenna can be affixed to existing railings, or on the side of buildings where a can be mounted. Installation can be tricky, and every situation is different, but once it’s set up there shouldn’t be much maintenance or worry.

In remote locations where there aren’t any buildings to attach towers, one can use a tripod and mast like those manufactured by , or a . Pop-up towers must be guyed (3 lines per 10-foot section) and anchored (1 anchor per guy or just 3 strong anchors). Pop-up towers are more sensitive to wind and ice than the DMX-style structures so regular maintenance will be necessary.

Sourcing equipment outside of North America and Europe

The list below includes a list of structure types that are commercially available, but these products are typically not sold outside of North America and Europe by this supplier. In these cases, a local solution will need to be found which we provide examples of in the list. Please if you would like to contribute to this list of suppliers.

Looking for local solutions can be difficult. If you plan to install large antennas (i.e.; 9-element Yagis) in a location that may experience high winds, it's especially important to look for robust solutions that won't fail after the first storm. If at all possible, it's best to avoid installing your own free standing structure and instead use a pre-exisiting tower or attach a mast to a building. It's usually easiest to find piping for a mast (aluminum or zinc-plated/galvenized steel) and a bracket that will hold to an exterior wall.

Structure types

Lattice tower

It is highly recommended for collaborators to install a tower that is intended for longer-term use which typically involves a lattice tower. These types of towers have several names, including: Rohn tower, DMX, Golden nugget, Delhi tower. It is common to see this type of tower for weather stations, rural internet and TV, or HAM radio, which is a testament to their utility.

While installing this type of tower can be a significant increase in cost from the pop-tower, it will reduce your overall long-term expense. These structures have fewer individual parts and are stronger than the pop-up masts so require less maintenance and do not always need to be guyed giving it a smaller footprint. Certain models of lattice towers can be attached to a building, cutting costs significantly.

Common setup locations

• Buildings

• Parks

• Interpretive Centres

• Forests

On a building

There is an unlimited number of ways antennas can be mounted, it all depends on location. Co-locating a station can save on costs and is often necessary for some locations.

Common setup locations

• Houses

• Out buildings

• Public schools, universities, museums

• Guard Rails

Wall-mounted mast

This is essentially a metal pipe bolted onto the wall of a building using some sort of bracket. The bracket you use will depend on two things:

• What's the expected maximum load on the mast?

• How deep are the eves?

Guard Rails

Many buildings and other structures will have guard rails at their highest point which can serve as a great place to anchor your mast. Also see lighthouses and fire towers for similar examples.

Bolt-on roof mount

If it's possible to bolt into the roof, this can be the best solution to get the clearance required a low-profile structure.

Non-penetrating Roof mount

There are many cases where you need to install a station on a flat roof and it's not possible to bolt into the roof. A non-penetrating roof mount is essentially a platform that is weighted down with aa mast at the center.

On a pre-existing tower

Fire Tower

Commercial Tower

Some researchers have had success with installing antennas on commercial telecommunications towers. These are often in great locations and are usually powered, but they require a professional climber (+$1000 in fees) and sometimes rental fees.

Weather Station

Lighthouse

These days, most lighthouses have been decommissioned and offer a great opportunity for hosting a robust Motus station. One of the very first Motus stations was installed on Sable Island off of Nova Scotia and operated without a hitch for over 5 years. Getting permission to host a station on a lighthouse can be tricky depending on the jurisdiction, but in many cases local communities are in charge of keeping the lights and getting permission is not difficult.

Free-standing

Pop-tower

These are very common setups since they can be deployed almost anywhere, but the weight of the materials can be prohibitive. This type of tower is most-often limited by its height with anything taller than 50′ require a more robust and professional-grade installation.

Common setup locations

• Hilltops

• Clearcuts

• Sea/Lakeshore

• General open spaces

Mast only

Using just the mast is a smallest practical version of a free-standing Motus station. Usually these only host omni antennas due to the weight restrictions, but more robust version can hold Yagi antennas as well. This has become a widely used setup for temporary installations due to its low cost and ease of use, but generally limits the number and size of antennas that can be deployed and they are less reliable in high winds.

Weighted platform

These are a bit heavier to transport, but can be the only solution for locations where there is no soil layer to anchor guy wires.

Utility Pole

Utility poles are a good long-term solution for a Motus station as they can last decades without requiring any maintenance; however, the initial installation costs can be prohibitive due to the heavy machinery and skilled worked required.

On a vehicle

Mounting antennas to a vehicle can require a fair bit of improvisation depending on the antenna and vehicle types. Below are just a few examples of what has been done in the past. Most of the time it only makes sense to use an omni antenna which has a low profile, but also a limited range.

Car

All examples of car-mounted antennas with Motus have used omni antennas with varied success due to the limited range of omnis (0.5-1 km).

Photos to come

Boat

If planned well, boats can be a great place to host a Motus station due to the fact they have their own power source and their weight capacity allows for multiple of any antenna type to be attached. For instance, a ferry with two 9-element Yagi pointing down its bow and stern could detect animals as they move down a strait. In another case, fishing boats have been fitted with omni antennas to detect Phalaropes while they are at sea.

Photos to come

Plane

Aerial surveys have been conducted in the past where an omni antenna was placed on the bottom of the aircraft, but ultimately it's usually up to the pilot to decide what they are comfortable with.

Photos to come

Drone

Only an omni antenna can be used with drones. All examples have used flexible whip antennas which hang from the base of the aircraft.

Photos to come

Antenna Spacing

Yagi antennas should be vertically spaced according to their direction and frequency. Make sure you have ample spacing between your antennas and any sheet metal, such as roofing. The typical figure for minimum spacing and metal roofing is 1 full wavelength. Yagi antennas that point in the opposite direction (parallel) will interfere with each other if spaced too close together, essentially eliminating the directionality and severely impacting the detection range. Antennas that are parallel (180 degrees) should be at least ½, but best at a whole wavelength apart. Antennas that are perpendicular (90 degrees) should be at least ¼ wavelength apart.

How to build a Laird PLC1669 antenna

How to select an antenna

It is very important you select the right antenna for the purpose of the station and the type of tags you intend to detect. Antennas are optimized for reception on a particular radio frequency. Since there are multiple tag frequencies, each tag type requires its own antenna; currently an antenna optimized to detect Lotek tags on 166.380 Mhz will not detect CTT tags on 434 Mhz, and vice versa. Wherever possible we recommend installing “dual-mode” stations outfitted with antennas and a receiver that can detect both tags. A dual-frequency antenna is under development, but for the time being, dual-mode stations (those that can listen for more than one frequency, must have two different types of antenna in place.

How antennas work

An antenna is a device used to send or receive radio signals, i.e., electromagnetic radiation. This radiation induces a voltage in conductive materials which will vary in magnitude based on the physical dimensions and orientation of the material. The induced voltage oscillates at the same frequency as the electromagnetic radiation and the magnitude of the voltage is proportional to the strength of the radiation. Antennas used in the Motus Network are built (“tuned”) with high precision such that the induced voltage is greatest when exposed to the narrow range of frequencies that Motus tags emit. Antennas can also be shaped to select for radiation from specific directions and orientations.

Each antenna has a theoretical radiation pattern which represents its range in 3D space. We use the radiation pattern to predict the distance and direction in which we can receive signals from radio transmitters. Omnidirectional (‘omni’) antennas, as the name suggests, have a uniform radiation pattern that is emitted perpendicular to its axis. The thin wire attached to Lotek and CTT tags is a type of omni antenna. When used on a receiver, omni antennas provide presence/absence information, typically within a short range. This makes them ideal for fine scale studies as demonstrated with CTT SensorNodes which can be used to create a high-resolution grid of stations.

Yagi-Uda (‘Yagi’) antennas are a type of directional antenna that are the most commonly used antenna in the Motus network. Their radiation pattern is directed into a beam which varies in length and width based on the number of ‘directing elements’ with a greater number of elements resulting in a longer, narrower beam. For example, a 9-element Yagi antenna can theoretically provide tag detections from 15 km away at 166.380 MHz, but in reality this will vary widely based on the landscape and atmospheric conditions. Yagi antennas are favorable for most applications since they can be used to create receiver ‘fences’ or ‘grids’ with fewer stations than an omni antennas could. In addition, multiple Yagi antennas on a single station can be used to infer flight direction based on the timing of detection across each antenna.

A variety of antenna options exist for VHF/UHF telemetry. To date, collaborators have used 3, 5, 6, and 9-element Yagi directional antennas, and omni-directional antennas. Generally the greater the number of elements, the longer the detection range and more narrow the detection beam. The fewer the elements, the shorter the detection range, but the broader the detection beam. Omni-directional antennas are best suited for determining species presence-absence patterns (e.g. seabirds at a colony), or for detecting birds in close proximity to stations (within a few hundred metres), not suited for providing directional information (e.g. departure directions of songbirds from a stopover site).

Ordering Antennas

When ordering antennas and cables, it is important to ensure:

1. Connectors between the coaxial cable, antennas, and receiver are compatible.

2. The impedance rating of all cables, connectors, and dongles are the same (50 Ohms).

3. Cable type is suitable for the length needed.

4. Get recommended equipment if inexperienced with the technology (highlighted in green).

Select an item from the list below to learn more:

Antenna Anatomy

Yagi-uda

This antenna, usually referred to as simply “Yagi” or more generally a directional antenna.

Antenna Types

A variety of antenna options exist for VHF telemetry. To date, users have used 3, 5, 6, and 9-element Yagi directional antennas, and single-pole omni-directional antennas. The 9-element Yagis have a long, narrow detection range, whereas 3, 5, or 6-element Yagis have gradually shorter and wider detection ranges. Omni-directional antennas are best suited for determining species presence-absence patterns (e.g. seabirds at a colony), or for detecting birds in close proximity to stations (within a few hundred metres), but not for providing directional information (e.g. departure directions of songbirds from a stopover site).

When ordering antennas, it’s important to know what frequency you need it to be tuned to. For detecting Lotek tags, antennas must be tuned to 150.1 MHz (Europe), 151.5 MHz (Australia), or 166.380 MHz (Western Hemisphere), depending on the region. For detecting CTT tags, antennas must be tuned to 434 MHz.

Antennas can be purchased from the following suppliers:

• Wade Antenna [LINK]

Use the table below to help select your antenna:

Coax Cables

Coaxial cables (coax for short) are responsible for carrying the received radio signal from the antennas to the receiver. This cable is so-called coaxial because it contains a central conductor surrounded by a second conductor that runs coaxial to the central conductor (around it). This second conductor is electrically connected to the ground plane and provides shielding that helps insulate the central signal-carrying conductor from external electromagnetic interference and also reduces the amount of energy lost from the central conductor. Between the central core and shielding is a layer of insulating material which can vary in thickness, as well as the plastic outer jacket of the cable.

The signal carried by coax is measured in decibels (dB) and calculated by comparing the power coming out of the coaxial cable to a theoretical 1 mW transmitter.

With this equation in mind you can see how an increase of 3 dB actually means a doubling of the received power. Antenna resistance is an intrinsic property of the antenna and usually runs at 50 Ω. The coaxial cable also has a resistance so it will reduce the power of the incoming signal which varies by frequency. This is known as attenuation.

When selecting coaxial cables, you want pick something that keeps attenuation to a minimum. Attenuation can’t be eliminated entirely, so we try to keep it within a reasonable limit. For weak signal detection a difference 0.2 dB can be significant. The supplier for our coaxial cables and antennas here in Canada (Maple Leaf Communications) has suggested we try to keep attenuation under 1.0 dB for any cable length, but obviously this is not always practical. The recommended low-loss cable is the LMR-400, but it is very bulky and difficult to work with. For this reason, we recommend using lower grade cables for short lengths, such as the LMR-240 or RG-58.

To get an idea of what kind of effect attenuation may have on tag detection, imagine a receiver with a theoretical detection radius of 10 km. If the antennas on the receiver experienced 1.0 dB of attenuation, this radius would be reduced to 9 km; if they experienced 2.5 dB of attenuation, that would be reduced to 7.5 km.

Signal loss by length of cable

One of our antenna equipment suppliers, Maple Leaf Communications, has written a helpful guidance document for selecting cables based on the length and frequency required.

Additional documentation

• RG58 – basic communications cable that typically comes with a BNC connector. Best used for lengths less than 50′. The least expensive option.

• RG213 – higher grade cable that can be used at length of up to 100′ with low signal loss. Custom cable ends depending on distributor/manufaturer. Moderate price.

• TWS/LMR-400 – similar to the RG-213, but higher quality (stronger weather/sun resistance) coating. Best for longer-term installations and long cable length. Most expensive. Manufacture can suggest which cable is best for your needs – LMR is generally more affordable.

• BMR-240 - available from Maple Leaf Communications, this cable has slightly less plastic insulation, making it much more flexible and easier to work with than LMR-400, while offering similar attenuation.

Radio Dongles

Radio dongles, also known as Software Defined Radios (SDRs), are used to convert analog signal received by the antennas into a digital signal that can be interpreted by the SensorGnome . Note that Lotek receivers have a built-in converter and do not require these for station operation. Note that SensorStations only need an SDR for antennas tuned for Lotek tags (anything that isn’t 434 MHz).

While there are dozens of available SDR’s on the market, only four models are compatible with SensorGnomes and SensorStations. Most commonly used are the FUNcube Pro Plus which have the smallest signal-to-noise ratio (SNR), noise figure, and DC voltage spike (poor reception at nominal frequency), and power rating. However, FUNcube dongles are the most expensive, costing ~$200 USD, compared to $35 USD for the RTL-SDR.

* CTT dongles listen to 434 MHz and are only used to make Sensorgnomes compatible with CTT tags.

Items listed in green are recommended.

Bandpass Filter

Connectors

There are several types of connectors that are used with radio antennas and coaxial cables, but not all perform equally. For instance, certain connectors are better at preventing water and dust ingress. For this reason, it’s important to know what kind of connectors your antennas have when being purchased, and which are most suitable for a Motus station. There are four connector types commonly found in Motus station setups: UHF (PL-259); N-type; BNC; and SMA.

Most 9-element Yagis and omni-directional antennas tend to come with a female UHF (Laird) or N-type connector (Maple Leaf), but this should be verified prior to purchase. Three and 5-element Yagis usually come with a male BNC connector and so they can be connected to a Lotek SRX receiver directly, or to a FUNcube with female BNC to male SMA adapter.

The following table outlines where we typically see these connectors. Dongles are the analog-to-digital converters that are part of the Sensorgnome (typically we use FUNcube dongles, or FCD).

Items listed in green are recommended.

The following are some common uses of these connectors:

1. Coax cable with male BNC connector at one end and male UHF connector at the other end (for Lotek receivers or Sensorgnomes with female BNC to male SMA adapter).

2. Coax cable with a male BNC connector at both ends with a BNC female to UHF male adapter (Lotek receivers or Sensorgnomes with female BNC to male SMA adapter).

3. Coax cable with custom female UHF connector at the antenna end and a male SMA connector at the FUNcube end. (Option with fewest adapters and therefore less signal loss, but may be more expensive due to custom ends). Sensorgnome only.

Grounding Antennas

Heavy-duty Container

Supplies

• 90L Rubbermaid Action Packer or equivalent heavy-duty, waterproof container.

  • If using an alternative, ensure the container is actually

    waterproof and the lid is not concave such that water pools on

    top. Handles will need to be closed securely either with zip

    ties or a lock.

• To prevent water ingress:

  • 2-inch pipe elbow (90 degrees) similar to:

  • 2-inch pipe bushing, similar to:

  • Electrical tape or ABS cement

• Zip ties

• [Optional] To prevent insects and rodent ingress

  • Plastic bags and/or steel wool.

  • Aluminum window screening.

  • JB Weld epoxy or equivalent.

    • Container and stir stick for epoxy.

  • Tool to cut into underside of container (e.g.: exacto knife).

Tools

• Drill

• 1/4" or similar sized drill bit

Instructions

1. Drill 2” hole on one end of the Action Packer, about 6" from its base.

2. Place the 2-inch pipe bushing through the hole from the inside of the bin.

   1. Apply a single layer of electrical tape or ABS cement to the exposed end of the bushing on the outside of the bin.

   2. Attach the 2-inch pipe elbow to the bushing from the outside of the bin and force into place with the open end of the elbow pointing down.

   3. Using the 1/4" drill bit, drill a couple holes in each of the bottom corners of the bin. This is to prevent water from pooling if it gets in somehow.

3. [Optional] To prevent insect and rodent ingress

   1. Cut a pieces of aluminum window screen large enough to cover the holes drilled into each of the corners of the bin.

   2. Prepare the epoxy

   3. Place the piece of aluminum window screen over the hole and apply a generous amount of the mixed epoxy around the entire edge, ensuring no gaps remain.

   4. Once you have inserted all necessary cables into the bin, including your GPS and SensorGnome, you will need to pack the remaining space in the elbow with plastic bags (insects) and/or steel wool (rodents).

Contents

• • 9-element Yagi (Laird)

  • 9-element Yagi (Intermod/Maple Leaf)

  • Omni (Intermod)

• Structures

Receivers

Not all receivers are compatible with all tag types!

Antennas and cables

166.380 MHz antennas

For Lotek Nanotags in the Western Hemisphere.

434 MHz antennas

For CTT LifeTags, PowerTags, and HybridTags globally.

Laird 6-Element Yagi TS4306

Coaxial Cables

Most RF or antenna suppliers will sell coaxial cable cut to size and with with your choice of connection type. We recommend LMR400 cable, which is durable and low-loss. However, due to its stiffness, we also recommend a 30 cm (12-inch) jumper cable made of a lighter grade material (e.g.; LMR-240) as strain relief for connectin between the LMR-400 cable and the FUNcube dongle. Alternatively, you may use bulkheads for strain relief.

Bulkheads

Bulkheads are connectors used to attach coaxial cables to the receiver. They attach directly to the 'radios' or 'dongles' which are part of the receiver (e.g.; CTT internal radios or FUNcube dongle). These parts can be readily found online at various retailes, just make sure you search for SMA male to Type N female bulkhead. We recommend waterproof bulkheads for mounting on cases - these come with o-rings which can maintain the original IP rating of the case. The product below is a somewhat expensive example of what we normally purchase, yet we are usually able to find the for under $10 USD apiece at other retailers.

Bandpass Filters

Power Supply

Antenna mounting structure

Instructions

Methods for downloading data from a Motus receiver depends on the model of receiver being used. Select a model from the links below to view instructions:

Uploading data to Motus

1. Log in to Motus.

2. Select your project from the dropdown menu.

3. Select '' from the management menu.

4. Follow the instructions on that page to upload these data.

Before you go

1. Check for wiring to solar panel, battery, and receiver. Make sure you have the wiring and connectors needed.

2. Cover the battery terminals. It can be easy to accidentally short the battery terminals with a tool or cable which is a fire hazard.

3. Use the hole saw that’s the same size as the pipe elbow and a drill bit to cut a hole into the short side of the action packer. Attach the pipe elbow and the bushing.

4. Tape tool boxes shut to prevent them from opening accidentally. Zip tie larger totes shut, too.

Parts Checklist

Tools

Setup instructions

Base Plate

1. Find an elevated and relatively flat rocky location large enough to fit the base plate (~1 foot in diameter)
2. Place the base plate on the ground and use a metal tool or grease marker to mark the center of each hole in the base plate.
3. Wearing safety goggles and an N-95 mask, use the rotary hammer to drill each hole about 3 inches deep. You should hold both handles while drilling – if you only hold the trigger it can break your wrist! Use the clear plastic tubing to blow the rock dust out of the hole periodically. You will likely need to replace the battery between holes.
4. Place a wedge anchor in each hole with the threads facing up and use the mallet to drive the anchor into the hole as far as it will go.

5. Put the base plate over the wedge anchors and then add the washers then nuts to each wedge anchor. Use the channel locks to tighten the nuts as much as possible.

Anchors for guy wires

1. Using the tape measure, mark a position on the bedrock that is at least 7 feet (213 cm) from the base of the tower, starting from one of the corners of the triangular base plate. Do this for each of the 3 corners.
2. Wearing safety goggles and an N-95 mask, use the rotary hammer and 5/8” masonry bit to drill each hole about 2 1/2 inches deep. You should hold both handles while drilling – if you only hold the trigger it can break your wrist! Use the clear plastic tubing to blow the rock dust out of the hole periodically. You will likely need to replace the battery between holes.
3. Place an expansion eye bolt in each of the drilled holes and use a mallet to drive them in. Use a wrench or channel lock to tighten the nuts on the top of each eye bolt.

Top kit

1. Open up the top kit box and baggies. It comes with instructions for two models – ours is the 244A so don’t worry about the diagrams with the U-bolts. The video below walks through these instructions. Follow instructions and video to put together this part. The only difference is that you’ll also be attaching the guy station brackets to the top where the bolt holes go. You won’t be using the larger V-shaped pieces of the guy station.

Guy wires

1. Take free end of the wire still attached to the spool and thread two crimps onto it. Feed the wire rope back through the crimps to make a small loop.
2. Add a wire rope thimble to the loop and the pull the wire rope to tighten the loop around it. Use the swage tool (if you have it) or the wire cutters to crimp the wire crimps onto the wire rope. If wire cutters are too difficult, you can also try the bolt cutters, but be gentle!
3. Attach a carabiner to the looped end and attach the carabiner to one the guy station brackets on the tower. Unspool about 15 feet (4.5 m) of wire rope, but don’t cut it yet.
4. Raise the tower and sit it onto the base plate in the position you imagine it to be when it’s finally set up. Use the level (it should be magnetic) to make sure the tower is vertical during the following steps.

5. With someone holding the tower (and ensuring the tower stays level), bring the spooled end of the guy wire to the eye bolt closest to that corner of the tower. While pulling the guy wire taught, measure about 1 foot (30 cm) beyond the eye bolt and then cut the cable using wire cutters.
6. On the new end of the cable segment you just cut, thread on 2 guy wire crimps and then feed the guy wire back through the 2 crimps to make a small loop. Add a wire rope thimble and then attach a turnbuckle to the new looped end of the cable. Don’t crimp the guy wire crimps yet!
7. Loosen the turnbuckle almost all the way until 1 turn or so before the bolt would come out.

8. Attach a carabiner to the free end of the turnbuckle and the carabiner to the expansion eye bolt.
9. Pull on the loose end of the guy wire until the guy wire is mostly taught and then crimp the guy wire crimps.

10. Repeat steps 2 thru 10 for the two other corners of the tower.

Mast

1. These steps are a bit complicated because you won’t be able to climb the tower to adjust the antenna bearings once the tower has been raised. You may have to adjust the antenna bearings multiple times before you’re satisfied with their position.

2. Lean the tower on a rock or the storage bin so the top is in the air.

3. Slide the mast into the top kit so the bottom is about 1 inch below the lower clamp of the top kit. Tighten the bolts so the mast doesn’t want to slide around.

4. Slide on the two Yagi antennas, starting with green and then yellow (green is on the bottom).

5. Slide on the two omni mounting brackets and then slide the omni on to the bracket. Tighten the bolts on the bracket until the omni is fixed firmly in place.

6. Attach the RED coax cable to the omni and zip tie it to the mast below it.

7. Slide up the YELLOW antenna until it’s directly below the omni and fix it firmly in place.

8. Use a compass or compass app on your phone to get the bearings for the two directions you’d like to point your Yagis.

9. Move the GREEN antenna until it is about 2 feet below the YELLOW antenna and then rotate it until the relative angle between the two antennas is the same as the angle between the two bearings you’d like to point them. Tighten the larger U bolts to fix the antenna firmly in place.

10. Rotate the angle of the antenna elements to ensure both Yagi antennas will be properly horizontal and once the tower is raised and then tighten the smaller U bolts to fix them firmly in place. Since the tower is leaning over in this step, it might be easier to make them horizontal if you just make sure the elements are perpendicular to the mast.

11. Get the compass bearing for one of the points on the base plate and then estimate how you’ll have to rotate the mast so the antennas are pointing in the intended direction once the tower is raised.

12. Tighten all the bolts on both mast clamps so the mast is fixed firmly in place.

13. Zip tie the coax cable to the mast all the way down the tower and then use the wire clips to clip off the ends of the zip ties.

Raising the Tower

1. Use the channel locks to squeeze the attachment points on the base plate so they are a little closer together.

2. Open the package of nuts and bolts that was attached to the base plate.

3. Carefully raise the tower and place on each of the attachment points.

4. With 2 people holding the tower up, check the antenna bearings to make sure they’re pointing in the right direction. If you need to adjust, lower the tower back down and try again.

5. With 2 people holding the tower up, a third person can start inserting the bolts into the attachment points. Bolts should be pointing inward to avoid scraping ankles on the ends. The feet of the tower will be raised a bit – this is normal. After putting a bolt in, add a lock washer and a nut on the other end. You only need it finger tight until all bolts are inserted.

6. Attach each guy line to their anchors, but make sure all the turnbuckles are still loose.

7. Use the magnetic level to make sure the tower is level. The people holding the tower should continuously ensure the tower is level as you start tightening the turnbuckles. You will likely have to tighten all the turnbuckles part way before doing a final tighten. You want the guy wires to be taught.

8. Tighten the nut on the turnbuckles to lock them in place and they won’t rotate any more.

Prerequisites

Location

• Must be flat and void of obstructions so antennas have a clear line of site.

• Cannot be near any elevated power or telephone lines for safety reasons.

• Tripod feet will sink into soft ground - use gravel or choose a hard/dry location to install. Also affix pieces of wood to each tripod foot to support the weight and movement and to prevent sinking (‘snow-shoe).

• Ground must be soft enough to insert anchors (1 m/3 ft. or more, depending on hardness).

• Choose a well-elevated site to avoid any risk of flooding during heavy rains or tidal surges.

• Footprint of a pop-tower with guy wires has a radius equal to 70% of the tower’s final height.

Hardware

• Pop tower

  • Tripod

  • Wooden blocks (optional)

  • Mast

    • Height will depend on location, desired detections. 40-feet is maximum suggested height.

    • Comes with a and 1x 3-inch bolt for each mast section.

  • Foot for mast (optional)

  • Guy wires (1/16 galvenized for inland sites; 3/32" stainless for marine areas)

  • Quick links and/or carabiners (max 3/16”)

  • [Optional] Turnbuckles with nuts or stainless steel wire (snare wire)

  • In-line wire tensioners.

  • Anchors

    • Can use #6 rebar in 3-foot sections or

      .

Tools

• Impact driver and/or ratchet

  • 7/16” socket

  • ½” deep socket

• Ratchet with ½” drive

• Drill

  • Cobalt drill bits (or equivalent) for metal drilling.

    • 3/16" and 1/4"

  • Phillips/Robinson’s screwdrivers for screws

Instructions

Tripod + Mast Assembly

1. Assemble the tripod according to instructions provided by the manufacturer.

   • It is easiest to install the TRM-10L with it lying on its side.

2. Insert mast into the center of the tripod. Bolts on the tripod's centre brackets may need to be loosened to allow space for the mast to slide through.

3. Attach foot to base of mast.

4. Attach lower guy wires to the lower guy ring using quick links or carabiners.

5. Place tripod + mast assembly upright.

6. Position the assembly so the mast stands level and the tripod legs are on stable ground.

7. Screw on wooden blocks to the tripod legs to prevent them from sinking into the ground. This is suggested for most installations as the ground will soften in the spring and fall.

   • Alternatively, you can bury cement blocks filled with sand for

     each foot to stand on.

8. If you are mounting a solar panel, rotate the tripod so that the ‘ladder’ side with four crossbars is facing south.

9. Place three anchors 7 feet (2 m) from the base of the mast such that once the guy wires are attached they are between the tripod legs.

   • If using angle iron

10. Attach the loose end of the lower guy wires to each anchor.

11. Tighten the guy wires with:

    • In-line wire tensioner:

      1. Remove tensioner lock.

      2. Place guy wire in the slot of tensioner.

      3. Insert ½” drive ratchet into square slot of tensioner.

      4. Use the ratchet to tightly spool guy wire until taught, but not too taught.

         • Tripod legs will lift off the ground if too tight, or

           the mast will bend.

      5. Insert tensioner lock in opposing holes to keep guy wire in place.

      6. Multiple tensioners may be necessary if there is too much excess guy wire.

    • 1. Before all guy wires are taught, loosen the turnbuckle until only 2 full turns remain.

      2. Tighten guy wires, either with in-line wire tensioners or another method.

      3. Use turnbuckles to finely adjust wire tension until all sides have equal tension.
12. Confirm tower is being held securely in place by guy wires by inspecting each end of all guy lines to ensure it is properly attached.

Mounting Antennas

2. Finger-tighten the U-bolts which attach to the antenna boom such that it can still rotate.

3. Loosely-attach the second set of U-bolts.

4. Coaxial cables should already be attached, sealed, and zip-tied to the antenna boom (one tie by driven element, a second tie by the mounting bracket).

5. Ensure the tripod is securely guyed at the base and is safe to climb.

6. Climb the tripod of the tower and pull out some of the top-most section of masting from the telescopic mast.

7. Slide the U-bolts of the antenna mounting bracket onto the mast and allow it to rest on the guy ring at the top of the tripod.

8. Rotate the antennas such that the elements are horizontal and then tighten the U-bolts which affix the boom to the mounting bracket. Don't tighten the U-bolts attaching the antenna mounts to the mast - this will be done later.

9. Slide on all other antennas in a similar manner (steps 7 and 8) except for the top-most.

10. Securely attach the mast collar approx 30 cm (1 foot) from the top of the mast and then slide on the spare guy ring and attach the top-most guy lines (they don't need to be anchored yet).

11. Slide on the last antenna and attach it securely in place approximately 15 cm (6") from the top (~15 cm above the guy ring).

12. Mark out planned antenna directions on the ground using visual markers so you can easily point antennas in those directions.

13. Determine the height of each antenna based on our guidelines for stacked antennas and then colour-code each antenna and coax cable so that they can be identified when plugging them in to the receiver.

    Our convention: port 1 = top (red or 1 stripe), port 2 = middle (yellow or 2 stripes), port 3 = bottom (green or 3 stripes).

14. Before raising the mast, ensure all guy lines and coax cables are uncoiled, and that the antennas and coax are colour-coded.

15. While holding the top-most section of masting with one hand, loosen the top-most L-bolt and then begin raising the mast.

16. Once there is adequate space between the upper-most antenna, tighten the L-bolt so the mast stays in place and then fix the next antenna to the mast, ensuring that both the top and middle antenna are pointing in the intended final direction.

17. Repeat steps 15 and 16 until all antennas have been fixed to the mast.

18. Continue raising the mast section until the hole below the L-bolt no longer shows metal on the inside.

19. Once the mast section has been raised, slide a 3-inch bolt through the hole below the L-bolt for that section and then allow the top section to rest on top of that bolt.

20. With the top mast section resting on top of the bolt, rotate it until it locks in place and starts rotating with the section below it. Tighten the L-bolt.

21. Continue raising mast sections (following steps 18-20) until the desired height has been reached. Don't worry if the angles aren't perfect - you can adjust the whole mast at the end.

22. If at the final height you cannot fit the 3-inch bolt into the hole below the L-bolt (because the inner masting is in the way), you can drill through the masting to insert the bolt. Make sure you lock the L-bolt in place!

23. Ensure the bolts on the tripod's centre brackets are loosened and then rotate the entire mast to it's final position (you may need 2 people to do this).

24. Tighten the centre bracket bolts, being careful not to dent the mast.

25. Place guy wire anchors at a distance from the mast that is approximately 70% of its height on the mast.

In regions where thunderstorms are frequent, we recommend that Motus stations be grounded. We have kindly been provided with instructions for how to make Motus stations R56 compliant in the PDF document below. Note that even if R56 compiance is not a requirement for your Motus stations, this document provides helpful guidance on grounding your Motus station.

Parts Checklist

Tools

Hardware

Steps

Choosing a location

The most important thing in choosing where to locate a tower on a building is to choose the location with the least obstructed view for the antennas. For example, the 9-element Yagi Antennas can reach about a 20 KM range, assuming that there is nothing obstructing their view within that distance. First step is to choose which direction you want your directional (Yagi) antennas to point. Then choose a location on the building where that direction can be easily accessed by the antenna. This usually means attaching near the highest point on the building so that the building it is attached to does not get in the way, but this is not necessary if the antennas all point away from the building. Other things to consider include:

• Relatively flat ground where the base plate needs to sit.

• Away from power lines, in case the equipment falls during installation.

• Where there is a bit of roof overhang (best for attaching brackets).

• Near an A/C outlet, otherwise you are running a long extension cable.

• Within range of Wi-Fi if you plan to connect. Otherwise you might want to use a Wi-Fi extender. This means you won’t have to download data manually.

Tower sections

1. If you need more than one 10 ft tower section, bolt multiple sections together by inserting the smaller end into the larger end.

2. Bolt pieces together using bolts provided (taped to tower sections). The bolts should be pointing inward to avoid scraping ankles on the ends when climbing.

Top kit

1. The end of the tower section with a smaller tube diameter is the top, where the top kit gets attached.

House brackets

1. Get a measurement from the ground to where the house brackets will attach to the building (underneath roof overhang).

Mast

1. Slide the mast into the top kit so the bottom is about 1 inch below the lower clamp of the top kit. Tighten the bolts on the top mast clamp so the mast stays in place when raising the tower. Remember to later tighten all the bolts on both mast clamps so the mast is fixed firmly in place AFTER attaching antennas.

Base plate

1. Temporarily raise tower to visualize where the base plate should be once the tower is properly located. You want the tower sections to be close to the building, but at least a couple inches away so it doesn’t rub against the building.

Soft ground

1. Place the drive stakes in the three holes of the base plate at 45 degree angles, each facing 3 different directions so that the base plate cannot lift up.

2. Using a mallet, hammer roughly 4/5 of the length of the drive stakes into the ground.

Hard ground

If installing over hard ground (e.g., cement, large rock), follow these instructions:

1. Place the base plate on the ground and use a metal tool or grease marker to mark the center of each hole in the base plate.

2. Wearing safety goggles and an N-95 mask, use the rotary hammer to drill each hole about 3 inches deep. You should hold both handles while drilling – if you only hold the trigger it can break your wrist! Use the clear plastic tubing to blow the rock dust out of the hole periodically. You will likely need to replace the battery between holes.

1. Place a wedge anchor in each hole with the threads facing up and use the mallet to drive the anchor into the hole as far as it will go.

2. Put the base plate over the wedge anchors and then add the washers then nuts to each wedge anchor. Use the channel locks to tighten the nuts as much as possible.

Raising the tower

1. Use the channel locks to squeeze the attachment points on the base plate so they are a little closer together.

2. Open the package of nuts and bolts that was attached to the base plate.

3. Carefully raise the tower and place on each of the attachment points.

4. With 2 people holding the tower up, a third person can start inserting the bolts into the attachment points. Bolts should be pointing inward to avoid scraping ankles on the ends. The feet of the tower will be raised a bit – this is normal. After putting a bolt in, add a lock washer and a nut on the other end. You only need it finger tight until all bolts are inserted.

5. Use the magnetic level to make sure the tower is level. The people holding the tower should continuously ensure the tower is level as you attach the house brackets.

6. Attach 2x4 wood to underside of roof using lag bolts and impact driver.

7. Attach house brackets to 2x4 wood using lag bolts and impact driver.

8. Tighten U-Bolt attachment points on tower. Remember, you attached the housing brackets to the tower before raising the tower (see above), which makes this much easier than doing it when the tower is raised.

Antennas

1. Assemble the Yagi antennas using the provided instructions. Some helpful tips:

   a. The hose clamps should be placed at the edge of the tube to maximize the clamping power.

   b. Tighten the hose clamps using a 5/16 hex bit – it’s so much easier!

   c. Attach the coax cable and seal it using the provided coax-seal before zip-tying.

   d. Attach the mounting bracket such that the plate sits vertically while the antenna elements are horizontal and fix in place so that it won’t move around on its own, but can be adjusted with a little force.

2. Assemble the omni antenna mounting brackets. Keep it loose so it can still easily slide on to the omni.

3. Colour- and number-code each antenna and the coax cable (end nearest ground) it is attached to with electrical tape.

4. From the roof, slide the two Yagi antennas onto the mast

5. Slide on the two omni mounting brackets and then slide the omni on to the bracket. Tighten the bolts on the bracket until the omni is fixed firmly in place.

6. Lower the mast as needed to reach the top by untightening and retightening the bolts in the top mast clamp.

7. Once all antennas are in position and the mast is raised, tighten all the bolts on both mast clamps so the mast is fixed firmly in place.

8. Attach the designated coax cable to the omni and zip tie it to the mast below it.

9. Use a compass to get the bearings for the two directions you’d like to point your Yagis.

10. Slide up the middle antenna until it’s directly below the omni, point it in the right direction, and fix it firmly in place.

11. Move the bottom antenna until it is about 2 feet below the middle antenna and then rotate it until it is pointing in the correct direction. Tighten the larger U bolts to fix the antenna firmly in place.

12. Rotate the angle of the antenna elements to ensure both Yagi antennas will be properly horizontal (i.e., elements are perpendicular to the mast).

13. Tighten the smaller U bolts to fix them firmly in place.

14. Zip tie the coax cable to the mast all the way down the tower and then use the wire clips to clip off the ends of the zip ties.

15. Attach the coax cables to the receiver in the following order:

    a. Top antenna on the first connector

    b. Middle antenna on the second

    c. Bottom antenna on the third

Climb shields

1. Place climb shields at a height on the tower that will prevent anyone from being able to climb the stairs.

2. Use impact driver and self-tapping screws with 5/16 hex bit to attach climb shield to lattice tower.

3. Attach a Motus sign on climb shields using self-tapping screws.

Receiver

1. Attach receiver case to a) tower, or b) inside building for further waterproofing.

   a. If attaching a Sensorgnome to tower, drill holes in outside ridges of Pelican case and use zip ties to attach to tower. Make sure you attach in a way that the box can still be opened for maintenance. If attaching a SensorStation to tower, use bracket provided to attach case to tower.

   b. If attaching receiver inside, drill a hole in the building with a 1 ½” hole saw: Use the stud finder to check for wires in the wall before drilling. Run the cables through the hole, and connect the coax cables to the receiver as explained in step 11 of “Antennas” section. Secure the receiver case somewhere convenient and where it will not be disturbed/unplugged. Fill the hole in the wall with sealant.

2. If the receiver is outdoors and you want to plug the extension cord into the wall indoors (for waterproofing or easier access to an outlet), use the ½” hole saw to drill a hole into the building. Use the stud finder to check for wires in the wall before drilling. The end of the extension cord will need to be cut in order to fit into the hole and reattached to an electrical plug (male-end) once inside the building.

Contents

When to schedule inspections

Inspections should be scheduled to ensure each station operates as expected prior to any critical period for research in your region. For some collaborators, stations are primarily used for personal research projects, but it is still important to maintain station operation throughout the year to spread the benefit to other projects in the network.

Offline stations

Depending on your location, stations that need to have their data downloaded manually should be inspected three to four** ** times per year. This corresponds to spring and fall migratory periods as well as breeding and wintering periods. In northern and southern latitudes, it is common for there to be no tags present during the wintering period so it may not be as important to check stations at that time.

Networked stations

If your station is connected to the internet, data will be sent to our servers automatically. However, this won't tell you whether the station antennas have shifted direction or if the mounting structure is properly secured. For this reason, we recommend networked stations are checked one to two times per year, depending on the frequency of storms and whether the station is in a marine environment.

Storms

If an extreme whether event has been forecasted it is important to ensure any vulnerable stations are properly secured prior to the storm's arrival to minimize damage. If damage is expected, stations should also be checked after the storm has passed to fix any issues that may have occurred. This applies to both networked and offline stations.

Marine environments

Stations close to sea water will deteriorate much faster due to salt and water accelerating oxidation and galvanic corrosion. Salt fog can affect metal structures dozens of kilometers inland so the station does not have to be near the ocean to impacted.

Winterizing stations

In locations that experience higher winds, less sunlight, and sub-zero temperatures in the winter, it may important to winterize stationst during those months. With a telescopic mast you can protect your station from wind damage during the winter by lowering your antennas further than normal. You can also save on power by unplugging some or all radio devices from the receiver or even by unplugging the receiver itself.

In the end, usually not necessary to completely dismantle your station at any time of year, unless you are concerned about theft, or if you want to reduce the amount of environmental exposure to your equipment.

What to bring

Below are a few items we recommend you bring on each station visit:

• Spares, spares, spares! Try to have at least two of everything you might need to replace at a station.

• If working at heights, appropriate safety equipment (harness, vest, etc.).

• Bolt cutters, for removing rusted bolts, etc. Very important!

• Multi-meter: measures both voltage and resistance (to check for shorts and breaks)

• Gloves

• Small flat head screwdriver (for rewirign, if needed)

• Phillips screwdriver

• Zip ties (to secure cables and wires; close storage bin)

• SensorGnomes only: spare SD card with software image.

What to do

By following a sequence of steps during each station visit it's harder to miss something.

Approaching the station

For safety reasons, it's important to do a proper inspection of the structure before approaching it to ensure it is being properly supported. If there are issues, they can be mitigated safely as long as the everyone is first aware of those issues.

Station structure

In most cases, stations need a structure for mounting the antennas. These take many forms, but they mostly have a central mast (can be telescopic) and a lower structure supporting that mast (typically a metal tripod).

Is the structure still standing straight? Is is properly supported? Is it showing signs of considerable corrosion where metal has been bolted together? Is the mast bent or cracked? Has the mast slid downwards or twisted since the last visit? Many of these features are most easily viewed from afar while walking towards the station.

Guy wires

If guy wires are present at this station, you must check for loose or broken lines and fix them before doing anything else. If any guy wires are frayed they should also be treated as unsafe and be replaced.

Antenna orientation

Are the antennas horizontal? If not, the mast is either bent or the structure has shifted. If you are using a tripod, it's common for them to become uneven if the feet sink into the ground.

If the antenna directions are wrong, either the mast has not been secured or one or more antenna mounts are loose. When mast is loose and there are multiple antennas, the difference between any two antenna directions should still remain the same from when the station was first installed (i.e.; the relative difference should remain the same).

Ants, Bees, Spiders & Wasps

Insect issues at Motus sites are uncommon, but on occasion they do occur. The storage and SensorGnome present attractive nuisances as a refuge for a variety of insects. The SensorGnome case is a sealed and waterproof case that should deter insects. The Action Packer is not sealed and is thus relatively easy for insects to invade. Always be cautious when opening an Action Packer. During autumn as the temperature drops the Action Packer may attract insects looking for a place to overwinter, especially some paper wasps. Ants may be attracted to the Action Packer’s environment as a safe place to incubate eggs or tend larvae and pupae. For a location that has continual insect issues leather gloves may be useful. Ant and wasp infestations may require occasional use of an insecticide.

Some examples of wasp nests include under the handles of the action packer (both at once!) as well as at the tips of antennas if they are not covered.

Bears

There is a playful aspect of bored or territorial Black Bears that on occasion causes problems with field equipment. Bears may swat at, push, move or overturn the Action Packer. The 90 pounds of battery in the bottom of the Action Packer provide some resistance, but any bear that seriously wants to move an Action Packer can do so. The batteries are sealed spiral gel cells that will not leak electrolyte, so if an Action Packer is tipped over there should not be any spilled electrolyte inside. Jostling of the Action Packer might cause severed wires, loose connections and/or other problems. Loose or broken wires may require specialized attention by someone capable of repairing electrical connections. Bears might chew on Action Packers. A possible solution to discourage repeated bear chewing is using Tabasco sauce or another product with Cayenne pepper in it on the outside of the Action Packer. If an Action Packer is repeatedly seriously moved by a bear this can be thwarted by strapping the Action Packer to the ground with earth anchors and webbing cinch straps.

Digging Mammals

Digging mammals, primarily woodchucks and foxes, may occasionally cause problems at Motus stations. When holes are dug at guy line anchors the holes can compromise the guy anchors and in a worst case situation risk tower failure in windy conditions if the hole allows a guy anchor to fail. Any and all holes should be filled in. Holes can be filled with soil or rocks. Holes dug underneath the base of a tower also need to be filled. If a serious hole is encountered at a guy anchor, obtain a cell phone picture and contact the PA Motus coordinator.

Inside the storage bin

Receivers are typically kept inside a heavy-duty storage bin which also houses the power supply and further protects the receiver from the elements.

Blown Fuse

The normal current draw of the receiver will not blow the system fuse. Blown fuses are a highly unlikely situation at Motus stations. A blown fuse is an indication of a current surge that exceeded the amperage of the fuse. The only conditions that will blow a fuse are a short circuit or a current surge resulting from a nearby lightning strike. As a first step replace the blown fuse. If it immediately blows upon replacement, then there is a short circuit in the system that must be located and repaired before the receiver can be successfully restarted. Locate the short circuit, repair it and then restart the receiver.

Rodents

Rodents, from mice, to chipmunks, to squirrels, to porcupines, have gnawing teeth and are good at using them. When inspecting the Motus system check for rodent damage to the various cables leading from the Action Packer to the various external components. If rodents chewing is found on any of the cables and the SensorGnome is still operating then the chewing has probably not damaged the cables. Repair the damage to the cable by wrapping the damaged area with electrical tape to seal out moisture. Cables that are totally severed as a result of mammal chewing will need to be repaired or replaced. Contact the PA Motus coordinator if a cable needs repair or replacement.

Battery voltage

It's always good to get an idea of how much power is in the battery. A typical 12-volt battery that we use will have a voltage of 14.5 v when fully charged and can cycle to as low as 10-11 v. A low battery voltage is indicative of not enough power being stored which can be due to a damaged battery or insufficent power coming from the solar panel. Keep in mind that if you're visiting the station early in the morning, the battery voltage will likely be at a moderate level (~12 v), depending on the capacity of the battery used. During the winter months or after a long overcast period, the voltage may be even lower.

The battery voltage can be measured either by using a volt-meter or some charge controllers will have battery voltage indicators (such as the SunSaver).

Solar charge controller

The charge controller (typically Morningstar SunSaver SS-12v-10L) is a critical component essential to managing battery recharging and power supply to the receiver. Morningstar SunSavers have a good track record of reliable operation over long periods of time. If the charge controller fails the power supply to the SensorGnome will be interrupted. If the failure is due to water damage, it's possible that the batteries will discharge or a fuse will be blown.

Besides monitoring charging and battery voltage level, the indicator lights on the Morningstar SunSaver are also used to indicate error conditions by various flashing patterns other than charging heartbeat or the full battery heartbeat. If the Morningstar SunSaver ever presents unusual indicator flashing light patterns then there is a problem with the charging and power supply to the SensorGnome. In situations where the Morningstar SunSaver is presenting error codes the receiver is not likely to be functioning properly. There is probably no remedy to this other than replacing the charge controller. If you have a replacement charge controller on hand, it can be hooked up immediately and it will charge the battery if the voltage is not too low.

Water & Leaks

Receivers are stored in heavy-duty bins (typically Action Packers) to keep water out and when not modified are pretty good at keeping the interior dry. The most important part of keeping the inside dry is careful routing of the antenna and other cables into the bin when it is closed up after each inspection and data download. Routing the cables into the bin required small modifications to the bin that may allow a small amount of water into the interior of the bin. If there is water accumulating in the bottom of the bin the simplest solution is to drill a 1⁄4 inch hole in one or two of the lowest corners in the bin. If the leaking is more serious, it might be necessary to place foam weather stripping in the area where the bin was modified to route the cables into the bin.

The Receiver

If the station is not connected to the internet, not only does the data need to be downloaded, it should also be checked to make sure it is collecting data correctly. Generally, you will not need to worry about this section if your receiver is networked because all the same information should also be available online.

This section will vary widely based on the type of device being used_._ Select a tab below to view information related to your device:

Cables and wires

Loose Connections/Shorts

While the Motus stations have been well constructed, nothing is perfect. Loose connections, disconnected wires, and/or shorts, are an infrequent gremlin that may be encountered. If something is not working look for loose connections. Solution of the problem can be as simple as identifying where the loose wire belongs and then securely reconnecting it. Sometimes, the solution is often as simple as disconnecting and then reconnecting the suspected loose connections. Shorts are harder to locate and may require additional assistance.

Having a multi-meter on hand can be very handy to trace shorts. By measuring resistance ('ohms' or 'Ω') you can identify whether two points are electrically connected (zero resistance) or not (infinite; sometimes displayed as a '1' on the far left of the screen).

Chewed or cracked insulation

The plastic insulation covering a cable or wire protects it from water ingress. Even tiny cracks can slowly cause issues by increasing electrical resistance, thereby reducing signal transmission and voltage.

To check for damage, run your hands along the length to feel for any disruption in the smooth surface. Critical locations to check are where the cables are fitted into the bin (usually via an elbow pipe joint) and wherever cables are closest to the ground on the outside of the bin.

Tag Test (optional)

If possible, we recommend you keep an activated tag test on your person at all times while visiting any station. This can provide valuable information about the stations operability without much effort. It does not necessarily measure the receptability of all antennas equally, but it's better than nothing. For a more accurate method for measuring station antenna ranges, see below:

Station Inspection Checklist

A prepared checklist below has been designed for stations in North America and may apply to others.

Below is a Word DOC version of the same checklist which can be modified:

Antennas are finely-tuned instruments that can easily be damaged without noticing. Proper inspection of antennas at the time of installation during regular maintenance checks ensures your antennas operate the expected frequency and sensitivity. Both the antenna and coaxial cable are passive devices, meaning they do not require power to operate and instead are designed to carry radio energy from the environment to the receiver.

About Antenna Tuning

Antennas used in the Motus are tuned to listen to a narrow band of frequencies near the 'nominal' frequency (the frequency at which tags are manufactured to emit a signal). This helps reduce the amount of environmental noised being received. A poorly-tuned antenna will receive more noise and as a 'louder' signal than the real tag pulses they are built to detect.

About coaxial cable

Coaxial cables carry the signal from the antenna to the receiver with two conductors: central core and a coaxial shield, separated by an insulator. The coaxial shield protects the central core from interference. A damaged coax cable or connector can result in loss of the signal from the antenna and/or increased noise.

Assessing Tuning Frequency using the NanoVNA

Estimated antenna detection ranges (“”) are purely theoretical and based on ideal conditions so they do not actually reflect the true ranges or shapes of any real antenna (Taylor et al 2017; Crewe et al. 2019). The actual range of an antenna is not easy to calculate because it depends on several factors such as: transmitted signal (by a tag), antenna type and orientation, length and type of coaxial cable, receiver type, and environmental conditions. Best estimates of mean or max antenna ranges are based primarily on biological data when simultaneous detections are recorded by antennas from different stations.

Test tags have been used to try and get estimates of antenna ranges in specific situations (Crewe et al. 2019) and in drone tests (Tremblay et al. 2017; Desrochers et al. 2018; Moore 2020).

Test tag trials can take a lot of time and are not always necessary beyond simply confirming the station is working and an antenna capable of detecting tags nearby. The amount of information you require about antenna range will differ depending on the purpose of your station and the information found in trials may not be representative of actual antenna performance. It is also important to understand the physical limitations of antennas if they are surrounded by trees, or if there is a building or hill in the line of sight that may not always be apparent. Free tools such as and can be used to find the ‘viewshed’, or line-of-site, of any given point and altitude.

Before you get started you should know that it is extremely difficult to emulate the performance of tags as they exist on living animals, the heights and flight directions of potential animals, and antennas, stations detecting living animals.

The following are suggested methods should you like to try and test the local range of a station and antennas.

Tag Test Methods

Supplies needed

• Lotek or CTT tag (activated)

• GPS with tracking on (a phone can work). Make sure units are set to LAT/LNG (WGS84)

• A stick or other non-conductive rod

• Dummy body: A small fruit (grape or clementine), tubed meat (sausage, hot dog), or frozen dead animal. Differences between these objects are not well tested - take your pick.

• Water bottle

• Optional: helium balloon and lots of string

• Optional: a drone

Making a dummy

• Take your activated tag and affix it to the dummy body using tape or string.

  • The purpose is to simulate the water content (i.e., capacitance)

    of an animal that is roosting such that the tag transmits a

    signal that resembles one coming from an actual bird. Keep in

    mind this is purely based on theory and is not an actual

    substitute for a real animal.

• Make sure the antenna hangs off the dummy in a similar orientation you’d expect it to be on your study species.

• This is required to stimulate tag performance for Lotek tags. Performance of CTT tags is not dependent on being affixed to an animal.

Ground simulation

To simulate an animal on or close to the ground, affix the dummy animal to a stick.

Flight Simulation

To simulate an animal in the air, affix the dummy animal to a helium balloon. Note: balloons made from metalized mylar might impede signal transmission.

Conducting the test

• With the tracking on, ensure your GPS has your location so that you can later download your track and correlate it with your tag detections. You may want to download a track ahead of time to make sure you know it works.

• While holding either the stick or the balloon, walk in concentric circles around the station of growing radius while trying to keep the tag at the same vertical position the whole time.

• Optionally, you can do this with a drone but don’t ask us how to fly it!

Analyzing your results

• Download your GPS track and extract the timestamp and latitude/longitude for the entire test.

• • When using the ‘tagme’ function, make sure you enter the serial

    number of the receiver you’re testing as the ‘projRecv’

    argument, like so:

tagme(projRecv = “SG-####RPI3####”, new = TRUE)

• You can now correlate your tag’s position with when detections

  occurred.

Notes

You may be able to test two tags at different vertical positions simultaneously, but if they have the same burst interval there’s a good chance you’ll run into issues with aliased tags. I won’t go into too many details about them here, but essentially aliased tags are false detections that occur when two real tag detections overlap. To avoid this, just make sure you offset each tag activation such that there are at least 0.3 seconds between bursts.

References

What is a tag or radio transmitter?

When most people use the word “tag” usually they’re talking about a clothing label or a sticker on a banana, but more generally it’s a type of marker which identifies the item in some way. This is no different from the way we use the word except in this instance we are using a radio transmitter as a marker. A radio transmitter is an electronic device which sends information through radio waves, similar to radio stations used to broadcast music to your car. The radio transmitters used in the Motus Wildlife Tracking Network are specially designed to be as small and lightweight as possible, allowing scientists to attach them to small animals without harming them. The signal transmitted by these transmitters, or “tags”, contains a special code which uniquely identifies the device. This signal is picked up by radio receiver stations which are placed in strategic locations across the globe. To Learn more about these receiver stations, click here.

What types of tags are there?

There are two main types of signals transmitted by radio tags used in the Motus Wildlife Tracking Network.

• Lotek Radio Tags use On-off Keying (OOK) to encode the tag ID within the signal. .

• CTT Radio Tags use Frequency-shift Keying (FSK) to encode the tag ID within the signal.

Lotek Radio Tags

To encode a unique ID, Lotek radio tags transmit a series of 4 pulses at a single frequency (166.380 MHz in the Americas; other regions differ).

Tag Pulses

A tag pulse consists of a single, 20 millisecond (ms) long radio transmission sent by the tag. Individual pulses are the raw data that SensorGnome receivers record.

Pulse Intervals and Bursts

A pulse interval is the time between two successive pulses. It is measured in milliseconds (ms). Tags emit four pulses at a time, together making a burst. The pulse interval is what we use to encode the Lotek Tag ID. This is measured to a high level of precision, allowing for just 1.5 ms of variation summed across all pulse intervals in a burst.

Note: these pulse intervals do not reflect properties of real tags are intended for demonstration purposes only.

Burst Intervals

A burst interval is the timing between successive bursts. It is measured in seconds.

Animation

CTT Radio Tags

To encode a unique ID, CTT radio tags transmit a signal that oscillates between two frequencies, 434 MHz and 433 MHz, to encode digital 1's and 0's. A total of 32 bits can be encoded in a single transmission, making it theoretically possible to encode over 4 billion unique IDs. A plot of this signal over time looks like a sine wave that flips between two different frequencies, like in the image below.