I’m not experienced with automotive light bars, so will avoid commenting on that component of the discussion.
It’s worth noting that the Navigator’s PWM driver chip is actually an LED driver. Assuming your light bar is ok with the same PWM frequency as the ESCs are using (e.g. up to ~400 Hz, using the RC_SPEED parameter) then you can just set the relevant SERVOn_MIN and SERVOn_MAX parameters for your output to achieve the duty cycle you want, which you can then feed to your MOSFET. A dedicated duty-cycle PWM converter is likely not necessary (unless you require higher frequencies than the other connected electronics can handle).
You could control that with ArduSub’s built in lights joystick button functions, or alternatives like an on-screen slider in Cockpit.
Thanks for the link, Elliot — that’s helpful documentation for setting up the PWM control and the Cockpit slider on the Navigator side.
What I’m still trying to understand, though, is the behavior on the load side. The guide explains very well how the PWM signal is generated and routed, but it doesn’t really address how a typical off-the-shelf automotive/work LED light bar behaves when its input power is PWM-controlled via an external MOSFET.
I’m mainly interested in real-world experience here: whether this approach works cleanly with such lights, or whether people have seen issues like flicker, instability, resets, noise, minimum duty-cycle limits — or cases where it simply didn’t work or went up in a smelly cloud of smoke