Wiki source code of LoRaWAN Communication Debug

Version 32.14 by Xiaoling on 2022/07/13 15:24

version	line-number	content
32.2	1	~ Table of Contents:
1.1	2
	3	{{toc/}}
	4
	5
30.2	6
1.1	7	= 1. OTAA Join Process Debug =
	8
32.3	9
1.1	10	These pages are useful to check what is wrong on the Join process. Below shows the four steps that we can check the Join Process.
2.1	11	\\If user has checked below steps and still can't solve the problem, please send us (support @ dragino.com) the sceenshots for each step to check. They include:
1.1	12
	13	* End node console to show the Join freuqency and DR. (If possible)
	14	* Gateway (from gateway UI) traffic to show the packet got from end node and receive from Server. (If possible)
	15	* Gateway traffic (from server UI) to shows the data exchange between gateway and server. (Normaly possible)
	16	* End Node traffic (from server UI) to shows end node activity in server. (Normaly possible)
	17	* End Node Keys screen shot shows in end node and server. so we can check if the keys are correct. (In most case, we found keys doesn't match, especially APP EUI)
	18
	19
32.14	20
	21	(% style="color:blue" %)1. End Device Join Screen shot, we can check:
	22
1.1	23	* If the device is sending join request to server?
	24	* What frequency the device is sending?
	25
23.2	26	[[image:image-20220526164956-15.png]]
1.1	27
	28	Console Output from End device to see the transmit frequency
	29
	30
32.14	31	(% style="color:blue" %)2. Gateway packet traffic in gateway web or ssh. we can check:
1.1	32
	33	* If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency)
	34	* If the gateway gets the Join Accept message from server and transmit it via LoRa?
	35
10.2	36	[[image:image-20220526163608-2.png]]
1.1	37
	38	Console Output from Gateway to see packets between end node and server.
	39
	40
32.14	41	(% style="color:blue" %)3. Gateway Traffic Page in LoRaWAN Server
1.1	42
	43	* If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings.
	44	* If the server send back a Join Accept for the Join Request? if not, check if the keys from the device match the keys you put in the server, or try to choose a different server route for this end device.
	45	* If the Join Accept message are in correct frequency? If you set the server to use US915 band, and your end node and gateway is EU868, you will see the Join Accept message are in US915 band so no possible to Join success.
	46
13.2	47	[[image:image-20220526163633-3.png]]
1.1	48
	49	The Traffic for the End node in the server, use TTN as example
	50
	51
32.14	52	(% style="color:blue" %)4. Data Page in LoRaWAN server
1.1	53
	54	* If this data page shows the Join Request message from the end node? If not, most properly you have wrong settings in the keys. Keys in the server doesn't match the keys in End Node.
	55
13.2	56	[[image:image-20220526163704-4.png]]
1.1	57
	58	The data for the end device set in server
	59
13.2	60	[[image:image-20220526163732-5.png]]
1.1	61
	62	Check if OTAA Keys match the keys in device
	63
	64
2.1	65	= 2. Notice of US915/CN470/AU915 Frequency band =
1.1	66
32.3	67
4.2	68	(((
1.1	69	If user has problem to work with lorawan server in band US915/AU915/CN470, he can check:
4.2	70	)))
1.1	71
4.2	72	* (((
	73	What sub-band the server support ?
	74	)))
	75	* (((
	76	What is the sub-band the gateway support ?
	77	)))
	78	* (((
	79	What is the sub-band the end node is using ?
	80	)))
1.1	81
4.2	82	(((
1.1	83	All of above should match so End Node can properly Join the server and don't have packet lost.
4.2	84	)))
1.1	85
4.2	86	(((
	87
	88	)))
	89
	90	(((
1.1	91	In LoRaWAN protocol, the frequency bands US915, AU915, CN470 each includes at least 72 frequencies. Many gateways support only 8 or 16 frequencies, and server might support 8 frequency only. In this case, the OTAA join time and uplink schedule is long and unpredictable while the end node is hopping in 72 frequencies, because the end node will send data in many frequency that the gateway or server doesn,t support.
4.2	92	)))
1.1	93
4.2	94	(((
	95
	96	)))
	97
	98	(((
1.1	99	Here are the freuqency tables for these bands as reference:
4.2	100	)))
1.1	101
14.2	102	[[image:image-20220526163801-6.png]]
1.1	103
	104	US915 Channels
	105
18.2	106	[[image:image-20220526163926-7.png]]
1.1	107
	108	AU915 Channels
	109
