Hello,
I used X-CTU to set my XB24-B module to function as end device (FW 2970). I configured also its 64-bit address 0x0000000000000001. I used another module XB24-B to work as Coordinator to send a Zigbbe Transmit Request Frame (0x10) :
7E 00 0F 10 01 00 00 00 00 00 00 00 01 FF FE 00 00 01 EF
but I received the reply from the coordinator like follow:
7E 00 07 8B 01 FF FE 01 24 03 4E
which means that address not found.
Then if I explicitly used the End Device Address 0xFFDB instead of 0xFFFE:
7E 00 0F 10 01 00 00 00 00 00 00 00 01 FF DB 00 00 01 12
I received another reply:
7E 00 07 8B 01 FF FE 02 24 02 4E
Is my sending frame correct?
why are you specifying a 64-bit address of 0x1? I strongly suspect the coordinator is rejecting that artificial address by comparing it to the true 64 bit address of the module.
try specifying the true address and that should work.
@kjensen8: because the address of my end device is set to 0x0000000000000001(DH=0, DL=1) using X-CTU. I discovered that my 16-bit address is not good because of an error in the firmware (an extension of signed bit), so i have corrected it. Now I use the good 16-bit address with the 64-bit address which is explictly assigned to the module by using X-CTU (always DH=0, DL=1) but I receive the same:
7E 00 07 8B 01 FF FE 00 24 02 50 (24 = Address not found )
I continued to test by sending a frame from the end device to the coordinator to verify the 64-bit address of the end device. I regconize that this is not the address that I have set using X-CTU. Fox example:
7E 00 0F 90 00 13 A2 00 40 5D 3B A7 9F 74 41 00 00 00 E7
The bold address is the actual 64-bit address of the end device. Then I reused these actuals addresses (64 bit + 16 bit obtained when joining to network) in the frame sent by coordinator to end device and it’s OK:
Sending: 7E 00 0F 10 01 00 13 A2 00 40 5D 3B A7 9F 74 00 00 01 A6
Receiving: 7E 00 07 8B 01 9F 74 00 00 00 60
So we can not set the 64-bit address using X-CTU?