adam/pyMC_Repeater
1
0 Fork 0
mirror of https://github.com/pyMC-dev/pyMC_Repeater.git synced 2026-10-30 19:51:59 +01:00
Code Issues 41 Packages Projects Releases Wiki Activity

[RX] Header error detected (0x0020) - corrupted header, restoring RX mode #35

New Issue
Closed
opened 2026-10-27 09:29:31 +01:00 by adam · 15 comments
adam commented 2026-10-27 09:29:31 +01:00
Owner
Copy link
Copy source

Can seem to get the repeater to see any other devices, I have confirmed both are using the same RF settings, and the companion device works fine.

Hardware:
Raspberry PI 4
Waveshare SX1262 LoraWAN HAT (SKU: 22002)

Could it be simple as the Waveshare hat I have its not supported?

Feb 18 16:58:12 MeshCore pymc-repeater[1983]: 2026-02-18 16:58:12,258 - Dispatcher - INFO - Registered fallback handler for unknown payload types.
Feb 18 16:58:12 MeshCore pymc-repeater[1983]: 2026-02-18 16:58:12,259 - RepeaterDaemon - INFO - Packet router registered as fallback (catches all packets)
Feb 18 16:58:12 MeshCore pymc-repeater[1983]: 2026-02-18 16:58:12,259 - RepeaterDaemon - INFO - Trace processing helper initialized
Feb 18 16:58:12 MeshCore pymc-repeater[1983]: 2026-02-18 16:58:12,259 - RepeaterDaemon - INFO - Advert processing helper initialized
Feb 18 16:58:12 MeshCore pymc-repeater[1983]: 2026-02-18 16:58:12,259 - RepeaterDaemon - INFO - Discovery processing helper initialized
Feb 18 16:58:12 MeshCore pymc-repeater[1983]: 2026-02-18 16:58:12,259 - HTTPServer - INFO - CORS enabled: False
Feb 18 16:58:12 MeshCore pymc-repeater[1983]: 2026-02-18 16:58:12,367 - HTTPServer - INFO - HTTP stats server started on http://0.0.0.0:8000
Feb 18 16:58:21 MeshCore pymc-repeater[1983]: 2026-02-18 16:58:21,241 - Dispatcher - INFO - TX 115 bytes (type=ADVERT, route=FLOOD)
Feb 18 16:58:21 MeshCore pymc-repeater[1983]: 2026-02-18 16:58:21,242 - RepeaterDaemon - INFO - Sent flood advert 'My-Repeater' at ( 0.000000, 0.000000)
Feb 18 16:58:32 MeshCore pymc-repeater[1983]: 2026-02-18 16:58:32,312 - SX1262_wrapper - WARNING - [RX] Header error detected (0x0020) - corrupted header, restoring RX mode
Feb 18 17:01:37 MeshCore pymc-repeater[1983]: 2026-02-18 17:01:37,947 - Dispatcher - INFO - TX 115 bytes (type=ADVERT, route=FLOOD)
Feb 18 17:01:37 MeshCore pymc-repeater[1983]: 2026-02-18 17:01:37,948 - RepeaterDaemon - INFO - Sent flood advert 'My-Repeater' at ( 0.000000, 0.000000)
Feb 18 17:01:43 MeshCore pymc-repeater[1983]: 2026-02-18 17:01:43,773 - SX1262_wrapper - WARNING - [RX] Header error detected (0x0020) - corrupted header, restoring RX mode

