is there any way how to get some debug information in case when LoRa module returns JOIN_ERROR after sending AT$JOIN? Or it would help if JOIN_ERROR was followed with code of error and there was a list of possible reason i.e. “100=no LoRa wan signal in range” etc.
So, how can we quickly determine what we are doing wrong in case of JOIN_ERROR?
there are two ways how to get more info. Howvere the firmware from Murata really sends just JOIN ok and JOIN error. But you can check if there is not problem somwehere else.
Can you copy me complete list commands that you write after you do power reset? Can you check that you have set AT$MODE=1 (OTAA) because this parameter is always 0 after reset (ABP).
USB UART TTL converter
Connect to the P3 RXD1 pin and see the modem response after the JOIN command. Baudrate is 9600 baud. https://developers.bigclown.com/hardware/header-pinout
The response should be +EVENT=1,1 in case of success and +EVENT=1,0 in case of JOIN_ERROR. This is related to the table above. First 1 means its a join reponse, and the 1 or 0 is the answer if the join was successful. In some case with bad settings it is possible that the modem could response with some other message.
JOIN_OK, trick was in NWK parameter you mentioned. Funny thing is that it was set to 0 and I dad to set it to 1.
Thank you for your hint, now I have to try to decode LoRa module message on server side.