Hi we have a CTT sensorstation detecting Lotek tags. We have deployed a test tag and after uploading our tag database to the sensorgnome we can see the chirps from the transmitter being picked up and we can see the tag appearing in the Known Tags pane on the Interface. From this we believe the station is working correctly, is seeing our test tag deployment and registering our data. We have suvpccessfully uploaded CTT files to Motus from the web interface but we get nothing back from the Motus dashboard to indicate a test tag has been identified. I’m not sure what to try next to get the station into a working status. Any help would be greatly appreciated
Hi John-
Have you confirmed that your test tag is registered with Motus, as such? This will be required for any tag detections to show up on the Motus side.
Cheers,
David
Hi David,
yes the tags have been restored with Motus. We have seen them recognised in real time on the sensor gnome interface but nothing coming back from the dashboard.
can you advise what the latest version of sensor gnome software for CTT tags in Europe should be so that I can check we’re using the right version please?
@jsrs can you check in on this? If his tag is registering on the SG backend, and the files are being pushed to Motus, even manually, and the tag is registered with Motus, I don’t see why he wouldn’t see them show up in the Motus web portal. Any thoughts?
Thanks
David
John is a member of Project 652 only so I’m assuming that’s the project in question. If so, there are two tags with deployments (and they would be the only two tags from this project that would be detected).
@user983 when you say you see chirps on the SG interface of the SensorStation, are you referring to the live pulses pane or have you uploaded the tag database to the SS? The latter would be the best approach since you would then be able to spot the tag code of those two tags and easily differentiate that from background radio noise.
You can read more about the local tag database here: Uploading a local tag database | SensorGnome User Guide. There is a section specific to uploading to a SensorStation.
Hi there, yes I’m referring to the live pulses pane.
Yes I’ve uploaded the tag database to the sensorgnome and yes it is identifying the test tag in the live tag as pane.
We did another trial on Friday 30th in the afternoon and observe live pulses on the aerials and detections in the live tags pane. After nearly an hour I downloaded the data file for nano tags and read it as a text file, whilst it’s a list of characters it di at least show we had a file of results present. I again forced an upload to Motus but with no results appearing on the portal.
I’m at a loss to explain this to the team and the sponsors.
Hi all,
Can I just ping @jsrs and @user80 to bring this to your attention again…
The data shows up on motus.org as being up to date by 4th Sept, but in R through tagme() I can only acquire data to 29th August… So presumably there is a processing gap at the moment from 30th Aug to present? Is this Sensorstation specific or everything? I wonder if there is a general problem with getting Sensorstation data to Motus? It can take multiple days, to weeks, for us to see anything, even when we know it should be there.
The station referenced in this post has the tags loaded to the database and they were appearing as known in the relevant pane. They recorded nearly 30 mins of this on ~29th/30th august, so it should pop up in Motus, when the data is eventually processed - if not, then I’m not sure what’s happening.
Best, Lucy
Also just to say that project 843 as well as 652 is having these issues - no data available via tagme after 29/8…and no detections when there were extensive tests. the latter part could be a genuine problem with the receiver, but I’m not sure at present.
Hi all, which station and which tag would are the ones you’ve been testing?
Josh
CTT-V30B0154C55F is the station ID Tag pane shows tag 652#8
Hope that’s what you need.
1 Like
And with regard to project 843 it is receivers “CTT-99F6C7F5204A” and “CTT-3749D48FB064” with either 84378 or 84377 tag.
Tag ID for the ABO site is 78763.
An update on this issue: It turns out that the difference between the actual frequency of the tag signal and the nominal frequency exceeded a threshold in the Motus server tagfinder. So when the data files were processed, the pulse data from this tag was essentially ignored.
Reprocessing the data with that threshold modified resulted in the missing detections.
Interesting. Could this be the case with more than 1 tag? I’m just wondering as I can see there are still no detections of the test tag at that receiver - nor a couple of other receivers where i know it was tested and they could see known tag detections coming up on the SG screen. So i think there is still an issue somewhere in terms of detections being properly processed by Motus.
Although having just said that I see you haven’t resolved the CTT processing backlog, which is presumably our actual issue…