# RC\_OVERRIDE/ MANUAL\_CONTROL not working mavlink **URL:** \ **Category:** Blue Robotics Software\ **Created:** [September 13, 2022, 5:29pm UTC](https://discuss.bluerobotics.com/t/rc-override-manual-control-not-working-mavlink/12898 "2022-09-13T17:29:43Z")\ **Posts on this page:** 1\ **Showing post:** 4
**Author:** ![cmarq](https://avatars.discourse-cdn.com/v4/letter/c/ee59a6/32.png) [@cmarq](https://discuss.bluerobotics.com/u/cmarq)\ **Post date:** [September 16, 2022, 6:20pm UTC](https://discuss.bluerobotics.com/t/rc-override-manual-control-not-working-mavlink/12898/4 "2022-09-16T18:20:08Z")
Hi Eliot, I was able to figure out a solution after reading your thoughts. In my C++ code, I found that if I sent the mavlink message to control the motors with the sys\_id of the Jetson nano, it was sending as ID 245. As you know, the ID of the GCS is 255. There is a line of code in Ardusub that says to ignore any incoming manual\_control messages if the ID is not 255. So from my C++ code, the ROV was quietly denying my messages. They would show up in QGC, but no change in the RC output would happen. I am still unsure what the issue is for my Python script, but my goal is to use C++, so I am not going to pursue that further. --- _[View the full topic](https://discuss.bluerobotics.com/t/rc-override-manual-control-not-working-mavlink/12898)._