Unable to connect to Windows BLE peripheral from Argon central

Firmware
,
1

Hi there,

I'm using an Argon as a BLE central in order to connect to a Windows laptop acting as a BLE peripheral. However, I've run into a bit of a predicament as it seems that the two parties do not want to talk to each other. The Argon is able to quickly connect to other devices (e.g. another Argon) that match the scan criteria I set (in this case a single service UUID for BLE UART), and I am able to connect and view the UART data being streamed from the Windows peripheral service using my phone and the Bluefruit app.

Here's a minimal example that I am using to test on my Argon:

SYSTEM_MODE(MANUAL);
SYSTEM_THREAD(ENABLED);

void setup() {
	BLE.on();
	Serial.begin(9600);
}

void loop() {
	if (BLE.connected()) {

	}
	else {
		BleScanFilter filter;
		filter.serviceUUID("6E400001-B5A3-F393-E0A9-E50E24DCCA9E");
		Vector<BleScanResult> scanResults = BLE.scanWithFilter(filter);

		for(int i = 0; i < scanResults.size(); i++) {
			Serial.printlnf("Found device: %s", scanResults.at(i).address().toString().c_str());
			Serial.printlnf("Name: %s", scanResults.at(i).scanResponse().deviceName().c_str());
			BLE.connect(scanResults.at(i).address());

			if(BLE.connected()) {
				Serial.println("Connected!");
				break;
			}
			else {
				Serial.println("Failed to connect!");
			}
		}
	}
}

What this logs is the following, indicating the Argon can see the device (with correct address and device name), but for some reason cannot connect.

Found device: 4A:B1:AC:AF:D4:3F
Name: R5313877
Failed to connect!

However, the Argon sometimes will connect - but this can either happen first try or after 20 minutes, so I'm a bit stumped as to what is going on. Is there some Windows privacy or security feature that the Argon isn't compatible with? I know it isn't a standard use case for Windows to act as a peripheral but my phone connects just fine so I'm thinking it's some configuration or limitation on the Argon side.

2

This topic was automatically closed 182 days after the last reply. New replies are no longer allowed.