zigbee messages not received in app layer

RE: zigbee messages not received in app layer

devtester — Thu, 09 Dec 2021 14:51:16 GMT

Hi,

I have tested setting the transaction time to 0xFF as suggested, it seem to work much better after that. Thanks for the answer, and the suggestion of not using the thread as I do too!

Kind regards

RE: zigbee messages not received in app layer

Edvin — Wed, 01 Dec 2021 15:41:47 GMT

Hello,
From our Zigbee team:
"Transition Time" field should be set to 0xFF to inform the device to alter the level attribute as fast as possible. Customer provided the code which sets it to "0" (macro definition "DIMM_TRANSACTION_TIME") and that's probably the reason why the callback is not called on every reception. Furthermore, using the Zephyr's semaphore to lock/unlock the thread to print the received data is probably not the best choice since the data can be received more often than scheduler is able to unlock the thread and lock it again (because of the 10ms systick).

So can you please test by setting the transition time to 0xFF instead of 0x00. I am missing some HW to test it right now. I can test once I am back in the office, if you like, but it would be faster for you to test yourself.

Best regards,

Edvin

RE: zigbee messages not received in app layer

devtester — Mon, 01 Nov 2021 07:55:26 GMT

Thanks, looking forward to hear their answer!

RE: zigbee messages not received in app layer

Edvin — Mon, 01 Nov 2021 07:23:57 GMT

Hello,

I am sorry for the late reply. I have looked at it, and I see the same behavior as you do. I have forwarded the question to our Zigbee team. I have not heard back from them yet, but I will let you know as soon as I do.

Sorry for the delay!

Best regards,

Edvin

RE: zigbee messages not received in app layer

devtester — Fri, 29 Oct 2021 05:22:15 GMT

Any news on this issue? Are you looking into it or what's happening?

RE: zigbee messages not received in app layer

devtester — Tue, 26 Oct 2021 12:56:34 GMT

Here's a run I did of the project with N_MESSAGES set to 30, ZED to the left and ZC to the right.

The ZED prints that it sends 30 messages.

The ZC only receives 16 messages in the app layer, 14 have not been reported. Nothing is printed from zcl_device_cb, but a semaphore is incremented for each message received and the print is done in the thread_process_data() thread.

I started in and use NCS v1.7.0, have verified by creating new freestanding projects and pasting the exact files I sent you, the behavior is still there.

I've also added CONFIG_USE_SEGGER_RTT=y, CONFIG_RTT_CONSOLE=y, and CONFIG_UART_CONSOLE=n to the proj.conf to log it via RTT instead of UART, but no difference.

LOG_ZIGBEE is a preprocessor function I've defined, only adds some more text to the printed string. I've never been able to see anything when I try to use LOG_INF(). I also find RTT very unreliable, communication drops when I connect to a second board or reboot devices.

RE: zigbee messages not received in app layer

Edvin — Tue, 26 Oct 2021 11:31:17 GMT

Ok, so I got the project that you sent me in a message. What am I looking for in the two logs? What are you lacking, and what device is lacking it? (ZED or ZC?)

I see that you use printk quite heavily, so it isn't that easy to change to RTT logging, which may help.

What NCS version did you start this project in, and what version are you running it in? I see that in the latest NCS version, all the zigbee samples uses LOG_INF(), and not LOG_ZIGBEE. Can you please try to port it to the latest version?

In that case it is easier to change to RTT backend on the logging module (see how it is done in the NCS\nrf\samples\bluetooth\peripheral_uart sample). That sample uses the RTT for logging, since the UART is used by the application.

Best regards,

Edvin

RE: zigbee messages not received in app layer

devtester — Tue, 26 Oct 2021 06:31:44 GMT

I trigger a semaphore for each time I get a ZB_ZCL_LEVEL_CONTROL_SET_VALUE_CB_ID in my zcl device cb, that I take in another thread which is incrementing and printing a counter for each lap it runs.

The semaphore is defined with K_SEM_MAX_LIMIT as limit, the extra threads with priority 7 and I've tested to increase the default thread (that I'm initiating Zigbee from, not sure if this is a isr or not) priority to 1.

This is my receiving routine in the ZC:

static void zcl_device_cb(zb_bufid_t bufid)
{
	zb_zcl_device_callback_param_t  *device_cb_param =
		ZB_BUF_GET_PARAM(bufid, zb_zcl_device_callback_param_t);

	device_cb_param->status = RET_OK; //Set default response value

	switch (device_cb_param->device_cb_id) {
	case ZB_ZCL_LEVEL_CONTROL_SET_VALUE_CB_ID:

		k_sem_give(&new_data_sem);

		break;

	case ZB_ZCL_SET_ATTR_VALUE_CB_ID:
		printk("Set_attr_value cb. \n");
		break;

	default:
		printk("Default cb\n");
		break;
	}
}

void thread_process_data(void *dummy1, void *dummy2, void *dummy3)
{
	uint8_t count = 0;
	while(1){
		k_sem_take(&new_data_sem, K_FOREVER);
		printk("Thread lap %d\n", ++count);
	}
}

This is the corresponding sending in the ZED:

static void cmd_sent(zb_bufid_t bufid)
{
	gettimeofday(&tv_stop, NULL);
	zb_zcl_command_send_status_t *status  = ZB_BUF_GET_PARAM(bufid,
						zb_zcl_command_send_status_t);
	time_current = CALC_US(); //NOTE: Should be some kind of buffer to not drop data points.
	k_sem_give(&sem_new_data);
	// k_sleep(K_MSEC(20));//7 ms somewhat usable

	gettimeofday(&tv_start, NULL);
	zb_buf_free(bufid);

	if (control_level++ < N_MESSAGES){
		zb_buf_get_out_delayed(send_level_control_message);
	}
}

// static void send_level_control_message(zb_bufid_t bufid, zb_uint16_t cmd_id)
static void send_level_control_message(zb_bufid_t bufid)
{
	ZB_ZCL_LEVEL_CONTROL_SEND_MOVE_TO_LEVEL_REQ(
		bufid,
		partner_ctx.short_addr,
		ZB_APS_ADDR_MODE_16_ENDP_PRESENT,
		partner_ctx.endpoint,
		LEVEL_CONTROL_SWITCH_ENDPOINT,
		ZB_AF_HA_PROFILE_ID,
		ZB_ZCL_DISABLE_DEFAULT_RESPONSE,
		cmd_sent,
		control_level, //Increment for visualization
		DIMM_TRANSACTION_TIME);
}


void thread_process_data(void *dummy1, void *dummy2, void *dummy3)
{
	while(1)
	{
		k_sem_take(&sem_new_data, K_FOREVER);
		time_total += time_current;
		printk("Control sent: %3d. Time: %.3f ms, avg: %.1f ms.\n",
			control_level,
			time_current*0.001,
			(time_total/control_level)*0.001);
	}
}

I'm aware for instance UART logging can be slow, but since I do that in another thread I should be safe, right?

RE: zigbee messages not received in app layer

Edvin — Mon, 25 Oct 2021 13:40:03 GMT

Hello,

[quote user=""]packets are dropped in the receiver side (often up to ~80%) before they reach the application level[/quote]

How do you determine that this is the case? For all I know, it is correct, but are you sure that the logging is not truncated, if you are trying to log very fast? If so, what is your log backend?

Is there a way for me to replicate this? Do you have some projects that you can share that replicates the issue?

Best Regards,

Edvin