advdata.p_manuf_specific_data and advdata.uuids_complete can not exists in same advertising packet?

RE: advdata.p_manuf_specific_data and advdata.uuids_complete can not exists in same advertising packet?

Martin — Fri, 28 Feb 2014 13:01:21 GMT

Hi, I have similar problem a few days ago in my Q: https://devzone.nordicsemi.com/index.php/how-to-add-more-services-with-128b-uuid-ble_advdata_set-returns-error-12-exceed-data-limit Take in mind that some demo apps use standardized BLE services that has only 16b short UUID so they can fit many in adv. packet but once you use custom 128b UUID it takes big part of adv. packet. But unless you use some very simplified client you don't need to add service UUIDs in adv. packet, they can be discovered by GAP after connection. In my project I use 14B device name and I can add up to 4B of manufacturer spec data (2B is company ID, 4B for data) and I can scan this data from client.

RE: advdata.p_manuf_specific_data and advdata.uuids_complete can not exists in same advertising packet?

Ken Matsui — Thu, 27 Feb 2014 14:18:36 GMT

My advertising packet was over 29bytes. Thank you for your advice.

https://devzone.nordicsemi.com/index.php/what-s-the-maximum-size-for-an-advertisement-package

RE: advdata.p_manuf_specific_data and advdata.uuids_complete can not exists in same advertising packet?

Ken Matsui — Thu, 27 Feb 2014 14:08:53 GMT

Thank you so much for quick reply. I see. It's likely that exceeding the maximum bytes... Will check into it.

Best regards,

RE: advdata.p_manuf_specific_data and advdata.uuids_complete can not exists in same advertising packet?

Håkon Alseth — Thu, 27 Feb 2014 14:02:04 GMT

Hi,

What is the error that you're seeing? Most likely, you are exceeding the number of bytes allowed in the advertising packet (max. 29 bytes of adv data).

Best regards Håkon