Hi all. New to this, just baught a second hand blue2. Has the std lights, but a relay board to control the lights. I cannot get them to turn on by the programmed aux port on the pixhawk.
And when connecting to another free aux port they are constant on. Tried to re program but naa. The Dashboard changes light % fine from 0-100%.
Could you share which ArduSub version you’re running, which port you have the lights plugged into, the corresponding SERVOn_FUNCTION parameter value (e.g. n=9 for AUX 1, and n=14 for AUX 6), and how you’re trying to control the lights?
Do you know what this is being used for / how it’s being used? If you’re using our Lumen lights they shouldn’t require anything between the signal wire and the flight controller board output pins.
If the relay(s) don’t switch fast enough then it may only be possible to use on/off control over the lights, rather than the variable control that’s possible with servo-style PWM commands.
It may also be relevant to know the other software you’re using. Is your vehicle running BlueOS, or the old Companion software? Are you controlling it with QGroundControl or Cockpit? Which versions?
I will post a few grabs showing the current SW versions etc. Easier that way:-)
Many settings may have been altered, not sure.
It is running blueos
I do not know why the relayboard is connected to the lights, but can disconnect and hook them up direct for test. Are they normally all connected to one output? or maybe i can set them up as 2x2.?
Im also looking for any info or feedback on upgrades to Navigator, is it a big difference ?
That depends how the lights are wired. If you have a daisy-chained quad set of lights then you’ll only be able to control them all simultaneously, but if you have two pairs then it should work fine to connect each pair independently (via the Lights1 and Lights2 outputs).
I’d suggest taking a look through this post. Whether the differences are meaningful depend on your operating priorities. I suspect for most users the Raspberry Pi upgrade is the most significant part, assuming the current flight controller is still working fine.
That error can be safely ignored - the QGC version is just too old to know about the latest parameters, and that parameter stopped being necessary a while ago.