Sensorgnome Update

Stations Receivers
,
1

Hi Gnomads,

Many thanks to Arne for the nudge. The SensorGnome project is far from dead, it’s just been quiet as we haven’t yet completed the objectives outlined in our update last spring. Nearly 800 active SensorGnomes are currently deployed in the Motus Wildlife Tracking System, and Sensorgnome software is running on an additional 79 Cellular Tracking Technologies SensorStations in the network enabling the autonomous monitoring of numerous tag-types and frequencies simultaneously.

It’s worth recalling that SensorGnome is intended to be an open-source, community-project with numerous supporters and developers. In reality, development has relied on a very limited pool of developers at Acadia University, Cellular Tracking Technologies, and Birds Canada.

Developers at Birds Canada have been continuing to work to understand, maintain and clean up original code and processes that make SensorGnomes tick, and have begun to implement a number of updates to improve functionality and reliability. In fact, we have made significant progress in our objectives, but little of it can be seen since so far these changes are mostly housekeeping, to ensure the SensorGnome software and servers remain robust.

We have informally set up a ‘working group’ to advise on priorities, progress, and ideally provide development support, but the group has not been very active as we don’t yet have software ready for testing. Admittedly our progress has been slower than desired primarily due to limited resources, the need to rebuild capacity and expertise on the software and hardware, and the complexities involved.

So, an update on our progress is below. If you have any problems, questions, suggestions, ideas for collaboration or support, please post to this group.

Luc Berrigan, Dale Floer, and the rest of the Motus team at Birds Canada.

What’s happening

Documentation:

Sensorgnome server software update:

  • Fixed some critical issues with server reliability

  • Various important updates to the sgserver environment including security updates

Sensorgnome software:

  • New software that contains standard support for CTT Tags/dongles (currently being tested)

  • Cleanup and modularization of the code to both make adding new features and fixing bugs easier.

Software Development:

  • New build environment in development that allows for easy ‘one-click’ software updates - no need to image/reimage cards for updates and fixes

  • New build environment that creates packages for Sensorgnome software, including automatic generation of install images: https://github.com/sensorgnome-org/sensorgnome-build

What’s planned

  • Software update that includes numerous bug fixes, universal support for any hardware (eg. all RPi models, SensorStations), additional devices (modems, dongles, etc.), improved web interface.

  • Further integration with Motus.org: monitoring, logging and alerting system for networked SG

  • Automated testing for entire system of networked SG’s

  • Testing and optimization of various dongles

  • RF fixes to improve detection of tags and rejection of noise.

Timelines

  • Timelines on all of the above are a little harder to predict and depend on available support, but stay tuned to this list for updates.
2

Hi Luc!

Sounds amazing what you are doing! Very promising! May I ask for a favor? It would be lovely when the Pi- based bug that the 6th antenna is not working well on a Pi becomes fixed. For test results, see the call of Bart Noort last year.

Many thanks and very sorry that I am very bad in programming, so I can’t help with this.

René

3

Luc,

The reply from Rene, reminded me to revisit your message and I’d like to echo his comment about the amazing work you guys are doing.

A question about how to collaborate, especially regarding the documentation. I see the documents are now in Word format on a Google Drive which is great for accessibility. If we have comments or suggested edits to the documents do you want us to make edits directly in the documents, email them to you, post them in this forum or some other way?

I see for example in the Motus Station Guide a comment from Stu suggesting adding a section on Lightning protection. As I initiated the recent discussion about lightning risks, adding a section about this is something that I could probably take on.

I also have a list of changes / new features to add to future SensorGnomes, what would be the best way of sharing those with you.

Again many thanks for all you are doing.

Kind regards.
EAP

Ewan A. Parsons
PI #291 & #307

4

Hi René and Ewan,

We are still working on the build environment for SensorGnome software, but once that’s complete we will begin looking into bugs like these. Unfortunately, we don’t have an exact timeline as there has been a lot of work needed just to repackage the software.

We are keeping track of these requests and once we are ready to fix bugs and add features will focus on our time on what is most needed.

In terms of collaboration on guides, it would be much appreciated if you’re interested in contributing. We are currently building guides through GitBook which interfaces with GitHub and can be forked like any other repository. You can find these repos below:

Motus Station Guide: GitHub - leberrigan/MotusStationGuide: Repo for GitBook referencing

SensorGnome Guide: GitHub - j-sayers/SensorGnomeUserGuide

In order to ensure we don’t duplicate our effort, it’s helpful to send us a note to let us know what section you will work on and we can coordinate from there. If you’re not comfortable using GitHub, let us know and we can arrange other means for you to contribute content.

Many thanks,

Lucas Berrigan

5

Hi Lucas,

Are there already signs for a new software release? The Pi 3B is horrible to find yet…

René

6

Hi Team.

Anyone tried booting on a 3B compute module?

Has anyone tried the build script?
GitHub - sensorgnome-org/sensorgnome-build: Tools and files needed to build Sensorgnome images and packages.

looking at upstream rpi-gen open issues, buster and onward builds may be broken on non arm hosts?

I’ll be having a look at a build before end of next week.

