HI, i'm using a DA14531mod as a DSPS server device, flashed with precompiled binaries (obtained from SDK: DSPS_6.150.4.50).
the DA14531mod is connected to a MCU via a 4-wire UART.
The intended use for the DA14531 is to expose a generic RX/TX BLE Service that allows data to be received by the module which will forward it to the main MCU that will process it and send it back (the other way around). Basically, the DA14531 will act as a "BLE bridge".
By default, given the precompiled DSPS binaries, the advertising name of the module is "SPS_531".
Does the DSPS allow to change the advertising name RUNTIME? if yes, how can i achieve it?
I'd like to achieve the following: during production phase, the MCU is flashed with its own FW, and the DA14531 is flashed with the DSPS device binary. Our boards are then uniquely labeled and this label is saved (as a string) inside the MCU non-volatile memory. I'd like the main MCU, upon power up, to send this name to the DA14531 which set it as its advertising name.
do you have any suggestions?
Hi There,Thank you for posting you question online.
sbtyreal said:By default, given the precompiled DSPS binaries, the advertising name of the module is "SPS_531". Does the DSPS allow to change the advertising name RUNTIME? if yes, how can i achieve it?
The Device name can be set in the user_config.h file.
/* **************************************************************************************** * * Device name. * * - If there is space left in the advertising or scan response data the device name is * copied there. The device name can be anytime read by a connected peer, if the * application supports it. * - The Bluetooth device name can be up to 248 bytes. * **************************************************************************************** */ /// Device name. Either "SPS_531" or "SPS_585". #if defined (__DA14531__) #define USER_DEVICE_NAME "SPS_531" #else #define USER_DEVICE_NAME "SPS_585" #endif
Hi There,The easiest approach to change the device name at runtime would be to create a custom characteristic for this sole purpose. Please refer on this ticket here: DA14531 Name Change Service/Characteristic - Bluetooth Low Energy - Wireless Connectivity - Renesas Engineering CommunityI have created a custom characteristic on the ble_app_peripheral example and whatever value you give on that characteristic, it will be stored as the device name. Please refer on the example and the code to get a better understanding.Please also refer on our DA145XX Tutorial Create a Custom GATT Profile — DA145XX Tutorial Create a Custom GATT Profile (renesas.com) to understand how you can create a custom Service and characteristics.Best Regards,OV_Renesas