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
Hi Peter,
have the same issue 2 brand new Pixhawks and cannot use them ...
in worthcase you can use PPM encoder :-( i will get soon taranis Radio.
could someone please compile the io firmware and attach it here ?
thanks
Thomas
Trisatan
Please join Google group "drones-dscuss" and post your result.
BTW, I am not a member of this group;-p
https://groups.google.com/forum/#!forum/drones-discuss
@Tristan: see my latest post here, thanks!
On my trial of S-Bus connection to Pixhawk.
1) Futaba R6303SB: Good
2) FrSky TFR8SB: Good
3) Futaba R3008SB: Fail (S-Bus nor S-Bus2)
4) FrSky TFR4B Good
*FrSky TFR4B is actually not a S-Bus receiver.
Compatibility List of Futaba receiver and Pixhawk
Xian; You mean something like this difference of S.Bus protocol ?
Xian,
Please - S.BUS2 is supported by Pixhawk. Here is the line that does decode S.BUS1 or S.BUS2.
https://github.com/PX4/Firmware/blob/master/src/modules/px4iofirmwa...
I can only recommend to get in touch with the APM developers (e.g. via the drones-discuss Google group) to check what the status is on a release incorporating this. You could compile the code yourself today and have S.BUS2 going.
-Lorenz
QGroundControl provides more information while updating firmware than Mission Planner.
It is stopped at 90% to updating firmware of the Pixhawk.
QGC also hard to detect Pixhawk version of PX4IO board.
After several try and error, Pixhawk gives endless tone.
OUCH!
It became Brick!?
Thanks, I will try later.
BTW, temporary bricked Pixhawk could awoke by hooking "px4uploader.exe" ;-)
Brand new Futaba R3008SB is also fail connection with Pixhawk.
-
5
-
6
-
7
-
8
-
9
of 9 Next