Release History

Release HistoryEdit

2017 May 24: update to support detection of Cornell tags

This update is for users who want their (beaglebone-based) SG to detect tags made by Gabrielson & Winkler
at Cornell University.   It should only be applied to a sensorgnome which is already running a version of the 
software from 2016 or later.  Details about the tags and support for them is here.

Update is here and installation instructions are here.
Notes: 

• this update might require a second reboot before it correctly recognizes the XCVR.
• this update breaks support for revision "D1" of the DLink DUB-H7 USB hub - bug john for a fix.

RECOMMENDED:
2017 March 6: image and update to support revision "D1" of DLink DUB-H7 USB hub. 

Fixes this problem:  only one funcubedongle (in port "0") appears on the web interface, even though
 several funcubedongles are plugged into the USB hub.

Only users with the revision "D1" hub need this update, but it is okay to install on any SG running a
version of the software from Aug. 2015 or later.  After installing this update and rebooting TWICE,
the SG will support the D1 hub as well as any older supported hub. 

(Note: there is an unknown revision of the DLink DUB-H7 USB hub which is not supported at all by linux
or sensorgnomes.  If you have such a hub, you will see  no USB devices on the web interface.  We don't
have a fix for this problem.)

The update (for SGs already running a 2016 version of the software) is here and installation instructions are here.

The image is here and installation instructions are here.

2017 Jan. 26: image and update: customized sleepable version

Most users should not use this version.  It is a custom release with these features:

• scan and sleep scheduling; only supported via changes to deployment.txt
• only works with funcube attached directly to beaglebone
• requires GPS cape with a fresh battery to retain accurate time

The image is here and installation instructions are here.

The (large) update is here and installation instructions are here.  This update can only be used if your
SG is already running the 2016 Sept 13 software.  It requires two reboots before it takes effect.

2016 Sept. 13:  image: default to not running a DHCP server on ethernet

The default ethernet set-up reverts to the original semantics:  if the SG is booted with a live
ethernet cable attached, it will try to connect to our server. For almost every user, this is what you want.

A very small number of users might want to be able to connect their laptop directly to the SG
via an ethernet cable, instead of by using the USB cable.  Only those users should delete the file
WIREDNET.TXT on the SG boot drive at \\192.168.7.2\boot
Having done this, the SG should not be plugged into an institutional ethernet jack, e.g. at a
university or offiice.   If you deleted WIREDNET.TXT and then decided you need to connect
the SG to the internet for remote troubleshooting or data sync, recreate a file called WIREDNET.TXT
on \\192.168.7.2\boot  (or \\192.168.9.2\boot if connected via ethernet cable).  The contents
don't matter:  the SG just checks for existence of this file.

The image is here and installation instructions are here.

2016 Sept. 2: fix bandgap temperature and formatting from 2016 June 17 version

Small update to fix the broken bandgap temperature on the web interface, and clean up an unterminated
<b> tag.

The update is here and installation instructions are here.

Anytime update: reset SG bootcount to 1000

This tiny update sets the SG bootcount to 1000.  This is only needed if your SG is writing
files with "-000NaN-"  in the filenames, instead of the actual boot count.

The update is here and installation instructions are here.

2016 Aug 25: optionally prevent SG from running DHCP server on ethernet

(optional incremental update to 2016 June 17 update)

This update fixes a problem with the 2017 June 17 update for those few users with SGs permanently
attached to wired ethernet.  Installing this update prevents the SG from serving IP addresses to other computers
on the local network.  Without this update, other computers on the local network might lose internet
connectivity.

Note:   If you install this update, you won't be able to connect your laptop to the SG by ethernet cable.
This can be undone by deleting the file WIREDNET.TXT from the network drive at \\192.168.7.2\boot

i.e. presence of the file works like so:

The update is available here:

2016-08-25_sensorgnome_update.tar.bz2

and installation instructions are here.

2016 July 6: allow user 'root' FTP access so log files can be downloaded

