Wiki source code of LoRaWAN Communication Debug

Last modified by Edwin Chen on 2025/01/29 20:30

version	line-number	content
32.2	1	~ Table of Contents:
1.1	2
	3	{{toc/}}
	4
	5
30.2	6
52.2	7	= 1. Join process page check =
1.1	8
52.2	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)
37.3	14
1.1	15	* Gateway (from gateway UI) traffic to show the packet got from end node and receive from Server. (If possible)
37.3	16
1.1	17	* Gateway traffic (from server UI) to shows the data exchange between gateway and server. (Normaly possible)
37.3	18
1.1	19	* End Node traffic (from server UI) to shows end node activity in server. (Normaly possible)
37.3	20
1.1	21	* 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)
	22
32.14	23	(% style="color:blue" %)1. End Device Join Screen shot, we can check:
	24
1.1	25	* If the device is sending join request to server?
37.3	26
1.1	27	* What frequency the device is sending?
	28
61.1	29	[[image:image-20240129142147-2.png\|\|height="736" width="964"]]
1.1	30
52.1	31	Console Output from End device to see the transmit frequency.
1.1	32
32.16	33
32.14	34	(% style="color:blue" %)2. Gateway packet traffic in gateway web or ssh. we can check:
1.1	35
	36	* If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency)
37.3	37
1.1	38	* If the gateway gets the Join Accept message from server and transmit it via LoRa?
	39
61.1	40	[[image:image-20240129151608-6.jpeg\|\|height="725" width="1256"]]
1.1	41
	42	Console Output from Gateway to see packets between end node and server.
	43
	44
49.1	45	(% style="color:blue" %)3. Gateway Live data in LoRaWAN Server
1.1	46
49.1	47	* Does the gateway real-time data contain information about Join Request? If not, check the internet connection and gateway LoRaWAN server Settings.
37.3	48
49.1	49	* Does the server send back a Join Accept for the Join Request? If not, check that the key from the device matches the key you put into the server, or try to choose a different server route for that end device.
37.3	50
1.1	51	* 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.
	52
61.1	53	[[image:image-20240129150821-5.jpeg\|\|height="522" width="1264"]]
1.1	54
49.1	55	The Traffic for the End node in the server, use TTN as example.
1.1	56
	57
32.14	58	(% style="color:blue" %)4. Data Page in LoRaWAN server
1.1	59
	60	* 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.
	61
61.1	62	[[image:image-20240129142557-3.png\|\|height="488" width="1267"]]
1.1	63
	64	The data for the end device set in server
	65
35.2	66
61.1	67	[[image:image-20240129142631-4.png\|\|height="637" width="1256"]]
1.1	68
49.1	69	Check if OTAA Keys match the keys in device.
1.1	70
	71
2.1	72	= 2. Notice of US915/CN470/AU915 Frequency band =
1.1	73
32.3	74
4.2	75	(((
50.1	76	If user has problem to work with LoRaWAN server in band US915/AU915/CN470, he can check:
4.2	77	)))
1.1	78
4.2	79	* (((
50.1	80	What sub-band the server support?
4.2	81	)))
	82	* (((
50.1	83	What is the sub-band the gateway support?
4.2	84	)))
	85	* (((
50.1	86	What is the sub-band the end node is using?
4.2	87	)))
1.1	88
4.2	89	(((
1.1	90	All of above should match so End Node can properly Join the server and don't have packet lost.
4.2	91	)))
1.1	92
4.2	93	(((
	94
	95	)))
	96
	97	(((
50.1	98	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	99	)))
1.1	100
4.2	101	(((
	102
	103	)))
	104
	105	(((
50.1	106	Here are the frequency tables for these bands as reference:
4.2	107	)))
1.1	108
14.2	109	[[image:image-20220526163801-6.png]]
1.1	110
	111	US915 Channels
	112
35.2	113
18.2	114	[[image:image-20220526163926-7.png]]
1.1	115
	116	AU915 Channels
	117
32.3	118
18.2	119	[[image:image-20220526163941-8.png]]
1.1	120
4.4	121	(((
1.1	122	CN470 Channels
32.3	123
	124
4.4	125	)))
1.1	126
4.3	127	(((
1.1	128	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	129	)))
1.1	130
49.1	131	[[image:image-20240123151225-3.png\|\|height="434" width="902"]]
1.1	132
4.4	133	(((
1.1	134	TTN FREQUENCY PLAN
32.3	135
37.2	136	(% style="display:none" %) (%%)
4.4	137	)))
1.1	138
4.3	139	(((
1.1	140	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	141	)))
1.1	142
37.2	143	(% style="display:none" %) (%%)
1.1	144
49.1	145	= 3. Why I see data lost/ is not periodically uplink？ Even the signal strength is good =
1.1	146
32.3	147
1.1	148	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:
	149
