PanId is 0x080a when the network just formed.
after a time...
PanId has change to 0xb4a0. but I was do nothing.
Debug Printf on Coordinator:
...
APP: Entering BDB_vStart()
APP-BDB: Init Success
BDB: Forming Centralized Nwk
APP-EVT: Request Nwk Formation 00
APP: Entering APP_vMainLoop()
BDB: APP_vGenCallback [0 4]
APP-BDB: NwkFormation Success
APP-ZDO: Network started Channel = 15
PanId(080a) Extended PanId(00158d00038c5353)
... (after a time)
BDB: APP_vGenCallback [0 13]
APP-ZDO: Network status Indication 0f addr 0000
PanId(b4a0) Extended PanId(00158d00038c5353)
Hi Xizhao,
What is the time that you are referring to? minutes, hours, days?
Could you please provide your sniffer log?
Are you working on Zigbee 3.0?
I want to confirm the reason that the coordinators send the network update, maybe it detected some PANID conflict.
Regards,
Mario
Hi, Mario:
Thanks for your reply!
1. It' s appeared after a few hours with the network forming.
2. I am trying to capture it. please wait my sniffer log.
3. Yes, SDK is JN-SW-4170
4. Maybe the coordinator has send the network update. because I found the UpdateId(ZPS_tsNWkNibPersist) has change to 1 from 0.
Whether a PanId conflict has occured. I don't known. but I think the channel is clear at here.
My question:
1. How many reasons can make a event of ZPS_NWK_ST_PAN_ID_UPDATE(0x0f)?
2. If 'PanId conflict' is true. Can I prevent to modify the PanId when it happens.
3. What method the PanId of child node can be manually modified?
thank you!
Printf the structure ZPS_tsNWkNibPersist:
u8UpdateId(01)
u8ActiveKeySeqNumber(00)
u8VsDepth(00)
u8CapabilityInformation(00)
u8VsChannel(15)
u8ParentTimeoutMethod(07)
u8VsAuxChannel(00)
u8MacEnhanced(00)
u16VsPanId(b4a0)
u16NwkAddr(0000)
u16VsParentAddr(0000)
u64ExtPanId(00158d00038c5353)
Hi Xizhao,
My question:
1. How many reasons can make an event of ZPS_NWK_ST_PAN_ID_UPDATE(0x0f)?
The operational network PAN identifier of the device has been updated
Depending on the network update(PAN ID, Channel, LinkKey update). The sniffer log will provide the reason for this.
2. If 'PanId conflict' is true. Can I prevent to modify the PanId when it happens?
It is part of the ZigBee Spec, and also it is a good feature if the Coordinator detects the same PAN ID, it is for security purpose.
3. What method the PanId of child node can be manually modified?
I am not following this question. But the Coordinator is the one that could send this Nwk update.
Waiting for the sniffer log.
Regards,
Mario
Hi Mario:
Your guess is right!
One child node report a 'PanId Conflict'. Please view the sniffer log at row NO.101592
But I think that the report is wrong. No other coordinator send a same PanId.
The report node device is a product of other manufacturers. I have no idear with it.
If can not disable that coordinator send the 'PanId Update'. then I want to sync the PanId to other node of sleeped manually.
But I can not found the 'Network Update Command' API interface. I only found 'Network Status Command': ZPS_vNwkSendNwkStatusCommand
Please help me. thank you!
Hi Xizhao,
You have another Zigbee network with the same PAN ID. Please look at the packet 101634. the coordinator is also sending the network update.
The Network Update Command is to avoid the same PAN ID. You could also select another channel that doesn't have a lot of noise.
Regards,
Mario
Hi Mario:
Thank you very much! Let me try it.