Skip to content

Conversation

@nkljajic
Copy link
Collaborator

Fix TX process stuck waiting for callback if transmission ongoing
Abort Add/Remove if in progress
Fix zwapi send data abort after emerency timeout

Fix TX process stuck waiting for callback if transmission ongoing
Abort Add/Remove if in progress
Fix zwapi send data abort after emerency timeout
@nkljajic
Copy link
Collaborator Author

nkljajic commented Apr 12, 2023

Pressing reset button on WSTK board during node inclusion/interview, can simulate Serial API unexpected restart.

@nkljajic
Copy link
Collaborator Author

Log file example, of TX queue being stuck

2023-04-03 18:23:29.943  DEBUG: [zwapi_connection] Outgoing Z-Wave API frame (hex): Length=10 Type=00 Cmd=A9 00 FF 00 10 02 20 02 25 00 00 00 00 01 AD 
2023-04-03 18:23:31.635  DEBUG: [zwapi_protocol_rx_dispatch] Incoming Z-Wave API frame (hex): Length=26 Type=00 Cmd=0A 07 00 01 01 00 1C 5E 55 6C 74 8A 8F 98 9F EF 25 26 2B 2C 2D 30 31 32 33 40 43 5B 60 62 70 71 80 84 9C 01 
2023-04-03 18:24:34.944  ERR: [zwave_api_transport] Emergency timer fired! Aborting transmission for element id=0xc
2023-04-03 18:24:34.951  DEBUG: [zwapi_connection] Outgoing Z-Wave API frame (hex): Length=03 Type=00 Cmd=16 EA 
2023-04-03 23:52:33.385  DEBUG: [zwave_tx_process] Received all expected replies from NodeID 16 for frame id=0xc.
2023-04-03 23:52:33.385  DEBUG: [zwave_tx_process] Resume from Z-Wave TX back off. Reason was: BACKOFF_CURRENT_SESSION_ID
2023-04-03 23:52:33.399  DEBUG: [zwave_tx_process] Received all expected replies from NodeID 16 for frame id=0xc.
2023-04-03 23:52:33.400  DEBUG: [zwave_tx_process] Resume from Z-Wave TX back off. Reason was: BACKOFF_CURRENT_SESSION_ID
2023-04-03 23:52:33.466  DEBUG: [zwave_tx_process] Received all expected replies from NodeID 16 for frame id=0xc.
2023-04-03 23:52:33.466  DEBUG: [zwave_tx_process] Resume from Z-Wave TX back off. Reason was: BACKOFF_CURRENT_SESSION_ID
2023-04-04 00:02:22.333  DEBUG: [zwave_tx_process] Received all expected replies from NodeID 16 for frame id=0xc.
2023-04-04 00:02:22.333  DEBUG: [zwave_tx_process] Resume from Z-Wave TX back off. Reason was: BACKOFF_CURRENT_SESSION_ID
2023-04-04 00:02:22.430  DEBUG: [zwave_tx_process] Received all expected replies from NodeID 16 for frame id=0xc.
2023-04-04 00:02:22.430  DEBUG: [zwave_tx_process] Resume from Z-Wave TX back off. Reason was: BACKOFF_CURRENT_SESSION_ID
2023-04-04 00:04:46.418  DEBUG: [zwave_tx_process] Received all expected replies from NodeID 16 for frame id=0xc.
2023-04-04 00:04:46.418  DEBUG: [zwave_tx_process] Resume from Z-Wave TX back off. Reason was: BACKOFF_CURRENT_SESSION_ID
2023-04-04 00:04:46.497  DEBUG: [zwave_tx_process] Received all expected replies from NodeID 16 for frame id=0xc.
2023-04-04 00:04:46.497  DEBUG: [zwave_tx_process] Resume from Z-Wave TX back off. Reason was: BACKOFF_CURRENT_SESSION_ID
2023-04-04 00:06:22.400  DEBUG: [zwave_tx_process] Received all expected replies from NodeID 16 for frame id=0xc.
2023-04-04 00:06:22.400  DEBUG: [zwave_tx_process] Resume from Z-Wave TX back off. Reason was: BACKOFF_CURRENT_SESSION_ID
2023-04-04 00:06:22.434  DEBUG: [zwave_tx_process] Received all expected replies from NodeID 16 for frame id=0xc.


@ghost
Copy link

ghost commented Apr 18, 2023

Thanks for the feedback, we will address these issues for the next release. 🙂

@nkljajic nkljajic closed this Jun 9, 2023
@nkljajic nkljajic deleted the 1.3.1-fix-SERIAL_API_STARTED branch August 24, 2023 16:06
@nkljajic nkljajic restored the 1.3.1-fix-SERIAL_API_STARTED branch August 24, 2023 16:06
@nkljajic nkljajic deleted the 1.3.1-fix-SERIAL_API_STARTED branch August 24, 2023 16:25
rzr added a commit that referenced this pull request Mar 28, 2025
This change allow building UnifySDK on github.

Removing LFS objects is a good start to slim down UnifySDK repo

Observed issue:

    (...)
    #11 538.0 100% tests passed, 0 tests failed out of 69
    #11 538.0 Total Test time (real) = 287.70 sec
    #11 538.0 cmake --build build --target package
    (...)
    #11 538.2 [2/3] Run CPack packaging tool...
    #11 538.2 CPack: Create package using DEB
    #11 538.2 CPack: Install projects
    #11 538.2 CPack: - Install project: uic []
    #11 538.2 CPack: -   Install component: libunify-dev
    #11 538.7 CMake Error at /usr/local/opt/unifysdk/build/components/cmake_install.cmake:195 (file):
    #11 538.7   file INSTALL cannot copy file

Relate-to: SiliconLabsSoftware/z-wave-engine-application-layer#11
Signed-off-by: Philippe Coval <philippe.coval@silabs.com>
Thomasdjb pushed a commit to Thomasdjb/UnifySDK that referenced this pull request May 22, 2025
This change allow building UnifySDK on github.

Removing LFS objects is a good start to slim down UnifySDK repo

Observed issue:

    (...)
    SiliconLabs#11 538.0 100% tests passed, 0 tests failed out of 69
    SiliconLabs#11 538.0 Total Test time (real) = 287.70 sec
    SiliconLabs#11 538.0 cmake --build build --target package
    (...)
    SiliconLabs#11 538.2 [2/3] Run CPack packaging tool...
    SiliconLabs#11 538.2 CPack: Create package using DEB
    SiliconLabs#11 538.2 CPack: Install projects
    SiliconLabs#11 538.2 CPack: - Install project: uic []
    SiliconLabs#11 538.2 CPack: -   Install component: libunify-dev
    SiliconLabs#11 538.7 CMake Error at /usr/local/opt/unifysdk/build/components/cmake_install.cmake:195 (file):
    SiliconLabs#11 538.7   file INSTALL cannot copy file

Relate-to: SiliconLabsSoftware/z-wave-engine-application-layer#11
Signed-off-by: Philippe Coval <philippe.coval@silabs.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant