ble_nus_data_send() can not send data to mobile app (nRF UART v2.0)

RE: ble_nus_data_send() can not send data to mobile app (nRF UART v2.0)

emotepp1 — Mon, 18 May 2020 03:25:40 GMT

Sr. No.	Short Name	Full Form
1	A2A full form	Ask to Answer
2	ACC full form	Actually
3	ACE full form	Excellent or Great
4	AFSfull form	Always Forever and Seriously
5	AKA full form	Also Known As
6	AMA full form	Ask Me Anything
7	ASAIC full form	As Soon As I Can
8	ASAP full form	As Soon As Possible
9	ASL full form	Tell me your Age, Sex, and Location
10	AUO full form	I don’t know
11	AW full form	Anyway
12	B4 full form	Before
13	BBL full form	Be Back Later
14	BBN full form	Be Back Never
15	BBS full form	Be Back Soon
16	BBZ full form	Babes
17	BF full form	Boy Friend
18	BFF full form	Best Friend Forever
19	BOT full form	Back On Topic
20	BRB full form	Be Right Back
21	BTW full form	By the Way
22	CYL full form	Catch You Later
23	DIY full form	Do it Yourself
24	DM full form	Direct Message
25	DP full form	Display Picture
26	ETA	Estimated Time of Arrival
27	FAQ	Frequently asked Questions
28	FYI	For Your Information
29	GE	Good Evening
30	GF	Girlfriend
31	GM	Good Morning
32	GN	Good Night
33	HHOJ	Ha Ha, Only Joking
34	HHOK	Ha Ha, Only Kidding
35	HHVF	Ha Ha, Very Funny
36	hmm	Thinking
37	IB	I’m Back
38	ICYMI	In Case You Missed It
39	IHS	I Hope So
40	IIL	I’m in Love

https://www.emotepp.com

RE: ble_nus_data_send() can not send data to mobile app (nRF UART v2.0)

Diana Chan — Tue, 17 Sep 2019 11:42:29 GMT

[quote userid="82470" url="~/f/nordic-q-a/51640/ble_nus_data_send-can-not-send-data-to-mobile-app-nrf-uart-v2-0/208339"]NRFX_ERROR_TIMEOUT[/quote]

It shows you are getting timeout in you code. In that line add the try catch block which will give your the details about the error. Then you can easily find the exact cause of this error.

RE: ble_nus_data_send() can not send data to mobile app (nRF UART v2.0)

Hung Bui — Fri, 06 Sep 2019 11:57:23 GMT

No, it's not NRFX_ERROR_TIMEOUT, it's NRF_ERROR_INVALID_PARAM. Please make sure you have an array of uint8_t as an input to the function.

You can have a look here on how to convert a string to an array: https://www.includehelp.com/c/convert-ascii-string-to-byte-array-in-c.aspx

RE: ble_nus_data_send() can not send data to mobile app (nRF UART v2.0)

Pepam — Thu, 05 Sep 2019 20:31:33 GMT

Hi Hung Bui,

I debugged my code with intenger to char type conversion by function snprintf and I got error code right under if() statement returned from APP_ERROR_CHECK(err_code) 0x00000007. I found on infocenter that might be NRFX_ERROR_TIMEOUT . Please, what should I do with it? I attached printscreen from debugging with the err_code.

Regards

RE: ble_nus_data_send() can not send data to mobile app (nRF UART v2.0)

Hung Bui — Wed, 04 Sep 2019 09:01:50 GMT

Hi Pepam,

The data sending over BLE is an array of byte. If you don't want to display in ASCII char, you can modify the source of nRFToolbox to display the raw data instead. The source code for nRFToolbox is provided on github.

RE: ble_nus_data_send() can not send data to mobile app (nRF UART v2.0)

Pepam — Tue, 03 Sep 2019 16:44:29 GMT

Hi Hung Bui,

Thank you for answer. I solved this problem by sending an intenger data type value

static void data_send()
{
    uint32_t   value;
    value = 12000; // test value
    uint16_t length = sizeof(int);
    (void)ble_nus_data_send(&m_nus, (uint8_t *) &value, &length, m_conn_handle);
    NRF_LOG_INFO("ADC measuremement %d", value)

}

static void repeated_timer_handler(void * p_context)
{
    data_send();
}

, insted of char and it works, but when i view log in nRF Toolbox, i can only see value: (hex number of my test value); please see what i have attached. Is there some way to convert this hex log value to decimal in nRF Toolbox?

thank you

RE: ble_nus_data_send() can not send data to mobile app (nRF UART v2.0)

Hung Bui — Mon, 02 Sep 2019 13:56:15 GMT

Hi Pepam,

nRFUART v2.0 is pretty old app and is deprecated. You should test using the UART profile inside nRFToolbox or using nRFConnect app instead.

What you described sound like the MCU was reset due to an assertion. You may want to step into the code an debug. You can follow the debug guide here. We need to know where the assertion occurs.