Lines Matching full:value
24 value: 1
30 value: 1
36 value: 0
42 value: 1
49 value: 1
54 using Node Identity. The given value is in seconds. The
56 be the appropriate value as well, so just leaving this as the
58 value: 60
64 value: 1
70 value: 1
76 value: 1
82 value: 1
88 value: 1
93 value: 1
100 value: 10
106 value: 9
114 value: 10
124 value: 6
146 stored to flash. E.g. the default value of 4 means that the
148 value: 4
154 value: 4
160 value: 2
166 can have. Each segment can contain 12 bytes, so this value should
170 value: 72
175 This value should typically be fine-tuned based on what
178 This value affects memory and call stack consumption, which
189 when setting this option to a higher value. There must be at
192 value: 3
197 value: 0
202 value: 0
211 value: 1
219 value: 1
225 value: 15
231 value: 8
237 value: 0
243 value: 0
250 MinQueueSizeLog value 1 gives N = 2, and value 7 gives N = 128.
251 value: 1
257 allows the Friend node time to prepare the response. The value
259 value: 100
267 terminated. The value is in units of 100 milliseconds, so e.g.
268 a value of 300 means 30 seconds.
269 value: 300
273 The initial value of the PollTimeout timer when Friendship
276 in value for each iteration. The value is in units of 100
277 milliseconds, so e.g. a value of 300 means 3 seconds.
278 value: MYNEWT_VAL_BLE_MESH_LPN_POLL_TIMEOUT
285 value: 10
290 value: 10
295 value: 0
300 value: 255
306 value: 16
312 value: 3
318 value: 2
326 value: 1
331 value: 0
336 value: 0
342 value: 0
348 value: 0
354 value: 0
360 value: 0
366 value: 0
372 value: 0
378 value: 0
384 value: 0
390 value: 0
396 value: 0
402 value: 0
408 value: 0
413 value: 0
418 value: 1
424 value: 0
429 value: 0
434 value: ((uint8_t[16]){0x11, 0x22, 0})
439 value: 0
450 value: ((BT_MESH_DISPLAY_NUMBER))
455 value: 4
465 value: ((BT_MESH_NO_INPUT))
470 value: 4
475 value: 1
479 This value defines in seconds how soon any pending changes
482 value: 2
486 This value defines how often the local sequence number gets
487 updated in persistent storage (i.e. flash). E.g. a value of 100
490 higher value makes more sense, whereas if the node sends
491 infrequently a value as low as 0 (update storage for every
494 off with a value that's guaranteed to be larger than the last
496 value: 128
500 This value defines in seconds how soon the RPL gets written to
503 large value, whereas if the RPL gets updated infrequently a
504 value as low as 0 (write immediately) may make sense. Note that
507 to set this value to anything else than 0 (a power loss before
510 value: 5
514 This value defines BLE Mesh device/node name.
515 value: '"nimble-mesh-node"'
520 value: 500
525 value: 1000