On the issue of updating some Characteristics value parts

RE: On the issue of updating some Characteristics value parts

ovrebekk — Thu, 10 Aug 2023 08:29:58 GMT

Please do.

Essentially you have to select your device in the Wireshark interface, connect to it from the phone, and then do the data exchange that will show the problem. Once the sniffer trace is complete you can stop the trace and save it to a file, which you can upload to this ticket.

Best regards
Torbjørn

RE: On the issue of updating some Characteristics value parts

Mikey — Wed, 09 Aug 2023 14:55:25 GMT

I will try using dongle to catch errors.

RE: On the issue of updating some Characteristics value parts

ovrebekk — Wed, 09 Aug 2023 14:14:27 GMT

Would you be able to capture a Bluetooth sniffer trace of the exchange, when you send updates from the phone which are incorrectly processed on the nRF side?

If you don't have access to a professional Bluetooth sniffer it is possible to use a Nordic DK or dongle as a sniffer through the nRF Sniffer project.

Best regards
Torbjørn

RE: On the issue of updating some Characteristics value parts

Mikey — Wed, 09 Aug 2023 04:10:45 GMT

Hi，

Thank you for your reply.

static void writeAttrCallback(Profile_t *pProfile, ble_evt_t const *pBleEvent)
{
    ble_gatts_evt_write_t const *pEventWrite = &pBleEvent->evt.gatts_evt.params.write;
    uint8_t characteristicId;

    if ((pEventWrite->handle == pProfile->uprequestHandle.cccd_handle) && (pProfile->ProfileCharWriteHandler != NULL))
    {
        characteristicId = PROFILE_CHAR_1;
        pProfile->ProfileCharWriteHandler(pBleEvent->evt.gap_evt.conn_handle, characteristicId,
                                                pProfile, pEventWrite->data, pEventWrite->len);
    }
    else if ((pEventWrite->handle == pProfile->pressureHandle.value_handle) && (pProfile->ProfileCharWriteHandler != NULL))
    {
        characteristicId = PROFILE_CHAR_2;
        pProfile->ProfileCharWriteHandler(pBleEvent->evt.gap_evt.conn_handle, characteristicId,
                                                pProfile, pEventWrite->data, pEventWrite->len);
    }
    else if ((pEventWrite->handle == pProfile->temperatureHandle.value_handle) && (pProfile->ProfileCharWriteHandler != NULL))
    {
        characteristicId = PROFILE_CHAR_3;
        pProfile->ProfileCharWriteHandler(pBleEvent->evt.gap_evt.conn_handle, characteristicId,
                                                pProfile, pEventWrite->data, pEventWrite->len);
    }
}

void Characteristichandle(ble_evt_t const *pBleEvent, void *pContext)
{
    LwsProfile_t *pProfile = (LwsProfile_t *)pContext;

    switch (pBleEvent->header.evt_id)
    {
    case BLE_GATTS_EVT_WRITE:
        writeAttrCallback(pProfile, pBleEvent);
        break;

    case BLE_GAP_EVT_CONNECTED:
        lws_on_connect(pProfile, pBleEvent);
        break;

    case BLE_GAP_EVT_DISCONNECTED:
        lws_on_disconnect(pProfile, pBleEvent);
        break;
	
	case BLE_GATTS_EVT_HVN_TX_COMPLETE:
		//DPrintf("BLE_GATTS_EVT_HVN_TX_COMPLETE\r\n");
		break;

    default:
        // No implementation needed.
        break;
    }
}

Encapsulate our data receiving handle function in the Nordic routine, as shown in the above code.

And PROFILE_ CHAR_ 1 and PROFILE_ CHAR_ 3 has data, while PROFILE_ CHAR_ 2 has no data, but it will enter the corresponding processing ID.
It's not always like this, PROFILE_ CHAR_ 2. Occasionally, there is no data available, but the corresponding data can be seen on both nrf connect reads and writes, and the corresponding ID cannot obtain its data.

RE: On the issue of updating some Characteristics value parts

ovrebekk — Tue, 08 Aug 2023 10:34:05 GMT

You mean to say the callback is triggered as expected on a write but the data is not available?

I don't think the Characteristichandle() function is one of the standard functions from our examples?

I assume it is triggered by the BLE_GATTS_EVT_WRITE event from the SoftDevice?
Have you checked the exact contents of the event to see what it includes?

When the BLE_GATTS_EVT_WRITE event occurs you will typically get the event data like this:

ble_gatts_evt_write_t const * p_evt_write = &p_ble_evt->evt.gatts_evt.params.write;

Then you can check the various fields in the p_evt_write struct to process the data.

Best regards
Torbjørn