The CYBT-213043-MESH is available from Mouser. You may also want to get the CY5670 Bluetooth CySmart dongle.

The module is called CYBT-213043-02 and it is available from Mouser. Cypress offers many different modules and a quick search on Mouser for “cypress Bluetooth module” will reveal them all.

 

Yes, the modules are certified in Canada and throughout the world. For more details and a list of certifications read this community article - https://community.cypress.com/docs/DOC-17352.

 

Yes, there is a coin cell socket underneath the kit. Alternatively, you can also power it with a USB cable.

 

There is a small header on the kit with a few GPIOs available. If you want a lot of IO, you can use a different kit (CYW920819EVB) that has Arduino headers on it with a bunch of GPIOs. It has the same silicon as the CYBT-213043-MESH kit used in the workshop.

 

 

Yes, over-the-air firmware update can be done to unprovisioned devices or provisioned devices that have a GATT proxy. However, the Bluetooth SIG is currently working on an update to the standard for OTA
updates over a mesh network so it is likely to change in the near future.

 

We want to show examples with lots of different settings so we have GATT proxy in some and not in others. There is no reason that you couldn't add a GATT proxy to it. One reason you might not want it though - if you have a switch that is battery powered instead of connected to the AC power source you might want to make it a low power node. In that use case you don't want it to be a proxy node.

 

Can we use the Cypress lighting models in our own application and do we need Bluetooth Sig approval for our mesh products?

Yes, the firmware is provided just so you can do that and all our Bluetooth modules are fully certified. See https://community.cypress.com/docs/DOC-17352 for details.

 


There is no debugger integrated on the evaluation boards. Is it possible to use a Segger J-Link to debug the code?

Yes, Segger J-Link is fully supported within ModusToolbox IDE. Go to Help > ModusToolbox General Documentation > ModusToolbox Documentation Index and look for Hardware Debugging for WICED Devices.

 

The client only runs on Windows 10 (Windows 7 does not support BLE). Source code is available if you wish to port to other operating systems. Look for windows.zip in the below link.

github.com/cypresssemiconductorco/Code-Examples-BT-SDK-for-ModusToolbox/tree/master/Mesh-Peer-Apps

 

Yes, the iOS app can be found in ios.zip in the below link.

github.com/cypresssemiconductorco/Code-Examples-BT-SDK-for-ModusToolbox/tree/master/Mesh-Peer-Apps.

 

We do not know why you would ever want to do this but, yes, both the desktop program and mobile app should work with any device that follows the Bluetooth Mesh spec.

 

There is a bug in the version of MeshClient in the SDK 1.2. The corrected version can be found on GitHub. There is a file called windows.zip in the Mesh-Peer-Apps folder.

github.com/cypresssemiconductorco/Code-Examples-BT-SDK-for-ModusToolbox.

 

Yes, but you must be running Windows 10 because Windows 7 does not support Bluetooth Low Energy.

 

 

That isn't really the expected model for friend/low power nodes, but if a low power node moves out of range of its friend it will eventually (after a defined number of failed attempts) realize that the friend is gone and will then look for a new friend. Obviously, any messages waiting in the previous friend node will be lost.

 

The maximum range is the same as the Bluetooth radio range, which is obviously dependent upon the antenna, environment, and so on.

 

Yes, nodes can be proxy and friend and relay at the same time.


How many low power nodes can a friend node support?

A low power node always has exactly 1 friend. A friend node can support multiple low power nodes. The maximum depends on how much RAM is available in the friend to store messages.

 

A configuration client is needed for removal, typically a provisioner, such as a mobile mesh app, does this job.

 

According to the SIG, devices should not send more than 100 network PDUs in any 10 second window,which corresponds to a median average of 10ms between messages.

 

The distance depends very much on the power of the radio and the physical arrangement of the nodes in the network. As a result, it is more useful to think about the maximum number of hops a message can make and that is defined by the SIG to be 127.

 

Security is mandatory in any Bluetooth mesh network. It is managed by a set of three keys.

 

Possession of the NetKey makes a node a member of a given mesh network. It allows a node to decrypt and authenticate messages at the network Layer. The mesh packet header and address are encrypted and authenticated with the network key, enabling relay nodes with the NetKey to forward messages that are not addressed to it without being able to access the data.

 

The mesh packet payload is encrypted and authenticated with the AppKey so that data for a specific application can only be decrypted by nodes that have the AppKey. AppKeys are used by the upper transport layer to decrypt and authenticate messages before passing them to the access layer. AppKeys enable multiple applications – such as room lighting and door locks in a hotel – to share a mesh network (and therefore gain all the benefits of having more nodes such as increased reliability and range) without each node having access to all messages.

 

Each device has its own unique device key known only to itself and the provisioner device. This key is used for secure communication during configuration.In addition to the keys, Cypress Bluetooth mesh has built in protection against trash can attacks (with automatic key refresh and black-listing of removed nodes) and replay attacks (using the sequence number and IV index).

 

Is it possible for a device to belong simultaneously to two different mesh networks?

Yes, there is a concept of sub-networks. Devices can belong to multiple sub-nets but only one main mesh network.