(incremental update to 2016 June 17 update)

After installing this update and rebooting, FTP access can be obtained with user "root" (password "root")
which will let you download log files via FTP.

You can update a beaglebone from the 2016-06-17 version using this update file:

2016-07-06_sensorgnome_update.tar.bz2

2016 June 17: access SG data files with FTP, via USB or Ethernet Cable

(this update replaces the 2016 June 9 update, and can be installed on top of it)

Some users are unable to connect to the SG using a USB cable, because drivers to do so
are buggy or cannot be installed on a government-issued computer.  For the same reasons,
some users are unable to download the SG's data files using the network drive.  This update enables
connection using an ethernet cable, and access via FTP.  After installing it, you can use any FTP client
on your computer to access the SG's data files.  Most web browsers can do this.  You should use
an FTP client that can download entire folders at a time.  We recommend the FireFTP extension to
the Firefox browser, which can be installed using Firefox's "Add-ons" menu.

You can update a beaglebone from the 2016-02-02 or later version using this update file:

2016-06-17_sensorgnome_update.tar.bz2

or you can (re-)image your beaglebone to this version using an image file:

sensorgnome_image_2016-06-17_12-56-03.img.7z

You can also operate a broken beaglebone with this rescue image:

sensorgnome_rescue_image_2016-06-17_12-56-03.img.7z

which works like a regular image, except it doesn't try to re-image
your beaglebone.  You need one rescue image SD card per broken
system, since the card has to be installed for the SG to work.

Installation instructions for the images and for the update.

Notes:

• this update also lets you access the boot drive via FTP, to download / upload the deployment.txt and SG_tag_database.csv files
   
• you must set your FTP client to use "Passive" mode (browsers do this automatically)
   
• this update includes the updates of 20 May, 4 May, 21 April, and 28 April.

Here's how to connect to your SG after you have installed this update and rebooted it:
 

2016 May 20: update and image; connect with Ethernet or USB cable

Some users are unable to connect to the SG using a USB cable, because drivers to do so
are buggy or cannot be installed on a government-issued computer.  This update and image
permit users to connect to an SG in two ways:

SG Interface
(use web browser)

Data Disk
(open as network drive)

Boot Disk
(open as network drive)

 Connection by:

USB cable
Drivers required
on your computer.

http://192.168.7.2

\\192.168.7.2\data

\\192.168.7.2\boot

Ethernet cable
No drivers needed!
Your computer's wired 
network adapter must be 
set to automatically
 obtain its IP address,
 which it probably is...

http://192.168.9.2

\\192.168.9.2\data

\\192.168.9.2\boot

Note:

Image file:

         sensorgnome_image_2016-05-20_15-59-45.img.7z

This image file includes the updates of 4 May, 21 April, and 28 April.

You can instead update from the 2016-02-02 image using this update file:

2016-05-20_sensorgnome_update.tar.bz2

Installation instructions for the image and for the update.  

Details:

With this image installed, you can connect a laptop to the SG's web interface and data driver using
a network ("ethernet") cable.  This does not require installing beaglebone drivers on the laptop.  The
laptop wired network adapter must be set to automatically obtain its IP address.  Also, this should
work even if you hot-plug the ethernet cable (i.e. plug into an already-running SG); you might need
to wait a minute for the ethernet connection to come up.  Ethernet cable connectors are not as robust
as USB cable connectors, unfortunately. 

If the other end of the ethernet cable is already plugged into a wall jack or router when the SG boots,
then it will still try to connect to our server for remote troubleshooting.

2016 May 4:  update: fix bug in funcube watchdog affecting a few SGs

Update file: 2016-05-04_sensorgnome_update.tar.bz2

Installation instructions

