64 October 2014
(Extended Unique Identifier).
Okay, it’s time to throw the meat into the HAN. I sent
the ZigBee Gateway a command to form a new PAN
which to our HA nodes will become our new HAN. The
official PAN construction orders can be seen in
Screenshot 10. I took the easy way out and left the PAN
creation details up to the data radio firmware. After
confirmation that the PAN had been created, I flipped the
“you can join my PAN” bit. In the meantime, I attached
the FFD node to a Telegesis Terminal session. Knowing
that a PAN was already in existence, I simply instructed
the FFD node to join the first available one. These orders
are displayed in Screenshot 11.
Once becoming a member of the ZigBee
Communications Gateway’s PAN, the Five-In-One FFD is
assigned a Node ID (51DB in Screenshot 10). The
Gateway is also now privy to the new member’s EUI,
which can also be seen in the FFD’s response in
Screenshot 10. We are finally at “home” and we’re
cooking with gas!
While We’re Here
Let’s see what we can find out about Node 51DB.
From the Telegesis HA documentation and the obvious
name, we know our Five-In-One FFD has five endpoints.
So, let’s send the AT command sequence you see in
Screenshot 12 to query the first endpoint of Node 51DB.
The IDENTIFY command is aimed at Node 51DB/endpoint
01 for 60 seconds. If the command is issued correctly and
is valid at the receiver, a default response (DFTREP) is
returned. In this case, the responding node is 51DB and
the response emanates from endpoint 01. The associated
cluster is 0003. The trailing zeros indicate a valid response.
Hmmmm. I issued the same command for all five
endpoints and received identical default responses with
only the responding endpoint field changed. So, if I didn’t
already know, I would say that Node 51DB contains five
endpoints that associate to cluster 0003. Einstein would
try to prove his theory. So will I.
With that, I issued the command sequence you see in
Screenshot 13. The DISCOVER command will query every
node in the HAN that has a cluster 0003. In our case,
there is only one node in our HAN (51DB). Its default
response to our DISCOVER query lists five endpoints.
; Screenshot 10. I let the
Gateway do all of the PAN
Once the PAN was up, I
turned on the "allow
you to join my PAN" bit.
; Screenshot 9. We're in! The ATI command forces
the ZigBee Communications Gateway to furnish some
of its vital ZigBee data radio settings. Here, the radio
module is revealed along with the firmware version
and the data radio's 64-bit EUI.
; Screenshot 12.
responses and patterns is
very important to
determining what is going
on inside of the Five-In-One
FFD. In this case, we will
find that the cluster
(0x0003) is common to the
; Screenshot 11. Normally,
we would issue an
AT+PANSCAN command to
search for available PANs.
In this case, we are in total
control and know there is a
PAN out there waiting for
us to join.