Linx EVM-900-PRO, Руководство по данным

Страница: 21 / 61

– – – –
36 37
A module is set as an administrator by pressing and holding the button for
30 seconds to start the Generate Key function. While the button is held, the
MODE_IND line is on. After 30s, the MODE_IND line repeats a double blink,
indicating that the function has begun. When the button is released the key
and address generation are complete and the module is an administrator.
When Generate Key is performed, the unit is set as the network
administrator. It generates a random 128-bit AES encryption key based on
ambient RF noise and scrambled by an encryption operation. If UMASK
is the default value (0xFFFFFFFF), it is set to 0x000000FF, supporting
up to 255 nodes, and ADDMODE is set to Extended User Address
with encryption (0x27) (or without encryption (0x07) if flag PGKEY in the
SECOPT register is 0). UMASK and ADDMODE are not changed if UMASK
is not 0xFFFFFFFF. A random 32-bit address is generated. By default, the
lower 8 bits are 0, forming the network base address. Other nodes are
assigned sequential addresses, starting with network base a1.
UDESTID is set to the bitwise OR of USRCID and UMASK, which is the
network broadcast address.
A module becomes a node by joining with an administrator. This is done
by pressing and releasing the PB button on both units. The modules
automatically search for each other using a special protocol. When they
find each other, the administrator sends the node the encryption key,
UMASK and its network address. The UDESTID is set to the address of the
administrator. The values are encrypted using a special factory-defined key.
Once the JOIN process is complete, the MODE_IND blinks on both units
and they now operate together. This is shown in Figure 30 A.
If UMASK is pre-set when Generate Key is initiated, then the JOIN process
uses that mask and sets the address accordingly. This can allow more
nodes in the network. This is shown in Figure 30 B. Likewise, the network
key can be written to the module with the CDI interface and the JOIN
process used to create an address and associate new modules. Or the
administrator can be completely configured through the CDI and the
JOIN process used to associate nodes in the field. This gives the system
designer many options for configuration.
The SECOPT register is used to configure options related to the JOIN
process. This allows the OEM to set desired values at the factory and allow
final network configuration in the field. This includes disabling the ability to
change the address, change the key and share the key. The built-in security
prohibits changing a node to an administrator without changing the key.
D
UMASK = FF FF FF FF
USRCID = FF FF FF FF
UDESTID = FF FF FF FF
No Key
A
UMASK = 00 00 00 FF
USRCID = 76 54 32 00
UDESTID = 76 54 32 FF
Network Key
Generate Key
D
UMASK = FF FF FF FF
USRCID = FF FF FF FF
UDESTID = FF FF FF FF
No Key
N
UMASK = 00 00 00 FF
USRCID = 76 54 32 0 1
UDESTID = 76 54 32 00
Network Key
JOIN
A
UMASK = 00 00 00 FF
USRCID = 76 54 32 00
UDESTID = 76 54 32 FF
Network Key
P
UMASK = 00 00 0F FF
USRCID = FF FF FF FF
UDESTID = FF FF FF FF
No Key
A
UMASK = 00 00 0F FF
USRCID = 76 54 30 00
UDESTID = 76 54 3F FF
Network Key
Generate Key
D
UMASK = FF FF FF FF
USRCID = FF FF FF FF
UDESTID = FF FF FF FF
No Key
N
UMASK = 00 00 0F FF
USRCID = 76 54 30 0 1
UDESTID = 76 54 30 00
Network Key
JOIN
A
UMASK = 00 00 0F FF
USRCID = 76 54 30 00
UDESTID = 76 54 3F FF
Network Key
Key Generation and Network Join from Factory Default
Key Generation and Network Join from Preset Mask
A)
B)
Figure 30: HumPRO-A
TM
Series JOIN Process
D = Factory Default
A = Network Administrator
N = Network Node
P = OEM Preset Unit