RC11xx(HP)-TM
RC25xx(HP)-TM
RC17xx(HP)-TM
2016 Radiocrafts AS
RC11xx(HP)/25xx(HP)/17xx(HP)-TM Data Sheet rev. 1.48 Page 20 of 86
2016 Tiny Mesh AS
Radiocrafts
Embedded Wireless Solutions
Bit
No
Bit
Val-
ue
De-
fault
Name
Applies
to
Function
Gateway
transmission.
CTS will be driven high immediately before the first start-bit is transmitted,
and will return low immediately following the last stop bit from the UART.
3
8
0
Xon/Xoff
Router
and
Gateway
When the Xon/ Xoff function is enabled, the module UART will transmit an
Xoff character (Value 0x13, ASCII DC3) a settable number of bytes
(SERIAL BUFFER FULL MARGIN) before the buffer runs full. The external
host MCU should then halt further data transfer until an Xon (0x11, ASCII
DC1) character has been received. An Xon character will be transmitted
continuously at 1 second intervals while the module is ready to receive
data.
The Gateway Device will only support Xon/ Xoff when in transparent
mode. Please also note that binary data transfer will not work with Xon/
Xoff, as the binary data may contain the Xon / Xoff characters.
4
16
0
ACK/
NAK
Gateway
When enabled, the Gateway Device will answer any received data on the
serial port with a COMMAND RECEIVED AND EXECUTED or a
COMMAND REJECTED, NOT EXECUTED message. In this mode, the
Gateway will do a format- and validity control of received commands
before transmitting in the RF mesh network.
The MESSAGE DATA MSB will contain the user selected Command
Number.
If the packet is not accepted by the Gateway Device, the MESSAGE DATA
LSB in the returned COMMAND REJECTED, NOT EXECUTED message
will indicate why the packet was not accepted.
5
32
0
Wait For
ACK
Gateway
When enabled, the Gateway Device will expect an ACK character (0x06,
ASCII ACK) response to any packet delivered to the host. If the ACK is not
received within a 1second time frame, the packet will be repeated until a
valid response has been received.
6
64
Reserved
7
128
Reserved
AES Encryption
Changing the
SECURITY LEVEL
parameter in
CONFIGURATION MEMORY
will enable automatic AES data
encryption. When AES encryption is enabled, the payload portion of all RF data packets are encrypted
using the 128 bit AES encryption algorithm.
The Gateway and Router Device must share a common AES key, settable by the
SETTING AND
CHANGING THE AES KEY (K7- COMMAND)
.
The encryption key is stored in a hidden and secure memory location.
The AES key is retained even after an @TM factory reset command.
Encrypted and unencrypted Router Devices may co-exist and will connect to a common network. A
Gateway Device will be able to receive data from encrypted, as well as unencrypted, Router Devices,
but an unencrypted Router Device will not be able to receive and interpret encrypted commands.
Co-Existence with AES Encrypted and Un-Encrypted Devices
Nodes with encryption enabled, may co-exist with unencrypted nodes in a common system. Encrypted
data packets are slightly larger than unencrypted packets.
SECURITY LEVEL
2 (Compatible mode) is
provided for backwards compatibility to field deployed systems where encryption has not been enabled.
In systems with a mixture of encrypted and unencrypted nodes, the following rules will apply:
•
Encrypted packets will be transported by unencrypted nodes to their final destination.
•
Un-encrypted packets will be transported by encrypted nodes to their final destination.
•
Encrypted nodes will not accept receipt of unencrypted packets (commands or serial out
packets)
•
Un-encrypted nodes will not accept receipt of encrypted packets (commands or serial out
packets)
•
An encrypted Gateway will accept and decrypt messages from encrypted nodes, as well as
accept data packets from unencrypted nodes.
•
An un-encrypted Gateway will only accept messages from un-encrypted nodes.
