how to do simple data transfer using bluetooth serail terminal?
how to do simple data transfer using bluetooth serail terminal?
Hello,
You could use the BLE NUS peripheral and central examples to do such a transfer between your devices.
The examples will relay anything they receive over UART to their connected peer over BLE, and the peer will output the messages received over BLE out on its UART, and visa versa.
Test this according to the example documentation, and let me know if you encounter any issues or questions.
Best regards,
Karl
i go through the nsu code but which api was used to transfer the data?
will online power profiler requires power profiler kit ?
where actually transmission power set api called and how to change the transmission power?
how to measure power consumption in nrf52840 development kit using power profiler kit?
venkatesha kj said:will online power profiler requires power profiler kit ?
No, the online power profiler only makes estimates of power consumption for the specified scenario. Please keep in mind that these estimates assume no other operations are happening on your DK concurrently with the radio activity.
venkatesha kj said:where actually transmission power set api called and how to change the transmission power?
You may set the TX power through the sd_ble_gap_tx_power_set function. This should be called as part of the advertising / scanning initialization, before advertising / scanning has begun. Connections will inherit the power level configured during initialization of advertising / scanning.
venkatesha kj said:how to measure power consumption in nrf52840 development kit using power profiler kit?
If you wish to measure the current consumption of the nRF52840 DK you should follow the Current Measurement section of its Product Specification.
I see that you have made a separate ticket for this. Please do not post duplicates of your questions, and please create new tickets for issues that diverge from your existing ticket - such as power consumption, in this case.
venkatesha kj said:this was the function to assign the buttons to appropriate bsp events but in that function why default event passed ? which means all the buttons assinged to default events then how come button1 assigned to bsp_event_wakeup?
This is only for the general bsp.c case, the application actually uses the bsp_btn_ble case which is what the button overview you are referencing is referring to. Please take a look at the bsp_btn_ble.c 's bsp_btn_ble_init function.
Best regards,
Karl
static void advertising_init(void)
{
uint32_t err_code;
ble_advertising_init_t init;
memset(&init, 0, sizeof(init));
init.advdata.name_type = BLE_ADVDATA_FULL_NAME;
init.advdata.include_appearance = false;
// init.advdata.flags = BLE_GAP_ADV_FLAGS_LE_ONLY_LIMITED_DISC_MODE;
init.advdata.flags = BLE_GAP_ADV_FLAGS_LE_ONLY_GENERAL_DISC_MODE;
init.srdata.uuids_complete.uuid_cnt = sizeof(m_adv_uuids) / sizeof(m_adv_uuids[0]);
init.srdata.uuids_complete.p_uuids = m_adv_uuids;
init.config.ble_adv_fast_enabled = true;
init.config.ble_adv_fast_interval = APP_ADV_INTERVAL;
//init.config.ble_adv_fast_timeout = APP_ADV_DURATION;
init.config.ble_adv_fast_timeout = 0;
init.evt_handler = on_adv_evt;
err_code = ble_advertising_init(&m_advertising, &init);
APP_ERROR_CHECK(err_code);
ble_advertising_conn_cfg_tag_set(&m_advertising, APP_BLE_CONN_CFG_TAG);
}
in advertisement initialisation where actually tx power was set?
static void advertising_init(void)
{
uint32_t err_code;
ble_advertising_init_t init;
memset(&init, 0, sizeof(init));
init.advdata.name_type = BLE_ADVDATA_FULL_NAME;
init.advdata.include_appearance = false;
// init.advdata.flags = BLE_GAP_ADV_FLAGS_LE_ONLY_LIMITED_DISC_MODE;
init.advdata.flags = BLE_GAP_ADV_FLAGS_LE_ONLY_GENERAL_DISC_MODE;
init.srdata.uuids_complete.uuid_cnt = sizeof(m_adv_uuids) / sizeof(m_adv_uuids[0]);
init.srdata.uuids_complete.p_uuids = m_adv_uuids;
init.config.ble_adv_fast_enabled = true;
init.config.ble_adv_fast_interval = APP_ADV_INTERVAL;
//init.config.ble_adv_fast_timeout = APP_ADV_DURATION;
init.config.ble_adv_fast_timeout = 0;
init.evt_handler = on_adv_evt;
err_code = ble_advertising_init(&m_advertising, &init);
APP_ERROR_CHECK(err_code);
ble_advertising_conn_cfg_tag_set(&m_advertising, APP_BLE_CONN_CFG_TAG);
}
in advertisement initialisation where actually tx power was set?
If you do not specify it explicitly it will use the default value of +0 dBm.
You may re-configure this at the end of the advertising_init function.
Best regards,
Karl