# Navigator - C++/Python - RC Inputs **URL:** \ **Category:** Blue Robotics Products\ **Tags:** navigator\ **Created:** [March 27, 2024, 7:42pm UTC](https://discuss.bluerobotics.com/t/navigator-c-python-rc-inputs/16430 "2024-03-27T19:42:40Z")\ **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:** [March 28, 2024, 1:30pm UTC](https://discuss.bluerobotics.com/t/navigator-c-python-rc-inputs/16430/2 "2024-03-28T13:30:59Z")
Hi @rturrisi, The reference implementation for all autopilot-related functionalities is the Navigator support in ArduPilot’s hardware abstraction layer, since that’s the only autopilot firmware we’ve done appreciable development for and testing with. [This Pull Request](https://github.com/ArduPilot/ardupilot/pull/21809/files) shows the commits that were used to add SBUS / RC Input support for Navigator, which is hopefully a helpful starting point. > [@rturrisi](#): > > When I was trying it in BlueOS/in Pirate mode looking at the individual variables, I wasn’t getting any RC readings either. I believe it’s not enabled by default, and RC input is not guaranteed to work at all in ArduSub. If you want to try it out, the recommended (/verified working) approach is to: > [@Navigator SBUS connection problem](https://discuss.bluerobotics.com/t/navigator-sbus-connection-problem/16283/2): > > 1. Flash Rover Beta (\>=4.4) > 2. Make sure there’s nothing connected to Serial1 > 3. Set [`SERIAL1_PROTOCOL`](https://ardupilot.org/rover/docs/parameters-Rover-stable-V4.4.0.html#serial1-protocol-telem1-protocol-selection) to `RCIN` > 4. set [`RC_OPTIONS`](https://ardupilot.org/rover/docs/parameters-Rover-stable-V4.4.0.html#rc-options-rc-options) to `36` (`0b100100`) > 5. Restart the autopilot --- _[View the full topic](https://discuss.bluerobotics.com/t/navigator-c-python-rc-inputs/16430)._