Thrust commands not accepted when using FrSky TX as controller
Posted: Tue Nov 17, 2020 12:49 pm
Hi,
I'm currently trying to control the CF2.1 (via the cfclient, current version) with a FrSky RC transmitter and the corresponding FrSky USB Sim dongle. The TX/dongle is visible in the OS as a joystick. I'm able to "see" and configure this input device in the cfclient menu and I've created an associated input mapping file (attached below). When I move the controls on the TX the corresponding control input values displayed in the cfclient move/change value including the thrust bar (see screenshot). However, the thrust command has no effect, i.e. the motors do not start. When I take off in assisted mode ("hover", the CF has a flow deck) I'm able to control pitch & roll / fwd & lateral speed but not thrust/vertical speed. When I use a PS4 game controller everything works fine, including thrust.
Are there any further diagnostics available (e.g. via the logging framework)? What could cause the thrust commands, that are quite obviously received by the cfclient, not being passed on to the CF?
Thanks and regards
Tintin
I'm currently trying to control the CF2.1 (via the cfclient, current version) with a FrSky RC transmitter and the corresponding FrSky USB Sim dongle. The TX/dongle is visible in the OS as a joystick. I'm able to "see" and configure this input device in the cfclient menu and I've created an associated input mapping file (attached below). When I move the controls on the TX the corresponding control input values displayed in the cfclient move/change value including the thrust bar (see screenshot). However, the thrust command has no effect, i.e. the motors do not start. When I take off in assisted mode ("hover", the CF has a flow deck) I'm able to control pitch & roll / fwd & lateral speed but not thrust/vertical speed. When I use a PS4 game controller everything works fine, including thrust.
Are there any further diagnostics available (e.g. via the logging framework)? What could cause the thrust commands, that are quite obviously received by the cfclient, not being passed on to the CF?
Thanks and regards
Tintin