Ruixinghengfang Network UM02103 LoRa-2.4G Relay User Manual

Ruixinghengfang

UM02103
RHF0M083 User Manual
V1.0

Document information

Rising HF LoRa-2.4G module

Introduction

LoRa-2.4G relay designed by RisingHF follows LoRa-2.4G relay specification and adds customized features like buffer mode (LoRa-2.4G application payload decrypted) and reserved replay mode. The LoRa-2.4G relay or relay mentioned in this documentation stands for RisingHF relay.

LoRa-2.4G relay is defined to two roles, the slave and the master. During relay communication slave first, send the wake-up sequence (WS) to the wake-up master and let the master receive the WS packet, the wake-up sequence contains the following standard LoRa-2.4G uplink RF configuration (DR / CH). When finished WS packet receiving, master switch to uplink receiving mode to receive slave uplink with correct channel and data rate. To do it this way, slaves can communicate with relay and gateway together at the same time. If uplink is successfully received, the master sends on ACK to slave, slave knows uplink delivered successfully if ACK packet received, the ACK packet also contains a time synchronize information, to let slave sync it time with master to predict master’s CAD window and send shorter wake-up sequence, and thus save power. At the same time, the slave keeps LoRa-2.4G Class A RX1 and RX2. The additional RX3 window is for relay downlink communication.
Refer to the LoRa-2.4G timing diagram for details.

Get Started

Preparation

• USB to TTL Serial tool x 2pcs
• RHF0M083 x 2pcs
• PC
• Serial Terminal tool (SSCOM, PUTTY, TERATERM, etc.)

RHF0M083 must be at v5.x.x firmware. If it is not, upgrade first.

 Relay Communication (Manual Key Mode)

Before relay communication, the user should select one device as master and another as a slave.

1. Configure Slave
   a) AT+DR=LR24; (Or any other available band as wishes)
   b) AT+RELAY=SLAVE; Set device to slave mode
   c) AT+MODE=ABP
   d) AT+ID; Get slave DEVADDR

2. Configure Master
   a) AT+DR=LR24; (Use the same configuration as a slave)
   b) AT+RELAY=WL,ADD,devaddr,nwkskey,apps key,relay key (use slave’s DIVIDER/NWKSKEY/APPSKEY/RELAYSKEY)
   c) AT+RELAY=MASTER; Set device to master mode

3. Slave sends packet AT+MSG=xxxxxxx

4. Master receive packet by polling AT+RELAY=PL

Enable low power mode by sending AT+LOWPOWER=AUTOON to both master and slave, after low power mode is enabled, the user should send four 0xFF wake-up prefixes at each AT command.

Relay Communication (Auto Key Mode)

Before relay communication, the user should select one device as master and another as a slave.

1. Configure Slave
   a) AT+DR=LR24; (Or any other available band as wishes)
   b) AT+RELAY=SLAVE; Set device to slave mode
   c) AT+MODE=ABP
   d) AT+ID; Get slave DEVADDR
   e) AT+KEY=AUTO

2. Configure Master
   a) AT+DR=LR24; (Use the same configuration as slave)
   b) Register device address to master whitelist
   i. AT+RELAY=WL,ADD,devaddr specify a single DevAddr
   ii. AT+RELAY=WL,devaddr_min,devaddr_max specify device address range
   c) AT+RELAY=MASTER; Set device to master mode

3. Slave sends packet AT+MSG=xxxxxxx

4. Master receive packet by polling AT+RELAY=PL

Above communication use default RootKey, if the user needs to specify a new RootKey use “AT+KEY=RO OTKEY, asked” command to overwrite default one.

Advanced Application Guide

Slave LoRa-2.4G Communication

To simplify LoRa-2.4G relay design and increase communication system stability. The Relay implementation makes a trade-off on connectivity switch between relay and gateway challenges. Once configured relay slave will always try to communicate with Relay and let the application user decide which connectivity it should use (Configure through AT command).
AT + MSG / CMSG / MSGHEX / CMSGHEX are still available for packet transmitting. Relay slave LoRa-2.4G transaction will take a longer time to finish. Maximum timeout to be defined

Master LoRa-2.4G Communication

Relay master LoRa-2.4G communication will keep the same as standard LoRa-2.4G AT modem. AT + MSG / CMSG / MSGHEX / CMSGHEX are still available for relay master mode.

