bluetooth 5 vs 4.2

RE: bluetooth 5 vs 4.2

MartinBL — Thu, 22 Mar 2018 09:15:09 GMT

I think my comment above may have been confusing, and for that I'm sorry. One very important thing to understand when talking about Bluetooth 5 though, is that the Bluetooth SIG has decided that vendors are not required to support any(!) Bluetooth 5 features to be allowed to brand their products as "Bluetooth 5 ready" (emphasis on the ready). Please have a look at this blog post and take special not of the "What’s not being talked about" paragraphs: Bluetooth 5: What to expect.

RE: bluetooth 5 vs 4.2

mikkel1e — Wed, 21 Mar 2018 17:34:08 GMT

Yes, in frustration that we could not really understand what version of Bluetooth was used, I think we were confused with what you wrote and what the other one has written, we can see how it is connected, I believe just that when nrf52840 use bt 5 we'd also think that when we use mesh it also use bt 5, but with your help and read more on the web, we understand it much better and I apologize for not believing at you a the first , but many thanks for the help

RE: bluetooth 5 vs 4.2

leonwj — Wed, 21 Mar 2018 16:04:56 GMT

hello mikkel1e,

I can only suggest that you re-read the article in the link that you posted (fairly slowly)... although it attempts to conflate the Bluetooth mesh and Bluetooth 5 standards, in no way does it state that Bluetooth 5 specific features are used in the Bluetooth Mesh. In fact, it's really about Bluetooth 5 with references to mesh thrown in (I would imagine to increase its hit count). Hopefully wishing for certain features to be implemented doesn't always help and at worst case you have the full specification to fall back on should you be in any doubt in the future. Additionally, most of the current vendor mesh stacks out there (Nordic, SiLabs, Zephyr to name a few) are published with the full source code available, so reviewing the code is also an option.

Nonetheless in this case, I believe that you have been corrected in your misconception regarding the mesh standard using Bluetooth 5 specific features by more than one person in this forum.

Take Care and good luck with your assignment.

Regards,

RE: bluetooth 5 vs 4.2

mikkel1e — Wed, 21 Mar 2018 10:17:29 GMT

Yes, because we wanted to make sure we did not write something wrong in our assignment, we also asked him to be sure

https://www.mouser.dk/applications/bluetooth-5-mesh-networking-standard/

RE: bluetooth 5 vs 4.2

rperkins — Tue, 20 Mar 2018 19:12:55 GMT

Thanks @leonwj for your detailed explanation...

btw - I wouldn't hold your breath waiting for @mikkel1e to post those links to the 'articles' that they supposedly read. It seems they continually ask the same question on different threads hoping to get the answer they want to hear.

RE: bluetooth 5 vs 4.2

leonwj — Mon, 19 Mar 2018 21:03:20 GMT

hello mikkelle,

Do you mind posting the links to the articles that you have read that explicitly state that Bluetooth 5 specific features are used in the SIG Mesh standard.

Thanks in advance.

Regards,

RE: bluetooth 5 vs 4.2

mikkel1e — Mon, 19 Mar 2018 20:28:51 GMT

cause i want to be sure what you are writing really is because i have read some articles around that nrft52840 uses bt 5 in mesh

Byt thanks for The help

RE: bluetooth 5 vs 4.2

leonwj — Mon, 19 Mar 2018 19:35:40 GMT

hello mikkelle,

At this point, I'm not sure that I can help you any further other than to suggest that you re-read (fairly slowly) all the previous responses that you have received in this thread. After absorbing the above, if you are still extremely keen on using any Bluetooth 5 related feature(s), then I can only direct you to Nordic's proprietary Instaburst feature, but at that point you will no longer be developing a compliant or interoperable Bluetooth SIG mesh solution.

Regards,

RE: bluetooth 5 vs 4.2

mikkel1e — Sat, 17 Mar 2018 01:55:54 GMT

Thanks, but okay do you have any documentation about it, because i have to use it in my project. But i dont understand why they make a new bluetooth 5 if you cant use it in any og the new features in mesh

RE: bluetooth 5 vs 4.2

leonwj — Sat, 17 Mar 2018 00:12:45 GMT

hello mikkelle,

No, the nrf52840 will NOT use any Bluetooth 5 features when operating on a Bluetooth SIG compliant mesh network.

Regards,

