DelphiUdIT

The connection parameters are described UUID 00002A04-0000-1000-8000-00805F9B34FB, with 8 bytes data, but this is read only characteristic; you can read the characteristic and see how your BLE device want to be connected. <?xml version="1.0" encoding="utf-8"?> <!-- Copyright 2011 Bluetooth SIG, Inc. All rights reserved. --> <Characteristic xsi:noNamespaceSchemaLocation="http://schemas.bluetooth.org/Documents/characteristic.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="Peripheral Preferred Connection Parameters" type="org.bluetooth.characteristic.gap.peripheral_preferred_connection_parameters" last-modified="2013-05-29" uuid="2A04"> <InformativeText> <Abstract> <!--The Information included in this page is informative. The normative descriptions are contained in the applicable specification.--> </Abstract> <InformativeDisclaimer /> </InformativeText> <Value> <Field name="Minimum Connection Interval"> <InformativeText>connInterval_min = Minimum Connection Interval * 1.25 ms</InformativeText> <Requirement>Mandatory</Requirement> <Format>uint16</Format> <Minimum>6</Minimum> <Maximum>3200</Maximum> <AdditionalValues> <Enumeration key="65535" value="no specific minimum" /> </AdditionalValues> </Field> <Field name="Maximum Connection Interval"> <InformativeText>connInterval_max = Maximum Connection Interval * 1.25 ms. and is equal or greater than the Minimum Connection Interval</InformativeText> <Requirement>Mandatory</Requirement> <Format>uint16</Format> <Minimum>6</Minimum> <Maximum>3200</Maximum> <AdditionalValues> <Enumeration key="65535" value="no specific maximum" /> </AdditionalValues> </Field> <Field name="Slave Latency"> <Requirement>Mandatory</Requirement> <Format>uint16</Format> <Minimum>0</Minimum> <Maximum>1000</Maximum> </Field> <Field name="Connection Supervision Timeout Multiplier"> <Requirement>Mandatory</Requirement> <Format>uint16</Format> <Minimum>10</Minimum> <Maximum>3200</Maximum> <AdditionalValues> <Enumeration key="65535" value="no specific value requested" /> </AdditionalValues> </Field> </Value>

