TC-CNET-4.10 Test step 11 timeout.

Hi,

      Our product is about to undergo Matter certification. However, in the testing of TC-CNET-4.10, during the 11th step " ./chip-tool generalcommissioning arm-fail-safe 0 0 1 0", there is a timeout error indicating that the command is not responding. However, when executing it immediately for the second time, it succeeds. This phenomenon is consistently reproducible. Can you provide any guidance on how to resolve this issue? We are anxious to proceed with the product testing.

      I'm urgently looking forward to your reply.

      Jerry.

      22/8/2023

Parents
  • Hi Jerry,

    Thanks for reporting this issue.

    I will try to repeat it and feedback to you later.

    Best regards,

    Charlie

  • Hi Charlie,

    I have some new discoveries:

    1. If I execute the command "./chip-tool generalcommissioning arm-fail-safe 900 1 1 0" and then directly execute "./chip-tool generalcommissioning arm-fail-safe 0 0 1 0", it will be successful.
    2. If I execute the command "./chip-tool generalcommissioning arm-fail-safe 900 1 1 0" , then
      "./chip-tool networkcommissioning  remove-network "and "./chip-tool networkcommissioning connect-network", then execute "./chip-tool generalcommissioning arm-fail-safe 0 0 1 0", the first time will fail and the second time will be successful.
    3. If I change 900 to 60 based on 2, remove and reconnect the network, wait for 60s, and then execute "./chip-tool generalcommissioning arm-fail-safe 0 0 1 0", it will be successful on the first attempt.

    Hope these can help you.

     Jerry.

Reply
  • Hi Charlie,

    I have some new discoveries:

    1. If I execute the command "./chip-tool generalcommissioning arm-fail-safe 900 1 1 0" and then directly execute "./chip-tool generalcommissioning arm-fail-safe 0 0 1 0", it will be successful.
    2. If I execute the command "./chip-tool generalcommissioning arm-fail-safe 900 1 1 0" , then
      "./chip-tool networkcommissioning  remove-network "and "./chip-tool networkcommissioning connect-network", then execute "./chip-tool generalcommissioning arm-fail-safe 0 0 1 0", the first time will fail and the second time will be successful.
    3. If I change 900 to 60 based on 2, remove and reconnect the network, wait for 60s, and then execute "./chip-tool generalcommissioning arm-fail-safe 0 0 1 0", it will be successful on the first attempt.

    Hope these can help you.

     Jerry.

Children
No Data
Related