# Failed to make the light on **URL:** \ **Category:** BlueROV2\ **Tags:** pymavlink\ **Created:** [July 2, 2021, 4:31pm UTC](https://discuss.bluerobotics.com/t/failed-to-make-the-light-on/10082 "2021-07-02T16:31:12Z")\ **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:** [July 3, 2021, 7:01am UTC](https://discuss.bluerobotics.com/t/failed-to-make-the-light-on/10082/2 "2021-07-03T07:01:19Z")
This has been responded to in your other post: > [@Rc\_channels\_override\_send() takes from 11 to 12 positional arguments but 21 were given](https://discuss.bluerobotics.com/t/rc-channels-override-send-takes-from-11-to-12-positional-arguments-but-21-were-given/10071/5): > > Have you checked which pixhawk port your light is plugged into? It’s possible it’s in a different port than the one in my example. You can, but it shouldn’t be required. Once the heartbeat is successfully detected from an autopilot that’s running mavlink 2, pymavlink should automatically detect that and change to using mavlink 2 as well. That means you don’t have a valid connection to your autopilot. There are multiple possible causes of that, but they depend on your setup. Assuming you’re … --- _[View the full topic](https://discuss.bluerobotics.com/t/failed-to-make-the-light-on/10082)._