This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Problem joining XBee (Zigbee)

I am trying to connect XBee 3.0 Zigbee to a Nordic USB dongle (PAC10059) which has the nRF52840 chipset.

I have been watching the traffic on channel 16 with a CC2531 sniffer which shows association attempts which

are initially successful, and then the network seems to keep reforming.

The ZC (nRF52840) is initialised as follows:

bdb factory_reset // power dongle off then on

bdb role zc

bdb channel 16

log enable info app // to show connection log

bdb policy enable

bdb start

Due to diagnosing the connection problem I then try to add the install code for the XBee 3.0 Zigbee router:

> bdb ic add 6E4D5F6989E752C9684A6D7C8BD7A4F9 0013A20041c78369
Error: Failed to add IC
> bdb ic add 6E4D5F6989E752C9684A6D7C8BD7A4F9 0013A20041C78369
Error: Failed to add IC

I have taken the install code from the XBee I? parameter, and the second parameter is the MAC address

of the XBee (EUI64 code?)

Anyone got any ideas why adding the install code to the ZC (PCA10059) isn't working?

Parents
  • Hi

    It looks like it lacks the checksum in the end of the install code. Please refer to the documentation:

    * ``bdb ic add`` must only be used on a coordinator.
      For *h:eui64*, use the address of the joining device.
      
    * ``bdb ic policy`` must only be used on a coordinator.
    
    Provide the install code as an ASCII-encoded :file:`HEX` file that includes CRC16/X-25 in little-endian order.
    
    For production devices, an install code must be installed by the production
    configuration present in flash.

    For the install code 6E4D5F6989E752C9684A6D7C8BD7A4F9 for example, the checksum is 0xfb08, and must be in little-endian order. The final install code with checksum should therefore look like this, 6E4D5F6989E752C9684A6D7C8BD7A4F908FB, and with this change CLI will accept the install code.

    Best regards,

    Simon

Reply
  • Hi

    It looks like it lacks the checksum in the end of the install code. Please refer to the documentation:

    * ``bdb ic add`` must only be used on a coordinator.
      For *h:eui64*, use the address of the joining device.
      
    * ``bdb ic policy`` must only be used on a coordinator.
    
    Provide the install code as an ASCII-encoded :file:`HEX` file that includes CRC16/X-25 in little-endian order.
    
    For production devices, an install code must be installed by the production
    configuration present in flash.

    For the install code 6E4D5F6989E752C9684A6D7C8BD7A4F9 for example, the checksum is 0xfb08, and must be in little-endian order. The final install code with checksum should therefore look like this, 6E4D5F6989E752C9684A6D7C8BD7A4F908FB, and with this change CLI will accept the install code.

    Best regards,

    Simon

Children
No Data
Related