Problem qualifying battery level service - GATTValue::CreateFields, Failed to assign data to the Field named 'Properties'.

[Ron]

Hi,

I am using NRF51822  SDK12; S130 and trying to qualify Batter level service, So far encountred a problem with  Test Case:     BAS/SR/DES/BV-02-C, the Verdict is INCONCE all other test cases were OK.

I also tried to qualify the nordic GLS example to compare and to find whether the problem is with my implementation, I removed the security protection from the GLS and started a preforming qualification process using the SIG PTS BLE Dongle and the Launch studio, I saw the exact same result, all Items were ok except from BAS/SR/DES/BV-02-C, to my understanding this is the notification support for the BAS:

This is the relevant part BAS (battery level) test plan I created in the Launch studio

to my understanding since we are enabling notification  I should mark support for item 2a/1; but this seems to be the problematic item

this is the log from the PTS software 

+37109 ms

Verdict Description:     GATTValue::AssignData, Cannot be parsed from the specified buffer. Field Name = Properties.

+37109 ms

Error:                   GATTValue::CreateFields, Failed to assign data to the Field named 'Properties'.

+37109 ms

Verdict Description:     GATTValue::CreateFields, Failed to assign data to the Field named 'Properties'.

+37109 ms

Inconclusive:            The data received for 'Client Characteristic Configuration' did not conform to the schema. An invalid number of bytes were received.

+37109 ms

Verdict Description:     The data received for 'Client Characteristic Configuration' did not conform to the schema. An invalid number of bytes were received.

I would appreciate any input on that issue

Thanks!

[Ron]

Hey

I had problems with 2 tests - BAS/SR/DES/BV-01-C and BAS/SR/CN/BV-01-C
For the latter test (CN) I was requested to "Please send notifications for Characteristic 'Battery Level' to the PTS."
To my understanding the central (PTS) should subscribe to notifications in order to receive them so this is unclear to me

Thanks again

 

[Ron]

I figured out that the CN failure was due to Battery level being constant, thus not send notification updates,

Still remains the problem with BAS/SR/DES/BV-02-C, Battery level - client characteristic configuration descriptor:

This is the PTS output tool window summary

- Discover All Characteristics of Service Request completed successfully.
- Discover All Characteristic Descriptors Request completed successfully.
- The IUT successfully returned the Characteristic Properties for Battery Level
- Read Request completed successfully.
- GATTValue::AssignData, Cannot be parsed from the specified buffer. Field Name = Properties.
- GATTValue::CreateFields, Failed to assign data to the Field named 'Properties'.
- The data received for 'Client Characteristic Configuration' did not conform to the schema. An invalid number of bytes were received.
- Connection terminated successfully.
-Final Verdict: INCONC
BAS/SR/DES/BV-02-C finished

Any ideas?

Thanks!

-----------

I understood this test was mandatory due to us using "Notify Battery Level characteristic"

[Ron]

Since there has been some progress since I opened that question, I opened a new question here 
https://devzone.nordicsemi.com/f/nordic-q-a/56206/qualifying-test-case-client-characteristic-configuration-for-bas-with-sig

Basically the problem is that if we do not enable notification we can not read the CCCD, Once we enabled notification once, we can disable it and still be able to read the CCCD

[bjorn-spockeli]

Hi Eran, I sincerly apologize for the late reply. DevZone is shortly staffed during the Christmas and New Years holidays so we're catching up with the backlog. 

The Battery Level in the Nordic SDK does support Battery Level Notification, see https://launchstudio.bluetooth.com/ICSDetails/45222, so  Item 2a/1 should be checked when generating the test plan.  

I see that you've provided more details in the new question so I suggest that we move the discussion there and close this. 

Best regards

Bjørn 

[Ron]

Hey Bjorn

Thanks for the reply and hope you had a great Christmas, 

Yes I have checked it and had a problem with the BAS/SR/DES/BV-02-C test reading to CCCD (0x2902), I could see the same problem myself using the nRF Connect on my SDK12 project and also an earlier SDK8 project, I also had the problem using nordic GLS example of SDK12,  

I have detailed it all in the new question, so as you suggested we will move here - https://devzone.nordicsemi.com/f/nordic-q-a/56206/qualifying-test-case-client-characteristic-configuration-for-bas-with-sig

Thanks!