# Issues getting valid Omniscan 450 side sonar data

**URL:** <https://discuss.bluerobotics.com/t/issues-getting-valid-omniscan-450-side-sonar-data/20969>\
**Category:** Sonar and Acoustics\
**Created:** [July 15, 2025, 11:42am UTC](https://discuss.bluerobotics.com/t/issues-getting-valid-omniscan-450-side-sonar-data/20969 "2025-07-15T11:42:31Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![kingfisher](https://avatars.discourse-cdn.com/v4/letter/k/bc8723/32.png) [@kingfisher](https://discuss.bluerobotics.com/u/kingfisher)\
**Post date:** [July 15, 2025, 11:42am UTC](https://discuss.bluerobotics.com/t/issues-getting-valid-omniscan-450-side-sonar-data/20969/1 "2025-07-15T11:42:31Z")

</div>

Hi,

I am new to the forum, so please let me know if there is something wrong with this post!

I have been having issues with getting valid data from the Omniscan 450 side sonars. The side sonars were installed and configured on a blueboat through following the [provided integration guide.](https://bluerobotics.com/learn/omniscan-450-ss-integration/) While I seem to get readings through sonarview, it does not look like I am getting any actual data?

For instance, here is what the images I get from sonarview look like in my testing so far:

 ![image](https://us1.discourse-cdn.com/flex019/uploads/bluerobotics/original/2X/e/ec243f19cf059cfba057940da81c8fdad41b0623.png)

The images are always smooth gradients, even when I know that there are discrete objects in the water that should be visible with sonar. There is also no discrete cutoff in the image for the area under the path of the boat that is out of the FOV of the sensors as seen in demos I’ve looked at.

Demo file referring to [the one included here.](https://sonarview.io/scanner) (Can only include one image in the post)

Any ideas on what I could be doing wrong with the side sonars? Thanks!

---

<div class="post-metadata">

**Author:** ![tony-white](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/tony-white/32/18385_2.png) [@tony-white](https://discuss.bluerobotics.com/u/tony-white)\
**Post date:** [July 15, 2025, 7:55pm UTC](https://discuss.bluerobotics.com/t/issues-getting-valid-omniscan-450-side-sonar-data/20969/2 "2025-07-15T19:55:57Z")

</div>

Hi @kingfisher -  
Welcome to the forums!  
Something does look a bit strange there - you seem to have the depth compensation turned on, and set to 0m - maybe it’s worth turning off?  
What water depth have you been testing in? How have the surface water conditions been, calm?

It may be best to[reach out to Cerulean directly](https://ceruleansonarhelp.zendesk.com/hc/en-us/requests/new) if the issue persists…

---

<div class="post-metadata">

**Author:** ![kingfisher](https://avatars.discourse-cdn.com/v4/letter/k/bc8723/32.png) [@kingfisher](https://discuss.bluerobotics.com/u/kingfisher)\
**Post date:** [July 16, 2025, 4:59am UTC](https://discuss.bluerobotics.com/t/issues-getting-valid-omniscan-450-side-sonar-data/20969/3 "2025-07-16T04:59:45Z")

</div>

It looks similar with depth compensation turned off. I had to use the web application here since it doesn’t seem like I can turn it off on the desktop application?

 ![image](https://us1.discourse-cdn.com/flex019/uploads/bluerobotics/original/2X/2/2726413ebb514db7d0f313620b8a8a0aeb18a33f.png)

Yes, the surface conditions have been calm. It was tested in a pond that has a max depth of ~2.5 m.

---

<div class="post-metadata">

**Author:** ![tony-white](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/tony-white/32/18385_2.png) [@tony-white](https://discuss.bluerobotics.com/u/tony-white)\
**Post date:** [July 16, 2025, 6:08am UTC](https://discuss.bluerobotics.com/t/issues-getting-valid-omniscan-450-side-sonar-data/20969/4 "2025-07-16T06:08:10Z")

</div>

Hi @kingfisher -  
Wow, that’s quite a shallow body of water! You may want to turn off auto gain, and reduce the gain to a minimum - you may be “overpowering” the environment if it is a small body of water or tank? Make sure you’re using the latest version of the desktop application, they should be identical…

It’s also possible your transducers aren’t connected properly. Make sure you’re fully inserting the wires into the PCB receptacles as the guide details, inside the hull on each lid-tray.

---

<div class="post-metadata">

**Author:** ![ljlukis](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/ljlukis/32/3983_2.png) [@ljlukis](https://discuss.bluerobotics.com/u/ljlukis)\
**Post date:** [July 16, 2025, 1:55pm UTC](https://discuss.bluerobotics.com/t/issues-getting-valid-omniscan-450-side-sonar-data/20969/5 "2025-07-16T13:55:35Z")

</div>

I’m thinking transducers not connected properly. As Tony suggested please put in a support ticket directly here at Cerulean and we’ll get you sorted out. [https://ceruleansonarhelp.zendesk.com/hc/en-us/requests/new](https://ceruleansonarhelp.zendesk.com/hc/en-us/requests/new)

---

<div class="post-metadata">

**Author:** ![ljlukis](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/ljlukis/32/3983_2.png) [@ljlukis](https://discuss.bluerobotics.com/u/ljlukis)\
**Post date:** [July 16, 2025, 2:11pm UTC](https://discuss.bluerobotics.com/t/issues-getting-valid-omniscan-450-side-sonar-data/20969/6 "2025-07-16T14:11:33Z")

</div>

A quick test: out of the water start pinging. If your hearing is as bad as mine you’ll have to put your ear right up to the transducer but you should be able to hear a rapid clicking sound. If not, it’s very likely your transducers are not connected properly.

---

<div class="post-metadata">

**Author:** ![kingfisher](https://avatars.discourse-cdn.com/v4/letter/k/bc8723/32.png) [@kingfisher](https://discuss.bluerobotics.com/u/kingfisher)\
**Post date:** [July 16, 2025, 8:00pm UTC](https://discuss.bluerobotics.com/t/issues-getting-valid-omniscan-450-side-sonar-data/20969/7 "2025-07-16T20:00:47Z")

</div>

I’ve definitely heard the transducer making their buzz while out of the water, so at the very least they seem to be doing _something_.

---

<div class="post-metadata">

**Author:** ![ljlukis](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/ljlukis/32/3983_2.png) [@ljlukis](https://discuss.bluerobotics.com/u/ljlukis)\
**Post date:** [July 16, 2025, 8:15pm UTC](https://discuss.bluerobotics.com/t/issues-getting-valid-omniscan-450-side-sonar-data/20969/8 "2025-07-16T20:15:35Z")

</div>

Well, that image does look like what I would expect if the transducer was not connected, or the vehicle was out of the water. Kinda weird that they both are exhibiting the same symptoms.

---

<div class="post-metadata">

**Author:** ![NickNothom](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/nicknothom/32/4607_2.png) [@NickNothom](https://discuss.bluerobotics.com/u/NickNothom)\
**Post date:** [July 24, 2025, 9:38pm UTC](https://discuss.bluerobotics.com/t/issues-getting-valid-omniscan-450-side-sonar-data/20969/9 "2025-07-24T21:38:21Z")

</div>

To any future readers, the problem was a bug in Omniscan FS/SS Firmware 1.5.8, which was packaged in SonarView 1.13.21-beta. The bug was fixed in Firmware 1.5.9 and SonarView 1.13.22-beta.
