SensorGnome User Guide
  • SensorGnome V2
  • SensorGnome V1 (Legacy)
  • Introduction and Overview
  • Connecting to your SensorGnome
  • The Web Interface
  • Establishing an FTP connection
  • Downloading detection data
  • Uploading detection data
  • Installing and updating SensorGnome software
  • Data syncing over the Internet
  • Appendix
    • What to bring
    • Underpowered SensorGnomes
    • Connection and folder path cheatsheet
    • Configuring the SensorGnome frequency
    • CTT LifeTag compatibility (dual-mode)
    • CTT Motus receiver dongles for 434 MHz (dual-mode) capability on SensorGnome
    • Anatomy of a SensorGnome
    • Installing BeagleBone drivers
    • Restoring BeagleBone drivers on Windows
    • Recovering a BeagleBone that can no longer be reimaged
    • Accessing BeagleBone as a network drive
    • Connecting to a BeagleBone using an Ethernet cable
    • Using Bonjour Browser to find the IP address
    • Uploading a local tag database
    • Reflash FUNcube dongle firmware
    • Motus data file formats
  • How to install the new SensorGnome software
Powered by GitBook
On this page
  1. Appendix

CTT LifeTag compatibility (dual-mode)

PreviousConfiguring the SensorGnome frequencyNextCTT Motus receiver dongles for 434 MHz (dual-mode) capability on SensorGnome

Last updated 8 days ago

You are viewing the V1 Legacy SensorGnome user guide. This software has not been updated since 2018.

By default a SensorGnome is capable of detecting only Lotek Nanotags. However by applying a software patch a SensorGnome can also detect CTT LifeTags/ PowerTags. We refer to SGs that are listening for both tag types as “dual-mode” SensorGnomes.

You will not be able to use the same dongles for CTT tags as you use for Lotek tags. For CTT-compatible dongles, contact or Birds Canada.

1) Download the CTT compatibility patch from the link below

  • Raspberry Pi.

  • BeagleBone. . Dual-mode function for BB SG's has not been fully implemented. It works, but there are some steps required on the back-end to enable this. If you wish to make a BB SG dual-mode, please and we will assist you.

2) Rename the downloaded file to sensorgnome_update.tar.bz2

3) Connect to the SG and navigate to the ubootfolder

Raspberry Pi uboot folder

  • FTP connection (e.g. in FileZilla)

    • /dev/sdcard/uboot

  • Directly on MicroSD card when removed from powered-down RPi

    • /uboot

BeagleBone uboot folder

  • FTP connection (e.g. in FileZilla)

    • /boot/uboot

  • Shared network drive (e.g. in Windows Explorer)

    • \\192.168.7.2\root\boot\uboot\

If you keep a copy of the Raspberry Pi SG software on your computer, you can simply copy in the renamed CTT patch into the uboot folder on your computer. Now every time you load this software onto a Raspberry Pi, it will be dual mode by default.

4) Copy the renamed software patch into this folder

5) Power down and reboot the SG.

6) Once powered up, connect to the SG and open the Web Interface

If the process was successful you should see any attached CTT dongles in the "Devices" pane of the Web Interface. However, they will not be displayed in the "What I'm doing now" pane. Additionally, both of these panes will only be displayed if there is a Nanotag-compatible dongle, such as a FUNcube dongle, attached.

It's possible that you will also see CTT tag IDs in the Live Known Tags section. These may be the signals of actual tags in the vicinity, or they be the product of background radio noise that happens to resolve to a tag ID, which is still useful in confirming that the SG is in fact listening for CTT tags. CTT tag hits will never show up in the Live Pulses Pane as this pane only displays radio pulses consistent with Lotek tag signals.

It sometimes requires two complete boot cycles of the SG for this process to succeed, so if you don't see your CTT dongle even though you have both a FUNcube and CTT dongle attached, reboot and try again.

CTT
2021-07-09-rpi_ctt.tar.bz2
2018-12-06_sensorgnome_beagle_ctt_update.tar.bz2
contact Motus
Web Interface of dual-mode SG. Note: there may not be any CTT tag IDs in the Live Known Tags section