# Interpreting data from transmitAngle() **URL:** \ **Category:** Ping Viewer\ **Tags:** ping\ **Created:** [June 14, 2024, 4:15pm UTC](https://discuss.bluerobotics.com/t/interpreting-data-from-transmitangle/17172 "2024-06-14T16:15:33Z")\ **Posts on this page:** 1\ **Showing post:** 2
**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:** [June 17, 2024, 2:20pm UTC](https://discuss.bluerobotics.com/t/interpreting-data-from-transmitangle/17172/2 "2024-06-17T14:20:48Z")
Hi @rsloven, welcome to the forum 🙂 - [The protocol documentation](https://docs.bluerobotics.com/ping-protocol/pingmessage-ping360/#2300-device_data) covers what each message field is expected to include - [This post](https://discuss.bluerobotics.com/t/ping360-range-setting-and-the-angle-definition/11686) is the first result when [searching the forum for “Ping360 transmitAngle”](https://discuss.bluerobotics.com/search?q=Ping360%20transmitAngle), and describes some of the practical aspects of working with that message - [This post](https://discuss.bluerobotics.com/t/ping-1d-profile-data-understanding/12775/2) provides some additional context around working with profile data from ping devices Feel free to follow up if there are additional aspects you want clarification on 🙂 > [@rsloven](#): > > Are they the distance to an object/obstacle at a certain angle? You specify the desired angle in your `transmitAngle` method call - it returns a profile from that angle\[1\], of echo response strength data * * * 1. Note that the sonar doesn’t know about its own or the vehicle’s orientation, so the angle is a body-frame orientation of the sonar transducer relative to the sonar device (e.g. `x` gradians from the penetrator), rather than a global / earth-frame / compass-aligned one. --- _[View the full topic](https://discuss.bluerobotics.com/t/interpreting-data-from-transmitangle/17172)._