Skip to content

Heltec v4.3 support#1857

Open
weebl2000 wants to merge 3 commits intomeshcore-dev:devfrom
weebl2000:heltec_v4.3
Open

Heltec v4.3 support#1857
weebl2000 wants to merge 3 commits intomeshcore-dev:devfrom
weebl2000:heltec_v4.3

Conversation

@weebl2000
Copy link
Contributor

@weebl2000 weebl2000 commented Feb 26, 2026

On Heltec V4 revision 3 there's a different FEM, KCT8103L instead of GC1109 used before.

Pinout is largely the same, except for GPIO5 now being used for TX switching with KCT8103L. Adjusted firmware accordingly. This makes the firmware fully compatible with all Heltec v4 variants.

Based on @Quency-D PR on MT.

BUILD FIRMWARE HERE

reference docs:

KCT8103L is similar to the KCT8101L, but different gain levels: KCT8101L.pdf

KCT8103L

@Quency-D
Copy link
Contributor

Thank you so much, you acted so quickly. But I was wondering if this method would be simpler, and would also make adding LNA control functions later on much easier?
https://github.com/Quency-D/MeshCore/tree/dev-heltec-v4.3

@weebl2000
Copy link
Contributor Author

weebl2000 commented Feb 26, 2026

Thank you so much, you acted so quickly. But I was wondering if this method would be simpler, and would also make adding LNA control functions later on much easier? https://github.com/Quency-D/MeshCore/tree/dev-heltec-v4.3

What LNA control functions do you think would be useful to add. Is there really any use-case where it should be disabled?

@Quency-D
Copy link
Contributor

It can control the LNA's on and off states.
image

@weebl2000
Copy link
Contributor Author

It can control the LNA's on and off states.

Would be interesting to have this. Do you know if testing was done where LNA bypass is useful? It would require a little more work and also meshcore firmware needs to know how to handle this. I think it would be a good follow-up as a separate PR to have more extensive PA/LNA control. That way we can keep this PR small to just support Heltec V4.3 with the current always on LNA.

@Quency-D
Copy link
Contributor

It can control the LNA's on and off states.

Would be interesting to have this. Do you know if testing was done where LNA bypass is useful? It would require a little more work and also meshcore firmware needs to know how to handle this. I think it would be a good follow-up as a separate PR to have more extensive PA/LNA control. That way we can keep this PR small to just support Heltec V4.3 with the current always on LNA.

Currently, turning off the LNA works well in noisy environments, but we are still testing it in other scenarios.

@towerviewcams
Copy link

towerviewcams commented Feb 26, 2026

I wake up to this! Do we have these boards and not know it? ha ha.... Where did/do you have the 4.3 @Quency-D @weebl2000 ?
Well this sure is major news. I will order some once I find them. Let the testing begin!!

@weebl2000
Copy link
Contributor Author

I wake up to this! Do we have these boards and not know it? ha ha.... Where did/do you have the 4.3 @Quency-D @weebl2000 ? Well this sure is major news. I will order some once I find them. Let the testing begin!!

See also:
https://wiki.heltec.org/docs/devices/open-source-hardware/esp32-series/lora-32/wifi-lora-32-v4/hardware-update-log#v431

@towerviewcams
Copy link

towerviewcams commented Feb 26, 2026

@weebl2000 @Quency-D
Do either of you know where I can purchase a couple of these 4.3.1 boards to start testing?

The GC1109 FEM needs its VFEM_Ctrl pin held HIGH during deep sleep
to keep the LNA active, enabling proper RX sensitivity for
wake-on-packet. Without this, the LNA is unpowered during sleep
and RX wake sensitivity is degraded by ~17dB.

Release RTC holds in begin() after configuring GPIO registers
(not before) to ensure glitch-free pin transitions on wake.

Trade-off: ~6.5mA additional sleep current for significantly
improved wake-on-packet range.
- runtime auto-detection of v4.3 board (KCT8103L FEM) vs V4.0-V4.2
(GC1109) via GPIO2 pull level
- different TX/RX path using PGIO5 for KCT8103L, GPIO46 CPS for GC1109
- hold both FEMs active for RX
- report Heltec V4.3 in manufacturer name
@weebl2000
Copy link
Contributor Author

@weebl2000 @Quency-D Do either of you know where I can purchase a couple of these 4.3.1 boards to start testing?

I highly suspect sellers are going to sell older boards until they get new stock. Your best bet might be the Heltec official store and ask them specifically if they ship out V4.3 yet :)

@Quency-D
Copy link
Contributor

@weebl2000 @Quency-D Do either of you know where I can purchase a couple of these 4.3.1 boards to start testing?

I asked around, and all you need to do is place your order on the Heltec website and note that you need version 4.3.

@Socalix
Copy link
Contributor

Socalix commented Feb 27, 2026

@Quency-D Do you offer any trade-in for those loyal early adopters that helped you realize v4.3 is needed? 😉

@Quency-D
Copy link
Contributor

@Quency-D Do you offer any trade-in for those loyal early adopters that helped you realize v4.3 is needed? 😉

You can send an email directly to support@heltec.cn, and a sales representative will provide a detailed response.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants