>> Back to LoRa Main topics

lamaPLC: Ebyte LoRA products

Model SeriesChip SolutionFrequency RangePowerDistanceKey Features
E220 SeriesLLCC68410–493 / 850–930 MHz22–30 dBm5–10 kmNew generation, lower power, faster speed than SX127x
E22 SeriesSX1262 / SX1268170 / 230 / 433 / 868 / 915 MHz22–33 dBm5–16 kmHigh efficiency, supports air wake-up and deep sleep
E30 SeriesSI4463 / SI4438148–173.5 / 433 MHz20–27 dBm~2-5 kmIndustrial-grade stability for specific narrow bands
E32 SeriesSX1276 / SX1278170 / 433 / 868 / 915 MHz20–37 dBm5–25 kmClassic “workhorse” series; TTL level, widely compatible

Key Technical Specifications

  • Operating Voltage: Most modules are compatible with 3.3V to 5V for the IO port.
  • Transmission Modes: These modules typically feature four operating modes (Normal, Wake-up, Power-saving, and Sleep) controlled via M0 and M1 pins.
  • Interface: Primarily uses UART (Serial Port) for transparent transmission, making it easy to interface with Arduino or Raspberry Pi.
  • Antenna Options: Available in SMD (stamp hole) or DIP (pin header) packages with IPEX or SMA antenna connectors.

E32 Series Comparison Table

The E32 series is based on the Semtech SX1276 and SX1278 chips, utilizing LoRa spread-spectrum technology for long-range, interference-resistant communication.

ModelChipFrequencyPowerDistanceInterface
E32-868T30DSX1276868 MHz30 dBm8.0 kmUART (TTL)
E32-868T20DSX1276868 MHz20 dBm3.0 kmUART (TTL)
E32-433T30DSX1278433 MHz30 dBm8.0 kmUART (TTL)
E32-433T20DSX1278433 MHz20 dBm3.0 kmUART (TTL)
E32-170T30DSX1278170 MHz30 dBm8.0 kmUART (TTL)
E32-900T20DSX1276862–931 MHz20 dBm3.0 kmUART (TTL)

E32 DIP Series Pinout

The Ebyte E32 series LoRa modules usually have either a 7-pin or 22-pin configuration, depending on the model (DIP or SMD). For the standard E32-433T20D and E32-TTL-100 (DIP models), the pinout is listed below:

Pin No.ItemDirectionDescription
1M0InputOperating mode control (with M1). Must not float
2M1InputOperating mode control (with M0). Must not float
3RXDInputUART TTL input. Connects to external TXD. 3.3V Logic
4TXDOutputUART TTL output. Connects to external RXD. 3.3V Logic
5AUXOutputIndicates status (Busy/Idle) or self-check initialization (3.3V when HIGH)
6VCCPowerPower supply: 2.3V to 5.5V DC
7GNDPowerGround

Configuration and Pins (M0, M1)

ModeM1M0Description
Normal0 (GND)0 (GND)UART and wireless channel are open; transparent transmission
Wake-up0 (GND)1 (VCC*)Same as normal, but adds a preamble to wake up the receiver
Power-saving1 (VCC*)0 (GND)WOR (Wake On Radio) mode; receiving only
Sleep1 (VCC*)1 (VCC*)Used for parameter configuration via AT commands or Ebyte software

*Note: VCC for logic pins must be 3.3V, even if the main module VCC is 5V.

Power Supply (VCC): Most E32 modules can be powered directly from a 5V supply, and some models require at least 5V to ensure maximum performance at high transmit power (e.g., 30dBm/1W versions).

Logic Level: The UART interface operates at 3.3V TTL. Using 5V logic from an MCU like an Arduino Uno without a level shifter can damage the module.

  • Level Shifting: Use a level shifter or a voltage divider (such as 2kΩ and 1kΩ resistors) on the RX, M0, and M1 pins.
  • Pull-up Resistors: For 5V MCUs, it is recommended to add 4.7kΩ to 10kΩ pull-up resistors to the TXD and AUX pins to enhance stability.

E32 module "AT" commands

In Sleep Mode (M1=1, M0=1), the E32 module does not use standard text-based “AT” commands (like AT+VER). Instead, it uses Hexadecimal Control Commands sent at a fixed baud rate of 9600bps (9600, 8N1).

