Coexist S132 on mesh with S140

[melt]

Hi,

1. Can one run the coexist sample with softdevice S132 on a mesh where all the other nodes run S140?

2. does the coexist (UART) example need to be provisioned.

3. I need to implement UART on a server of the client light switch. Would it be easier to use the light_switch server example and impliment the UART code in there or rather use the BLE_UART example and build the mesh server code in there.

Thanks in advance

[Joakim Jakobsen]

Hello! 

1.
Yes, there is no problem using both S140 and S132 in the same network. They are compatible with eachother.

2.
Take a look at the documentation for the example to see how to setup and test the example;
SDK UART coexistence example - Documentation

3.
Please take a look at these previous question on the same topic.
https://devzone.nordicsemi.com/f/nordic-q-a/29108/how-to-add-mesh-into-nrf5-sdk-v14-1-v15-ble-application

However, the UART coexistence example might be a good place to start.

Best regards.
Joakim Jakobsen

[melt]

Thanks Joakim

I have looked at how to implement the co existence example , however the below is not clear to me,

"You can now run the two coexisting examples in parallel or in sequence:

• Run the light switch example as described in Light switch example.
• Run the ble_app_uart example as described in the nRF5 SDK documentation."

I have successfully ran and implemented the the BLE_APP_UART and the LIGHT_SWITCH example independently, so I know they work. 

on the co-existence example I run and provision the servers as normal. I then replace the client on my PCA10056 with the co-assistance example.  but 1) what does the documentation mean by "Parallel or in sequence" .

After provisioning the servers and loading the co-existence client I  have a UART terminal open in my PC and I presume I must send the codes 31,32,33,34 to the uart and it should turn on the lights  just like the original client firmware. Do I need to hard code the publication key and APPkey for the coexisting client to join the mesh or does it need to be provisioned.

Thanking you in advance

[Joakim Jakobsen]

Hi.

Sorry about the delay.

melt said:

Do I need to hard code the publication key and APPkey for the coexisting client to join the mesh or does it need to be provisioned.

 The coexist example should be provisioned, yes. You can use the nRF Mesh app for smartphone to provision and configure it.
You should configure the Generic OnOff Client to publish to the same address as your server is subscribing to. 

melt said:

have a UART terminal open in my PC and I presume I must send the codes 31,32,33,34 to the uart and it should turn on the lights  just like the original client firmware

 Yes, you can send this using a terminal SW on your computer. You can also send this over BLE to the uart example and that will simulate a button press.

Best regards,
Joakim

[melt]

I am loading this example on my PCA10056 DK.  The example staes PCA10040.

It compiles and loads successfully. The mesh app does not pick it up to be provisioned. Would that be due to my PCA10056 DK?

[Joakim Jakobsen]

That might be the reason. The SDK only have this example for the nRF52-DK (PCA10040), not the nRF52840-DK (PCA10056).

Do you have a nRF52-DK that you can use to test the example?

I'll run some tests on the nRF52840-DK and see if there is an easy way to port the project.

Best regards,
Joakim.

[melt]

The PCA10056 is the 52840 DK. Yes I do have one. Non of the co-existence examples come on on the mesh app (IOS). 

[Joakim Jakobsen]

melt said:

Yes I do have one. Non of the co-existence examples come on on the mesh app (IOS).

 They didn't appear in the Mesh App using the nRF52-DK (PCA10040) either?

[melt]

I dont have the PCA10040.  I will  have a look at the differences and see if I can port the code