Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pixracer: SBUS input not working with Copter-3.4-dev #3605

Closed
rmackay9 opened this issue Feb 10, 2016 · 14 comments

Comments

Projects
None yet
8 participants
@rmackay9
Copy link
Contributor

commented Feb 10, 2016

No description provided.

@rmackay9 rmackay9 added the Copter label Feb 10, 2016

@rmackay9 rmackay9 changed the title Pixracer: SBUS not working with Copter-3.4-dev Pixracer: SBUS input not working with Copter-3.4-dev Feb 10, 2016

@olexs

This comment has been minimized.

Copy link

commented Feb 17, 2016

The 3.3.3 beta release available through the Mission Planner has the same problem. It definitely used to work in an earlier build of 3.4dev. This is currently a blocking issue for me, can't test my Pixracer quad since it has a FrSky X4R-SB receiver with SBUS being the only option.

@MR444

This comment has been minimized.

Copy link

commented Feb 19, 2016

Just tested SBUS (X4R) and 3.4-dev tricopter. No problems!
rcinput

@rmackay9

This comment has been minimized.

Copy link
Contributor Author

commented Feb 20, 2016

@MR444, great, thanks for testing.

Fixed in Copter-3.3.4-rc2.

@rmackay9 rmackay9 closed this Feb 20, 2016

@govsux

This comment has been minimized.

Copy link

commented Mar 19, 2016

FYI Cannot get my X8R Frysky receiver to work on the P racer sbus. It doesn't see it. I'm running the PX4 flight stack so it seems it's more than just amp copter code???

@olexs

This comment has been minimized.

Copy link

commented Mar 19, 2016

SBUS works fine with PX4 stack for me. Apparently, it's also fixed in APM now - I haven't tested, but have seen several videos of people using X4R-SB receivers with the Pixracer and APM. Will confirm tomorrow, since I'm planning on reflashing to APM anyway.

@lorbass

This comment has been minimized.

Copy link

commented Mar 21, 2016

@govsux
Same issue with Pixracer. PX4 (master, Beta, stable) do NOT recognize the radio channels.
APM (3.3.3) flashed with QGC or MP the radio channels are reconized and no problem to calibrate.

@govsux

This comment has been minimized.

Copy link

commented Mar 21, 2016

@lorbass Yes same here. Also APM 3.4 dev doesn't see sbus RX. 3.3.3 seems fine. Except... the wifi only works with PX4 not APM. Guess you just can't have your cake and eat it too yet.

@govsux

This comment has been minimized.

Copy link

commented Mar 21, 2016

APM 3.4 sbus does work now...

@lorbass

This comment has been minimized.

Copy link

commented Mar 22, 2016

@govsux I do not like Wifi because of possible interference with the 2.4 GHz TX/RX.
e.g. strongly recommended to disable Wifi at the Gopro camera. But I would prefer PX4 do to
the possiblity of VTOL Tailsitter.
I wonder why the PX4 developer not react on my Issue message in the appropriate List.
APM Developer are capable to solve the issue on 3.4 in no time

@govsux

This comment has been minimized.

Copy link

commented Mar 22, 2016

@lorbass Yes that does seem like it could create interference but there is already 2.4 mhz flying all over the place and no issue. But being so close to the RX does seem sort of risky. I would love it if we had an option in the params to shut wifi off when the board arms. Is that the VTOL Tailsitter you refer too? I read somewhere that has been discussed already. Re- PX4 devs... I think they are just really busy sorting out minor issues and growing pains. I did find out 3dr radio works fine with APM 3.3.3 and 3.4. It's odd that works but not blue tooth. Maybe it's my GCS or something. But as long as the 3dr radio's work I'm good to go. Anyway... as you know there are these discussions here too http://diydrones.com/forum/topics/pixracer-with-ardupilot?

@rezafarokhian

This comment has been minimized.

Copy link

commented Oct 16, 2016

hi. please help me. my futaba 8fg does not connecting s.bus to pixracer no channel detected in qgroundcontrol

@lorbass

This comment has been minimized.

Copy link

commented Oct 16, 2016

Nobody can help with no more detailed information.
e.g. which versions for QG and Firmware.
And why QG in order to use Ardupilot Firmware and not Missionplanner?
http://ardupilot.org/planner/docs/common-install-mission-planner.html
For me it's like a VW with Mercedes Engine.
Pixracer is something special. It works from AC 3.4 only.
In Missionplanner you will have to select Beta Version AC 3.4 rc5 so far.

@lvale

This comment has been minimized.

Copy link
Member

commented Oct 16, 2016

3.4 RC6 :) ;)

@Biswajit1995

This comment has been minimized.

Copy link

commented Apr 25, 2017

Same Here,

I have upgraded my Pixhawk firmware from copter 3.3.3 to copter 3.4 and, in RC calibration none of the channels are responding in QGroundControl and no green bars are showing up in mission planner. Don't know what to do.

Please help, if anyone has solved this issue.

Note: I am using FUTABA T14SG transmitter and FUTABA R7008SB receiver. I have tested my receiver and transmitter at least 50 times, no issue found on them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.