FrSky FPort support - testers wanted

please test the latest fw from here:
https://firmware.ardupilot.org/Plane/latest/MatekF765-Wing/

Not sure what I doing wrong but I cannot load 4.1 to test.
Process:
Ctrl-Q to populate the latest release.
Connect the FC, and wait few seconds to make sure USB is recognized.
Pick the plane type
Question/answer = “No” (Is this CHIBOS, Pixhawk, AMP 2+)
it reads the board but during upload fails.

please try downloading the fw from firmware.ardupilot.org then use “load custom fw”

I already tried that.

@tridge, I have tried all the tricks in the book to load 4.1dev on F765, it reads the file from the board but during install, the process fails.
I can connect this with MP and it works fine, but unable to load new FW. I tried both _bl and non _bl files.

Any other suggestions.

You might want to try iNav configurator to load 4.1.

I upgraded from 4.0.5 to 4.0.6 and didn’t had any issue.
Read my process above, is there something I am doing wrong?

Assuming you already have Ardupilot running on the board the .apj file should do the job via MissionPlanner.

Are you saying not to use hex file, use apj file?
Yes, I have arduplane on the FC.

@RizHass
Exactly. If you already have a version of Ardupilot running on the board and recognized by MissionPlanner you can update the board via MissionPlanner.

Further details can be found here:
https://ardupilot.org/plane/docs/common-loading-firmware-onto-pixhawk.html

In your case you should look for the button “Load custom firmware” on the lower right.

Good luck!!

@tridge, I uploaded the development FW (4.1.0) on my F765-wing, using R9 receiver with fport. Parameter settings are listed below. I have RC control but no telemetry, meaning no info from the FC.

  • SERIAL7_OPTIONS=15
  • RC_OPTIONS=8
  • RSSI_TYPE=3
    fport wire is connected to UART6.

BRD_ALT_CONFIG (1)
SERIAL7_PROTOCOL (23)
SERIAL7_OPTIONS (15)
RSSI_TYPE =3
RC_OPTIONS (try at default otherwise 8)

@Dave, I have tried all these parameters without any telemetry response.
somthing still not working.

I have kakute f7 with teko32 4 in 1. Flashed with 4.1 dev from 30-Oct
R-XSR with RXSR_ACCST_2.1.0.Fport_LBT
Taranis X9D+ with OpenTX 2.3.9 and internal module with XJT_ACCST_2.1.0_LBT.frk

Then the R-XSR s.port wire connected to the Kakute Rx6
and

  • SERIAL6_PROTOCOL=23
  • BRD_ALT_CONFIG=1
  • SERIAL6_OPTIONS=15
  • RSSI_TYPE=3
  • RC_OPTIONS = 0

Control and telemetry working now

1 Like

Yes, this has been working for me also on a Kakute F7 with an R9MM and Fport firmware. UART6 is SERIAL7 on the Wing so assumed the config would work.

It’s the original R9 Rx (the big one)? Which specific firmware?

@RizHass take a look at this post.

RC_OPTIONS must be 0, not 8 for the setup you are describing.

@tridge, Any chance of backporting this to 4.0.x?

Its working for me now (Matek F765-wing, R9mm Rx, and FW 4.1.0dev) with the parameter mentioned above. The reason it was not working for me initially, was because Serial6 was enabled. Once disabled, I started receiving Yaapu telemetry.