EmberZNet serial protocol
SN260
7.2.8
7.2.9
SN260 status
The frame control byte of every response sent by the SN260 contains two status bits:
● The overflow bit is set if the SN260 ran out of memory at any time since the previous
response was sent. If this bit is set, then messages may have been lost.
● The truncated bit is set if the SN260 truncated the current response. If this bit is set, the
command from the Host produced a response larger than the maximum EZSP frame
length.
You can use the nop command to check the status of the SN260 without also performing
another action.
Random number generator
The Host can obtain a random number from the SN260 using the getRandomNumber
command. The random number is generated from analog noise in the radio and can be
used to seed a random number generator on the Host.
7.3
Protocol format
All EZSP frames begin with a frame control byte. Table 18 describes the meaning of this
byte for command and response frames. Table 19 describes the sleep modes, Table 20
describes the overflow status bit and Table 21 describes the truncated status bit. The
second byte of all EZSP frames is the frame ID byte.
Table 18. Frame control byte
Bit
Command
7 (MSB)
0
6
0 (reserved)
5
0 (reserved)
4
0 (reserved)
3
0 (reserved)
2
0 (reserved)
1
sleepMode[1]
0 (LSB)
sleepMode[0]
Response
1
0 (reserved)
0 (reserved)
0 (reserved)
0 (reserved)
0 (reserved)
truncated
overflow
Table 19. Sleep modes
sleepMode[1]
1
1
0
0
sleepMode[0]
1
0
1
0
Description
Reserved.
Power down.
Deep sleep.
Idle.
38/88