Remote User Terminated Connection

1,154 views
Skip to first unread message

Jim Horner

unread,
Dec 27, 2012, 12:58:58 AM12/27/12
to antido...@googlegroups.com

I am using the tag 2.0.5 from gitorious. I used the script create_deb.sh and installed the packages. I've tried the following on a test laptop using ubuntu 12.04 server (32-bit) with the same problem (so it must be something I'm doing wrong).

My main desktop 

lsb_release -a
LSB Version:    core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch
Distributor ID: Ubuntu
Description:    Ubuntu 12.10
Release:        12.10
Codename:       quantal

I pair the device, Nonin 9560BT, to my desktop using

$ bluez-simple-agent hci0 [btaddr]
$ bluez-test-device trusted [btaddr] yes

I have 3 terminal windows open and I run the following in this sequence/order as myself
$ healthd
$ test_healthd.py (executed from the src directory)
$ sudo hcidump hci0

I've tried various combinations of running as root (sudo), pairing while healthd is running, all of the combinations work the same and I see device removed, device created debug statements... what I am missing is the data from the device. Below in the hcidump output I see the request to disconnect before I see anything that resembles data. Any help is appreciated. 

Thanks, Jim

healthd output
DEBUG   <srv_object_class_init in healthd_service.c:1800>  
DEBUG   <manager_init in manager.c:159> Manager Initialization
DEBUG   <ext_configurations_load_configurations in extconfigurations.c:275> Zero-sized ext config buffer
DEBUG   <manager_start in manager.c:410> Manager starting...
DEBUG   <init in plugin_bluez.c:1211> Starting BlueZ link...
DEBUG   <connect_adapter in plugin_bluez.c:805> connecting adapter: /org/bluez/1360/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/1360/hci0/dev_40_FC_89_51_13_B5
DEBUG   <get_device_addr in plugin_bluez.c:283>         Device address is 40:FC:89:51:13:B5
DEBUG   <connect_device_signals in plugin_bluez.c:711> device to be connected: /org/bluez/1360/hci0/dev_00_1C_05_00_8E_90
DEBUG   <get_device_addr in plugin_bluez.c:283>         Device address is 00:1C:05:00:8E:90
DEBUG   <srv_configurepassive in healthd_service.c:590> Agent: /com/signove/health/agent/7117
DEBUG   <srv_configurepassive in healthd_service.c:604> Data type: 1004
DEBUG   <srv_configurepassive in healthd_service.c:604> Data type: 1007
DEBUG   <srv_configurepassive in healthd_service.c:604> Data type: 1029
DEBUG   <srv_configurepassive in healthd_service.c:604> Data type: 100f
DEBUG   <get_agent_proxy in healthd_service.c:797> get_agent_proxy
DEBUG   <create_health_application in plugin_bluez.c:1028> Created health application: /org/bluez/health_app_5
DEBUG   <create_health_application in plugin_bluez.c:1028> Created health application: /org/bluez/health_app_6
DEBUG   <create_health_application in plugin_bluez.c:1028> Created health application: /org/bluez/health_app_7
DEBUG   <create_health_application in plugin_bluez.c:1028> Created health application: /org/bluez/health_app_8

test_healthd.py output
Starting...
Configuring...
Waiting...

hcidump output
< HCI Command: Create Connection (0x01|0x0005) plen 13
    bdaddr 00:1C:05:00:8E:90 ptype 0xcc18 rswitch 0x01 clkoffset 0x0000
    Packet type: DM1 DM3 DM5 DH1 DH3 DH5 
> HCI Event: Command Status (0x0f) plen 4
    Create Connection (0x01|0x0005) status 0x00 ncmd 1
< HCI Command: Read RSSI (0x05|0x0005) plen 2
    handle 43
> HCI Event: Command Complete (0x0e) plen 7
    Read RSSI (0x05|0x0005) ncmd 1
    status 0x00 handle 43 rssi 0
> HCI Event: Connect Complete (0x03) plen 11
    status 0x00 handle 42 bdaddr 00:1C:05:00:8E:90 type ACL encrypt 0x00
< HCI Command: Read Remote Supported Features (0x01|0x001b) plen 2
    handle 42
> HCI Event: Command Status (0x0f) plen 4
    Read Remote Supported Features (0x01|0x001b) status 0x00 ncmd 0
> HCI Event: Max Slots Change (0x1b) plen 3
    handle 42 slots 5
> HCI Event: Command Status (0x0f) plen 4
    Unknown (0x00|0x0000) status 0x00 ncmd 1
