Technology Ltd REnex ZcoRE3-2400
(ZcoRE3-2400/ZcoRE3(20)-2400) OEM Serial Wireless Transceiver Module User Manual Version 1.0 May, 2007 This manual covers the operations of the ZcoRE3-2400 family of serial OEM wireless transceiver modules. For the most part, operation of each product in the ZcoRE3-2400 family is identical; where operating differences exist, every effort has been made to clearly identify which product is being referred to. This manual is produced for users of the ZcoRE3-2400 OEM wireless transceiver module from REnex Technology Limited. It covers the operating principles and capabilities of the ZcoRE3-2400 module. It is recommended that you read this document before using the ZcoRE3-2400 module in order to operate it correctly and optimize its performance. WARRANTY REnex Technologys ZcoRE3-2400 module is warranted against defect in materials and manufacturing for a period of two years from date of purchase. In the event of a product failure due to materials or workmanship, REnex will, at its discretion, repair or replace the product. REnex and its suppliers shall in no event be liable for any damages arising from the use of or inability to use this product. This includes business interruption, loss of business information, or other loss which may arise from the use of the product. Changes or modifications to this unit not expressly approved by the party responsible for compliance could void the users authority to operate the 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, and (2) this device must accept any interference received, including interference that may cause undesired operation. WARNING equipment. REMINDING While using for ZcoRE3(20)-2400, precaution below is necessary:
PRECAUTION 1. The installed antenna must not be located in a manner that allows exposure of the general population at a distance of less than 4cm. 2. Mount the antenna in a manner that prevents any personnel from entering the area within 4cm from the central position of the antenna. 3. It is recommended that the installer place radio frequency hazard warnings signs on the barrier that prevents access to the antenna. 4. Prior to installing the antenna to the antenna connector, make sure the power is adjusted to the settings specified in section of this manual. 5. During antenna installation, be sure that the power to the equipment is turned off in order to prevent any energy presence on the coaxial connector. This manual contains information of proprietary interest to REnex Technology Limited. It has been supplied in confidence to purchasers and other authorized users of the ZcoRE3-2400 module, and by accepting this material, the recipient agrees that no part of the document shall be reproduced or transmitted in any form or by any means, without prior written consent of REnex Technology Limited. Information in this document is subject to change without notice. REnex Reference Number:
Print Date: Feb. 2007 2006-2010 REnex Technology Limited. All rights reserved. Microsoft and Windows are registered trademarks of Microsoft Corporation. HyperTerminal is copyrighted by Hilgraeve Inc, and developed for Microsoft. All other products mentioned in this document are trademarks or registered trademarks of their respective holders. Document Version History:
ZcoRE3-2400_User_Manual_V1.0 Version V1.0 V1.1 Release Date Feb 28,2007 May 18 2007 Comment Initial Release Updating for Approval iii ZcoRE3-2400_User_Manual_V1.0 Table of Content 1. Introduction...............................................................................................................................1 2. Technical Parameters ................................................................................................................2 3. Module Interface.......................................................................................................................3 1.27 mm Pin Header Interface.......................................................................................3 3.1 RF Interface...................................................................................................................6 3.2 3.3 RMCI interface..............................................................................................................7 3.4 Wakeup..........................................................................................................................8 4. Power Supply ............................................................................................................................8 5. Module Configuration...............................................................................................................8 6. RAEMESH Module Command Interface (RMCI)..................................................................11 Serial port setting ............................................................................................11 Package format................................................................................................11 Quick review of RMCI....................................................................................12 7. Mechanical Drawing ...............................................................................................................17 Top View .....................................................................................................................17 Bottom (top perspective).............................................................................................18 8. Order Information ...................................................................................................................19 6.1.1 6.1.2 6.1.3 7.1 7.2 iv ZcoRE3-2400_User_Manual_V1.0 Terms:
Coordinator:
A FFD used for gateway. Only one coordinator per network. FFD:
Full Function Device. Sensor node with routing ability. FFD requires line power all time. RFD:
Reduce Function Device. A Sleeping node can only talk to a FFD or Coordinator. Can not relay the message. Can be a battery powered device. RCM:
Radio Communications Module RDTE:
Reader Data Terminal Equipment. SDTE:
Sensor Data Terminal Equipment. RMCI:
RAEMESH Module Command Interface. RCM:
Radio Frequency Communication Module, ZcoRE3-2400/ZcoRE3(20)-2400 OEM module v 1. Introduction ZcoRE3-2400_User_Manual_V1.0 The ZcoRE3-2400 serial OEM transceiver module is a small size, high performance wireless module, which is designed to provide a cost efficient solution for reliable data transmission and low power consumption. It is ideal for low data rate wireless applications, including sensor monitoring, building automation, security systems and any other application requiring low power consumption. The ZcoRE3-2400 module family includes devices that work at two different RF power, including 0dBm and 18dBm, to enable license-free operations in varies applications. The ZcoRE3-2400 module offers data communication capabilities to application equipment via a standard UART interface. Using a pair of ZcoRE3-2400 wireless modules, users can transfer data between almost any type of equipment that use this interface. The ZcoRE3-2400 module provides two power modes, normal working mode and sleep mode, which has very low power consumption since the device can neither transmit nor receive data in this mode. Switching to sleep mode whenever possible generally creates significant energy savings, which is important for battery-powered systems. These modules are preloaded wireless sensor mesh network application (RAEMESH), which was developed based on EmberZnet 2.23 mesh stack. This documentation also describes the RAEMESH Module Command Interface (RMCI) for IEEE 802.15.4/Zigbee enabled RF Module
(RCM), Including ZcoRE3 (20)-2400 and ZcoRE3-2400. By using RMCI, users can easily integrate the mesh radio into a wide range of applications without pain to develop the mesh stack by themselves and no RF expertise is required. Features of ZcoRE3-2400:
Mesh network
ISM frequency bands 2.4 GHz ~ 2.4835GH
High receiver sensitivity - superior transmission range for a given RF power
Designed to hazardous industrial requirements - may be used in instruments certified for intrinsic safety operation
Low power consumption - conserves battery power
Small size, light weight - easy to integrate
Low cost - cost-efficient systems Application examples:
Smart badges
Remote monitoring and control
Perimeter security/access control
Medical instrumentation
Environmental monitoring
Sensor networks
Diagnostic monitoring
Industrial telemetry
Automatic meter reading
1 ZcoRE3-2400_User_Manual_V1.0 2. Technical Parameters Table 2.1 Technical Parameters of ZcoRE3-2400/ZcoRE3(20)-2400 Radio Characteristics RF Frequency Band Number of Channels Channel Spacing RF Data Rate Modulation Duplex Maximum E.R.P. Receiver Sensitivity Receiver Classification Operating Range Network Protocol Operating Mode Error Detection Radio Type Approval Intrinsic Safety Design Miscellaneous 2.4 ~ 2.4835GHz 16 channels 5 MHz 250 kbps OQPSK TDD 1 (0 dBm) ~ 60 mW (18 dBm)
-95 dBm at 10-3 BER Class 2 Up to 1 km in line-of-sight(18dBm)*
Zigbee & IEEE 802.15.4 compliant Mesh CRC and ARQ CE: EN300-328 FCC: Part 15.247 SRRC & Middle-East : (pending) UL C1D1 / ATEX T4 I/O Interface Serial TTL with universal socket: 2 x 20 pins with 1.27 mm I/O Option Antenna Port Interface Power Supply Power Consumption Operating Temperature Humidity Two digital I/O; one analog I/O;
RS-232(TTL) for optional modules (Bluetooth, GPS, GPRS and WiFi) Chip antenna(0dBm,18dBm)/MMCX female(18dBm) 3.3 .3V Normal working mode:
Tx: 44 mA | 230mA(18dBm)@ 3.3 V Rx: 35 mA | 35mA(18dBm)@ 3.3 V Sleep mode: 9 uA | 9 uA(18dBm) @ 3.3 V
-40o C to 75o C 20% to 90% non-condensing Dimensions (L W H) 46.5 mm x 26 mm x 10 mm Weight 10 grams (0.35 ounce)
*Depending on the interference environment. 2 3. Module Interface ZcoRE3-2400_User_Manual_V1.0 The module interface includes the power input (3.3 V), power output (3.3 V), configuration button signal, serial ports (CMOS 3.3 V), A/D, I2C, test signal, JTAG and digital I/O, etc. These are integrated on a dual row, 20 pins per row, 1.27 mm pitch connector (J1). Refer to Table 3.1 for a detailed pin definition. REnex can provide an evaluation kit for the ZcoRE3-2400/ZcoRE3 (20)-2400 module, which includes 4 modules and 4 evaluation mother board (refer to the ZcoRE3-2400 evaluation kit user manual for more details). The module interface and other important IO are provided on the module evaluation board. The users can also design their own application board with the required module interface. Two of the most important interfaces are the pin header interface and the RF interface described below. 3.1 1.27 mm Pin Header Interface The pin header interface of the ZcoRE3-2400/ZcoRE3(20)-2400 is designed using a dual row 1.27 mm socket with a total of 40 pins. The JVE 21N21040-40M00B-01G-2.2/5.8 will be mounted on when the module is shipped. Refer to the JVE datasheet for detailed socket information. Users that want to use a different socket can also request that the pin header is not mounted. These users must make sure to match the PCB design of the interface. The following is a general drawing of the JVE socket (dimensions in mm). To match the ZcoRE3-2400/ZcoRE3(20)-2400 interface using the JVE pin header, JVE 22p8702-40M00B-01G-4.5 is an appropriate housing. The following is a general drawing of the JVE housing (dimensions in mm). 3 ZcoRE3-2400_User_Manual_V1.0 The pin definition of the header interface is shown on Table 3.1; the input and output description is based on module side. The main serial port is port 1 which includes TxD1 (pin 5) and RxD1 (pin 7). It will be set as the default port in the factory. There are three UART ports which can be used on the module. Pin 3 (RST) is the reset input; the module will reset if a low level signal is input. The ZcoRE3-2400/ZcoRE3(20)-2400 module provides RFD two power modes, wakeup and sleep mode. In wakeup mode, the module can execute normal operations, transmit and receive data via the RF channel. A low level input on Pin 19 will put the RFD module enter sleep mode. Pin 17, 28 and 30 can be used for temperature or battery voltage detecting input. Pins 27, 32, 34, 36, 38 are reserved for In-System Programming (ISP), and also for firmware debugging. All these pins are dedicated to JTAG and cannot be used for any other IO functions. 4 ZcoRE3-2400_User_Manual_V1.0 Function Table 3.1: Pin Definition of J1 Pin 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 GND GND RST GND TxD1 TxD0 RxD1 RxD0 GPIO0 LED_2 GPIO1 LED_3 GPIO2 LED_4 GPIO3 LED_5 TEMP_EN_GPIO4 PS_CS GPIO5 PS_FRAME BUZZER_GPIO6 3.3V_Vout PS_DIR_GPIO7 GND BUTTON_0_GPIO8 AREF BUTTON_1_GPIO9 ATEMP_ADC1 DBG_SYNC_GPIO10 ADC2 RF_SO JTCK RF_SI JTMS RF_SCLK JTDO RF_SFD JTDI 3.3Vin 3.3Vin IN/OUT Description Remark COMM COMM IN COMM OUT OUT IN IN IN&OUT OUT IN&OUT OUT IN&OUT OUT IN&OUT OUT IN&OUT IN IN IN IN&OUT OUT IN&OUT COMM IN&OUT OUT IN IN&OUT OUT OUT OUT IN IN IN IN OUT IN IN IN IN Ground Ground Reset signal input Ground UART1, transmit data UART0, transmit data UART1, receive data UART0, receive data General IO LED control signal General IO LED control signal General IO LED control signal General IO LED control signal Temperature /GPIO Reserved, Reserved, Reserved, Buzzer or General IO 3.3V output General IO Ground Button 0 input/GPIO Reserved, Button 1 input/GPIO General IO/ADC1 RF debug/GPIO10 ADC2 Reserved, Reserved, Reserved, Reserved, Reserved, Reserved, Reserved, Reserved, 3.3V, power input 3.3V, power input 5 External reset, active low Default serial port Default serial port Connect to LED for debugging Connect to LED for debugging Connect to LED for debugging Connect to LED for debugging Temperature Enable (active high) PACKET_TRACE_CS PACKET_TRACE_FRAME External power output, 20mA max PACKET_TRACE_DIR Reference level output Battery pack voltage input Temperature calibration RF testing points JTAG, common clock RF testing points JTAG, mode selection RF testing points JTAG, serial data out of service RF testing points JTAG, serial data into service 3.2 RF Interface ZcoRE3-2400_User_Manual_V1.0 Different RF interfaces are provided on the ZcoRE3-2400 module. For the ZcoRE3-2400 module, only a chip antenna can be soldered on when the modem ship out. Refer to diagram below for detail information of chip antenna. For the ZcoRE3(20)-2400 module, only the external antenna is available. P1 (refer to mechanical drawing) is designed on PCB board for the reversed SMA antenna connection via a special RF cable. The socket is user a right-angle straight MMCX (Miniature Microax RF Coaxial) connector which can be soldered on the top of PCB when the module is delivered. The maximum height of the MMCX socket is less than 4 mm. If customer would like to use a different socket, they may also elect not to have the MMCX socket soldered on. In that case, they should be sure to match the PCB design of the socket. To connect with the SMA antenna, a MMCX-to-SMA converter RF cable is provided together with the ZcoRE3(20)-2400 module as option. Refer to table and picture below for detail information of SMA antenna. Model: RO-IK-0504 Electrical Item Specifications Remarks Type of antenna Frequency range Electrical length Nominal impedance Dipole antenna 2.40 ~ 2.48 GHz 1 / 2 50 Ohm 6 Polarization V.S.W.R Peak gain Vertical Less than 2.0 1.5 dBi Mechanical Item Specifications Remarks Element Sleeve Base Connector Antenna total length RG-316 cable Urethane Nylon 66 SMA male 168 3 mm Black Black Ni plate 3.3 RMCI interface The module is pre-loaded with the EmberZnet bootloader (version:1005), which supports both over-the-air bootloading and serial bootloading of firmware update. The module contains RAEMESH application developed base on EmberZnet stack 2.23 and comply with the RAE Systems RCS protocol. The module also has built-in RAEMESH Module Command Interface
(RMCI). Section 6 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 coordinator to hook up to a getaway or just a standalone regular full function node or a sleepy reduce function node. Make sure to configure the module to right mode before using. 7 3.4 Wakeup ZcoRE3-2400_User_Manual_V1.0 If the radio is set to RFD mode, the Wakeup pin Pin19 is used to make the radio asleep and wakeup. A constant high on this pin will make 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 with very low power consumption. (<60uA) The Wakeup pin must be held up to 10ms before sending a data packet. 4. Power Supply As OEM module, the power supply should be provided by the main equipment, in which the OEM module is built. Normally, a 3.0 ~ 3.6V DC power is required. 5. Module Configuration Enter Configuration Status Via the TXD and RXD 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 Atmega 128L 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. Bits per second Data bits Parity check Stop bits Flow control Coordinator FFD and RFD 19,200 8 None 1 None 19,200 8 None 1 None PC communication Confirm that the serial port debugging software is 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. Data packet RCM will transmit any data in the { }, and all data in the {} will be transparently sent out without radios interpretation. The maximum data packet is 50 bytes including {}. The data in the {} can be any characters including {, }, [and ]. The interval between two data packets must be >50 ms for FFD and coordinator. The interval between two data packets must be >1 s for RFD. For old RAEWATCH_PSP 8 When the sensor node sends data to gateway, the gateway will receive the data plus the last four digits of sensor node ID in the {}. When the gateway sends data to sensor node, the sensor node radio will only receive data in the {}. For RAEWATCH_RCS The data in the {} will be untouched by either gateway or sensor node. You get what you send. For RCS details, refer to: 904-E800-120 RAEWATCH WSN Communication Standard.doc 9 ZcoRE3-2400_User_Manual_V1.0 Base on correct setting and connection, you will see following display on your screen when power is applied. Coordinator:
EVENT: emberInit passed INIT: sink app 000D6F0000002DF8 chan:0x1A, pwr:FF, panID:0x30FF EVENT: stack Status now EMBER_NETWORK_UP EVENT: setting multicast binding, status is 0x00 FFD:
EVENT: emberInit passed FFD SENSOR APP: joined to network 000D6F0000002DA5 chan:0x1A, pwr:FF, panID:0x30FF EVENT: stack Status now EMBER_NETWORK_UP EVENT: setting multicast binding, status is 0x00 This is a free sensor. RFD (if there is a coordinator or FFD) EVENT: emberInit passed RFD Sleep SENSOR APP: joined to network 000D6F0000002DA5 chan:0x1A, pwr:FF, panID:0x30FF EVENT: stack Status now EMBER_NETWORK_UP EVENT: setting multicast binding, status is 0x00 This is a free sensor. RFD (if there is no coordinator or FFD) EVENT: emberInit passed RFD Sleep SENSOR APP: joined to network 000D6F0000002DA5 chan:0x1A, pwr:FF, panID:0x30FF EVENT: stackStatus now MOVE_FAILED. Lost the Parent (Coordinator) 10 ZcoRE3-2400_User_Manual_V1.0 6. RAEMESH Module Command Interface (RMCI) 6.1.1 Serial port setting Between RDTE and RRCM: 38400 bps, 8N1 Between SDTE and SRCM: 19200 bps, 8N1 6.1.2 Package format Packet format as listed below:
SOP Length Command Code Command Data EOP Byte 1 1 1 0~n 1 The minimum length for one packet is 4 bytes long. The Length is 0x20 based. E.g. the total The SDTE or RDTE always initiate the communication with Radio module (RRCM,
length of a packet without command data is 4, the Length byte is 0x20 + 4 = 0x24.
SRCM). Radio module responses to the command it received.
response from Radio module to SDTE or RDTE is 1 higher than the command code.
Command Data can be empty. Table 5.1: Byte definition of packet The Command Code for packet sent from SDTE or RDTE to Radio module is even, the Byte Number 0 1 2 3 N+3 Name SOP Comment 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 such as help, version etc. Even for packet sent from SDTE or RDTE to RCM. Odd for packet response from RCM to SDTE or RDTE. Command Data Hex EOP Radio protocol end of packet. This is always ] (0x5D). Notes:
1. Always perform a Network Joining for FFD before using it. A coordinator must be presented when perform the network joining. Command: 5B24505D. 2. Check RCMs information when turn on the radio. Command: 5B24605D. 3. Wait at least 5s for RCM to finish the initialization. 11 ZcoRE3-2400_User_Manual_V1.0 4. Check the Network Status of the RFD before sending the data at the first time. Command:
5. 5B24205D. It is recommend 1s interval between two data packets for RFD. Check [] for sending acknowledge in Unicast mode. There is no ACK for multicast mode. 6. For RFD, if there is no network, the RCM will automatically wake up every 1 minute to search for a new network. It can be interrupted at any time. RCM will keep in asleep if it has joined a network. Quick review of RMCI 7. For debug purpose, check network status and Parent ID of RFD. 6.1.3 5b24205d = NETWORK_STATUS 5b24225d = GET_BINDING_LIST 5b24245d = SYSCH_ADVERTISE 5b2526XX5d = COM_UNICAST_RID. XX is the radio index 5b24285d = DEL_RMT_BINDING 5b242c5d = COM_MULTI_RID 5b24305d = GATEWAY_ENABLE. Enable Coordinator function. 5b24325d = FFD_ENABLE. Enable Full Functional Device function as a Router. 5b2534XX5d = CHAN_RRCM_CHANNEL. XX is channel number (0x0B-0x1A). 5b2536XX5d = DEL_LOCAL_BINDING. XX is the binding index started from 1. 5b24385d = RPT_SENSOR_POSITION. 5b243E5d = LEAVE THE NETWORK. 5b24465d = RFD_ENABLE. Enable RFD function.
**PE7 High makes radio sleep.PE7 Low actives the radio. 5b24485d = SOFT_RST. Perform soft reset. 5b244A5d = RACTORY_RST. Restore the radio to factory setting. 5b244C5d = VERSION_CHK. Check the firmware version of the Radio. 5b244E5d = PRINT_TOKEN. Print stack and application tokens. 5b24505d = JOIN_FORM_NETWORK. Form (Gateway) or Join (Sensor) a new network. 5b24525d = MULTICAST_HELLO. Say HELLO to the world. 5b24545d = PRINT_CHILD_TABLE. Print Child table. 5b24565d = BOOT_LOADER. Launch the standalone boot loader. 5b24605d = GET_NODE_INFO. Get Radio's information like EUI, channel and PANID. 5b24625d = BUTTON_0_PRESS. Press Button 0. 5b24645d = BUTTON_1_PRESS. Press Button 1. 5b2566xx5d = SET_PROTOCOL. Set communication protocol. 5b24685d = GET_PARENT_ID. Get the parent ID for RFD. 5b24705d = JIT_MSG_STATUS. Just In Time Message Status. 5b24F05d = HELP 5b24F25d = PRINT ASCII BINDING TABLE. 5b2CF4xxxx0000006F0D005d = Pass the image to remote node through the Gateway. 5b2CF6xxxx0000006F0D005d = Clone the Gateway image to a remote node.
**RAEWATCH: 0, RCS: 1, Transparent: 2. 12 Command Name NETWORK_STATUS Use on:
Coordinator FFD RFD GET_BINDING_LIST Use on:
Coordinator FFD RFD SYNCH_ADVERTISE Use on:
Coordinator COM_UNICAST_RID Use on: Coordinator DEL_RMT_BINDING Use on: Coordinator COM_MULTI_RID Use on: Coordinator COOR_ENABLE Use on: FFD/RFD Table 5.2.1: Detailed information of RMCI package CMD Data CMD Code
(bytes) 0x20 None Response CMD Code 0x21 Response CMD Data (Bytes) STATUS(1) Description Return the radios network status 0x00: NO NETWORK 0x01: JOINING NETWORK 0x02: JOINED NETWORK 0x03: JOINED_NETWORK_NO_PARENT 0x04: LEAVING NETWORK For FFD and RFD: Radio return with bound target ID with index=0x00. For Coordinator: Return bound node ID with index separately for each bound radio nodes. Start from 0 and up to 30.
*: Use this command after SYNCH_ADVERTISE. Requests RCM to synchronize all radio nodes in the network to bind with the coordinator. Nodes are in the Unicast mode after executing this command. The maximum binding table size is 30 due to RAM limitation. Requests RCM to send following data to specified radio nodes in Unicast mode per radio index. Using datagram. Requests RCM to send a delete binding command to all nodes in network. All nodes in the network became to free nodes and will communicate in Multicast mode. RFD will not respond this command. Requests to go back to multicast mode after using COM_UNICAST_RID. All data after this command will be broadcasted. Set the radio as a Coordinator so that the radio can be use on a Gateway device. Baud rate change to 38400 8N1 0x22 None 0X23 Radio ID(8) Radio Index(1) 0x24 None 0X25 None 0x26 Radio index(1) 0X27 None. 0x28 None 0X29 None 0x2C None 0X2D none 0x30 None 0x31 None 13 Command Name FFD_ENABLE Use on: Coordinator/RFD CHG_RRCM_CHAN Use on:
Coordinator DEL_LOCAL_BINDING Use on:
Coordinator/FFD/RFD RPT_LOCATION Use on: RFD LEAVE_NETWORK Use on: Coordinator/FFD/RFD RFD_ENABLE Use on: Coordinator/FFD SOFT_RST FACTORY_RST Use on:
Coordinator/FFD/RFD VERSION_CHK Use on:
Coordinator/FFD/RFD Table 5.2.2: Detailed information of RMCI package CMD Data Response CMD Code 0x33 Response CMD Data (Bytes) None Description Set radio to FFD. Always on and has router function. CMD Code
(bytes) 0x32 None 0x34 0x36 Channel Number(1) Binding index(1) 0x35 None 0x37 None 0x38 None 0x39 None 0x3E None 0x3F None Requests RCM in the Gateway to change its radio channel to specified channel. 0x0B to 0x1A total 15 channels. Corresponding to 11 to 26 of IEEE 802.15.4. Deletes binding indexes stored in the radio. Binding index is from 1 to 30. Always 1 for FFD and RFD Report RFD parents ID. Leave the current network 0x46 None 0x47 None Put a node into RFD. PE7 interrupt enable. Active low. 0x48 0x4A None None 0x49 0x4B None None 0x4C None 0x4D DS[0] = V DS[1~n+1]
Firmware Version [0~n]
14 Reset the radio Restore the RCM to factory defaults. Channel: 0x1A, Power: 0xFF, PanID: 0x30FF Sensor Node FFD. Baud rate: 19200 8N1 Request Firmware Version. Return In ASCII. e.g.: EZ2.23.0.0 Send:5B244C5D Return:5B 2E 4D 45 5A 32 2E 32 33 2E 30 2E 30 5D Command Name PRINT_TOKEN Use on: Coordinator/FFD/RFD JION_FORM_NETWORK Use on:
Coordinator/FFD/RFD MULTICAST_HELLO Use on: Coordinator/FFDRFD PRINT_CHILD_TABLE Use on: Coordinator/FFD BOOT_LOAD Use on: Coordinator GET_NODE_INFO Use on:
Coordinator/FFD/RFD BUTTON_0_PRESS Use on: Coordinator/FFD/RFD BUTTON_1_PRESS Use on: Coordinator/FFD/RFD SET_PROTOCOL Use on: Coordinator/FFD/RFD Table 5.2.3: Detailed information of RMCI package CMD Data CMD Code
(bytes) 0x4E None Response CMD Code 0x4F Response CMD Data (Bytes) 0x50 None 0x51 None Description Print radios Token information in ASCII. For PC debug Coordinator:
Form a network to allow the other nodes to join. FFD/RFD:
Search the network and try to join the network. Broadcast a hello to entire network Print the child table in ASCII Start the bootloader to download the radio application Get the node information: EUI, Channel, Power, PAN ID, Send: 5B24605D Return:
5B 30 61 00 0D 6F 00 00 00 2D A5 1A FF 30 FF 5D Simulate Button Zero pressed 0x52 None 0x54 None 0x56 None 0x60 None 0x62 None 0x64 None 0x53 0x55 0x57 0x61 0x63 0x65 None None none Radio ID(8) Channel(1) Power(1) PAN ID(2) None None Simulate Button One Pressed 0x66 Protocol(1) 0x67 None Set radios protocol 0x00: RAEWATCH_PSP.(old version) 0x01: RAEWATCH_RCS. 0x02: Transparent Mode. 15 Command Name GET_PARENT_ID Use on:
RFD HELP Use on: Coordinator/FFD/RFD PRINT_BINDING_TABLE Use on: Coordinator/FFD/RFD BOOTLOAD_PASSTHROUGH Use on: Coordinator BOOTLOAD_CLONE Use on: Coordinator Table 5.2.4: Detailed information of RMCI package CMD Data CMD Code
(bytes) 0x68 None Response CMD Code 0x69 Response CMD Data (Bytes) radio Parent ID(8) Description Get the parent ID for RFD Return:
5B 2C 69 00 0D 6F 00 00 00 2E CB 5D if no parent, return 5B 2C 69 00 00 00 00 00 00 00 00 5D List all RMCI commands in ASCII 0xF0 None 0xA1 None 0xF2 None 0xA3 None List all bindings in a table in ASCII 0xF4 0xF6 Remote Radio ID(8) Remote Radio ID(8) 0xF5 None Bootload remote node in pass through mode. 0xF7 None Bootload remote node and update the firmware in clone mode. Fast way. 16 7. Mechanical Drawing 7.1 Top View ZcoRE3-2400_User_Manual_V1.0 Units: mm Note:
1: E1 is for the chip antenna and available only in ZcoRE3-2400. The length of the chip antenna is less than 7.3mm 2: P1 is the MMCX connector for SMA antenna (connect via an MMCX-SMA RF cable) and available only in ZcoRE3(20)-2400. 3: The height of the shield box on the top layer is less than 4.3mm from PCB board. 17 7.2 Bottom (top perspective) ZcoRE3-2400_User_Manual_V1.0 Units: mil Note:
1. J1 is the application and power supply interface (1.27mm pin header) which can be used for board-to-board connection. Pay attention to the direction of socket. 2. There are two holes on board revered for modem fixing. 18 8. Order Information ZcoRE3-2400_User_Manual_V1.0 REnex provide series of ZcoRE3 OEM module that vary in RF output power and frequency as well as standalone modems to cover a variety of application in different countries and regions. Products RF Power ZcoRE3-2400 ZcoRE3(20)-2400 ZcoRE3-868*
ZcoRE3(20)-868*
ZcoRE3-915*
ZcoRE3(20)-915*
0 dBm 18 dBm 0 dBm 18 dBm 0 dBm 18 dBm Dimension RF Regulation 46.5 x 26 x 10 mm Worldwide 46.5 x 26 x 10 mm worldwide 46.5 x 26 x 10 mm 46.5 x 26 x 10 mm 46.5 x 26 x 10 mm 46.5 x 26 x 10 mm Europe Europe USA USA 18 dBm 18 dBm 18 dBm REmesh-2400*
REmesh-868*
REmesh-915*
*Available in 2007 Product Ordering Information for the ZcoRE3-2400 series:
TBD TBD TBD Worldwide Europe USA Intrinsic Safety C1D1/ATEX(T4) C1D1/ATEX(T4) ATEX(T4) ATEX(T4) C1D1 C1D1 Type OEM OEM OEM OEM OEM OEM
Standalone Standalone Standalone Products Part Number of REnex ZcoRE3 -2400 ZcoRE3(20) -2400 R-001-0003-410 R-001-0003-400 Reference:
Ember: www.ember.com Atmel: www.atmel.com FCC: www.gcc.gov Zigbee Alliance: www.zigbee.org 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. REnex does not convey any license under its patent rights or assume any responsibility for the use of the described product. REnex Technology Limited REnex Technology (ShangHai) Limited Room 608, 6/F., Hong Leong Plaza Room C3-2, 3/F, No33 33 Lok Yip Road, Fanling, N.T., Hong Kong FuHua Road, JiaDing, Shanghai, China Tel: 852-2607-4088 Fax: 852-2669-0803 Tel: 86-021-59902255 Fax: 86-021-59902211 Email: Sales@renextechnology.com Email: Sales@renextechnology.com www.renextechnology.com www.renextech.com 19