Use Dongle as Client

RE: Use Dongle as Client

Simonr — Wed, 08 Feb 2023 08:03:10 GMT

We have a message sequence chart describing characteristic discovery on the GATT client here that should be helpful. You can see the characteristics_discover() function in our ble_db_discovery.c file for reference of how it's used in the discovery module.

Best regards,

Simon

RE: Use Dongle as Client

Simsim — Wed, 08 Feb 2023 07:24:27 GMT

Hi Simon

I had sucess.

I had to discover the Characteristic UUID as well right?-> Will be found and adressed automaticly by the discovery module

Do i have to add the second UUID to the scan response telegram as well? Not needed Service UUID is sufficent.

ble_nus_c.c

uint32_t ble_nus_c_init(ble_nus_c_t * p_ble_nus_c, ble_nus_c_init_t * p_ble_nus_c_init)
{
    uint32_t      err_code;
    ble_uuid_t    uart_uuid;
    ble_uuid_t    char_uuid;
    ble_uuid128_t nus_base_uuid = NUS_BASE_UUID;//UUID for Service
    ble_uuid128_t second_char_uuid = CHAR_UUID; // UUID for Character
   

    VERIFY_PARAM_NOT_NULL(p_ble_nus_c);
    VERIFY_PARAM_NOT_NULL(p_ble_nus_c_init);
    VERIFY_PARAM_NOT_NULL(p_ble_nus_c_init->p_gatt_queue);

    err_code = sd_ble_uuid_vs_add(&nus_base_uuid, &p_ble_nus_c->uuid_type);
    VERIFY_SUCCESS(err_code);



    uart_uuid.type = p_ble_nus_c->uuid_type;
    uart_uuid.uuid = BLE_UUID_NUS_SERVICE;

    p_ble_nus_c->conn_handle           = BLE_CONN_HANDLE_INVALID;
    p_ble_nus_c->evt_handler           = p_ble_nus_c_init->evt_handler;
    p_ble_nus_c->error_handler         = p_ble_nus_c_init->error_handler;
    p_ble_nus_c->handles.nus_tx_handle = BLE_GATT_HANDLE_INVALID;
    p_ble_nus_c->handles.nus_rx_handle = BLE_GATT_HANDLE_INVALID;
    p_ble_nus_c->p_gatt_queue          = p_ble_nus_c_init->p_gatt_queue;

    uint8_t type; 
    err_code = sd_ble_uuid_vs_add(&second_char_uuid, &type); // char UUID add
    VERIFY_SUCCESS(err_code);

    char_uuid.type = type;
    char_uuid.uuid = BLE_UUID_NUS_RX_CHARACTERISTIC;

   // ble_db_discovery_evt_register(&char_uuid); // Do not add for dicovery only Services

    return ble_db_discovery_evt_register(&uart_uuid);

Kind regards

Simon

RE: Use Dongle as Client

Simsim — Tue, 07 Feb 2023 07:32:21 GMT

Hi Simon

The CDC-ACM helped me not a lot, this side is Working as expected. I did some Testing with the Plain BLE-UART server and could make it running till the point where i change the UUID from the Characteristic. As log it is the same as the Base UUID it works.

Question:

I had to discover the Characteristic UUID as well right?

Do i have to add the second UUID to the scan response telegram as well?

Can you give me a hint where to add the second vs_uuid to discover, sd_ble_uuid_vs_add() is called aftre the base UUID, uuid_type is 0x03. Base UUID is 0x02

Regards

Simon

RE: Use Dongle as Client

Simsim — Thu, 02 Feb 2023 15:27:31 GMT

The firmware running on the Server Side is based on the nrf Mesh Dimming server(Softdevice 140), the Gatt Modells are modified to have the Custom UUID and Services. Softdevice 140

The service i try to discover is a plain GATT service, write, notify.

Snipping of the NRF Connect for Desktop

I will have a look on the CDC_ACM example.

Regards

Simon

RE: Use Dongle as Client

Simonr — Thu, 02 Feb 2023 12:17:40 GMT

What firmware is running on the server side (nRF52840 DK) here? There seem to be some mentions to Bluetooth Mesh here, which a "regular" BLE application (like the CDC_ACM example project) won't be able to communicate properly with without having some Mesh firmware as well. A phone usually has a stack for both BLE and Bluetooth Mesh by default which would explain why it's able to communicate with it as expected. Is the service you're trying to discover a Mesh service by any chance?

Best regards,

Simon

RE: Use Dongle as Client

Simsim — Wed, 01 Feb 2023 11:19:07 GMT

Hi Simon

Thanks for the answer, i logged both sides to see whats happening.

USB Dongle:

I added the Characteristc UUID as well on the discovery List, with no further success(as expected).

<info> app_timer: RTC: initialized.
<info> app: USBD BLE UART example started.
<debug> nrf_sdh_ble: RAM starts at 0x20002AE8
<debug> nrf_sdh_ble: RAM start location can be adjusted to 0x20002A48.
<debug> nrf_sdh_ble: RAM size for application can be adjusted to 0x3D5B8.
<info> app: Initializing Nordic UART Service Client.
<debug> ble_scan: Added filter on UUID 498B
<debug> ble_scan: Scanning
<debug> nrf_sdh_ble: BLE event: 0x1D.
<debug> nrf_sdh_ble: BLE event: 0x1D.
<debug> nrf_sdh_ble: BLE event: 0x1D.
<debug> nrf_sdh_ble: BLE event: 0x1D.
<debug> nrf_sdh_ble: BLE event: 0x1D.
<debug> nrf_sdh_ble: BLE event: 0x1D.
<debug> ble_scan: Connecting
<debug> ble_scan: Connection status: 0
<debug> nrf_sdh_ble: BLE event: 0x10.
<debug> nrf_ble_gatt: Requesting to update ATT MTU to 247 bytes on connection 0x0.
<debug> nrf_ble_gatt: Updating data length to 251 on connection 0x0.
<info> app: Connecting to target 6314D2F8FDCC
<debug> nrf_ble_gq: Registering connection handle: 0x0000
<debug> ble_db_disc: Starting discovery of service with UUID 0x498B on connection handle 0x0.
<debug> nrf_ble_gq: Adding item to the request queue
<debug> nrf_ble_gq: GATTC Primary Services Discovery Request
<debug> nrf_ble_gq: SD is currently busy. The GATT request procedure will be attempted                       again later.
<debug> nrf_ble_gq: Processing the request queue...
<debug> nrf_ble_gq: GATTC Primary Service Discovery Request
<debug> nrf_ble_gq: SD is currently busy. The GATT request procedure will be attempted                           again later.
<debug> nrf_sdh_ble: BLE event: 0x3A.
<debug> nrf_ble_gatt: ATT MTU updated to 69 bytes on connection 0x0 (response).
<info> app: ATT MTU exchange completed.
<info> app: Ble NUS max data length set to 0x42(66)
<debug> nrf_ble_gq: Processing the request queue...
<debug> nrf_ble_gq: GATTC Primary Service Discovery Request
<debug> nrf_ble_gq: SD GATT procedure (2) succeeded on connection handle: 0.
<debug> nrf_sdh_ble: BLE event: 0x24.
<debug> nrf_ble_gatt: Data length updated to 73 on connection 0x0.
<debug> nrf_ble_gatt: max_rx_octets: 73
<debug> nrf_ble_gatt: max_tx_octets: 73
<debug> nrf_ble_gatt: max_rx_time: 2120
<debug> nrf_ble_gatt: max_tx_time: 2120
<debug> nrf_sdh_ble: BLE event: 0x30.
<debug> ble_db_disc: Service UUID 0x498B not found.
<debug> ble_db_disc: Starting discovery of service with UUID 0xCFBB on connection handle 0x0.
<debug> nrf_ble_gq: Adding item to the request queue
<debug> nrf_ble_gq: GATTC Primary Services Discovery Request
<debug> nrf_ble_gq: SD GATT procedure (2) succeeded on connection handle: 0.
<debug> nrf_ble_gq: Processing the request queue...
<debug> nrf_sdh_ble: BLE event: 0x1F.
<debug> nrf_sdh_ble: BLE event: 0x30.
<debug> ble_db_disc: Service UUID 0xCFBB not found.
<debug> nrf_ble_gq: Processing the request queue...
<debug> nrf_sdh_ble: BLE event: 0x12.

Server:

<t:          0>, main.c,  691, ----- Control -----
<t:      11921>, main.c,  567, Initializing and adding models
<t:      11924>, main.c,  365, App Client Model handle: 2 
<t:      11928>, main.c,  371, App Level Model handle: 3
<t:      11931>, main.c,  377, App DTT Model handle: 4
<t:      11935>, main.c,  384, App Scene Model handle: 6, Element index: 0
<t:      11953>, main.c,  733, Loaded flash Parameters 
<t:      17182>, mesh_app_utils.c,   66, Device UUID (raw): 407843200FBC4045A314D2F8FD8CAD20
<t:      17185>, mesh_app_utils.c,   67, Device UUID : 40784320-0FBC-4045-A314-D2F8FD8CAD20
<t:      17204>, main.c,  771, 
		-------------------------------------------------------------
		 RTT 1) Set the Signal on T1 equal for Testig purpose        
		 RTT 2) Set the Signal on T2 equal for Testig purpose        
		 RTT 3) Send Mesh Telegram from this Node ID          
		 RTT 4) Clear all the states to reset the node.              
		-------------------------------------------------------------
