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

MIC mismatch with ttgo lora #20

Closed
Bighoneypot opened this issue Oct 18, 2021 · 4 comments
Closed

MIC mismatch with ttgo lora #20

Bighoneypot opened this issue Oct 18, 2021 · 4 comments
Labels
question Further information is requested

Comments

@Bighoneypot
Copy link

Hi, with this firmware I have always error in TTN:
Join-request to cluster-local join server failed MIC mismatch

Do you have a idea?

Can you hel me? Thank you!

on terminal:

Device-id: ttgo-lora32-v1
LMIC library: MCCI
Activation: OTAA
Interval: 60 seconds

000000023153: Event: EV_JOINING

000000023943: doWork job started
000000161248: Event: EV_TXSTART
000000555186: Event: EV_JOIN_TXCOMPLETE

@lnlp
Copy link
Owner

lnlp commented Oct 27, 2021

Hi,

I just see your question (missed the notification).

Your MIC mismatch may be related to incorrect Network Layer settings.
For LMIC-node / MCCI LMIC I suggest to use the following Network Layer settings for a device:

  • LoRaWAN version: MAC V1.0.3
  • Regional parameters version: PHY V1.0.3 REV A

If the parameters for your device are currently different from above you may try to set them to above values.

There are several options to do this:

  1. In the console, change the exisiting device settings to the ones above.
    While this should work, in practice it may very well not (changed in console but not effective).

  2. Change the parameters via the commandline tool (see TTS docs and TTN forum for more information).
    This should work (but I have not verified it).

  3. In the console, delete the current device (this will render the device-id useless for later use), then in the same application create a new device for your node using above Network Layer settings (need to specify a new device-id).

  4. Same as 3. but create the device in a new application.
    Use only if 3 does not solve the issue.

A user with similar MIC mismatch issue (and same board) reported that option 4 fixed it and option 3 apparently did not but lacked further details. Maybe that was you? If the issue is Network Layer settings related then option 3 should work just as well (and is preferred over 4).

@lnlp lnlp added the question Further information is requested label Oct 27, 2021
@lnlp
Copy link
Owner

lnlp commented Nov 3, 2021

@Bighoneypot
Please respond.
Did above help to solve your issue?

@Bighoneypot
Copy link
Author

@lnlp
Gday,
yes I solve my issue with remove entire application and after I create new application the device work fine.

@lnlp
Copy link
Owner

lnlp commented Nov 4, 2021

Thanks. Good to hear your issue has been solved.

@lnlp lnlp closed this as completed Nov 4, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants