How to resolve PAN ID conflict issue?

[bhautikrupareli]

we are using JN_SW_4168 Stack and JN5169 controller for development of Home Automation device. we have created a one network. In this network, we used one coordinator, end device with NXP stack, sleepy end device with NXP stack. so below we explained basic flow,
1. coordinator formed the network.
2. End Device joined with network.
3. Sleepy End Device also joined with same network.
4. After successfully joined two device then temperature data report and humidity data report to coordinator continuously.
5. If any other device to joined this network then first new device broadcast the beacon request and coordinator received the request and send the beacon but END device also send the beacon. And coordinator detect PAN ID conflict and send the network update command. so sleepy end device not received any command from coordinator.
6. But sleepy end device continuously report the data based on old PAN ID so coordinator not received any reported data.

we also shared Ubiqua traces for this issue.

So Is there any way to resolved this PAN ID conflict issue?

[weisheng]

Hi Bhautik,

      I have meet a same problem, can you tell me how you fix this?

[bhautikrupareli]

Hi Mario,

I have already attached [panid coflict.cubx.zip] Ubiqua traces.

we are not using JN-AN-1189 coordinator, but we are using another coordinator.

Regards,

Bhautik

[bhautikrupareli]

Hi Mario,

Have you check Ubiqua traces that i have already attached?

Regards,

Bhautik

[mario_castaneda]

HI Bhautik,

We did see in an older version the end device was responding back with beacon response for beacon request though it should not.

Could you please confirm the version (AN and SDK)that you are working on?

Mario

[bhautikrupareli]

Hi Mario,

the coordinator is not resetting continuously.

We have prepared the Temperature Sensor application with sleepy end device configuration with the reference of OccupancySensor application in JN-AN-1189-ZigBee-HA-Demo.

Regards,

Bhautik

[mario_castaneda]

Hi Bhautik,

I was trying to reproduce this issue. 

I create a Zigbee network, I used the JN-AN-1216 and followed the steps mentioned before.

1. coordinator formed the network.
2. End Device joined the network.
3. Sleepy End Device also joined the same network.
4. After successfully joined two device then occupancy data report to coordinator continuously.

 An end device joins the network without any problem.

So, Did you capture the data that is sending any network?

Are you working with the JN-AN-1189 Coordinator?

Regards,

Mario

[mario_castaneda]

Hi Bhautik,

It seems to be the joining handling with the first End device that is joining the network. It shouldn't be sent and beacon.
Do you know or see if the Coordinator is resetting continuously?

Could you please confirm the AN that you are working on? I will try to reproduce this issue.

Regards,
Mario