Thank you for complementing the documentation. Unfortunatly it did not help.
As far as I understood these settings affect the TL2 Port on the Pixracer board only (TL1 unaffected).
I tried all 5 settings without success. As far as I understand the Teensy initially polls the flightcontroller to send specific parameters via MavLink. I can see this initial request via the LED briefly lighting up on the Teensy. Then nothing happens anymore.
Connected to a Pixhawk v2 with AC3.3 the request of the Teensy is followed by the LED rapidly flashing, indicatng that it receives data. Somehow this "handshake" seems to fail on PX4
Furthermore we developed a Raspberry based All-in-One WiFi solution (realtime HD Video and OSD downlink + MavLink Command Uplink). Works flawlessly using a Pixhawk with AC3.3 and these settings:
* SERIAL2_PROTOCOL 1
* SERIAL2_BAUD 57
* SR2_EXT_STAT 2
* SR2_EXTRA1 8
* SR2_EXTRA2 2
* SR2_EXTRA3 0
* SR2_PARAMS 2
* SR2_POSITION 2
* SR2_RAW_CRTL 0
* SR2_RAW_SENS 0
* SR2_RC_CHAN 0
OSD and MavLink Control Uplink do not work at all with PX4 yet - regardless which of the 5 presets we tried.
Correct cabling and connections have been double checked already.
Wouldn't it make sense to implement a 100% Arducopter compatible/identical way to configure the serial Ports for PX4?
There are tons of MavLink peripherals out there which need very specific parameters and settings in order to work properly. I am not sure if one can give good coverage for all those solutions with 5 presets?
Many Thanks for the excellent Support and Help in Advance!