Hi,
I'm using the DA14580 for my project.
I’m looking to read data off the hardware but I don’t know the device UUID to distinguish the device from other hardware in the vicinity.
I suppose there is one UUID for each BLE module to distinguish them but the only things i have found are the lines below contained in the sps_server.c file :
#define SPS_SERVER_TX_UUID {0xb8, 0x5c, 0x49, 0xd2, 0x04, 0xa3, 0x40, 0x71, 0xa0, 0xb5, 0x35, 0x85, 0x3e, 0xb0, 0x83, 0x07}
#定义SPS_SERVER_RX_UUID {0 xba, 0 x5c 0 x49 0 xd2, 0x04, 0xa3, 0x40, 0x71, 0xa0, 0xb5, 0x35, 0x85, 0x3e, 0xb0, 0x83, 0x07}
#define SPS_FLOW_CTRL_UUID {0xb9, 0x5c, 0x49, 0xd2, 0x04, 0xa3, 0x40, 0x71, 0xa0, 0xb5, 0x35, 0x85, 0x3e, 0xb0, 0x83, 0x07}
Thank in advance
Keywords:
Device:
Hi Avouaill,
The devices that your phone, for example, discovers are distinguished via the bluetooth address they have or via their name (if they have one to their advertising string). I can tell that you are using the DSPS from the UUID's that you mention (by the way those UUID are characteristic UUIDs and they are not visible unless you establish a connection with the device). So in DSPS on a generic phone scanner, if you run the fw as is, you should see the "DIALOG-SPS" which is the name of the device and the 80:EA:CA:00:00:00 which is the default bd address of the device.
Thanks MT_dialog
Hi,
Thank for the answer.
The hardware is transmitting data but I’ve no way of capturing that data as I don’t know what the characteristic’s UUID is.
Do I need now to create an Eddystone-UID packet (10-byte namespace, 6-byte instance) for my device then transmit the data using a BLE beacon advertisement packet. What do I have to do in the keil project to implement such a thing ?
Thanks in advance ,
Hi Avouaili,
I dont really get the question what the DSPS and the UUID of the characteristics have to do with the Eddystone UID ? If you would like to have a beacon and change the advertising string there are plenty of examples and documentation on how to achieve that, you can have a look at the ble_app_barebone example for start or check the beacon reference design. The advertising string of a device can be captured by a generic android/ios application but in order to see the characteristics of a service you will have to connect to the device.
Thanks MT_dialog
Hi,
I'm looking for a way to know the structure of the emitted packet (advertisement, data structure, ..). I'm using the code provided in the reference design section which woks with DSPS app. I'm using the keil5 project in sps_device.
Thanks
Hi Avouaill,
You mean the structure of the advertising channel packet of the BLE ? You will be able to find that in the BLE specification.
Thanks MT_dialog
Hi,
That's what I mean, i search in the DA14580 documents. there are a lot of document, could you tell me which one is the good one?
Thanks in advance
Hi Avouaill,
You wont be able to find that info in dialog's documents, you will have to check the specification of the BLE protocol.
Thanks MT_dialog
Hi,
Where could i find the specifications of the BLE Protocol ?
I searched for it in the Keil project provided in your website and I found a file called "app_adv_data.h".
I suppose that some values are concatenated to create the final sent string. How could i know the final structure ?
Thanks in advance for your help
Hi Avouaill,
A mentioned in the previous post you can find the structure of a BLE advertising string in the BLE specification, the header file that you mention just includes the options/definitions for all the available AD flags and UUIDs for every profile in the SDK. In order to check how the advertising structure is, you can download the BLE spec (download it from the SIG), and you will be able to find the advertising format (at least on core 4.0) in Volume 3 / Part C / Paragraph 11 ADVERTISING AND SCAN RESPONSE DATA FORMAT.
Thanks MT_dialog