This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Master Emulator example differences

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.

Parents
  • The code until the part to connect the device between the HealthThermoDemo and the Proximity app are very similar. Only difference I can see is that we call masterEmulator.Connect() in HealthThermo app with connection parameters when we don't do that with the same call in Proximity.

    This shouldn't cause a problem. But you can try to modify the Proximity app to make it more similar to the HealthThermo app and see at which point you can connect to the device.

    I would suggest you to create an simple app base on the examples just for testing.

Reply
  • The code until the part to connect the device between the HealthThermoDemo and the Proximity app are very similar. Only difference I can see is that we call masterEmulator.Connect() in HealthThermo app with connection parameters when we don't do that with the same call in Proximity.

    This shouldn't cause a problem. But you can try to modify the Proximity app to make it more similar to the HealthThermo app and see at which point you can connect to the device.

    I would suggest you to create an simple app base on the examples just for testing.

Children
No Data
Related