Heltec V4 Setup Guide
Heltec V4 (WiFi LoRa 32 V4) - Setup Guide
The Heltec V4 offers higher TX power than the V3 (the high-power variant is rated ~28 dBm vs the V3's 21 dBm; a low-power 22 dBm variant also exists) and includes a built-in solar charging interface, making it well-suited for permanent outdoor installations. Note: the "Heltec V4" (WiFi LoRa 32 V4) is a distinct product from the Heltec Vision Master series (e.g. T190) — they share the ESP32-S3 + SX1262 platform but are different boards with different form factors and separate flasher entries. This page covers the WiFi LoRa 32 V4 only.
Specifications
| Attribute | Value |
|---|---|
| MCU | ESP32-S3 |
| Radio | SX1262 |
| Max TX Power | ~28 dBm conducted (~630 mW) on the high-power variant, via the onboard front-end module (PA); a low-power variant is ~22 dBm. The SX1262 itself is +22 dBm max — the extra gain comes from the FEM, so actual output and EIRP must account for the FEM plus any filter/coax loss. |
| Solar | Built-in solar charging interface |
| USB | USB-C (native ESP32-S3 USB) |
| Price | $25 - 35 (as of 2026-06-08; prices vary by seller and tariff) |
| Strengths | Higher TX power than V3, solar interface, good for permanent installs |
Driver Installation
The Heltec V4 removed the external USB-serial bridge chip (the CP2102 used on the V3 is gone). It uses the ESP32-S3's native USB CDC, so it generally needs no separate USB-serial driver on any modern operating system.
- Windows: Modern Windows enumerates the V4's native USB CDC automatically and assigns a COM port — no CH340/CP210x driver download is required.
- macOS: Native USB CDC enumerates automatically; no WCH/CH34x or CP210x driver needed.
- Linux: The kernel enumerates the V4's native USB CDC automatically — no driver needed.
Entering Bootloader / DFU Mode
Method 1 - From powered-off state (recommended):
- Disconnect the USB cable.
- Hold the BOOT button.
- Connect the USB cable while continuing to hold BOOT.
- Hold for 1 - 2 seconds after connecting, then release BOOT.
Method 2 - From powered-on state:
Firmware Flashing
- Enter bootloader mode (see above).
- Open Chrome or Edge and navigate to:
- MeshCore: flasher.meshcore.io
- Meshtastic: flasher.meshtastic.org
- Select the Heltec V4 variant from the device list.
- Click Flash and grant serial port access when prompted.
- Wait for completion. Device reboots automatically.
Post-Flash Configuration
- Connect via Bluetooth app.
- Set region to US.
- Select the appropriate channel preset (MeshCore: USA/Canada; Meshtastic: US region).
- Configure solar charging settings if using a solar panel.
Known Quirks & Fixes
- Do not wrap the PCB in aluminum foil. An ungrounded foil wrap is not a Faraday shield — it can detune the antenna matching and the BLE/Wi-Fi antennas, short exposed pads or pins, and parasitically couple into the front end, often making self-interference worse. Proper shielding uses a grounded board-level shield can soldered over the RF section only, keeping the antenna connector and feed clear.
- Add a 915 MHz bandpass filter (JMT or Baymesh) on the antenna line — this is usually the most effective single fix.
rxgain is enabled by default on
V4.3 hardware. This improves receive sensitivity but adds ~0.5 mA idle draw. If the device is power-critical
(e.g., solar with a limited panel), you can disable it via serial or Bluetooth. Verify the exact command and the default behavior against your firmware version's MeshCore release notes before relying on it — syntax can change between versions:
set radio.rxgain off
No comments to display
No comments to display