IQ 3.1.0 Beta 2 BLE - Can't connect

Any tips on getting the development board to connect with the simulator?

I've tried:

- NRF52 DK board with the CIQ firmware downloaded from here: https://developer.garmin.com/downloads/connect-iq/connectivity_2.0.1_115k2_with_s132_5.0.zip

- Installed drivers. - Tested that board can connect to the Thingy using the NRF connect BLE app. Used NRF Connect and flashed the CIQ firmware.

- Installed JDK8

- Set Up Eclipse CIQ Plugin

- Downloaded and set up the 3.1.0 Beta2 SDK

- Launched the NordicThingy52 app in the Simulator. Getting the Device 0/0 prompt.

- Clicked BLE Settings - entered COM3 (based on device manager info)

- Getting "BLE Initialization Failed. Check port name.". From here any attempts will not trigger the error message anymore but the simulator won't connect either.

Tried the above on Windows, OS X and Linux.

Can anyone that has it working export the device firmware out of NRF Connect? I'm ready to give up on this thing

mariusp over 6 years ago in reply to jim_m_58

Okay, made some progress with my app. I'm able to find my device, pair and successfully connect. On connection I set the notify parameter on the characteristic I want to read. I was able to get characteristic change events and read values a few times but it's very unstable.

I get a disconnect and reconnect every few seconds and most of the time the notifications are not raised. Signal strength is not great... about -60, -70 dBm so I'm not sure if that's that cause.

Maybe I'm doing something wrong... but looking at most of the other examples and reading the API docs it should be working.

Using nRF connect and setting the notify flag manually works just fine, the values are streaming in. Also using the Android app the device comes with works fine.. no connection drops and values are being read correctly.

Here's the output of my debugging messages.

Found wind meter.
Processing scan result. -53 RSSI
Pairing wind meter: WFANO-02 815
Connected to wind meter.
Start notify.
CCCD UUID: 00002902-0000-1000-8000-00805F9B34FB
Disconnected.
Connected to wind meter.
Start notify.
CCCD UUID: 00002902-0000-1000-8000-00805F9B34FB
Disconnected.
Connected to wind meter.
Start notify.
CCCD UUID: 00002902-0000-1000-8000-00805F9B34FB
Disconnected.
Connected to wind meter.
Start notify.
CCCD UUID: 00002902-0000-1000-8000-00805F9B34FB
Disconnected.
Connected to wind meter.
Start notify.
CCCD UUID: 00002902-0000-1000-8000-00805F9B34FB
Disconnected.
Connected to wind meter.
Start notify.
CCCD UUID: 00002902-0000-1000-8000-00805F9B34FB
Disconnected.
Connected to wind meter.
Start notify.
CCCD UUID: 00002902-0000-1000-8000-00805F9B34FB
Disconnected.
Connected to wind meter.
Start notify.
CCCD UUID: 00002902-0000-1000-8000-00805F9B34FB

jim_m_58 over 6 years ago in reply to mariusp

Can you try with the wind meter closer? Could there be some kind of conflict with say a phone app that's trying to talk to it? Maybe low battery?

Does it disconnect right after you try to turn on notify, or is it later? Do you stay connected if you don't turn on notify?

mariusp over 6 years ago in reply to jim_m_58

I'm actually having the meter right next to the board. It seems to disconnect every 6 seconds and it doesn't matter if I try to turn on notify or not.. Weird since it works fine with every other app that connects to the device. I checked and and the other apps are closed when I'm trying to do this.

Battery is 100%...according to the device.

Here's a printout with timestamps:

Found wind meter.
Processing scan result. -83 RSSI
Pairing wind meter: WFANO-02 815
9:56:38 Sat 4 May 2019 Connected to wind meter.
Obj: 154Disconnected.
9:56:45 Sat 4 May 2019 Connected to wind meter.
Found wind meter.
Processing scan result. -79 RSSI
Pairing wind meter: WFANO-02 815
10:0:32 Connected to wind meter.
10:0:38 Disconnected.
10:0:39 Connected to wind meter.
10:0:46 Disconnected.
10:0:47 Connected to wind meter.
10:0:53 Disconnected.
10:0:54 Connected to wind meter.
10:1:0 Disconnected.
10:1:1 Connected to wind meter.
10:1:7 Disconnected.
10:1:9 Connected to wind meter.
10:1:15 Disconnected.
10:1:16 Connected to wind meter.
10:1:22 Disconnected.
10:1:23 Connected to wind meter.
10:1:30 Disconnected.
10:1:30 Connected to wind meter.
10:1:37 Disconnected.
10:1:38 Connected to wind meter.
10:1:44 Disconnected.
10:1:46 Connected to wind meter.
10:1:52 Disconnected.
10:1:53 Connected to wind meter.
10:2:0 Disconnected.
10:2:1 Connected to wind meter.
10:2:8 Disconnected.
10:2:8 Connected to wind meter.
10:2:14 Disconnected.
10:2:16 Connected to wind meter.

jim_m_58 over 6 years ago in reply to mariusp

Is this the way the wind meter works? Connect and send data and then disconnect? Not doing notifies and streaming the data but expecting to get a connect every 10 seconds or more? And you're not doing the unpair in your code, correct? Maybe to save battery in the wind meter?

mariusp over 6 years ago in reply to jim_m_58

I'm not sure. I'm also debugging with NRF Connect and the Logger app and I don't see this happening in those cases. I'm able to stay connected, initiate notify and get notifications forever without being disconnected. I'm definitely not un-pairing in my code. I attached my code a few messages up in any case.

I also wrote the manufacturer maybe they can give me more information.

Thanks for trying to help!