Hi Yunhan, On Mon, Jul 31, 2017 at 10:22 AM, Yunhan Wang <yunhanw@xxxxxxxxxx> wrote: > Hi, > > I am doing some experiments to understand Bluez DBUS API using Bluez > 5.46, and feel a little bit confused about Gatt Dbus example code and > bluetoothctl. > > First, I do sudo bluetoothd --experimental -d, then I create two > virtual bt interfaces and bring up example-gatt-server, then > example-gatt-client cannot find any new gatt service. Any idea? You would have to connect so the client could discover the services. > Also, I have checked all information under org.bluez using d-feet, the > gatt service and characteristics from example-gatt-client have not yet > been added. I print all infos under ObjectManager for bluez, and > cannot find these services and characteristics. example-gatt-client only discover service over D-Bus, anyway in case you refering to example-gatt-server its services are on the client side, so they won't show on the bluetoothd D-Bus connection in d-feet instead you would have to look at example-gatt-server connection. > I also try to use register-service, and register-characteristic for > hci0 using bluetoothctl, but I cannot find any added service and > characteristics under d-feet and ObjectManager. Any idea? Same thing, they are under bluetoothctl connection not bluetoothd. > > bluez-5.46$ sudo ./emulator/btvirt -L -l2 > Bluetooth emulator ver 5.46 > > > bluez-5.46/test$ sudo ./example-gatt-server > Registering GATT application... > GetManagedObjects > GATT application registered > Battery Level drained: 98 > Battery Level drained: 96 > Battery Level drained: 94 > Battery Level drained: 92 > Battery Level drained: 90 > Battery Level drained: 88 > Battery Level drained: 86 > Battery Level drained: 84 > > sudo ./example-gatt-client > Getting objects... > No Heart Rate Service found > example-gatt-client doesnt connect, this is why there is no parameter in the first place, so you would have to connect to the device first then run it. > sudo ./client/bluetoothctl > [NEW] Controller 00:AA:01:00:00:23 hostname [default] > [NEW] Device 00:AA:01:01:00:24 hostname #2 > Agent registered > [bluetooth]# power on > Changing power on succeeded > [CHG] Controller 00:AA:01:00:00:23 Powered: yes > [bluetooth]# register-service 00001820-0000-1000-8000-00805f9b34fb > [NEW] Primary Service > /org/bluez/app/service0xd5eac0 > 00001820-0000-1000-8000-00805f9b34fb > Internet Protocol Support > [/org/bluez/app/service0xd5eac0] Primary (yes/no): yes > register-characteristic 00002a06-0000-1000-8000-00805f9b34fb > write-without-response > [NEW] Characteristic > /org/bluez/app/service0xd5eac0/chrc0xd5f150 > 00002a06-0000-1000-8000-00805f9b34fb > Alert Level > [/org/bluez/app/service0xd5eac0/chrc0xd5f150] Enter value: 0x1 > [bluetooth]# register-application > [CHG] Controller 00:AA:01:00:00:23 UUIDs: 00001801-0000-1000-8000-00805f9b34fb > [CHG] Controller 00:AA:01:00:00:23 UUIDs: 00001820-0000-1000-8000-00805f9b34fb > [CHG] Controller 00:AA:01:00:00:23 UUIDs: 0000110e-0000-1000-8000-00805f9b34fb > [CHG] Controller 00:AA:01:00:00:23 UUIDs: 00001200-0000-1000-8000-00805f9b34fb > [CHG] Controller 00:AA:01:00:00:23 UUIDs: 00001800-0000-1000-8000-00805f9b34fb > [CHG] Controller 00:AA:01:00:00:23 UUIDs: 0000110c-0000-1000-8000-00805f9b34fb > Application registered > [bluetooth]# advertise on > Advertising object registered Now you would have to select the second controller you have created, scan and connect, that in turn will discover the service above. Btw, I just discover a little problem when the controllers are dual-mode it seems we don't fallback to the second bearer if the first could not be connected, but since you are using single mode only that should work just fine. -- Luiz Augusto von Dentz -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
