Running healthd and test_healthd.py
382 views
Skip to first unread message
Liong Hung Wong
May 25, 2011, 11:40:15 AM5/25/11
to antido...@googlegroups.com
Hi,
I execute healthd and src/test_healthd.py with Nonin Oximeter activeted, however, I don't get anything from test_healthd.py (callback methods such as Connected, Associated and etc. not get called).
Debug log of bluetoothd
-----------------------------------
bluetoothd[28234]: src/sdpd-service.c:add_record_to_server() Adding record with handle 0x10005
bluetoothd[28234]: plugins/hciops.c:hciops_add_uuid() hci0
bluetoothd[28234]: plugins/hciops.c:update_service_classes() hci0 value 72
bluetoothd[28234]: plugins/hciops.c:update_ext_inquiry_response() hci0
bluetoothd[28234]: src/sdpd-service.c:add_record_to_server() Record pattern UUID 0000001e-0000-1000-8000-00805f9
bluetoothd[28234]: src/sdpd-service.c:add_record_to_server() Record pattern UUID 0000001f-0000-1000-8000-00805f9
bluetoothd[28234]: src/sdpd-service.c:add_record_to_server() Record pattern UUID 00000100-0000-1000-8000-00805f9
bluetoothd[28234]: src/sdpd-service.c:add_record_to_server() Record pattern UUID 00001002-0000-1000-8000-00805f9
bluetoothd[28234]: src/sdpd-service.c:add_record_to_server() Record pattern UUID 00001400-0000-1000-8000-00805f9
bluetoothd[28234]: src/sdpd-service.c:add_record_to_server() Record pattern UUID 00001402-0000-1000-8000-00805f9
bluetoothd[28234]: health/hdp.c:manager_create_application() Health application created with id /org/bluez/health_app_8
Debug log of bluetoothd when the oximeter is activated
---------------------------------------------------------------------------------------
bluetoothd[28234]: plugins/hciops.c:conn_complete() status 0x00
bluetoothd[28234]: src/adapter.c:adapter_get_device() 00:1C:05:00:40:09
bluetoothd[28234]: plugins/hciops.c:disconn_complete() handle 11 status 0x00
bluetoothd[28234]: src/event.c:btd_event_disconn_complete()
bluetoothd[28234]: src/adapter.c:adapter_remove_connection()
Debug log of healthd
--------------------------
DEBUG <srv_object_class_init in managerdbus.c:928>
DEBUG <main in managerdbus.c:1034> IEEE 11073 D-Bus service
DEBUG <manager_init in manager.c:155> Manager Initialization
DEBUG <manager_start in manager.c:363> Manager starting...
DEBUG <init in plugin_bluez.c:1116> Starting BlueZ link...
DEBUG <connect_adapter in plugin_bluez.c:741> connecting adapter: /org/bluez/28234/hci0
DEBUG <connect_adapter in plugin_bluez.c:780> Getting known devices list
DEBUG <connect_device_signals in plugin_bluez.c:647> device to be connected: /org/bluez/28234/hci0/dev_00_1C_05_00_40_09
DEBUG <get_device_addr in plugin_bluez.c:235> Device address is 00:1C:05:00:40:09
DEBUG <srv_configurepassive in managerdbus.c:288> Agent: /com/signove/health/agent/28256
DEBUG <srv_configurepassive in managerdbus.c:302> Data type: 1004
DEBUG <srv_configurepassive in managerdbus.c:302> Data type: 1007
DEBUG <srv_configurepassive in managerdbus.c:302> Data type: 1029
DEBUG <srv_configurepassive in managerdbus.c:302> Data type: 100f
DEBUG <get_agent_proxy in managerdbus.c:458> get_agent_proxy
DEBUG <create_health_application in plugin_bluez.c:939> Created health application: /org/bluez/health_app_5
DEBUG <create_health_application in plugin_bluez.c:939> Created health application: /org/bluez/health_app_6
DEBUG <create_health_application in plugin_bluez.c:939> Created health application: /org/bluez/health_app_7
DEBUG <create_health_application in plugin_bluez.c:939> Created health application: /org/bluez/health_app_8
Output of test_healthd.py
-------------------------------------
Configuring...
Waiting...
Below are details of my system:
Ubuntu 11.04
Linux ewl-ubuntu-wonglh 2.6.38-8-generic #42-Ubuntu SMP Mon Apr 11 03:31:50 UTC 2011 i686 i686 i386 GNU/Linux
Bluez 4.91
dbus 1.4.6-1ubuntu6
NONiN Oximeter
Antidote 1.0.0
Any idea?
Regards,
--Wong Liong Hung
Elvis Pfutzenreuter
May 25, 2011, 12:17:46 PM5/25/11
to antido...@googlegroups.com
It should work. It is the most often-tested device (for quick tests) in Antidote...
It seems that it is disconnecting right after connection. Try either of these:
0) Make sure device is paired.
1) remove batteries and put again. Sometimes oximeter gets stuck in an internal state
and won't do a new SDP search until batteries are removed.
2) remove pairing / pair again. This forces the oximeter to redo SDP search and also
makes sure that device is really paired.
Liong Hung Wong
May 25, 2011, 2:22:38 PM5/25/11
to antido...@googlegroups.com
It is paired as connection is observed from the bluetoothd's log. However, almost immediately 'disconn' is also observed. I have tried remove pairing/pair (from the bluetooth applet / preference on Ubuntu or using 'blue-simple-agent hci0 00:1c:05:00:40:09) many times.
I will try 1) removing batteries and try again.
Liong Hung Wong
May 26, 2011, 6:52:52 AM5/26/11
to antido...@googlegroups.com
Hi,
I tried by removing batteries and repairing the Nonin Oximeter Model 9560BT, however, the problem still persists.
I managed to get the measurement data using A&D Blood Pressure Monitor UA-767 Plus BT-C and Weight Scale UC-321PBT-C. However, they
work intermittently. In the case nothing received by the test_healthd.py, the log as below is observed:
bluetoothd[31197]: plugins/hciops.c:conn_complete() status 0x00
bluetoothd[31197]: src/adapter.c:adapter_get_device() 00:09:1F:80:12:21
bluetoothd[31197]: plugins/hciops.c:remote_features_information() hci0 status 0
bluetoothd[31197]: plugins/hciops.c:remote_name_information() hci0 status 0
bluetoothd[31197]: plugins/hciops.c:disconn_complete() handle 12 status 0x00
bluetoothd[31197]: src/event.c:btd_event_disconn_complete()
bluetoothd[31197]: src/adapter.c:adapter_remove_connection()
When this happens I don't see the connected icon next to the device item in the paired device list of Bluetooth Preference dialog of Ubuntu. Whenever measurement data is received by test_healthd.py, an connected icon is displayed next to the device.
I am wondering what is the cause of the problem. Could it be caused by Bluez is not functioning well?
Regards,
--Wong Liong Hung
I tried by removing batteries and repairing the Nonin Oximeter Model 9560BT, however, the problem still persists.
I managed to get the measurement data using A&D Blood Pressure Monitor UA-767 Plus BT-C and Weight Scale UC-321PBT-C. However, they
work intermittently. In the case nothing received by the test_healthd.py, the log as below is observed:
bluetoothd[31197]: plugins/hciops.c:conn_complete() status 0x00
bluetoothd[31197]: src/adapter.c:adapter_get_device() 00:09:1F:80:12:21
bluetoothd[31197]: plugins/hciops.c:remote_features_information() hci0 status 0
bluetoothd[31197]: plugins/hciops.c:remote_name_information() hci0 status 0
bluetoothd[31197]: plugins/hciops.c:disconn_complete() handle 12 status 0x00
bluetoothd[31197]: src/event.c:btd_event_disconn_complete()
bluetoothd[31197]: src/adapter.c:adapter_remove_connection()
When this happens I don't see the connected icon next to the device item in the paired device list of Bluetooth Preference dialog of Ubuntu. Whenever measurement data is received by test_healthd.py, an connected icon is displayed next to the device.
I am wondering what is the cause of the problem. Could it be caused by Bluez is not functioning well?
Regards,
--Wong Liong Hung
Elvis Pfutzenreuter
May 26, 2011, 8:36:29 AM5/26/11
to antido...@googlegroups.com
It is certainly something lower-level than Antidote, since, as you say, it does not even
connect.
connect.
I am not no Bluetooth guru, but you could try to send an hcidump to the list,
so there is some chance we identify the problem.
The command for a very complete dump from Bluetooth could be
sudo hcidump hci0 -XXXXXXXXXX > log 2>&1
Liong Hung Wong
Jun 1, 2011, 6:14:12 AM6/1/11
to antido...@googlegroups.com
Hi,
Below is the dump upon powering up the A&D UC-321PBT-C Weight Scale. However, a lot of time I don't get anything in dump as well as bluetooth log when powering up the device. May I know how to test if my bluetooth is working fine?
HCI sniffer - Bluetooth packet analyzer ver 1.42
device: hci0 snap_len: 1028 filter: 0xffffffff
> HCI Event: Connect Request (0x04) plen 10
0000: fd 09 80 1f 09 00 0c 09 00 01 ..........
< HCI Command: Accept Connection Request (0x01|0x0009) plen 7
0000: fd 09 80 1f 09 00 00 .......
> HCI Event: Command Status (0x0f) plen 4
0000: 00 01 09 04 ....
> HCI Event: Role Change (0x12) plen 8
0000: 00 fd 09 80 1f 09 00 00 ........
> ACL data: handle 12 flags 0x02 dlen 12
L2CAP(s): Connect req: psm 1 scid 0x0040
> HCI Event: Connect Complete (0x03) plen 11
0000: 00 0c 00 fd 09 80 1f 09 00 01 00 ...........
< HCI Command: Read Remote Supported Features (0x01|0x001b) plen 2
0000: 0c 00 ..
> HCI Event: Max Slots Change (0x1b) plen 3
0000: 0c 00 05 ...
> HCI Event: Command Status (0x0f) plen 4
0000: 00 01 1b 04 ....
> HCI Event: Read Remote Supported Features (0x0b) plen 11
0000: 00 0c 00 ff ff 8f fe 9b ff 59 83 .........Y.
< HCI Command: Read Remote Extended Features (0x01|0x001c) plen 3
0000: 0c 00 01 ...
> HCI Event: Command Status (0x0f) plen 4
0000: 00 01 1c 04 ....
> ACL data: handle 12 flags 0x02 dlen 12
L2CAP(s): Connect req: psm 1 scid 0x0040
< ACL data: handle 12 flags 0x02 dlen 16
L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 1 status 0
Connection pending - No futher information available
< ACL data: handle 12 flags 0x02 dlen 10
L2CAP(s): Info req: type 2
> ACL data: handle 12 flags 0x02 dlen 16
L2CAP(s): Info rsp: type 2 result 0
Extended feature mask 0x003f
< ACL data: handle 12 flags 0x02 dlen 16
L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 0 status 0
Connection successful
< ACL data: handle 12 flags 0x02 dlen 23
L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 11
RFC 0x00 (Basic)
> HCI Event: Read Remote Extended Features (0x23) plen 13
0000: 00 0c 00 01 01 01 00 00 00 00 00 00 00 .............
< HCI Command: Remote Name Request (0x01|0x0019) plen 10
0000: fd 09 80 1f 09 00 02 00 00 00 ..........
> ACL data: handle 12 flags 0x02 dlen 12
L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 0
< ACL data: handle 12 flags 0x02 dlen 18
L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 4
MTU 672
> ACL data: handle 12 flags 0x02 dlen 14
L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 0
Success
> ACL data: handle 12 flags 0x02 dlen 34
L2CAP(d): cid 0x0040 len 30 [psm 1]
SDP SSA Req: tid 0x1 len 0x19
pat uuid-16 0x1402
max 256
aid(s) 0x0004 (ProtocolDescList) 0x000d (IconURL) 0x0200 (VersionNumList) 0x0301 (SuppDataStoresList) 0x0302 (unknown)
cont 00
< ACL data: handle 12 flags 0x02 dlen 14
L2CAP(d): cid 0x0040 len 10 [psm 1]
SDP SSA Rsp: tid 0x1 len 0x5
count 2
cont 00
> ACL data: handle 12 flags 0x02 dlen 12
L2CAP(s): Disconn req: dcid 0x0040 scid 0x0040
< ACL data: handle 12 flags 0x02 dlen 12
L2CAP(s): Disconn rsp: dcid 0x0040 scid 0x0040
> HCI Event: Number of Completed Packets (0x13) plen 5
0000: 01 0c 00 02 00 .....
> HCI Event: Command Status (0x0f) plen 4
0000: 00 01 19 04 ....
> HCI Event: Number of Completed Packets (0x13) plen 5
0000: 01 0c 00 02 00 .....
> HCI Event: Remote Name Req Complete (0x07) plen 255
0000: 00 fd 09 80 1f 09 00 41 4e 44 20 53 43 35 30 39 .......AND SC509
0010: 30 39 35 30 32 38 37 00 00 00 00 00 00 00 00 00 0950287.........
0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0050: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0060: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0070: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0080: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0090: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ...............
> HCI Event: Number of Completed Packets (0x13) plen 5
0000: 01 0c 00 02 00 .....
> HCI Event: Number of Completed Packets (0x13) plen 5
0000: 01 0c 00 01 00 .....
> HCI Event: Disconn Complete (0x05) plen 4
0000: 00 0c 00 13 ....
> HCI Event: Connect Request (0x04) plen 10
0000: 21 12 80 1f 09 00 04 09 00 01 !.........
< HCI Command: Accept Connection Request (0x01|0x0009) plen 7
0000: 21 12 80 1f 09 00 00 !......
> HCI Event: Command Status (0x0f) plen 4
0000: 00 01 09 04 ....
> HCI Event: Role Change (0x12) plen 8
0000: 00 21 12 80 1f 09 00 00 .!......
> ACL data: handle 11 flags 0x02 dlen 12
L2CAP(s): Connect req: psm 1 scid 0x0040
> HCI Event: Connect Complete (0x03) plen 11
0000: 00 0b 00 21 12 80 1f 09 00 01 00 ...!.......
< HCI Command: Read Remote Supported Features (0x01|0x001b) plen 2
0000: 0b 00 ..
> HCI Event: Max Slots Change (0x1b) plen 3
0000: 0b 00 05 ...
> HCI Event: Command Status (0x0f) plen 4
0000: 00 01 1b 04 ....
> HCI Event: Read Remote Supported Features (0x0b) plen 11
0000: 00 0b 00 ff ff 8f fe 9b ff 59 83 .........Y.
< HCI Command: Read Remote Extended Features (0x01|0x001c) plen 3
0000: 0b 00 01 ...
> HCI Event: Command Status (0x0f) plen 4
0000: 00 01 1c 04 ....
> ACL data: handle 11 flags 0x02 dlen 12
L2CAP(s): Connect req: psm 1 scid 0x0040
< ACL data: handle 11 flags 0x02 dlen 16
L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 1 status 0
Connection pending - No futher information available
< ACL data: handle 11 flags 0x02 dlen 10
L2CAP(s): Info req: type 2
> ACL data: handle 11 flags 0x02 dlen 16
L2CAP(s): Info rsp: type 2 result 0
Extended feature mask 0x003f
< ACL data: handle 11 flags 0x02 dlen 16
L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 0 status 0
Connection successful
< ACL data: handle 11 flags 0x02 dlen 23
L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 11
RFC 0x00 (Basic)
> ACL data: handle 11 flags 0x02 dlen 12
L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 0
< ACL data: handle 11 flags 0x02 dlen 18
L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 4
MTU 672
> ACL data: handle 11 flags 0x02 dlen 14
L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 0
Success
> ACL data: handle 11 flags 0x02 dlen 34
L2CAP(d): cid 0x0040 len 30 [psm 1]
SDP SSA Req: tid 0x1 len 0x19
pat uuid-16 0x1402
max 256
aid(s) 0x0004 (ProtocolDescList) 0x000d (IconURL) 0x0200 (VersionNumList) 0x0301 (SuppDataStoresList) 0x0302 (unknown)
cont 00
< ACL data: handle 11 flags 0x02 dlen 14
L2CAP(d): cid 0x0040 len 10 [psm 1]
SDP SSA Rsp: tid 0x1 len 0x5
count 2
cont 00
> HCI Event: Read Remote Extended Features (0x23) plen 13
0000: 00 0b 00 01 01 01 00 00 00 00 00 00 00 .............
< HCI Command: Remote Name Request (0x01|0x0019) plen 10
0000: 21 12 80 1f 09 00 02 00 00 00 !.........
> ACL data: handle 11 flags 0x02 dlen 12
L2CAP(s): Disconn req: dcid 0x0040 scid 0x0040
< ACL data: handle 11 flags 0x02 dlen 12
L2CAP(s): Disconn rsp: dcid 0x0040 scid 0x0040
> HCI Event: Number of Completed Packets (0x13) plen 5
0000: 01 0b 00 02 00 .....
> HCI Event: Number of Completed Packets (0x13) plen 5
0000: 01 0b 00 02 00 .....
> HCI Event: Number of Completed Packets (0x13) plen 5
0000: 01 0b 00 02 00 .....
> HCI Event: Command Status (0x0f) plen 4
0000: 00 01 19 04 ....
> HCI Event: Remote Name Req Complete (0x07) plen 255
0000: 00 21 12 80 1f 09 00 41 4e 44 20 42 50 35 30 39 .!.....AND BP509
0010: 31 31 30 30 30 32 37 00 00 00 00 00 00 00 00 00 1100027.........
0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0050: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0060: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0070: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0080: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0090: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ...............
> HCI Event: Number of Completed Packets (0x13) plen 5
0000: 01 0b 00 01 00 .....
> HCI Event: Disconn Complete (0x05) plen 4
0000: 00 0b 00 13 ....
> HCI Event: Connect Request (0x04) plen 10
0000: 21 12 80 1f 09 00 04 09 00 01 !.........
< HCI Command: Accept Connection Request (0x01|0x0009) plen 7
0000: 21 12 80 1f 09 00 00 !......
> HCI Event: Command Status (0x0f) plen 4
0000: 00 01 09 04 ....
> HCI Event: Role Change (0x12) plen 8
0000: 00 21 12 80 1f 09 00 00 .!......
> ACL data: handle 12 flags 0x02 dlen 12
L2CAP(s): Connect req: psm 1 scid 0x0040
> HCI Event: Connect Complete (0x03) plen 11
0000: 00 0c 00 21 12 80 1f 09 00 01 00 ...!.......
< HCI Command: Read Remote Supported Features (0x01|0x001b) plen 2
0000: 0c 00 ..
> HCI Event: Max Slots Change (0x1b) plen 3
0000: 0c 00 05 ...
> HCI Event: Command Status (0x0f) plen 4
0000: 00 01 1b 04 ....
> HCI Event: Read Remote Supported Features (0x0b) plen 11
0000: 00 0c 00 ff ff 8f fe 9b ff 59 83 .........Y.
< HCI Command: Read Remote Extended Features (0x01|0x001c) plen 3
0000: 0c 00 01 ...
> HCI Event: Command Status (0x0f) plen 4
0000: 00 01 1c 04 ....
> ACL data: handle 12 flags 0x02 dlen 12
L2CAP(s): Connect req: psm 1 scid 0x0040
< ACL data: handle 12 flags 0x02 dlen 16
L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 1 status 0
Connection pending - No futher information available
< ACL data: handle 12 flags 0x02 dlen 10
L2CAP(s): Info req: type 2
> ACL data: handle 12 flags 0x02 dlen 16
L2CAP(s): Info rsp: type 2 result 0
Extended feature mask 0x003f
< ACL data: handle 12 flags 0x02 dlen 16
L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 0 status 0
Connection successful
< ACL data: handle 12 flags 0x02 dlen 23
L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 11
RFC 0x00 (Basic)
> ACL data: handle 12 flags 0x02 dlen 12
L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 0
< ACL data: handle 12 flags 0x02 dlen 18
L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 4
MTU 672
> ACL data: handle 12 flags 0x02 dlen 14
L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 0
Success
> ACL data: handle 12 flags 0x02 dlen 34
L2CAP(d): cid 0x0040 len 30 [psm 1]
SDP SSA Req: tid 0x1 len 0x19
pat uuid-16 0x1402
max 256
aid(s) 0x0004 (ProtocolDescList) 0x000d (IconURL) 0x0200 (VersionNumList) 0x0301 (SuppDataStoresList) 0x0302 (unknown)
cont 00
< ACL data: handle 12 flags 0x02 dlen 14
L2CAP(d): cid 0x0040 len 10 [psm 1]
SDP SSA Rsp: tid 0x1 len 0x5
count 2
cont 00
> ACL data: handle 12 flags 0x02 dlen 12
L2CAP(s): Disconn req: dcid 0x0040 scid 0x0040
< ACL data: handle 12 flags 0x02 dlen 12
L2CAP(s): Disconn rsp: dcid 0x0040 scid 0x0040
> HCI Event: Read Remote Extended Features (0x23) plen 13
0000: 00 0c 00 01 01 01 00 00 00 00 00 00 00 .............
< HCI Command: Remote Name Request (0x01|0x0019) plen 10
0000: 21 12 80 1f 09 00 02 00 00 00 !.........
> HCI Event: Number of Completed Packets (0x13) plen 5
0000: 01 0c 00 02 00 .....
> HCI Event: Number of Completed Packets (0x13) plen 5
0000: 01 0c 00 02 00 .....
> HCI Event: Number of Completed Packets (0x13) plen 5
0000: 01 0c 00 02 00 .....
> HCI Event: Command Status (0x0f) plen 4
0000: 00 01 19 04 ....
> HCI Event: Remote Name Req Complete (0x07) plen 255
0000: 13 21 12 80 1f 09 00 00 00 00 00 00 00 00 00 00 .!..............
0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0050: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0060: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0070: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0080: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0090: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ...............
> HCI Event: Number of Completed Packets (0x13) plen 5
0000: 01 0c 00 01 00 .....
> HCI Event: Disconn Complete (0x05) plen 4
0000: 00 0c 00 13 ....
> HCI Event: Connect Request (0x04) plen 10
0000: 21 12 80 1f 09 00 04 09 00 01 !.........
< HCI Command: Accept Connection Request (0x01|0x0009) plen 7
0000: 21 12 80 1f 09 00 00 !......
> HCI Event: Command Status (0x0f) plen 4
0000: 00 01 09 04 ....
> HCI Event: Role Change (0x12) plen 8
0000: 00 21 12 80 1f 09 00 00 .!......
> ACL data: handle 11 flags 0x02 dlen 12
L2CAP(s): Connect req: psm 1 scid 0x0040
> HCI Event: Connect Complete (0x03) plen 11
0000: 00 0b 00 21 12 80 1f 09 00 01 00 ...!.......
< HCI Command: Read Remote Supported Features (0x01|0x001b) plen 2
0000: 0b 00 ..
> HCI Event: Max Slots Change (0x1b) plen 3
0000: 0b 00 05 ...
> HCI Event: Command Status (0x0f) plen 4
0000: 00 01 1b 04 ....
> HCI Event: Read Remote Supported Features (0x0b) plen 11
0000: 00 0b 00 ff ff 8f fe 9b ff 59 83 .........Y.
< HCI Command: Read Remote Extended Features (0x01|0x001c) plen 3
0000: 0b 00 01 ...
> HCI Event: Command Status (0x0f) plen 4
0000: 00 01 1c 04 ....
> ACL data: handle 11 flags 0x02 dlen 12
L2CAP(s): Connect req: psm 1 scid 0x0040
< ACL data: handle 11 flags 0x02 dlen 16
L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 1 status 0
Connection pending - No futher information available
< ACL data: handle 11 flags 0x02 dlen 10
L2CAP(s): Info req: type 2
> ACL data: handle 11 flags 0x02 dlen 16
L2CAP(s): Info rsp: type 2 result 0
Extended feature mask 0x003f
< ACL data: handle 11 flags 0x02 dlen 16
L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 0 status 0
Connection successful
< ACL data: handle 11 flags 0x02 dlen 23
L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 11
RFC 0x00 (Basic)
> ACL data: handle 11 flags 0x02 dlen 12
L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 0
< ACL data: handle 11 flags 0x02 dlen 18
L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 4
MTU 672
> ACL data: handle 11 flags 0x02 dlen 14
L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 0
Success
> HCI Event: Read Remote Extended Features (0x23) plen 13
0000: 00 0b 00 01 01 01 00 00 00 00 00 00 00 .............
< HCI Command: Remote Name Request (0x01|0x0019) plen 10
0000: 21 12 80 1f 09 00 02 00 00 00 !.........
> ACL data: handle 11 flags 0x02 dlen 17
> ACL data: handle 11 flags 0x01 dlen 17
L2CAP(d): cid 0x0040 len 30 [psm 1]
SDP SSA Req: tid 0x1 len 0x19
pat uuid-16 0x1402
max 256
aid(s) 0x0004 (ProtocolDescList) 0x000d (IconURL) 0x0200 (VersionNumList) 0x0301 (SuppDataStoresList) 0x0302 (unknown)
cont 00
< ACL data: handle 11 flags 0x02 dlen 14
L2CAP(d): cid 0x0040 len 10 [psm 1]
SDP SSA Rsp: tid 0x1 len 0x5
count 2
cont 00
> ACL data: handle 11 flags 0x02 dlen 12
L2CAP(s): Disconn req: dcid 0x0040 scid 0x0040
< ACL data: handle 11 flags 0x02 dlen 12
L2CAP(s): Disconn rsp: dcid 0x0040 scid 0x0040
> HCI Event: Number of Completed Packets (0x13) plen 5
0000: 01 0b 00 02 00 .....
> HCI Event: Number of Completed Packets (0x13) plen 5
0000: 01 0b 00 02 00 .....
> HCI Event: Command Status (0x0f) plen 4
0000: 00 01 19 04 ....
> HCI Event: Number of Completed Packets (0x13) plen 5
0000: 01 0b 00 02 00 .....
> HCI Event: Remote Name Req Complete (0x07) plen 255
0000: 00 21 12 80 1f 09 00 41 4e 44 20 42 50 35 30 39 .!.....AND BP509
0010: 31 31 30 30 30 32 37 00 00 00 00 00 00 00 00 00 1100027.........
0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0050: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0060: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0070: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0080: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0090: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ...............
> HCI Event: Number of Completed Packets (0x13) plen 5
0000: 01 0b 00 01 00 .....
> HCI Event: Disconn Complete (0x05) plen 4
0000: 00 0b 00 13 ....
> HCI Event: Connect Request (0x04) plen 10
0000: 21 12 80 1f 09 00 04 09 00 01 !.........
< HCI Command: Accept Connection Request (0x01|0x0009) plen 7
0000: 21 12 80 1f 09 00 00 !......
> HCI Event: Command Status (0x0f) plen 4
0000: 00 01 09 04 ....
> HCI Event: Role Change (0x12) plen 8
0000: 00 21 12 80 1f 09 00 00 .!......
> ACL data: handle 12 flags 0x02 dlen 12
L2CAP(s): Connect req: psm 1 scid 0x0040
> HCI Event: Connect Complete (0x03) plen 11
0000: 00 0c 00 21 12 80 1f 09 00 01 00 ...!.......
< HCI Command: Read Remote Supported Features (0x01|0x001b) plen 2
0000: 0c 00 ..
> HCI Event: Max Slots Change (0x1b) plen 3
0000: 0c 00 05 ...
> HCI Event: Command Status (0x0f) plen 4
0000: 00 01 1b 04 ....
> HCI Event: Read Remote Supported Features (0x0b) plen 11
0000: 00 0c 00 ff ff 8f fe 9b ff 59 83 .........Y.
< HCI Command: Read Remote Extended Features (0x01|0x001c) plen 3
0000: 0c 00 01 ...
> HCI Event: Command Status (0x0f) plen 4
0000: 00 01 1c 04 ....
> ACL data: handle 12 flags 0x02 dlen 12
L2CAP(s): Connect req: psm 1 scid 0x0040
< ACL data: handle 12 flags 0x02 dlen 16
L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 1 status 0
Connection pending - No futher information available
< ACL data: handle 12 flags 0x02 dlen 10
L2CAP(s): Info req: type 2
> ACL data: handle 12 flags 0x02 dlen 16
L2CAP(s): Info rsp: type 2 result 0
Extended feature mask 0x003f
< ACL data: handle 12 flags 0x02 dlen 16
L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 0 status 0
Connection successful
< ACL data: handle 12 flags 0x02 dlen 23
L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 11
RFC 0x00 (Basic)
> ACL data: handle 12 flags 0x02 dlen 12
L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 0
< ACL data: handle 12 flags 0x02 dlen 18
L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 4
MTU 672
> ACL data: handle 12 flags 0x02 dlen 14
L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 0
Success
> ACL data: handle 12 flags 0x02 dlen 34
L2CAP(d): cid 0x0040 len 30 [psm 1]
SDP SSA Req: tid 0x1 len 0x19
pat uuid-16 0x1402
max 256
aid(s) 0x0004 (ProtocolDescList) 0x000d (IconURL) 0x0200 (VersionNumList) 0x0301 (SuppDataStoresList) 0x0302 (unknown)
cont 00
< ACL data: handle 12 flags 0x02 dlen 14
L2CAP(d): cid 0x0040 len 10 [psm 1]
SDP SSA Rsp: tid 0x1 len 0x5
count 2
cont 00
> HCI Event: Read Remote Extended Features (0x23) plen 13
0000: 00 0c 00 01 01 01 00 00 00 00 00 00 00 .............
< HCI Command: Remote Name Request (0x01|0x0019) plen 10
0000: 21 12 80 1f 09 00 02 00 00 00 !.........
> ACL data: handle 12 flags 0x02 dlen 12
L2CAP(s): Disconn req: dcid 0x0040 scid 0x0040
< ACL data: handle 12 flags 0x02 dlen 12
L2CAP(s): Disconn rsp: dcid 0x0040 scid 0x0040
> HCI Event: Number of Completed Packets (0x13) plen 5
0000: 01 0c 00 02 00 .....
> HCI Event: Number of Completed Packets (0x13) plen 5
0000: 01 0c 00 02 00 .....
> HCI Event: Number of Completed Packets (0x13) plen 5
0000: 01 0c 00 02 00 .....
> HCI Event: Command Status (0x0f) plen 4
0000: 00 01 19 04 ....
> HCI Event: Remote Name Req Complete (0x07) plen 255
0000: 00 21 12 80 1f 09 00 41 4e 44 20 42 50 35 30 39 .!.....AND BP509
0010: 31 31 30 30 30 32 37 00 00 00 00 00 00 00 00 00 1100027.........
0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0050: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0060: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0070: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0080: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0090: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ...............
> HCI Event: Number of Completed Packets (0x13) plen 5
0000: 01 0c 00 01 00 .....
> HCI Event: Disconn Complete (0x05) plen 4
0000: 00 0c 00 13 ....
Liong Hung Wong
Jun 1, 2011, 7:28:16 AM6/1/11
to antido...@googlegroups.com
Hi,
I also try to use hcitool to create connection
root@ewl-ubuntu-wonglh:/home/ewl# hcitool cc 00:09:1F:80:09:FD
hcidump:
HCI sniffer - Bluetooth packet analyzer ver 1.42
device: hci0 snap_len: 1028 filter: 0xffffffff
< HCI Command: Create Connection (0x01|0x0005) plen 13device: hci0 snap_len: 1028 filter: 0xffffffff
0000: fd 09 80 1f 09 00 18 cc 02 00 00 00 01 .............
> HCI Event: Command Status (0x0f) plen 4
> HCI Event: Connect Complete (0x03) plen 11
< HCI Command: Read Remote Supported Features (0x01|0x001b) plen 2
> HCI Event: Max Slots Change (0x1b) plen 3
> HCI Event: Command Status (0x0f) plen 4
0000: 00 01 1b 04 ....
> HCI Event: Read Remote Supported Features (0x0b) plen 11
< HCI Command: Remote Name Request (0x01|0x0019) plen 10
0000: fd 09 80 1f 09 00 02 00 00 00 ..........
> HCI Event: Command Status (0x0f) plen 4
0000: 00 01 19 04 ....
> HCI Event: Remote Name Req Complete (0x07) plen 255
0000: 00 01 19 04 ....
> HCI Event: Remote Name Req Complete (0x07) plen 255
0000: 00 fd 09 80 1f 09 00 41 4e 44 20 53 43 35 30 39 .......AND SC509
0010: 30 39 35 30 32 38 37 00 00 00 00 00 00 00 00 00 0950287.........
0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0050: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0060: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0070: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0080: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0090: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ...............
< HCI Command: Disconnect (0x01|0x0006) plen 30010: 30 39 35 30 32 38 37 00 00 00 00 00 00 00 00 00 0950287.........
0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0050: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0060: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0070: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0080: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0090: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ...............
0000: 10 00 13 ...
> HCI Event: Command Status (0x0f) plen 4
> HCI Event: Disconn Complete (0x05) plen 4
No connection:
root@ewl-ubuntu-wonglh:/home/ewl# hcitool con
Connections:
Liong Hung Wong
Jun 2, 2011, 6:38:25 AM6/2/11
to antido...@googlegroups.com
It seems to be caused by the following error
L2CAP(s): Connect rsp: dcid 0x0000 scid 0x0041 result 3 status 0
Connection refused - security block
Detail log:
> ACL data: handle 11 flags 0x02 dlen 34
L2CAP(d): cid 0x0040 len 30 [psm 1]
SDP SSA Req: tid 0x1 len 0x19
pat uuid-16 0x1402
max 256
aid(s) 0x0004 (ProtocolDescList) 0x000d (IconURL) 0x0200 (VersionNumList) 0x0301 (SuppDataStoresList) 0x0302 (unknown)
cont 00
L2CAP(d): cid 0x0040 len 140 [psm 1]
SDP SSA Rsp: tid 0x1 len 0x87
count 132
record #0
aid 0x0004 (ProtocolDescList)
< < uuid-16 0x0100 (L2CAP) uint 0x1001 > <
uuid-16 0x001e uint 0x100 > >
aid 0x000d (IconURL)
< < < uuid-16 0x0100 (L2CAP) uint 0x1003 > < uuid-16 0x001f > > >
aid 0x0200 (VersionNumList)
< < uint 0x8 uint 0x100f uint 0x1 str "healthd" > < uint 0x7 uint 0x1029 uint 0x1 str "healthd" > < uint 0x6 uint 0x1007 uint 0x1 str "healthd" > < uint 0x5 uint 0x1004 uint 0x1 str "healthd" > >
aid 0x0301 (SuppDataStoresList)
uint 0x1
aid 0x0302 (unknown)
uint 0x6
cont 00
> ACL data: handle 11 flags 0x02 dlen 12
L2CAP(s): Disconn req: dcid 0x0040 scid 0x0040
< ACL data: handle 11 flags 0x02 dlen 12
L2CAP(s): Disconn rsp: dcid 0x0040 scid 0x0040
> ACL data: handle 11 flags 0x02 dlen 10
L2CAP(s): Info req: type 2
< ACL data: handle 11 flags 0x02 dlen 16
L2CAP(s): Info rsp: type 2 result 0
Extended feature mask 0x00b8L2CAP(s): Info req: type 2
< ACL data: handle 11 flags 0x02 dlen 16
L2CAP(s): Info rsp: type 2 result 0
> ACL data: handle 11 flags 0x02 dlen 12
> HCI Event: Number of Completed Packets (0x13) plen 5
0000: 01 0b 00 02 00 .....
< ACL data: handle 11 flags 0x02 dlen 16
L2CAP(s): Connect rsp: dcid 0x0000 scid 0x0041 result 3 status 0Connection refused - security block
> HCI Event: Number of Completed Packets (0x13) plen 5
0000: 01 0b 00 02 00 .....
> HCI Event: Command Status (0x0f) plen 4
0000: 00 01 19 04 ....
0000: 00 01 19 04 ....
> HCI Event: Number of Completed Packets (0x13) plen 5
0000: 01 0b 00 02 00 .....
0000: 01 0b 00 02 00 .....
> HCI Event: Remote Name Req Complete (0x07) plen 255
0000: 00 21 12 80 1f 09 00 41 4e 44 20 42 50 35 30 39 .!.....AND BP509
0010: 31 31 30 30 30 32 37 00 00 00 00 00 00 00 00 00 1100027.........0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0050: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0060: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0070: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0080: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0090: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ...............
> HCI Event: Number of Completed Packets (0x13) plen 5
0000: 01 0b 00 02 00 .....
> HCI Event: Number of Completed Packets (0x13) plen 5
0000: 01 0b 00 01 00 .....0000: 01 0b 00 02 00 .....
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Disconn Complete (0x05) plen 4
Elvis Pfutzenreuter
Jun 2, 2011, 8:20:16 AM6/2/11
to antido...@googlegroups.com
Looks like it was not paired, or some problem with SSP.
Liong Hung Wong
Jun 7, 2011, 2:53:32 AM6/7/11
to antido...@googlegroups.com
Hi,
I managed to solve the problem after setting hciconfig to enable auth and encrypt modes.
Now the blood pressure monitor is working constantly. I can get the measurement data on test_healthd.py.
However, I am still getting problem on Nonin Oximeter 9560BT.
< HCI Command: Accept Connection Request (0x01|0x0009) plen 7
bdaddr 00:1C:05:00:40:09 role 0x00
Role: Master
> HCI Event: Command Status (0x0f) plen 4
Accept Connection Request (0x01|0x0009) status 0x00 ncmd 1
> HCI Event: Role Change (0x12) plen 8
status 0x00 bdaddr 00:1C:05:00:40:09 role 0x00
Role: Master
> HCI Event: Link Key Request (0x17) plen 6
bdaddr 00:1C:05:00:40:09
< HCI Command: Link Key Request Reply (0x01|0x000b) plen 22
bdaddr 00:1C:05:00:40:09 key 8712220DF111132E6F579FED2B8E5E96
> ACL data: handle 11 flags 0x02 dlen 10
L2CAP(s): Info req: type 2
> HCI Event: Command Complete (0x0e) plen 10
Link Key Request Reply (0x01|0x000b) ncmd 1
status 0x00 bdaddr 00:1C:05:00:40:09
> HCI Event: Connect Complete (0x03) plen 11
status 0x00 handle 11 bdaddr 00:1C:05:00:40:09 type ACL encrypt 0x01
< HCI Command: Read Remote Supported Features (0x01|0x001b) plen 2
handle 11
> HCI Event: Max Slots Change (0x1b) plen 3
handle 11 slots 5
> HCI Event: Disconn Complete (0x05) plen 4
status 0x00 handle 11 reason 0x13
Reason: Remote User Terminated Connection
> HCI Event: Command Status (0x0f) plen 4
Read Remote Supported Features (0x01|0x001b) status 0x12 ncmd 1
Error: Invalid HCI Command Parameters
Any idea?
I managed to solve the problem after setting hciconfig to enable auth and encrypt modes.
Now the blood pressure monitor is working constantly. I can get the measurement data on test_healthd.py.
However, I am still getting problem on Nonin Oximeter 9560BT.
< HCI Command: Accept Connection Request (0x01|0x0009) plen 7
Role: Master
> HCI Event: Command Status (0x0f) plen 4
> HCI Event: Role Change (0x12) plen 8
Role: Master
> HCI Event: Link Key Request (0x17) plen 6
bdaddr 00:1C:05:00:40:09
< HCI Command: Link Key Request Reply (0x01|0x000b) plen 22
bdaddr 00:1C:05:00:40:09 key 8712220DF111132E6F579FED2B8E5E96
> ACL data: handle 11 flags 0x02 dlen 10
L2CAP(s): Info req: type 2
Link Key Request Reply (0x01|0x000b) ncmd 1
status 0x00 bdaddr 00:1C:05:00:40:09
> HCI Event: Connect Complete (0x03) plen 11
< HCI Command: Read Remote Supported Features (0x01|0x001b) plen 2
> HCI Event: Max Slots Change (0x1b) plen 3
> HCI Event: Disconn Complete (0x05) plen 4
Reason: Remote User Terminated Connection
> HCI Event: Command Status (0x0f) plen 4
Error: Invalid HCI Command Parameters
Any idea?
Elvis Pfutzenreuter
Jun 7, 2011, 9:49:30 AM6/7/11
to antido...@googlegroups.com
Will have to dig deeper (in BT documentation) to see why it is rejecting.
Meanwhile, try to remove oximeter batteries, open it (so it eats up any
leftover charge) and try to pair again. BTW, which kernel version are you
using?
Liong Hung Wong
Jun 8, 2011, 6:49:58 AM6/8/11
to antido...@googlegroups.com
I removed the batteries, opened it and tried pairing again. I found out that there was a Read Remote Supported Features command completed successfully when the pairing was in progress.
See below:
> HCI Event: Connect Complete (0x03) plen 11
status 0x00 handle 11 bdaddr 00:1C:05:00:40:09 type ACL encrypt 0x01
< HCI Command: Read Remote Supported Features (0x01|0x001b) plen 2
handle 11
> HCI Event: Max Slots Change (0x1b) plen 3
handle 11 slots 5
> HCI Event: Command Status (0x0f) plen 4
Read Remote Supported Features (0x01|0x001b) status 0x00 ncmd 1> HCI Event: Read Remote Supported Features (0x0b) plen 11
status 0x00 handle 11
Features: 0xff 0xeb 0x8d 0xf8 0x1b 0x08 0x00 0x00
However, after that I did another measurement. The command failed again. When this happened the value for the handle is 12. When the command completed successfully, the value was 11.
Is the invalid command parameter referring to the value 11?
> HCI Event: Connect Request (0x04) plen 10
< HCI Command: Accept Connection Request (0x01|0x0009) plen 7
bdaddr 00:1C:05:00:40:09 role 0x00
Role: Master
> HCI Event: Command Status (0x0f) plen 4
Accept Connection Request (0x01|0x0009) status 0x00 ncmd 1
> HCI Event: Role Change (0x12) plen 8
status 0x00 bdaddr 00:1C:05:00:40:09 role 0x00
Role: Master
> HCI Event: Link Key Request (0x17) plen 6
bdaddr 00:1C:05:00:40:09
< HCI Command: Link Key Request Reply (0x01|0x000b) plen 22
> ACL data: handle 12 flags 0x02 dlen 10
L2CAP(s): Info req: type 2
> HCI Event: Command Complete (0x0e) plen 10
Link Key Request Reply (0x01|0x000b) ncmd 1
status 0x00 bdaddr 00:1C:05:00:40:09
> HCI Event: Connect Complete (0x03) plen 11
< HCI Command: Read Remote Supported Features (0x01|0x001b) plen 2
handle 12
> HCI Event: Max Slots Change (0x1b) plen 3
> HCI Event: Disconn Complete (0x05) plen 4
Reason: Remote User Terminated Connection
> HCI Event: Command Status (0x0f) plen 4
Read Remote Supported Features (0x01|0x001b) status 0x12 ncmd 1
Error: Invalid HCI Command Parameters
Elvis Pfutzenreuter
Jun 8, 2011, 7:52:23 AM6/8/11
to antido...@googlegroups.com
Really weird. I use the same oximeter with the same Ubuntu (saw the kernel version) and it
works perfectly.
Prashant Kumar
Apr 9, 2013, 6:03:32 AM4/9/13
to antido...@googlegroups.com
hii Elvis,
I told that iam getting one reading from Nonin 9560 oximeter.But now iam not getting that one reading also.
I downloaded Health service and Health service test activity again and created new shared library but still iam not getting any data.
I tried with ubuntu 12.04, 11.04 (natty) systems and samsung ICS phones(kernel 3.0.8) but iam getting data from AND BP machie and Weighing scale when i disable the SSP mode in the phone and system.
So Is my Oximeter having problem but it is communicating with My fitness companion and working fine there.
Can u help.
Logcat is showing the following:
W/HST ( 4993): Activity created
W/HST ( 4993): Service connection established
W/HST ( 4993): Configuring...
W/HSS ( 4948): ConfigurePassive
W/HSS ( 4948): Configured agent com.signove.health.service.
I told that iam getting one reading from Nonin 9560 oximeter.But now iam not getting that one reading also.
I downloaded Health service and Health service test activity again and created new shared library but still iam not getting any data.
I tried with ubuntu 12.04, 11.04 (natty) systems and samsung ICS phones(kernel 3.0.8) but iam getting data from AND BP machie and Weighing scale when i disable the SSP mode in the phone and system.
So Is my Oximeter having problem but it is communicating with My fitness companion and working fine there.
Can u help.
Logcat is showing the following:
W/HST ( 4993): Activity created
W/HST ( 4993): Service connection established
W/HST ( 4993): Configuring...
W/HSS ( 4948): ConfigurePassive
W/HSS ( 4948): Configured agent com.signove.health.service.
test.HealthAgentAPI$Stub$Proxy@40d22610
I/ActivityManager( 193): Displayed com.signove.health.servicetest/.HealthServiceTestActivity: +238ms
D/OpenGLRenderer( 363): Flushing caches (mode 1)
D/OpenGLRenderer( 363): Flushing caches (mode 0)
W/InputManagerService( 193): Starting input on non-focused client com.android.internal.view.IInputMethodClient$Stub$Proxy@40f498a8 (uid=10005 pid=363)
D/AudioHardware( 137): AudioHardware pcm playback is going to standby.
V/AudioHardware( 137): closeMixer_l() mMixerOpenCnt: 1
D/AudioHardware( 137): closePcmOut_l() mPcmOpenCnt: 1
D/AlarmManagerService( 193): Kernel timezone updated to -330 minutes west of GMT
D/SystemClock( 347): Setting time of day to sec=1365428706
V/AlarmClock( 5253): AlarmInitReceiver finished
D/ConnectivityService( 193): ConnectivityChange for mobile: CONNECTED/CONNECTED
W/NetworkStats( 193): dropping UID delta from unknown iface: iface=pdp0 uid=0 set=DEFAULT tag=0x0 rxBytes=0 rxPackets=0 txBytes=58 txPackets=1 operations=0
D/Tethering( 193): MasterInitialState.processMessage what=3
D/CMStats ( 382): Prompting user for opt-in.
I/ActivityManager( 193): Displayed com.signove.health.servicetest/.HealthServiceTestActivity: +238ms
D/OpenGLRenderer( 363): Flushing caches (mode 1)
D/OpenGLRenderer( 363): Flushing caches (mode 0)
W/InputManagerService( 193): Starting input on non-focused client com.android.internal.view.IInputMethodClient$Stub$Proxy@40f498a8 (uid=10005 pid=363)
D/AudioHardware( 137): AudioHardware pcm playback is going to standby.
V/AudioHardware( 137): closeMixer_l() mMixerOpenCnt: 1
D/AudioHardware( 137): closePcmOut_l() mPcmOpenCnt: 1
D/AlarmManagerService( 193): Kernel timezone updated to -330 minutes west of GMT
D/SystemClock( 347): Setting time of day to sec=1365428706
V/AlarmClock( 5253): AlarmInitReceiver finished
D/ConnectivityService( 193): ConnectivityChange for mobile: CONNECTED/CONNECTED
W/NetworkStats( 193): dropping UID delta from unknown iface: iface=pdp0 uid=0 set=DEFAULT tag=0x0 rxBytes=0 rxPackets=0 txBytes=58 txPackets=1 operations=0
D/Tethering( 193): MasterInitialState.processMessage what=3
D/CMStats ( 382): Prompting user for opt-in.
Elvis Pfutzenreuter
Apr 9, 2013, 10:32:13 AM4/9/13
to antido...@googlegroups.com
Should not be the software. It is something related to Nonin pairing.
Did you try to take the cells out and back in?
> --
> You received this message because you are subscribed to the Google Groups "Antidote: open-source IEEE 11073 stack" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to antidote-lib...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
Did you try to take the cells out and back in?
> You received this message because you are subscribed to the Google Groups "Antidote: open-source IEEE 11073 stack" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to antidote-lib...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
Prashant Kumar
Apr 10, 2013, 12:56:31 AM4/10/13
to antido...@googlegroups.com
Thanks Elvis for the reply.
I tried removing the cells and putting in after some time.I tried some 30 times but still it is the same log i am getting.
I am thinking there may be problem with Nonin Oximeter Bluetooth but when i try with My Fitness Companion Android app ,it is working fine .What's the reason that it is working with MyFitness Companion ??
I tried removing the cells and putting in after some time.I tried some 30 times but still it is the same log i am getting.
I am thinking there may be problem with Nonin Oximeter Bluetooth but when i try with My Fitness Companion Android app ,it is working fine .What's the reason that it is working with MyFitness Companion ??
Elvis Pfutzenreuter
Apr 10, 2013, 9:02:37 AM4/10/13
to antido...@googlegroups.com
Really strange. Does the MyFitness use HDP? Are you using Android 4.2.x?
Prashant Kumar
Apr 11, 2013, 2:37:21 AM4/11/13
to antido...@googlegroups.com
Thats my doubt actualy........Is it using HDP or SPP i dont know...
But continuous readings are coming from nonin oximeter.Iam using Android ICS 4.04..........
Is there any method to find whether it is using HDP or not ?
Elvis Pfutzenreuter
Apr 11, 2013, 9:55:15 AM4/11/13
to antido...@googlegroups.com
Running a scanner, or hcidump at phone.
Federico Veronesi
Aug 29, 2013, 3:25:47 AM8/29/13
to antido...@googlegroups.com
Hi,
this thread its quite old however after a bit o struggling I found the solution for this kind of problem with Nonin oximeter not connecting and not sending anything to healthd.
Nonin oxymeter has several operating mode. If for example you connect it to MyFitnessCompanion it enters in a SPP mode (I think 13) that does not tries to reconnect and it is not going to change till another mode is requested.
The only solution I found was to send manually through bluetooth the comand to change mode.On linux using PyBluez is quite simple:
from bluetooth import *
import binascii
server_address ="00:1C:05:00:9D:7B"
port = 1
sock = BluetoothSocket( RFCOMM )
sock.connect((server_address, port))
print "connected to Nonin 9560, sending request..."
stx=binascii.a2b_hex("02")
# 02 70 04 02 0D 00 83 03 look at nonin technical docs to know which command to send
# or 02 70 04 02 0D 01 84 03
opcode70=binascii.a2b_hex("70")
b3=binascii.a2b_hex("04")
b4=binascii.a2b_hex("02")#
b5=binascii.a2b_hex("0D")#
b6=binascii.a2b_hex("01")#
b7=binascii.a2b_hex("84")#
b8=binascii.a2b_hex("03")#
ChageFormat=stx+opcode70+b3+b4+b5+b6+b7+b8
sock.send(ChageFormat)
I hope it may help.
Federico
this thread its quite old however after a bit o struggling I found the solution for this kind of problem with Nonin oximeter not connecting and not sending anything to healthd.
Nonin oxymeter has several operating mode. If for example you connect it to MyFitnessCompanion it enters in a SPP mode (I think 13) that does not tries to reconnect and it is not going to change till another mode is requested.
The only solution I found was to send manually through bluetooth the comand to change mode.On linux using PyBluez is quite simple:
from bluetooth import *
import binascii
server_address ="00:1C:05:00:9D:7B"
port = 1
sock = BluetoothSocket( RFCOMM )
sock.connect((server_address, port))
print "connected to Nonin 9560, sending request..."
stx=binascii.a2b_hex("02")
# 02 70 04 02 0D 00 83 03 look at nonin technical docs to know which command to send
# or 02 70 04 02 0D 01 84 03
opcode70=binascii.a2b_hex("70")
b3=binascii.a2b_hex("04")
b4=binascii.a2b_hex("02")#
b5=binascii.a2b_hex("0D")#
b6=binascii.a2b_hex("01")#
b7=binascii.a2b_hex("84")#
b8=binascii.a2b_hex("03")#
ChageFormat=stx+opcode70+b3+b4+b5+b6+b7+b8
sock.send(ChageFormat)
I hope it may help.
Federico
Chaganti Suresh Naidu
Jun 2, 2015, 3:32:01 AM6/2/15
to antido...@googlegroups.com
Dear Wong Liong Hung
Thanks for ur support on this mailing list,
I need a help on the usage of antidote sample programs
currently I am trying to use OMRAN-708 Bluetooth enabled device, and I want to integrate to my platform where I use the following
1. Using Linux box with kernel version 3.x ( using Bluetooth dongle )
2. using bluez version 4.99
3. installed dbus as well.
Here I am trying to run healthd test application server, wwhere I tried to upload the data from Blood pressure monitoring device.
I manually paired the device and my Linux box with Bluetooth dongle.
pairing successful I can see the OK status on the omran device.
later when I run the Healthd program and try to upload the data, After trying the few seconds the timeout and shows ERR on the Bluetooth device.
I want your help to how I can manage to communicate through the bluez hdp profile using the sample healthd service
please let me know is there any package I am missing to be installed.I am new to this bluez usage
I even try to run the sample_bt_agent but still they communicate
I executed, the healthd I got the following output.
sudo ./healthd --bluez
DEBUG <srv_object_class_init in healthd_service.c:1760>
DEBUG <manager_init in manager.c:158> Manager Initialization
DEBUG <ext_configurations_load_configurations in extconfigurations.c:274> Zero-sized ext config buffer
DEBUG <manager_start in manager.c:409> Manager starting...
DEBUG <init in plugin_bluez.c:1211> Starting BlueZ link...
DEBUG <connect_adapter in plugin_bluez.c:805> connecting adapter: /org/bluez/13102/hci0
DEBUG <connect_adapter in plugin_bluez.c:844> Getting known devices list
DEBUG <connect_device_signals in plugin_bluez.c:711> device to be connected: /org/bluez/13102/hci0/dev_00_22_58_35_C0_12
DEBUG <get_device_addr in plugin_bluez.c:283> Device address is 00:22:58:35:C0:12
DEBUG <srv_object_class_init in healthd_service.c:1760>
DEBUG <manager_init in manager.c:158> Manager Initialization
DEBUG <ext_configurations_load_configurations in extconfigurations.c:274> Zero-sized ext config buffer
DEBUG <manager_start in manager.c:409> Manager starting...
DEBUG <init in plugin_bluez.c:1211> Starting BlueZ link...
DEBUG <connect_adapter in plugin_bluez.c:805> connecting adapter: /org/bluez/13102/hci0
DEBUG <connect_adapter in plugin_bluez.c:844> Getting known devices list
DEBUG <connect_device_signals in plugin_bluez.c:711> device to be connected: /org/bluez/13102/hci0/dev_00_22_58_35_C0_12
DEBUG <get_device_addr in plugin_bluez.c:283> Device address is 00:22:58:35:C0:12
00:22:58:35:C0:12 is my Bluetooth enabled BPM device.
I executed sample_bt_agent .. output is ...
IEEE 11073 sample agent
DEBUG <agent_init in agent.c:135> Agent Initialization
DEBUG <agent_start in agent.c:342> Agent starting...
DEBUG <init in plugin_bluez.c:1211> Starting BlueZ link...
DEBUG <connect_adapter in plugin_bluez.c:805> connecting adapter: /org/bluez/13102/hci0
DEBUG <connect_adapter in plugin_bluez.c:844> Getting known devices list
DEBUG <connect_device_signals in plugin_bluez.c:711> device to be connected: /org/bluez/13102/hci0/dev_00_22_58_35_C0_12
DEBUG <get_device_addr in plugin_bluez.c:283> Device address is 00:22:58:35:C0:12
DEBUG <create_health_application in plugin_bluez.c:1028> Created health application: /org/bluez/health_app_9
Main loop started
DEBUG <plugin_bluez_connect_cb in plugin_bluez.c:1450> connection initiation error: Error getting remote SDP records
DEBUG <agent_init in agent.c:135> Agent Initialization
DEBUG <agent_start in agent.c:342> Agent starting...
DEBUG <init in plugin_bluez.c:1211> Starting BlueZ link...
DEBUG <connect_adapter in plugin_bluez.c:805> connecting adapter: /org/bluez/13102/hci0
DEBUG <connect_adapter in plugin_bluez.c:844> Getting known devices list
DEBUG <connect_device_signals in plugin_bluez.c:711> device to be connected: /org/bluez/13102/hci0/dev_00_22_58_35_C0_12
DEBUG <get_device_addr in plugin_bluez.c:283> Device address is 00:22:58:35:C0:12
DEBUG <create_health_application in plugin_bluez.c:1028> Created health application: /org/bluez/health_app_9
Main loop started
DEBUG <plugin_bluez_connect_cb in plugin_bluez.c:1450> connection initiation error: Error getting remote SDP records
======================================================
After executing the test_healthd.py
Starting...
Configuring...
Waiting.
Configuring...
Waiting.
========================================================
at the ./healthd terminal I see the following lines
DEBUG <srv_configurepassive in healthd_service.c:588> Agent: /com/signove/health/agent/18404
DEBUG <srv_configurepassive in healthd_service.c:602> Data type: 1004
DEBUG <srv_configurepassive in healthd_service.c:602> Data type: 1007
DEBUG <srv_configurepassive in healthd_service.c:602> Data type: 1029
DEBUG <srv_configurepassive in healthd_service.c:602> Data type: 100f
DEBUG <get_agent_proxy in healthd_service.c:795> get_agent_proxy
DEBUG <create_health_application in plugin_bluez.c:1028> Created health application: /org/bluez/health_app_14
DEBUG <create_health_application in plugin_bluez.c:1028> Created health application: /org/bluez/health_app_15
DEBUG <create_health_application in plugin_bluez.c:1028> Created health application: /org/bluez/health_app_16
DEBUG <create_health_application in plugin_bluez.c:1028> Created health application: /org/bluez/health_app_17
Reply all
Reply to author
Forward
0 new messages