Hi Mario,
I was trying to describe my changes in the post, but maybe it'll be clearer if I paste them:
In coordinator example in file mwa_coordinator.c in function App_StartCoordinator I have changed lines 656-659 from:
/* Beacon Order - 0xF = turn off beacons */
pStartReq->beaconOrder = 0x0F;
/* Superframe Order - 0xF = turn off beacons */
pStartReq->superframeOrder = 0x0F;
to:
/* Beacon Order - 0xF = turn off beacons */
pStartReq->beaconOrder = 0x01;
/* Superframe Order - 0xF = turn off beacons */
pStartReq->superframeOrder = 0x01;
I did no more changes.
Unfortunately I don't have the sniffer, yet. But I have set up a third board to perform passive scanning in the loop. Each time it receives a beacon frame it toggles it's LED. I can see that the LED was chaging before the changes above. With the changes above, the LED stays in the initial state. So I assume that the issue is with the controller.
Scan request is a success - otherwise it won't be waiting for ScanConf (I have checked it with a debuger to confirm it).
In the end device I have set up a breakpoint in App_HandleScanActiveConfirm - just at the beginning of the function - line 760 in mwa_end_device.c:
uint8_t panDescListSize = pMsg->msgData.scanCnf.resultListSize;
Vale of pMsg->msgData.scanCnf is:
status = gNoBeacon_c
scanType = gScanModeActive_c
channelPage = gChannelPageId0_c
resultListSize = 0
unscannedChannels = 0
Regards,
Paweł