Thanks for the positve answer.
And yes, protocol is automatically recognized but you must tell the FC on which port pin to search
Good to hear Werner!!
Another problem (with calibration) was that if the Throttle bar value falls below 950,
The SRXL Bus values are not decoded! No bars move then!
Throttle above 950, all bars move again!
Multiplex SRXL Bus – Servos adjustment ±100% (standard) - Value: 950 - 2043
Multiplex SRXL Bus – Servos adjustment ±110% (max ) - Value: 895 – 2104
There are still problems with the assignment of the servos
(for me it would be logical)
Calibration RC-RX
RC1 – Roll – Aileron Parameter: SERVO1_FUNCTION value 4
Parameter: SERVO2_FUNCTION value 0
RC2 – Pitch – Elevator Parameter: SERVO3_FUNCTION value 19
RC3 – Throttle – Throttle Parameter: SERVO4_FUNCTION value 70
RC4 – Yaw ¬ – Rudder Parameter: SERVO5_FUNCTION value 21
RC5 – Radio5 – Aileron Parameter: SERVO6_FUNCTION value 4
Parameter: SERIAL1_PROTOCOL value 23
Servo Output
If you move the ailerons right or left with Ailoron 1 and 6, value 1337 1503 1670
and Rudder 1419 1503 1584!?
All other control stick movements, no bar moves.
What am I doing wrong here again.
The calibration of your four channels shows very different results mainly in the MIN values.
Did you use any triming on the transmitter. If so remove the trimming and recalibrate your Rx channels
Thanks for the info.
Sorry, I should have deleted the last entry if something like that happens.
Now everything works as it should (manual / stabilized)
It is now important that you do not choose the service path too far
and that you know that the order of the hardware does not match the order in the software.
One advise, choose channel 1 or 2 for throttle if throttle goes to an ESC.
Those channels form a group, so you can use advanced ESC protocols like DShot for the motor control.
If your throttle is a servo for a combustion motor, it does not matter.