MDBT42V Series, Bluetooth 5.4, LGA module; nRF52832 based

The MDBT42V-AT comes with AT command firmware preloaded, so the host only needs to send high-level commands over UART to manage Bluetooth functions. In contrast, a standard module without AT firmware typically requires the developer to implement and maintain the BLE stack and application code directly on the SoC.

Applications that need reliable BLE connectivity but have limited firmware resources or tight development schedules are ideal candidates. Examples include beacons, asset tags, compact sensors, remote controls, handheld instruments, consumer accessories and small industrial nodes where a simple UART-based interface to a host microcontroller is preferred.

Advertising settings such as advertising time, enabling or disabling advertising, and LED indication patterns for advertising and connection states are configured through dedicated AT commands. This makes it easy to adjust behaviour during development, production or even in-field firmware updates without rewriting low-level Bluetooth code.

Yes. The module offers selectable on-air data rates of 1 Mbps or 2 Mbps and supports five different TX power levels. By choosing suitable combinations, designers can trade off maximum range, robustness, throughput and current consumption to match their application needs.

The AT command set includes controls for power-down modes and the use of DC-DC or LDO power configurations, while GPIO wake-up allows external events to bring the module out of low-power states. Together with the efficient nRF52832-class SoC, this enables long battery life in devices such as beacons and portable sensors.

The module provides AT commands for both hardware-style and software-style system resets, as well as for restoring configuration to default values. This simplifies recovery from misconfiguration and allows robust in-field maintenance procedures.

A dedicated AT command lets the host retrieve ADC readings, which are commonly used for monitoring battery level or other analogue voltages connected to the module. This avoids the need for a separate analogue front-end on the host system.

The module supports commands for setting and reading a serial number, as well as retrieving the device MAC address. These functions are useful for asset tracking, provisioning workflows and production test logging.

Yes. With regulatory approvals such as FCC, IC, CE, Telec (MIC), SRRC and NCC, together with RoHS and REACH compliance, the module is designed to support deployment in a wide range of territories and sectors, subject to final end-product testing.

The module is positioned as the peripheral/slave element and is intended to work alongside compatible central/master role modules in the same family. This allows designers to build complete systems—for example, a central gateway or controller with multiple MDBT42V-AT peripheral nodes—using closely related hardware across the network.