The fcd_watchdog runs every 2 minutes to make sure all attached funcubes are operating, and restarts
any which are not.  fcd_watchdog is a one-line script, but uses a program called nc to connect to the
funcube data capture program.  Unfortunately, some SGs seem to have the "busybox" version of nc installed
in /usr/bin, which is trumping the correct version installed in /bin as part of the sensorgnome software.
I don't understand how this has happened, as the SG software installation is supposed to delete all
pre-installed software.  In any case, if your SG has the 2016-02-02 software release, and is still showing
antennas stalling, then try this update.

2016 Apr 28: optional update: show "core" temperature and LAN MAC address on web interface

Update file:  2016-04-28_sensorgnome_update.tar.bz2

Installation instructions

This update displays the "bandgap temperature" on the SG web interface.  The value is re-sampled each time
the web interface page is manually refreshed.   This is an estimate of the temperature in
the SG's main processing chip.  The beaglebone is only rated to operate at bandgap temperatures up to 90° C.
Higher temperatures will likely cause system failure.  

This update includes the 21 April update, so it also displays the LAN MAC address on the SG web interface.

2016 Apr 22: update ONLY for users of the Huawei E398 turbostick with Deutsche Telekom

Update file:  2016-04-22_sensorgnome_update_for_Huawei_e398_deutsche_telekom_turbostick.tar.bz2
Apply this update to an SG running the 2016-02-02 image to use this device.

2016 Apr 21: optional update: show LAN MAC address on web interface

Update file:  2016-04-21_sensorgnome_update.tar.bz2

Installation instructions

This update displays the Beaglebone ethernet adapter's MAC address on the SG web interface,
for those few users who might need to supply this information to their internet providers.

2016 Apr 13: update ONLY for users of the Huawei E8372 turbostick with Bell Canada

Update file:  2016-04-13_sensorgnome_update_for_Huawei_e8372_bell_canada_turbostick.tar.bz2
Apply this update to an SG running the 2016-02-02 image to use this device.

2016 Feb 2:  New software image and update - Recommended for all deployments

Update file:  2016-02-02_sensorgnome_update.tar.bz2 
This updates a unit from the 2015-08-27 version to the 2016-02-02 version.

If your SG has a software version older than 2015-08-27, you should instead re-image it
with the following file:
Image: sensorgnome_image_2016-02-02_13-00-09.img.7z

Installation instructions for the image and for the update.

Changes:

• fix problem preventing imaging of newer Beaglebone Black, especially from Element14.com
• have funcubedongle show up in device list at slot 0, even when a GPS cape is installed

2015 Oct 16: optional update for LAN access to SG

Update file:  2015-10-16_sensorgnome_optional_update.tar.bz2

Installation instructions

This allows you to connect to your SG via  a network cable.  However, you will need to know the IP address the SG has
been assigned, either by the router or by your own computer.  This is only intended for local area networks,
and should not be applied to an SG which will be connected directly to the internet, as it is not secure: anyone anywhere
could modify files on your SG.  This is identical in purpose to the 2015 Mar 16 update, but modified to apply
to the 2015 Aug 27 image.

2015 Aug 27:  New software image and update.

Update file: 2015-08-27_sensorgnome_update.tar.bz2

Image: sensorgnome_image_2015-08-27_13-18-25.img.7z

Installation instructions for the image and for the update.

This update replaces the broken 28 July update, and should fix several reliability issues.
While it has not undergone as much testing as we'd like, it has run without issues on 5
SGs (both beaglebone blacks and whites) with a total of 14 funcubes for 17 days,
with some stress testing.   It will be the version used to update the Motus Ontario and Atlantic
arrays over the coming weeks.  Any bugs discovered will be reported to the sensorgnomads
mailing list and fixed as soon as possible.  The update file should work on any late-2014 version of
the SG software, bringing it fully up to date, but those running versions from 23 May 2014
or earlier should re-image their SG, rather than using the update.

Unlike previous images, if this one is used to re-image an SG, it will preserve existing
deployment.txt, network.txt, and SG_tag_database.csv/.sqlite files. 
(The update file also preserves these user files, as usual.)

This update will reprogram all attached funcubedongles to the 48 kHz sampling firmware.

