Mainboard and flight controller
Broken traces, burnt components, memory shaken loose. We solder on the board itself rather than replacing it, even when the part is no longer supplied.
Home-built and research aircraft are normal here.
Leuven has research, and research means aircraft that did not come out of a box. Students and labs build their own, hang sensors under them that were never meant for it, and run firmware they modified themselves. That breaks more often than a factory aircraft, and it breaks in different ways.
We enjoy that work. A board with no documentation, measured through until we know which line is dead, is exactly what a workshop should be able to do. You do not need a serial number and you do not have to explain why there is an extra cable coming out of the aircraft.
One thing, though: tell us what you changed yourself. That saves us hours of searching and saves you money.
Broken traces, burnt components, memory shaken loose. We solder on the board itself rather than replacing it, even when the part is no longer supplied.
Aircraft frozen during an update, activation that keeps failing, error messages that keep returning. Often solved without replacing anything at all.
A motor that stutters, an arm that will not spin up, controllers blown after a crash. We replace the failed component, not the whole module.
You do not have to drive. Everything happens by courier, and you know where your aircraft is at all times.
The more concretely you describe the fault, the sharper our first estimate. Answer within one working day.
Briefly describe what is wrong. Within one working day you will know what it probably is and roughly what it costs.