Can seem to get the repeater to see any other devices, I have confirmed both are using the same RF settings, and the companion device works fine. Hardware: Raspberry PI 4 Waveshare SX1262 LoraWAN HAT (SKU: 22002) Could it be simple as the Waveshare hat I have its not supported? Feb 18 16:58:12 MeshCore pymc-repeater[1983]: 2026-02-18 16:58:12,258 - Dispatcher - INFO - Registered fallback handler for unknown payload types. Feb 18 16:58:12 MeshCore pymc-repeater[1983]: 2026-02-18 16:58:12,259 - RepeaterDaemon - INFO - Packet router registered as fallback (catches all packets) Feb 18 16:58:12 MeshCore pymc-repeater[1983]: 2026-02-18 16:58:12,259 - RepeaterDaemon - INFO - Trace processing helper initialized Feb 18 16:58:12 MeshCore pymc-repeater[1983]: 2026-02-18 16:58:12,259 - RepeaterDaemon - INFO - Advert processing helper initialized Feb 18 16:58:12 MeshCore pymc-repeater[1983]: 2026-02-18 16:58:12,259 - RepeaterDaemon - INFO - Discovery processing helper initialized Feb 18 16:58:12 MeshCore pymc-repeater[1983]: 2026-02-18 16:58:12,259 - HTTPServer - INFO - CORS enabled: False Feb 18 16:58:12 MeshCore pymc-repeater[1983]: 2026-02-18 16:58:12,367 - HTTPServer - INFO - HTTP stats server started on http://0.0.0.0:8000 Feb 18 16:58:21 MeshCore pymc-repeater[1983]: 2026-02-18 16:58:21,241 - Dispatcher - INFO - TX 115 bytes (type=ADVERT, route=FLOOD) Feb 18 16:58:21 MeshCore pymc-repeater[1983]: 2026-02-18 16:58:21,242 - RepeaterDaemon - INFO - Sent flood advert 'My-Repeater' at ( 0.000000, 0.000000) Feb 18 16:58:32 MeshCore pymc-repeater[1983]: 2026-02-18 16:58:32,312 - SX1262_wrapper - WARNING - [RX] Header error detected (0x0020) - corrupted header, restoring RX mode Feb 18 17:01:37 MeshCore pymc-repeater[1983]: 2026-02-18 17:01:37,947 - Dispatcher - INFO - TX 115 bytes (type=ADVERT, route=FLOOD) Feb 18 17:01:37 MeshCore pymc-repeater[1983]: 2026-02-18 17:01:37,948 - RepeaterDaemon - INFO - Sent flood advert 'My-Repeater' at ( 0.000000, 0.000000) Feb 18 17:01:43 MeshCore pymc-repeater[1983]: 2026-02-18 17:01:43,773 - SX1262_wrapper - WARNING - [RX] Header error detected (0x0020) - corrupted header, restoring RX mode <!-- github-sync-id:3956143415 -->
adam closed this issue 2026-10-27 09:29:31 +01:00
adam commented 2026-10-27 09:29:32 +01:00
Author
Owner
Copy link
Copy source

