mesh network

[noam]

Hi!

I am currently using SEGGER Embedded Studio version  4.12, nRF5 SDK version15.2.0,  nRF5 SDK for Mesh version 3.1.0,   Hardware BMD-300 Evaluation Board.

i using the uart to send data over the ble mesh and all work fine except that if i get data from the uart and sending it over the mesh(ble) in interval lowest from 2 sec between two message and the second one the ble doesn't sending it.

i changed in the header file  transport.h the parameters:

/** Default base TX retry timeout. */ TRANSPORT_SAR_TX_RETRY_BASE_TIMEOUT_DEFAULT_US  FROM: MS_TO_US(500)    TO: MS_TO_US(200)

and

/** Default number of retries before cancelling SAR TX session. */ TRANSPORT_SAR_TX_RETRIES_DEFAULT FROM: (4)       TO: (2)

and it fix my problem and for now all work fine.

those changes will cause problems/bugs? how those changes 'will affect my mesh network?

thanks!

[Hung Bui]

Hi Noamb, 

How large is your data ? 

Note that if you are doing segmented message, you can only send one message at a time. Have you made sure when you call a packet send function, you check if it returns success ? 

[noam]

my data is 25 byte (i know that in mesh can send less ) and yes i check if it returns success (when its not sending the message its return 8-->NRF_ERROR_INVALID_STATE).

i want to know if my changes will makes me problems or affect my mesh network?

[Hung Bui]

Hi Noamb, 

Mesh should be able to handle 25bytes easily (using SAR packets). How many devices you used in your test ? Which message did you send ? was it acknowledged message or unacknowledged message ?

By default we have the advertising interval of 20ms. So to be able to send 25 bytes (3 SAR packets) it can take only 60ms. 

How do you know that the second message doesn't get sent ? We need to step into the code to know what could be wrong here. 

[noam]

its was acknowledged message.

i know that the second message doesn't get sent because i get  NRF_ERROR_INVALID_STATE, i get this error from the function segmented_packet_tx in this function there is a comment: 

/* According to the Mesh Profile Specification v1.0 Section 3.6.4.1, we should only ever send one
* transport SAR packet at the same time between a given source and destination. Return FORBIDDEN if
* there's a SAR session in progress with the same parameters. */

 

[Hung Bui]

Could you check if the first packet is acknowledged before you send the next package ? 

Have you check how long it takes to have the packet acknowledged ?  How many devices in the network you are testing  ? How do you send the message ? To a unicast address or to a group address ? 

[noam]

i'm using 2 devices a client and a server. i'm sending a message from the server to the client using the function app_onoff_status_publish, so i don't check if i getting ack (do i need to add it to my code?).

i sending the messages from the server to a group address