I finally have my test SG v2 station hardware assembled, so I’ve been doing the customisation for our deployment. Since it’s an Australian project, the Lotek tags operate on 151.500 MHz.
However, when I go to set that frequency on the Radios tab of the web interface, it doesn’t have 151.500 MHz available as an option. The three options offered are 166.380 MHz, 150.100 MHz, and 150.500 MHz (corresponding values with the 4 kHz offset appearing for the funCubePro in the Acquisition Configuration .json text).
I had already done an SG software upgrade, so it should be running with the latest version. Is the 1 MHz difference just an incorrect label, a deliberate frequency offset, or a genuine problem? If so, what’s the best way to proceed?
Hi Andrew, apparently the 150.5Mhz frequency should have been 151.5 but I made a mistake at some point. I will fix it in the next build, my apologies for the error.
To fix it, if you’re comfortable with a bit of CLI you can do the following:
SSH into the SG as user gnome (same password as for web UI)
edit /opt/sensorgnome/control/dashboard.js as root,
e.g. sudo nano /opt/sensorgnome/control/dashboard.js
on line 22 change 150.500 to 151.500
restart the control process: sudo systemctl restart sg-control
log into the web UI and toggle the frequency
If you’re having difficulties, please let me know!
I made the change to the dashboard json file, and everything now looks good. (I will now pass it on to my academic colleague for an end-to-end test, since I don’t have any radio tags to try it with.)
Thank you for the assistance, and no apology necessary… I certainly make more than my fair share of my own mistakes.