37.2	150	* (% style="color:blue" %)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.
1.1	151
37.2	152	* (% style="color:blue" %)Gateway (%%) ~-~-> Use Sub-band2 (Channel 8,9,10,11,12,13,14,15) for Dragino Gateway. this is the default settings for dragino sensors.
	153
	154	* (% style="color:blue" %)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.
	155
4.3	156	(((
1.1	157	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	158	)))
1.1	159
4.3	160
	161	(((
1.1	162	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	163	)))
1.1	164
	165
2.1	166	= 4. Transmision on ABP Mode =
1.1	167
32.3	168
4.3	169	(((
1.1	170	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	171	)))
1.1	172
4.3	173	(((
1.1	174	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	175	)))
1.1	176
4.3	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.
49.1	179
	180	[[image:image-20240123161737-4.png\|\|height="395" width="763"]]
4.3	181	)))
1.1	182
49.1	183	[[image:image-20240123161853-6.png\|\|height="599" width="771"]]
1.1	184
	185	Disable Frame Counter Check in ABP Mode
	186
	187
2.1	188	= 5. Downstream Debug =
1.1	189
2.1	190	== 5.1 How it work ==
1.1	191
32.3	192
1.1	193	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.
	194
4.3	195	(((
92.1	196	Depends on Class A or Class C, the receive windows will be a little difference. The main difference between Class A and Class C:
	197
	198	* Class A : Suitable for Battery powered end node. Class A will save a lot of power but it can only receive downlink after each uplink
	199	* Class C: End node can receive downlink immediately but have higher power consumption.
	200
	201
	202
4.3	203	)))
1.1	204
31.2	205	[[image:image-20220531161828-1.png]]
1.1	206
	207	receive windows for Class A and Class C
	208
32.3	209
1.1	210	Below are the requirement for the End Device to receive the packets.
	211
	212	* The End Device must open the receive windows: RX1 or RX2
37.2	213
1.1	214	* The LoRaWAN server must send a downstream packet, and the gateway forward this downstream packet for this end node.
37.2	215
1.1	216	* This downstream packet must arrive to the end node while RX1 or RX2 is open.
37.2	217
1.1	218	* This packet must match the frequency of the RX1 or RX2 window.
37.2	219
32.3	220	* 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	221
2.1	222	== 5.2 See Debug Info ==
1.1	223
32.3	224
4.6	225	(((
32.3	226	(% style="color:blue" %)For LoRaWAN Server
4.6	227	)))
1.1	228
4.6	229	(((
1.1	230	We can check if there is downlink message for this end node, use TTN for example:
4.6	231	)))
1.1	232
4.6	233	(((
49.1	234	Configure a downlink to the end device
61.1	235
	236	[[image:image-20240129152412-8.png\|\|height="486" width="1206"]]
4.6	237	)))
1.1	238
	239
4.6	240	(((
1.1	241	Set a downstream in TTN and see it is sent
4.6	242	)))
1.1	243
63.1	244	(% style="color:red" %)Note: After the downlink command is successfully sent from the platform to the node, the downlink command is executed only after the platform receives the next uplink package from the node.
1.1	245
63.1	246
4.3	247	(((
63.1	248	This downlink info will then pass to the gateway downlink list. and the DR which is used (SF7BW500) in US915 is DR5.
4.3	249	)))
1.1	250
61.1	251	[[image:image-20240129152049-7.png\|\|height="463" width="1166"]]
1.1	252
4.6	253	(((
63.1	254	Gateway Traffic can see this downlink info
4.6	255	)))
1.1	256
	257
32.16	258
4.6	259	(((
32.3	260	(% style="color:blue" %)For LoRaWAN Gateway
4.6	261	)))
1.1	262
4.3	263	(((
63.1	264	When the downlink packet appear on the traffic of Gateway page. The LoRaWAN gateway can get it from LoRaWAN server and transmit it. In Dragino Gateway, this can be checked by running "logread -f" in the SSH console. and see below:
4.3	265	)))
1.1	266
63.1	267	[[image:image-20240129154321-9.png]]
1.1	268
4.6	269	(((
1.1	270	Gateway Sent out this packet
4.6	271	)))
1.1	272
	273