> HCI Event: Read Remote Supported Features (0x0b) plen 11
    status 0x00 handle 42
    Features: 0xff 0xeb 0x8d 0xf8 0x1b 0x08 0x00 0x00
< HCI Command: Remote Name Request (0x01|0x0019) plen 10
    bdaddr 00:1C:05:00:8E:90 mode 2 clkoffset 0x0000
< ACL data: handle 42 flags 0x02 dlen 10
    L2CAP(s): Info req: type 2
> HCI Event: Command Status (0x0f) plen 4
    Remote Name Request (0x01|0x0019) status 0x00 ncmd 1
> ACL data: handle 42 flags 0x02 dlen 10
    L2CAP(s): Info req: type 2
< ACL data: handle 42 flags 0x02 dlen 16
    L2CAP(s): Info rsp: type 2 result 0
      Extended feature mask 0x00b8
        Enhanced Retransmission mode
        Streaming mode
        FCS Option
        Fixed Channels
> HCI Event: Number of Completed Packets (0x13) plen 5
    handle 42 packets 1
> HCI Event: Number of Completed Packets (0x13) plen 5
    handle 42 packets 1
> ACL data: handle 42 flags 0x02 dlen 16
    L2CAP(s): Info rsp: type 2 result 0
      Extended feature mask 0x0038
        Enhanced Retransmission mode
        Streaming mode
        FCS Option
< ACL data: handle 42 flags 0x02 dlen 12
    L2CAP(s): Connect req: psm 1 scid 0x0040
> HCI Event: Number of Completed Packets (0x13) plen 5
    handle 42 packets 1
> ACL data: handle 42 flags 0x02 dlen 16
    L2CAP(s): Connect rsp: dcid 0x0042 scid 0x0040 result 0 status 0
      Connection successful
< ACL data: handle 42 flags 0x02 dlen 23
    L2CAP(s): Config req: dcid 0x0042 flags 0x00 clen 11
      RFC 0x00 (Basic) 
> HCI Event: Remote Name Req Complete (0x07) plen 255
    status 0x00 bdaddr 00:1C:05:00:8E:90 name 'Nonin_Medical_Inc._465129'
> HCI Event: Number of Completed Packets (0x13) plen 5
    handle 42 packets 1
> ACL data: handle 42 flags 0x02 dlen 18
    L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 4
      MTU 250 
> ACL data: handle 42 flags 0x02 dlen 20
    L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 8
      MTU 250 
      FlushTO 65535 
< ACL data: handle 42 flags 0x02 dlen 18
    L2CAP(s): Config rsp: scid 0x0042 flags 0x00 result 0 clen 4
      MTU 250 
< ACL data: handle 42 flags 0x02 dlen 24
    L2CAP(d): cid 0x0042 len 20 [psm 1]
        SDP SSA Req: tid 0x0 len 0xf
          pat uuid-16 0x1401
          max 65535
          aid(s) 0x0000 - 0xffff
          cont 00
> HCI Event: Number of Completed Packets (0x13) plen 5
    handle 42 packets 1
> HCI Event: Number of Completed Packets (0x13) plen 5
    handle 42 packets 1
> ACL data: handle 42 flags 0x02 dlen 159
    L2CAP(d): cid 0x0040 len 155 [psm 1]
        SDP SSA Rsp: tid 0x0 len 0x96
          count 147
          record #0
              aid 0x0000 (SrvRecHndl)
                 uint 0x10016
              aid 0x0001 (SrvClassIDList)
                 < uuid-16 0x1401 >
              aid 0x0004 (ProtocolDescList)
                 < < uuid-16 0x0100 (L2CAP) uint 0x1001 > <
                 uuid-16 0x001e uint 0x100 > >
              aid 0x0006 (LangBaseAttrIDList)
                 < uint 0x656e uint 0x6a uint 0x100 >
              aid 0x0009 (BTProfileDescList)
                 < < uuid-16 0x1400 uint 0x100 > >
              aid 0x000d (AdditionalProtocolDescLists)
                 < < < uuid-16 0x0100 (L2CAP) uint 0x1003 > < uuid-16 0x001f > > >
              aid 0x0100 (SrvName)
                 str "Nonin Oximeter"
              aid 0x0200 (VersionNumList)
                 < < uint 0x1 uint 0x1004 uint 0x0 str "Nonin Oximeter" > >
              aid 0x0301 (SuppDataStoresList)
                 uint 0x1
              aid 0x0302 (unknown)
                 uint 0x18
          cont 00
< HCI Command: Read RSSI (0x05|0x0005) plen 2
    handle 43
> HCI Event: Command Complete (0x0e) plen 7
    Read RSSI (0x05|0x0005) ncmd 1
    status 0x00 handle 43 rssi 0
