1 of 1 people found this helpful
1) Did you upgrade the crystal warmup to 5000?
2) Can you do a clean recompilation on SDK 2.2.3 on a Windows 7 (preferred) or 10, 32-bit (preferred), PC environment?
This drifting issue in the advertising frequencies should have been resolved from 2.2.2.
boont thank you for responding.
I should point out that we are using 6S modules which should not be subject to the crystal warmup issue. Having said that we have tried setting the warmup time to 5000 as well as setting it back to 2800 and we have done clean builds repeatedly. These have had no impact on the problem.
We are using Windows 10 and the 32 bit WICED IDE. This is the only software installed on the machine, it was a clean install of the OS then the WICED environment.
I have some suggestions:
1) load the hello_sensor app onto those problematic modules, using sdk223 on your win10 pc. Observe
whether does the issue occur again.
2) since you have access to an SA, you may want to invoke "manufacturing-bluetooth-test-tool (MBT)" to
put the device into test mode and perform Tx test on it. It's available in "Tools" and the app note in "Doc".
And do continue to bump up the crystal warmup to 5000.
From whom are you sourcing your SIP module?