I am trying to integrate an Exo3 Sonde with the Spotter Smart Mooring system. Having completed the Bristlemouth Dev Kits Guides 1-5 and now working through Integrating an SDI12 Sensor guide (Bristlemouth Dev Kit Guide: Integrating an SDI-12 Serial Sensor), data from the Sonde can be seen when connected to the Dev Kit using an Ubuntu terminal but when connected to the Spotter Buoy no data and a range of errors now appear (image attached below).
The issue occurred after completing Step 3 and flashing the v0.13.0-sdi12_example.elf.dfu.bin code to the Dev Kit. Please let me know if you have any advice on troubleshooting the cause of the errors. From my understanding it could be due to how the Spotter Bouy is configured.
(Output after flashing the sdi12_example.elf.dfu.bin code. The Dev kit is seen on the left displaying the sonde parameters and on the right the Spotter Bouy showing a range of errors and no data)
Nice job getting the EXO3 sonde integrated with SDI-12! Yes you are correct, this does look like a mismatch between firmware versions between the devkit and the Spotter buoy. Seeing as you updated the devkit with the v0.13.0 sdi12 example app, I suspect your Spotter is on an older version that is no longer able to print the log lines the devkit is now sending.
Could you please type info in the Spotter CLI and report back the output. This command will give us the Spotter’s FW version. If the FW version is v2.15.x, then we will need to update. Similarly, can you type bm info 0 in the Spotter CLI and also report the output from this command. This should give us the Bristlemouth version of the Bridge (Spotter’s Bristlemouth interface). If this is on v0.12.x we will need to update it. Thankfully the latest installers found here, update both the Bridge and the Spotter FW.
The Spotter was running firmware version v2.15.1 and bridge version v0.11.0. After updating the firmware, the data from the Exo3 is now able to be viewed through the Spotter Bouy.
