DA1468x

When designing MESH device, it is possible for an element to contain multiple models inside.

For example, we can register a generic level server and a level client into an element, and it is so-called "control model".

But, in current SDK 1.6.1, only one model can call its callback, in my case, MS_ACCESS_GENERIC_LEVEL_STATUS_OPCODE is received in level server, but not in level client.

Is this behaviour by design, or bug?

嗨,团队,

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.

Hi, teams.

I am analyzing MESH SDK codes, and build my own MESH application on SDK base.

There are very strange implementations in several models.

For example, in Generic Level Server Model, STATUS message is sent to client by the following code.

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 Opcode0x00A000D2

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

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