Strictly necessary cookies are on by default and cannot be turned off. Functional, Performance and Tracking/targeting/sharing cookies can be turned on below based on your preferences (this banner will remain available for you to accept cookies). You may change your cookie settings by deleting cookies from your browser. Then this banner will appear again. You can learn more details about cookies HERE.
Strictly necessary (always on)
Functional, Performance and Tracking/targeting/sharing (default off)
I'm having an issue with Bluetooth transmission where my program is erroring out after the 20th iteration. I found out the setting max_attr_len in the file wiced_app_cfg.c.
The default value is 20. when changing this setting, there is no change in the behavior of my code. on the 20th iteration the system is throwing WICED_BT_GATT_CONGESTED oncefollowed by WICED_BT_GATT_INTERNAL_ERROR for the rest of the loop.
I noticed that in the comment section there is a reference to gki_cfg which I am not able to locate in any of the files.
Max attribute length / Max MTU size decides on how much data can be send on single transmission . In your case it's not about the data size, its about how frequently you are sending the data . I think that was expected behavior. Too many Notification data cannot be sent quickly enough.
You need to monitor congestion event(congested or cleared). If congested, you need to stop sending and wait congestion clear.
In application layer,
Can you try a work around. Application should do two things