< HCI Command: Read RSSI (0x05|0x0005) plen 2
    handle 43
> HCI Event: Command Complete (0x0e) plen 7
    Read RSSI (0x05|0x0005) ncmd 1
    status 0x00 handle 43 rssi 0
< ACL data: handle 42 flags 0x02 dlen 12
    L2CAP(s): Disconn req: dcid 0x0042 scid 0x0040
> HCI Event: Number of Completed Packets (0x13) plen 5
    handle 42 packets 1
> ACL data: handle 42 flags 0x02 dlen 12
    L2CAP(s): Disconn rsp: dcid 0x0042 scid 0x0040
< HCI Command: Read RSSI (0x05|0x0005) plen 2
    handle 43
> HCI Event: Command Complete (0x0e) plen 7
    Read RSSI (0x05|0x0005) ncmd 1
    status 0x00 handle 43 rssi 0
< HCI Command: Read RSSI (0x05|0x0005) plen 2
    handle 43
> HCI Event: Command Complete (0x0e) plen 7
    Read RSSI (0x05|0x0005) ncmd 1
    status 0x00 handle 43 rssi 0
< HCI Command: Disconnect (0x01|0x0006) plen 3
    handle 42 reason 0x13
    Reason: Remote User Terminated Connection
> HCI Event: Command Status (0x0f) plen 4
    Disconnect (0x01|0x0006) status 0x00 ncmd 1
> HCI Event: Disconn Complete (0x05) plen 4
    status 0x00 handle 42 reason 0x16
    Reason: Connection Terminated by Local Host

David Cornejo

unread,
Dec 27, 2012, 1:48:13 PM12/27/12
to antido...@googlegroups.com
Near as I can tell, the Nonin only gives a single sample in this mode.  I don't know if it can be reconfigured to provide continuous samples.  In the end, we abandoned this track and used the Nonin native modes.

The 9560BT in our experience is also a battery hog, so continuous monitoring is less usable than it could be.

dave c

Jim Horner

unread,
Dec 27, 2012, 2:13:12 PM12/27/12
to antido...@googlegroups.com

Thanks. I'd be happy to get just the one data point. I found a post in this group which seems to indicate an issue with the Nonin and the kernel. I've been so fixated on the oximeter that I forgot that I have a scale and blood pressure cuff which work just fine in my configuration... had I tried them 4 days ago my blood pressure would be lower. For the Nonin I'm going to try going backwards to 11.10/Natty and trying again. I appreciate your experience tidbit, with respect to the "native" modes, that's something I'll research. Mahalo, Jim

David Cornejo

unread,
Dec 27, 2012, 2:18:18 PM12/27/12
to antido...@googlegroups.com
I think somewhere on this list I published my how-to with, I think, 12.04, you might try searching the archives

Jim Horner

unread,
Dec 27, 2012, 3:25:11 PM12/27/12
to antido...@googlegroups.com

Absolutely I have that post starred!! I was not able to get 12.04 to work but I'm also using v2.0 which that post states "(didn't have as good luck with 2.0 released version)". I actually did not have good luck getting v1.1 to compile (I think I got it eventually by removing a -W from CFLAGS); admittedly I've been through too many laptops, dongles, version combinations and variations to keep it all straight. Now that I have something working, a baseline of sorts, I can start to revisit combinations. It appears that this group has had more success with 2.6 kernels which is my reasoning for going backwards.

David Cornejo

unread,
Dec 27, 2012, 3:38:43 PM12/27/12
to antido...@googlegroups.com
Sorry it didn't help more, but please post if you get it working, thanks!

Jim Horner

unread,
Dec 27, 2012, 10:53:56 PM12/27/12
to antido...@googlegroups.com

I just did a search for SPP and found another one of your posts. All of your posts are helpful, I just did not find them in the right order or at the right time because of my lack of knowledge. Having said that, I was able to get the oximeter to work with 11.10/Natty, kernel 2.6.38. Afterwards I went back to my desktop and the oximeter worked with 12.10/Quantal. So there never really was a problem, per se, I guess. My thought is the oximeter was stuck in some mode, perhaps SPP or ???. I don't know. The 2.6 series kernel apparently does something that the 3.2 does not.

Prashant Kumar

unread,
Mar 5, 2013, 4:25:59 AM3/5/13
to antido...@googlegroups.com
You were able to get the oximeter working with 11.10 and 12.10 ubuntu versions...........means how ??....
You used  ./healthd and ./test_healthd.py ....Am i correct ?
Did u get multiple reading or only one measurement.
Did u tried with android mobile ???

Reply all
Reply to author
Forward
0 new messages