Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LoRaWAN 1.0.x and SX176 returning RADIOLIB_ERR_LORA_HEADER_DAMAGED #1271

Closed
oseiler2 opened this issue Oct 13, 2024 · 1 comment
Closed

LoRaWAN 1.0.x and SX176 returning RADIOLIB_ERR_LORA_HEADER_DAMAGED #1271

oseiler2 opened this issue Oct 13, 2024 · 1 comment
Labels
duplicate This issue or pull request already exists

Comments

@oseiler2
Copy link

RadioLib v7.0.2

I just came across an issue where activateOTAA returns RADIOLIB_ERR_LORA_HEADER_DAMAGED when using LoRaWAN spec 1.0.4 on an SX1276 ESP32 board. When I change the spec to 1.1 it works fine.

I've had a look through the source and believe that I have identified the root cause. processJoinAccept has a comment to ignore RADIOLIB_ERR_LORA_HEADER_DAMAGED for SX127x but does not override state - this only happens further down for spec 1.1 devices (state = LoRaWANNode::pushMacCommand), but not for 1.0.x. The method then returns RADIOLIB_ERR_LORA_HEADER_DAMAGED.

// downlink frames are sent without CRC, which will raise error on SX127x
  // we can ignore that error
  if(state != RADIOLIB_ERR_LORA_HEADER_DAMAGED) {
    RADIOLIB_ASSERT(state);
  }

Now that I was looking through the latest source to link from here I found a commit that should this issue:
a7feeee

I'll submit this issue for completeness, but feel free to close once that above commit is released. Thanks

@jgromes
Copy link
Owner

jgromes commented Oct 13, 2024

As you can see in #1262, the commit you have mentioned has been merged. To me it is quite pointless to keep open issues for resolved stuff. You can use the latest master if you really need to have this fixed, or you can wait for the next update.

Closing as duplicate.

@jgromes jgromes closed this as not planned Won't fix, can't repro, duplicate, stale Oct 13, 2024
@jgromes jgromes added the duplicate This issue or pull request already exists label Oct 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

2 participants