Hi Andrew, I’m told it was indeed the frequency issue suggested above. We’ve made the change to the receiver, and scheduled a rerun of the data. Due to the roughly 2 week backlogs mentioned earlier that hasn’t happened yet though.
EDIT…
A bit of clarification… The frequency setting I was referring to only affects data that has been processed by the Motus server (as Lucas pointed out). However, that setting had not been implemented on our end so there would have been issues with the processed data anyway. That’s now been fixed.
But the SG frequency issue is upstream of that and there may still be problems with the configuration.
Lucas’s screenshot shows two frequencies for this receiver. As far as I know, the info logs are related to the V2 SG (and tagfinder per se) and is also the source of what is displayed on the web UI. So 151.5 should correspond what what you set in the web UI of the SG. The values in the array appear to correspond to the “acquisition configuration” (the old “deployment.txt” file). But this is no longer directly editable in the UI. It should reflect what you set in radios panel of the UI.
Whatever the root cause, it’s safe to say that this receiver is not recording properly. When you are there next, you can try to see where that other incorrect frequency is coming from, but the simplest way to resolve this may be to start with a clean software image. (And best to update the boot number following that.
Also note that, while 151.5 is the frequency the tags broadcast at, it’s not actually what the FunCubes are set to. Rather, they are set 4 kHz below the nominal. You will be able to confirm this in your logs. I’ve given an example below of an SG here in Canada that listening for tags on 166.380. This adjustment should take place automatically when you select the nominal frequency in the UI, but it’s helpful context if you are looking in the sgcontrol logs and wonder why you are seeing frequency values of 151.496 instead of the 151.5 that you set! And example below of a receiver here in Canada listening for tags at the nominal frequency of 166.38
[Note: I mistakenly referred to the Australia Lotek frequency as 150.5 instead of 151.5. I’ve fixed that in the message body]