how to built a 128 UUID bit

[DavidC]

Hallo comunnity

I have a sensor which is working is sending data via BLE and it has a 128 UUID bit service [0x 000000-000000-1000-8000-0080-5F9B34FB]

In order to do the discovery i should add it using sd_ble_uuid_vs_add () But I´ve problem there, in my code, the ble_uuid_t is not accepting me the .uuid, it gives me the follwing error: aggregate value used where an integer was expected.

static ble_uuid128_t  quatServ128uuidd= {{0xFB, 0x34, 0x9B, 0x5F, 0x80, 0x00,
                0x00, 0x80, 0x00, 0x10, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00}};

static ble_uuid_t const QUAT_UUID_SERVICE =
{
	.uuid = (uint16_t) quatServ128uuidd,
	.type = BLE_UUID_TYPE_VENDOR_BEGIN
};
err_code = sd_ble_gattc_primary_services_discover(m_conn_handle, start_handle, &QUAT_UUID_SERVICE);

But In the ble_uuid_t I've problems to set it up.

Other questions it is about the ble_gattc_write_params_t, I have problem in the handle and p_value. When I compile ,it says: initializer element is not constant.

static uint16_t  handle	 	= 0x0022;		/**<Quaternios handle>*/
static uint8_t* const p_value			= {0x01, 0x01};	/**<Activiation for the 
notifications>*/
 /**<Parameters for notifications>*/
static  ble_gattc_write_params_t const write_params =
{
	.write_op 	= BLE_GATT_OP_WRITE_CMD,
	.flags		= BLE_GATT_EXEC_WRITE_FLAG_PREPARED_WRITE,
	.handle		= handle,
	.offset		= 0,
	.len		= sizeof(p_value),
	.p_value	= p_value
}

Regards,

David Caraveo

[bjorn-spockeli]

No, ble_app_uart found in examples/peripheral/ble_app_uart.

[endnode]

Well the examples/ble_central/ble_app_uart_c is counterpart of examples/ble_peripheral/ble_app_uart, isn't it?

[DavidC]

I'm doing an app for central and I need to discover a service which has a 128 uuid, Do I need to add it?

[bjorn-spockeli]

Oh, my bad. Yes, then you need to take a look at the ble_app_uart_c example, specifically the ble_nus_c_init function, where you add the vendor specific UUID.

[endnode]

Add 128-bit base UUID to SoftDevice ATT/GATT table? Yes and no. If you don't care to receive 2-byte UUID + BLE_UUID_TYPE_UNKNOWN type for 128-bit base then you can go with it. Otherwise you need to provision all 128-bit bases to the stack because that's how Soft Device work on GATT layer, whatever Client or Server role.