I am running the same setup but when purchasing I did note that there are a couple of different ones. I think the main difference was either the frequencies and GPS but worth checking Mine has worked amazingly well. Just want to get the MQTT bit working :)Thanks On 18 Feb 2026, at 06:06, jbalki @.***> wrote:jbalki created an issue (rightup/pyMC_Repeater#95)
Can seem to get the repeater to see any other devices, I have confirmed both are using the same RF settings, and the companion device works fine.
Hardware:
Raspberry PI 4
Waveshare SX1262 LoraWAN HAT (SKU: 22002)
Could it be simple as the Waveshare hat I have its not supported?
Feb 18 16:58:12 MeshCore pymc-repeater[1983]: 2026-02-18 16:58:12,258 - Dispatcher - INFO - Registered fallback handler for unknown payload types.
Feb 18 16:58:12 MeshCore pymc-repeater[1983]: 2026-02-18 16:58:12,259 - RepeaterDaemon - INFO - Packet router registered as fallback (catches all packets)
Feb 18 16:58:12 MeshCore pymc-repeater[1983]: 2026-02-18 16:58:12,259 - RepeaterDaemon - INFO - Trace processing helper initialized
Feb 18 16:58:12 MeshCore pymc-repeater[1983]: 2026-02-18 16:58:12,259 - RepeaterDaemon - INFO - Advert processing helper initialized
Feb 18 16:58:12 MeshCore pymc-repeater[1983]: 2026-02-18 16:58:12,259 - RepeaterDaemon - INFO - Discovery processing helper initialized
Feb 18 16:58:12 MeshCore pymc-repeater[1983]: 2026-02-18 16:58:12,259 - HTTPServer - INFO - CORS enabled: False
Feb 18 16:58:12 MeshCore pymc-repeater[1983]: 2026-02-18 16:58:12,367 - HTTPServer - INFO - HTTP stats server started on http://0.0.0.0:8000
Feb 18 16:58:21 MeshCore pymc-repeater[1983]: 2026-02-18 16:58:21,241 - Dispatcher - INFO - TX 115 bytes (type=ADVERT, route=FLOOD)
Feb 18 16:58:21 MeshCore pymc-repeater[1983]: 2026-02-18 16:58:21,242 - RepeaterDaemon - INFO - Sent flood advert 'My-Repeater' at ( 0.000000, 0.000000)
Feb 18 16:58:32 MeshCore pymc-repeater[1983]: 2026-02-18 16:58:32,312 - SX1262_wrapper - WARNING - [RX] Header error detected (0x0020) - corrupted header, restoring RX mode
Feb 18 17:01:37 MeshCore pymc-repeater[1983]: 2026-02-18 17:01:37,947 - Dispatcher - INFO - TX 115 bytes (type=ADVERT, route=FLOOD)
Feb 18 17:01:37 MeshCore pymc-repeater[1983]: 2026-02-18 17:01:37,948 - RepeaterDaemon - INFO - Sent flood advert 'My-Repeater' at ( 0.000000, 0.000000)
Feb 18 17:01:43 MeshCore pymc-repeater[1983]: 2026-02-18 17:01:43,773 - SX1262_wrapper - WARNING - [RX] Header error detected (0x0020) - corrupted header, restoring RX mode

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>

I am running the same setup but when purchasing I did note that there are a couple of different ones. I think the main difference was either the frequencies and GPS but worth checking Mine has worked amazingly well. Just want to get the MQTT bit working :)Thanks On 18 Feb 2026, at 06:06, jbalki ***@***.***> wrote:jbalki created an issue (rightup/pyMC_Repeater#95) Can seem to get the repeater to see any other devices, I have confirmed both are using the same RF settings, and the companion device works fine. Hardware: Raspberry PI 4 Waveshare SX1262 LoraWAN HAT (SKU: 22002) Could it be simple as the Waveshare hat I have its not supported? Feb 18 16:58:12 MeshCore pymc-repeater[1983]: 2026-02-18 16:58:12,258 - Dispatcher - INFO - Registered fallback handler for unknown payload types. Feb 18 16:58:12 MeshCore pymc-repeater[1983]: 2026-02-18 16:58:12,259 - RepeaterDaemon - INFO - Packet router registered as fallback (catches all packets) Feb 18 16:58:12 MeshCore pymc-repeater[1983]: 2026-02-18 16:58:12,259 - RepeaterDaemon - INFO - Trace processing helper initialized Feb 18 16:58:12 MeshCore pymc-repeater[1983]: 2026-02-18 16:58:12,259 - RepeaterDaemon - INFO - Advert processing helper initialized Feb 18 16:58:12 MeshCore pymc-repeater[1983]: 2026-02-18 16:58:12,259 - RepeaterDaemon - INFO - Discovery processing helper initialized Feb 18 16:58:12 MeshCore pymc-repeater[1983]: 2026-02-18 16:58:12,259 - HTTPServer - INFO - CORS enabled: False Feb 18 16:58:12 MeshCore pymc-repeater[1983]: 2026-02-18 16:58:12,367 - HTTPServer - INFO - HTTP stats server started on http://0.0.0.0:8000 Feb 18 16:58:21 MeshCore pymc-repeater[1983]: 2026-02-18 16:58:21,241 - Dispatcher - INFO - TX 115 bytes (type=ADVERT, route=FLOOD) Feb 18 16:58:21 MeshCore pymc-repeater[1983]: 2026-02-18 16:58:21,242 - RepeaterDaemon - INFO - Sent flood advert 'My-Repeater' at ( 0.000000, 0.000000) Feb 18 16:58:32 MeshCore pymc-repeater[1983]: 2026-02-18 16:58:32,312 - SX1262_wrapper - WARNING - [RX] Header error detected (0x0020) - corrupted header, restoring RX mode Feb 18 17:01:37 MeshCore pymc-repeater[1983]: 2026-02-18 17:01:37,947 - Dispatcher - INFO - TX 115 bytes (type=ADVERT, route=FLOOD) Feb 18 17:01:37 MeshCore pymc-repeater[1983]: 2026-02-18 17:01:37,948 - RepeaterDaemon - INFO - Sent flood advert 'My-Repeater' at ( 0.000000, 0.000000) Feb 18 17:01:43 MeshCore pymc-repeater[1983]: 2026-02-18 17:01:43,773 - SX1262_wrapper - WARNING - [RX] Header error detected (0x0020) - corrupted header, restoring RX mode —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: ***@***.***> <!-- github-comment-id:3920240926 -->
adam commented 2026-10-27 09:29:32 +01:00
Author
Owner
Copy link
Copy source

Thank you, mine is the 915 frequency, correct for my location and no GPS.

Thank you, mine is the 915 frequency, correct for my location and no GPS. <!-- github-comment-id:3922844523 -->
adam commented 2026-10-27 09:29:33 +01:00
Author
Owner
Copy link
Copy source

Seems that the issue exists on Australia (Narrow) frequency, when i move it to Australia frequency (and change settings on my companion device) it works fine.

In short:
916.575MHz SF7/BW62.5/CR8 fails with header errors,
915.800MHz SF10/BW250/CR5 works

I have also tried the US/Canada settings (BW62.5) and that also produces the same error. Looks like this could potentially be an issue with the 62.5 bandwidth.

Seems that the issue exists on Australia (Narrow) frequency, when i move it to Australia frequency (and change settings on my companion device) it works fine. In short: 916.575MHz SF7/BW62.5/CR8 fails with header errors, 915.800MHz SF10/BW250/CR5 works I have also tried the US/Canada settings (BW62.5) and that also produces the same error. Looks like this could potentially be an issue with the 62.5 bandwidth. <!-- github-comment-id:3924776038 -->
adam commented 2026-10-27 09:29:34 +01:00
Author
Owner
Copy link
Copy source

Have you tried the dev branch? there have been some changes in ref to this.

Have you tried the dev branch? there have been some changes in ref to this. <!-- github-comment-id:3944157575 -->
adam commented 2026-10-27 09:29:34 +01:00
Author
Owner
Copy link
Copy source

Have you tried the dev branch? there have been some changes in ref to this.

Im currently running the dev branch, and still receive the same error.

Image
> Have you tried the dev branch? there have been some changes in ref to this. Im currently running the dev branch, and still receive the same error. <img width="215" height="217" alt="Image" src="https://github.com/user-attachments/assets/a7b17e56-3a3a-46b4-8bc4-73d3df63a749" /> <!-- github-comment-id:3948771082 -->
adam commented 2026-10-27 09:29:35 +01:00
Author
Owner
Copy link
Copy source

Do you mind trying the feat/newRadios sorry I just realised I pushed the fix to that branch not dev.

Do you mind trying the feat/newRadios sorry I just realised I pushed the fix to that branch not dev. <!-- github-comment-id:3952096916 -->
adam commented 2026-10-27 09:29:35 +01:00
Author
Owner
Copy link
Copy source

Do you mind trying the feat/newRadios sorry I just realised I pushed the fix to that branch not dev.

I changed to the feat/newRadios. Seems a step in the right direction. I have had a flood message forwarded but still a lot of the same errors in the logs

> Do you mind trying the feat/newRadios sorry I just realised I pushed the fix to that branch not dev. I changed to the feat/newRadios. Seems a step in the right direction. I have had a flood message forwarded but still a lot of the same errors in the logs <!-- github-comment-id:3955297460 -->
adam commented 2026-10-27 09:29:36 +01:00
Author
Owner
Copy link
Copy source

updated to the latest feat/newRadios and im getting the same errors still and also some CRC errors.

2026-03-09 17:36:43,793 - SX1262_wrapper - WARNING - [RX] CRC error #1 - RSSI=-106dBm, SNR=-1.0dB, SignalRSSI=-108dBm, Length=40, Noise Floor=-116.2dBm, DeviceErrors=0x0000, IRQ=0x0042, RawData=2e8092f49d88c4538c6d99824ebb3ee96b54607edeff917bebd5446dae70b626053dbe6d71b53

updated to the latest feat/newRadios and im getting the same errors still and also some CRC errors. 2026-03-09 17:36:43,793 - SX1262_wrapper - WARNING - [RX] CRC error #1 - RSSI=-106dBm, SNR=-1.0dB, SignalRSSI=-108dBm, Length=40, Noise Floor=-116.2dBm, DeviceErrors=0x0000, IRQ=0x0042, RawData=2e8092f49d88c4538c6d99824ebb3ee96b54607edeff917bebd5446dae70b626053dbe6d71b53 <!-- github-comment-id:4021511855 -->
adam commented 2026-10-27 09:29:36 +01:00
Author
Owner
Copy link
Copy source

CRC errors like that are normal with LoRa and usually aren’t something to worry about on their own.

LoRa will still receive packets that are partially corrupted due to noise or weak signal, and the CRC check is simply what flags them as invalid so they get discarded. Seeing CRC errors just means the radio is detecting frames but the payload failed the integrity check.

Interference, collisions, RF noise, or having multiple repeaters transmitting in the same location can also cause this.

The important thing is that the radio is still receiving and validating packets correctly — CRC failures are part of normal LoRa operation.

CRC errors like that are normal with LoRa and usually aren’t something to worry about on their own. LoRa will still receive packets that are partially corrupted due to noise or weak signal, and the CRC check is simply what flags them as invalid so they get discarded. Seeing CRC errors just means the radio is detecting frames but the payload failed the integrity check. Interference, collisions, RF noise, or having multiple repeaters transmitting in the same location can also cause this. The important thing is that the radio is still receiving and validating packets correctly — CRC failures are part of normal LoRa operation. <!-- github-comment-id:4023603033 -->
adam commented 2026-10-27 09:29:37 +01:00
Author
Owner
Copy link
Copy source

Even though this is closed, still receiving [RX] Header error detected (0x0020) - corrupted header, restoring RX mode. I cannot see the device from my companion device, every time I ping from the companion device the error appears

Even though this is closed, still receiving [RX] Header error detected (0x0020) - corrupted header, restoring RX mode. I cannot see the device from my companion device, every time I ping from the companion device the error appears <!-- github-comment-id:4025895070 -->
adam commented 2026-10-27 09:29:38 +01:00
Author
Owner
Copy link
Copy source

Are you sure you have you radio settings correct freq etc

Sent from Outlook for iOShttps://aka.ms/o0ukef

From: jbalki @.>
Sent: Monday, March 9, 2026 6:32:27 PM
To: rightup/pyMC_Repeater @.>
Cc: Lloyd @.>; State change @.>
Subject: Re: [rightup/pyMC_Repeater] [RX] Header error detected (0x0020) - corrupted header, restoring RX mode (Issue #95)

[https://avatars.githubusercontent.com/u/29947722?s=20&v=4]jbalki left a comment (rightup/pyMC_Repeater#95)https://github.com/rightup/pyMC_Repeater/issues/95#issuecomment-4025895070

Even though this is closed, still receiving [RX] Header error detected (0x0020) - corrupted header, restoring RX mode. I cannot see the device from my companion device, every time I ping from the companion device the error appears

—
Reply to this email directly, view it on GitHubhttps://github.com/rightup/pyMC_Repeater/issues/95#issuecomment-4025895070, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACM32JOLO3XRXEJOD3PDJV34P4E3XAVCNFSM6AAAAACVP7EPEOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DAMRVHA4TKMBXGA.
You are receiving this because you modified the open/close state.Message ID: @.***>

Are you sure you have you radio settings correct freq etc Sent from Outlook for iOS<https://aka.ms/o0ukef> ________________________________ From: jbalki ***@***.***> Sent: Monday, March 9, 2026 6:32:27 PM To: rightup/pyMC_Repeater ***@***.***> Cc: Lloyd ***@***.***>; State change ***@***.***> Subject: Re: [rightup/pyMC_Repeater] [RX] Header error detected (0x0020) - corrupted header, restoring RX mode (Issue #95) [https://avatars.githubusercontent.com/u/29947722?s=20&v=4]jbalki left a comment (rightup/pyMC_Repeater#95)<https://github.com/rightup/pyMC_Repeater/issues/95#issuecomment-4025895070> Even though this is closed, still receiving [RX] Header error detected (0x0020) - corrupted header, restoring RX mode. I cannot see the device from my companion device, every time I ping from the companion device the error appears — Reply to this email directly, view it on GitHub<https://github.com/rightup/pyMC_Repeater/issues/95#issuecomment-4025895070>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ACM32JOLO3XRXEJOD3PDJV34P4E3XAVCNFSM6AAAAACVP7EPEOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DAMRVHA4TKMBXGA>. You are receiving this because you modified the open/close state.Message ID: ***@***.***> <!-- github-comment-id:4026961381 -->
adam commented 2026-10-27 09:29:38 +01:00
Author
Owner
Copy link
Copy source

Are you sure you have you radio settings correct freq etc

Yes, both set on Australia (Narrow). Earlier testing worked (main repo) when i changed both bandwidth to something higher like 150 then I was able to get them to talk

> Are you sure you have you radio settings correct freq etc > Yes, both set on Australia (Narrow). Earlier testing worked (main repo) when i changed both bandwidth to something higher like 150 then I was able to get them to talk <!-- github-comment-id:4026980667 -->
adam commented 2026-10-27 09:29:39 +01:00
Author
Owner
Copy link
Copy source

The waveshare board has no txco so it could be way off freq or something, I have a few and personally not seen an issue, do you have an sdr?

The waveshare board has no txco so it could be way off freq or something, I have a few and personally not seen an issue, do you have an sdr? <!-- github-comment-id:4027023431 -->
adam commented 2026-10-27 09:29:39 +01:00
Author
Owner
Copy link
Copy source

The waveshare board has no txco so it could be way off freq or something, I have a few and personally not seen an issue, do you have an sdr?

I do have an SDR, HackRF

> The waveshare board has no txco so it could be way off freq or something, I have a few and personally not seen an issue, do you have an sdr? I do have an SDR, HackRF <!-- github-comment-id:4027055396 -->
adam commented 2026-10-27 09:29:40 +01:00
Author
Owner
Copy link
Copy source

I would check that when transmitting from the repeater how far off it's from the set frequency etc.

I would check that when transmitting from the repeater how far off it's from the set frequency etc. <!-- github-comment-id:4027090503 -->
Sign in to join this conversation.
No Branch/Tag Specified
Labels
No items
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
adam (Adam Wojcieszonek)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/pyMC_Repeater#35