i don't understand the programming examples as light switchs
i don't understand the programming examples as light switchs
Hi davidesteban13. I would take a look at this link on the Nordic Infocenter. Take a look at these two links to get a good introduction to Mesh: link1 & link2. If I were you, I would start with the light switch example, as it is a good introduction to the capabilities of mesh. As the Infocenter document explains, you will need at least two devices, a server & a client. The client is the provisioner, which means that it provides other new device(s) with information needed to join the mesh network. The server is the provisionee in this case (i.e. the new device being added to the mesh network). The client is essentially the light switch & the server is the light that is being toggled on and off. In the Nordic Mesh SDK Light Switch example, you can have multiple servers. So one client can act as a switch for multiple servers (in this case LEDs). The light switch example uses the SimpleOnOff model to let every node in the mesh network know about server statuses. Every time a server changes state, the client & all of the other server nodes will be informed of the change in state. Hope that helps a bit.
Hi davidesteban13. I would take a look at this link on the Nordic Infocenter. Take a look at these two links to get a good introduction to Mesh: link1 & link2. If I were you, I would start with the light switch example, as it is a good introduction to the capabilities of mesh. As the Infocenter document explains, you will need at least two devices, a server & a client. The client is the provisioner, which means that it provides other new device(s) with information needed to join the mesh network. The server is the provisionee in this case (i.e. the new device being added to the mesh network). The client is essentially the light switch & the server is the light that is being toggled on and off. In the Nordic Mesh SDK Light Switch example, you can have multiple servers. So one client can act as a switch for multiple servers (in this case LEDs). The light switch example uses the SimpleOnOff model to let every node in the mesh network know about server statuses. Every time a server changes state, the client & all of the other server nodes will be informed of the change in state. Hope that helps a bit.
Wouldn't it help to add 2 relay nodes also? They don't need to be DKs, just the cheap nRF52 breakout boards should do, for the purpose of testing a mini mesh :)
Sure, I agree with you Matt. Doesn't really make sense to have a mesh network with 2 nodes. I find it ideal to have 4 boards to be able to use all four LEDs on the DK. But I understand that not everyone has four nrf52 DKs available. I have not tried it with cheap nrf52 breakout boards, but I guess that could work. Saw that you managed to get this working with open mesh. Have you tried the same with the nrf52 mesh Matt?
Shamefully not yet. I saw the mesh sdk pre-release back in last August, and was going to migrate my mesh work and then my project got "shelved" (yeah, *** happened!) and I left the company by November, and now I'm working on Bluetooth classic profiles (A2DP, HSP, HFP) so it may be another 2 months before I can delve back into the mesh work :(
That's too bad. Hope you get to try it soon.