The short answer
A MADBrain autopilot is not an isolated unit. The chain includes the navigation processor, motion and wind data, rudder angle, acquisition interfaces, the MADController that drives the power unit, the mechanical or hydraulic actuator, and crew controls. To prepare a project, diagram this chain on your vessel and qualify each interface: reference, signal, voltage, protocol, range, frequency, and failure scenario. Do not purchase software or an interface before validating the actual sensor and actuator. A promise of CAN or NMEA 2000 integration alone does not prove the compatibility of an existing reference.
The autopilot is a complete loop
The computer compares a setpoint to the estimated state of the vessel, decides on a correction, and commands the actuator. The vessel reacts; the sensors measure the new movement, and the loop restarts. Quality depends on the entire chain, not just the algorithm.
Unstable heading data, an incorrect rudder angle, poorly acquired wind data, a noisy power supply, or an undersized actuator can limit an excellent computer. Conversely, replacing all sensors without addressing mechanical play or hydraulics does not resolve rudder control.
The Madintec catalog separates the computer, software, sensors, interfaces, controller, and remote controls to make this architecture readable.
MADBrain: processor and software functions
MADBrain is presented by Madintec as the core of the navigation and piloting system. The official brochure describes CAN, Ethernet, and serial integrations, as well as motion and wind processing. Software functions are offered in modules or modes depending on the package.
Before selecting these functions, list the available data and its source: attitude, heading, speed, apparent wind, rudder angle, and potentially performance information. Note their frequency, quality, and the path to the computer.
« Wind », « safety », or « performance » software does not create the data it lacks. Verify the prerequisites for the exact version and the license scope. A mode name is not a guarantee of autonomous safety.
MAD Sensor Motion and attitude sources
The attitude sensor provides information necessary for motion estimation. Its location, orientation, mounting rigidity, power supply, and calibration influence the measurement. Keep it away from disturbances identified in the documentation and record its actual orientation.
If an existing source is to be retained, identify the message and protocol actually provided, not just the brand of the display. Multiple devices can transmit the same data on the network; choose a primary source and avoid uncontrolled switching.
After installation, verify the axes, heading, roll, and pitch both at the dock and at sea. An inversion or constant offset must be corrected before autopilot operation.
Wind: acquisition and validation
The MAD Interface Mast is described in the brochure as a wind acquisition module, specifically from an NMEA 0183 input, with data verification. Real wind calculation also depends on available motion and speeds.
For an existing sensor, note the reference, baud rate, sentence format, frequency, cabling, and settings. NMEA 0183 is a family of serial connections: two « NMEA 0183 » devices are not automatically ready to communicate without agreement on electrical level, direction, baud rate, and sentences.
Compare displayed wind and actual behavior across various points of sail. An offset or a disturbed mast sensor can degrade the wind mode even if the computer receives numerical data.
Rudder angle: closing the mechanical loop
The angle sensor indicates the actual position of the rudder blade. The Madintec brochure presents the MAD Sensor Rudder and its output range. The installation must translate the entire rudder travel into a monotonic measurement, without sensor stops or play in the linkage.
Measure port, zero, and starboard angles with the actual rudder. Verify that the displayed direction corresponds to the physical direction. Secure the linkage so that it cannot detach or exceed its travel.
Software calibration does not correct a flexing lever, a sensor reaching its stop, or a rudder whose angle is not symmetrical. Document the geometry and end-of-travel values.
MADController and actuator
MADController is the unit that controls the actuator's power according to the system. It is located between the computer's decisions and the motor, pump, or steering mechanism. Voltage, current, feedback, protections, and actuator type must be compatible.
The choice between hydraulic and electromechanical cylinders is detailed in the hydraulic or electromechanical cylinder guide. In all cases, calculate the force, speed, travel, and cycle according to the steering gear and vessel.
Add mechanical stops, electrical protections, and disengagement procedures. The autopilot must not use the actuator or sensor as a rudder stop.
Interfaces and remote controls
The MAD Interface Analog, Digital, and Mast respond to distinct signals and functions. For each, establish the converted data or command, the direction of flow, and behavior in case of loss. An interface is not a « universal adapter ».
Wired and radio remote controls are used to engage, correct, or change modes according to the configuration. Define stations, actual range, access to essential controls, and manual override. A remote control does not replace access to the helm or the shutdown procedure.
Label the controls and verify that a click produces the expected action before testing under sail.
Commissioning layer by layer
First, validate power supplies and networks, then each sensor independently. Then, control the rudder angle and actuator command at low effort. Test the correction direction: a sign error can make the rudder go the wrong way.
Proceed to sea trials in moderate conditions with a crew member ready to take over. Start with heading mode, then modes dependent on wind or performance data. Record versions, calibrations, and results.
The recipe must include sensor loss, voltage drop, control cutoff, and manual override. A high-performance system is also a system whose crew understands degraded states. The autopilots hub then allows comparing architectures without inferring compatibility between brands.
Frequently Asked Questions
Can MADBrain use all NMEA 2000 sensors?
No, not as a simple principle. You must verify the data, versions, interfaces, and supported references for the actual configuration.
Is it always necessary to replace the existing actuator?
Not necessarily, but its electrical, mechanical, and dynamic compatibility must be proven with the controller and the vessel.
Is the rudder angle sensor optional?
This depends on the documented configuration. For a specific project, verify Madintec prerequisites; do not dismiss it based on an assumption.
Does safety software replace onboard procedures?
No. It can add a function to the system, but the crew, structural limits, and recovery procedures remain essential.
Official Sources
- Madintec — MADBrain Autopilot
- Official French brochure
MADBrain — The autopilot reinvented, SHA-256 hash54f11d032b8b8e9b1ccb0b3dc09e4ad692908f8c51212cfac21924a62e903a18, archived and OCR'd in Nexus on May 6, 2026. - NMEA — marine standards NMEA 0183 and NMEA 2000
