[FAST_PROV_CLIENT_DEMO] Timeout

Post Reply
tania-ferreira
Posts: 1
Joined: Sat Apr 11, 2020 4:33 pm

[FAST_PROV_CLIENT_DEMO] Timeout

Postby tania-ferreira » Sat Apr 11, 2020 4:56 pm

While running the FAST_PROV_CLIENT_DEMO on one board and FAST_PROV_SERVER_DEMO in other, I keep receiving a timeout at the client when sending the ESP_BLE_MESH_VND_MODEL_OP_FAST_PROV_NODE_ADDR_GET message to the server. After that occurs, nothing else happens as the client still tries to send the same message.

The obtained log files in both sides are as follow:
Code: [Select all] [Expand/Collapse]
  1. I (1208) FAST_PROV_CLIENT_DEMO: BLE Mesh Provisioner initialized
  2. I (13258) FAST_PROV_CLIENT_DEMO: address:  246f28251a6e, address type: 0, adv type: 3
  3. I (13258) FAST_PROV_CLIENT_DEMO: dev uuid: dddd246f28251a6e0000000000000000
  4. I (13268) FAST_PROV_CLIENT_DEMO: oob info: 0, bearer: PB-ADV
  5. I (13278) FAST_PROV_CLIENT_DEMO: ESP_BLE_MESH_PROVISIONER_PROV_LINK_OPEN_EVT, bearer PB-ADV
  6. I (13278) FAST_PROV_CLIENT_DEMO: PB-ADV link open
  7. I (13288) FAST_PROV_CLIENT_DEMO: ESP_BLE_MESH_PROVISIONER_ADD_UNPROV_DEV_COMP_EVT, err_code: 0
  8. I (15228) FAST_PROV_CLIENT_DEMO: ESP_BLE_MESH_PROVISIONER_PROV_COMPLETE_EVT
  9. I (15228) FAST_PROV_CLIENT_DEMO: Node index: 0x0, unicast address: 0x05, element num: 1, netkey index: 0x00
  10. I (15238) FAST_PROV_CLIENT_DEMO: Node uuid:  dddd246f28251a6e0000000000000000
  11. I (15248) FAST_PROV_CLIENT_DEMO: ESP_BLE_MESH_PROVISIONER_SET_NODE_NAME_COMP_EVT, err_code: 0
  12. I (15718) FAST_PROV_CLIENT_DEMO: example_config_client_callback, error_code = 0x00, event = 0x01, addr: 0x0005
  13. I (15728) FAST_PROV_OP: min:       0x0006, max:        0x7fff
  14. I (15728) FAST_PROV_OP: flags:     0x00,   iv_index:   0x00000000
  15. I (15738) FAST_PROV_OP: net_idx:   0x0000, group_addr: 0xc000
  16. I (15738) FAST_PROV_OP: action:    0x81
  17. I (15748) FAST_PROV_OP: match_val: dd dd
  18. I (15748) 8.2.: chamada: esp_ble_mesh_client_model_send_msg()
  19. I (15758) 8.3.: executada: esp_ble_mesh_client_model_send_msg()
  20. I (15778) FAST_PROV_CLIENT_DEMO: ESP_BLE_MESH_MODEL_SEND_COMP_EVT, err_code 0
  21. I (16168) FAST_PROV_CLIENT_DEMO: example_custom_model_callback: Fast Prov Client Model receives status, opcode 0xc102e5
  22. I (16168) fast prov client receives: 7f 00 00 00 00 00 00 00 00
  23. I (16178) fast prov info status: 7f 00 00 00 00 00 00 00 00
  24. I (16188) 23. : chamada: k_delayed_work_init()
  25. I (16188) 24. : executada: k_delayed_work_init(), chamada: k_delayed_work_submit()
  26. I (16198) 25. : executada: k_delayed_work_submit()
  27. W (16658) BLE_MESH: Got segment for already complete SDU
  28. W (16738) BLE_MESH: Got segment for already complete SDU
  29. I (17218) FAST_PROV_CLIENT_DEMO: ESP_BLE_MESH_PROVISIONER_PROV_LINK_CLOSE_EVT, bearer PB-ADV reason 0x00
  30. I (17218) FAST_PROV_CLIENT_DEMO: PB-ADV link close, reason 0x00
  31. W (17238) BLE_MESH: Got segment for already complete SDU
  32. W (17318) BLE_MESH: Got segment for already complete SDU
  33. W (17818) BLE_MESH: Got segment for already complete SDU
  34. W (17898) BLE_MESH: Got segment for already complete SDU
  35. W (18398) BLE_MESH: Got segment for already complete SDU
  36. W (18478) BLE_MESH: Got segment for already complete SDU
  37. I (76208) FAST_PROV_CLIENT_DEMO: ESP_BLE_MESH_MODEL_SEND_COMP_EVT, err_code 0
  38. I (86208) FAST_PROV_CLIENT_DEMO: ESP_BLE_MESH_CLIENT_MODEL_SEND_TIMEOUT_EVT, opcode 0xc602e5, dst 0x0005
  39. W (86208) FAST_PROV_CLIENT: example_fast_prov_client_recv_timeout: Receive fast prov server status timeout
  40. I (86228) FAST_PROV_CLIENT_DEMO: ESP_BLE_MESH_MODEL_SEND_COMP_EVT, err_code 0
  41. I (96228) FAST_PROV_CLIENT_DEMO: ESP_BLE_MESH_CLIENT_MODEL_SEND_TIMEOUT_EVT, opcode 0xc602e5, dst 0x0005
  42. W (96228) FAST_PROV_CLIENT: example_fast_prov_client_recv_timeout: Receive fast prov server status timeout
