I have one that says it is sending data but is now >2 weeks delayed. I am not sure what it is about this particular receiver (CTT-V3023D36A547 - Receiver - Motus) as I know it is connected to wifi and the website says it is processing the data, yet when I download in R, I can only get up to 30th November.
Hi Lucy, this receiver appears to be up to date. I can’t access your CTT Portal (which you should check if you aren’t seeing up-to-date data on Motus for a SensorStation) but on your project page, everything looks fine here. Most recent data is up-to-date, and nothing looks amiss in the deployment timeline either.
Is it just in the R package that you’re seeing this issue?
Yes - when I try to find the data through R, I can only download up to 30/11 - I am only really querying it because there was significant testing done at this location on the 8th December, which I would expect to show up as I deployed the tag, and they confirmed it was on using a handheld radio.
I have also had situations with other receivers where I know there has been tagging done, and thus would expect some data, but it has not been available in R until a significant number of weeks later - but this time I really need to know if there are data there. It’s unfortunate, perhaps I will just have to wait for something to change? I don’t believe that there cannot be nothing available for me to look at through R, unless everything has just gone completely wrong with the system.
Going back to basics - was the tag you tested with registered?Antennas connections all OK? How many antenna attached to the SS?From trouble-shooting team:The receiver deployment plot shows activity (antenna noise but no detections in this case) up to the current date. It also shows the receiver has been rebooting at least daily since 2024-09-11. Looking at the raw pulse data from 2024-12-08 when they were doing testing, although I see an increase in pulses recorded compared to the previous day, there’s no sign of coherent tag bursts, just random-ish looking noise at around -64dB. There are no bursts detected by the tag finder because there aren’t any to be detected. So, I suspect there’s something wrong with the receiver or the test tag(s). Probably not the same issue as #1560, there were bursts visible in the pulse data for that. Download of data through R should have succeeded, just reported 0 detections. Is that what happened, or was there some other error?
[I split this into a new topic since it’s a different issue]
It actually doesn’t look like it’s related to the R package or a processing backlog.
So based on the information posted above, and as indicated by Stu as well, the receiver is regularly sending data and the “most recent data” date is up-to-date. The activity on the deployment timeline looks normal as well.
But there are no detections whatsoever on the Lotek frequencies, which are the only antennas you have connected based on the deployment record.
I had a look from the database side and though there are pulse counts in many of the uploaded batches (reflected by the coloured bars in the deployment timeline) there isn’t a single resolved hit in any of them. That seems strange considering you are testing a tag nearby.
This actually looks a lot like this issue. The next time that someone is at this station, could they connect to the SS web interface and confirm that the FunCube frequency is set to 150.096 (150.1 minus 4 kHz). There is more information about the frequency setting here.
As for why you are seeing some data in R up to the 30th/31st, that has to do with the integrated 434 MHz CTT radios. Even though you don’t have any antennas connected to them, they can and will often pick up ambient noise. In fact you can see evidence of that noise on the deployment timeline above, where there are occasional blips on all 5 integrated 434 MHz radios (the ones with the “L” prefix). And occasionally that ambient noise will resolve to an actual CTT code. It’s not impossible to pick up real tags on the integrated radios without antennas attached, but considering all of these just have a run length of one (single hits) they are most likely false positives.
Unrelated, I notice you have 4 FunCubes on this SS. If you haven’t already, it would be good to update the image on the SS to newest version as it fixes an issue related to FunCube performance, and includes some other various fixes and improvement.
@user969 In addition to double checking the frequency, it would also be helpful if you could:
- bring along an activated test tag (or two) that have active deployment records. Ideally you’d also upload the tag database for these tags to the SS so that you can view the detections in real time while at the station.
- copy the contents of the SensorGnome configuration at the bottom of the SS web interface and save it somewhere to share with us
- if you can download the previous several days of data files just before leaving that could also help.
Thank you so much, both of you… a slight disaster but glad you caught this!
It’s very difficult to troubleshoot problems from a different country, normally i would go my self and check the stations and run through a checklist. I think i was thrown by the fact that they reported detections on the SG screen, but it presumably was just noise associated with the test tag but as you say it was never resolved into an actual hit because the frequency is off.
So, there are a few things to try. Sounds like we can get this reaolved pretty quickly.
I just checked now and it doesn’t look like anything has changed with regards to the detections. Do you know if they were able to get an activated test tag out there that with an active deployment record (and ideally the tag database copied over to the SS as well)?
yes, tag #23 as part of project #365 UK Motus has been used out there a couple of times. The tag database should be on the receiver… The tag database was loaded up also onto CTT-V3023D369880 and the test tag showed up on that receiver as a known tag - I can also see through my CTT account that the files are large, so I anticipate there being detections on that one… The former one, it sounds like what they did didn’t actually change anything. The files certainly look small to me. I suspect if they made changes, including correcting the deployment file, and could see detections on the screen, perhaps it’s the dongles despite being set to reboot.
Hi again Josh,
I downloaded the data from the CTT account page SOC Motus-CTT-V3023D36A547-000078-2025-02-24T09-24-27.7920P-all.txt.zip (41.7 KB) I see larger files over the last few days which matches with someone out with the test tag #23 from project 365. I’m waiting for it to be processed to download through R… I received this picture from the installer - dongles tuned correctly, and seemingly functioning (CTT page shows consistent functioning as well…)
There is a disconnect somewhere, and I can’t see where it could be now!
Also, I notice that this particular station is very slow to upload/update - Motus says it has received data, but when i download through R, it’s 5 days behind (so today, I can only download data to 21/2, but Motus says it has data to 26/2). Would these issues be related? If it’s a local connection problem, that can be solved, but I pushed some data to Motus by downloading from ctt account page, then uploading to Motus, and none of it is still available… It seems specific to this station as well, or just coincidence that everytime I try to deal with this station Motus has a melt down ;)