Relay Buffer Mode Limitation

• Relay Buffer Mode never supports an uplink frame counter which is larger than 0x3FFFFFF (67108863), it is equal to about 21 years’ time device transmitting at 10 seconds period
• If two master devices work closely, make sure the masters are isolated either by wake-up channel, RootKeys (Key Auto mode), or register device to a different master (manual mode). In a word, the whitelist or wake-up channel of the two masters must be carefully designed.
•  Relay Buffer Mode master doesn’t send ACK to the slave device
• Relay Buffer Mode doesn’t support ADR
• Relay Buffer Mode supports only ABP communication

Key Mode

 Automatic Session Key Workflow

1. Relay Slave set DevAddr / RootKey and enable auto key mode
2. Relay Master set the root key
3. Relay Master set DevAddr range
4. Relay Master and Slave communication without specifying any session key

Manually Bind Slave and Master Workflow

1. Relay Slave set DevAddr / NwkSKey / AppSKey / RelaySKey (nothing special, no need algorithm)
2. Relay Master set single DevAddr (DevAddr / NwkSKey / AppSKey / RelaySKey needed)
3. Relay Master and Slave communication

Master supports two workflows at the same time.

Relay Channel Configuration Guidance

Lora receiver is very sensitive and can restore signal under noise floor. This characteristic brings trouble when scanning CAD on two-channel. If the signal is strong and channel space is not far enough, the master is possible to be woken up on the wrong channel which leads to a communication error. This CAD error wake-up test aims to get a guideline about how to select channel space.

Relay Master Database

Relay master integrates a small footprint database to save slave information (whitelist and blacklist) in non-volatile areas. The database will be kept at each firmware upgrade without any notification, user can use AT+RELAY=WL / BL command to write and read the database.

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.
(2) This device must accept any interference received, including interference that may cause undesired operation.

NOTE: 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

NOTE: The manufacturer is not responsible for any radio or TV interference caused by unauthorized modifications to this equipment. Such modifications could void the user’s authority to operate the equipment.

This equipment complies with FCC radiation exposure limits set forth for an uncontrolled environment. This equipment should be installed and operated with a minimum distance of 20 cm between the radiator and your body. This transmitter must not be co-located or operating in conjunction with any other antenna or transmitter.

ORIGINAL EQUIPMENT MANUFACTURER (OEM) NOTES

The OEM must certify the final end product to comply with unintentional radiators before declaring compliance of the final product to Part 15 of the FCC rules and regulations. Integration into devices that are directly or indirectly connected to AC lines must add with Class II Permissive Change.
The OEM must comply with the FCC labeling requirements. If the module’s label is not visible when installed, then an additional permanent label must be applied on the  outside of the finished product which states:
“Contains transmitter module FCC ID: 2AJUZ0M083. Additionally, the following statement should be included on the label and in the final product’s user manual: “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 interferences, and (2) this device must accept any interference received,  including interference that may cause undesired operation.”
The module is limited to installation in mobile or fixed applications. Separate approval is required for all other operating configurations, including portable configuration with respect to Part 2.1093 and different antenna configurations.
Professional installation:
This module needs to be installed under professional guidance, if there is any questions, please contact us.
Antenna information：Gain: 2.0dBi; Type: Dipole antenna; Impedance: 50Ω
The module can work on the host device, which means the driver is matched, different host devices have different drives.
The host manufacturer can not get the module drive authorization to remain compliant until the host device is compliant with the requirements.
Note: The module has the antenna schematics, so the host device just provides the antenna connector for this device. The antenna port and connector is designed by OEM,  it needs to comply with the 15.203 requirements, and it is not designed for use with high-gain directional antennas.
A module or modules can only be used without additional authorizations if they have been tested and granted under the same intended end‐use operational conditions,  including simultaneous transmission operations.
When they have not been tested and granted in this manner, additional testing and/or FCC application filing may be required. The most straightforward approach to address additional testing conditions is to have the grantee responsible for the certification of at least one of the modules submit a permissive change application.
When having a module grantee file a permissive change is not practical or feasible, the following guide provides some additional options for host manufacturers.  Integrations using modules where additional testing and/or FCC application filing(s) may be required are: (A) a module used in devices requiring additional RF exposure compliance information (e.g., MPE evaluation or SAR testing); (B) limited and/or split modules not meeting all of the module requirements; and (C) simultaneous transmissions for independent collocated transmitters not previously granted together.
This Module is full modular approval, it is limited to OEM installation ONLY.
Integration into devices that are directly or indirectly connected to AC lines must add with Class II Permissive Change. (OEM) The integrator has to assure compliance of the entire end product including the integrated Module.
Additional measurements (15B) and/or equipment authorizations (e.g Verification) may need to be addressed depending on co-location or simultaneous transmission issues if applicable. (OEM) Integrator is reminded to assure that these installation instructions will not be made available to the end-user of the final host device.