32.16	274
4.6	275	(((
32.3	276	(% style="color:blue" %)For End Node
4.6	277	)))
1.1	278
4.8	279	(((
1.1	280	we can use AT Command (AT+CFG) to check the RX1 configure and RX2 configure. as below:
4.8	281	)))
1.1	282
4.9	283	(((
37.3	284	* (% style="color:#037691" %)AT+RX2FQ=869525000 (%%) ~-~--> The RX2 Window frequency
32.4	285
37.3	286	* (% style="color:#037691" %)AT+RX2DR=3 (%%) ~-~--> The RX2 DataRate
32.16	287
37.3	288	* (% style="color:#037691" %)AT+RX1DL=1000 (%%) ~-~--> Receive Delay 1
	289
	290	* (% style="color:#037691" %)AT+RX2DL=2000 (%%) ~-~--> Receive Delay 2
4.9	291	)))
	292
	293	(((
32.3	294	(% style="color:blue" %)when the device running, we can see below info:
4.7	295	)))
1.1	296
4.8	297	{{{ [12502]*** UpLinkCounter= 0 ***
	298	[12503]TX on freq 868500000 Hz at DR 0
	299	[13992]txDone
4.13	300	[15022]RX on freq 868500000 Hz at DR 0 --> RX1 window open at frequency: 868500000, DR0, after 15022-13992= 1030ms of txdone
	301	[15222]rxTimeOut --> no packet arrive in RX1 window. (duration: 200ms)
	302	[15987]RX on freq 869525000 Hz at DR 3 --> RX2 window open at frequency: 869525000, DR3, after 15987-13992= 1995ms of txdone
	303	[16027]rxTimeOut --> no packet arrive in RX2 window. (duration: 40 ms)}}}
1.1	304
4.3	305	(((
4.5	306
32.16	307
	308
4.5	309	)))
	310
4.7	311	(((
32.3	312	(% style="color:blue" %)Another message:
4.7	313	)))
4.5	314
4.8	315	{{{ [12502]*** UpLinkCounter= 0 ***
	316	[12503]TX on freq 868100000 Hz at DR 0
	317	[13992]txDone
	318	[15022]RX on freq 868100000 Hz at DR 0
	319	[15222]rxTimeOut
	320	[15987]RX on freq 869525000 Hz at DR 3
4.13	321	[16185]rxDone --> We have got the downstream packet.
4.8	322	Rssi= -64
	323	Receive data
	324	1:0012345678}}}
