Handle Value Notification variable conn.interval

RE: Handle Value Notification variable conn.interval

samcornell — Tue, 30 Aug 2016 18:07:23 GMT

Thank you very much i will use the start to start delta value then in future

RE: Handle Value Notification variable conn.interval

Hung Bui — Tue, 30 Aug 2016 07:46:52 GMT

@Samcornell: The timestamps are the time the packet arrived on PC (on UART), so it may not be accurate. I would suggest to use the delta time start to start instead. The "end to start" also has an issue, so it's not usable too.

EDIT: I was wrong. "End to Start" is the correct one. It's varied because it's depends on the length of the packet.

So, if the "End to start" of 2 packets of a connection interval is "a" and "b" and the TX time of the packets are "c" and "d", the connection interval will be = a + b +c +d.

RE: Handle Value Notification variable conn.interval

samcornell — Mon, 29 Aug 2016 15:54:11 GMT

Ok I've checked the delta time it is constant: start to start is 14.92 ms, end to start is 14.69 ms. Does this means that the conn. interval is not changing ? But then why in the image attached i have different values if i check the Time Column in Wireshark ?

RE: Handle Value Notification variable conn.interval

Hung Bui — Mon, 29 Aug 2016 12:06:03 GMT

@samcornell: Could you please upload the full sniffer trace ? Could you check the delta time (from start to start) in the Nordic BLE sniffer meta ? EDIT: Start to start is not reliable. My mistake. The "end to start" is the correct one. Calculation needed if we want to find connection interval because "end to start" is dependent on the packet length. See the answer.