Additional:
Alternate I’ve been thinking about a workaround,
64 bit ARM capable raspberry pi processors can run KVM.
Anyone tried booting the rootfs in a VM and using USB passthrough?

Regards,
Evan.

7

I’m trying to get familiar with the workings of the SensorGnome software (in the context of Motus) and I’m wondering what the status of the “new release” is? Looking at the github repos I see no activity since about Feb this year… Maybe I’m looking in the wrong place? Is anyone currently doing any work on this?

8

I thought I’d post a short update here. I’ve been working (with the Motus team) on a complete software update for SensorGnomes. This includes the latest Raspberry PI OS, new USB port mapping, and completely new Web UI allowing full web-based configuration. Currently only rPi3, rPi4, and rPi Zero-2W are supported. The current status is that I have an alpha release that BofC is providing feedback on (and that is not ready for deployment). I do not have an ETA for a beta release: it depends on feedback and on my volunteer time availability. My primary purpose in posting here is to let everyone know that all discussions about features/functionality/feedback is happening in the Motus slack (#sensorgnome channel), so if you want to chime in please connect there.
Thorsten

9

So, one year has passed since my latest request and I still do not see any schedules for updates on the Sensorgnome firmware. My interpretation of the silence is that nothing happens, or that things are happening at a very slow pace. I would love to be proven wrong!

so I ask again: when will there be an updated firmware? When will e.g. Raspberry Pi 4 be supported?

tisdag 18 januari 2022 kl. 19:38:56 UTC skrev tvone...@gmail.com:

10

Hi Arne,

An option is the CCT option. That is, as far as I hear the reviews, a
very solid and updated version of a SG.

René

11

Hi Arne, progress has actually been made… I rewrote/repackaged the entire SensorGnome software using the latest Rasperry Pi OS, revised and upgraded the security model, and rebuilt the web interface. It’s all working quite well and BofC and I are currently “acceptance testing”. We’re having some long term stability issues: SGs don’t always boot correctly and become inoperational. I realized that without decent remote monitoring capability it’s going to be difficult to pin this down so I’m currently adding that type of functionality.
All the work is open source as usual but I’ve not been announcing anything 'cause there are still known issues to fix that I’d rather not have others run into and get frustrated. If someone with technical expertise would like to try things out I’m happy to provide pointers and instructions.
The new software build supports rPi3, rPi4, and rPi Zero-2W, it supports the usual radios, the Adafruit GPS HAT as well has the SixFab UPS and GPS HATs.
Cheers,
Thorsten
NB: I’m a volunteer not affiliated with BofC but I’ve been working very closely with them and support from them.

12

Hej Thorsten, that is good news, and I am sure you are doing a tremendous job with the update (I am having the same role as you in various project, so I have a feeling for the workload involved…). However, the old software is also causing quite a bit of frustration, and it would be nice to have an official roadmap and regular info updates from BofC, so that we have a clearer view of the future for the SG system.

tisdag 27 september 2022 kl. 16:49:26 UTC skrev tvone...@gmail.com:

13

Arne, as far as I can tell, there is exactly zero manpower to do anything with the old software build. The new one is functional and available and it would be great if more people with technical skills could test it and provide input. I haven’t announced anything 'cause I’ve been focusing on some other projects for the past 2 months and I have the sense that few people here have the motivation and time necessary.
One of the most difficult changes to get right on the new version is security. All communication is now encrypted but getting HTTPS to work on embedded devices is a total mess. What I have now is close to the right thing (IMHO) but will need some more iterations.

In terms of path forward, my recommendation would be that existing functioning stations remain as they are (don’t fix if it ain’t broke) and that problem stations and new stations use the new version, once ready. Also, I haven’t ported the new build to sensorstations so there’ll be work on that front to be done.
Can you be more specific about “the old software is also causing quite a bit of frustration”?
Thorsten

14

Some of the 5-10 stations I work with cause problems that are difficult to pinpoint. Usually they just stop working. A majority of them are connected to the internet via WIFI (SG:s being sensitive to unstable connections?), but not all of them. Corrupt SD cards is sometimes an issue, but it is difficult to be sure, the fastest way of getting back on track is swapping cards, thus the problem disappears before it is properly analyzed. This happens a few times every year. It is difficult to know if this only happens to us.

Then there are quite a few things that would be “good to have”, usually more tools to administer the SG:s remotely; delete local data, update tag database, etc.

I did expect a more stable system, with more options, and I was going to update all units to the latest available version. That is usually a good idea for all programmable units, not only SG:s ;-)

However, I am still a bit surprised that such a complex, wide-spread system relies on the support of one single volunteer (if that is the case?). Long term stability and support is crucial, and lots of research projects rely on a reliable system. Lack of funding, I suppose?

onsdag 28 september 2022 kl. 18:36:43 UTC+2 skrev tvone...@gmail.com:

15

I did expect a more stable system, with more options, and I was going to update all units to the latest available version.

The new SW version is available for testing, I have not made a big announcement 'cause I still have a list of issues to work down and I want to avoid having many people all run into the same already-known issues. However, note that the new SW only runs on rPi3 and newer so “upgrade” involves a new rPi in many cases, besides the $$ the most painful is even get hold of an rPi…