This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

ATT MTU > 20 and DLE enabled - central write issue

SDK12 and SD 132 v3.

I have my code working for HVX from the peripheral. I can HVX send up to 80 bytes on one characteristic in one call (ATT MTU was set to 83 and DLE negotiated for 83 as well [also tried 87]) and I see it arrive on the central no problem. When I do a write without response, on the central, of anything greater than 20 I get a successful return code from the write API and then nothing. The peripheral never gets an event for the write. Is there something that I am missing here? I followed the setup from the DLE.zip file that was posted in another thread and I do see the MTU and the DLE events come back so I know that the negotiation finished before I sent anything.

Parents
  • the problem is that the product has multiple layers of security and app level authentication that gets in the way of debug. The problem actually fixed it self. A file must not have recompiled when I made a change in the Eclipse project. After cleaning everything and rebuilding on one of the steps things just magically fixed themselves. It was too weird only working in one direction like that to not be an evironment problem. Tests are running well now against the code so the transport is solid with the long MTU. - Thanks!

Reply
  • the problem is that the product has multiple layers of security and app level authentication that gets in the way of debug. The problem actually fixed it self. A file must not have recompiled when I made a change in the Eclipse project. After cleaning everything and rebuilding on one of the steps things just magically fixed themselves. It was too weird only working in one direction like that to not be an evironment problem. Tests are running well now against the code so the transport is solid with the long MTU. - Thanks!

Children
No Data
Related