Mesh SDK

MESH message is fragmented even when it should not be

Mon, 2019-12-23 13:59 -- firebird

Hi teams,

AFAIK, MESH model 1.0 specification defines each model 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.

 

Using Custom OpCode in MESH vendor model

Wed, 2019-12-18 06:33 -- firebird

I am using MESH SDK 1.6.1 and tried to modify vendor model for specific uasge.

When I tried to change Vendor OpCode, the following error occurs and not working.

 

[** ERR **]:[access_api.c]:[833]: [ACCESS] Check FAILED for 3 Octet Opcode 0x00A000D2

 

If I changed back to the original definition, i.e. to 0x00C000D2, it works.

Why this happens, and how can I change this behaviour?

Subscribe to RSS - Mesh SDK