Giters

lnlp / LMIC-node

LMIC-node | One example to rule them all. LMIC-node is an example LoRaWAN application for a node that can be used with The Things Network. It demonstrates how to send uplink messages, how to receive downlink messages, how to implement a downlink command and it provides useful status information. With LMIC-node it is easy to get a working node quickly up and running. LMIC-node supports many popular (LoRa) development boards out of the box. It uses the Arduino framework, the LMIC LoRaWAN library and PlatformIO.

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

MIC mismatch with ttgo lora

Bighoneypot opened this issue · comments

commented

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

commented

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).

commented

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

commented

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

commented

Thanks. Good to hear your issue has been solved.