M320 Quick Start Guide

Revision Notes

1. Overview

The M320 is a low-power wide-area IoT wireless communication module based on the STM32WLE5CC chip. The module complies with the LoRaWAN Specification 1.0.3 Class A/B/C published by LoRa Alliance.

The M320 uses a serial interface to interact with user host for data and commands, which can quickly provide users with services such as LoRaWAN network access and wireless data communication. The module supports connecting to a variety of LoRaWAN server platforms, such as The Things Network (TTN), Chirpstack, and so on, and it also supports point-to-point (P2P) communication mode, helping you quickly implement your own customized remote network.

M320 is characterized by small size, low power consumption, long transmission distance, and strong anti-interference ability, which makes it suitable for various low-power wide-area IoT application scenarios.

2. Module Preview

The M320 pinout is shown in Figure 2-1.

2.1 Pin Function

3. LoRaWAN Usage Guidelines

M320 supports LoRaWAN protocol and therefore supports data transfer over the LoRaWAN network. The master communicates with M320 through the serial port. The default serial port configuration is 115200, 8 data bits and 1 stop bit.

3.1 Join Network By APB

End-device can join a pre-selected network through ABP (Activation By Personalization) active mode. The Join Server is not involved in the ABP process. Before activation, the AppSKey, NwkSKey, and DADDR should be stored in the end device.

3. 1. 1 Setting The Network Mode

Set the network mode to LoRaWAN by AT+NWKM command.

3. 1. 2 Setting The Region Band

Set the region band by AT+BAND command.

3. 1. 3 Setting The AppSKey

Set the AppSKey by AT+APPSKEY command.

3. 1. 4 Setting The NwkSKey

Set the NwkSKey by AT+NWKSKEY command.

3. 1. 5 Setting The Device Network Address

Set the DADDR by AT+DADDR command.

3. 1. 6 Start Join Network

Set the active mode and start join network by AT+JOIN command.

3. 1. 7 Query Join Status

Check the join status by AT+JOINSTA command.

3. 1.8 Switch Class Mode

After join, end device can be switched to Class B or Class C by AT+CLASS command.

3. 1. 9 Send Data Through LoRaWAN Network

After join, device can send data to network server by AT+SEND command.

3.2 Join Network By OTAA

End device can also join network through OTAA (Over-The-Air-Activation) active mode, which perform a join procedure with the network, during which a dynamic device address is assigned and security keys are negotiated with the device. Before activation, the AppEUI, DevEUI, and AppKey should be stored in the end device.

3. 2. 1 Setting The Network Mode

Set the network mode to LoRaWAN by AT+NWKM command.

3. 2. 2 Setting The Region Band

Set the region band by AT+BAND command.

3. 2. 3 Setting The AppEUI

Set the AppEUI by AT+APPEUI command.

3. 2. 4 Setting The AppKey

Set the AppKey by AT+APPKEY command.

3. 2. 5 Setting The DEUI

Set the DEUI by AT+DEUI command.

3. 2. 6 Start Join Network

Set the active mode and start join network by AT+JOIN command.

3. 2. 7 Query Join Status

Check the join status by AT+JOINSTA command.

3.2.8 Switch Class Mode

After join, end device can be switched to Class B or Class C by AT+CLASS command.

3. 2. 9 Send Data Through LoRaWAN Network

After join, device can send data to network server by AT+SEND command.

3.3 P2P Usage Guidelines

M320 supports P2P mode communication and can exchange data between two modules directly. P2P mode supports FSK and LoRa.

3. 3. 1 Setting The Network Mode

Set the network mode to LoRaWAN by AT+NWKM command.

3. 3. 2 Setting The P2P Mode

Set the P2P configuration by AT+RFCONF command. To ensure successful communication, both modules need to be configured with the same parameters.

3. 3. 3 Start P2P RX

After P2P setting done, start P2P data receive by AT+RFRECV command.

3. 3. 4 Start P2P TX

At the same time, start P2P data transmission by AT+RFSEND command on the other module.

4. Common commands

The following are some commonly used AT commands, for complete commands please refer to the AT Command Manual.

4.1 Reboot (ATZ)

4.2 Restore Default Config (AT+RFS)

4.3 Log Level (AT+LOG)

4.4 Uart Baudrate (AT+BAUD)

4.5 Set Auto Run Command (AT+AR)

4.6 Clear Auto Run Command (AT+ARDEL)

4.7 Save Auto Run Command (AT+ARSAVE)

FCC Warning

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.

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

Important Note: In the event that these conditions cannot be met (for example certain laptop configurations or co-location with another transmitter), then the Federal Communications Commission of the U.S. Government (FCC) and the Canadian Government authorizations are no longer considered valid and the FCC ID cannot be used on the final product. In these circumstances, the OEM integrator shall be responsible for re-evaluating the end-product (including the transmitter) and obtaining a separate FCC authorization in the U.S. and Canada. OEM Integrators – End Product Labeling Considerations: This transmitter module is authorized only for use in device where the antenna may be installed such that 20 cm may be maintained between the antenna and users. The final end product must be labeled in a visible area with the following: " Contains, FCC ID: 2BM2KM320". The grantee's FCC ID can be used only when all FCC compliance requirements are met.

OEM Integrators – End Product Manual provided to the End User: The OEM integrator shall not provide information to the end user regarding how to install or remove this RF module in end product user manual. The end user manual must include all required regulatory information and warnings as outlined in this document.

2.2 List of applicable FCC rules

The device compliance with FCC Part 15.247

2.3 Summarize the specific operational use conditions

The OEM integrator is still responsible for testing their end-product for any additional compliance requirements required for the installed module

2.4 Limited module procedures

Device is single module approval

2.5 Trace antenna designs

PIFA antenna, antenna gain is 1.83dBi the antenna size as below

2.6 RF exposure considerations

Compliance with FCC Part 2.1091

This device is intended only for OEM integrators under the following conditions: 1.The antenna must be installed such that 20 cm is maintained between the antenna and users. 2. The transmitter module may not be co-located with any other transmitter or antenna. As long as the two conditions above are met, additional transmitter testing will not be required.

2.7 Antennas

PIFA antenna, antenna gain is 1.83dBi.

2.8 Label and compliance information

The label compliance with FCC requirement and the end product must be labeled in a visible area with the following: " Contains, FCC ID: 2BM2KM320"

2.9 Information on test modes and additional testing requirements

The module under Continuous transmit ion and lager than 98% duty cycle

2.10 Additional testing, Part 15 Subpart B disclaimer

The test results compliance with FCC Part 15B requirement

2.11 Note EMI Considerations

The host manufacturer is recommended to use FCC KDB 996369 D04 Module Integration Guide recommending as "best practice" RF design engineering testing and evaluation in case non-linear interactions generate additional non-compliant limits due to module placement to host components or properties

2.12 How to make changes

This module is stand-alone modular. If the end product will involve the Multiple simultaneously transmitting condition or different operational conditions for a stand-alone modular transmitter in a host, host manufacturer have to consult with module manufacturer for the installation method in end system.