Mobile Application

RE: Mobile Application

Bjørn Kvaale — Thu, 23 Nov 2017 13:18:14 GMT

@milav Have you checked to see what the differences between your app and the app used in the high throughput demo are? I would use the high throughput demo app as a starting point for your app, as that one definitely works.

RE: Mobile Application

milav — Tue, 21 Nov 2017 08:02:10 GMT

I changed MTU SIZE in nRF connect application from 23 to 30..

and in peripheral side it will change from 23 to 30.

but still we get error ..

request mtu not supported..MTU changed to 23 in mobile application.

And peripheral restart ....

where is the problem?

RE: Mobile Application

milav — Tue, 21 Nov 2017 07:04:59 GMT

here I have send the snap shots of both characteristic.

static uint32_t rx_char_add(ble_nus_t * p_nus, const ble_nus_init_t * p_nus_init)
{
    /**@snippet [Adding proprietary characteristic to S110 SoftDevice] */
    ble_gatts_char_md_t char_md;
    ble_gatts_attr_md_t cccd_md;
    ble_gatts_attr_t    attr_char_value;
    ble_uuid_t          ble_uuid;
    ble_gatts_attr_md_t attr_md;

    memset(&cccd_md, 0, sizeof(cccd_md));

    BLE_GAP_CONN_SEC_MODE_SET_OPEN(&cccd_md.read_perm);
    BLE_GAP_CONN_SEC_MODE_SET_OPEN(&cccd_md.write_perm);

    cccd_md.vloc = BLE_GATTS_VLOC_STACK;

    memset(&char_md, 0, sizeof(char_md));

    char_md.char_props.notify = 1;
    char_md.p_char_user_desc  = NULL;
    char_md.p_char_pf         = NULL;
    char_md.p_user_desc_md    = NULL;
    char_md.p_cccd_md         = &cccd_md;
    char_md.p_sccd_md         = NULL;

    ble_uuid.type = p_nus->uuid_type;
    ble_uuid.uuid = BLE_UUID_NUS_RX_CHARACTERISTIC;

    memset(&attr_md, 0, sizeof(attr_md));

    BLE_GAP_CONN_SEC_MODE_SET_OPEN(&attr_md.read_perm);
    BLE_GAP_CONN_SEC_MODE_SET_OPEN(&attr_md.write_perm);

    attr_md.vloc    = BLE_GATTS_VLOC_STACK;
    attr_md.rd_auth = 0;
    attr_md.wr_auth = 0;
    attr_md.vlen    = 1;

    memset(&attr_char_value, 0, sizeof(attr_char_value));

    attr_char_value.p_uuid    = &ble_uuid;
    attr_char_value.p_attr_md = &attr_md;
    attr_char_value.init_len  = sizeof(uint8_t);
    attr_char_value.init_offs = 0;
    attr_char_value.max_len   = BLE_NUS_MAX_RX_CHAR_LEN;

    return sd_ble_gatts_characteristic_add(p_nus->service_handle,
                                           &char_md,
                                           &attr_char_value,
                                           &p_nus->rx_handles);
    /**@snippet [Adding proprietary characteristic to S110 SoftDevice] */
}

static uint32_t tx_char_add(ble_nus_t * p_nus, const ble_nus_init_t * p_nus_init)
{
    ble_gatts_char_md_t char_md;
    ble_gatts_attr_t    attr_char_value;
    ble_uuid_t          ble_uuid;
    ble_gatts_attr_md_t attr_md;

    memset(&char_md, 0, sizeof(char_md));

    char_md.char_props.write         = 1;
    char_md.char_props.write_wo_resp = 1;
    char_md.p_char_user_desc         = NULL;
    char_md.p_char_pf                = NULL;
    char_md.p_user_desc_md           = NULL;
    char_md.p_cccd_md                = NULL;
    char_md.p_sccd_md                = NULL;

    ble_uuid.type = p_nus->uuid_type;
    ble_uuid.uuid = BLE_UUID_NUS_TX_CHARACTERISTIC;

    memset(&attr_md, 0, sizeof(attr_md));

    BLE_GAP_CONN_SEC_MODE_SET_OPEN(&attr_md.read_perm);
    BLE_GAP_CONN_SEC_MODE_SET_OPEN(&attr_md.write_perm);

    attr_md.vloc    = BLE_GATTS_VLOC_STACK;
    attr_md.rd_auth = 0;
    attr_md.wr_auth = 0;
    attr_md.vlen    = 1;

    memset(&attr_char_value, 0, sizeof(attr_char_value));

    attr_char_value.p_uuid    = &ble_uuid;
    attr_char_value.p_attr_md = &attr_md;
    attr_char_value.init_len  = 1;
    attr_char_value.init_offs = 0;
    attr_char_value.max_len   = BLE_NUS_MAX_TX_CHAR_LEN;

    return sd_ble_gatts_characteristic_add(p_nus->service_handle,
                                           &char_md,
                                           &attr_char_value,
                                           &p_nus->tx_handles);
}

the last sentence you said.... You may also request higher mtu from Android or nrf before transiting the image.

I did not get .... how the android request me ....??

RE: Mobile Application

Aleksander Nowakowski — Tue, 21 Nov 2017 06:43:53 GMT

Did you configure your characteristic for write without response? You may also request higher mtu from Android or nrf before transiting the image.

RE: Mobile Application

milav — Tue, 21 Nov 2017 06:29:12 GMT

Thank You Much...

Now i have to be transfer 2912 Bytes Image From Mobile application to nrf51822 Board (display on LCD).

The Mobile Application is same replica of nRF Toolbox UART app.

So the maximum Time the bytes to transfer is 0.046592 sec.

and if we add delay of application and software delay around 5 sec...

but it take 50 SEC between browse the image and display on LCD.

please suggest me a right way.

thank You.

RE: Mobile Application

Aleksander Nowakowski — Fri, 17 Nov 2017 13:01:42 GMT

Hi, you may find this interesting: github.com/.../nrf52-ble-image-transfer-demo This allows you to send images from the nRF52840 DK + camera to a phone, and also streaming.