Radio InActive Notification

RE: Radio InActive Notification

Petter Myhre — Mon, 25 Jul 2016 12:02:03 GMT

Unfortunately, there is no way to disable the delay for the first one.

RE: Radio InActive Notification

FA — Thu, 21 Jul 2016 03:37:42 GMT

About the 0-10msec random delay, I knew that, but I was thinking it only happens between advertisements and the first one always happen immediately. As you said my tests show that the delay is there even for the very first packet. Is there any way to disable that at least for the first one?

RE: Radio InActive Notification

FA — Thu, 21 Jul 2016 03:32:27 GMT

Thanks Petter! With your code in my project the results were the same. However, as a stand alone code it was working fine. So, I decided to re-build my program around the working notification and see which block make it go wrong (and that's why it took so long!) Finally, here is what I think is happening: Before starting the advertisement and notification, I'm running scanning in timeslot. When I close it, it will generate an inactive notification and in the handler I'm turning off advertisement (as it's needed in the program). I can see a delay of 20msec or 120msec between disabling timeslot scanning and its inactive notification (depending on where initializing notification). During this time it seems the radio can not advertise and waits for timeslot to be closed, and as I stop advertisement in the handler, the first adv never happens, and this is fine for me.

RE: Radio InActive Notification

Petter Myhre — Fri, 15 Jul 2016 11:28:12 GMT

I tested this with S110 v8 and S130 v1 and SDK 9.

I'm not able to reproduce your first problem. Here is my project, see if you experience the same with it.

The interrupt is set immidiately after TX/RX. The actual radio transmission of the advertisment (3 packets on 3 channels) only takes around 2.5 ms, but there is a random delay between 0 and 10 ms, and with some preprocessing 5-15 ms between sd_ble_gap_adv_start() and the end of the first advertising is expected.