Sbe37/RS232 Integration Issue

[ALMOSHSG]

Hi all,

I’m facing trouble integrating an SBE37 sensor via RS232. Despite following the user guide and RS232 serial port guide
and making code adjustments ( I’m not sure about the modification I did but I tried to follow the sensor output format ) , the BM Dev Kit console doesn’t display sensor data or recognize its commands. I tried The sensor on its own and it works on the terminal. Any help or insights would be appreciated!

Thanks,
Shatha

[evan]

Hi @ALMOSHSG I’d recommend backing up a couple steps and focusing on getting the output from the sensor showing up on the Dev Kit before modifying any code from the serial payload example or connecting your Dev Kit to the Spotter.

Some suggestions:

• Follow the process in this guide in detail step-by-step, just for your sensor instead of the RBR Coda, and update this thread with details at the very first point where things go sideways and we can take it from there.

Some gotchas to watch out for:

• Use the latest bm_protocol release for your serial_payload_example application on your Dev Kit.
• Make sure you have the RS232 jumpers on the Dev Kit set correctly.
• Make sure you have the baud rate set correctly for your sensor.
• Make sure you have the Rx / Tx connected in the proper orientation (Rx sensor → Tx Dev Kit, Tx sensor → Rx Dev Kit).

[ALMOSHSG]

Hi Evan ,

Thanks for the suggestions! I appreciate your guidance.
I’m confident about the jumpers, baud rate, and connections, as I’ve double-checked everything. I actually have a terminal output showing some data in hexadecimal, as shown here

Thanks again for your help!
Best,

ALMOSHSG

[evan]

Awesome, it looks like the BM Dev Kit console is displaying the sensor data @ALMOSHSG.

Is there a different issue you’re having?

[ALMOSHSG]

Thanks, Evan!

I’m actually encountering an issue retrieving the data. I used the sofar API and the spotter ID, but I’m only seeing this without any data

When I check the spotter log stream and SD files, it indicates “All messages sent successfully!”

Any help or suggestions would be greatly appreciated!

Thanks!

[evan]

@ALMOSHSG Can you provide:

• The full API call that you’re making (but remove/obscure your API token). Note - it is safe to share your Spotter ID. Your API token is required to access data or change settings.
• Approximate times when data was sent from your Spotter.

[ALMOSHSG]

Of course here is the full API :

and here is the time of the data received on the sofar dashboard

s shown, with the +3 offset, it is 7:57 UTC, which matches the log file.

[evan]

Hi @ALMOSHSG - I’m able to confirm the system is connecting and sending data as expected, but it has not sent any Bristlemouth data recently (it did send Bristlemouth data a couple of weeks ago around October 1st).

So it’s not an API access/backend issue - the system isn’t sending the data.
The fact that the other Spotter data (waves, system data, etc.) is being transmitted means it’s not a telemetry issue, and the fact that you can see other kinds of Bristlemouth data on your Spotter/SD card means it’s not a Bristlemouth issue.

So I suspect it is either:

1. Your Dev Kit code isn’t ever calling spotter_tx_data - maybe the Spotter sampling configurations aren’t leaving the system powered on long enough?
2. There’s an issue with the call to spotter_tx_data such that it’s resulting in an error - maybe the payload is too large - the maximum supported is 311 bytes?

Suggested next steps:

• In your custom code that is running on the Dev Kit and sending the data, put a call to bm_printf right before your call to spotter_tx_data.
• When testing, make sure you see the expected output on the Spotter console USB console output from the bm_printf call right around the same time you see Added message to queue line.

Additional questions:

• How often do you expect your Dev Kit application to send data over telemetry?
• How have you setup your Spotter’s sampling configurations?
• Could you run a test with a freshly cleared SD card in your Spotter, and zip up and share the SD card data for us to review?
• Would you be able to share a link to your code with us via a DM so we can advise on troubleshooting?

[evan]

@ALMOSHSG how are you progressing on this one?