I have 2 Heltec V3.2 boards which do not receive packets on RF.
One board received some packets and further none and teh other never received anything.
On the displays there are no messages.
The first board gives this information:
heltec_wifi_lora_32_V3
-DELEGANTOTA_USE_ASYNC_WEBSERVER=1,-DRADIOLIB_EXCLUDE_CC1101=1,-DRADIOLIB_EXCLUDE_NRF24=1,-DRADIOLIB_EXCLUDE_RF69=1,-DRADIOLIB_EXCLUDE_SX1231=1,-DRADIOLIB_EXCLUDE_SX1233=1,-DRADIOLIB_EXCLUDE_SI443X=1,-DRADIOLIB_EXCLUDE_RFM2X=1,-DRADIOLIB_EXCLUDE_AFSK=1,-DRADIOLIB_EXCLUDE_BELL=1,-DRADIOLIB_EXCLUDE_HELLSCHREIBER=1,-DRADIOLIB_EXCLUDE_MORSE=1,-DRADIOLIB_EXCLUDE_RTTY=1,-DRADIOLIB_EXCLUDE_SSTV=1,-DRADIOLIB_EXCLUDE_AX25=1,-DRADIOLIB_EXCLUDE_DIRECT_RECEIVE=1,-DRADIOLIB_EXCLUDE_BELL=1,-DRADIOLIB_EXCLUDE_PAGER=1,-DRADIOLIB_EXCLUDE_FSK4=1,-DRADIOLIB_EXCLUDE_APRS=1,-DRADIOLIB_EXCLUDE_LORAWAN=1,-I variants/${PIOENV},-D HELTEC_V3_2
Version date: 2025-06-20
Build date: 2025-06-19 16:16:36 UTC
The second board gives this information:
heltec_wifi_lora_32_V3
-DELEGANTOTA_USE_ASYNC_WEBSERVER=1,-DRADIOLIB_EXCLUDE_CC1101=1,-DRADIOLIB_EXCLUDE_NRF24=1,-DRADIOLIB_EXCLUDE_RF69=1,-DRADIOLIB_EXCLUDE_SX1231=1,-DRADIOLIB_EXCLUDE_SX1233=1,-DRADIOLIB_EXCLUDE_SI443X=1,-DRADIOLIB_EXCLUDE_RFM2X=1,-DRADIOLIB_EXCLUDE_AFSK=1,-DRADIOLIB_EXCLUDE_BELL=1,-DRADIOLIB_EXCLUDE_HELLSCHREIBER=1,-DRADIOLIB_EXCLUDE_MORSE=1,-DRADIOLIB_EXCLUDE_RTTY=1,-DRADIOLIB_EXCLUDE_SSTV=1,-DRADIOLIB_EXCLUDE_AX25=1,-DRADIOLIB_EXCLUDE_DIRECT_RECEIVE=1,-DRADIOLIB_EXCLUDE_BELL=1,-DRADIOLIB_EXCLUDE_PAGER=1,-DRADIOLIB_EXCLUDE_FSK4=1,-DRADIOLIB_EXCLUDE_APRS=1,-DRADIOLIB_EXCLUDE_LORAWAN=1,-I variants/${PIOENV},-D HELTEC_V3_2
Version date: 2025-08-04
Build date: 2025-08-04 18:54:15 UTC
Funfact: the tracker from this author works fine with the same board.
My questions:
what can I do to debug this issue,
I anyone else having this problem?
Is this a known issue?
Thanks in advance.
I have 2 Heltec V3.2 boards which do not receive packets on RF.
One board received some packets and further none and teh other never received anything.
On the displays there are no messages.
The first board gives this information:
```
heltec_wifi_lora_32_V3
-DELEGANTOTA_USE_ASYNC_WEBSERVER=1,-DRADIOLIB_EXCLUDE_CC1101=1,-DRADIOLIB_EXCLUDE_NRF24=1,-DRADIOLIB_EXCLUDE_RF69=1,-DRADIOLIB_EXCLUDE_SX1231=1,-DRADIOLIB_EXCLUDE_SX1233=1,-DRADIOLIB_EXCLUDE_SI443X=1,-DRADIOLIB_EXCLUDE_RFM2X=1,-DRADIOLIB_EXCLUDE_AFSK=1,-DRADIOLIB_EXCLUDE_BELL=1,-DRADIOLIB_EXCLUDE_HELLSCHREIBER=1,-DRADIOLIB_EXCLUDE_MORSE=1,-DRADIOLIB_EXCLUDE_RTTY=1,-DRADIOLIB_EXCLUDE_SSTV=1,-DRADIOLIB_EXCLUDE_AX25=1,-DRADIOLIB_EXCLUDE_DIRECT_RECEIVE=1,-DRADIOLIB_EXCLUDE_BELL=1,-DRADIOLIB_EXCLUDE_PAGER=1,-DRADIOLIB_EXCLUDE_FSK4=1,-DRADIOLIB_EXCLUDE_APRS=1,-DRADIOLIB_EXCLUDE_LORAWAN=1,-I variants/${PIOENV},-D HELTEC_V3_2
Version date: 2025-06-20
Build date: 2025-06-19 16:16:36 UTC
```
The second board gives this information:
```
heltec_wifi_lora_32_V3
-DELEGANTOTA_USE_ASYNC_WEBSERVER=1,-DRADIOLIB_EXCLUDE_CC1101=1,-DRADIOLIB_EXCLUDE_NRF24=1,-DRADIOLIB_EXCLUDE_RF69=1,-DRADIOLIB_EXCLUDE_SX1231=1,-DRADIOLIB_EXCLUDE_SX1233=1,-DRADIOLIB_EXCLUDE_SI443X=1,-DRADIOLIB_EXCLUDE_RFM2X=1,-DRADIOLIB_EXCLUDE_AFSK=1,-DRADIOLIB_EXCLUDE_BELL=1,-DRADIOLIB_EXCLUDE_HELLSCHREIBER=1,-DRADIOLIB_EXCLUDE_MORSE=1,-DRADIOLIB_EXCLUDE_RTTY=1,-DRADIOLIB_EXCLUDE_SSTV=1,-DRADIOLIB_EXCLUDE_AX25=1,-DRADIOLIB_EXCLUDE_DIRECT_RECEIVE=1,-DRADIOLIB_EXCLUDE_BELL=1,-DRADIOLIB_EXCLUDE_PAGER=1,-DRADIOLIB_EXCLUDE_FSK4=1,-DRADIOLIB_EXCLUDE_APRS=1,-DRADIOLIB_EXCLUDE_LORAWAN=1,-I variants/${PIOENV},-D HELTEC_V3_2
Version date: 2025-08-04
Build date: 2025-08-04 18:54:15 UTC
```
The second board sends this over serial:
```
ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
rst:0x1 (POWERON),boot:0x8 (SPI_FAST_FLASH_BOOT)
SPIWP:0xee
mode:DIO, clock div:1
load:0x3fce3808,len:0x4bc
load:0x403c9700,len:0xbd8
load:0x403cc700,len:0x2a0c
entry 0x403c98d0
Starting Station: PE1MEW-10 Version: 2025-08-04
(DigiEcoMode: OFF)
Initializing LoRa Module
init : LoRa Module ... done!
Connecting to WiFi '<myssid>' ...
.Connected as <myIP> / MAC Address: B0:81:84:9A:49:94
Connecting to APRS-IS ... Connected!
(Server: rotate.aprs2.net / Port: 14580)
-- Sending Beacon to APRSIS --
```
Funfact: the tracker from this author works fine with the same board.
My questions:
- what can I do to debug this issue,
- I anyone else having this problem?
- Is this a known issue?
Thanks in advance.
<!-- github-sync-id:3373417165 -->
PE1MEW-10 is sending its beacon without any issue to APRS_IS over tcp/ip internet without any problem.
how or why do you mention you don't receive any other stations (trackers?)
if they are connected to WiFi you can look at the received packets on the WebUI.
CA2RXU.
Hi,
PE1MEW-10 is sending its beacon without any issue to APRS_IS over tcp/ip internet without any problem.
how or why do you mention you don't receive any other stations (trackers?)
if they are connected to WiFi you can look at the received packets on the WebUI.
CA2RXU.
<!-- github-comment-id:3243096032 -->
Hi, I have a car driving around (pe1mew-9) which is received by other I-gates. And my i-gate running on a Lillygo with the same software does receive all packets. at the same time the i-gate with the Helltec (PI1APD-10) is not receiving anything. this i-gate is located a 50 m heigh and a GP antenna.
From this I conclude that when I run the software on the Heltec board it does not work while on the Lillygo it does work (work means rceived RF signals are send to the internet) I observe received packets in the WebUI.
Hi, I have a car driving around (pe1mew-9) which is received by other I-gates. And my i-gate running on a Lillygo with the same software does receive all packets. at the same time the i-gate with the Helltec (PI1APD-10) is not receiving anything. this i-gate is located a 50 m heigh and a GP antenna.
From this I conclude that when I run the software on the Heltec board it does not work while on the Lillygo it does work (work means rceived RF signals are send to the internet) I observe received packets in the WebUI.
<!-- github-comment-id:3243115930 -->
so this happens only on the HELTEC_V3.2 boards (which does work indeed)
so we have to start solving this mystery:
can you post a picture of the board to validate is V3.2 and not V3 ???
the LoRa module configuration is the same on all boards, right?
so this happens only on the HELTEC_V3.2 boards (which does work indeed)
so we have to start solving this mystery:
1) can you post a picture of the board to validate is V3.2 and not V3 ???
2) the LoRa module configuration is the same on all boards, right?
<!-- github-comment-id:3243134964 -->
1: This is the board confirming V3.2:
<img width="400" height="480" alt="Image" src="https://github.com/user-attachments/assets/ab882278-c4d1-43b6-a0cc-b2edbf417e67" />
2: I don't know.
<!-- github-comment-id:3243138874 -->
so you flash with the HELTEC_V3.2 version of the iGate firmware webflasher, right?
lets jump into the configuration topic:
A) could you just flash 1 of them with the latest firmare... and only add:
callsign
GPS latitude and longitude
enable APRS-IS connection and add it with your passcode for your callsign.
Enable LoRa Rx and Tx and adjust the frequency to the same surrounding stations of yours
ok,
so you flash with the HELTEC_V3.2 version of the iGate firmware webflasher, right?
lets jump into the configuration topic:
A) could you just flash 1 of them with the latest firmare... and only add:
callsign
GPS latitude and longitude
enable APRS-IS connection and add it with your passcode for your callsign.
Enable LoRa Rx and Tx and adjust the frequency to the same surrounding stations of yours
<!-- github-comment-id:3243297182 -->
The not-working igate has "Enable LoRa TX" disabled and "Send beacon via APRS-IS" enabled. The first one required as that station has no HAM licence. Do you feel that this configuration may have caused the malfunction?
Yes, with this configuration, it works.
The not-working igate has "Enable LoRa TX" disabled and "Send beacon via APRS-IS" enabled. The first one required as that station has no HAM licence. Do you feel that this configuration may have caused the malfunction?
<!-- github-comment-id:3247825816 -->
The not-working igate has "Enable LoRa TX" disabled and "Send beacon via APRS-IS" enabled. The first one required as that station has no HAM licence. Do you feel that this configuration may have caused the malfunction?
not valid calling may have caused some problems when trying to enable LoRa Tx for sure.
is all else working fine for you now?
> Yes, with this configuration, it works.
>
> The not-working igate has "Enable LoRa TX" disabled and "Send beacon via APRS-IS" enabled. The first one required as that station has no HAM licence. Do you feel that this configuration may have caused the malfunction?
not valid calling may have caused some problems when trying to enable LoRa Tx for sure.
is all else working fine for you now?
<!-- github-comment-id:3249404885 -->
Based upon your information, the software seems to have undeterministic behaviour. I am not confident if teh software will operate stable on this hardware.
Today I-gate PI1APD-10 seem to work sometimes but is also missing packets over many hours. PE1MEW-10 seems to work continously now. I will monitor its operation the coming period.
Based upon your information, the software seems to have undeterministic behaviour. I am not confident if teh software will operate stable on this hardware.
Today I-gate PI1APD-10 seem to work sometimes but is also missing packets over many hours. PE1MEW-10 seems to work continously now. I will monitor its operation the coming period.
<!-- github-comment-id:3250136972 -->
let me know how the testing goes (but there are many Heltec V3.2 running well with it)
will close this "ISSUE" for now and if needed will reopen it
let me know how the testing goes (but there are many Heltec V3.2 running well with it)
will close this "ISSUE" for now and if needed will reopen it
<!-- github-comment-id:3250184740 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
I have 2 Heltec V3.2 boards which do not receive packets on RF.
One board received some packets and further none and teh other never received anything.
On the displays there are no messages.
The first board gives this information:
The second board gives this information:
The second board sends this over serial:
Funfact: the tracker from this author works fine with the same board.
My questions:
Thanks in advance.
Hi,
PE1MEW-10 is sending its beacon without any issue to APRS_IS over tcp/ip internet without any problem.
how or why do you mention you don't receive any other stations (trackers?)
if they are connected to WiFi you can look at the received packets on the WebUI.
CA2RXU.
Hi, I have a car driving around (pe1mew-9) which is received by other I-gates. And my i-gate running on a Lillygo with the same software does receive all packets. at the same time the i-gate with the Helltec (PI1APD-10) is not receiving anything. this i-gate is located a 50 m heigh and a GP antenna.
From this I conclude that when I run the software on the Heltec board it does not work while on the Lillygo it does work (work means rceived RF signals are send to the internet) I observe received packets in the WebUI.
so this happens only on the HELTEC_V3.2 boards (which does work indeed)
so we have to start solving this mystery:
1: This is the board confirming V3.2:
2: I don't know.
ok,
so you flash with the HELTEC_V3.2 version of the iGate firmware webflasher, right?
lets jump into the configuration topic:
A) could you just flash 1 of them with the latest firmare... and only add:
callsign
GPS latitude and longitude
enable APRS-IS connection and add it with your passcode for your callsign.
Enable LoRa Rx and Tx and adjust the frequency to the same surrounding stations of yours
Ok, w'll do that:
1: Done (with erase):
2: coordinates: set.
3: Enable RX and TX on local (default) frequency.
igate is running as pe1mew-10
so , do you see RX packet on the webui ?
Yes, with this configuration, it works.
The not-working igate has "Enable LoRa TX" disabled and "Send beacon via APRS-IS" enabled. The first one required as that station has no HAM licence. Do you feel that this configuration may have caused the malfunction?
not valid calling may have caused some problems when trying to enable LoRa Tx for sure.
is all else working fine for you now?
Based upon your information, the software seems to have undeterministic behaviour. I am not confident if teh software will operate stable on this hardware.
Today I-gate PI1APD-10 seem to work sometimes but is also missing packets over many hours. PE1MEW-10 seems to work continously now. I will monitor its operation the coming period.
let me know how the testing goes (but there are many Heltec V3.2 running well with it)
will close this "ISSUE" for now and if needed will reopen it
Thank you for your attention, I'll keep you posted. Best 73es.