HRM disconection after 1 minute in Windows 8 machine about node-bluetooth-hci-socket HOT 7 CLOSED

Hi @erwinkendo,

Could you please share the full debug log on Windows? As well as the HCI dump capture from Linux (sudo hcidump -t -x).

There might be a non-4 CID type for connection interval that the Linux kernel is handling.

from node-bluetooth-hci-socket.

Hi

Sorry for the delay, here attached are both logs

I do not see anything different after 1 minute of operation (time when the disconnection happens), but hopefully you are better at noticing anything unusual.

Kind regards,
hcidump.txt
outDebugWin.txt

from node-bluetooth-hci-socket.

Just a small update:

Tried using the latest version of all packages, as well as using different adapters and USB ports but it does no seem to improve. Could this be related to the node version I am using? (4.5)

from node-bluetooth-hci-socket.

I have the same issue.

Running node Version 6.6.0 on windows 10, 64 bit.

Last event:

 hci-usb HCI event: 050400400013 +130ms
  hci onSocketData: 04050400400013 +2ms
  hci   event type = 4 +1ms
  hci   sub event type = 5 +1ms
  hci           handle = 64 +0ms
  hci           reason = 19 +1ms

@erwinkendo how do you catch the disconnect?

from node-bluetooth-hci-socket.

Hi @mrothenbuecher , I am using noble-device example for hrm connection

My last event is similar to yours... but the names change for some way:

update measument: 81
  hci-usb ACL Data In: 48200b00070004001b12001651f502 +990ms
  hci onSocketData: 0248200b00070004001b12001651f502 +1ms
  hci   event type = 2 +1ms
  hci           cid = 4 +1ms
  hci           handle = 72 +0ms
  hci           data = 1b12001651f502 +1ms
update measument: 81
  hci-usb HCI event: 05040048003b +478ms
  hci onSocketData: 0405040048003b +1ms
  hci   event type = 4 +1ms
  hci   sub event type = 5 +0ms
  hci           handle = 72 +1ms
  hci           reason = 59 +0ms
disconnected!
  hci set scan enabled - writing: 010c20020001 +3ms
  hci-usb write: 010c20020001 +1ms

Is it normal that the HCI event and other data is not the same for our systems @sandeepmistry ?

from node-bluetooth-hci-socket.

The problem is nothing handles the following messages on Windows:

2016-09-10 21:21:44.061067 > ACL data: handle 33 flags 0x02 dlen 16
    L2CAP(d): cid 0x0005 len 12 [psm 0]
      12 39 08 00 FA 00 90 01 00 00 58 02 

The Linux kernel responds with:

2016-09-10 21:21:44.061134 < ACL data: handle 33 flags 0x00 dlen 10
    L2CAP(d): cid 0x0005 len 6 [psm 0]
      13 39 02 00 00 00 
2016-09-10 21:21:44.061140 < HCI Command: LE Connection Update (0x08|0x0013) plen 14
  21 00 FA 00 90 01 00 00 58 02 00 00 00 00 
2016-09-10 21:21:44.062661 > HCI Event: Command Status (0x0f) plen 4
    LE Connection Update (0x08|0x0013) status 0x00 ncmd 1

There is nothing in noble to handle this event and reply.

Could you please close this issue and open a new one in the noble Github repo?

from node-bluetooth-hci-socket.

Thanks @sandeepmistry

Opened a new issue here

from node-bluetooth-hci-socket.