4.5	325
22.2	326
32.6	327	== 5.3 If problem doesn't solve ==
1.1	328
32.6	329
23.2	330	(% 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	331
	332	* End node console to show the transmit freuqency and DR.
37.3	333
1.1	334	* Gateway (from gateway UI) traffic to show the packet got from end node and receive from Server.
37.3	335
1.1	336	* Gateway traffic (from server UI) to shows the data exchange between gateway and server.
37.3	337
1.1	338	* End Node traffic (from server UI) to shows end node activity in server.
	339
2.1	340	= 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
1.1	341
32.7	342
4.5	343	(((
63.1	344	In LoRaWAN, the gateway 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	345	)))
1.1	346
4.5	347	(((
	348
	349	)))
	350
	351	(((
1.1	352	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	353	)))
1.1	354
4.7	355	{{{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	356
4.5	357	(((
4.6	358
	359	)))
	360
	361	(((
1.1	362	In this case, please double check the gateway frequency and the server frequency band.
4.5	363	)))
1.1	364
	365
2.1	366	= 7. Decrypt a LoRaWAN Packet =
1.1	367
	368
70.1	369	(% style="color:blue" %)1. LHT65N End device configure:
1.1	370
32.7	371	Change to ABP Mode: AT+NJM=0
37.3	372
70.1	373	Change to fix frequency: AT+CHE=1
37.3	374
32.7	375
70.1	376	AT+CFG(Print configuration):
32.12	377
80.1	378	[[image:image-20240129170603-7.png\|\|height="697" width="545"]][[image:image-20240129163741-3.png\|\|height="694" width="565"]]
1.1	379
29.2	380
32.16	381
70.1	382	Configuration:
1.1	383
70.1	384	[[image:image-20240129164219-4.png\|\|height="612" width="440"]]
1.1	385
29.2	386
1.1	387
70.1	388	(% style="color:blue" %)2. In LPS8-v2, configure to receive above message
1.1	389
70.1	390	[[image:image-20240129164326-5.png\|\|height="506" width="1114"]]
29.2	391
32.16	392
70.1	393	In LPS8-v2 console, we can see the Base64 receive are:
1.1	394
70.1	395	[[image:image-20240129170137-6.png\|\|height="459" width="1116"]]
1.1	396
70.1	397
	398
91.1	399	(% style="color:blue" %)3. Decode the info in CMD(Command prompt window)
70.1	400
91.1	401	LoRa packet Base64 format: QP~/~/~/~/+AFQACZv8Hjmc8gFTAkhMzU+75 (from LPS8-v2)
1.1	402
80.1	403	Then the instructions and format parsed in SecureCRT are: ./node_modules/.bin/lora-packet-decode ~-~-base64 QP~/~/~/~/+AFQACZv8Hjmc8gFTAkhMzU+75
1.1	404
	405
91.1	406	Step1: Open CMD, Enter the gateway IP and port.(ssh root@gateway IP -p 22)
32.9	407
91.1	408	[[image:image-20240129190752-17.png\|\|height="338" width="901"]]
1.1	409
91.1	410	[[image:image-20240129191937-21.png\|\|height="450" width="901"]]
1.1	411
	412
91.1	413	Step2: Enter the command to download the LoRa parsing package.(npm install lora-packet)
80.1	414
91.1	415	[[image:image-20240129192239-22.png\|\|height="416" width="902"]]
80.1	416
91.1	417	[[image:image-20240129192549-23.png\|\|height="459" width="898"]]
80.1	418
	419
91.1	420	Step3: Parse the gateway raw payload.(./node_modules/.bin/lora-packet-decode ~-~-base64 QP~/~/~/~/+AFQACZv8Hjmc8gFTAkhMzU+75)
80.1	421
	422
	423
	424
91.1	425	[[image:image-20240129192908-24.png\|\|height="477" width="907"]]
80.1	426
	427
91.1	428	[[image:image-20240129192954-25.png\|\|height="485" width="916"]]
80.1	429
91.1	430
	431
	432
	433
	434
	435
50.1	436	= 8. Why I see uplink 0x00 periodically on the LHT65 v1.8 firmware =
1.1	437
32.9	438
1.1	439	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.
	440
29.3	441
2.1	442	= 9. Why do I see a "MIC Mismatch" error message from the server? =
1.1	443
32.9	444
4.7	445	(((
32.9	446	1) If the user receives a "MIC Mismatch" message after registering the node on the server.
4.7	447	)))
1.1	448
4.7	449	(((
1.1	450	It is likely that the user filled in the wrong APPKEY when registering the node. Many users fill in "APPSKEY".
4.7	451	)))
1.1	452
4.7	453	* (((
	454	Please note the distinction between "APPKEY" and "APPSKEY".
	455	)))
1.1	456
4.7	457	(((
1.1	458	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	459	)))
1.1	460
4.7	461	(((
1.1	462	The user needs a USB-TTL adapter to connect the serial port to modify the node APPKEY.
4.7	463	)))
1.1	464
4.7	465	* (((
	466	If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
39.1	467	)))
5.1	468
39.1	469	(% class="wikigeneratedid" %)
	470	3）Wrong Regional Parameters version selected
	471	We generally use versions above 1.0.2
32.9	472
39.1	473	(% class="wikigeneratedid" %)
	474	[[image:image-20230322163227-1.png]]
1.1	475
39.1	476	(% class="wikigeneratedid" %)
	477	4）We have had cases where it was automatically fixed the next day despite no manual changes, probably a server side issue
	478
39.2	479
63.1	480	= 10. Why I got the payload only with "0x00" or "AA~=~="? =
1.1	481
32.9	482
41.1	483	(% style="color:blue" %)Why sensor sends 0x00?
35.1	484
41.1	485	For US915, AU915 or AS923 frequencies, the max payload lenght is 11 bytes for DR0. Some times sensor needs to send MAC command to server, because the payload is 11 bytes, The MAC command + Payload will exceed 11 bytes and LoRaWAN server will ignore the uplink. In this case, Sensor will send two uplinks together: one uplink is the payload without MAC command, another uplink is 0x00 payload + MAC Command. For the second uplink, in the server side, it will shows the payload is 0x00. Normally, there are several case this will happen.
1.1	486
41.1	487	Possible Case 1:
1.1	488
41.1	489	Sensor has ADR=1 enable and sensor need to reply server MAC command (ADR request) while sensor has DR=0.
40.1	490
1.1	491
41.1	492	Possible Case 2:
33.1	493
41.1	494	For the sensor which has Datalog Feature enable, the sensor will send TimeRequest MAC Command to sync the time. This Time Request will be sent once Sensor Join Network and Every 10 days. While they send such command with DR=0, sensor will send this command with 0x00 payload.
40.1	495
41.1	496
37.3	497	(% style="color:blue" %)How to solve:
35.1	498
40.1	499	Solution:
35.1	500
41.1	501	~1. Use the decoder to filter out this 0x00 packet. (Recommand)
40.1	502
	503	2. Data rate changed from DR3 to DR5, increasing upload byte length
	504	AT+ADR=0
	505	AT+DR=3
	506
	507	Downlink：
	508
	509	[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/#H7.4DataRate>>http://wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/#H7.4DataRate]]
	510
34.1	511	Some node decoders may not have the filter function, or you need decoders of other servers and formats. Please send an email to [[support@dragino.com>>mailto:support@dragino.com]]
6.1	512
32.9	513
5.1	514	= 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
	515
32.9	516
29.4	517	(((
7.1	518	It is possible the keys is erased during upgrading of firmware. and the console output shows below after AT+CFG
29.4	519	)))
5.1	520
29.4	521	(((
5.1	522	AT+APPKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
29.4	523	)))
5.1	524
29.4	525	(((
5.1	526	AT+NWKSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
29.4	527	)))
5.1	528
29.4	529	(((
5.1	530	AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
29.4	531	)))
5.1	532
29.4	533	(((
5.1	534	AT+APPEUI=00 00 00 00 00 00 00 00
29.4	535	)))
5.1	536
29.4	537	(((
	538
	539	)))
5.1	540
29.4	541	(((
5.1	542	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	543	)))
5.1	544
29.4	545	(((
5.1	546	You can rewrites the keys by running commands in AT Console
32.9	547
	548
29.4	549	)))
5.1	550
29.4	551	(((
	552	For example：
	553	)))
5.1	554
29.4	555	(((
8.1	556	AT+APPKEY=85 41 47 20 45 58 28 14 16 82 A0 F0 80 0D DD EE
29.4	557	)))
5.1	558
29.4	559	(((
8.1	560	AT+NWKSKEY=AA CC B0 20 30 45 37 32 14 1E 14 93 E2 3B 20 11
29.4	561	)))
8.1	562
29.4	563	(((
8.1	564	AT+APPSKEY=11 23 02 20 30 20 30 60 80 20 20 30 30 20 10 10
29.4	565	)))
8.1	566
29.4	567	(((
8.1	568	AT+APPEUI=2C 45 47 E3 24 12 23 24
29.4	569	)))
8.1	570
29.4	571	(((
8.1	572	(Any combination of 16 bit codes can be used）
32.1	573
	574
63.1	575	= 12. I set my device is LoRaWAN Class C mode, why I still see Class A after boot? =
29.4	576	)))
8.1	577
	578
32.1	579	Class C only refers to status after OTAA Join successfully. The OTAA Join Process will use Class A mode.
	580
	581
37.1	582	= 13. Why it takes longer time for OTAA joined in US915/CN470/AU915 band? =
32.1	583
37.1	584
50.1	585	In US915, AU915 or CN470 frequency band, there are 8 sub-bands, totally 72 channels. and LoRaWAN server normally use only one sub-band, for example Sub-band 2 in TTN. The gateway also configured to Sub-band 2 and cover eight channels in this sub-band. If the end node transfer data in Sub-band 2, it will reach to gateway and to the LoRaWAN server. If the end node transfer packets in other sub-bands, for example sub-band 1, the packet won't arrive both gateway or LoRaWAN server.
37.1	586
	587
50.1	588	In Dragino Sensors old version firmware (before early 2022), the sub-band is fixed the sub-band to 2 , but this cause a problem, the end node is hard to use in other subband and need program. So the new logic is as below:
37.1	589
50.1	590	We have improved this, the end node will use frequency 1 from sub-band1, then frequency 1 from sub-band2, then frequency 1 from sub-band3, etc to process the OTAA join, in this case, in this case, the end node can support LoRaWAN servers with different sub-bands. To make sure the end node will only transmit the proper sub-band after OTAA Joined successfully, the end node will:
37.1	591
	592	* (((
50.1	593	Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band.
37.1	594	)))
	595	* (((
50.1	596	Use the Join successful sub-band if the server doesn't include sub-band info in the OTAA Join Accept message (TTN v2 doesn't include).
37.1	597	)))
	598
50.1	599	This change will make the activation time a little longer but make sure the device can be used in any sub-band.
37.1	600
	601
50.1	602	Below is a photo to show why it takes longer time for OTAA Join. We can see in 72 channels mode, why it takes more time to join success. If users want to have faster OTAA Join success, he can change default CHE to the sub-band he uses.
37.1	603
	604
	605	[[image:image-20221215223215-1.png\|\|height="584" width="1280"]]

Wiki source code of LoRaWAN Communication Debug

Applications

Navigation