https://devzone.nordicsemi.com/f/nordic-q-a/231/i-m-having-trouble-advertising-a-vs-serviceI&#39;m leveraging off the heart rate sensor example to create my own VS service. I&#39;ve successfully registered a 128-bit UUID with the Soft Device which is enumerated along with 0x1800, 0x1801, the Battery Service and the Device Information Service when Ien-USTelligent Community 13Tue, 06 Aug 2013 04:41:58 GMThttps://devzone.nordicsemi.com/thread/1280?ContentTypeID=1Tue, 06 Aug 2013 04:41:58 GMT137ad170-7792-4731-bb38-c0d22fbe4515:e9aba0dc-84a5-4e78-9cf9-914fc81041deOle Morten<p>Great that you found the solution! Just for future reference, this question explains a little more on advertisement data sizes: <a target="_blank" href="https://devzone.nordicsemi.com/index.php/what-s-the-maximum-size-for-an-advertisement-package" rel="nofollow">https://devzone.nordicsemi.com/index.php/what-s-the-maximum-size-for-an-advertisement-package</a></p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/1281?ContentTypeID=1Mon, 05 Aug 2013 23:21:11 GMT137ad170-7792-4731-bb38-c0d22fbe4515:50941be7-60d8-452f-bd0e-335b7d048b59Dan Danknick<p>I hate to sound like a n00b but I just read the nRF51 SDK docs that said specifically that this error code is returned if your advertising string is too long. I dropped the other services and pared the name down. This works!</p> <p>Note to all future developers that if you use a vendor specific 128-bit UUID and you want to advertise it, drop every other enumerated service and pick a very short ASCII name. Like Zip.</p><div style="clear:both;"></div>