advertising interval

RE: advertising interval

roger.k — Tue, 12 Dec 2017 23:25:15 GMT

Thank you very much for your help.

RE: advertising interval

endnode — Tue, 12 Dec 2017 09:38:08 GMT

No Roger, that doesn't make sense. There is no connection if there is no ADV_XXX packet (because CONNECT_REQ must be issued on the same channel exactly in 150us after connectable ADV_XXX packet is sent) and if your device isn't scanning it doesn't know when to connect (misses that 150us window).

RE: advertising interval

roger.k — Tue, 12 Dec 2017 09:32:21 GMT

I have one more question. If central doesn't scan and it tyries to connect to my peripheral's pear address directly, is it possible? I hope your help.

RE: advertising interval

roger.k — Tue, 12 Dec 2017 09:26:37 GMT

Thanks a lot. Let me check.

RE: advertising interval

endnode — Tue, 12 Dec 2017 09:11:24 GMT

Standard GAP compliant device which uses certified BLE stack (such as Nordic Soft Device) should add some jitter to advertising interval so it's normal that you see 400ms +- few percent. But if you see longer gaps (e.g. few seconds) then either your scanner cannot run on 100% duty cycle or there is some serious problem on advertiser's FW. Can you test it with simple mobile BLE app like nRF5 Connect for Android or iOS? These typically display row of captured advertising packets and if there are unusual gaps you can spot them easily.