Please Read Carefully:

Information in this document is provided solely in connection with RisingHF products. RisingHF reserves the right to make changes, corrections, modifications or improvements, to this document, and the products and services described herein at any time, without notice.

All RisingHF products are sold pursuant to RisingHF’s terms and conditions of sale.

Purchasers are solely responsible for the choice, selection, and use of the RisingHF products and services described herein, and RisingHF assumes no liability whatsoever relating to the choice, selection, or use of the RisingHF products and services described herein.

No license, express or implied, by estoppel or otherwise, to any intellectual property rights is granted under this document. If any part of this document refers to any third party products or services it shall not be deemed a license grant by RisingHF for the use of such third party products or services, or any intellectual property contained therein or considered as a warranty covering the use in any manner whatsoever of such third party products or services or any intellectual property contained therein.

UNLESS OTHERWISE SET FORTH IN RISINGHF’S TERMS AND CONDITIONS OF SALE RisingHF DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY WITH RESPECT TO THE USE AND/OR SALE OF RisingHF PRODUCTS INCLUDING WITHOUT LIMITATION IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE (AND THEIR EQUIVALENTS UNDER THE LAWS OF ANY JURISDICTION), OR INFRINGEMENT OF ANY PATENT, COPYRIGHT OR OTHER INTELLECTUAL PROPERTY RIGHT.

RISINGHF PRODUCTS ARE NOT DESIGNED OR AUTHORIZED FOR USE IN: (A) SAFETY- CRITICAL APPLICATIONS SUCH AS LIFE-SUPPORTING, ACTIVE IMPLANTED DEVICES OR SYSTEMS WITH PRODUCT FUNCTIONAL SAFETY REQUIREMENTS; (B) AERONAUTIC APPLICATIONS; (C) AUTOMOTIVE APPLICATIONS OR ENVIRONMENTS, AND/OR (D) AEROSPACE APPLICATIONS OR ENVIRONMENTS. WHERE RISINGHF PRODUCTS ARE NOT DESIGNED FOR SUCH USE, THE PURCHASER SHALL USE PRODUCTS AT PURCHASER’S SOLE RISK, EVEN IF RISINGHF HAS BEEN INFORMED IN WRITING OF SUCH USAGE, UNLESS A PRODUCT IS EXPRESSLY DESIGNATED BY RISINGHF AS BEING INTENDED FOR “AUTOMOTIVE, AUTOMOTIVE SAFETY OR MEDICAL” INDUSTRY DOMAINS ACCORDING TO RISINGHF PRODUCT DESIGN SPECIFICATIONS. PRODUCTS FORMALLY ESCC, QML, OR JAN QUALIFIED ARE DEEMED SUITABLE FOR USE IN AEROSPACE BY THE CORRESPONDING GOVERNMENTAL AGENCY.

Resale of RisingHF products with provisions different from the statements and/or technical features set forth in this document shall immediately void any warranty granted by RisingHF for the RisingHF product or service described herein and shall not create or extend in any manner whatsoever, any liability of RisingHF.

RisingHF and the RisingHF logos are trademarks or registered trademarks of RisingHF in various countries.
Information in this document supersedes and replaces all information previously supplied.
The RisingHF logo is a registered trademark of RisingHF. All other names are the property of their respective owners.

© 2015 – 2021 RISINGHF – All rights reserved
http://www.risinghf.com

V1.0 2021-02-07
www.risinghf.com

References

• RisingHF

Read User Manual Online (PDF format)

Read User Manual Online (PDF format)  >>

Download This Manual (PDF format)

Download this manual  >>