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

Frsky Telemetry not working on Holybro Kakute F7 #14802

Closed
benjinne opened this issue Apr 30, 2020 · 8 comments
Closed

Frsky Telemetry not working on Holybro Kakute F7 #14802

benjinne opened this issue Apr 30, 2020 · 8 comments
Labels

Comments

@benjinne
Copy link
Contributor

benjinne commented Apr 30, 2020

When trying to use any of the UARTs on the Kakute, and configuring TEL_FRSKY_CONFIG to the matching tx pin no sensors (other than rxbat and rssi) are discovered on my transmitter (a Jumper T16).

To Reproduce
Steps to reproduce the behavior:

  1. Set TEL_FRSKY_CONFIG
  2. Discover new Sensors on transmitter

Expected behavior
A list of sensors should be displayed on the transmitter

*Other steps I tried

  1. using the non-inverted smart-port pad on my r-xsr
  2. verifying packets are being sent using "frsky_telemetry status"
  3. changing the mode using "frsky_telemetry -m" to both sport and sport_single
  4. tried rewiring to UARTs 1,2,3,6 and changing TEL_FRSKY_CONFIG
@dagar
Copy link
Member

dagar commented May 1, 2020

Any thoughts on this @bkueng?

@bkueng
Copy link
Member

bkueng commented May 4, 2020

Yes it requires NuttX changes to make this work on F7 - I'm still waiting on @davids5 for testing it.

@julianoes julianoes added the bug label May 4, 2020
@justas-
Copy link
Contributor

justas- commented May 14, 2020

Affects Kakute F7 AIO as well.

@benjinne
Copy link
Contributor Author

Affects Kakute F7 AIO as well.

That's what I'm using

@bys1123
Copy link
Contributor

bys1123 commented Jun 24, 2020

@bkueng Is this F7 NuttX change required include fmuv5?

@justas-
Copy link
Contributor

justas- commented Jun 30, 2020

Are there any updates on this?

@davids5
Copy link
Member

davids5 commented Jun 30, 2020

Sorry - I am running behind on getting to it.

@davids5
Copy link
Member

davids5 commented Aug 8, 2020

The fix for this is un #15492 that was merged. If this is not resolved please re-open

@davids5 davids5 closed this as completed Aug 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

7 participants