GeSHi © Codebox Plus Extension
Code: [Select all] [Expand/Collapse]
  1. I (3908) FAST_PROV_SERVER_DEMO: ESP_BLE_MESH_PROV_REGISTER_COMP_EVT, err_code: 0
  2. I (3918) FAST_PROV_SERVER_DEMO: ESP_BLE_MESH_NODE_PROV_ENABLE_COMP_EVT, err_code: 0
  3. I (3918) FAST_PROV_SERVER_DEMO: BLE Mesh Fast Prov Node initialized
  4. I (3968) FAST_PROV_SERVER_DEMO: ESP_BLE_MESH_NODE_PROV_LINK_OPEN_EVT, bearer: PB-ADV
  5. I (5848) FAST_PROV_SERVER_DEMO: ESP_BLE_MESH_NODE_PROV_COMPLETE_EVT
  6. I (5848) FAST_PROV_SERVER_DEMO: net_idx: 0x0000, unicast_addr: 0x0005
  7. I (5848) FAST_PROV_SERVER_DEMO: flags: 0x00, iv_index: 0x00000000
  8. I (6068) FAST_PROV_SERVER_DEMO: ESP_BLE_MESH_NODE_PROV_LINK_CLOSE_EVT, bearer: PB-ADV
  9. I (6248) FAST_PROV_SERVER_DEMO: example_ble_mesh_config_server_cb, event = 0x00, opcode = 0x0000, addr: 0x0001
  10. I (6248) FAST_PROV_SERVER_DEMO: Config Server get Config AppKey Add
  11. I (6608) FAST_PROV_SERVER_DEMO: example_ble_mesh_custom_model_cb: Fast prov server receives msg, opcode 0xc002e5
  12. I (6618) fast prov server recv: 7f 03 64 00 06 00 ff 7f 00 00 00 00 00 00 00 00
  13. I (6618) fast prov server recv: c0 dd dd 81
  14. I (6628) FAST_PROV_SERVER_DEMO: ESP_BLE_MESH_SET_FAST_PROV_INFO_COMP_EVT
  15. I (6638) FAST_PROV_SERVER_DEMO: status_unicast: 0x00, status_net_idx: 0x00, status_match 0x00
  16. I (6638) 13. : chamada: esp_ble_mesh_set_fast_prov_action()
  17. I (6648) 14. : executada: esp_ble_mesh_set_fast_prov_action()
  18. I (6658) FAST_PROV_SERVER_DEMO: ESP_BLE_MESH_SET_FAST_PROV_ACTION_COMP_EVT, status_action 0x00
  19. I (6668) 19. : chamada: example_send_fast_prov_status_msg()
  20. I (6668) 20. : executada: example_send_fast_prov_status_msg()
  21. I (6678) FAST_PROV_SERVER_DEMO: ESP_BLE_MESH_MODEL_SEND_COMP_EVT, err_code 0
  22. I (6688) FAST_PROV_SERVER: example_handle_fast_prov_status_send_comp_evt: opcode 0xc102e5
  23. W (6698) FAST_PROV_SERVER: example_handle_fast_prov_status_send_comp_evt: Disable BLE Mesh Relay & GATT Proxy
  24. I (6708) 20.4. : chamada: esp_ble_mesh_proxy_gatt_disable()
  25. I (6708) 20.5. : executada: esp_ble_mesh_proxy_gatt_disable()
  26. I (6718) FAST_PROV_SERVER_DEMO: ESP_BLE_MESH_NODE_PROXY_GATT_DISABLE_COMP_EVT
GeSHi © Codebox Plus Extension


Does someone know why this keeps happening? I don't get it since until that step the server node is able to receive all the messages. The current esp-idf branch is version 4.2 but at this point I already tried all the branches and the observed behavior is the same.
Top
Post Reply

Return to “General Discussion”

Who is online

Users browsing this forum: Baidu [Spider] and 91 guests