Growing problem!..

[PatrikE]

It's a problem of luxury ...
The number of supported FlightControllers is constantly growing.

In _r1232 i can count to 54 different FC!..
V2.1 have 45 FC's
I believe MWii must be the MK project who supports most boards.

Back to the problem......
How are we supposed to identify all the FC's
The situation isn't impoved by Bad markings on the boards.
It's easy to be lost in the jungle...

I think we need a reference register or some database with Pictures,Names and information of the boards.
It means collecting lots of data somewhere permanent.
Config.h contains some links to webshops etc.
But the info there is temporary and usually dissapear when the board is discontinued.

Does anyone else se the problem?

[copterrichie]

I think it should be the manufacture responsibility to provide a signature for the board or config.c and the def.h files.

[Alexinparis]

It's a problem of luxury ...
The number of supported FlightControllers is constantly growing.

In _r1232 i can count to 54 different FC!..
V2.1 have 45 FC's
I believe MWii must be the MK project who supports most boards.

Back to the problem......
How are we supposed to identify all the FC's
The situation isn't impoved by Bad markings on the boards.
It's easy to be lost in the jungle...

I think we need a reference register or some database with Pictures,Names and information of the boards.
It means collecting lots of data somewhere permanent.
Config.h contains some links to webshops etc.
But the info there is temporary and usually dissapear when the board is discontinued.

Does anyone else se the problem?

I think a board should be added in the code only if you feel relatively confident about the "source" of the code line. Otherwise, no.
"Bad markings on the boards" effect is only the fault of who added it without any checking. It's not due the the growing FC number.
I personally add without exception any board I own, or for which the manufacturer gives me the lines to add.