Tricopter support for NAZE-32 broken about cleanflight-configurator

[mikeller]

Your configuration seems to be from an old version of the firmware. This looks like the firmware update did not work at all, and instead just mangled your configuration.

[icebreaker-ch]

In fact the file represents the old configuration which I tried to load into the new software.
But even after a full erase and new full setup of the configuration, the behavior was the same; Servo on channel 1 seems to be controlled as an ESC, not as the yaw servo (No reaction on rudder stick but on moving the copter in roll and pitch axes). For a tricopter, the connections on the ESC port should be as follows:
CH1: Yaw Servo
CH2: -
CH3: Motor 1
CH4: Motor 2
CH5: Motor 3

I Think this is exactly the same problem as described here: cleanflight/cleanflight#2775
Seems the mapping has been changed compared to Version 1 or the servo is not assigned at all.
I will try to reconfigure the resource mapping as described in issue 2775.

[icebreaker-ch]

The following mapping seems to work for my NAZE32:

resource servo 1 A08
resource servo 2 A11
resource motor 1 B06
resource motor 2 B07
resource motor 3 B08

I would appreciate, if this mapping is set on using a Tricopter configuration (as it was in V1)

[mikeller]

@icebreaker-ch: Good to see that you managed to find the solution for your problem! The problem with resource mappings for different mixers is that they are entirely dependend on pin allocation for the different outputs, and hence different for every board. (i.e. on NAZE, motor pins 1 & 2 share a common timer, and 3 - 5 share another one, so the split between motors and servos has to be 1, 2 / 3, 4, 5.) In cleanflight 1, which supported 2 dozen or so different boards, the definition of the resource mappings for different mixers for all of these boards was a horrible mess. With over 100 boards supported in cleanflight 2, maintaining these mappings in firmware is simply not feasible. At some stage we will be looking into adding and maintaining mappings in the configurator, but even this will require a lot of work, and unfortunately a lot of the board vendors are not exactly forthcoming with support for the target definitions for their boards...

[icebreaker-ch]

Thanks a lot for your work.