Windows 10, Thingy 52 BLE

[jublin]

I'm attempting to write a plugin/dll to pull data from the Nordic Thingy52. I can scan all devices that are paired with windows 10, and load up the services, etc.

I can also read from descriptors that have explicit Read permissions. However, when I attempt to set a characteristic (such as motion data) to notify, or write to a service configuration characteristic, It instantly disconnects.

I loaded up the Thingy Firmware as a debug build from the github repo, and logged the data thingy_log.txt

It appears to reboot 20+ times. Int he Jlink RTT Viewer I would sometimes see drv_ext_gpio.c line 466 error (in Keil it's a blank line) (correction: line 446)

err_code = drv_sx1509_data_modify((1UL << pin_number), 0);
RETURN_IF_ERROR_EXT_GPIO_CLOSE(err_code);

Is there a sequence to connecting to the Thingy that's done in android/iOS apps that I'm missing here?

Edit: I am Currently connecting by getting the Config service, then getting motion, sound, and UI services (I don't need the rest) from the DeviceInfo on windows.

I am then attempting to write characteristic values for motion config, etc. But nothing stays connected. Do I need to be doing some sort of MTU request?

[ketil]

Hi jublin,

Just did a test on a Microsoft Surface 2 with Windows 10 version 1703 (Creators update). I used the Bluetooth LE Explorer app which was downloaded from the Windows Store.

With the app I was able to connect to Thingy:52 and read the GATT profile. In addition I was able to:

1. Read and write device name with the device name characteristic (EF680101-9B35-4933-9B10-52FFA9740042)
2. Start notifications for the temperature characteristic (EF680201-9B35-4933-9B10-52FFA9740042)
3. Read and write Eddystone URL with the Eddystone URL characteristic (EF680105-9B35-4933-9B10-52FFA9740042)
4. Start notifications for the Euler characteristic (EF680407-9B35-4933-9B10-52FFA9740042)

Could you try to recreate these steps? Also make sure your Windows 10 version is updated since Microsoft has made several recent improvements to their BLE drivers and APIs.

If you manage to get it working with the Bluetooth LE Explorer app you might want to take a look at the source code for tips on how to write your plugin/dll. I also recommend these videos introducing BLE for Windows developers.

Also, there is no need to do an MTU request unless you are using the speaker or microphone on Thingy:52. The reason for this is to get an adequate throughput.

Ketil

[jublin]

Well, I've also tried removing the motion characteristic config (and just using defaults) in my application. It still fails to even subscribe to notifications (device unreachable).

Is there a reason why a previously paired device (which was required before the spring update) would fail to connect?

The device name characteristic works on LE Explorer. The last letter (I renamed to "jubthingy") appears to be cut off on a scan ("jubthing" is shown in lists) for a few refreshes.

I'm beginning to wonder if it'd be faster to write an android app, but I feel like the problem lies somewhere in either the windows api's or in the firmware itself. This is the first time I've seen a device that's paired to the machine be unreachable, but work without being paired. They usually work both ways.