Using Custom OpCode in MESH vendor model

Hi firebird,

I am working on this with our team internally. Will get back to you with a solution asap.

Best,
LC_Dialog

Hi firebird,

The format of the Vendor Opcode is restricted by the Mesh spec. Please refer to section 3.7.3.1 of Mesh_v1_0 spec. In short all vendor specific opcodes have to have the two most significant bits of thethird octet set to 0b11. Please implement an Opcode with this format and check if the error is resolved. Attaching a refernce to the spec below..

3.7.3.1 Operation codes

An operation code (opcode) is an array of octets comprising 1, 2, or 3 octets. The first octet of the opcode determines the number of octets that are part of the opcode.

If the most significant bit of the first octet of the opcode is zero, then the opcode contains a single octet. If the two most significant bits of the first octet are 0b10, then the opcode contains two octets. If the two most significant bits of the first octet are 0b11, then the opcode contains three octets. This is shown in Table 3.43.

用于蓝牙特别兴趣小组def 1-octet操作码ined application opcodes. There are 127 1-octet opcodes that can be defined and allocated by the Bluetooth SIG. Opcode 0x7F is reserved for future possible extension.

The 2-octet opcodes are used for Bluetooth SIG defined application opcodes. There are 16384 2-octet opcodes that can be defined and allocated by the Bluetooth SIG.

The 3-octet opcodes are used for manufacturer-specific opcodes. There are 64 3-octet opcodes available per company identifier, identified using ”x” in Table 3.43, although a company may further sub-class opcodes if desired. The company identifiers are 16-bit values defined by the Bluetooth SIG and are coded into the second and third octets of the 3-octet opcodes, identified using ”z” in Table 3.43. The company- specific opcodes are managed by the company associated with the identifier

Best regards,
LC_Dialog