RAE Systems RM900 RAEmesh Radio (RM900) User Manual SU3RM900
RAE Systems, Inc RAEmesh Radio (RM900) SU3RM900
User Manual
| Download: |  |
| Mirror Download [FCC.gov] | |
| Document ID | 2293072 |
| Application ID | EFHR/2wLExqKNuN0879EyA== |
| Document Description | User Manual |
| Short Term Confidential | No |
| Permanent Confidential | No |
| Supercede | No |
| Document Type | User Manual |
| Display Format | Adobe Acrobat PDF - pdf |
| Filesize | 270.33kB (3379138 bits) |
| Date Submitted | 2014-06-12 00:00:00 |
| Date Available | 2014-06-12 00:00:00 |
| Creation Date | 2014-06-05 14:48:16 |
| Producing Software | Acrobat Distiller 7.0 (Windows) |
| Document Lastmod | 2014-06-05 14:48:16 |
| Document Title | SU3RM900_User Manual |
| Document Creator | PScript5.dll Version 5.2.2 |
| Document Author: | jkong |
RAEMesh2 User Manual
Doc.No:
Originator: kren
Page 1 of 38
Data: 2014-3-18
RAEMesh2 Radio User Manual
RAE Systems Inc
RAEMesh2 User Manual
Doc.No:
Originator: kren
Page 2 of 38
Revision
0.1
0.2
0.3
0.4
0.5
0.6
Date
11/28/2008
12/1/2008
1/4/2009
1/5/2009
3/26/2010
4/22/2010
0.7
5/20/10
0.8
5/25/10
0.9
8//17/10
1.0
10/14/10
1.1
11/19/10
1.2
Comments
Initial
Add “Radio Core Setting Procedure”
Add “Fuse config”, “Firmware programmer”
Add “Soft Reset” command
Add “Reset reason” command
Add description about TXPOWER and
Channel setting
Add START_ROUTING command.
Change SET_FACTORY_RST for RM2400
Add RAEMesh and RAEMesh-II difference,
CHG START_ROUTING to
SET_ROUTEINTERVAL, add
GET_ROUTEINTERVAL and SET_REGION.
Modify ModuleType definition.
Data: 2014-3-18
Author
Alven
Alven
Alven
Alven
kren
kren
kren
kren
kren
Add modem longest startup time;
Add modem longest packet length from SOP
to EOP; rename “RFD” as “STD”,
rename “FFD” as “RTR”, rename
“Coordinator” as “GTW”.
Error, best rssi of at command response is
240, not 100.
kren
01/31/11
Add new command, GET_FWVERSION
kren
1.3
03/25/11
Add new commands, SET_CMDBATCH and
GET_CMDBATCH
kren
1.4
04/07/11
Modify GET_PARENT_ID definition.
Modem return 0x5b 24 27 5d when it transmit
a pack and get acknowledge successfully.
kren
1.5
6/28/2011
11/25/2011
Add SET_BOOTLOADER
Add bootloader section
kren
kren
5/8/2012
Add RM900A module type.
Add SAM7X RAELoader Section
Add RM900A low temperature current
comsumption.
Add RM2400, RM2400AM, RM900AM, Wifi and
Cellular modem type.
kren
8/16/2013
Modify FACTORY_RESET.
kren
9/23/13
1/23/14
2/18/14
Add GET_TRIAL_INFO
Add Wi-Fi related command
Add three commands, SYS_CTRL_GET,
SYS_CTRL_SET, SEC_KEY_SET
Delete Wi-Fi related command
Add GET_NEIGHBOUR_LIST
kren
Wu Wei
kren
5/23/2012
04/03/14
4/3/2014
kren
kren
Wu Wei
kren
RAEMesh2 User Manual
Doc.No:
Originator: kren
Page 3 of 38
Data: 2014-3-18
1. 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.
2. Hardware
1) Specifications
Frequency Band
802.15.4 standard.
2.4Ghz:16 channels of operation in the 2.4GHz world wide ISM band. 5MHz
channel spacing.
915Mhz: 10 channels. 906,908……924Mhz
868Mhz: 1 channel, 868Mhz
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 @2.4GHz
40kbps BPSK DSSS @915MHz
20kbps BPSK DSSS @868MHz
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
RM2400A
RM900
RM900A
RF receive sensitivity
23µA Sleep
120 mA TX @Medium Level 18dBm
25 mA RX / Idle
23µA Sleep
50 mA TX @High Level 11dBm
20mA RX / Idle
600µA Sleep
170mA TX 25ć or 200mA TX -20ć@Medium Level
35mA RX/Idel
-100dBm at at 1% packet error rate for a 20 byte payload.
RAEMesh2 User Manual
Doc.No:
Originator: kren
Page 4 of 38
2) 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
Data: 2014-3-18
RAEMesh2 User Manual
Doc.No:
Originator: kren
Page 5 of 38
Data: 2014-3-18
3. 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
RAEMesh2 User Manual
Doc.No:
Originator: kren
Page 6 of 38
Data: 2014-3-18
4. Firmware
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.
1) 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 90 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.
RAEMesh2 User Manual
Doc.No:
Originator: kren
Page 7 of 38
Data: 2014-3-18
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:V1.02b on Sep 28 2011 09:52:14
Stack: BC1.10.0
Type: Coordinator/Gateway
Band: 2400
EUI: 0001002400001005
Channel: 0x10
TxPwr: Medium
PanId: 0x03E5
RTR:
[%A١ ]RAEMESH-II RM2400A 8MHz
FwVer:V1.02b on Sep 28 2011 09:52:14
Stack: BC1.10.0
Type: FFD/Router
Band: 2400
EUI: 0001002400001005
Channel: 0x10
TxPwr: Medium
PanId: 0x03E5
STD
[%A١ ]RAEMESH-II RM2400A 8MHz
FwVer:V1.02b on Sep 28 2011 09:52:14
Stack: BC1.10.0
Type: RFD Sleep Sensor
Band: 2400
EUI: 0001002400001005
Channel: 0x10
TxPwr: Medium
PanId: 0x03E5
RAEMesh2 User Manual
Doc.No:
Originator: kren
Page 8 of 38
Data: 2014-3-18
2) RAEMesh Module Command Interface
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.
Table1 RAEMesh and RAEMeshII Difference
Item
RAEMesh
RAEMeshII
Hardware
MCU: ATMEGA128L
Radio: EM2420
Stack
Ember Zigbee Stack
MCU: ATMEGA1281V
Radio: AT86RF212,
AT86RF230, AT86RF231
Atmel Bitcloud
Specification
Zigbee 2004
Zigbee Pro
Power Failure
Support
Un-support
RSSI
Router/RTR update
RSSI when it receive
every frame.
Support
Router/RTR read next
hop’s RSSI.
EUI
Set it on RangeTest.
Transmission
power
Always is maximum.
Set it on application
firmware.
There are three level to be
choose.
Bootloader
Provide by Ember
Provide by Atmel
N/A
Warm up time
time scale of
milliseconds
More than five seconds
N/A
Many-to-one
routing(MTOR)
Un-support
For Internal Use Only
Description
N/A
N/A
Owing to the difference of specification, RAEMesh
and RAEMeshII can’t inter-communication
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.
Command List of RMCI
5B 24 20 5D = Get network status
5B 24 50 5D = Join or form network by scan.
5B xx 26 dd dd 7B .. .. 7D 5D = Send massage in unicast
5B
5B
5B
5B
5B
5B
5B
5B
24
24
24
24
24
24
24
24
2A
3A
60
6C
68
7B
40
4C
5D
5D
5D
5D
5D
5D
5D
5D
Get Radio Type
Get device application type
Get Radio's UID, channel, PANID
Get Application's UID, channel, PANID
Get parent Network ID
Get Last Hop Link Quality (LQI)
Get reset reason.
GET_FWVERSION
5B 24 30 5D = Enable GTW function
5B 24 32 5D = Enable RTR function
5B 24 46 5D = Enable STD function
5B 24 4A 5D = Restore the radio to factory setting
5B 25 34
America,
5B 25 A0
5B 24 A2
5B 25 A4
5B 24 A6
5B 25 3C
minimum)
5B 26 44
5B 2C 4E
5B 25 AC
5B 24 AE
5B 24 A8
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 0x00 for
xx
xx
xx
5D
5D
xx 5D = Set PanId, xxxx(0x0000-0x03E7)
xx xx xx xx xx xx xx 5D = Set MAC/UID address
5D = SET_CMDBATCH
= GET_CMDBATCH
= GET TRIAL INFOMATION
5B 24 3E 5D = Leave current network
5B 26 42 xx xx 5D = Set routing discovery interval
5B 24 52 5d = Get routing discovery interval
5B 24 38 5D = Report node’s position
5B 24 48 5D = Soft reset
5B 24 56 5D = Access into bootloader
5B 25 FE xx 5D = Set print debug info, xx(00-disable; 01-enable)
For Internal Use Only
GET_MODULE_TYPE RM
Use on:
RMII
GTW
RTR
STD
0x2A
0x26
SEND_MSG_UNI
Use on:
GTW
RTR
STD
RM
0x20
Effect CMD
Area Code
NETWORK_STATUS RM
Use on:
RMII
GTW
RTR
STD
Command Name
3) Command Sets
For Internal Use Only
None
DestAdd(2)
RCS Pack(x)
None
CMD Data (bytes)
0x2B
0x27
Resp
onse
CMD
Code
0x21
Type(1)
None
STATUS(1)
Response
Data(Bytes)
CMD
RCS Pack(x) must be compliant with RCS format.
Return the radio’s type.
Type definition:
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
DestAddr
0x0000 ->to coordinator
0x0001~0Xfff0 ->to STD or RTR
0xfff1~0xfffb –reserved
0xfffc ->all RTR in network
0xfffd ->all receiver on in network
0xfffe ->reserved
0xffff ->all modem in network
Send message in Zigbee address mode.
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.
Description
Use on:
GTW
RTR
STD
CHG_RRCM_CHAN
Use on:
GTW
RTR
STD
Use on:
GTW
RTR
STD
RTR_ENABLE
GTW_ENABLE
RM
RMII
RM
RMII
RM
RMII
0x34
0x32
0x30
For Internal Use Only
Channel Number(1)
None
None
0x35
0x33
0x31
None
None
None
0x01 to 0x0A total 10 channels for RM900 if region is
0x00 for RM900 if region is BAND_868_EU.
Requests change radio channel to specified channel.
Meanwhile, specified channel should be compliance with
radio region setting.
Reset automatically.
Set radio to RTR. Always on and has router function.
Baud rate change to 19200 8N1
Reset automatically.
9: RM900A
10: RM2400A
11: coRE1-433MHz
12: coRE1-868MHz
13: coRE1-915MHz
14: coRE2-433MHz
15: coRE2-868MHz
16: coRE2-915MHz
17: coRE6-2.4GHz
18: RM2400
19: RM2400AM
20: Reserved for 2.4GHz modem
21: RM900AM
22: Reserved for 900MHz modem
23: Roving Wifi
24: GainSpan Wifi
25: Reserved for wi-fi Modem
26: Cellular Modem1
27: Cellular Modem2
28: Cellular Modem3
Set the radio as a GTW so that the radio can be use on a
Gateway device.
Baud rate change to 38400 8N1
0x3A
0x3C
RM
RMII
RM
RMII
RM
RMII
SET_TX_POWER
Use on:
GTW
RTR
STD
LEAVE_NETWORK
Use on:
GTW
RTR
STD
0x3E
0x38
RM
RMII
RPT_LOCATION
Use on:
GTW
RTR
STD
GET_APPTYPE
Use on:
GTW
RTR
STD
For Internal Use Only
None
TxPwr(1)
None
None
0x3F
0x3D
0x3B
0x39
None
None
AppType(1)
None
Reset automatically.
Leave the current network.
For RAEMesh
Power setting from 0xE3(-25dBm) to 0xFF(0dBm).
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,
If channel number is not compliance with radio region, do not
return response CMD.
Reset automatically.
Print node’s network information in ASCII.
0x0B to 0x1A total 16 channels for RM2400 if region is
BAND_2400_ISM.
BAND_915_NA.
0x44
0x46
0x48
0x4A
RM
RMII
RM
RMII
RM
RMII
RM
RMII
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
0x40
RM
RMII
RST_REASON
Use on:
GTW
RTR
STD
For Internal Use Only
None
None
None
PanID:(2)
XXXX
None
0x4B
0x49
0x47
0x45
0x41
None
None
None
None
Reason(1)
Reset automatically.
Restore the RCM to factory defaults.
PanId is 0x03E7;
Device Type is STD;
Txpower is medium;
STD receiver is disable;
Debug print is off;
When RM2400A, channel is 15;
When RM900A and RM900, channel is 6;
Reset automatically.
Perform soft reset.
Reset automatically.
Put a node into STD. Interrupt enable and active low.
Baud rate change to 19200 8N1
Reset automatically.
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,
Change GTW Pan ID into XXXX.
From 0x0001 to 0x03E7(1-999)
None
None
0x50
0x54
JION_FORM_NETWO RM
RK
RMII
Use on:
GTW
RTR
STD
GET_NEIGHBOUR_LI RMII
ST
Use on:
GTW
RTR
STD
For Internal Use Only
UID(8)
0x4E
RMII
None
SET_UID
Use on:
GTW
RTR
STD
0x4C
RM
RMII
RW
GET_FWVERSION
Use on:
GTW
RTR
STD
0x55
0x51
0x4F
0x4D
and
Node[0]
shortAddr[2]
rssi[1]
relation[1]
depth[1]
Node[1]…
Node[2]…
…
None
None
Fw Version
Time[30]
Build
Neighbor table list like this:
shortAddr:
Short address when network is up.
RSSI:
Best: 240, Worst:0
Relation:
PARENT
= 0x00
CHILD
= 0x01
SIBLING
= 0x02
NONE_OF_ABOVE = 0x03
PREVIOUS_CHILD
= 0x04
UNAUTHENTICATED_CHILD = 0x05
EMPTY = 0x06
Depth:
Network depth in the routing link toward coordinator.
RTR/STD: Search the network using customized PANID and
try to join the network.
Reset automatically.
GTW: Form a network using customized PANID to allow the
other nodes to join.
For RMII:
Set radio’s UID(MAC address).
Note:
The last two bytes must not set to 0x0000, 0xFFF00xFFFF
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.
0x58
0x60
0x6C
RMII
RMII
RMII
RM
RMII
RM
RMII
SYS_CTRL_SET
SYS_CTRL_GET
SEC_KEY_SET
GET_NODE_INFO
Use on:
GTW
RTR
STD
GET_APPNODE_INF
Use on:
GTW
RTR
STD
0x5C
0x5A
0x56
SET_BOOTLOADER RM
Use on:
RMII
GTW
RTR
STD
For Internal Use Only
None
None
KEY[15]…KEY[0]
None
System Control Word,
B[3]…B[0]
None
0x6D
0x61
0x5D
0x5B
0x59
0x57
UID(8)
Channel(1)
Power(1)
PAN ID(2)
UID(8)
Channel(1)
Power(1)
PAN ID(2)
00- failed
01- success
System Control Word,
B[3]…B[0]
00 – failed
01 – success
None
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.
Get the node information: UID, Channel, Txpower level,, PAN
ID,
Set AES-128 key for application encrypt/decrypt.
System Control Word.
Bit0: Roaming function, 1 – enable; 0 – disable;
Bit1: pending, AES128 security, 1 – enable; 0 – disable;
Bit2: Receiver setting of RFD; 1 – always on when idle; 0 –
power saving mode;
Bit31: reversed;
Get System Control Word.
Make modem into bootloader mode and wait for new app
image.
0x68
0x7B
0xA0
0xA2
0xA4
RM
RMII
RM
RMII
RW
RMII
RMII
RMII
GET_PARENT_ID
Use on:
RTR
STD
LAST_HOP_RSSI
Use on:
RTR
STD
SET_RECEIVER
Use on:
STD
GET_RECEIVER
Use on:
STD
SET_REGION
Use on:
GTW
RTR
STD
For Internal Use Only
Region(1)
None
00 - Disable
01 - Enable
None
None
0xA5
0xA3
0xA1
0x7C
0x69
None
Status(1)
None
RSSI(1)
Parent radio ID(8)
Reset automatically.
When 915/868Mhz modem, default channel is 0x00 if set
region to BAND_868_EU; default channel is 0x06 if set region
to BAND_915_NA.
For RMII
Region(1)
BAND_868_EU = 0x01,
BAND_915_NA = 0x04,
BAND_2400_ISM = 0x08,
When 2.4Ghz modem, this command is useless because
RM2400 always work on BAND_2400_ISM.
Reset automatically.
Return STD receiver’s status,
00 – Disable
01 - Enable
STD should use poll to request data packet from parent if
disable receiver.
STD should receive data packet from parent if enable
receiver;
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.
Enable or disable STD’s receiver.
0xA8
0xFE
0xAC
RMII
SET_DEBUG_PRINT RM
Use on:
RMII
GTW
RTR
STD
RMII
SET_CMDBATCH
Use on:
GTW
RTR
STD
0xA6
RMII
RW
GET_REGION
Use on:
GTW
RTR
STD
GET_TRAIL_INFO
Use on:
GTW
RTR
STD
For Internal Use Only
00,
Disable
01,
Enable
00,Disable
01,Enable
None
None
0xAD
0xFF
0xA9
0xA7
None
None
NWK_INFO[16]
Region(1)
Enable or disable command batch function. If enable, modem
will not reset automatically after change panid, channel,
power, eui, regionˈ receiver and join permission. They will
take effect after reset manually.
Batch function will disable after reset.
BYTE3~BYTE15: reserved.
Set display debug information enable/disable.
The default setting is disabled.
BYTE2: network depth(0~15)
BYTE1: reset reason.
0x00 = UNKNOW,
0x01 = EXTERNAL,
0x02 = POWERON
0x03 = WATCHDOG,
0x04 = BROWNOUT,
0x05 = JTAG,
0x06 = WARM
BYTE0: modem reset count. This count should be increased if
any reset occur.(0~255)
Use this command to get modem trail information.
Get modem setting of region.
RMII
0xAE
None
0xAF
00: Disable
01: Enable
Return command batch configuration.
For Internal Use Only
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.
GET_CMDBATCH
Use on:
GTW
RTR
STD
4) RMII Command Classification
There are a lot of RMCI command set in this manual, different application need different command, below is a
table that which command must have, which are recommend and which are optional.
Table 2 Command Classification
MUST
HAVE
RECOMMENED
OPTIONAL
ITEM
FACTORY_RST
GET_MODEM_TYPE
GET_APPTYPE
CMDS
NETWORK_STATUS
SET_TXPOWER
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
SET_DEBUG_PRINT
5. Bootloader
Bootloader is a stand-alone utility consisting of two parts: embedded bootstrap code that should be loaded to the
flash memory of a supported MCU and the PC based application that sends data to the embedded bootstrap over
serial link. Embedded bootstrap code uses the received data to program the internal flash memory of the MCU.
A simple communication protocol is used to ensure proper programming. RAEMeshII have two types of
bootloader, one is from Atmel, the other is from REC.
When we buy Atmel Zigbit module, it have been programmed Atmel Bootloader in its boot section, it use
Motorola S-record (SREC) format files as source images for serial bootloader PC part. ZigBitFwUpgrade.exe
or RadioSmart.exe can be PC Utility for upgrade.
RAELoader is compliance with 904-E800-310 RAELoader Communication Protocol.doc. RFP format files are
supported as source images for the serial bootloader PC part. RAEProgrammer4000.exe can be PC Utility for
upgrade.
Serial Bootloader is supported on a set of Atmel microcontrollers as shown below Table.
MCU
Bootloader
Modem Type Remark
ATmaga1281
Atmel Bootloader RM2400A
Use AVRUsb to embed loader.
RM900
RAELoader
AT91SAM7X256 RAELoader
RM900A
Use Jlink to embed loader
1) How to distinguish
When a RAEMeshII modem is in our hand, how can we distinguish what bootloder they have? This section will
teach you.
Caution: if module type is RM2400A or RM900, we need use following section to distinguish; if module type is RM900A,
all of them use RAELoader_Sam7x, jump to section 2 “How to embed”.
a) Just have bootloader
If this modem just have bootloader in its boot flash memory and its application flash memory is empty, we
should reset modem to distinguish whether it print startup message. When this modem have RAELoader, reset
may cause modem toggle LED1 and print startup message as below:
For Internal Use Only
If there is not any phenomenon on LED1 and USART after reset modem, this modem embed Atmel bootloader.
b) Bootloader and application mixed
If modem have bootloader and application in corresponding flash memory, using above method is useless. We
can use SET_BOOTLOADER(0x5B 24 56 5D) to distinguish.
First, send SET_BOOTLOADER through USART port to modem.
Then, if modem reset and print startup menu of application as below, this modem embed Atmel bootloader.
If modem print startup menu of RAELoader as below and toggle LED1 very quickly, this modem embed
RAELoader.
For Internal Use Only
2) How to embed RAELoader_ATMega1281
If you want to embed bootloader into RM900 or RM2400A which use ATMega1281 as mcu, no matter Atmel
bootloader or RAELoader, you should prepare corresponding tool.
Software: AVRUSB V2.0.2.231
Hardware: AVRUSB Programmer and RAEMeshII Dev board.
Then, operate step by step as below,
a) Make sure the correct hardware selected
b) Make sure the AVRUSB connected to dev board and board is power on, click “Reset”.
If a green label is at bottom of AVRUSB framework, go to next step.
For Internal Use Only
c) Erase target MCU
d) Read out current fuse setting.
If you want to embed Atmel bootloader, please go to Step e).
If you want to embed RAELoader, please go to Step f).
For Internal Use Only
e) Check the following setting, it’s used for Atmel bootloader
For Internal Use Only
f) Check the following settings and make sure as same as showed.
Caution: RAELoader ATmega1281’s Boot Block Size should be 4096 bytes.
For Internal Use Only
g) Write back Fuse setting if any changes made, make sure program successfully.
If you want to embed Atmel bootloader, please go to Step h).
If you want to embed RAELoader, please go to Step i).
For Internal Use Only
h) Load ATMEL bootloader hex image.
Find corresponding path and load *.hex which should be written into boot flash memory.
i) Load RAELoader hex image.
Find corresponding path and load *.hex which should be written into flash merory.
For Internal Use Only
j) Press Device -> Program -> Flash, load bootloader image successfully.
For Internal Use Only
3) How to embed RAELoader_Sam7x
If you want to embed bootloader into RM900A which use AT91SAM7X256 as mcu, you should prepare
corresponding tool.
Software: SEGGER J-Flash ARM V4.20
Hardware: JLINK ARM Programmer and RAEMeshII Dev board.
Then, operate step by step as below,
a) open J-Flash ARM and press “Alt + F7”, you will see this window:
For Internal Use Only
b) click “CPU” and choose AT91SAM7X256 as device.
c) put RM900A on dev board and use JLINK to connect with it.
d) click “File” ->”Open data file” to choose RAELoader_Sam7x *.hex file.
For Internal Use Only
e) click “Target” -> “Erase chip” to erase all flash memory.
f) click “Target” -> “Program” to downloader RAELoader hex file into mcu.
For Internal Use Only
g) click “Target” -> “Start application” to make mcu run.
h) Then, embed RAELoader_Sam7x is successful, go to Section4.
4) Firmware Upgrade
User should use different utility to upgrade RAEMeshII application firmware.
a) Using Atmel bootloader to upgrade
1. Select firmware file, *.srec
2. Select correct com port
3. Click “Program”, then Reset RAEMesh2 module in 30 seconds
Waiting for program successful.
For Internal Use Only
b) Using RAELoader to upgrade
1. Use RMCI command to access RAELoader
If modem run app firmware, we can use RMCI command, 0x5b 24 56 5d, to access RAELoader for firmware
upgrade.
2. Use jumper to access RAELoader
We can use hardware jumper to access RAELoader. First, jump specified pin to ground; second, press reset
button on evaluation board to reset modem; then modem access into RAELoader.
For Internal Use Only
Now, we have two type of evaluation board, please use following method for loader jumper. Old evaluation board
setup, it is the same with how to set ZcoRAE-M3 into bootloader.
New evaluation board setup
For Internal Use Only
3. RAELoader Indication
RAELoader use LEDs blink and toggle on M3 adapter or evaluation board to tell user the situation of loader.
When modem access into RAELoader, one LED, which lable is LED2 on M3 adapter, will blink continuously. If start to
upgrade firmware, two LEDs on evaluation board will blink continuously and alternately.
4. Upgrade
When modem is in RAELoader, we use RAEProgrammer4000 to upgrade firmware, detail please refer to user
guide of RAEProgrammer4000.
5. Quit
if modem access into RAELoader using RMCI command, reset or upgrade successfully can make modem out.
For Internal Use Only
6. 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.
7. Reference
Atmel:
FCC: www.gcc.gov
Zigbee Alliance: www.zigbee.org
8. Contact
Developer: Kai Ren
Tel:021-69522616 Ext4115
Email: kren@raesystems.com
9. 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.
10. 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
For Internal Use Only
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.
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.
Information for the OEM Integrators
This device is intended for OEM integrators only. Please see the full grant of
equipment document for restrictions.
Label Information to the End User by the OEM or Integrators
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 label with
"Contains FCC ID: SU3RM900".
For Internal Use Only
Source Exif Data:
File Type : PDF File Type Extension : pdf MIME Type : application/pdf PDF Version : 1.4 Linearized : Yes XMP Toolkit : 3.1-701 Keywords : Producer : Acrobat Distiller 7.0 (Windows) Create Date : 2014:06:05 14:48:16+08:00 Modify Date : 2014:06:05 14:48:16+08:00 Metadata Date : 2014:06:05 14:48:08+08:00 Creator Tool : PScript5.dll Version 5.2.2 Document ID : uuid:5E64E3017DECE311A9D4B9AC5B745C39 Instance ID : uuid:85a98901-ca5d-42b5-9a85-20daa3f27d12 Derived From Document Name : uuid:a13ff579-c78f-11e3-0000-3113b7a479a9 Derived From Document ID : uuid:a13ff579-c78f-11e3-0000-3113b7a479a9 Format : application/postscript Title : SU3RM900_User Manual Creator : jkong Description : Page Count : 38 Subject : Author : jkongEXIF Metadata provided by EXIF.tools