Problems with Custom model in Mesh App

RE: Problems with Custom model in Mesh App

kc89rst — Thu, 28 Nov 2019 12:59:08 GMT

Hello, what is the status regarding this bug, 'cos it looks it is not fixed in the current version of the SKD (3.2.0)? Can you provide the patch for fixing this in the SDK, or we have to struggle with ugly hacks?

RE: Problems with Custom model in Mesh App

Oleh — Mon, 18 Nov 2019 11:55:09 GMT

Hello Roshan,

we experience the same with the sdk 3.2.0... was is fixed or postponed?

RE: Problems with Custom model in Mesh App

Roshan Rajaratnam — Fri, 26 Oct 2018 13:14:26 GMT

Well the sequence of the messages may not always be in the correct order when it comes to segmented messages, that's something the library handles as the messages may be relayed via different nodes. The order is never guaranteed but this is handled in the lower transport layer of the network. Once or if all messages are received successfully it will be reassembled in the correct order and sent to the upper transport layer and the access layer.

A new ticket would be much appreciated to for a newer question

And don't forget to accept the answer if it helps ;)

Roshan

RE: Problems with Custom model in Mesh App

julian.demicoli — Fri, 26 Oct 2018 11:14:52 GMT

Hi, thank you very much. This could be the reason why the messages arrive in the wrong sequence.

I used a fake Sigmodel opcode to decrease the implementation time just for evaluation of how the app works.

I have one more question. Is the android app also suitable for receiving messages, which have been published by the microcontroller? For example if I want to connect to a sensor which publishes a signal if the sensor values go to dangerous values. (Or should I open a new ticket for it?)

Best regards

Julian Demicoli

RE: Problems with Custom model in Mesh App

Roshan Rajaratnam — Fri, 26 Oct 2018 11:05:58 GMT

Hi there is a bug in the mesh sdk causing the vendor model opcodes to be parsed in the wrong endianness. So all messages sent and received will have in big endian instead of little endian. This bug is fixed internally and probably be out in the next mesh release. The Mesh App is using the correct endianness hence its breaking for you. What you may do is to swap your opcode around in the fw and it will work for you. Also if i'm not mistaken, your opcode seems to be wrong according to the spec. All vendor models must have a 3-octet opcode according to page 93 on the mesh profile spec, so the 2 most significant bits are 0b11.

Anyways like i mentioned this is due to the endianness bug in the mesh sdk as of now. Hope this helps

RE: Problems with Custom model in Mesh App

julian.demicoli — Fri, 26 Oct 2018 10:40:31 GMT

I actually found the problem. I was wrong on that the access message length. The problem is, that there is a bug in the app itself.

In this function (located in MeshParserUtils.java) the opCode is returned as a short. Afterwards it is used as a int, so I am having a negative number even if it's the same in hex in further processing of the opCode.