RAE Systems RM2400A RAEMesh Radio User Manual RAEMeshII
RAE Systems, Inc RAEMesh Radio RAEMeshII
SU3RM2400A_User Manual rev1
| Download: |  |
| Mirror Download [FCC.gov] | |
| Document ID | 1510964 |
| Application ID | 1TOqpIf3R3WWGjLtYx35VA== |
| Document Description | SU3RM2400A_User Manual rev1 |
| Short Term Confidential | No |
| Permanent Confidential | No |
| Supercede | No |
| Document Type | User Manual |
| Display Format | Adobe Acrobat PDF - pdf |
| Filesize | 133.44kB (1668054 bits) |
| Date Submitted | 2011-07-27 00:00:00 |
| Date Available | 2011-07-29 00:00:00 |
| Creation Date | 2011-06-02 13:51:42 |
| Producing Software | Acrobat Distiller 6.0 (Windows) |
| Document Lastmod | 2011-06-02 13:51:42 |
| Document Title | Microsoft Word - RAEMeshII User Manual.doc |
| Document Creator | PScript5.dll Version 5.2.2 |
| Document Author: | jliu |
Revision: June 2, 2011
RAEMesh Radio User Manual
(for RM2400, RM900…)
RAE Systems Inc
Revision: June 2, 2011
Introduction
The RAEMesh Radio module offers a complete microcontroller/transceiver solution Containing all hardware features
necessary for development of a low data-rate, low-power wireless application. The primary components include an IEEE
802.15.4 compliant Zigbee-ready transceiver , a microcontroller, a 40-pin interface connector, a MMCS antenna
connector,
This documentation describes the RAEMesh radio module hardware interface as well as RAE System’s Command
Interface.
Hardware
Specifications
Frequency Band
802.15.4 standard.
RM2400:16 channels of operation in the 2.4GHz world wide ISM band. 5MHz
channel spacing.
RM900: 11 channels. 868, 906,908……924Mhz
Power
+3.3V + .3V from carrier board, 3.0V to 3.6V from battery pack
Interfaces
40-pin surface-mount 2x20 1.27mm pitch
RF
250kbps OQPSK Direct Sequence Spread Spectrum.
Dimensions
46.5 mm x 26 mm x 10 mm
Antenna Interface
50-Ohm MMCX female
Operating Temperature Range
-40ºC to +85ºC
Indicators
Two LEDs, one red, one yellow (DS1, DS2)
Current Consumption
0.5 µA Sleep
120 mA TX @ 18 dBm
25 mA RX / Idle
RF receive sensitivity
-100dBm at at 1% packet error rate for a 20 byte payload.
Output Power EIRP
Up to 18dBm
Data Rate
250 kbps
Antenna
Omnidirectional antenna, 3.5dBi max.
Revision: June 2, 2011
Mechanical Size:
Top View
The height of the shielding box is 4.3mm from the PCB.
40 Pin header (1.27mm) is used for board to board connection. Corresponding mate connector can be JVE
22P8702-40M00B-01G-4.5
Revision: June 2, 2011
Pin Layout
Pin
11
13
15
17
19
21
23
25
27
29
31
33
35
37
39
Description
DGND
nRESET
TXD1
RXD1
GPIO0
GPIO1
GPIO2
GPIO3
TEMP_E/GPIO4
WakeUp/GPIO5
BUZZER/GPIO6
GPIO7/PS_DIR
BUTTON0/GPIO8
BUTTON1/GPIO9
GPIO10
RF_SO
RF_SI
RF_CK
SFD
+3.3V
Pin
10
12
14
16
18
20
22
24
26
28
30
32
34
36
38
40
Description
DGND
DGND
TXD0/Bootload.
RXD0
GPIO/LED2
GPIO/LED3
GPIO/LED4
GPIO/LED5
GPIO/PS_CS
GPIO/PS_FRAME
+3.3V
AGND
AREF
ATEMP/ADC1
ADC2
TCK
TMS
TDO
TDI
+3.3V
Revision: June 2, 2011
Firmware Description
The module is pre-loaded with the bootloader, which supports serial bootloading of firmware update. The
module contains RAEMesh application and comply with the RAE System’s RCS protocol. The module also has
built-in RAEMesh Module Command Interface(RMCI).
This documentation is focused on the instruction on RMCI interface.
The RMCI command interface allows customer to easily access to low level mesh functionality without pain to
develop the firmware. The module can be configured to a GTW to hook up to a getaway or just a stand alone
regular full function node or a Sleepy reduce function node.
Make sure to configure the module to right mode before using.
Quick Start
UART
Via the TXD1 and RXD1 pins the command interpreter can be accessed. The RCM can buffer up to 128 bytes of incoming
data in a software FIFO buffer and uses XON/XOFF flow control. See the datasheet of the Atmel ATmega1281 for more
information about the build-in UART.
Connect Pin5 (TXD1) and Pin7 (RXD1) to the customer board. Use the following settings for serial port.
RTR and STD: 19200bps, 8N1.
GTW: 38400bps, 8N1.
Data Packet
RCM will transmit any data in the { }, all data in the {} will be transparently sent out without radio’s interpretation. The
maximum data packet is 50 bytes including {}.
The data in the {} can be any characters including ‘{‘ ‘}’ ’[‘ ’]’ .
The interval between 2 data packets must be >200ms for RTR and GTW.
The interval between 2 data packets must be >1s for STD.
Wakeup
If the radio is set to STD mode, the Wakeup pin Pin19 (PE7) is used to make the radio asleep and wakeup. A constant
high on this pin will let the radio go to the sleep mode and a low level signal on this pin will wake-up the radio.
The Radio sleep mode is the power save mode so the power consumption can be very low. (<40uA)
The Wakeup pin must be held up to 10ms before sending a data packet.
Power
Ground: Pin1, Pin2 and Pin4.
VCC: Pin39, Pin40. 3.0V or 3.3V
Radio consumes less than 100mW in normal RX/TX mode.
Radio consumes 600mW at TX and 100mW at RX for High power module
Heartbeat
Connect Pin12 to a LED for heartbeat indicator.
Revision: June 2, 2011
Reset.
RST: Pin3 Active Low.
PC communication
Please has your serial port debug software installed on the PC. For example: sscom32.exe
Microsoft Hyper Terminal is not recommended for this application because it is not good to send characters and
commands in Hex.
Base on correct setting and connection, you will see following display on your screen when power is applied.
GTW:
[%A ]RAEMESH-II RM2400A 8MHz
FwVer:1.10.0.03 on Oct 29 2010 14:16:08
Type: Coordinator/Gateway
EUI: 0001000024006001
Channel: 0x10
TxPwr: High
PanId: 0x0026
RTR:
[%A ]RAEMESH-II RM2400A 4MHz
FwVer:1.10.0.03 on Oct 29 2010 14:17:15
Type: FFD/Router
EUI: 0001000024006001
Channel: 0x10
TxPwr: High
PanId: 0x0026
STD
[%A ]RAEMESH-II RM2400A 4MHz
FwVer:1.10.0.03 on Oct 29 2010 14:17:15
Type: RFD Sleep Sensor
EUI: 0001000024006001
Channel: 0x10
TxPwr: High
PanId: 0x0026
Revision: June 2, 2011
RAEMesh2 Module Command Interface (RMCI)
Format:
SOP
Byte:
Length
Command Code
Command Data
0~n
EOP
Byte Number
Name
Comment
SOP
Radio Protocol beginning of packet. This is always ‘[‘ (0x5B)
Length
Total length of packet + 0x20, include ‘[‘ and ‘]’.
Command Code
0x20 ~ 0xFF. Excluding:0x5A~0x5F and 0x7A~0x7F. 0xF0~0xFF are
reserved for common commands.
Even for packet sent from SDTE or RDTE to RCM.
Odd for packet response from RCM to SDTE or RDTE.
Command Data
…
…
N+3
EOP
Hex
Radio protocol end of packet.. This is always ‘]’(0x5D)
The minimum length for one packet is 4 bytes long. The Length is 0x20 based. E.g. the total length of a packet without
command data is 4, the Length byte is 0x20 + 4 = 0x24.
The SDTE or RDTE always initiate the communication with Radio module (RRCM, SRCM). Radio Module responses to
the command it received.
The Command Code for packet sent from SDTE or RDTE to Radio module is even, the response from Radio module to
SDTE or RDTE is 1 higher than the command code.
Command Data can be empty.
No command for 0x5A~0x5F and 0x7A~0x7F.
A Section 0xF0~0xFF is reserved for common commands such as help, Version etc.
Caution: the maximum packet length from SOP to EOP is 64 bytes.
Notes:
1.
2.
3.
4.
5.
All commands response in 50ms
Check RCM’s information when turn on the radio. Command: 5B 24 60 5D.
Wait at least 5s for RCM to finish the initialization after power on.
Check the network status of the STD before sending the data for first time. Command: 5B 24 20 5D.
It is recommend to add 1s interval between 2 data packets for STD. Check 0x5b 24 27 5d for sending
acknowledge with successfully. There is no ACK for transmission failed.
6. For STD, if there is no network, the RCM will automatically wake up every 10 minute to search for a new network.
It can be interrupted any time. RCM will keep in asleep if it has joined a network.
RAEMesh2 RMCI Protocol
Doc.No. 904-E800-316
Rev.No. A
Date: 10/14/10
Page 8 of 9
RAEMesh and RAEMeshII Difference
Item
RAEMesh
RAEMeshII
Hardware
MCU:
ATMEGA128L
Radio: EM2420
Stack
Specification
Ember Zigbee
Stack
Zigbee 2004
MCU: ATMEGA1281V
Radio: AT86RF212,
AT86RF230,
AT86RF231
Atmel Bitcloud
Power Failure
Support
RSSI
Router/RTR update
RSSI when it
receive every
frame.
Support
Many-to-one
routing(MTOR)
EUI
Zigbee Pro
Un-support
Router/RTR read next
hop’s RSSI.
Un-support
Transmission
power
Set it on
RangeTest.
Always is
maximum.
Set it on application
firmware.
There are three level to
be choose.
Bootloader
Provide by Ember
Provide by Atmel
Warm up time
time scale of
milliseconds
More than five seconds
For Internal Use Only
Description
N/A
N/A
Owing to the difference of specification,
RAEMesh and RAEMeshII can’t intercommunication
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.
Next hop is that Router/RTR send frame to
GTW through next hop’s routing.
In RAEMesh, GTW manage MTOR
periodically and automatically.
In RAEMeshII, Router need to do route
discovery and maintenance by themselves.
N/A
In RAEMeshII, high, medium and low
represent different txpower on different
platform.
N/A
N/A
RAEMesh2 RMCI Protocol
Doc.No. 904-E800-316
Rev.No. A
Date: 10/14/10
Page 9 of 9
Command List of RMCI
5B
5B
5B
5B
5B
5B
5B
5B
5B
24
xx
24
24
24
24
24
24
24
20
26
2A
3A
60
6C
68
7B
40
5D
dd
5D
5D
5D
5D
5D
5D
5D
= Get
dd 7B
= Get
= Get
= Get
= Get
= Get
= Get
= Get
network status
.. .. 7D 5D = Send massage in unicast
Radio Type
device application type
Radio's UID, channel, PANID
Application's UID, channel, PANID
parent Network ID
Last Hop Link Quality (LQI)
reset reason.
5B 24 30 5D = Enable GTW function
5B 24 32 5D = Enable RTR function
5B 24 46 5D = Enable STD function
5B 24 4A
5B 25 34
America,
5B 25 A0
5B 24 A2
5B 25 A4
5B 24 A6
5B 25 3C
0x00 for
5B 26 44
5B 2C 4E
5D = Restore the radio to factory setting
xx 5D = Set channel number, xx( 0x00 for EURO, 0x01-0x0A for North
0x0B-0x1A for ISM)
xx 5D = Enable receiver while idle on STD.
5D = Get receiver on/off on STD.
xx 5D = Set region.
5D = Get region.
xx 5D = Set Tx power, xx(0xFF for maximum, 0x80 for middle, and
minimum)
xx xx 5D = Set PanId, xxxx(0x0000-0x03E7)
xx xx xx xx xx xx xx xx 5D = Set MAC/UID address
5B
5B
5B
5B
5D
5D
xx
5d
24
24
26
24
3E
50
42
52
= Leave current network
= Join or form network by scan.
xx 5D = Set routing discovery interval
= Get routing discovery interval
5B 24 38 5D = Report node’s position
5B 24 48 5D = Soft reset
5B 25 FE xx 5D = Set print debug info, xx(00-disable; 01-enable)
For Internal Use Only
RAEMesh2 RMCI Protocol
Doc.No. 904-E800-316
Rev.No. A
Date: 10/14/10
Page 10 of 9
z Command Sets:
Command Name
Effect
Area
CMD
Code
CMD
Data
(bytes)
None
Response
CMD Code
0x21
Response
CMD
Data(Bytes)
STATUS(1)
DestNw
kID(2)
RCS
Pack(x)
0x27
None
None
0x2B
NETWORK_STATU Both
Use on:
GTW
RTR
STD
0x20
SEND_MSG_UNI RAEMesh
Use on:
GTW
RTR
STD
GET_MODULE_TY Both
PE
Use on:
GTW
RTR
STD
0x26
GTW_ENABLE
Both
0x30
None
0x31
None
Use on:
GTW
RTR
STD
RTR_ENABLE
Both
0x32
None
0x33
None
Use on:
GTW
RTR
STD
CHG_RRCM_CHA Both
0x2A
Description
Return the radio’s network status
0x00: NO NETWORK
0x02: JOINED NETWORK.
Host controller or instrument
should call it periodically with
certain duty cycle to check the
network status.
Send message in unicast mode.
NwkAddr: Network address
Message must in RCS format.
Type(1)
Return the radio’s type.
Type:
0: Bluetooth
1: coRE3-433MHz
2: coRE3-868MHz
3: coRE3-915MHz
4: ZcoRE3-2400
5: UART to Ethernet
6: UART to RS485
7: RM2420
8: RM900
9: Reserve
10: RM2400
11: coRE1-433MHz
12: coRE1-868MHz
13: coRE1-915MHz
14: coRE2-433MHz
15: coRE2-868MHz
16: coRE2-915MHz
17: coRE6-2.4GHz
Set the radio as a GTW so that
the radio can be use on a
Gateway device.
Baud rate change to 38400 8N1
Reset automatically.
Set radio to RTR. Always on and
has router function.
Baud rate change to 19200 8N1
Reset automatically.
0x34
Channel
0x35
For Internal Use Only
None
Requests change radio channel
N
Use on:
GTW
RTR
STD
RAEMesh2 RMCI Protocol
Doc.No. 904-E800-316
Rev.No. A
Date: 10/14/10
Page 11 of 9
Number
(1)
to specified channel. Meanwhile,
specified channel should be
compliance with radio region
setting.
0x00 for RM900 if region is
BAND_868_EU.
0x01 to 0x0A total 10 channels
for
RM900
if
region
is
BAND_915_NA.
0x0B to 0x1A total 16 channels
for
RM2400
if
region
is
BAND_2400_ISM.
Both
0x38
None
0x39
None
Both
0x3A
None
0x3B
AppType(1)
SET_TX_POWER Both
Use on:
GTW
RTR
STD
0x3C
TxPwr(1
0x3D
None
RPT_LOCATION
Use on:
GTW
RTR
STD
GET_APPTYPE
Use on:
GTW
RTR
STD
If channel number is not
compliance with radio region, do
not return response CMD.
Reset automatically.
Print node’s network information
in ASCII.
Get application type.
AppType:
1 – GTW;
2 – RTR;
3 – Reserved;
4 – STD;
5 – Reserved;
other - invalid
Set modem transmission power
level.
For RAEMeshII
0xFF – maximum level,
0x80 – middle level,
0x00 – minimum level,
For RAEMesh
Power setting from 0xE3(-25dBm)
to 0xFF(0dBm).
LEAVE_NETWORK Both
Use on:
GTW
RTR
STD
0x3E
None
0x3F
For Internal Use Only
None
Reset automatically.
Leave the current network.
RST_REASON
Use on:
GTW
RTR
STD
Both
SET_ROUTEINTER RAEMeshII
VAL Use On:
RTR
RAEMesh2 RMCI Protocol
Doc.No. 904-E800-316
Rev.No. A
Date: 10/14/10
Page 12 of 9
0x40
None
0x41
Reason(1)
0x42
Type(1)
Interval(
1)
0x43
None
Below just list RAEMeshII reset
reason,
0x00 = UNKNOW,
0x01 = RESET_ EXTERNAL,
0x02 = RESET_ POWERON_,
0x03 = RESET_ WDT,
0x04 = RESET_BROWNOUT,
0x05 = RESET_JTAG,
0x06 = RESET_WARM,
Type(1)
Bit7~bit2: reverse,
Bit1: enable route discovery
immediately if set,
Bit0: set route discovery
interval with the value of
Interval(1).
Interval(1)
Routing interval, range is
from 10 to 240, unit is second.
If RTR/Router lost connection
with its next hop, it should route
discovery periodically as per the
value of Interval(1).
CHG_PAN_ID
Use on:
GTW
RTR
STD
STD_ENABLE
Use on:
GTW
RTR
STD
SOFT_RESET
Use on:
GTW
RTR
STD
FACTORY_RST
Use on:
GTW
RTR
STD
Both
0x44
PanID:(
2)
XXXX
0x45
None
Change GTW Pan ID into XXXX.
From 0x0001 to 0x03E7(1-999)
Reset automatically.
Both
0x46
None
0x47
None
Both
0x48
None
0x49
None
Put a node into STD. Interrupt
enable and active low.
Baud rate change to 19200 8N1
Reset automatically.
Perform soft reset.
Reset automatically.
Both
0x4A
None
0x4B
None
Restore the RCM to factory
defaults.
PanId: 0x03E7, Device Type:
STD.
For RM2400, channel is 0x0f and
txpower is -6dBm and 17dBm
through power amplifier.
For RM900, TBD
Reset automatically.
For Internal Use Only
SET_RECEIVER
Use on:
STD
RAEMeshII
0xA0
RAEMesh2 RMCI Protocol
Doc.No. 904-E800-316
Rev.No. A
Date: 10/14/10
Page 13 of 9
00
Disable
01
Enable
0xA1
None
Enable or disable STD’s receiver.
STD should receive data packet
from parent if enable receiver;
STD should use poll to request
data packet from parent if disable
receiver.
GET_RECEIVER
Use on:
STD
RAEMeshII
0xA2
None
0xA3
Status(1)
SET_REGION
Use on:
GTW
RTR
STD
RAEMeshII
0xA4
Region(
1)
0xA5
None
Reset automatically.
Return STD receiver’s status,
00 – Disable
01 - Enable
Region(1)
BAND_868_EU = 0x01,
BAND_915_NA = 0x04,
BAND_2400_ISM = 0x08,
For RM2400, this command is
useless because RM2400 always
work on BAND_2400_ISM.
For RM900, default channel is
0x00
if
set
region
to
BAND_868_EU; default channel
is 0x06 if set region to
BAND_915_NA.
GET_REGION
Use on:
GTW
RTR
STD
SET_UID
Use on:
GTW
RTR
STD
Reset automatically.
Get modem setting of region.
RAEMeshII
0xA6
None
0xA7
Region(1)
RAEMeshII
0x4E
UID(8)
0x4F
None
JION_FORM_NET Both
WORK
Use on:
GTW
RTR
STD
0x50
None
0x51
None
GET_ROUTEINTE RAEMeshII
RVAL
Use on:
RTR
GET_NODE_INFO Both
Use on:
0x52
None
0x53
Interval(1)
RTR/STD: Search the network
using customized PANID and try
to join the network.
Return the routing interval.
0x60
None
0x61
UID(8)
Channel(1)
Get the node information: UID,
Channel, Txpower level,, PAN ID,
For Internal Use Only
Set radio’s UID(MAC address).
Note:
The last two bytes must not set
to 0x0000, 0xFFF0-0xFFFF
Reset automatically.
GTW: Form a network using
customized PANID to allow the
other nodes to join.
GTW
RTR
STD
GET_APPNODE_I Both
NFO
Use on:
GTW
RTR
STD
GET_PARENT_ID Both
Use on:
RTR
STD
RAEMesh2 RMCI Protocol
Doc.No. 904-E800-316
Rev.No. A
Date: 10/14/10
Page 14 of 9
Power(1)
PAN ID(2)
0x6C
None
0x6D
UID(8)
Channel(1)
Power(1)
PAN ID(2)
0x68
None
0x69
Parent radio
ID(8)
LAST_HOP_RSSI Both
Use on:
RTR
STD
0x7B
None
0x7C
RSSI(1)
SET_DEBUG_PRIN Both
Use on:
GTW
RTR
STD
0xFE
00,Disa
ble
01,Enab
le
0xFF
None
GET_FWVERSION Both
Use on:
GTW
RTR
STD
0x4C
None
0x4D
Fw Version
and
Build
Time[30]
Return fw version and build time,
for example
[BMv1.00
Feb
14
2011
10:11:11], this mean fw version is
V1.00 and build is on Feb 14
2011 10:11:11.
SET_CMDBATCH RAEMeshII
Use on:
GTW
RTR
STD
0xAC
00,
Disable
01,
Enable
0xAD
None
GET_CMDBATCH RAEMeshII
Use on:
GTW
RTR
STD
0xAE
None
0xAF
00,
Disable
01,
Enable
Enable or disable command
batch function. If enable, modem
will not reset automatically after
change panid, channel, power,
eui, region and receiver. They will
take effect after reset manually.
Batch function will disable after
reset.
Return
command
batch
configuration.
For Internal Use Only
Get the application information:
UID, Channel, Power, PAN ID. If
the network is not connected, the
GET_NODE_INFO will return
wrong information, and then use
this to get what we set.
0x00 00 00 00 00 00 00 00
means that STD or RTR’s parent
is coordinator/gateway.
0x00 00 00 00 00 00 mm nn
means STD or RTR’s parent is a
RTR which short address is mm
nn.
0x00 00 00 00 00 00 ff fe means
that STD or RTR do not have
parent.
Get RSSI percent, the higher, the
better.
Best: 240
Worst:0
RTR get next hop rssi;
STD get parent rssi.
Set display debug information
enable/disable.
The default setting is disabled.
RAEMesh2 RMCI Protocol
Doc.No. 904-E800-316
Rev.No. A
Date: 10/14/10
Page 15 of 9
Caution: RCM will save corresponding command data of AT command into its persist data server if this
command cause “Reset automatically”, it will take effect after reset.
z Command Sets for RAEMeshII
ITEM
CMDS
MUST
RECOMMENED
OPTIONAL
GET_APPTYPE
GET_MODEM_TYPE
FACTORY_RST
NETWORK_STATUS
SET_TXPOWER
SET_DEBUG_PRINT
GET_APPNODE_INFO
RST_REASON
GTW_ENABLE
SEND_MSG_UNI
RTR_ENABLE
SET_UID
STD_ENABLE
SET_REGION
SET_PANID
SET_RECEIVER
JOIN_FORM_NETWORK
LEAVE_THE_NETWORK
SET_CHANNEL
GET_PARENT_ID
LAST_HOP_RSSI
For Internal Use Only
RAEMesh2 RMCI Protocol
Doc.No. 904-E800-316
Rev.No. A
Date: 10/14/10
Page 16 of 9
Procedure for Radio Core Setting:
A. Configure ATMega1281 Fuse. Software: AVRUSB V2.0.2.231, Hardware: AVRUSB ISP on M3 Eva Board.
1. Make sure the correct hardware selected
2. Click “Reset”, make sure the AVRUSB connected to target
3. Read out current Fuse setting first
For Internal Use Only
RAEMesh2 RMCI Protocol
Doc.No. 904-E800-316
Rev.No. A
Date: 10/14/10
Page 17 of 9
4. Check the following settings and make sure as same as showed
For Internal Use Only
RAEMesh2 RMCI Protocol
Doc.No. 904-E800-316
Rev.No. A
Date: 10/14/10
Page 18 of 9
5. Write back Fuse setting if any changes made, make sure program successfully
For Internal Use Only
RAEMesh2 RMCI Protocol
Doc.No. 904-E800-316
Rev.No. A
Date: 10/14/10
Page 19 of 9
For Internal Use Only
RAEMesh2 RMCI Protocol
Doc.No. 904-E800-316
Rev.No. A
Date: 10/14/10
Page 20 of 9
B. Firmware Program. Software ZigBit Firmware Programmer V1.32
1. Select firmware file, *.srec
2. Select correct com port
3. Click “Program”, then Reset RAEMesh2 module in 30 seconds
4. Waiting for program successful.
C. Configure RAEMesh2 Application. Software SSCOM32.exe, RMCI.
1. Set UID/MAC address
5B 2C 4E xx xx xx xx xx xx xx xx 5D
Note:
The last two bytes must not set to 0x0000 ~ 0x0010, 0xFFF0-0xFFFF
2. Set PANID
5B 26 44 xx xx 5D = Set PanId, xxxx(0x0000-0x03E7)
3. Set Channel
5B 25 34 xx 5D = Set channel number
4. Set Tx Power
5B 25 3C xx 5D = Set Tx power
5. Set Application Type
5B 24 30 5D = Enable GTW function
5B 24 32 5D = Enable RTR function
5B 24 46 5D = Enable STD function
6. Set Debug Off
5B 25 FE 00 5D
This equipment has been tested and found to comply with the limits for
a Class B digital device, pursuant to part 15 of the FCC Rules. These
limits are designed to provide reasonable protection against harmful
interference in a residential installation. This equipment generates
uses and can radiate radio frequency energy and, if not installed and
used in accordance with the instructions, may cause harmful interference
to radio communications. However, there is no guarantee that interference
will not occur in a particular installation. If this equipment does cause
harmful interference to radio or television reception, which can be
determined by turning the equipment off and on, the user is encouraged
to try to correct the interference by one or more of the following
measures:
-Reorient or relocate the receiving antenna.
-Increase the separation between the equipment and receiver.
-Connect the equipment into an outlet on a circuit different from that
to which the receiver is connected.
-Consult the dealer or an experienced radio/TV technician for help.
RAEMesh2 RMCI Protocol
Doc.No. 904-E800-316
Rev.No. A
Date: 10/14/10
Page 21 of 9
Terms:
GTW: A RTR used for gateway. Only one GTW per network.
RTR: Full Function Device. Sensor node with routing ability. RTR requires line power all time.
STD: Reduce Function Device. A Sleeping node can only talk to a RTR or GTW. Can not relay the message. Can be a
battery powered device.
RCM :Radio Communications Module
RDTE: Reader Data Terminal Equipment.
RMCI: RAEMesh Module Command Interface.
SDTE : Sensor Data Terminal Equipment.
Reference:
Atmel: www.atmel.com
FCC: www.gcc.gov
Zigbee Alliance: www.zigbee.org
Contact:
Disclaimer
Product and Company names and logos referenced may either be trademarks or registered trademarks of their respective
companies. We reserve the right to make modifications and/or improvements without prior notification. All information is
correct at time of issue. RAE Systems does not convey any license under its patent rights or assume any responsibility for
the use of the described product.
Warnings:
FCC Notifications:
Compliance Statement (Part 15.19)
This device complies with part 15 of the FCC rules. Operation is subject to the following two
conditions:
1. This device may not cause harmful interference received, including interference
that may cause undesired operation.
2. This device must accept any interference received, including interference that may
cause undesired operation.
Warning (Part 15.21)
Changes or modifications not expressly approved by the party responsible for compliance
could void the user’s authority to operate the equipment.
This device must be operated as supplied by Raesystems. Any changes or
modifications made to the device can be jeopardize, but there is one
exception. The radio’s antenna can be replaced as long as the specification of the
antenna matches the original.
Information for the OEMs and Integrators
This device is intended for OEM integrators only. Please see the full Grant of Equipment document for restrictions.
This device must be operated and used with a locally approved access point.
Label Information to the End User by the OEM or Integrator
If the FCC ID of this module is not visible when it is installed inside another device, then the
outside of the device into which the module is installed must be labeled with "Contains FCC ID:
SU3RM2400A" in a visible area.
MPE reminding
To satisfy FCC RF exposure requirements, a separation distance of 20 cm or more should be
maintained between the antenna of this device and persons during device operation.
To ensure compliance, operations at closer than this distance is not recommended.
Source Exif Data:
File Type : PDF File Type Extension : pdf MIME Type : application/pdf PDF Version : 1.4 Linearized : No Page Count : 21 XMP Toolkit : XMP toolkit 2.9.1-13, framework 1.6 About : uuid:3c06a7b7-55c9-477b-b3db-63ab875a23bc Producer : Acrobat Distiller 6.0 (Windows) Creator Tool : PScript5.dll Version 5.2.2 Modify Date : 2011:06:02 13:51:42-07:00 Create Date : 2011:06:02 13:51:42-07:00 Document ID : uuid:f8154e18-8241-4a3a-a9e3-7252b4b2266c Format : application/pdf Title : Microsoft Word - RAEMeshII User Manual.doc Creator : jliu Author : jliuEXIF Metadata provided by EXIF.tools