I don't think the 20 byte limit was due to a decision by Nordic. It is part of the BLE spec and be increased using the packet length extension which the nRF52 supports.
On 4 January 2017 at 17:30, Kevin Townsend <[email protected]> wrote: > This is something I've been curious about myself as well. Nimble is still > a work in progress, but I've wondered if there were any plans once the > final 1.0 release is done and initial development is considered closed. > > The SD from Nordic has some significant trade-offs in terms of losing real > time control of the system, and being limited by the design decisions made > by Nordic (20 bytes per packet), but it does make it much easier to sell > products since part of the certification process is handled by Nordic. > Particularly for low volume, low cost products the thousands of > dollars/Euros saved here can have a big impact on total per device cost, > and every bit matters in a startup. > > What would the financial burden be of getting a 1.0 Nimble through > certification along with some certified code for a handful of common > services/characteristics defined by the SIG? You will still always need to > register your product with the SIG (which costs money), as well as getting > FCC certification (which will also cost money), but if the stack itself is > certified that's one less step to take and one less cheque to write for > Mynewt users. > > K. > > > > On 04/01/17 18:22, Klaus Hagen wrote: > >> Hi, >> >> Is or will released Nimble stack versions be Bluetooth SIG qualified in >> the >> future? Or are companies integrating the Nimble stack supposed to get >> their >> own qualification done? >> >> Br, >> Klaus >> >> >
