https://devzone.nordicsemi.com/f/nordic-q-a/23744/devname-maximum-lengthHello, I am working on a project with STM32 master and nRF51822 slave connecting to Android/iOS mobile apps. I send the advertising parameters from STM32 to my nRF51822 (the name is one of the parameters and I am sure I get the whole name in myen-USTelligent Community 13Wed, 26 Jul 2017 14:54:34 GMThttps://devzone.nordicsemi.com/thread/93397?ContentTypeID=1Wed, 26 Jul 2017 14:54:34 GMT137ad170-7792-4731-bb38-c0d22fbe4515:844eca5b-e488-436d-bd16-99052d8abf6aBayram ZAYET<p>Hello,</p> <p>thank you for answering, I got my answer through what you mentioned and refering to the SIG.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/93396?ContentTypeID=1Mon, 24 Jul 2017 14:44:25 GMT137ad170-7792-4731-bb38-c0d22fbe4515:3bbfb234-bb8c-4f80-8e33-ce2dca21ec22endnode<p>Show us whole payload of <code>ADV_xxx</code> packet (and I guess you will find the answer when you will be pasting it here). Note that limit of 31 Bytes doesn&#39;t apply to effective payload (like device name string) but to overall data. At least 2 Bytes get lost on GAP AD header (Length and Tag bytes) and in your case there are probably other AD objects (e.g. like Flags AD which are mandatory by BT SIG GAP layer specification). So no, you won&#39;t be able to fit 31-byte device name string into BLE GAP formatted advertisement packet, at least not in BT SIG Core specification v4.0-4.2.</p><div style="clear:both;"></div>