Zigate Node Descriptor

[pipiche38]

When a device do a Node Descriptor Request to Zigate, it gets in return a Node Descriptor Response with the following informations

Why is the Max Incoming Transfer Size and Max Outgoing Transfer Size is set to 0 ? This is totally different than the other CIE. Does that mean teh CIE tell the Routers and Devices its have unlimited Incoming/Outgoing transfer size ?

What is the Purpose of the Network Manager flag ? This also doesn't look common in other gateways

[fairecasoimeme]

I don't know, I will investigate.

But I believe the Node Descriptor Response is internal to the SDK libraries. I don't know if we can find the information

[fairecasoimeme]

Ok we can find the information in the ZPSCFG

[pipiche38]

yep. but why 0 for Max Incoming and Max outgoing tranfsert size ? Does that mean unlimited ?

[fairecasoimeme]

This is the default value from nxp application note. Apparently, this value is not editable now. Here is the doc from JN-UG-3113:

[pipiche38]

So then I'm really questioning why 0. this doesn't make sense

[fairecasoimeme]

I don't know what is the consequence for devices. But if you want to test with other value, tell me how much what you need and I do.

[pipiche38]

My question was not about testing, it was much more questioning why 0 and what is the meaning, when I see all other coordinators/firmware coming with different values but definitively different than 0.

Looks like here this is not set accordingly to the documentation

[fairecasoimeme]

As I already said, the value 0, according to nxp documentation, for coordinator is not editable. 0 mean not avalaible or rather "calculated" But, besides other coordinators give different values, what is the purpose ? what is nor working properly with devices ?

Looks like here this is not set accordingly to the documentation

Which documentation are you talking about ?

[pipiche38]

Fred, the fact that there is 0 in the config file, if ok, but on the network it is not! My understanding is that it must be set to the Maximum incoming or outgoing transfer size.

As the what is not working properly, I think that you know that we have data corruption, we have errors on Zigate without any explanation. I'm just trying to point out incoherence versus other coordinators which doesn't show such type of dysfunction and data corrtuption.

Now it is your firmware and your coordinator. Closing

[fairecasoimeme]

I simply follow the NXP documentation and it's clear for this point. The maximum Incoming and outgoing Transfer size properties from node descriptor is used to give informations to devices. There is no link with PDM or any data corruptions and there is no data corruption on zigate v2 against zigate v1. The only problem is PDM tables which are full in under some conditions (that is difficult to reproduce)

The firmware is open, you can download/compile and do test.

Thanks for all