# How to read digital input from Navigator and show its value in QGroundControl? **URL:** \ **Category:** QGroundControl\ **Created:** [December 11, 2022, 7:30pm UTC](https://discuss.bluerobotics.com/t/how-to-read-digital-input-from-navigator-and-show-its-value-in-qgroundcontrol/13359 "2022-12-11T19:30:41Z")\ **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:** [December 12, 2022, 7:05am UTC](https://discuss.bluerobotics.com/t/how-to-read-digital-input-from-navigator-and-show-its-value-in-qgroundcontrol/13359/2 "2022-12-12T07:05:43Z")
Hi @Blublub, welcome to the forum 🙂 The Navigator isn’t set up with general purpose digital inputs, and the only digital input directly supported by the ArduSub firmware is the one for the leak sensor. The ADCs can also be used for firmware-enabled functions (like an analog leak sensor), but I don’t believe the autopilot firmware supports streaming the raw ADC values to the topside. It may be possible to disable some of the serial ports in the firmware parameters, then run some code on the Raspberry Pi (perhaps as a BlueOS [extension](https://discuss.bluerobotics.com/t/external-integrations-extensions/10912)) that reads them and sends the state to QGC via some form of MAVLink messages. QGC does not support arbitrary messages, so your options would be to make use of messages QGC already supports that aren’t otherwise being used by the firmware, or to [modify QGC to support additional messages](https://discuss.bluerobotics.com/t/adding-a-sensor-to-mavlink-stream/7985/22). --- _[View the full topic](https://discuss.bluerobotics.com/t/how-to-read-digital-input-from-navigator-and-show-its-value-in-qgroundcontrol/13359)._