Wiki source code of LoRaWAN Communication Debug

Version 37.1 by Edwin Chen on 2022/12/15 22:33

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
35.2	19
32.14	20	(% style="color:blue" %)1. End Device Join Screen shot, we can check:
	21
1.1	22	* If the device is sending join request to server?
	23	* What frequency the device is sending?
	24
23.2	25	[[image:image-20220526164956-15.png]]
1.1	26
	27	Console Output from End device to see the transmit frequency
	28
	29
32.16	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
35.2	41
32.14	42	(% style="color:blue" %)3. Gateway Traffic Page in LoRaWAN Server
1.1	43
	44	* If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings.
	45	* 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.
	46	* 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.
	47
13.2	48	[[image:image-20220526163633-3.png]]
1.1	49
	50	The Traffic for the End node in the server, use TTN as example
	51
	52
35.2	53
32.14	54	(% style="color:blue" %)4. Data Page in LoRaWAN server
1.1	55
	56	* 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.
	57
13.2	58	[[image:image-20220526163704-4.png]]
1.1	59
	60	The data for the end device set in server
	61
35.2	62
13.2	63	[[image:image-20220526163732-5.png]]
1.1	64
	65	Check if OTAA Keys match the keys in device
	66
	67
32.16	68
2.1	69	= 2. Notice of US915/CN470/AU915 Frequency band =
1.1	70
32.3	71
4.2	72	(((
1.1	73	If user has problem to work with lorawan server in band US915/AU915/CN470, he can check:
4.2	74	)))
1.1	75
4.2	76	* (((
	77	What sub-band the server support ?
	78	)))
	79	* (((
	80	What is the sub-band the gateway support ?
	81	)))
	82	* (((
	83	What is the sub-band the end node is using ?
	84	)))
1.1	85
4.2	86	(((
1.1	87	All of above should match so End Node can properly Join the server and don't have packet lost.
4.2	88	)))
1.1	89
4.2	90	(((
	91
	92	)))
	93
	94	(((
1.1	95	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	96	)))
1.1	97
4.2	98	(((
	99
	100	)))
	101
	102	(((
1.1	103	Here are the freuqency tables for these bands as reference:
4.2	104	)))
1.1	105
14.2	106	[[image:image-20220526163801-6.png]]
1.1	107
	108	US915 Channels
	109
35.2	110
18.2	111	[[image:image-20220526163926-7.png]]
1.1	112
	113	AU915 Channels
	114
32.3	115
18.2	116	[[image:image-20220526163941-8.png]]
1.1	117
4.4	118	(((
1.1	119	CN470 Channels
32.3	120
	121
4.4	122	)))
1.1	123
4.3	124	(((
1.1	125	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	126	)))
1.1	127
18.2	128	[[image:image-20220526164052-9.png]]
1.1	129
4.4	130	(((
1.1	131	TTN FREQUENCY PLAN
32.3	132
	133
4.4	134	)))
1.1	135
4.3	136	(((
1.1	137	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	138	)))
1.1	139
	140
32.16	141
2.1	142	= 3. Why i see data lost/unperiocially uplink data? Even the signal strength is good =
1.1	143
32.3	144
1.1	145	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:
	146
2.1	147	* 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.
	148	* Gateway ~-~-> Use Sub-band2 (Channel 8,9,10,11,12,13,14,15) for Dragino Gateway. this is the default settings for dragino sensors.
	149	* 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	150
4.3	151	(((
1.1	152	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	153	)))
1.1	154
4.3	155	(((
	156
	157	)))
	158
	159	(((
1.1	160	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	161	)))
1.1	162
	163
32.16	164
2.1	165	= 4. Transmision on ABP Mode =
1.1	166
32.3	167
4.3	168	(((
1.1	169	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	170	)))
1.1	171
4.3	172	(((
	173
	174	)))
	175
	176	(((
1.1	177	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	178	)))
1.1	179
4.3	180	(((
	181
	182	)))
	183
	184	(((
1.1	185	To solve this, disable the Frame Counter Check will solve this issue , or reset the frame counter in the device page.
4.3	186	)))
1.1	187
18.2	188	[[image:image-20220526164508-10.png]]
1.1	189
	190	Disable Frame Counter Check in ABP Mode
	191
	192
