# Missing parameters, no parameter for lights, how to fix?

**URL:** <https://discuss.bluerobotics.com/t/missing-parameters-no-parameter-for-lights-how-to-fix/20153>\
**Category:** Blue Robotics Software\
**Tags:** ardusub\
**Created:** [April 20, 2025, 7:33pm UTC](https://discuss.bluerobotics.com/t/missing-parameters-no-parameter-for-lights-how-to-fix/20153 "2025-04-20T19:33:35Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![nurjan14](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/nurjan14/32/16632_2.png) [@nurjan14](https://discuss.bluerobotics.com/u/nurjan14)\
**Post date:** [April 20, 2025, 7:33pm UTC](https://discuss.bluerobotics.com/t/missing-parameters-no-parameter-for-lights-how-to-fix/20153/1 "2025-04-20T19:33:35Z")

</div>

Having this issue with missing parameter message all the time with latest stable ardusub 4.5.3 on the latest stable QGC 4.4.4

 ![image](https://us1.discourse-cdn.com/flex019/uploads/bluerobotics/original/2X/f/f71068b4b171cf0376dbe677fb0acb8724a6b60a.png)

Also, can see options for channel number in lights setup, it required BRD\_PWM\_COUNT parameter which is missing as well.

 ![image](https://us1.discourse-cdn.com/flex019/uploads/bluerobotics/original/2X/a/a6851060ebd578a54651c822f0c4ac785d9b345d.png)

Any suggestion how to fix it?  
Thanks

---

<div class="post-metadata">

**Author:** ![nurjan14](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/nurjan14/32/16632_2.png) [@nurjan14](https://discuss.bluerobotics.com/u/nurjan14)\
**Post date:** [April 20, 2025, 8:33pm UTC](https://discuss.bluerobotics.com/t/missing-parameters-no-parameter-for-lights-how-to-fix/20153/2 "2025-04-20T20:33:24Z")

</div>

Just found it in the blueos setup in the vehicle setup tab -\>configure → lights where you can set the the channels.

 ![image](https://us1.discourse-cdn.com/flex019/uploads/bluerobotics/original/2X/1/1e6d1a40f0f5bd48402d2a9a0cccffb7363a7c0c.png)

---

<div class="post-metadata">

**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:** [April 24, 2025, 1:47am UTC](https://discuss.bluerobotics.com/t/missing-parameters-no-parameter-for-lights-how-to-fix/20153/3 "2025-04-24T01:47:45Z")

</div>

Hi @nurjan14,

> [@nurjan14](#):
>
> Also, can see options for channel number in lights setup, it required BRD\_PWM\_COUNT parameter which is missing as well.

For some relevant context:

> [@Bug in firmware Qgroundcontrol](https://discuss.bluerobotics.com/t/bug-in-firmware-qgroundcontrol/19978/3):
>
> the `BRD_PWM_COUNT` parameter was removed in ArduSub 4.5, and your installed QGroundControl version is unaware that there are valid builds of ArduSub that don’t include that parameter, so it’s complaining when it can’t find it. That said, … the warning is unlikely to cause issues (it’s just annoying) - the servo output type functionality that it was used for has remained effectively the same, it just doesn’t use that parameter anymore.
> 
> You should generally be able to avoid such warnings by installing a version of QGroundControl that’s newer than your ArduSub version, but be aware that the most recent versions have not been thoroughly tested with ROV use-cases, so may have some unexpected issues.

Note that our currently [latest recommended](https://bluerobotics.com/learn/technical-reference/#software-and-firmware) (read: thoroughly tested) QGroundControl version is 4.2.8, although our development efforts are now focused on [Cockpit](https://blueos.cloud/cockpit/docs) instead, so QGroundControl is effectively a working fallback/alternative for [situations where Cockpit is not yet sufficient](https://github.com/orgs/bluerobotics/projects/34/views/1?groupedBy%5BcolumnId%5D=186954979&sortedBy%5Bdirection%5D=asc&sortedBy%5BcolumnId%5D=186955427).

---

<div class="post-metadata">

**Author:** ![thomas\_G](https://avatars.discourse-cdn.com/v4/letter/t/439d5e/32.png) [@thomas\_G](https://discuss.bluerobotics.com/u/thomas_G)\
**Post date:** [September 12, 2025, 9:52am UTC](https://discuss.bluerobotics.com/t/missing-parameters-no-parameter-for-lights-how-to-fix/20153/4 "2025-09-12T09:52:53Z")

</div>

hi@Eliot

Thanks you for that suggestion, I face this `BRD_PWM_COUNT` issue when I was trying to tune the PID for a custom ardusub-stable( 4.5.5) . After switching from QGCS 5.06 to 4.2.8, I can now tune my PID. By the way, is there any tool or software to automatically tune a sub vehicle attitude and position PID like the “PID Tunning” tool of PX4 in QGroundControl ?

---

<div class="post-metadata">

**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:** [September 16, 2025, 11:19am UTC](https://discuss.bluerobotics.com/t/missing-parameters-no-parameter-for-lights-how-to-fix/20153/5 "2025-09-16T11:19:38Z")

</div>

> [@thomas\_G](#):
>
> is there any tool or software to automatically tune a sub vehicle attitude and position PID like the “PID Tunning” tool of PX4 in QGroundControl ?

I’m not aware of one, but I’ve [raised an Issue](https://github.com/bluerobotics/BlueOS/issues/2724) about adding PID tuning support to BlueOS, which it might be worth referring to for links on how other ArduPilot firmware approach tuning (as some of the approaches may work similarly).