I can make two suggestions: 1) Use Bluetooth LE Lab (https://www.microsoft.com/store/productId/9N6JD37GWZC8) that you find in the Windows store and with that try to write the Gatt characteristic that affect your hardware, so you see the response times with another software; 2) Try to use the BLE connection parameters: these are the settings that an application can try to impose on a BLE device, related to the communication protocol between SERVER GATT and CLIENT GATT (which I never used nor know how to use). The most interesting parameters are the AdvertisingInterval, ConnectionInterval, SlaveLatency, Connection monitoring timeout. But I don't know at this moment how to monitor them or how to set them.

I have no news of operating differences on receiving messages in Windows. I tested my application (which I think uses BLE like yours) in MAC, Android and Windows and no change to read and write between the platforms, OnCharacteristicRead should works. Tomorrow I'll tested with BLE device. ……..

Yes, stay on BLE specifications the maximum response time should be around 10 seconds. I normaly use about 5 seconds (timer or timeout) (5.2 seconds exactly) and Always all the devices respond. But the logic to "list" the device is different: in Android I use the "end" event, while in Windows I use the "single" discovery event. This should be in that way: if the "end" discovery event works, the "single" discovery event doesn't work and vice versa. I don't know if in the last updates somthing is changed, but surely in that way is working. Bye

This is the reference page for Tokyo release: http://docwiki.embarcadero.com/Libraries/Tokyo/en/System.Bluetooth.TDiscoverLEDeviceEvent That is the same in the Sydney edition. I don't know if the method is hidden when in use with FMX framework in Tokyo edition. Bye

Under Windows you must use "OnDiscoverLEDevice" event. It will be fired for every device discovered. The "OnEndDiscoverDevices" is not fired in Windows, it works on Android Platform. Hope the answer wil be usefull. Bye

May be the options "Local symbols" should be flagged and "Symbol reference info" should be set to "Reference Info". "Debug dcu", my experience, is necessary to step in the source system files during debug.

Yes, this is true. Windows 10 works only with paired BLE devices. After the first time, means the first time that you paired the devices, Windows 10 do this operation automatically, For some devices the manually paired is not necessary. The devices that i use are without auth protocol and Windows 10 paried them automatically when my app tries to scan and get gatt services.

@Rollo62: Thanks for your links. I already use the Nordic microcontrollers, and in particular the BLE devices I was talking about in this post ... they are really them …. Bye

@Rollo62: No, both old (Acer I7 Intel) and new PC (Asus I7 Intel) have the integrated Bluetooth. The old one was ( RIP) 3 years old, the new is less then one year old. I think that the malfunction of the old one was about the compatibility with BLE radio spectrum, may be the Bradcomm Bluetooth was not fully certified for BLE. I tried also in the past with old versions of Windows 10 and different Bluetooth constructors with no success. But the failure probably also depends on the implementation of the Windows Bluetooth (stack), which only in Windows 10 and after several releases of the same has been made fully functional. In an old test, while in Windows 10 the BLE devices were not seen, in an Oracle virtual machine with MAC OSX (I don't remember the exact version, I think Sierra) the BLEs were seen .... very curious. Now, in the next weeks (thanks LOCKDOWN ) i restart testing BLE on Windows with various hardware. Bye

Now that you have tickled the Bluetooth topic, which I had filed, I tried again with the new PC, which has an Intel Bluetooth compared to the one I tested with which had a BroadComm, and in fact the BLE devices are seen correctly without pair them. To see them I use the TBluetoothLE component and the DiscoverLEDevice event which is called for each BLE device found.

From Help: You should "have" the event immedialtly if all is working. I doubt that the BLE is working without any pairing (i cannot try beacuse i don't have any BLE that Windows can see …). If you want to test it after a period, I recommend that you test it after 10.24 seconds. This time comes from a Bluetooth 4.0 specification and is the maximum (worse) response time of a Bluetooth device. I use half of that time (5.2 seconds) and BLE devices always respond ... obviously not tested on Windows platform but on Android. I normally use around seven BLE devices via GATT. There are some answers on Stackoverflow about that (if i remember good). Since I have to work with BLE devices that Windows cannot see, I have given up on developing BLE applications on Windows. Tell us if you will be luckier. Bye

This is the explanation why in Windows 10 it is not necessary to "pair" BLE devices. But the devices must be able to pair, which normal BLEs don't.

Bluetooth "classic" and Bluetoooth "LE" are different things !!! With Windows (any version) you can use BClassic after pairing the devices. And you can use normal api from (TBlutooth component for example). To use BLE in Windows application the BLE devices should be able to pairing with OS. But BLE pure devices (like industrial sensor devices, or other commercial devices) doesn't understand the "piairing" conditions, because it's a no sense. They work on the GATT services basis. So the normal Windows application cannot use BLE. Again, the BClassic and BLE use different radio spectrum tipologies. Microsoft told that the UWP applications using the WinRT api (that are different from the standard Blutooth api) are able to use the BLE. Also, there should be some Bluetooth stacks that may work in Windows with BLE. Take care: some devices (like many smartphones) have the Blutooth radio that works both in BClassic and BLE. This means that you can pair a smartphone and somtimes use the BLE. @emailx45: i'll look at you suggestions, but i think that they speak about BLE with pair conditions. Bye

I have never been able to connect a BLE device with any version of Windows. If you want to use BLE with Windows you have to use WinRT api (i.e. you have to create a UWP application). I've heard you can use BLE with Windows with a special BL stack, but I don't know anything about it. Like you I was able to use BLE with other devices like Android 32 or 64 without any problem. Bye