Hi Motus team
Looks like all our the DIY Sensorgnomes are falling behind by 17 days or so. Server issues or is the webpage reporting the wrong Last Data Received date?
Hi Mark, unfortunately the data processing backlogs remain an ongoing issue, due to a variety of related factors. For V2 SG that are internet connected, you should be able to confirm their connectivity at www.sensorgnome.net
Hi Josh, thanks for the quick update. The SG Hub shows the stations to be sending files (ie. for the most part the number of files on each station is decreasing or steady), so that’s good. Best of luck with the processing fix. :)
Did notice that most of the CTT stations are up to date with processing. Is that because processing is done on the CTT stations or a decision to throttle the DIY SG’s before the commercial stations?
Mark
Hi Mark,
166 MHz data from CTT sensorstations is also delayed, same as the SGs. As I understand it, they show last data processed as up-to-date because data from sensorstations first goes to CTT, where 434 MHz data is processed, then comes to Motus where 166 MHz data is processed. So the 434 data has been processed hence the current date, but the 166 data is delayed. Here’s an example of a deployment timeline where you can see the delay on data from the 166 antennas:
Hi Amie, thanks for that.
Interesting to learn that
- CTT processes their Sensorstation 433/4MHz FSK signal themselves.
- the timestamp changes if either signal type is processed (by either Motus or CTT)
Just for completeness, I’m guessing that for our DIY Sensorgnomes, Motus (Birds Canada) processes both the 166 and the 434MHz signals; no CTT involvement (other then them kindly providing the software images for the Adafruit 434MHz radios and I’m guessing some sort of algorithm to allow Motus to process the 433/4 FSK signals)?
Hi Mark, here are some diagrams outlining the data processing pipeline. CTT actually processes all the 434 data, the data just all comes to Motus first if from a sensorgnome.
1 Like
Perfect, thanks Amie!