Are you in Australia and looking to purchase a Matek H743 WLite Wing flight controller? This top - notch flight controller comes with an array of great features. Its MCU is the STM32H743VIH6, running at 480MHz with 512KB RAM and 2MB Flash. The IMU is the ICM42688 - P, and it has a DPS310 barometer. It also features an AT7456E OSD and a MicroSD card slot for blackbox recording. With 7 Uarts, 13 PWM outputs, and 6 ADCs, it offers great flexibility. It has 3 LEDs for FC status and a 3.3V indicator. The controller supports 2 I2C interfaces and 1 CAN. It comes with a USB/Beep Extender with Type - C. There are dual camera inputs and a 9V(12V) VTX power switch. It has high - precision current sensing up to 220A. The firmware supports INAV and ArduPilot. The PDB has an input voltage range of 6.8 - 30V. It has various BEC outputs for different devices like flight controllers, receivers, video transmitters, and servos. Physically, it has a 25 x 25mm mounting, dimensions of 44 x 29 x 14.5 mm, and weighs 22g with the USB/buzzer adapter. The package includes the H743 - WLITE, USB/Beep Extender, cables, a capacitor, and Dupont pins.


Using the Matek H743 - WLite flight controller is quite straightforward. First, connect it to your aircraft according to the mounting holes (25 x 25mm). Use the provided cables to link different components like CAN and I2C devices. Plug in the USB/Beep Extender with Type - C for communication and beeping functions. When powering it, make sure the input voltage is within the 6.8 - 30V range for the PDB. For different BEC outputs, connect the appropriate devices such as flight controllers, receivers, video transmitters, or servos. When using the BEC outputs, ensure the input voltage is at least 1V higher than the output voltage for stable operation. Regarding maintenance, keep it clean and dry. Avoid exposing it to extreme temperatures or humidity. If you need to replace parts, make sure to use compatible components. Regularly check the connections to ensure they are secure. If you face any issues, refer to the INAV or ArduPilot firmware documentation for troubleshooting.