# Ping Sensor Beam profile **URL:** \ **Category:** Sensors\ **Tags:** ping\ **Created:** [March 3, 2022, 2:50pm UTC](https://discuss.bluerobotics.com/t/ping-sensor-beam-profile/11662 "2022-03-03T14:50:35Z")\ **Posts on this page:** 1\ **Showing post:** 5
**Author:** ![EliotBR](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/eliotbr/32/6937_2.png) [@EliotBR](https://discuss.bluerobotics.com/u/EliotBR)\ **Post date:** [March 11, 2022, 10:41am UTC](https://discuss.bluerobotics.com/t/ping-sensor-beam-profile/11662/5 "2022-03-11T10:41:31Z")
> [@EliotBR](#): > > I’ve just sent another message to the two engineers who are most likely to know the status, in case my original message got missed. Following up on this, I got a response from our primary sonar development engineer: > [@BrianBR](#): > > … we did get the beam plot rig working enough to take a few plots but I’m not comfortable sharing the data yet. There’s a few things to do still to verify the test setup then I’d like to run a decent number of units through to confirm that the production units are consistent enough to publish a single plot. > > … > > we probably won’t have anything for [you] by [the end of the month] unfortunately. When I get back [from leave] this is going to be a priority so hopefully we’ll have it more polished soon. Seems like we’re unlikely to have tangible measurements in time for your report due date, and given you would presumably want some time to look at/analyse the beam profile it’s unfortunately best to assume we won’t be able to provide that in time, sorry! Feel free to follow up if there’s anything else we can help with 🙂 --- _[View the full topic](https://discuss.bluerobotics.com/t/ping-sensor-beam-profile/11662)._