How to use "ble_nus_string_send correctly" ?

RE: How to use "ble_nus_string_send correctly" ?

hmolesworth — Fri, 23 Feb 2018 15:15:58 GMT

Look more closely at the responses; you need this:

uint16_t length = sizeof(string);

RE: How to use "ble_nus_string_send correctly" ?

Kenneth — Fri, 23 Feb 2018 08:48:06 GMT

Did you notice &length?

RE: How to use "ble_nus_string_send correctly" ?

purgoufr — Fri, 23 Feb 2018 06:35:44 GMT

I got an error like this ;

..\..\..\main.c(853): error: #167: argument of type "uint16_t *" is incompatible with parameter of type "uint16_t"

I try to define uint16_t* length = sizeof(string);

But that did not work either.

RE: How to use "ble_nus_string_send correctly" ?

purgoufr — Fri, 23 Feb 2018 05:00:57 GMT

I got an error like this ;

..\..\..\main.c(853): error: #167: argument of type "uint16_t *" is incompatible with parameter of type "uint16_t"

I try to define uint16_t* length = sizeof(string);

But that did not work either.

RE: How to use "ble_nus_string_send correctly" ?

hmolesworth — Thu, 22 Feb 2018 21:47:28 GMT

In addition to the other points, (uint16_t *)17 doesn't do what you think. It actually indicates the contents of physical memory address 17. Not surprisingly the byte contents of physical address 17 is likely 5. So instead use a variable thus:

uint16_t someLength = 17;
blahBlah, &somelength, BlahBlah
or better
uint16_t someLength = sizeof(whatever);
blahBlah, &somelength, BlahBlah
or better for strings
nt16_t someLength = strlen("whatever dude");
blahBlah, &somelength, BlahBlah

RE: How to use "ble_nus_string_send correctly" ?

Kenneth — Thu, 22 Feb 2018 17:36:14 GMT

Try this:

APP_TIMER_DEF(send_some_uart_data);    /**< Some timer */

void send_some_uart_data_handler(void * p_context)
{
    ret_code_t err_code;
    
    uint8_t string[] = "serial updated\n\r";
    uint16_t length = sizeof(string);
    
    do
    {
        
        err_code = ble_nus_string_send(&m_nus, string, &length);
        if ( (err_code != NRF_ERROR_INVALID_STATE) && (err_code != NRF_ERROR_BUSY) )
        {
            APP_ERROR_CHECK(err_code);
        }
    } while (err_code == NRF_ERROR_BUSY);    
}

void send_some_data_uart_init(void)
{
    app_timer_create(&send_some_uart_data,APP_TIMER_MODE_REPEATED, send_some_uart_data_handler);
    app_timer_start(send_some_uart_data, APP_TIMER_TICKS(1000), NULL);
}

// Call send_some_data_uart_init(); in main() to run send_some_uart_data_handler() at configured internal.

RE: How to use "ble_nus_string_send correctly" ?

purgoufr — Thu, 22 Feb 2018 09:00:56 GMT

// <o> NRF_SDH_BLE_GAP_EVENT_LENGTH - The time set aside for this connection on every connection interval in 1.25 ms units. 
#ifndef NRF_SDH_BLE_GAP_EVENT_LENGTH
#define NRF_SDH_BLE_GAP_EVENT_LENGTH 3
#endif

Could it be an effect of this setting?

RE: How to use "ble_nus_string_send correctly" ?

purgoufr — Wed, 21 Feb 2018 10:14:43 GMT

Original code like this;

while(ble_nus_string_send(&m_nus, (uint8_t *)"serial no updated", (uint16_t *)17) != NRF_SUCCESS);

and I received "seria"

RE: How to use "ble_nus_string_send correctly" ?

Kenneth — Wed, 21 Feb 2018 08:29:08 GMT

Blank character should not be a problem, I am more concerned about the 2 non-defined characters that I can't see from the string.

RE: How to use "ble_nus_string_send correctly" ?

purgoufr — Wed, 21 Feb 2018 06:19:52 GMT

Normally I did not use "a" character just I write sample string. I've just realized, spacing between characters can be messing up. Can not perceive blank as character?

RE: How to use "ble_nus_string_send correctly" ?

Kenneth — Mon, 19 Feb 2018 13:25:11 GMT

Hi,

For debugging I suggest to make the length parameter be the size of the string, the length of the two strings above seems to be 15 and 17, not 17 and 19?

Can you use "abcde.." instead so we may see if it's the first or last bytes that is missing?

Have you checked the baudrate is correct and possible tried to disable hardware flow control?

I assume there is no assert occuring here on either sides of the link?

Finally, for testing you may also remove power_manage() to see if that make any difference.

Hopefully one of these changes will change behaviour and identify the cause.