Skip to main content

BDE-BLEM301

Bluetooth module

BDE-BLEM301

BDE-BLEM301 is one of the most cost-efficient Bluetooth® 5.1 Low Energy Module in the field. Based on Dialog ultra-low power DA14531 SoC, it comprises a Cortex® M0+ MCU, 1Mbit on board Flash memory, a Bluetooth 5.1 Low Energy radio and a high efficiency PCB antenna in a single module.

The module can be used with or without an external MCU. It also offers flexible hardware interfaces for sensor applications. BDE-BLEM301 is compatible with Dialog DA14531 TINY™ Bluetooth Module - DA14531MOD. The same software tools and hardware kits can be used for BDE-BLEM301. It is empowered with Dialog BT5.1 qualified Bluetooth LE stack and SDK with a rich set of software functions & examples to kickstart your development.

Features

Bluetooth 5.1 qualified (Bluetooth DID: D050903)

FCC/CE/RoHS certified

Integrated high-efficiency Antenna

支持s up to 3 BLE connections

16 MHz 32-bit Arm® Cortex® M0+

Memories: 1Mbit Flash, 48KB RAM, 144KB ROM, 32KB OTP

Rx current 2mA at 3V

Tx current 4mA at 3V at 0dBm

1.8uA at sleep with all RAM retained

Programmable Tx power from -19dBm to +2.2 dBm

-93 dBm receiver sensitivity

Quadrature decoder with 3 channels

4 channel 11-bit ENOB ADC

2 timers with PWM capabilities

Real-Time Clock

Built-in temperature sensor

Interfaces: 9 GPIOs, SPI, 2xUART, I2C

Operation: 1.8V - 3.3V, -40°C to +85°C

Dimensions: 12.5x14.5x2.1 mm

Compatible with Dialog DA14531MOD

雷竞技安卓下载

Beacons

Remote Controls

Proximity tags

Low Power Sensors

Commissioning/Provisioning

Toys

Serial port transmission

Smart home

Smart meters

Smart medical devices

Every quarter, we bundle up the best technical info on our products, software development topics, trainings, events and deliver it to your inbox.

Sign me up
Product Briefs and Summaries
Name Date Version
BDE-BLEM301 Product Brief(165.85 KB) 01/01/2021 1.1

Ordering information

Back to results

1 week ago

Setting the BD address

Posted byUnicycleBloke155 points 2 replies
0 upvotes

DA14531 with SDK 6.0.14

I'm confused about how the BD address is made unique for each device for production. The SDK has a static const data structure in which the address is set with a macro.

Can someone please explain how this works?

I have same question for the DISS, which contains a serial number that should vary between devices.

6 days ago

PM_Dialog

Hi UnicycleBloke,

You can set the USER_CFG_ADDRESS_MODE macro to APP_CFG_ADDR_STATIC in the user_config.h header file.

Then you should use either default_app_generate_unique_static_random_addr() or default_app_generate_static_random_addr() API in.app_on_generate_static_random_addr callback in user_callback_config.h file.

Please first check the comments above those APIs in app_default_handlers.h.

With regards to your question about the DIS, I assume that you mean the “DIS System ID”. You can set your preferable ID be configuring the APP_DIS_SYSTEM_ID in user_profiles_config.h

Thanks, PM_Dialog

6 days ago

UnicycleBloke 155 points

Thanks for the response on the BD address - that's very clear. I guess the device get a new random address after power on. I can see that it is stored in retained memory.

For the DIS I meant APP_DIS_SERIAL_NB_STR - I assumed that this is intended to be something that is unique to each device. This is not so important, but I wondered if a dynamic DISS is possible with the SDK.