All commands must be sent as a sequence of bytes. The module will not respond if the format is incorrect.

Command (HEX)PurposeResponse from Module
C0 + 5 bytesSet & Save: Configures parameters and saves to EEPROM (persists after power-off)C0 + 5 bytes (Current config)
C2 + 5 bytesSet Temporary: Configures parameters for current session only (lost after power-off)C0 + 5 bytes (Current config)
C1 C1 C1Read Config: Requests the current working parametersC0 + 5 bytes (Current config)
Default: 192-0-0-26-6-68,
Default Address :00
Default channel: 6
C3 C3 C3Read Version: Requests the hardware and firmware version infoC3 + Frequency code + Version + Features
Example 192-69-12-30
Frequency code:
Hex 46, dec 70: 170 MHz
Hex 45, dec 69: 868 MHz
Hex 44, dec 68: 915 MHz
Hex 38, dec 56: 470 MHz
Hex 32, dec 50: 433 MHz
C4 C4 C4Reset: Performs a software reset of the moduleNone (AUX pin goes LOW then HIGH)

Parameter Byte Format (for C0/C2)

When configuring, send a total of 6 bytes: 1 Command Byte and 5 Parameter Bytes:

  1. HEAD: 0xC0 (Save) or 0xC2 (Temporary).
  2. ADDH: High byte of module address (00-FF).
  3. ADDL: Low byte of module address (00-FF).
  4. SPED: UART parity, UART baud rate, and Air data rate.
  5. CHAN: Communication channel (Frequency = 410M + CHAN * 1M).
  6. OPTION: Transmission mode (Fixed/Transparent), IO drive mode, Wake-up time, FEC, and Transmit power.

Example: Reading the Version

To check your module version, send these three bytes in HEX via your serial monitor: C3 C3 C3

The module will return 4 bytes, with the second byte typically indicating the frequency (e.g., 0x32 for 433 MHz).

Operational Tip: Monitor the AUX pin; it will go LOW while the module processes a command and return HIGH when it is ready for the next one.

Another Example: High-Performance Configuration (Fixed Transmission)

If you want to use Fixed Transmission (sending to specific addresses) at 115.2kbps UART speed and maximum power (20dBm), send:

Command: C0 00 01 3F 17 C0

Byte Breakdown:

  • C0: Save to EEPROM.
  • 00 01: Sets Module Address to 1.
  • 3F: UART 115200bps, 8N1, Air Data Rate 19.2kbps.
  • 17: Channel 23 (433MHz for 433 series).
  • C0: Fixed transmission mode, Pull-up enabled, FEC on, 20dBm power.

Another Example: Change Frequency/Channel

To change the module to a different frequency (e.g., 430MHz on a 433MHz module), adjust the 5th byte:

Command: C0 00 00 1A 14 44

Calculation: 410M + Channel * 1M. Here, 14 (Hex) = 20 (Dec). So, 410 + 20 = 430MHz

Communication topics on lamaPLC

