Hi, I’ve been having difficulty getting both my lumen lights to work at the same time. I followed the advice on this thread, but everytime i set the value for output 13 and 14 to be the same thing (both RCIN9) it disables the other.
On top of this when i do try set them to be RCIN9 and RCIN10, when I reboot the autopilot it changes them to be “Custom: 181” for output 13 and “Custom: 182” for output 14. For some strange reason the light plugged into output 13 does work when its set to “Custom:181” but the light on output 14 does not work.
I’m mostly confused because the lights had previously both been turning on and I hadn’t touched any of the BlueOS parameters. Any help getting both of them to work without having to attach the yellow wires would be appreciated.
Did you recently update your ArduSub firmware? What version of ArduSub and BlueOS are you using? There have been some major changes to how the lights are labeled - newer BlueOS versions convert those custom numbers into something more human readable. Please verify you’re running BlueOS 1.4.3 - a stable version update to 1.4.4 is imminent!
ArduSub used to overload the RCIN passthrough outputs for its lights functionality, but in 4.5.5 transitioned to using dedicated Lights1 (181) and Lights2 (182) outputs. The latest firmware detects the old RCIN9/10 configuration and auto-corrects it on startup, but if you change it after booting then the lights won’t work until rebooting the autopilot.
The new lights values should show up correctly in BlueOS 1.4.3, though the Lights page in vehicle setup has only been properly updated in the upcoming 1.4.4 release.
If you want to control multiple sets of lights with a single signal (e.g. Lights1), I’ve confirmed it should work fine to just assign the same function to the relevant outputs.