How to run Zigbee Console Application

I don’t think so - the driver should configure it when the console starts. I have never used Z-Tool and I’ve used the CC2531 a lot over the years.

Hi @chris,

I had connected CC2538EM device to my PC. The CC2538EM going to ONLINE in my workspace.

CC2531EMK properties shown in below.

When I was going to search for router in Paper UI .I didn’t get any router. I got below info.

13:01:17.248 DEBUG [pool-24-thread-5] 063A490C00124B00: Node SVC Discovery already scheduled or running
13:01:48.185 DEBUG [pool-24-thread-4] 063A490C00124B00: Node SVC Discovery running
13:01:48.191 DEBUG [pool-24-thread-4] TX CMD: NetworkAddressRequest [0/0 -> 65535/0, cluster=0000, TID=10, ieeeAddr=063A490C00124B00, requestType=0, startIndex=0]
13:01:48.194 DEBUG [pool-24-thread-4] TX APS: ZigBeeApsFrame [sourceAddress=0/0, destinationAddress=65535/0, profile=0000, cluster=0, addressMode=DEVICE, radius=31, apsSecurity=false, apsCounter=16, payload=00 00 4B 12 00 0C 49 3A 06 00 00]
13:01:48.203 DEBUG [pool-24-thread-4] ->  AF_DATA_REQUEST (Packet: subsystem=null, length=21, apiId=24 01, data=FE 15 24 01 FF FF 00 00 00 00 10 30 1F 0B 00 00 4B 12 00 0C 49 3A 06 00 00 24, checksum=24, error=false)
13:01:48.315 DEBUG [ZToolPacketParser] <-  AF_DATA_SRSP (FE 01 64 01 00 64)
13:01:56.192 DEBUG [pool-24-thread-1] Transaction timeout: NetworkAddressRequest [0/0 -> 65535/0, cluster=0000, TID=10, ieeeAddr=063A490C00124B00, requestType=0, startIndex=0]
13:01:56.198 DEBUG [pool-24-thread-4] 0: Node SVC Discovery NetworkAddressRequest returned null
13:01:56.202 DEBUG [pool-24-thread-4] 063A490C00124B00: Node SVC Discovery request NWK_ADDRESS failed. Retry 16, wait 17160ms before retry.
13:02:13.371 DEBUG [pool-24-thread-4] 063A490C00124B00: Node SVC Discovery running
13:02:13.376 DEBUG [pool-24-thread-4] TX CMD: NetworkAddressRequest [0/0 -> 65535/0, cluster=0000, TID=11, ieeeAddr=063A490C00124B00, requestType=0, startIndex=0]
13:02:13.381 DEBUG [pool-24-thread-4] TX APS: ZigBeeApsFrame [sourceAddress=0/0, destinationAddress=65535/0, profile=0000, cluster=0, addressMode=DEVICE, radius=31, apsSecurity=false, apsCounter=17, payload=00 00 4B 12 00 0C 49 3A 06 00 00]
13:02:13.388 DEBUG [pool-24-thread-4] ->  AF_DATA_REQUEST (Packet: subsystem=null, length=21, apiId=24 01, data=FE 15 24 01 FF FF 00 00 00 00 11 30 1F 0B 00 00 4B 12 00 0C 49 3A 06 00 00 25, checksum=25, error=false)
13:02:13.502 DEBUG [ZToolPacketParser] <-  AF_DATA_SRSP (FE 01 64 01 00 64)
13:02:21.378 DEBUG [pool-24-thread-6] Transaction timeout: NetworkAddressRequest [0/0 -> 65535/0, cluster=0000, TID=11, ieeeAddr=063A490C00124B00, requestType=0, startIndex=0]
13:02:21.385 DEBUG [pool-24-thread-4] 0: Node SVC Discovery NetworkAddressRequest returned null
13:02:21.389 DEBUG [pool-24-thread-4] 063A490C00124B00: Node SVC Discovery request NWK_ADDRESS failed. Retry 17, wait 34320ms before retry.
13:02:55.718 DEBUG [pool-24-thread-4] 063A490C00124B00: Node SVC Discovery running
13:02:55.724 DEBUG [pool-24-thread-4] TX CMD: NetworkAddressRequest [0/0 -> 65535/0, cluster=0000, TID=12, ieeeAddr=063A490C00124B00, requestType=0, startIndex=0]
13:02:55.728 DEBUG [pool-24-thread-4] TX APS: ZigBeeApsFrame [sourceAddress=0/0, destinationAddress=65535/0, profile=0000, cluster=0, addressMode=DEVICE, radius=31, apsSecurity=false, apsCounter=18, payload=00 00 4B 12 00 0C 49 3A 06 00 00]
13:02:55.735 DEBUG [pool-24-thread-4] ->  AF_DATA_REQUEST (Packet: subsystem=null, length=21, apiId=24 01, data=FE 15 24 01 FF FF 00 00 00 00 12 30 1F 0B 00 00 4B 12 00 0C 49 3A 06 00 00 26, checksum=26, error=false)
13:02:55.948 DEBUG [ZToolPacketParser] <-  AF_DATA_SRSP (FE 01 64 01 00 64)
13:03:03.724 DEBUG [pool-24-thread-5] Transaction timeout: NetworkAddressRequest [0/0 -> 65535/0, cluster=0000, TID=12, ieeeAddr=063A490C00124B00, requestType=0, startIndex=0]
13:03:03.730 DEBUG [pool-24-thread-4] 0: Node SVC Discovery NetworkAddressRequest returned null
13:03:03.734 DEBUG [pool-24-thread-4] 063A490C00124B00: Node SVC Discovery request NWK_ADDRESS failed. Retry 18, wait 10725ms before retry.
13:03:14.468 DEBUG [pool-24-thread-4] 063A490C00124B00: Node SVC Discovery running
13:03:14.471 DEBUG [pool-24-thread-4] TX CMD: NetworkAddressRequest [0/0 -> 65535/0, cluster=0000, TID=13, ieeeAddr=063A490C00124B00, requestType=0, startIndex=0]
13:03:14.473 DEBUG [pool-24-thread-4] TX APS: ZigBeeApsFrame [sourceAddress=0/0, destinationAddress=65535/0, profile=0000, cluster=0, addressMode=DEVICE, radius=31, apsSecurity=false, apsCounter=19, payload=00 00 4B 12 00 0C 49 3A 06 00 00]
13:03:14.477 DEBUG [pool-24-thread-4] ->  AF_DATA_REQUEST (Packet: subsystem=null, length=21, apiId=24 01, data=FE 15 24 01 FF FF 00 00 00 00 13 30 1F 0B 00 00 4B 12 00 0C 49 3A 06 00 00 27, checksum=27, error=false)
13:03:14.688 DEBUG [ZToolPacketParser] <-  AF_DATA_SRSP (FE 01 64 01 00 64)
13:03:22.472 DEBUG [pool-24-thread-2] Transaction timeout: NetworkAddressRequest [0/0 -> 65535/0, cluster=0000, TID=13, ieeeAddr=063A490C00124B00, requestType=0, startIndex=0]
13:03:22.484 DEBUG [pool-24-thread-4] 0: Node SVC Discovery NetworkAddressRequest returned null
13:03:22.487 DEBUG [pool-24-thread-4] 063A490C00124B00: Node SVC Discovery request NWK_ADDRESS failed. Retry 19, wait 15015ms before retry.
13:03:32.198 DEBUG [qtp946323269-110] Starting ZigBee scan for zigbee:coordinator_cc2531:15bff614
13:03:32.199 DEBUG [qtp946323269-110] Permit join to 65532/0 for 60 seconds.
13:03:32.200 DEBUG [qtp946323269-110] TX CMD: ManagementPermitJoiningRequest [0/0 -> 65532/0, cluster=0036, TID=14, permitDuration=60, tcSignificance=true]
13:03:32.201 DEBUG [qtp946323269-110] TX APS: ZigBeeApsFrame [sourceAddress=0/0, destinationAddress=65532/0, profile=0000, cluster=54, addressMode=DEVICE, radius=31, apsSecurity=false, apsCounter=20, payload=00 3C 01]
13:03:32.202 DEBUG [qtp946323269-110] ->  AF_DATA_REQUEST (Packet: subsystem=null, length=13, apiId=24 01, data=FE 0D 24 01 FC FF 00 00 36 00 14 30 1F 03 00 3C 01 18, checksum=18, error=false)
13:03:32.309 DEBUG [ZToolPacketParser] <-  AF_DATA_SRSP (FE 01 64 01 00 64)
13:03:32.311 DEBUG [qtp946323269-110] TX CMD: ManagementPermitJoiningRequest [0/0 -> 0/0, cluster=0036, TID=15, permitDuration=60, tcSignificance=true]
13:03:32.313 DEBUG [qtp946323269-110] TX APS: ZigBeeApsFrame [sourceAddress=0/0, destinationAddress=0/0, profile=0000, cluster=54, addressMode=DEVICE, radius=31, apsSecurity=false, apsCounter=21, payload=00 3C 01]
13:03:32.314 DEBUG [qtp946323269-110] ->  AF_DATA_REQUEST (Packet: subsystem=null, length=13, apiId=24 01, data=FE 0D 24 01 00 00 00 00 36 00 15 30 1F 03 00 3C 01 1A, checksum=1A, error=false)
13:03:32.525 DEBUG [ZToolPacketParser] <-  AF_DATA_SRSP (FE 01 64 01 00 64)
13:03:32.526 DEBUG [ZToolPacketParser] <-- ZToolPacket (FE 03 45 B6 00 00 00 F0)
13:03:32.527 DEBUG [ZToolPacketParser] Received Async Cmd: Packet: subsystem=null, length=3, apiId=45 B6, data=FE 03 45 B6 00 00 00 F0, checksum=F0, error=false
13:03:32.527 DEBUG [ZToolPacketParser] Unhandled ZToolPacket type 0x45b6
13:03:32.528 DEBUG [ZToolPacketParser] <-- ZToolPacket (FE 0A 45 FF 00 00 00 36 80 00 00 00 00 00 06)
13:03:32.528 DEBUG [ZToolPacketParser] Received Async Cmd: Packet: subsystem=null, length=10, apiId=45 FF, data=FE 0A 45 FF 00 00 00 36 80 00 00 00 00 00 06, checksum=06, error=false
13:03:32.529 DEBUG [ZToolPacketParser] RX APS: ZigBeeApsFrame [sourceAddress=0/0, destinationAddress=0/0, profile=0000, cluster=32822, addressMode=null, radius=0, apsSecurity=false, apsCounter=0, payload=00 00]
13:03:32.530 DEBUG [ZToolPacketParser] RX CMD: ManagementPermitJoiningResponse [0/0 -> 0/0, cluster=8036, TID=NULL, status=SUCCESS]
13:03:37.504 DEBUG [pool-24-thread-4] 063A490C00124B00: Node SVC Discovery running
13:03:37.516 DEBUG [pool-24-thread-4] TX CMD: NetworkAddressRequest [0/0 -> 65535/0, cluster=0000, TID=16, ieeeAddr=063A490C00124B00, requestType=0, startIndex=0]
13:03:37.520 DEBUG [pool-24-thread-4] TX APS: ZigBeeApsFrame [sourceAddress=0/0, destinationAddress=65535/0, profile=0000, cluster=0, addressMode=DEVICE, radius=31, apsSecurity=false, apsCounter=22, payload=00 00 4B 12 00 0C 49 3A 06 00 00]
13:03:37.525 DEBUG [pool-24-thread-4] ->  AF_DATA_REQUEST (Packet: subsystem=null, length=21, apiId=24 01, data=FE 15 24 01 FF FF 00 00 00 00 16 30 1F 0B 00 00 4B 12 00 0C 49 3A 06 00 00 22, checksum=22, error=false)
13:03:37.639 DEBUG [ZToolPacketParser] <-  AF_DATA_SRSP (FE 01 64 01 00 64)

Had tested both devices in Z-Tool. I got below info.

I got received data from router Unsupported or Unformatted received Raw data.

Thanks and Regards,
Amar.

Sorry - I don’t understand what you are doing? Why are you looking for “router” in the first place? The binding doesn’t support being configured as a router if that is what you are trying to do (I think we’ve discussed that previously)?

I am trying to send (switch ON or OFF) data from coordinator to end device. When we can get the channels to link the items. It’s my mistake configured as a router in Z-Tool . If I want to communicate with end device. I have to configure device as a end device instead of router

Sorry, but I really don’t understand what you are doing, or what your configuration is. You should not need to use ZTool for the coordinator - this should be configured by the binding. If you are also trying to produce your own end-device, or router, then this is another issue and also not related I think to the binding.

I am not particularly familiar with the TI ecosystem as I mostly work with Silabs devices, so I can’t really help too much - sorry.

Thanks @chris,

Now I understood.How to get the channels to link the items. How to start the discover process.

Hi @chris,

How to discover the devices from paper ui. How the bindings are will recognize the devices.

Best Regards,

Amar.