Device execution stops after particular duration

⚠️
Hi there.. thanks for coming to the forums. Exciting news! we’re now in the process of moving to our new forum platform that will offer better functionality and is contained within the main Dialog website. All posts and accounts have been migrated. We’re now accepting traffic on the new forum only - please POST any new threads at//www.wsdof.com/support. We’ll be fixing bugs / optimising the searching and tagging over the coming days.
2 posts / 0 new
Last post
Mon, 2017-04-17 13:15
#1
wisilica
Offline
Last seen:10 months 2 weeks ago
加入:2015-03-17 08:16
Device execution stops after particular duration

Hi Team,

I am working on a project wherein the device A is initially in the observer mode(scan mode). There is another device B which transmits packets every 1s. A timer of 20 ms duration is started during this time, and if any packets are captured by device A, scan is stopped in this timer callback and received packets are transmitted after hardware encryption. Then after advertisement, scanning is resumed and the process continues. The problem we are facing is, after few seconds, no more packets are being sent from device A. While checking with debugger, the device is still running but advertisement stops after few seconds. Please suggest the possible reasons for the same.

Thanks in advance,
Wisilica

Device:
DA14580
Thu, 2017-04-20 04:11
LT_Dialog(未验证)
Hi Wisilica,

Hi Wisilica,
From the description, there might be several points worth checking from my point of view.

  1. Make sure the flow control is implemented properly. For example, after the scanning is cancelled, application shall receive the message GAPM_CMT_EVT with the operation of GAPM_SCAN_ACTIVE or GAPM_SCAN_PASSIVE, depending on what you've implemented. After that, application sends the command GAPM_START_ADVERTISE_CMD to start the advertising. Same to how you handle the advertising.
  2. The windows of both sides, DeviceA and DeviceB, might not be overlapped thus DeviceA did not receive anything from DeviceB through the air.The windows here are referred to the time span when devices do air activities, e.g. sending or scanning packets and etc. You can probably try a longer scanning first, e.g. 2 seconds.