RE: bluetooth 5 vs 4.2

mikkel1e — Fri, 16 Mar 2018 22:00:32 GMT

Thanks, but just to be sure, e.g. Nrf52840 there use bluetooth 5, Will it also use bluetooth 5 features doing mesh, it is just too be sure

RE: bluetooth 5 vs 4.2

leonwj — Fri, 16 Mar 2018 21:40:32 GMT

hello mikkelle,

The Nordic Mesh SDK v1.0.1 is compliant with the Bluetooth Mesh Specification v1.0 and as such it supports the features inherent in BLE v4.2...

The backstory is that when the Bluetooth SIG Mesh Working Group set out to implement the mesh standard they had a number of key design choices to make. One of those was which BLE version to base the mesh standard on. So the choice was:

(1) Base it on Bluetooth LE v5.0 (and in doing so take advantage of increased range, increased speed, encoded PHY, utilize data channels for advertising etc.) BUT exclude the millions of Bluetooth v4.x radios currently in the marketplace (in phones etc.)

(2) Base it on Bluetooth LE v.4.x, thereby allowing all the (millions of) current Bluetooth v4.x radios in use to be able to take part in Bluetooth mesh networks. This option would also allow Bluetooth v5.0 radios to take part in mesh networks since Bluetooth LE v5.0 is backwards compatible with v4.2 (as indicated by MartinBL and David Erwin above)

The Mesh Working Group chose to go with option (2), therefore any compliant (and fully interoperable) mesh stack from any vendor (whether it runs on a Bluetooth v5.0 (e.g. nrf52840) or Bluetooth v4.2 radio) will only utilize the inherent features of Bluetooth v4.2.

I hope that clarifies things for you.

Regards,

RE: bluetooth 5 vs 4.2

mikkel1e — Fri, 16 Mar 2018 14:33:30 GMT

just one more thing, it's board nrf52840 if you burge sdk mesh version 1.0.1 then run it on bluetooth 5 or 4.2 because i'm not sure

RE: bluetooth 5 vs 4.2

David Edwin — Mon, 19 Feb 2018 10:30:44 GMT

Just to make this very clear, BTLE Mesh does NOT require BT 5 , though it can run on BT 5. It should be able to run on BT 4.0 and greater with the CSA 6.

RE: bluetooth 5 vs 4.2

MartinBL — Mon, 19 Feb 2018 10:02:31 GMT

Hi,

Please refer to Mesh Profile Specification 1.0 Ch 1.2:

1.2 Bluetooth specification release compatibility
This specification shall be used with:

Core Specification Addendum 6 [3] combined with an allowed Bluetooth Core Specification (see [3]
Volume 1, Part D, Section 1.2, Table 1.3), OR
Any version of the Bluetooth Core Specification later than v5.0.

RE: bluetooth 5 vs 4.2

mikkel1e — Sat, 17 Feb 2018 11:32:15 GMT

thanks, i know you done a lot but do you have a place it says that bluetooth mesh makes use of bluetooth 5 so we can prove it in the report we are going to write.

RE: bluetooth 5 vs 4.2

MartinBL — Fri, 16 Feb 2018 17:49:10 GMT

As mentioned, BLE 5 is backwards compatible. So let us say that

BLE 4.2 supports feature A and B
BLE 5.0 supports feature A, B, C, and D.

A BLE 5.0 device can communicate just fine with a 4.2 device using feature A and B, but a 4.2 device cannot use feature C and D. Examples of features a 4.2 doesn't support is Long range (also known as coded phy) and 2Mbps mode.

RE: bluetooth 5 vs 4.2

mikkel1e — Fri, 16 Feb 2018 17:35:43 GMT

Why use 5 if 4.2 supports the same, does 5 not have some better features like range but thanks

RE: bluetooth 5 vs 4.2

MartinBL — Fri, 16 Feb 2018 16:21:04 GMT

Hi,

The short answer is that you can use any device compatible with BLE version 4.2 or above.

The longer answer is that BLE 5 devices are backwards compatible and support all the features you will find in BLE 4.2. When a BLE 5 device tries to connect with a 4.2 device they exchange information about what features each device supports and then decide upon the "least common denominator". If you want to use a Nordic device I suggest that you chose a device from the nRF52 family. You can find more information about Nordic's mesh solution here: nRF5 SDK for Mesh.