This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Out of spec advertising (short name and long name at the same time)

Due to a particularly stupid thing I have done on another chip, I have ended up depending on the ability to advertise a short name and a long name. However, when I build an advertising buffer that has both on SDK 17 using the nRF52, the sd_ble_gap_adv_set_configure function indicates INVALID_DATA.  Now this is most likely the correct thing to do, but is there a workaround I can use?  Interoperability against my older devices depends on pulling off this stupid trick.

Parents
  • Hi Smackey, 
    I think the easiest way of solving this is to use one of the name on the advertising packet (adv_data) and the other name on the scan response packet (scan_rsp_data). I haven't tried so I'm not 100% sure it would be allowed but I believe so. 

    If it's not allowed then you would need to think about sending multiple advertising packets with different content. See here and here

  • Ah, that suggestion is great.  I ended up using the advert buffer with a short name and some data in the manufacturer specific part, and long name in the scan response.  It doesn't behave exactly like the original devices but its close enough that a minor change to our android app accommodates the difference.  The original devices also see enough data to be operational.  Not exactly perfect but good enough to continue with the prototype.  Thanks!

Reply
  • Ah, that suggestion is great.  I ended up using the advert buffer with a short name and some data in the manufacturer specific part, and long name in the scan response.  It doesn't behave exactly like the original devices but its close enough that a minor change to our android app accommodates the difference.  The original devices also see enough data to be operational.  Not exactly perfect but good enough to continue with the prototype.  Thanks!

Children
No Data
Related