PageDateTags
2026/04/23 21:51, , , , , , , , , , , , , , , , , , , , , , ,
2026/04/23 21:51, , , , , , ,
2026/04/23 21:51, , , , , , , ,
2026/04/23 21:51, , , , , , , , , , , , ,
2026/04/23 21:51, , , , , , , ,
2026/04/23 21:51, , , , , , , , , , , , , ,
2024/11/16 21:08, , , , , , , , , , , , , ,
2026/04/23 21:51, , , , , , , , ,
2024/11/16 20:43, , , , , , , , , , , , , ,
2024/11/16 01:16, , , , , ,
2026/04/23 21:51, , , , , , , , , , , , ,
2024/11/15 21:15, , , , , , , , , , ,
2026/04/23 21:51, , , , , , , , ,
2024/11/16 01:46, , , , ,
2026/04/23 21:51, , , , , , , , , , , , , , , , , , , , , , , , , , , , ,
2025/09/23 21:25, , , , , ,
2026/04/23 21:51, , , , , , , , , , ,
2026/04/23 21:51, , , , , , , , , , , ,
2026/04/23 21:51, , , , , , , , ,
2024/11/15 21:28, , , , , , , , , , , , , ,
2026/04/23 21:51, , , , , , ,
2024/11/16 02:26, , , , , , ,
2024/11/15 21:33, , , , , , , , , , , , , , ,
2026/04/23 21:51, , , , , , , ,
2026/04/23 21:51, , , , , , , , ,
2026/04/23 21:51, , , , , , , , , , , , , , , , , ,
2026/04/23 21:51, , , ,
2026/04/23 21:51, , , ,
2026/04/23 21:51, , , , ,
2026/04/23 21:51, , , ,
2026/04/23 21:51, , , , , , , , , ,
2026/04/23 21:51, , , , , , , ,
2025/11/20 22:49, , , , , , , , , , , , , , , , , , , , ,
2024/11/15 23:07, , , , , , , , , , ,
2026/04/23 21:51, , , , ,
2026/04/23 21:51, , , , , , , , , , ,
2026/04/23 21:51, , , , ,
2026/04/23 21:51, , , , , , , , , , , , ,
2024/11/16 00:36, , , , , , , , , , , , , , ,
2026/04/23 21:51, , , , ,
2026/04/23 21:51, , , , , , , , , , , , , , , , , , , , , , ,
2026/03/22 03:14, , , , , , ,
2026/04/23 21:51, , , , , , , ,
2026/04/23 21:52, , , , , , , , , , , , ,
2026/03/28 23:50, , , , , , ,
2026/04/23 21:52, , , , , , , , , , , , , ,
2026/03/06 01:19, , , , , ,
2026/04/23 21:52, , , , , , , , , , ,
2026/04/23 21:52, , , , , , , , , ,
2026/04/23 21:52, , , , , , , , , , ,
2026/04/23 21:52, , , , , , , , , , , , ,
2026/04/23 21:52, , , , , , , ,
2026/04/23 21:52, , , , , ,
2026/04/23 21:51, , , ,
2025/05/31 23:32, , , , , , , ,
2026/04/23 21:52, , , , , , , , , , , , , ,
2025/11/22 00:07, , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,
2023/07/01 17:29, , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,
2026/04/23 21:52, , , , , , , , ,
2026/04/23 21:52, , , , , , , , , , , , , , , ,
2026/04/23 21:52, , , , , , , , , , , , , , , , , , , , , , , , ,
2026/04/11 18:28, , , , , , , , , , ,
2026/04/11 19:54, , , , , , , , , , , , , , , , , , ,
2026/04/23 21:52, , , , , , , , , , ,
2026/04/23 21:51, , , , , , , , , , , , , , ,
2026/02/14 18:27, , , , , , , , , ,
2026/04/23 21:52, , , , ,
2026/04/23 21:52, , , , , , ,
2026/04/23 21:52, , , , , , , ,
2026/04/23 21:52, , , , , , , , , , , , , , , , , ,
2026/04/23 21:52, , , , , , , ,
2026/04/23 21:51, , , , , , , , ,
2026/02/14 18:42, , , , , , ,
2026/04/23 21:52, , , , , , , ,
2026/04/23 21:52, , , , , , , , , ,
2023/06/19 23:24, , , , , , , , , , , , ,
2026/04/15 19:41, , , , , , , , , , , , , , , ,
2026/04/23 21:52, , , , , , , , , , , , , ,
2026/02/14 23:51, , , , , ,
2026/04/23 21:52, , , , , , , , , , , , , , , , , , , , , , , ,
2026/04/23 21:52, , , , , , , , , , , , ,
2026/04/23 21:51, , , , , , ,
2023/06/25 00:43, , , , , ,
2026/04/23 21:52, , , , , , , , , , ,
2026/04/23 21:52, , , , , , , ,
2026/03/07 01:46, , , , , , , , , , ,
2024/08/18 16:52, , , , , , ,
2026/02/15 00:00, , , , , , , , ,
2026/03/05 21:19, , , , , , , , , , , , , , , , ,
2026/02/14 18:49, , , , , ,
2026/04/23 21:52, , , , , , , , , , , , , , , ,
2026/04/23 21:52, , , , ,
2026/04/23 21:52, , , , , , ,




This page has been accessed for: Today: 2, Until now: 4