<t:      17289>, app_level.c,  295, SET: Level: 0  delay: 0  tt: 0  req-delta: 0  trans-type: 0
<t:      17294>, main.c,  293, command: 0 
<t:      17296>, main.c,  338, Transition time: 0, Target level: 0, Transition type: 0
<t:     596545>, mesh_gatt.c,  834, GATT connencted UNprovisioned 
<t:     596550>, mesh_gatt.c,  616, New MTU: 66
<t:     608340>, ble_softdevice_support.c,  104, Successfully updated connection parameters

Server when Connected with Mobilephone and Serial APP Send "123456BEEF":

<t:          0>, main.c,  691, ----- Control -----
<t:      11165>, main.c,  567, Initializing and adding models
<t:      11168>, main.c,  365, App Client Model handle: 2 
<t:      11171>, main.c,  371, App Level Model handle: 3
<t:      11175>, main.c,  377, App DTT Model handle: 4
<t:      11179>, main.c,  384, App Scene Model handle: 6, Element index: 0
<t:      11197>, main.c,  733, Loaded flash Parameters 
<t:      16419>, mesh_app_utils.c,   66, Device UUID (raw): 407843200FBC4045A314D2F8FD8CAD20
<t:      16422>, mesh_app_utils.c,   67, Device UUID : 40784320-0FBC-4045-A314-D2F8FD8CAD20
<t:      16439>, main.c,  771, 
		-------------------------------------------------------------
		 RTT 1) Set the Signal on T1 equal for Testig purpose        
		 RTT 2) Set the Signal on T2 equal for Testig purpose        
		 RTT 3) Send Mesh Telegram from this Node ID          
		 RTT 4) Clear all the states to reset the node.              
		-------------------------------------------------------------
