User's Manual

RAEMesh2 RMCI Protocol
Doc.No. 904-E800-316 Rev.No. A
Date: 10/14/10
Page
8 of 9
For Internal Use Only
RAEMesh and RAEMeshII Difference
Item RAEMesh RAEMeshII Description
Hardware MCU:
ATMEGA128L
Radio: EM2420
MCU: ATMEGA1281V
Radio: AT86RF212,
AT86RF230,
AT86RF231
N/A
Stack Ember Zigbee
Stack
Atmel Bitcloud N/A
Specification Zigbee 2004 Zigbee Pro Owing to the difference of specification,
RAEMesh and RAEMeshII can’t inter-
communication
Power Failure Support Un-support In RAEMesh, all device can save their child
or neighbor table into eeprom.
RAEMeshII can’t support this feature, so
they should re-form or re-join by themselves
after reset.
RSSI Router/RTR update
RSSI when it
receive every
frame.
Router/RTR read next
hop’s RSSI.
Next hop is that Router/RTR send frame to
GTW through next hop’s routing.
Many-to-one
routing(MTOR)
Support Un-support In RAEMesh, GTW manage MTOR
periodically and automatically.
In RAEMeshII, Router need to do route
discovery and maintenance by themselves.
EUI Set it on
RangeTest.
Set it on application
firmware.
N/A
Transmission
power
Always is
maximum.
There are three level to
be choose.
In RAEMeshII, high, medium and low
represent different txpower on different
platform.
Bootloader Provide by Ember Provide by Atmel N/A
Warm up time time scale of
milliseconds
More than five seconds N/A