Gents I need your help.
I recently upgraded one of my 2.6APM powered quads to a Pixhawk. One of the reasons I went ahead and did this is because the Pixhawk is supposed to take PWM RSSI signals directly (into the Sbus port aka Pin 103) and I could ditch my PWM to analog conversion circuit is used in my APM.
I have verified that my EZUHF receiver is outputting RSSI in PWM form on one of the channels. (it will move a servo appropriately when the RF gets weak or disappears... and it worked fine for the APM as an RSSI input via a PWM to analog conversion circuit)
And, I have hooked up the PWM RSSI output to the Sbus port (pin 103).... it does nothing. Shows zero RSSI on the OSD no matter what.
I can't find any useful description of how to configure this in the wiki, mission planner or this site.
How do you make a Pixhawk show RSSI from a PWM input on pin 103 as its advertised?
Thanks for your help.
Hi, I am struggling to make ezuhf to work with fixhawk(rctimer pixhawk). But can't see my rc inputs over msn planner. Looks like the fixhawk board is not listening to the rx. Is there any step by step instruction for making it work with ezuhf rx? Thanks
Steve Cain said:
The PPM output from the EZUHF works nicely with both APM 2.6 and Pixhawk. I highly recommend the EZUHF radio gear. I have 4ch, 8ch lite, and two 8ch diversity receivers. All are used for 8 channels (including the 4 channel one) via PPM sum output on channel 1.
The current "issue" I am having is simply that the PWM (pulse width modulation) output for RSSI or Link Quality that can be sent from the EZUHF receiver has to go through a special home made circuit to turn the PWM signal into a readable analog signal so the APM or Pixhawk can get signal strength or link quality to show up on my OSD. I have used 1cell non-brushless speed controllers from hobby king for this for the last year with the APMs and I'm sure it will work ok with the Pixhawk too, I'd simply prefer a direct connection. (as they promised)
I did hear from Craig at 3DR that the PWM input for RSSI will be included in a future software release...he did not indicate which one... I have not yet looked to see if it is on the list for 3.2 which is at least 6 weeks away according to Randy.