32.3	110
18.2	111	[[image:image-20220526163941-8.png]]
1.1	112
4.4	113	(((
1.1	114	CN470 Channels
32.3	115
	116
4.4	117	)))
1.1	118
4.3	119	(((
1.1	120	If we look at the [[TTN network server frequency plan>>url:https://www.thethingsnetwork.org/docs/lorawan/frequency-plans.html]], we can see the US915 frequency band use the channel 8~~15.So the End Node must work at the same frequency in US915 8~~15 channels for TTN server.
4.3	121	)))
1.1	122
18.2	123	[[image:image-20220526164052-9.png]]
1.1	124
4.4	125	(((
1.1	126	TTN FREQUENCY PLAN
32.3	127
	128
4.4	129	)))
1.1	130
4.3	131	(((
1.1	132	In dragino end node, user can use AT+CHE command to set what frequencies set the end node will use. The default settings for Dragino end node are preconfigure for TTN server, so use 8~~15 channels, which is AT+CHE=2. (AT+CHE=1 for first 8 channels, AT+CHE=2 for second 8 channels.. etc, and AT+CHE=0 for all 72 channels. )
4.3	133	)))
1.1	134
	135
2.1	136	= 3. Why i see data lost/unperiocially uplink data? Even the signal strength is good =
1.1	137
32.3	138
1.1	139	In this case, we can check if the frequency band matches in End Node, Gateway and LoRaWAN server. A typical case is using US915 in ChirpStack server as below:
	140
2.1	141	* End node ~-~-> Use Sub-band2 (Channel 8,9,10,11,12,13,14,15) for Dragino Sensor. ADR is also enable, this is the default settings for dragino sensors.
	142	* Gateway ~-~-> Use Sub-band2 (Channel 8,9,10,11,12,13,14,15) for Dragino Gateway. this is the default settings for dragino sensors.
	143	* LoRaWAN server ~-~-> ChirpStack default installation and use Sub-band1, enabled_uplink_channels=[0, 1, 2, 3, 4, 5, 6, 7] in the file chirpstack-network-server.toml.
1.1	144
4.3	145	(((
1.1	146	When Sensor power on, it will use sub-band2 to join the network, the frequency matches the settings in gateway so all Join Request will be passed to the server for Join. Server will ask the sensor to change to Sub-band1 in the Join Accept downlink message. Sensor will change to sub-band1 for data upload. This cause the sensor and gateway have different frequencies so user see lost of most data or even no data.
4.3	147	)))
1.1	148
4.3	149	(((
	150
	151	)))
	152
	153	(((
1.1	154	Use Subband2 as a default subband cause the sensor to have problem to work with the LoRaWAN server which use other subband, and use need to access to the end node to change the subband by console. that is not user frendily,. So since Dragino LoRaWAN Stack version DLS-005(release on end of 2020), we have changed the device to use All Subbands for OTAA join, for example, device will use the first frequency in Sub-Band1 as firt OTAA join packet, then use the first frequency in Sub-Band 2 , then first frequency in sub-band 3, and so on. LoRaWAN server will normally provide the required subband in the OTAA accept process, so end node will know what subband it use after join. If LoRaWAN server doesn't provide subband info in OTAA join, end node will use the subband which join success as the working subband. So the new method cause a longer OTAA Join time but will be compatible with all LoRaWAN server. And new method won't affect the normal uplink after Join Success.
4.3	155	)))
1.1	156
	157
2.1	158	= 4. Transmision on ABP Mode =
1.1	159
32.3	160
4.3	161	(((
1.1	162	In ABP mode, there is a Frame Counter Checks. With this check enabled, the server will only accept the frame with a higher counter. If you reboot the device in ABP mode, the device will start from count 0, so you won't be able to see the frame update in server.
4.3	163	)))
1.1	164
4.3	165	(((
	166
	167	)))
	168
	169	(((
1.1	170	So in ABP mode, first check if the packet already arrive your gateway, if the packet arrive gatewat but didn't arrive server. Please check if this is the issue.
4.3	171	)))
1.1	172
4.3	173	(((
	174
	175	)))
	176
	177	(((
1.1	178	To solve this, disable the Frame Counter Check will solve this issue , or reset the frame counter in the device page.
4.3	179	)))
1.1	180
18.2	181	[[image:image-20220526164508-10.png]]
1.1	182
	183	Disable Frame Counter Check in ABP Mode
	184
	185
2.1	186	= 5. Downstream Debug =
1.1	187
2.1	188	== 5.1 How it work ==
1.1	189
32.3	190
1.1	191	LoRaWAN End node will open two receive windows to receive the downstream data. If the downstream packets arrive the end node at these receive windows, the end node will be able to get this packet and process it.
	192
4.3	193	(((
1.1	194	Depends on Class A or Class C, the receive windows will be a little difference,
4.3	195	)))
1.1	196
31.2	197	[[image:image-20220531161828-1.png]]
1.1	198
	199	receive windows for Class A and Class C
	200
32.3	201
1.1	202	Below are the requirement for the End Device to receive the packets.
	203
	204	* The End Device must open the receive windows: RX1 or RX2
	205	* The LoRaWAN server must send a downstream packet, and the gateway forward this downstream packet for this end node.
	206	* This downstream packet must arrive to the end node while RX1 or RX2 is open.
	207	* This packet must match the frequency of the RX1 or RX2 window.
32.3	208	* This packet must match the DataRate of RX1(RX1DR) or RX2 (RX2DR). (% style="color:red" %)This is the common fail point, because different lorawan server might use different RX2DR and they don't info End Node via ADR message so cause the mismatch. If this happen, user need to change the RX2DR to the right value in end node. In OTAA, LoRaWAN Server will send the RX2DR setting in Join Accept message so the end node will auto adjust. but ABP uplink doesn't support this auto change.
1.1	209
2.1	210	== 5.2 See Debug Info ==
1.1	211
32.3	212
4.6	213	(((
32.3	214	(% style="color:blue" %)For LoRaWAN Server
4.6	215	)))
1.1	216
4.6	217	(((
1.1	218	We can check if there is downlink message for this end node, use TTN for example:
4.6	219	)))
1.1	220
4.6	221	(((
1.1	222	Configure a downstream to the end device
4.6	223	)))
1.1	224
22.2	225	[[image:image-20220526164623-12.png]]
1.1	226
4.6	227	(((
1.1	228	Set a downstream in TTN and see it is sent
4.6	229	)))
1.1	230
	231
4.3	232	(((
1.1	233	This downstream info will then pass to the gateway downstream list. and include the DR which is used (SF9BW125) in EU868 is DR3
4.3	234	)))
1.1	235
22.2	236	[[image:image-20220526164650-13.png]]
1.1	237
4.6	238	(((
1.1	239	Gateway Traffic can see this downstream info
4.6	240	)))
1.1	241
	242
4.6	243	(((
32.3	244	(% style="color:blue" %)For LoRaWAN Gateway
4.6	245	)))
1.1	246
4.3	247	(((
1.1	248	When the downstream packet appear on the traffic of Gateway page. The LoRaWAN gateway can get it from LoRaWAN server and transmit it. In Dragion Gateway, this can be checked by runinng "logread -f" in the SSH console. and see below:
4.3	249	)))
1.1	250
22.2	251	[[image:image-20220526164734-14.png]]
1.1	252
4.6	253	(((
1.1	254	Gateway Sent out this packet
4.6	255	)))
1.1	256
	257
4.6	258	(((
32.3	259	(% style="color:blue" %)For End Node
4.6	260	)))
1.1	261
4.8	262	(((
1.1	263	we can use AT Command (AT+CFG) to check the RX1 configure and RX2 configure. as below:
4.8	264	)))
1.1	265
4.9	266	(((
32.4	267	(% style="color:#037691" %)AT+RX2FQ=869525000 (%%) ~-~--> The RX2 Window frequency
	268	(% style="color:#037691" %)AT+RX2DR=3 (%%) ~-~--> The RX2 DataRate
	269	(% style="color:#037691" %)AT+RX1DL=1000 (%%) ~-~--> Receive Delay 1
	270	(% style="color:#037691" %)AT+RX2DL=2000 (%%) ~-~--> Receive Delay 2
	271
4.9	272
	273	)))
	274
	275	(((
32.3	276	(% style="color:blue" %)when the device running, we can see below info:
4.7	277	)))
1.1	278
4.8	279	{{{ [12502]*** UpLinkCounter= 0 ***
	280	[12503]TX on freq 868500000 Hz at DR 0
	281	[13992]txDone
4.13	282	[15022]RX on freq 868500000 Hz at DR 0 --> RX1 window open at frequency: 868500000, DR0, after 15022-13992= 1030ms of txdone
	283	[15222]rxTimeOut --> no packet arrive in RX1 window. (duration: 200ms)
	284	[15987]RX on freq 869525000 Hz at DR 3 --> RX2 window open at frequency: 869525000, DR3, after 15987-13992= 1995ms of txdone
	285	[16027]rxTimeOut --> no packet arrive in RX2 window. (duration: 40 ms)}}}
1.1	286
4.3	287	(((
4.5	288
	289	)))
	290
4.7	291	(((
32.3	292	(% style="color:blue" %)Another message:
4.7	293	)))
4.5	294
4.8	295	{{{ [12502]*** UpLinkCounter= 0 ***
	296	[12503]TX on freq 868100000 Hz at DR 0
	297	[13992]txDone
	298	[15022]RX on freq 868100000 Hz at DR 0
	299	[15222]rxTimeOut
	300	[15987]RX on freq 869525000 Hz at DR 3
4.13	301	[16185]rxDone --> We have got the downstream packet.
4.8	302	Rssi= -64
	303	Receive data
	304	1:0012345678}}}
4.5	305
22.2	306
32.6	307	== 5.3 If problem doesn't solve ==
1.1	308
32.6	309
23.2	310	(% style="color:red" %)If user has checked below steps and still can't solve the problem, please send us (support @ dragino.com) the sceenshots for each step to check. They include:
1.1	311
	312	* End node console to show the transmit freuqency and DR.
	313	* Gateway (from gateway UI) traffic to show the packet got from end node and receive from Server.
	314	* Gateway traffic (from server UI) to shows the data exchange between gateway and server.
	315	* End Node traffic (from server UI) to shows end node activity in server.
	316
32.6	317
	318
2.1	319	= 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
1.1	320
32.7	321
4.5	322	(((
1.1	323	In LoRaWAN, the gatewat will use the frequency specify by the server to transmit a packet as downlink purpose. Each Frequency band has different downlink frequency. and the gateway has a frequency range limited to transmit downlink.
4.5	324	)))
1.1	325
4.5	326	(((
	327
	328	)))
	329
	330	(((
1.1	331	So if the LoRaWAN server is an AS923 server which ask the gateway to transmit at 923.2Mhz frequency, but the gateway is IN868 frequency band (support 865~~867Mhz to transmit). In the gateway log it will show something like below:
4.5	332	)))
1.1	333
4.7	334	{{{Sat Nov 21 08:04:17 2020 daemon.info lora_pkt_fwd[1680]: ERROR~ Packet REJECTED, unsupported frequency - 923200000 (min:865000000,max:867000000)}}}
1.1	335
4.5	336	(((
4.6	337
	338	)))
	339
	340	(((
1.1	341	In this case, please double check the gateway frequency and the server frequency band.
4.5	342	)))
1.1	343
	344
2.1	345	= 7. Decrypt a LoRaWAN Packet =
1.1	346
	347
32.7	348	(% style="color:blue" %)1. LHT65 End device configure:
1.1	349
32.7	350	Change to ABP Mode: AT+NJM=0
	351	Change to fix frequency: AT+CHS=904900000
	352	Change to fix DR: AT+DR=0
	353
32.12	354
29.2	355	[[image:image-20220526165525-16.png]]
1.1	356
29.2	357
32.7	358	(% style="color:blue" %)2. In LG02 , configure to receive above message
1.1	359
29.2	360	[[image:image-20220526165612-17.png]]
1.1	361
29.2	362
1.1	363	In LG02 console, we can see the hex receive are:
	364
29.2	365	[[image:image-20220526171112-21.png]]
1.1	366
29.2	367
32.7	368	(% style="color:blue" %)3. Decode the info in web
1.1	369
	370	[[https:~~/~~/lorawan-packet-decoder-0ta6puiniaut.runkit.sh>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/]]
	371
	372	Need these three fields:
	373
	374	LoRa packet hex format: 40c1190126800100024926272bf18bbb6341584e27e23245 (from LG02)
	375
	376	AT+NWKSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 11 (End node Network Session Key)
	377
	378	AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 11 (End Node App Session Key)
	379
32.9	380
1.1	381	[[https:~~/~~/lorawan-packet-decoder-0ta6puiniaut.runkit.sh/?data=40c1190126800100024926272bf18bbb6341584e27e23245&nwkskey=00000000000000000000000000000111&appskey=00000000000000000000000000000111>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/?data=40c1190126800100024926272bf18bbb6341584e27e23245&nwkskey=00000000000000000000000000000111&appskey=00000000000000000000000000000111]]
	382
29.2	383	[[image:image-20220526171029-20.png]]
1.1	384
4.10	385	(((
4.11	386	The FRMPayload is the device payload.
4.10	387	)))
1.1	388
	389
2.1	390	= 8. Why i see uplink 0x00 periodcally on the LHT65 v1.8 firmware =
1.1	391
32.9	392
1.1	393	Since firmware v1.8, LHT65 will send MAC command to request time, in the case if DR only support max 11 bytes, this MAC command will be bundled to a separate uplink payload with 0x00.
	394
29.3	395
2.1	396	= 9. Why do I see a "MIC Mismatch" error message from the server? =
1.1	397
32.9	398
4.7	399	(((
32.9	400	1) If the user receives a "MIC Mismatch" message after registering the node on the server.
4.7	401	)))
1.1	402
4.7	403	(((
1.1	404	It is likely that the user filled in the wrong APPKEY when registering the node. Many users fill in "APPSKEY".
4.7	405	)))
1.1	406
4.7	407	* (((
	408	Please note the distinction between "APPKEY" and "APPSKEY".
	409	)))
1.1	410
4.7	411	(((
1.1	412	2）If the node works on the server for a period of time, the device stops working and receives a "MIC Mismatch" message.
4.7	413	)))
1.1	414
4.7	415	(((
1.1	416	The user needs a USB-TTL adapter to connect the serial port to modify the node APPKEY.
4.7	417	)))
1.1	418
4.7	419	* (((
	420	If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
5.1	421
32.9	422
	423
5.1	424
4.7	425	)))
1.1	426
2.1	427	= 10. Why i got the payload only with "0x00" or "AA~=~="? =
1.1	428
32.9	429
4.16	430	* If you are using US915, AU915 and AS923 frequencies.This is normal phenomenon.
1.1	431
4.7	432	(((
4.19	433	When using the frequency mentioned above, the server sometimes adjusts the rate of the node, because the node defaults to the adaptive rate.
4.7	434	)))
1.1	435
4.7	436	(((
4.19	437	When the server adjusts your node rate to 0, the maximum payload length is 11 bytes. The server sometimes sends an ADR packet to the node,and the node will reply to the server after receiving the ADR packet, but the number of payload bytes exceeds the limit,so it will send a normal uplink packet, and an additional 00 data packet.
4.7	438	)))
1.1	439
4.7	440	* (((
	441	Solution: Use the decoder to filter out this 00 packet.
	442	)))
	443	* (((
6.1	444	Some node decoders may not have filtering function, or you need decoders of other servers and formats. Please send an email to [[david.huang@dragino.cc>>mailto:david.huang@dragino.cc]]
	445
32.9	446
	447
6.1	448
4.7	449	)))
1.1	450
5.1	451	= 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
	452
32.9	453
29.4	454	(((
7.1	455	It is possible the keys is erased during upgrading of firmware. and the console output shows below after AT+CFG
29.4	456	)))
5.1	457
29.4	458	(((
5.1	459	AT+APPKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
29.4	460	)))
5.1	461
29.4	462	(((
5.1	463	AT+NWKSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
29.4	464	)))
5.1	465
29.4	466	(((
5.1	467	AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
29.4	468	)))
5.1	469
29.4	470	(((
5.1	471	AT+APPEUI=00 00 00 00 00 00 00 00
29.4	472	)))
5.1	473
29.4	474	(((
	475
	476	)))
5.1	477
29.4	478	(((
5.1	479	You can get the keys from the box sticker or send mail to Dragino Support to check keys with the provided SN number.
29.4	480	)))
5.1	481
29.4	482	(((
5.1	483	You can rewrites the keys by running commands in AT Console
32.9	484
	485
29.4	486	)))
5.1	487
29.4	488	(((
	489	For example：
	490	)))
5.1	491
29.4	492	(((
8.1	493	AT+APPKEY=85 41 47 20 45 58 28 14 16 82 A0 F0 80 0D DD EE
29.4	494	)))
5.1	495
29.4	496	(((
8.1	497	AT+NWKSKEY=AA CC B0 20 30 45 37 32 14 1E 14 93 E2 3B 20 11
29.4	498	)))
8.1	499
29.4	500	(((
8.1	501	AT+APPSKEY=11 23 02 20 30 20 30 60 80 20 20 30 30 20 10 10
29.4	502	)))
8.1	503
29.4	504	(((
8.1	505	AT+APPEUI=2C 45 47 E3 24 12 23 24
29.4	506	)))
8.1	507
29.4	508	(((
8.1	509	(Any combination of 16 bit codes can be used）
32.1	510
	511
	512	= 12. I set my device is LoRaWAN Class C mode, why i still see Class A after boot? =
29.4	513	)))
8.1	514
	515
32.1	516	Class C only refers to status after OTAA Join successfully. The OTAA Join Process will use Class A mode.
	517
	518
	519
29.3	520	(% class="wikigeneratedid" %)
	521

Wiki source code of LoRaWAN Communication Debug

Applications

Navigation