# Ping360 Scanning Sonar Issue

**URL:** <https://discuss.bluerobotics.com/t/ping360-scanning-sonar-issue/21462>\
**Category:** General Discussion\
**Created:** [August 25, 2025, 3:22pm UTC](https://discuss.bluerobotics.com/t/ping360-scanning-sonar-issue/21462 "2025-08-25T15:22:16Z")\
**Posts on this page:** 1\
**Showing post:** 3

<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:** [August 27, 2025, 6:01pm UTC](https://discuss.bluerobotics.com/t/ping360-scanning-sonar-issue/21462/3 "2025-08-27T18:01:31Z")

</div>

Hi @omer_1 -

As @FlyingManta mentions, this is likely due to the motion of the ROV - if you want to eliminate the gaps, you could disable the mavlink connection of the Ping360 under the Ping Sonar Devices menu.

The sonar spins at a an almost constant rate so when the ROV moves there will be sectors with no data, if the ROV motion is accounted for - that’s why disabling the mavlink heading connection will eliminate the gaps!

Have you updated the sonar to the latest [firmware](https://discuss.bluerobotics.com/t/ping360-firmware-update/21023)? This improves the scan rate, as does using the [ethernet interface.](https://bluerobotics.com/learn/changing-communications-interface-on-the-ping360/)

---

_[View the full topic](https://discuss.bluerobotics.com/t/ping360-scanning-sonar-issue/21462)._