Master Emulator example differences

[Andrew]

I am looking at the Master Emulator examples ProximityDemo and HealthThermoDemo. I can use both to connect to one device that I have (Device A). I try to use ProximityDemo to connect to a different device (Device B) but it won't have anything of it. HealthThermoDemo can connect to Device B just fine. I am looking through the code for both and it looks like they do the same things. What is different between the two examples as for how they try to connect?

Note: When ProximityDemo fails, it gets to "masterEmulator.Connect" but then silently fails.

[Hung Bui]

Hi Andrew,

What is the difference between device A and device B? What firmware was on device B ? If you flash the proximity profile on the Device B are you able to connect using Proximity Demo ?

I suspect that the ProximityDemo simply disconnect if there is no proximity service on the peer device.

[Andrew]

ProximityDemo can connect to other devices just fine, independent of the GATT they have.

[Andrew]

Looking at the code for both of the examples, they both do a lot of the same things (connecting, bonding, ...) but they do them in slightly different orders. What are the advantages to each example's approach? Which example shows a more correct way to connect?

[Hung Bui]

I don't think order could cause a problem. I don't think there is a "more correct" way. It's pretty straight forward, you scan for device, you choose the device you want to connect, you connect. After you connect you do service discovery.

I would suggest you to create your own application based on one of the example and continue from there.

You can try to capture a sniffer trace, it will be more clear what happens.

Are you saying that with the proximity example, you can connect to many different devices, but there is only one device you can't connect ?

[Andrew]

Yes, there is one device that it cannot connect to. (This device can be connected to through the HealthThermoDemo, NRF Connect, and other BLE apps.)