\\192.168.7.2\root         (Windows)

   or

smb://192.168.7.2/root     (OS X, linux)

   bin
   boot
   dev
   etc  ---->  ... 
   ...         cron.d   ---->  ...
               ...             fcd_watchdog     ## delete to prevent automatic restart of funcubes
                               usb_watchdog     ## delete to prevent automatic reboots of SG when no USB devices are found
                               ...

2015 July 20: update to permit more than 3 funcubes per SG

Update file: 2015-07-20_sensorgnome_update.tar.bz2

Installation instructions here.  After uploading the update file to the SG, power down the SG, attach all
funcubes you wish to use with it, then power back up.  When you then visit the web interface,
all funcubes should be operating at a hardware frame rate of 48 kHz, as shown in the
What I'm doing now table.  Booting will take approximately 25 seconds longer for each
funcubedongle that needs to be reprogrammed, but this happens only once per FCD.

This update should work on any version of the 2014 software release.

After installation, whenever the SG boots, any attached Funcubedongle
Pro Plus will have its firmware updated to do sampling at 48 kHz
(rather than the default 192 kHz). This permits up to 6 Funcubedongle
Pro Plus dongles to be used on a single SG.  The firmware update
persists across reboots, even if the funcubedongle is subsequently plugged into a
different SG. 

    {
        "info": "default deployment",
        "who": "who is responsible for this deployment",
   

    {
        "info": "default deployment",
        "option": "NO_AUTO_FCD_UPDATE",
        "who": "who is responsible for this deployment",

2015 May 1: recommended upate to 2014 Dec 11 release; fixes problems with parameter change scheduling  

Update file: 2015-05-01_sensorgnome_update.tar.bz2

Image: sensorgnome_image_2014-12-11_11-57-00-rev2.img.7z

Installation instructions for the image and for the update.

This is now the recommended image of the 2014 software release.  A serious bug in frequency switching
is fixed.  The tag database can now contain tags from the same project with the same ID but different burst interval,
and these are displayed correctly in the web interface.  Users can install either the .sqlite or the .csv version
of the tag database.

2015 Apr 23: optional update to 2014 Dec 11 release to distinguish between
                      different tags with the same ID in the web interface

Update file:  2015-04-23_sensorgnome_update.tar.bz2

Installation instructions

For users deploying more than one tag with the same ID a software update is required in order to distinguish
between those tags in the web interface.  This just allows you to distinguish between tag detections in the field.
If you only care about distinguishing between those tags when sensorgnome.org processes the raw data from
your receiver, then you do not need to apply this update.  The upcoming 2015 software release will include
this fix. 

Note:  Users applying this fix will also need to install the ".sqlite" version of their tag database on the receiver,
rather than the ".csv" version.

2015 Apr 13: bug fix to 2014 Dec 11 release for very recent Beaglebone Blacks

Recent Beaglebone Black computers have a slightly different flash memory chip capacity, which confused
the SG software.  This bug has now been fixed in a way that should prevent it happening again with any
subsequent changes to the flash memory.   If you imaged a new beaglebone, and found that it would
not work correctly with a micro SD data card installed, you will need to do two things:

• use the image below to re-image your beaglebone. 
   
• completely reformat your micro SD data card, using one of the programs available here.

(The bug caused the SG to reformat and copy its software to the data card, in a way that prevented
its use for storing data.  With this bug, if you image the beaglebone and then reboot with a blank
micro SD card, you will not be able to connect to the web interface.)

Thanks to Michelle Stantial for help in diagnosing and correcting this problem.

Image: sensorgnome_image_2014-12-11_11-57-00-rev1.img.7z

The 2015 Mar 16 update can still be applied to the revised 2014-12-11 image.

Barring other show-stopping bugs, this is the final release of the 2014 SG software. 
 

2015 Mar 16: optional update to allow connecting to the SG web interface and file server
via a network cable.

Update file:  2015-03-16_sensorgnome_update.tar.bz2

Note: above link corrected on 2015 03 28.

Installation instructions

This allows you to connect to your SG via  a network cable.  However, you will need to know the IP address the SG has
been assigned, either by the router or by your own computer.  This is only intended for local area networks,
and should not be applied to an SG which will be connected to the internet, as it is not secure: anyone anywhere
could modify files on your SG.

2014 Dec 11:  image and update to support the Compudata GPS cape (fixed)

Image: sensorgnome_image_2014-12-11_11-57-00-rev1.img.7z

Update file:  2014-12-11_sensorgnome_update.tar.bz2

Installation instructions

Note:  the update requires 2 reboots (rather than the usual 1) before it takes effect.

Replaces the 2014-09-03, 2014-08-27, and 2014-09-10 updates, which were broken.
The most recent fix corrects the hang-on-boot problem with the 2014-09-10 update when
a GPS cape was not installed.

This is for the initial model of the cape, which does not have an embedded serial number
and so is not (yet) an official beaglebone cape.  It also supports the Adafruit GPS breakout
board, as described here.  Users of the standard USB GPS or of the older, non-cape PPS GPS
do not need this update, but it should not cause any problems.   This update includes the changes
from the 2013 Aug 13 update, and slightly reformats the device list to better distinguish
between devices attached directly to the beaglebone and those connected via a USB hub.
The update must be applied to the 23 May image.

2014 Aug 13: update to support attaching a funcubedongle directly to the beaglebone without a USB hub

Update file:  2014-08-13_sensorgnome_update.tar.bz2

Installation instructions

Problems fixed:

If you tried to run a stripped-down sensorgnome without a USB hub, and with a funcubedongle attached directly
to the beaglebone computer's USB port, the live tag window would not show any detections and the device
list does not show the funcube.

2014 May 23: new images with all fixes to date

Note: if you are deploying to a remote site with little chance of revisiting during the field season,
and your SG computer is not the Beaglebone Black Revision C (which requires the May 23 or later
version), please use the March 03 version instead - it has seen longer field testing.

Image: sensorgnome_image_2014-05-23_17-23-36.img.7z

Installation instructions

Changes:

• in addition to updates since last image, this image should now work on the BBB Rev. C
  as well as all previous Beaglebone models
  [thank-you to Christa DeRaspe for help with this]
   

2014 May 15: (for testing): possible reduction in file size at noisy sites

Update file:  2014-05-15_sensorgnome_update.tar.bz2

Installation instructions

Uses a more numerically stable pulse detection algorithm, which may result in smaller file sizes
at noisy sites.

2014 May 13: update to fix 'off-by-one' bug in periodic schedules

Update file:  2014-05-13_sensorgnome_update.tar.bz2

Installation instructions

Problems fixed:

If a periodic schedule was created in deployment.txt to e.g. switch VHF telemetry frequencies, the periods were not applied to the corresponding parameter values, but rather the next one.  For example:

"schedule": {
              "type": "periodic",
              "states":  [ 150, 166 ],
              "periods": [  30,  10]
             }

would incorrectly schedule listening as 10 seconds @ 150 MHz alternating with 30 seconds @ 166 MHz. [incorrect behaviour]
The update corrects the behaviour to:   30 seconds @  150 MHz alternating with 10 seconds @ 166 MHz, as clearly intended.

2014 May 12: update for PPS-GPS users; faster PPS sync

Update file: 2014-05-12_sensorgnome_update.tar.bz2

Installation instructions

• modifies configuration for chronyd program responsible for synchronizing system clock to GPS;
  the PPS GPS clock is high quality, and syncing can occur faster than allowed by default chrony configuration

2014 May 9: new image with all fixes to date

Image file:  sensorgnome_image_2014-05-09_17-10-18.img.7z

Installation instructions

Problems fixed:

• no web interface, due to failure to obtain machine serial number; apparently I did not
  test the version of the 2014 April 29 release which ended up on the download site! 
  Apologies to all who struggled with that one. 
  Thank-you to Sarah Neima for help in troubleshooting this.

For those few users who installed the 2014 April 29 image:
Update file: 2014-05-09_sensorgnome_update.tar.bz2

• download this file and rename to sensorgnome_update.tar.bz2
   
• copy to the shared network drive at \\192.168.7.2\boot or copied to the SENSORGNOME
  disk of a beaglebone white, but only for those units on which you installed the 2014 April 29 image.
  The usual web-interface method of applying this update does not work (because the web interface
  is broken in the 2014 April 29 version!)
   
• reboot the SG twice, waiting 2 minutes between reboots

2014 April 25: updates to signal acquisition and web interface

Update file:  2014-04-25_sensorgnome_update.tar.bz2
Installation instructions

Problems fixed:

• loss of chunks of incoming signal due to buffer overruns
• instability of web interface, especially in noisy environments
• partially broken Start/Stop listen controls for funcubedongle devices on web interface

2014 April 17: update for those (few) users with PPS GPS

(if you don't know what this is, you don't need it)

Update file:  2014-04-17_sensorgnome_update.tar.bz2
Installation instructions

Problems fixed:

• slow or inconsistent syncing of system time to PPS signal from GPS, even when the former is present

The fix increases the priority of the chronyd process (responsible for clock syncing) above that of the data acquisition processes,
and prevents chrony from selecting the non-PPS GPS times as the primary clock source.

2014 April 12: update for those (few) users recording raw radio signal in the lab

The update file is 2014-04-12_sensorgnome_update.tar.bz2 and update installation instructions are here.

Problems fixed:

• frequency setting for funcube telemetry radios was not being used if the enabled field of the raw option was
  set.  i.e. if the deployment.txt file had a section like this:

                "devParams": [
                    {
                        "name": "frequency",
                        "schedule": {
                            "type": "Constant",
                            "value": 166.376
                        }
                    }
                ],
                "raw": {
                    "enabled": true,
                    "chunkMinutes": 5
                },

then funcubes would not be set to listen at 166.376 MHz. 

• the web interface device list did not reflect manual or automatic changes to funcube listening frequencies
• manually setting the funcube listening frequency with raw recording enabled crashed the recording process

2014 March 3: first release for 2014 field season

Image file:  sensorgnome_image_2014-03-03_17-58-42.img.7z

This release has been tested in the field and is recommended for deployment at remote
telemetry locations where visits during the season are impractical. 
NOTE: users with the latest Beaglebone Black (Revision "C", shipped from May 2014 onward) must
use the 23 May version or later, not this version.

2014 Feb. 25: fix issue with remote registration and data upload

The register_sg and maintain_ssh_tunnel scripts are now run from a crontab, rather than when a network interface comes up.  The latter approach did not work reliably with wireless networks, and was less robust in dealing with broken leases on the router end.

2014 Feb 16: Fix how network.txt file is used.

Other issues from 2014 Feb 12 release remain.

2014 Feb 12: Single image for both Beaglebones (black and white); remote data upload

This is the first version to support both models of beaglebone from a single image file. 
The image can be written to 4, 8, 16, or 32 GB micro SD cards.  Space on the card not used by the download
will be reclaimed as data sorage space the first time the card is booted in a SensorGnome.

If either a wired internet connection, or a WiFi connection via the TP-Link TL-WN725N
USB adapter is found, then live tag, GPS, and status data are uploaded to the server at sensorgnome.org
via an encrypted connection.  This connection also allows us to remotely troubleshoot a sensorgnome.

Known issues are here.

2013 September 6: Beaglebone Black: update: support for using GWC 10-port USB hub

While we don't recommend using this hub due to bandwidth allocation issues, some older sensorgnomes have
them.  The Beaglebone White version of the software supports this hub, but the Beaglebone Black version
does not, until you apply this update.

2013 August 29: Beaglebone Black: update: force setting of clock from non-PPS GPS

For users whose sensorgnomes are not getting a correct date/time on the web interface even though
they are getting a GPS fix, this update will force the clock to be set.  Normally, we use third party
software (gpsd and chrony) to handle updating the system clock from the GPS, but this appears to
be problematic for the non-PPS GPS.

2013 August 29: Beaglebone Black: update:  support for USB hard drives

For users requiring hard drive storage (e.g. acoustic monitoring), this update adds drivers
needed to allow writing data to a USB hard drive formatted in Windows' NTFS
file system.  Just about any off-the-shelf PC USB hard drive comes pre-formatted with NTFS.
Without this update, hard drives might appear in the device list, but no data will be written to them
and their size and free space will not be shown. 

For this upgrade to take effect, you need to reboot the sensorgnome 2 times after applying the update. 
After the first reboot, wait until you can connect via the web interface before booting again.
("Boot" means disconnect then reconnect the power; always disconnect the USB connection
to the computer before disconnecting the power to the sensorgnome).

Note: only use a hard drive if you really need the storage - the power consumption is considerably higher than
that of a flash drive or micro SD card.

2013 August 28: Beaglebone Black: new image

Fixes various issues, such as not setting the system clock from a non-PPS GPS.
Use this to image new BBB sensorgnomes, and re-image any non-working BBB sensorgnomes.
No updates need to be applied to this image.

2013 August 16 - URGENT: Beaglebone Black: fix for broken plugin library

This bug prevents VHF telemetry from working!!  I inadvertently pushed out a broken
version of the plugin library.  The attached fix file should be saved as sensorgnome_update.tar.bz2
onto the SENSORGNOME drive that pops up when you put the BBB imaging disk into your computer.

2013 August 14 - Beaglebone Black: fix for inability to delete files on \\192.168.7.2\boot

This bug prevents users from deleting the existing deployment.txt and SG_tag_database.csv files
on the shared network drive at \\192.168.7.2\boot.  Even with this bug, users should still be able to
overwrite these files directly, by right-clicking on the file, opening it with WordPad (Windows) or
TextEdit (Mac), editing, then resaving.  The bug can be fixed by uploading the
update file attached below via the SensorGnome's web interface, as described here.
 

2013 August 03 - fix for frequency-switching bug

This bug affects users doing frequency switching, using either the white or
black beaglebone.  It can be fixed by uploading the update file attached below
via the SensorGnome's web interface, as described here
Details on the bug are here.

2013 June 12 - write your own SensorGnome microSD card

At long last, we've started putting disk images on the web for download, so that you don't have to
rely on us to burn cards for your SensorGnome.  Instructions are here.

2013 June 04 - Beaglebone Black

• we've moved the SensorGnome software to a distribution of Linux which supports
  the new Beaglebone "Black", as well as the original Beaglebone "White".  This and subsequent
  releases will be based on the armhf port of the Debian 7.0 Linux distribution.  We'll soon
  create a page with the full release and instructions on burning your own micro SD card.

2013 May 07 - broken update function

• users with the 19 April software: unfortunately, the 19 April release broke the update function,
  so you won't be able to apply subsequent fixes listed here.
  This probably affects only Taylor lab users.

2013 May 08 - bug fix

• bug fix: attempt to reconnect to GPS server was failing, so in some situations, GPS fixes
  were not being written to disk.  Symptom was no GPS fix visible in web interface despite
  correct date/time being displayed.  The fix can be applied to both the 26 April and 19 April
  releases, whichever you have.

2013 April 26 - release

• various changes; most users will not need this update.  Update file not yet available.

2013 April 19 - release

• bug fix: don't filter out pulses at negative offset frequencies
• web interface:
  • allow listening to a funcube device through your computer's speakers
  • live tag detection (from installed tag database; no filtering)

2013 April 08 - release

• initial release of SensorGnome software
• 10 deployments in coastal Nova Scotia
• 2 deployments on ships