<t:      16826>, app_level.c,  295, SET: Level: 0  delay: 0  tt: 0  req-delta: 0  trans-type: 0
<t:      16831>, main.c,  293, command: 0 
<t:      16833>, main.c,  338, Transition time: 0, Target level: 0, Transition type: 0
<t:    3899567>, mesh_gatt.c,  834, GATT connencted UNprovisioned 
<t:    3924723>, ble_softdevice_support.c,  104, Successfully updated connection parameters
<t:    3990664>, ble_softdevice_support.c,  104, Successfully updated connection parameters
<t:    4029167>, mesh_gatt.c,  839, GATT disonnencted UNprovisioned 
<t:    4431815>, mesh_gatt.c,  834, GATT connencted UNprovisioned 
<t:    4459813>, ble_softdevice_support.c,  104, Successfully updated connection parameters
<t:    4526616>, ble_softdevice_support.c,  104, Successfully updated connection parameters
<t:    5083484>, mesh_gatt.c,  616, New MTU: 66
<t:    5107820>, mesh_gatt.c,  867, GATT write UNprovisioned 
<t:    5789036>, mesh_gatt.c,  867, GATT write UNprovisioned 
<t:    5789043>, mesh_gatt.c,  484, Received Data (raw): 123456BEEF
<t:    5789046>, mesh_gatt.c,  495, Reply Data    (raw): F4ED03200000D300

I used also the nRF Sniffer running wireshark but there is not realy something to see in both cases Mobile-Server or Dongle to server just advertising, last Message is Connect_IND in both cases. then silence till disconnect.

What happend after "connected" would be Interesting.

Kind regards

Simon

RE: Use Dongle as Client

Simonr — Tue, 31 Jan 2023 14:20:50 GMT

Can you also provide the log from the peripheral side so we can take a look there as well. Have you added the service in the peripheral project as well? It just seems like the application requests a discovery with "Starting discovery of service with UUID 0x498B" , and then don't find the service UUID. Another thing that might be helpful is if you could take a sniffer trace of the connection so we can see what exactly is happening on the air. You can use a dedicated Bluetooth sniffer, like the Ellisys devices, or a spare nRF52 DK/Dongle if you have one and the nRF Sniffer running on Wireshark.

Best regards,

Simon