https://devzone.nordicsemi.com/f/nordic-q-a/53132/publish-period-format-not-aligned-with-mesh-standard-definitionIn acces.h there is the publish period format definition, which is /** * Model publish period structure. */ typedef struct { /** Step resolution. */ uint8_t step_res : ACCESS_PUBLISH_STEP_RES_BITS; /** Number of steps. */ uint8_t step_num : ACCESS_PUBLISH_STEP_NUM_BITS;en-USTelligent Community 13Tue, 15 Oct 2019 08:32:14 GMThttps://devzone.nordicsemi.com/thread/214992?ContentTypeID=1Tue, 15 Oct 2019 08:32:14 GMT137ad170-7792-4731-bb38-c0d22fbe4515:5711a71e-67c7-4ce0-ab9a-8349e8ed3aaftesc<p>Hi,</p> <p>The mesh team had a look at the matter, and the structure you mentioned is only used internally. For communication over the Bluetooth mesh network, we use the usual patterns of masks, bitshifts and other bit operations to put the fields in the correct location and to read from the correct locations within the packets. Bitfields cannot be used for that, as implementation differs between toolchains.</p> <p>Regards,<br />Terje</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/214641?ContentTypeID=1Fri, 11 Oct 2019 15:52:17 GMT137ad170-7792-4731-bb38-c0d22fbe4515:f8bc1df6-af17-4ad9-94f1-5cfa174f23aetesc<p>Hi,</p> <p>Thank you for raising concerns regarding the bit ordering of the bit fields. I have reported it to the developers for them to have a look into it.</p> <p>The internal representation used by our SDK is not necessarily the same as what is sent over the air, even though the structure is similar. That means this is not necessarily an error, but it is good to have it checked anyway.</p> <p>Have you experienced any compatibility issues when connecting nRF based Bluetooth mesh devices with other devices, that can be tracked down to different interpretation of the Access Publish Period structure?</p> <p>Regards,<br />Terje</p><div style="clear:both;"></div>