[Zigbee] ZCL Tunneling cluster / APS Fragmentation

RE: Zigbee: ZCL Tunneling cluster / APS Fragmentation

Marte Myrvold — Tue, 21 May 2024 08:30:40 GMT

Hi Pawel,

I have taken over this ticket and started looking into it.

[quote user="pwpot"]When MaxIncomingPacketSize is limited to 52bytes everything works very well [/quote]

Can you share where MaxIncomingPacketSize is defined and used?

Do you have a sniffer log that shows the packet being sent?

Best regards,
Marte

RE: Zigbee: ZCL Tunneling cluster / APS Fragmentation

Pawel(embeddedsolutions.pl) — Wed, 08 May 2024 06:45:54 GMT

Hi,

I implemented the tunnelling cluster on my own. I wanted to use the APS fragmentation feature implemented in the stack and from my understanding, lower layers will handle it if needed.

Do you mean that APS is broken and requires bug fixing?

What do you mean by

[quote userid="108933" url="~/f/nordic-q-a/106858/zigbee-zcl-tunneling-cluster-aps-fragmentation/482414"]APS fragmentation won't work. [/quote]

Could you elaborate more?

Thanks in advance,

Pawel

RE: Zigbee: ZCL Tunneling cluster / APS Fragmentation

Kazi Afroza Sultana — Wed, 08 May 2024 06:25:44 GMT

Hello Pawel,

Sorry for the late reply.

APS fragmentation won't work. We do not have any support for the tunneling cluster, so, you have to implement it yourself.

Thanks.

BR
Kazi

RE: Zigbee: ZCL Tunneling cluster / APS Fragmentation

Pawel(embeddedsolutions.pl) — Fri, 12 Apr 2024 06:48:46 GMT

Hi,

Do you have any updates on that matter?

Regards,

Pawel

RE: Zigbee: ZCL Tunneling cluster / APS Fragmentation

Kazi Afroza Sultana — Fri, 02 Feb 2024 12:31:03 GMT

Hello,

I have asked the respective team. I will let you know soon.

RE: Zigbee: ZCL Tunneling cluster / APS Fragmentation

Pawel(embeddedsolutions.pl) — Sun, 21 Jan 2024 12:43:03 GMT

Hi,
I would like to share my newest findings.
It seems that APS fragmentation does not work properly -> more than 58bytes.
I was thinking that it works well, but after more long term tests it seems to be different.

Even if sending the ZCL Command returns RET_OK, the APS callback returns RET_NO_MEMORY and command is not being sent at all (I verify it under Wireshark).

zb_ret_t zb_zcl_tunneling_server_send_transfer_data(zb_uint8_t param, zb_uint8_t ep, zb_uint16_t prfl_id,
                                                    zb_uint8_t def_resp, zb_callback_t cb, zb_uint16_t tunnel_id,
                                                    zb_uint16_t data_size, zb_uint8_t *image_data) {
    ARG_UNUSED(def_resp);
    ARG_UNUSED(ep);
    ARG_UNUSED(prfl_id);

    if (!data_size || !image_data) {
        zb_buf_free(param);
        return RET_EMPTY;
    }

    tunnel_session_t *tunnel = find_session_by_tunnel_id(tunnel_id);
    if (!tunnel) {
        zb_buf_free(param);
        return RET_EMPTY;
    }

    zb_addr_u addr = {.addr_short = tunnel->session_data.dst.short_addr};
    uint8_t *ptr = ZB_ZCL_START_PACKET(param);
    ZB_ZCL_CONSTRUCT_SPECIFIC_COMMAND_RES_FRAME_CONTROL(ptr);
    ZB_ZCL_CONSTRUCT_COMMAND_HEADER(ptr, ZB_ZCL_GET_SEQ_NUM(), ZB_ZCL_TUNNELING_SRV_CMD_TRANSFER_DATA);
    ZB_ZCL_PACKET_PUT_DATA16(ptr, &tunnel_id);
    ZB_ZCL_PACKET_PUT_DATA_N(ptr, image_data, data_size);
    return zb_zcl_finish_and_send_packet_new(
        param, ptr, &addr, ZB_APS_ADDR_MODE_16_ENDP_PRESENT, tunnel->session_data.dst.ep, CONFIG_ZB_DEVICE_ENDPOINT,
        CONFIG_ZB_DEVICE_PROFILE_ID, ZB_ZCL_CLUSTER_ID_TUNNELING, cb, false, false, 0);
}

static void transfer_ams_data_aps_ack_cb(zb_bufid_t bufid) {
    zb_zcl_command_send_status_t *cmd_send_status = ZB_BUF_GET_PARAM(bufid, zb_zcl_command_send_status_t);
    if (cmd_send_status) {
        if (cmd_send_status->status != RET_OK) {
            LOG_ERR("APS CB stat: %d", cmd_send_status->status);
        }
    }

    k_mutex_lock(&tunnel_ctx_mtx, K_FOREVER);
    tunnel_session_t *tunnel = &tunnel_sessions[AMS_IDX];
    /* Stop the timer if started by UART RX thread as we are going to call send_tunnel_data from here */
    k_timer_stop(&tunnel->timer);
    zb_buf_free(bufid);
    zigbee_get_out_buf_delayed_ext(send_tunnel_data, tunnel->tunnel_id, MIN_REQUIRED_BUFFER_SIZE);
    k_mutex_unlock(&tunnel_ctx_mtx);
}

When MaxIncomingPacketSize is limited to 52bytes everything works very well :) but I would like to have slightly better throughput

RE: Zigbee: ZCL Tunneling cluster / APS Fragmentation

Kazi Afroza Sultana — Fri, 05 Jan 2024 15:45:45 GMT

Hello,

It seems like something wrong in the ZBOSS stack. I have asked our team. I will let you know soon.

RE: Zigbee: ZCL Tunneling cluster / APS Fragmentation

Kazi Afroza Sultana — Wed, 27 Dec 2023 08:45:22 GMT

Hello,

We are severely understaffed this week because of the Christmas holidays, and I will have to get back to you on this next week. Sorry for the inconvenience.

RE: Zigbee: ZCL Tunneling cluster / APS Fragmentation

Pawel(embeddedsolutions.pl) — Sat, 23 Dec 2023 01:00:35 GMT

Hi,

Thanks for fast reply,

Understood, so knowing that maximum number of APS fragments is limited to 8 and the available payload is something about 82bytes - ZCL Header it means that the maximum amount of data supported should be more than 600 bytes.

As I mentioned at the beginning, there is unknown for me limitation which forces me to send maximally 255bytes.

Why is that ?

Best regards,

Pawel

RE: Zigbee: ZCL Tunneling cluster / APS Fragmentation

Kazi Afroza Sultana — Fri, 22 Dec 2023 14:55:17 GMT

Hello,

You will not be able to send 1kB with APS fragmentation. You can look at the explanation here in this (+) Nordic DevZone (nordicsemi.com) similar case.

Thanks.

Kazi