Eachine Racer 250 CleanFlight Motor Mapping
CleanFlight on the Eachine Racer 250
When swapping the CC3D for a SP Racing F3 Pro Mini, I soldered up the connectors so that the ribbon cables connectors matched up to the numbering on the board. My PWM outputs 1-4 were therefore mapped directly to pins 1-4, silk screened into the board - this seemed perfectly logical at the time of building, but when configuring CleanFlight later it became apparent that it's naming convention is different to the Eachine Racer 250.
The following table shows what CleanFlight expects, versus the mapping printed on the board.
|Bottom Right 1 CW||2 CW||3 CW|
|Top Right 2 CCW||3 CCW||2 CCW|
|Bottom Left 3 CCW||1 CCW||4 CCW|
|Top Left 4 CW||4 CW||1 CW|
So for example, the PWM pin number 1 on the SP Racing F3 Pro Mini is connected to the Pin 1 marked on the Eachine Racer 250 board, however when CleanFlight spins this motor up it's actually spinning up what it thinks is motor 3. And in KK2.1, for reference, this would be named motor number 3.
Motor Mapping Using MMIX
You can remap the motors by using the CLI and entering the following, copy and paste will work just fine. The first command tells CleanFlight to use a custom mixer, rather than the pre-defined layouts you can choose. This will cause the 3d model of the drone to change to a block with top/bottom/left/right on it and you'll also see a big question mark in the config page rather than a graphical representation of the layout.
mixer custom mmix reset mmix 0 1.0, 1.0, 0.930, 1.0 mmix 1 1.0, -1.0, -0.930, -1.0 mmix 2 1.0, -1.0, -0.930, 1.0 mmix 3 1.0, 1.0, -0.930, -1.0 set yaw_control_direction = 1
`set yaw_control_direction = 1` may not be required, but if you've previously changed it whilst messing about (like I did) then you'll want to reset it with this config. Once done, ensure you execute a `save`, which will save the settings and cause the board and GUI to reload.