Hi
Two of my customers have trouble setting up the Pixhawk - I myself have a Pixhawk, but don't use a Futaba receiver, thereby I can't replicate the problem (I would like to find out if the problem is connected to the receiver they use, or something else).
Both use a Futaba R7008SB receiver.
Both managed to upload the Firmware to their Pixhawks - but they are not able to do the radio calibration (the Pixhawk doesn't "see" the receivers, the bars in the calibration are all grey).
They have nothing else connected to the Pixhawk, except receiver (connected to the right port / RC), buzzer, safety switch and USB cable.
The Pixhawk signals via the big LED "pre-arm check failed" (which makes sense ;)
They power the Pixhawk via USB and at the same time with a LiPo (via the Power Module).
The receiver is "found" by the remote, the LEDs are on, the setting of receiver and remote (regarding the use of the SBUS) seems to be right. They use the right port of the receiver to connect to the Pixhawk.
I am happy about any suggestions ...
Thanks a lot in advance
Felix
Replies
DO NOT POWER THE RECEIVER FROM ANY EXTERNAL POWER SOURCE OTHER THAN PIXHAWK.
Still waiting for solutin, Pixhawk and R7008SB rx. I cant use Pixhawk without rx.
(I have telemetry sensors so I cant use other rx)
Can somebody confirm that Futaba R7008SB is working with Pixhawk?
I can confirm it works with Pixhawk when connected to RC IN. I do not know if the last stable release of the APM software includes support.
Hi Lorenz,
which firmware version are you using on the Pixhawk (the one where it works)?
Hi,
i have the same Problem.
I use a Futaba R7008SB receiver and Pixhawk (1 Week old)
It's not able to do the radio calibration.
The Messages in APM Planner are:
[MAV 001:1] UNABLE TO DECODE MESSAGE NUMBER 152
[MAV 001:1] UNABLE TO DECODE MESSAGE NUMBER 162
[MAV 001:1] UNABLE TO DECODE MESSAGE NUMBER 163
[MAV 001:1] UNABLE TO DECODE MESSAGE NUMBER 165
[MAV 001:1] UNABLE TO DECODE MESSAGE NUMBER 2
[MAV 001:1] ArduCopter V3.1.1 (681dafcf)
[MAV 001:1] PX4: bf42b124 NuttX: a6686464
[MAV 001:1] PX4v2 31003C00 07473234 38353838
[MAV 001:1] Calibrating barometer
[MAV 001:1] Initialising APM...
[MAV 001:1] barometer calibration complete
[MAV 001:1] GROUND START
[MAV 001:1] PreArm: RC not calibrated
[MAV 001:1] PreArm: RC not calibrated
[MAV 001:1] PreArm: RC not calibrated
r7008sb is in Mode B
Any idea?
Thanks Dmitri
Hi,
The same config with R2008SB and Pixhawk can receiver "see" and radio calibration OK.
May be 16 channels-SBUS message from R7008SB too long?
The Futaba receiver R7008SB has a slight modification to the S.Bus protocol,
which makes it unusable with the current firmware.
http://forums.openpilot.org/topic/31284-futaba-sbus-changes/
"FASSTest 12CH" mode generates frames every 6.3ms.
This only allows 10 channels, plus 2 digital (on/off) channels, and
it only allows RX and Ext bat voltages for telemetry.
For the "FASSTest 12CH" mode using the R7008SB, the protocol is the same,
except the endbyte is fixed at 00010000. This would actually make an easy fix
from the original s.bus code if you only wanted to use the FASSTest 12CH mode.
Default endbyte = 00000000b
Please, compile a special R7008SB 12CH mode px4io.bin with 00010000 endbyte for testing.
Are those files for Pixhawk though??
Mine works great on FrSky TFR8SB Rx
R6303sb does work with T14sg and 3.1.1-rc1, atleast for Trad Heli. It does need a 'forced update' for IO firmware(Safety switch at power-on)