Notify stops working after a second connect

Mikael Alexiusson1

I have some notify parameters set up. They work fine for the first connection, but when i disconnect and connects again the notifys are not sent. Write/read on other parameters work but the notify is not sent?

Any ideas on what to check? Any known problems?

When debugging I can see that the setParameter is called and returns SUCCESS but the readAttrCB is never called as it is on the first connection.

over 10 years ago

0 Steeve Sinigaglia over 10 years ago

Intellectual 805 points

Hello,
Do you have hardcoded a connection handle (like 0x0001) in your notification?

0 Mikael Alexiusson1 over 10 years ago in reply to Steeve Sinigaglia

Intellectual 740 points

I may have... ;)
In AddService i have added this code as seen in an example:
//AUTO Notification
hkvInformationProfileSwInfoConfig[0].connHandle = 0x0000;
hkvInformationProfileSwInfoConfig[0].value = 0x01;

Maybe not the best idea! How do you suggest to handle this instead?

0 Steeve Sinigaglia over 10 years ago in reply to Mikael Alexiusson1

Intellectual 805 points

I did the same error before.. ;)

Just check the exemple of simpleProfilChar 4 !

In addService you have to do :

// Allocate Client Characteristic Configuration table
  simpleProfileChar4Config = (gattCharCfg_t *)ICall_malloc( sizeof(gattCharCfg_t) *
                                                            linkDBNumConns );
  if ( simpleProfileChar4Config == NULL )
  {     
    return ( bleMemAllocError );
  }

And in SetParameter :

    case SIMPLEPROFILE_CHAR4:
      if ( len == sizeof ( uint8 ) ) 
      {
        simpleProfileChar4 = *((uint8*)value);
        
        // See if Notification has been enabled
        GATTServApp_ProcessCharCfg( simpleProfileChar4Config, &simpleProfileChar4, FALSE,
                                    simpleProfileAttrTbl, GATT_NUM_ATTRS( simpleProfileAttrTbl ),
                                    INVALID_TASK_ID, simpleProfile_ReadAttrCB );
      }
      else
      {
        ret = bleInvalidRange;
      }
      break;

Don't forget in writeAttrCB to add :

      case GATT_CLIENT_CHAR_CFG_UUID:
        status = GATTServApp_ProcessCCCWriteReq( connHandle, pAttr, pValue, len,
                                                 offset, GATT_CLIENT_CFG_NOTIFY );

And this for each characteristic you want notify :)

0 Mikael Alexiusson1 over 10 years ago in reply to Steeve Sinigaglia

Intellectual 740 points

Thanks! That probably solves the problem. I only need to get the android app developers to be able to set the 2902 char.
I already had all the code, but the notfifcation was also added and hardcoded...

0 Steeve Sinigaglia over 10 years ago in reply to Mikael Alexiusson1

Intellectual 805 points

To able to sett 2902 char, you have to use "mBluetoothLeService.setCharacteristicNotification(yourCharacteristic,true);"
mBluetoothLeService it's your class extends Service.
Just follow the developer BLE guide from Android developer for bettter understanding.

Please be sure to mark the thread as answered if your question was answered :)

0 Mikael Alexiusson1 over 10 years ago in reply to Steeve Sinigaglia

Intellectual 740 points

Thanks! It works now! :)

0 Steeve Sinigaglia over 10 years ago in reply to Mikael Alexiusson1

Intellectual 805 points

Glad to help you ! :)
Steeve

Bluetooth®︎

Bluetooth forum

Notify stops working after a second connect