32.16	193
2.1	194	= 5. Downstream Debug =
1.1	195
2.1	196	== 5.1 How it work ==
1.1	197
32.3	198
1.1	199	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.
	200
4.3	201	(((
1.1	202	Depends on Class A or Class C, the receive windows will be a little difference,
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
	213	* The LoRaWAN server must send a downstream packet, and the gateway forward this downstream packet for this end node.
	214	* This downstream packet must arrive to the end node while RX1 or RX2 is open.
	215	* This packet must match the frequency of the RX1 or RX2 window.
32.3	216	* 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	217
35.2	218
2.1	219	== 5.2 See Debug Info ==
1.1	220
32.3	221
4.6	222	(((
32.3	223	(% style="color:blue" %)For LoRaWAN Server
4.6	224	)))
1.1	225
4.6	226	(((
1.1	227	We can check if there is downlink message for this end node, use TTN for example:
4.6	228	)))
1.1	229
4.6	230	(((
1.1	231	Configure a downstream to the end device
4.6	232	)))
1.1	233
22.2	234	[[image:image-20220526164623-12.png]]
1.1	235
4.6	236	(((
1.1	237	Set a downstream in TTN and see it is sent
4.6	238	)))
1.1	239
	240
4.3	241	(((
1.1	242	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	243	)))
1.1	244
22.2	245	[[image:image-20220526164650-13.png]]
1.1	246
4.6	247	(((
1.1	248	Gateway Traffic can see this downstream info
4.6	249	)))
1.1	250
	251
32.16	252
4.6	253	(((
32.3	254	(% style="color:blue" %)For LoRaWAN Gateway
4.6	255	)))
1.1	256
4.3	257	(((
1.1	258	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	259	)))
1.1	260
22.2	261	[[image:image-20220526164734-14.png]]
1.1	262
4.6	263	(((
1.1	264	Gateway Sent out this packet
4.6	265	)))
1.1	266
	267
32.16	268
4.6	269	(((
32.3	270	(% style="color:blue" %)For End Node
4.6	271	)))
1.1	272
4.8	273	(((
1.1	274	we can use AT Command (AT+CFG) to check the RX1 configure and RX2 configure. as below:
4.8	275	)))
1.1	276
4.9	277	(((
32.4	278	(% style="color:#037691" %)AT+RX2FQ=869525000 (%%) ~-~--> The RX2 Window frequency
	279	(% style="color:#037691" %)AT+RX2DR=3 (%%) ~-~--> The RX2 DataRate
	280	(% style="color:#037691" %)AT+RX1DL=1000 (%%) ~-~--> Receive Delay 1
	281	(% style="color:#037691" %)AT+RX2DL=2000 (%%) ~-~--> Receive Delay 2
	282
32.16	283
4.9	284
	285	)))
	286
	287	(((
32.3	288	(% style="color:blue" %)when the device running, we can see below info:
4.7	289	)))
1.1	290
4.8	291	{{{ [12502]*** UpLinkCounter= 0 ***
	292	[12503]TX on freq 868500000 Hz at DR 0
	293	[13992]txDone
4.13	294	[15022]RX on freq 868500000 Hz at DR 0 --> RX1 window open at frequency: 868500000, DR0, after 15022-13992= 1030ms of txdone
	295	[15222]rxTimeOut --> no packet arrive in RX1 window. (duration: 200ms)
	296	[15987]RX on freq 869525000 Hz at DR 3 --> RX2 window open at frequency: 869525000, DR3, after 15987-13992= 1995ms of txdone
	297	[16027]rxTimeOut --> no packet arrive in RX2 window. (duration: 40 ms)}}}
1.1	298
4.3	299	(((
4.5	300
32.16	301
	302
4.5	303	)))
	304
4.7	305	(((
32.3	306	(% style="color:blue" %)Another message:
4.7	307	)))
4.5	308
4.8	309	{{{ [12502]*** UpLinkCounter= 0 ***
	310	[12503]TX on freq 868100000 Hz at DR 0
	311	[13992]txDone
	312	[15022]RX on freq 868100000 Hz at DR 0
	313	[15222]rxTimeOut
	314	[15987]RX on freq 869525000 Hz at DR 3
4.13	315	[16185]rxDone --> We have got the downstream packet.
4.8	316	Rssi= -64
	317	Receive data
	318	1:0012345678}}}
4.5	319
22.2	320
32.16	321
32.6	322	== 5.3 If problem doesn't solve ==
1.1	323
32.6	324
23.2	325	(% 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	326
	327	* End node console to show the transmit freuqency and DR.
	328	* Gateway (from gateway UI) traffic to show the packet got from end node and receive from Server.
	329	* Gateway traffic (from server UI) to shows the data exchange between gateway and server.
	330	* End Node traffic (from server UI) to shows end node activity in server.
	331
35.2	332
2.1	333	= 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
1.1	334
32.7	335
4.5	336	(((
1.1	337	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	338	)))
1.1	339
4.5	340	(((
	341
	342	)))
	343
	344	(((
1.1	345	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	346	)))
1.1	347
4.7	348	{{{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	349
4.5	350	(((
4.6	351
	352	)))
	353
	354	(((
1.1	355	In this case, please double check the gateway frequency and the server frequency band.
4.5	356	)))
1.1	357
	358
32.16	359
2.1	360	= 7. Decrypt a LoRaWAN Packet =
1.1	361
	362
32.7	363	(% style="color:blue" %)1. LHT65 End device configure:
1.1	364
32.7	365	Change to ABP Mode: AT+NJM=0
	366	Change to fix frequency: AT+CHS=904900000
	367	Change to fix DR: AT+DR=0
	368
32.12	369
29.2	370	[[image:image-20220526165525-16.png]]
1.1	371
29.2	372
32.16	373
32.7	374	(% style="color:blue" %)2. In LG02 , configure to receive above message
1.1	375
29.2	376	[[image:image-20220526165612-17.png]]
1.1	377
29.2	378
1.1	379	In LG02 console, we can see the hex receive are:
	380
29.2	381	[[image:image-20220526171112-21.png]]
1.1	382
29.2	383
32.16	384
32.7	385	(% style="color:blue" %)3. Decode the info in web
1.1	386
	387	[[https:~~/~~/lorawan-packet-decoder-0ta6puiniaut.runkit.sh>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/]]
	388
	389	Need these three fields:
	390
	391	LoRa packet hex format: 40c1190126800100024926272bf18bbb6341584e27e23245 (from LG02)
	392
	393	AT+NWKSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 11 (End node Network Session Key)
	394
	395	AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 11 (End Node App Session Key)
	396
32.9	397
1.1	398	[[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]]
	399
29.2	400	[[image:image-20220526171029-20.png]]
1.1	401
4.10	402	(((
4.11	403	The FRMPayload is the device payload.
4.10	404	)))
1.1	405
	406
32.16	407
2.1	408	= 8. Why i see uplink 0x00 periodcally on the LHT65 v1.8 firmware =
1.1	409
32.9	410
1.1	411	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.
	412
29.3	413
32.16	414
2.1	415	= 9. Why do I see a "MIC Mismatch" error message from the server? =
1.1	416
32.9	417
4.7	418	(((
32.9	419	1) If the user receives a "MIC Mismatch" message after registering the node on the server.
4.7	420	)))
1.1	421
4.7	422	(((
1.1	423	It is likely that the user filled in the wrong APPKEY when registering the node. Many users fill in "APPSKEY".
4.7	424	)))
1.1	425
4.7	426	* (((
	427	Please note the distinction between "APPKEY" and "APPSKEY".
	428	)))
1.1	429
4.7	430	(((
1.1	431	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	432	)))
1.1	433
4.7	434	(((
1.1	435	The user needs a USB-TTL adapter to connect the serial port to modify the node APPKEY.
4.7	436	)))
1.1	437
4.7	438	* (((
	439	If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
5.1	440
32.9	441
	442
5.1	443
4.7	444	)))
1.1	445
2.1	446	= 10. Why i got the payload only with "0x00" or "AA~=~="? =
1.1	447
32.9	448
35.1	449	Why this happen:
	450
34.1	451	For US915, AU915 or AS923 frequencies.It is possible because: .
1.1	452
33.1	453	When using the frequency mentioned above, the server sometimes adjusts the Data Rate (DR) of the node, because the end node has Adaptive Data Rate (ADR) Enabled.
1.1	454
34.1	455	When the server adjusts end node data rate to 0, the maximum payload length is 11 bytes. The server sometimes sends an ADR packet to the end 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 following an additional 00 data packet to handle this MAC command response.
1.1	456
33.1	457
35.1	458	How to solve:
	459
	460	Solution: Use the decoder to filter out this 0x00 packet.
	461
34.1	462	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	463
32.9	464
	465
5.1	466	= 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
	467
32.9	468
29.4	469	(((
7.1	470	It is possible the keys is erased during upgrading of firmware. and the console output shows below after AT+CFG
29.4	471	)))
5.1	472
29.4	473	(((
5.1	474	AT+APPKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
29.4	475	)))
5.1	476
29.4	477	(((
5.1	478	AT+NWKSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
29.4	479	)))
5.1	480
29.4	481	(((
5.1	482	AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
29.4	483	)))
5.1	484
29.4	485	(((
5.1	486	AT+APPEUI=00 00 00 00 00 00 00 00
29.4	487	)))
5.1	488
29.4	489	(((
	490
	491	)))
5.1	492
29.4	493	(((
5.1	494	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	495	)))
5.1	496
29.4	497	(((
5.1	498	You can rewrites the keys by running commands in AT Console
32.9	499
	500
29.4	501	)))
5.1	502
29.4	503	(((
	504	For example：
	505	)))
5.1	506
29.4	507	(((
8.1	508	AT+APPKEY=85 41 47 20 45 58 28 14 16 82 A0 F0 80 0D DD EE
29.4	509	)))
5.1	510
29.4	511	(((
8.1	512	AT+NWKSKEY=AA CC B0 20 30 45 37 32 14 1E 14 93 E2 3B 20 11
29.4	513	)))
8.1	514
29.4	515	(((
8.1	516	AT+APPSKEY=11 23 02 20 30 20 30 60 80 20 20 30 30 20 10 10
29.4	517	)))
8.1	518
29.4	519	(((
8.1	520	AT+APPEUI=2C 45 47 E3 24 12 23 24
29.4	521	)))
8.1	522
29.4	523	(((
8.1	524	(Any combination of 16 bit codes can be used）
32.1	525
	526
32.16	527
32.1	528	= 12. I set my device is LoRaWAN Class C mode, why i still see Class A after boot? =
29.4	529	)))
8.1	530
	531
32.1	532	Class C only refers to status after OTAA Join successfully. The OTAA Join Process will use Class A mode.
	533
	534
37.1	535	= 13. Why it takes longer time for OTAA joined in US915/CN470/AU915 band? =
32.1	536
37.1	537
	538	In US915, AU915 or CN470 frequency band, there are 8 subbands, totally 72 channels. and LoRaWAN server normally use only one sub-band, for example Subband 2 in TTN. The gateway also configured to Subband 2 and cover eight channels in this subband. If the end node transfer data in Subband 2, it will reach to gateway and to the LoRaWAN server. If the end node transfer packets in other subbands, for example subband 1, the packet won't arrive both gateway or LoRaWAN server.
	539
	540
	541	In Dragino Sensors old version firmware (before early 2022), the subband is fixed the subband 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:
	542
	543	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 subbands. To make sure the end node will only transmit the proper sub-band after OTAA Joined successfully, the end node will:
	544
	545	* (((
	546	Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that subband
	547	)))
	548	* (((
	549	Use the Join successful sub-band if the server doesn't include subband info in the OTAA Join Accept message ( TTN v2 doesn't include)
	550	)))
	551
	552	This change will make the activation time a littler longer but make sure the device can be used in any subband.
	553
	554
	555	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 subband he use.
	556
	557
	558	[[image:image-20221215223215-1.png\|\|height="584" width="1280"]]
	559
29.3	560	(% class="wikigeneratedid" %)
	561

Wiki source code of LoRaWAN Communication Debug

Applications

Navigation