Glucose Profile/Service version

Ketan the BLE Stack is certified. If the glucose profile is part of the stack, then that too is certified by the SIG.

Hi

Thankyou for the information

I am seeing an issue with GlucoseSensor profile that comes with BLE stack

When i am running PTS testcase, PTS as collector and GlucoseSensor(BLE stack Sample as Sensor), test case verdict is INCONC

When i check event logs i can see, its showing "Not mapped" error and "(deprecated)Client Characteristic Configuration Improperly Configured for this Service"

I have attached cfa logs

Is it possible to find out whats going wrong?

Also i was running TC_CN_BV_01_C testcase in PTS

Regards

Ketan

Hi Joakim

Thankyou for your reply

I am testing with latest GlucoseSensor that comes with BLEv1.3.2

any idea why this error are seen?

Regards

Ketan

Hello Ketan,

That's odd. Have you modified the example project? If so, to what extent?

I'll cress check with the test team to see if there is something obvious going on here.

Best Regards

Joakim

Hi Joakim

Thankyou for your reply

No, i have not modified anything in the code

I have already attached cfa logs.

if you need any more information please let me know

Regrads

Ketan

Hi Joakim

Some extra information:-

PTS configured Glucose measurement and Glucose measurement context for notification (handle 19, 22), configured RACP (handle 26) for indication.

But in GlucoseSensor, glucose_WriteAttrCB(gluservice.c) function returns GLUCOSE_ERR_CCC_CONFIG status, as CCC is not configured for glucose measurement

Regards

Ketan

Hi Ketan,

You are getting an error for writing to the RACP, because bonding is done without MITM (referring to frame#137 in his sniffer trace).  According to the GLS spec GLS_SPEC_V10.pdf, page 9, Table 3.1 Glucose Service characteristic, RACP shall be Writeable with Authentication.  I believe this is the reason why you are getting write error.

Please try with MITM bit set and let me know if it works.

Best Regards

Joakim

Hi Joakim

Thankyou for your investigation

by default in glucoseSensor MITM Mode is already set to TRUE.

Below is the code in glucose.c file

// Default MITM mode (TRUE to require passcode or OOB when pairing)

#define DEFAULT_MITM_MODE                     TRUE

Do i need to change anywhere ? if so please let me know which file.

Thankyou for your help

Regards

Ketan

Hi Joakim

Please let me know, if i need to make any changes anywhere ? if so please let me know which file.

as i mention in my previous post  Default MITM mode is set to TRUE.

Do i need to make changes any where else?

Regards

Ketan

Hi Joakim,

Sorry for trouble, I would be grateful for your response as soon as possible, to my queries, so that I can resolve my problems quickly

Thank you in advance

Best regards

Ketan

Hello Ketan,

Sorry for the slow response. I found out that we used internal test equipment when qualifying the GLS and not the PTS dongle (due to some technical difficulties). I can provide you the test log for the test your are stuck on, if you need the evidence. If so, add me as friend here on e2e and I can send it to you.

Also, feedback from the test team suggests that you are getting an error for writing to the RACP. You are bonding without MITM (referring to frame#137 in his sniffer trace). According to the GLS spec GLS_SPEC_V10.pdf, page 9, Table 3.1 Glucose Service characteristic, RACP shall be Writeable with Authentication. I believe this is the reason why you are getting write error (although the error message is odd).

This test case for reporting the last record works when RACP can be written, basically only after bonding with MITM (passkey is fixed at 019655) is performed. The reason why the passkey is fixed is because with just two buttons on the keyfob, it is difficult to enter in a 6 digit numeric passkey.

Looking at our sample app guide in v1.3.2, we do mention bonding and the fixed passkey (written as 19655 instead of 019655) but don’t explicitly mention MITM requirement. We'll fix that.

Best Regards.

Hi Joakim,

Thank you for the information

Looking at our sample app guide in v1.3.2, we do mention bonding and the fixed passkey (written as 19655 instead of 019655) but don’t explicitly mention MITM requirement. We'll fix that.

So bit confuse, so are you planning to fix the MITM issue, so that it works, with PTS as well.

Waiting for your reply

Regards

Ketan

Hi Joakim

Sorry for trouble, is it possible to reply about my queries

Thankyou for your help and support

Regrads

Ketan