Configuration Change Counter is not incrementing

Modified on Fri, 17 Jun, 2016 at 10:00 AM

A good test for this is to send Command 17 with a different message prior to running UALU005. 

The test sends Command 17 with the following contents: 0x000000000000000000000000000000000000000000000000. 


If the test administrator manually sends Command 17 with 0x000000000000000000000000000000000000000000000001 and then runs the test case, the test will change the configuration and then the counter must update during the test.  

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article