https://devzone.nordicsemi.com/f/nordic-q-a/120678/clock-synchronizationDear Engineer When the advertiser and the scanner enter the connect callback, a timestamp will be printed immediately. The problem now is that the advertiser and the scanner do not seem to enter the connect callback at the same time and there will been-USTelligent Community 13Tue, 22 Apr 2025 08:15:23 GMThttps://devzone.nordicsemi.com/thread/532281?ContentTypeID=1Tue, 22 Apr 2025 08:15:23 GMT137ad170-7792-4731-bb38-c0d22fbe4515:3316c1dc-2cbb-4598-85ba-bbf267b85746Simonr<p>Hi</p> <p>The Sniffer that Susheel is referring to is the nRF Sniffer for Bluetooth LE here:&nbsp;<a href="https://www.nordicsemi.com/Products/Development-tools/nRF-Sniffer-for-Bluetooth-LE">https://www.nordicsemi.com/Products/Development-tools/nRF-Sniffer-for-Bluetooth-LE</a>&nbsp;</p> <p>There is also a documentation page there you can go through to set it up correctly. Regarding the delay Susheel is mentioning, there is some back and forth between the devices before connecting, so 2800µs might be the devices trying to connect.&nbsp;</p> <p>Best regards,</p> <p>Simon</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/531924?ContentTypeID=1Wed, 16 Apr 2025 01:59:03 GMT137ad170-7792-4731-bb38-c0d22fbe4515:134d988a-7a31-4c46-8210-4486a3ca5171zeyuwang<p>Can you describe more clearly the clear sniffer log for this transaction and how I got this log from ncs v2.5.2? And the time it takes for this peripheral to process the connection request, establish the connection and notify its application layer, is this time clearly specified in the Bluetooth manual, or the program in the ncs suite of nordic company requires this fixed time, thank you</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/531642?ContentTypeID=1Mon, 14 Apr 2025 08:06:13 GMT137ad170-7792-4731-bb38-c0d22fbe4515:6c38674b-b2b5-4992-b667-474b36f8aab1Susheel Nuguru<p>The 2800 µs delay&nbsp;might be corresponding to the time taken for the peripheral to process the connection request, establish the connection, and notify its application layer.</p> <p>It might help to get a clear sniffer log of this transactions so that we understand clearly what is going on in air to see if any side of the connection is misbehaving in terms of BLE timings.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/531641?ContentTypeID=1Mon, 14 Apr 2025 07:53:01 GMT137ad170-7792-4731-bb38-c0d22fbe4515:f93f5248-3335-48e6-b0b0-cb1f5235fe6ezeyuwang<p>I need to further supplement the problem I encountered. In the serial port debugging information of the advertiser, I will be given a warning, which is as follows: W: opcode 0x200a status 0x0d</p> <p>The following is the debugging information printed out of my serial port</p> <p>*** Booting nRF Connect SDK v2.5.0 ***<br />Timestamp service provider starting...<br />I: SoftDevice Controller build revision: <br />I: c5 93 ba a9 14 4d 8d 05 |.....M..<br />I: 30 4e 9b 92 d7 71 1e e8 |0N...q..<br />I: aa 02 50 3c |..P&lt; <br />I: HW Platform: Nordic Semiconductor (0x0002)<br />I: HW Variant: nRF52x (0x0002)<br />I: Firmware: Standard Bluetooth controller (0x00) Version 197.47763 Build 2370639017<br />I: Identity: E1:61:76:F1:19:1B (random)<br />I: HCI: version 5.4 (0x0d) revision 0x1102, manufacturer 0x0059<br />I: LMP: version 5.4 (0x0d) subver 0x1102<br />Bluetooth initialized successfully<br />== Advertising Data ==<br /> Type: 0x01, Length: 1, Data: 06 <br /> Type: 0x03, Length: 2, Data: 56 78 <br /> Type: 0x19, Length: 2, Data: 00 07 <br /> Type: 0x09, Length: 11, Data: 54 53 5f 50 72 6f 76 69 64 65 72 <br />W: opcode 0x200a status 0x0d<br />1 0 802825<br />W: opcode 0x200a status 0x0d<br />1 1 10902984<br />W: opcode 0x200a status 0x0d<br />1 2 20992767<br />W: opcode 0x200a status 0x0d<br />1 3 31084533</p><div style="clear:both;"></div>