One of our cellular-connected V3.2 Sensorstations (V3023D417BE7) is behaving normally except for the fact that no SGdata files are being sent to the servers. Power is solar, but steady, and all other log files, check-ins and GPS files are regular and up to date. Cellular signal is very strong; recorded at -53db during last visit. Only running 2 antennas on each frequency, so very manageable load on the USB hub.
The issue was clocked withing 24 hours of deployment and was returned to a few days later. A manual data download produced regular, hourly SGdata files in daily folders for the four days it had been running at that point. Any reasons SGdata files would be written but not sent along with other data packets? Anyone else experience a bug like this?
I assigned an autossh key to your station. If your station is accessible, using the LCD menu go to System –> Bash Update. The station will take the autossh key and I can remote into your station from my computer.
In the future, you should make a Customer Service Desk (CSD ticket)so I can be alerted to your station’s issues quicker and so I can keep track of them.
Thanks, Meelyn. We may have someone out there later next week to run the bash update.
If you have some code that would do the trick, we could run it ourselves when we’re out there. But if the need is to poke around a little bit first to determine the issue, I get it.
I was finally able to fix the filename issue and your sensorgnome data is getting uploaded now. You should see it in your account within an hour or two.
They named their SensorGnome files as “Petty’s Island…”. The single apostrophe was interpreted as unicode rather than ASCII, and Python (which we use to upload the files to our servers) didn’t like that unicode character.
I went ahead and changed the name in their deployment.txt file. In the future, we should advise people to not use spaces or apostrophes in the file name.
