C#应用中BLE ValueChanged事件停止触发问题咨询

Hey Dan, let's dig into why your BLE ValueChanged events are stopping unexpectedly. Even though you're holding references to the device/service/characteristic as form members, there are still a few common culprits here for Windows 10 16299 and WinForms:

If your event handler throws an uncaught exception, the .NET runtime will stop triggering subsequent events for that characteristic. Always wrap your processing logic in a try-catch block to avoid this silent failure:

private void Characteristic_ValueChanged(GattCharacteristic sender, GattValueChangedEventArgs args)
{
    try
    {
        // Your existing data processing code
        var rawData = args.CharacteristicValue;
        // Parse, log, or update UI with the data
    }
    catch (Exception ex)
    {
        // Log the error (use Debug.WriteLine or a proper logging library)
        Debug.WriteLine($"ValueChanged handler failed: {ex.Message}\n{ex.StackTrace}");
    }
}

The BLE device or Windows itself might drop the connection even if you hold references. Add a handler to track connection status changes:

// Add this after you've connected to the BLE device
myBLEDevice.ConnectionStatusChanged += Device_ConnectionStatusChanged;

private void Device_ConnectionStatusChanged(BluetoothLEDevice sender, object args)
{
    Debug.WriteLine($"BLE Connection Status: {sender.ConnectionStatus}");
    if (sender.ConnectionStatus == BluetoothConnectionStatus.Disconnected)
    {
        // Add reconnection logic here if needed
        Debug.WriteLine("BLE device disconnected unexpectedly!");
    }
}

If you see a Disconnected status when events stop, the issue is at the connection level (not GC). You might need to request a longer connection interval from the device or adjust Windows' BLE power settings.

Windows 10 1709 (your 16299 release) introduced the GattSession.MaintainConnection property, which prevents the system from auto-disconnecting idle BLE sessions. Enable this after acquiring your characteristic:

// Get the session from your characteristic and enable persistent connection
var gattSession = myGattCharacteristic.Session;
gattSession.MaintainConnection = true;

This tells Windows to keep the connection alive even if it thinks the link is idle (even though you're receiving data every second, system heuristics might still trigger a disconnect).

Even with form-level members, edge cases like accidental reassignment or anonymous method reference issues can lead to GC. Add debug finalizers to verify:

// Add this to your main form class for debugging
~MainForm()
{
    Debug.WriteLine("Main form finalized - check if BLE objects were disposed alongside it");
}

// Or if you use a wrapper class for your characteristic:
public class BleCharacteristicWrapper
{
    public GattCharacteristic Characteristic { get; }

    public BleCharacteristicWrapper(GattCharacteristic characteristic)
    {
        Characteristic = characteristic;
    }

    ~BleCharacteristicWrapper()
    {
        Debug.WriteLine("Characteristic wrapper finalized - this means the characteristic was GC'd!");
    }
}

If you see these debug messages when events stop, you'll know your references are being released somewhere—double-check for accidental null assignments or unsubscribed events.

If your handler does heavy processing or blocks the UI thread, it can cause the event loop to hang, leading to missed events. Offload work to a background thread:

private async void Characteristic_ValueChanged(GattCharacteristic sender, GattValueChangedEventArgs args)
{
    try
    {
        // Copy data first to avoid accessing args on a background thread
        var data = args.CharacteristicValue.ToArray();
        await Task.Run(() =>
        {
            // Process data here on a non-UI thread
        });
        // Update UI safely if needed
        Invoke((Action)(() => { /* Update labels/controls here */ }));
    }
    catch (Exception ex)
    {
        Debug.WriteLine($"Processing error: {ex.Message}");
    }
}

16299 is an older Windows 10 release, and early WinRT BLE APIs had known event-handling issues. If possible, test your app on a newer Windows 10 version (1909 or later) to see if the problem resolves. If you can't update, check for applicable KB patches for BLE connectivity in the 16299 release.

内容的提问来源于stack exchange，提问作者Dan