mesh2.0 coexistance with SDK15. Problem node configuartion

RE: mesh2.0 coexistance with SDK15. Problem node configuartion

Jui-Chou (Rick) Chung — Wed, 27 Jun 2018 13:48:09 GMT

Hello Collet,

I would assume this results from the heap region reservation in the memory.

Since in the ble_central example, the default setting for the heap is "0", but SAR transaction which needs by sending composition data need to use heap.

Please check this thread, hope this can do help :)

RE: mesh2.0 coexistance with SDK15. Problem node configuartion

FormerMember — Tue, 08 May 2018 09:42:24 GMT

The light switch proxy client example show how to set up a BLE connection in combination with Mesh. In that connection, the device is a BLE peripheral, however, it could be a starting point.

RE: mesh2.0 coexistance with SDK15. Problem node configuartion

Collet — Mon, 07 May 2018 07:52:45 GMT

Hi, thanks for your answer.

I've check during the week end with this values :

#define MIN_CONNECTION_INTERVAL     MSEC_TO_UNITS(100, UNIT_1_25_MS)    /**< Determines minimum connection interval in millisecond. */
#define MAX_CONNECTION_INTERVAL     MSEC_TO_UNITS(200, UNIT_1_25_MS)   /**< Determines maximum connection interval in millisecond. */

#define MIN_CONNECTION_INTERVAL     MSEC_TO_UNITS(250, UNIT_1_25_MS)    /**< Determines minimum connection interval in millisecond. */
#define MAX_CONNECTION_INTERVAL     MSEC_TO_UNITS(500, UNIT_1_25_MS)   /**< Determines maximum connection interval in millisecond. */

#define MIN_CONNECTION_INTERVAL     MSEC_TO_UNITS(500, UNIT_1_25_MS)    /**< Determines minimum connection interval in millisecond. */
#define MAX_CONNECTION_INTERVAL     MSEC_TO_UNITS(1000, UNIT_1_25_MS)   /**< Determines maximum connection interval in millisecond. */

With each test i ve try with this two value

#define SCAN_INTERVAL 0x00A0
#define SCAN_WINDOW 0x0050

and

#define SCAN_INTERVAL 0x0400
#define SCAN_WINDOW 0x000A

I've change the value of MAX_CONN_INTERVAL and MIN_CONN_INTERVAL in the blinky peripheral.

I've always the same error in each test. The mesh node client isn't configure and I've the timeout in the provisionner

RE: mesh2.0 coexistance with SDK15. Problem node configuartion

FormerMember — Fri, 04 May 2018 06:40:01 GMT

Could you try to increase the minimum accepted connection interval of ble_app_blinky to at least 100 ms? If that doesn't work, you can try to increase it even more, 250 ms or 500ms. The co-existence examples (SDK 14.2) in this thread uses a minimum connection interval of 500 ms.