Acknowledged
4 days ago
CIQQA-3377

impossible to keep ANT+ sensors paired to the simulator

I'm running Connect IQ Device Simulator 8.2.2 the most recent version on my Mac, and I have a Garmin ANT+ stick.

I'm able to pair ANT+ sensors; but I have no idea how to keep them paired.

Currently the flow goes like this:

- Start datafield simulator

- Open Settings -> Manage Sensors menu

- Search and pair ANT+ sensors (this process kills the running app, but does allow me to pair the sensors).

- But now we have to somehow restart our app because the app is not running; so I kill the simulator and restart it

- Now my app is running but my ANT+ sensors are all in the "Disconnected" state. There is no obvious way to get them to search mode or reconnect without going through the same flow as before which will kill my app; clicking Unpair or RemoveAll will kill the app. Then I can repair the sensors but I will have to reboot the simulator to get my app running again and then it will not be disconnected.

Sometimes, with shear luck, when I restart the simulator my app will be successfully paired with the ANT+ sensor(s). No idea why this sometimes works, it's about 1 in 20. Makes it very cumbersome to test and develop locally. Am i doing something wrong? What is the recommended approach to get your app restarted after the pairing menu kills the app?

renschler
Parents
  • 3 days ago in reply to FlowState

    > Funnily enough, I've found that when the app gets stuck like this, the *2nd-last* attempt at running the app usually works - the final attempt is seemingly what causes the 2nd-last attempt to finally go through, as at this point, VS Code will tell me that the app is already running and it asks me if I want to start another instance. Or maybe I'm just not waiting long enough, idk.

    yes I reproduced this exact behavior; I think it's a bug

Comment
  • 3 days ago in reply to FlowState

    > Funnily enough, I've found that when the app gets stuck like this, the *2nd-last* attempt at running the app usually works - the final attempt is seemingly what causes the 2nd-last attempt to finally go through, as at this point, VS Code will tell me that the app is already running and it asks me if I want to start another instance. Or maybe I'm just not waiting long enough, idk.

    yes I reproduced this exact behavior; I think it's a bug

Children
No Data