Thanks Eliot - for the response on the light Pwm duty cycle I posted the the specs on the the led driver I am using post before.
I went on a wild chase with the software last night and basically install every single one to make sure I was not going crazy but when I did the Pixhawk1-1M it kepts giving me an error too after it installed but kept say I should use the frmuv2 intead of the -1M.
Only way I got it to work again without any error was go back to the 4.1.2 (Fmuv2) ,which calmed me down because I was on a nervous breakdown.
That depends on whatâs connected to it, how much current it draws, and whether the output voltage is outside the range of the components youâre connecting.
We normally recommend using a 5V 6A BEC inside our vehicles, which is used to power a Raspberry Pi + a flight controller board + a camera tilt servo.
That parameter has been removed in recent ArduSub versions, in favour of just directly specifying the type of each servo output. You may need to install a more recent QGroundControl version which knows about the more recent parameters.
I install the lastest Ground Control and I am still getting this error - any help with how to work around this will be highly appreciated - I know you said something about servo .
I install the lastest Ground Control and I am still getting this error - any help with how to work around this will be highly appreciated - I know you said something about servo .
HI Fam - I still cannot get out of the disable mode on my firmware , I did all the updates and no progress or do I make all these setup in the 1.4 stable software in BlueOS? Sorry to drag this too long but I really need help
Do you mean the message in your second screenshot? Add Eliot explained, it is not possible to eliminate that message while using older versions of QGC⊠But it doesnât impact functionality!
When you try and arm the vehicle, what error do you receive?
Hi Tony- I figure it out and was able to get the light configured on the software side , for some reason, I was trying to get it done on the QC interface which was grayed out - Now , I have to play with Mosfet I bought on Ali Express and if I do recall , some modification will have to be done with the PWM on the prevoius one .
Can you let me know if I still neeed to any modifcation on this one below or it should work right off the Pixhawk
A MOSFET just passes out whatever signal you put in, scaled to the MOSFETâs input voltage level.
ArduPilot firmware (like ArduSub, which is running on your Pixhawk) assumes that connected outputs on its servo rails use servo-style PWM values (with pulse durations ranging between ~1000-2000”s, regardless of frequency). For directly driving an LED you likely want duty-cycle PWM, where the pulse durations are instead set to provide a proportion of ON vs OFF time within the period of the pulse frequency - i.e. you want 0-100% pulses[1], and will need to do some extra configuration to enable that.
Assuming youâre still on the old firmware version you managed to get working, the instructions I linked to should still generally be correct. In summary:
Basic lights configuration
The lights 1 channel is configured by setting the relevant SERVOn_FUNCTION parameter to RCIN9 (59)
BlueOS does this for you (when you choose the Lights 1 channel)
Newer firmware versions use a dedicated Lights1 (181) function value, in case thatâs relevant
The number of steps (between min and max) for the lights increment/decrement joystick button functions is configured using the JS_LIGHTS_STEPS parameter
BlueOS does this for you when you set the âJoystick stepsâ field in the Lights setup
PWM duty-cycle configuration
Frequency checking / configuration
Frequency of MAIN outputs 1-8 are controlled (as a group) by the RC_SPEED parameter
With your current configuration of Lights 1 on Channel 7, this is the relevant one for you
For Navigator flight controller board users this parameter controls all of the servo rail outputs, because thereâs only one driver for all the channels
Frequency of AUX outputs 1-6 are controlled (as a group) by the SERVO_RATE parameter
You may need to change to using one of these outputs if the MAIN outputs cannot manage the fully off or on duty-cycle states, since theyâre not really intended for driving non-servo signals
Setting relevant channel limits
The lights 1 limits are configured using the RC9_MIN / RC9_MAX parameters
Newer firmware versions instead use the SERVOn_MIN/MAX parameters of the channel youâre configuring
For a 0% duty-cycle, the minimum value should generally be set to 0”s
Itâs possible this will skip the lowest joystick button step, which could be annoying, in which case you can try setting it to 1”s (which is probably close enough to off for most use-cases, especially if the frequency is relatively low)
For a 100% duty-cycle, the maximum value should be set to the period corresponding to the relevant channel group frequency \left(\frac{1000000}{\text{freq}}\right)
e.g. for channel 7, with RC_SPEED set to 50Hz, the max would be 20000”s
If the relevant frequency is set to 200Hz, the max would instead be 5000”s
