Hi teams,
AFAIK, 1.0规范定义了每个m网格模型odel messages not to be fragmented.
So, when we use SIG-defined model, each message SHOULD NOT be fragmented, if we make a size mistake.
According to the specification, a single packet can deliver 8,9,10 bytes of message data when using 3,2,1 bytes opcode each.
But, when I tested with MS_access_publish() function, packet fragmentation occurs when more than 5,6,7 bytes are in a packet.
In the other word, MESH SDK handles 3 bytes less than specification.
I am strongly suspicious of unpacked structures which is used in message store. I changed them myself, but no effects.
So, I think the mesh library may have the same issues inside.
Please check about this issue.
Keywords:
Device:
Hi firebird,
Looking into this. Will get back asap. Please note our offices are closed during Christmas and so response might be delayed for this query.
Best regards,
LC_Dialog
Awaiting updates...
Hi firebird,
We are working on this question and should be able to provide some update next week. Apologies for the delay, but most of the mesh team is on vacation due to holiday season..
Best regards,
LC_Dialog
Reminding...
Awaiting update...again...