# Work waypoint mission with m64 acoustick modem

**URL:** <https://discuss.bluerobotics.com/t/work-waypoint-mission-with-m64-acoustick-modem/8501>\
**Category:** Sonar and Acoustics\
**Tags:** water-linked, acoustic-modem\
**Created:** [November 3, 2020, 12:20am UTC](https://discuss.bluerobotics.com/t/work-waypoint-mission-with-m64-acoustick-modem/8501 "2020-11-03T00:20:10Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![YuryArnaut](https://avatars.discourse-cdn.com/v4/letter/y/67e7ee/32.png) [@YuryArnaut](https://discuss.bluerobotics.com/u/YuryArnaut)\
**Post date:** [November 3, 2020, 12:20am UTC](https://discuss.bluerobotics.com/t/work-waypoint-mission-with-m64-acoustick-modem/8501/1 "2020-11-03T00:20:10Z")

</div>

Hello Bluerobotics community, I found an article where you provide simple script for control ROV via acoustcik channel. FOr now I want to test it with my ROV. But also I want such regime as:

1. I set mission by waypoints via qgc or pymavlink.
2. set ROV to sea , without transferring data through cable. I use cable as a chain.
3. arm the vehicle, and transfer all needed data via m64 for rov, so it could pass the mission.

For now, the main prob;em is, that I don’t know how to transfer this data, I mean what pymavlink messages I have to use to put data into them. What’s the queue of this messages. Please can you provide some reference messages to it?

---

<div class="post-metadata">

**Author:** ![YuryArnaut](https://avatars.discourse-cdn.com/v4/letter/y/67e7ee/32.png) [@YuryArnaut](https://discuss.bluerobotics.com/u/YuryArnaut)\
**Post date:** [November 4, 2020, 1:52pm UTC](https://discuss.bluerobotics.com/t/work-waypoint-mission-with-m64-acoustick-modem/8501/2 "2020-11-04T13:52:48Z")

</div>

I found this post:  
[https://waterlinked.com/forums/topic/split-modem-m64-and-qgroundcontrol/](https://waterlinked.com/forums/topic/split-modem-m64-and-qgroundcontrol/)

But still, can you provide to me, what data, and what messages I have to use , for transfering data for autonomous working autonomous mission without eth-cable, but with m64 instead.

There is a big problem for me now.