Hello,
The release notes from the 6.10 SDK show TI154STACK-3903 as a fixed issue.
Can you explain what exactly was the issue?
best regards,
Marijn
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Hello,
The release notes from the 6.10 SDK show TI154STACK-3903 as a fixed issue.
Can you explain what exactly was the issue?
best regards,
Marijn
Hi Marjin,
TI154STACK-3903 Reduced beacon interval offset in beacon mode.
The offset mentioned is the offset between when a beacon should be sent according to the beacon interval, and when it is actually transmitted over the air. For SDK 6.10 this offset is smaller than it used to be. (10s of us instead of 100s of us.)
Cheers,
Marie H
Hi Marie,
Thanks, I was asking because we have devices regularly missing beacons and going into resync. Could this be a fix for that? I'm not sure what time period the receiver is on to receive a beacon but we have a relatively low beacon interval (1.2sec) and if this offset could cause the beacon to be missed.
thanks,
Marijn
Hi Marjin,
If you're using beacon interval of 1.2 s, it sounds like you're using beacon order 6. For BO = 6 the offset has gone from around 35 us to 7 us (depending on device and PHY). Both of these offsets are well within the spec and I would not expect any trouble for the peer device to receive these beacons.
You can try to use a logic analyzer on the RF pins to check what the offset is in your case.
Cheers,
Marie H