ble_nus_data_send() usage

[Baruch]

This is from the documentation:

[in,out]

p_length

Pointer Length of the string. Amount of sent bytes.

I'd translate it to a pointer to the requested length of the string to send and holds the actual sent number, like write() for example.

Now let's see at the example of usage:

                err_code = ble_nus_data_send(&m_nus, data_array, &sent, m_conn_handle);
                if ( (err_code != NRF_ERROR_INVALID_STATE) 
									&& (err_code != NRF_ERROR_BUSY) 
								  && (err_code != NRF_ERROR_NOT_FOUND) )
                    {
                        APP_ERROR_CHECK(err_code);
                    }
                } while (err_code == NRF_ERROR_BUSY);

Apparently it doesn't matter.

Should my application take care of it or err_code will return some code that will let me know that something is not kosher?

Thanks.

[Martin Lesund]

Hi Baruch,

If I understand you correctly, you shouldn't worry.

The function will return something else than NRF_SUCCESS if something is wrong, and this is why we have this "APP_ERROR_CHECK" to see if the function was "successful".

and that Macro will call the error handler. 

 

 

[Baruch]

Hi Martin,

I'm not sure that you did understand my concern. I mentioned the write function example for a reason. My understanding is that ble_nus_data_send() writes into length the actual number of sent bytes and if it is less than requested I need to resend them again to have the continuity of my data. 

Thanks. 

[Martin Lesund]

Hi Baruch,

So for p_length:

in = Pointer Length of the string

out =Amount of sent bytes.

---

If you look in the ble_nus_data_send() function in "ble_nus.c" you will see it returns the sd_ble_gatts_hvx() function.

Please take a look at the return values and the documentation for that function. I think that would answer your question.

[Baruch]

The problem that the given example ignores the returned value.