What is a typical size for adv_data?

[BenBurch]

I have modified the template app to advertise several custom UUIDs and one SIG UUID.  All UUIDs are being sent as a Scan Response.  I have selected expanded data size.  S140 is the Softdevice

When I reach the call to sb_ble_gap_adv_set_configure, I receive an error 7 NRF_ERROR_INVALID_PARAM.

When I inspect the second param is p_advertising->p_adv_data and when I dive into this, p_advertising->p_adv_data.adv_data.len is a HUGE number, 0x51F8, and I need to know if there is any way that is a correct length?  I suspect this might be my issue, but don't have a window into why the Softdevice rejected the parameter, or even if it IS this parameter that is being rejected.

Is there some magic to debugging the Softdevice calls I am missing, or are their actions completely obscured?

Thanks so much!

-Ben Burch

BTR Controls, Inc.

[BenBurch]

It occurs to me to say what I intend to be doing;  I have several custom service UUIDs.  These are of course too large for the adv packet.  I want to send the data using an expanded response packet during the scan response.  I am told that I have to not send the adv packet if I am going to use expanded data in the scan response, so I have moved all services to the scan response packet and am attempting to suppress the advertising data.

However, any strategy which will send out all of my service data without running out of space is equally acceptable.

Thanks!

[BenBurch]

So I did an experiment to see if I could keep everything in the adv data and select expanded size and see if it applied to that, but I get an NRF_ERROR_NO_MEM when I try to call sd_ble_uuid_vs_add on the first of them.  So not quite sure if this shows that approach will not work or if there is some other condition I am missing here.

[BenBurch]

Well, not sure what was wrong the first time I tired just using expanded data for the advert packer rather than the sr packet, but I made it work.

So, I still don't know how to suppress the advert packet if using expanded data in the sr packet, but I don't need to know that now.