Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -84,15 +84,16 @@
84	84	The Dragino gateway has supports the Secondary server settings.
85	85
86	86
	87	+
87	87	=== 2.2.2  Below list the support products and Requirements: ===
88	88
89	89
90	90	(((
91		-~1. LoRaWAN Gateway model: [[LIG16>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/171-lig16.html]], [[LG308>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/140-lg308.html]], [[DLOS8>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/160-dlos8.html]] [[LPS8>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/148-lps8.html]]
	92	+1.  LoRaWAN Gateway model:  [[LIG16>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/171-lig16.html]], [[LG308>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/140-lg308.html]], [[DLOS8>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/160-dlos8.html]] [[LPS8>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/148-lps8.html]]
92	92	)))
93	93
94	94	(((
95		-2. Firmware version since :[[lgw~~-~~-build-v5.4.1644658774>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LIG16/Firmware/Release/]]
	96	+2.  Firmware version since :  [[lgw~~-~~-build-v5.4.1644658774>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LIG16/Firmware/Release/]]
96	96	)))
97	97
98	98
...	...	@@ -109,6 +109,7 @@
109	109
110	110	The users is needing to download and install the helium gateway-rs then click the button of Save&Apply
111	111
	113	+
112	112	[[image:image-20220526135049-6.png]]
113	113
114	114	Download and Install gateway-rs
...	...	@@ -333,8 +333,9 @@
333	333	)))
334	334	)))
335	335
336		-== 4.1 Step1 ==
	338	+== 4.1  Step1 ==
337	337
	340	+
338	338	(((
339	339	(((
340	340	Create a device in TTN with the OTAA keys from LSE01.
...	...	@@ -358,11 +358,15 @@
358	358	[[image:image-20220526140044-18.png]]
359	359
360	360
361		-== 4.2 Step2 ==
362	362
	365	+== 4.2  Step2 ==
	366	+
	367	+
363	363	(((
364	364	(((
365	365	There are all our nodes in the repository. Users can choose the corresponding brand, model, firmware version and frequency.The decoder and configuration information of the node are pre-configured.Users do not need to configure them.
	371	+
	372	+
366	366	)))
367	367	)))
368	368
...	...	@@ -369,34 +369,45 @@
369	369	[[image:image-20220526140132-19.png]]
370	370
371	371
372		-== 4.3 Step3 ==
373	373
	380	+== 4.3  Step3 ==
	381	+
	382	+
374	374	Add APP EUI in the application:
375	375
	385	+
376	376	[[image:image-20220526140205-20.png]]
377	377
378	378
379		-== 4.4 Step4 ==
380	380
	390	+== 4.4  Step4 ==
	391	+
	392	+
381	381	Add APP KEY and DEV EUI:
382	382
	395	+
383	383	[[image:image-20220526140251-21.png]]
384	384
385	385
386		-= 5. TTN V3 integrated into MQTT server =
387	387
388		-== 5.1 Introduction ==
	400	+= 5.  TTN V3 integrated into MQTT server =
389	389
	402	+
	403	+== 5.1  Introduction ==
	404	+
	405	+
390	390	(((
391	391	(((
392	392	The Application Server exposes an MQTT server to work with streaming events. In order to use the MQTT server you need to create a new API key, which will function as connection password. You can also use an existing API key, as long as it has the necessary rights granted.
393	393
	410	+
394	394
395	395	)))
396	396	)))
397	397
398		-== 5.2 Create device steps at MQTT ==
	415	+== 5.2  Create device steps at MQTT ==
399	399
	417	+
400	400	(((
401	401	(((
402	402	The user creates a new API KEY after creating a device on TTN V3.
...	...	@@ -412,6 +412,8 @@
412	412	(((
413	413	(((
414	414	Fill in Broker Address and Broker port.
	433	+
	434	+
415	415	)))
416	416	)))
417	417
...	...	@@ -420,8 +420,10 @@
420	420	Fill in the username and password into MQTT.
421	421
422	422
	443	+
423	423	[[image:image-20220526140420-23.png]]
424	424
	446	+
425	425	The Application Server publishes uplink traffic on the following topics:
426	426
427	427	(% class="box" %)
...	...	@@ -438,13 +438,18 @@
438	438	)))
439	439
440	440	(((
	463	+
	464	+
441	441	(((
442		-**Note**: Remember that the format of these topics for The Things Stack Open Source would contain {application id} instead of {application id}@{tenant id}.
	466	+(% style="color:red" %)**Note**: **Remember that the format of these topics for The Things Stack Open Source would contain {application id} instead of {application id}@{tenant id}.**
	467	+
	468	+
443	443	)))
444	444	)))
445	445
446	446	[[image:image-20220526140452-24.png]]
447	447
	474	+
448	448	(((
449	449	(((
450	450	While you could subscribe to all of these topics separately, for the simplicity of this tutorial we use # to subscribe to all topics, i.e. to receive all uplink traffic.
...	...	@@ -461,7 +461,11 @@
461	461
462	462	(((
463	463	(((
464		-**Note**: Remember that the format of this topic for The Things Stack Open Source deployment would be v3/{application id}/devices/{device id}/down/push.
	491	+
	492	+
	493	+(% style="color:red" %)**Note**: **Remember that the format of this topic for The Things Stack Open Source deployment would be v3/{application id}/devices/{device id}/down/push.**
	494	+
	495	+
465	465	)))
466	466	)))
467	467
...	...	@@ -475,17 +475,23 @@
475	475
476	476	(((
477	477	To send an unconfirmed downlink message to the device dev1 in application app1 in tenant tenant1 with the hexadecimal payload BE EF on FPort 15 with normal priority, use the topic v3/app1@tenant1/devices/dev1/down/push with the following contents:
	509	+
	510	+
478	478	)))
479	479
480	480	(((
481		-**Note**: Use this handy tool to convert hexadecimal to base64.
	514	+(% style="color:red" %)**Note**: **Use this handy tool to convert hexadecimal to base64.**
	515	+
	516	+
482	482	)))
483	483
484	484	[[image:image-20220526140936-27.png]]
485	485
486	486
487		-== 5.3 Send Downlink message ==
488	488
	523	+== 5.3  Send Downlink message ==
	524	+
	525	+
489	489	(((
490	490	How to configure downlink in TTN V3?
491	491	)))
...	...	@@ -495,7 +495,9 @@
495	495	)))
496	496
497	497	(((
498		-Downlink command:01 00 00 5A
	535	+(% style="color:blue" %)**Downlink command: 01 00 00 5A**
	536	+
	537	+
499	499	)))
500	500
501	501	[[image:image-20220526141021-28.png]]
...	...	@@ -503,6 +503,7 @@
503	503	downlink
504	504
505	505
	545	+
506	506	After sending, you can view it in live data.
507	507
508	508	[[image:image-20220526141052-29.png]]
...	...	@@ -510,12 +510,15 @@
510	510	downlink
511	511
512	512
	553	+
513	513	(((
514	514	When downlink is successfully sent, the downlink information can be received on the serial port.
515	515	)))
516	516
517	517	(((
518		-**Note**: If the downlink byte sent is longer, the number of bytes will be displayed.
	559	+(% style="color:red" %)**Note**:** If the downlink byte sent is longer, the number of bytes will be displayed.**
	560	+
	561	+
519	519	)))
520	520
521	521	[[image:image-20220526141116-30.png]]
...	...	@@ -531,13 +531,13 @@
531	531
532	532	(((
533	533	(((
534		-If the equipment uses CLASS A. You can set **AT+RPL=2** or send the downlink command: **2102**
	577	+If the equipment uses (% style="color:blue" %)**CLASS A**(%%). You can set (% style="color:red" %)**AT+RPL=2** (%%)or send the downlink command: (% style="color:red" %)**2102**
535	535	)))
536	536	)))
537	537
538	538	(((
539	539	(((
540		-If the equipment uses CLASS C. You can set** AT+RPL=4** or send the downlink command: **2104**
	583	+If the equipment uses (% style="color:blue" %)**CLASS C**(%%). You can set** (% style="color:red" %)AT+RPL=4(%%)** or send the downlink command: (% style="color:red" %)**2104**
541	541	)))
542	542	)))
543	543
...	...	@@ -544,6 +544,8 @@
544	544	(((
545	545	(((
546	546	When the device successfully receives the downlink, the server will receive a confirmation packet of 00.
	590	+
	591	+
547	547	)))
548	548	)))
549	549
...	...	@@ -552,8 +552,10 @@
552	552	downlink
553	553
554	554
555		-= 6. Request Remote Support =
556	556
	601	+= 6.  Request Remote Support =
	602	+
	603	+
557	557	(((
558	558	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.
559	559	\\If problem not solve, and you need dragino remote support, please follow to this document: [[TTN Support instruction>>url:https://www.dragino.com/downloads/index.php?dir=&file=TTNv3_Support_Guide.pdf]](% style="color:red" %) **If user has checked below steps and still can't solve the problem, please send us (support @ dragino.com) the screenshots for each step to check. They include:**
...	...	@@ -565,19 +565,24 @@
565	565	* End Node traffic (from server UI) to shows end node activity in server. (Normally possible)
566	566	* 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)
567	567
568		-**~1. End Device Join Screen shot, we can check:**
569	569
	616	+(% style="color:blue" %)**1. End Device Join Screen shot, we can check:**
	617	+
570	570	* If the device is sending join request to server?
571	571	* What frequency the device is sending?
572	572
	621	+
573	573	[[image:image-20220526141308-33.png]]
574	574
575	575	Console Output from End device to see the transmit frequency
576	576
577		-User can run **AT+CFG **command to print configuration information.
578	578
579		-* Is the device in OTAA mode or ABP mode? **AT+NJM=1** (OTAA mode), **AT+NJM=0** (ABP mode)
	627	+User can run (% style="color:blue" %)**AT+CFG **(%%)command to print configuration information.
580	580
	629	+* Is the device in OTAA mode or ABP mode? (% style="color:red" %)**AT+NJM=1** (%%)(OTAA mode), (% style="color:red" %)**AT+NJM=0**(%%) (ABP mode)
	630	+
	631	+
	632	+
581	581	[[image:image-20220526141612-36.png]]
582	582
583	583
...	...	@@ -584,13 +584,17 @@
584	584	Console Output from End device to see the transmit frequency
585	585
586	586
587		-**2. Gateway packet traffic in gateway web or ssh. we can check:**
588	588
	640	+(% style="color:blue" %)**2. Gateway packet traffic in gateway web or ssh. we can check:**
	641	+
589	589	* (((
590	590	If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency)
591	591	)))
592	592	* (((
593	593	If the gateway gets the Join Accept message from server and transmit it via LoRa?
	647	+
	648	+
	649	+
594	594	)))
595	595
596	596	[[image:image-20220526141739-37.png]]
...	...	@@ -598,8 +598,9 @@
598	598	Console Output from Gateway to see packets between end node and server.
599	599
600	600
601		-**3. Gateway Traffic Page in LoRaWAN Server**
602	602
	658	+(% style="color:blue" %)**3. Gateway Traffic Page in LoRaWAN Server**
	659	+
603	603	* (((
604	604	If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings.
605	605	)))
...	...	@@ -608,6 +608,9 @@
608	608	)))
609	609	* (((
610	610	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.
	668	+
	669	+
	670	+
611	611	)))
612	612
613	613	[[image:image-20220526141823-38.png||height="501" width="1144"]]
...	...	@@ -615,18 +615,21 @@
615	615	The Traffic for the End node in the server, use TTNv3 as example
616	616
617	617
	678	+
618	618	[[image:image-20220526141917-39.png]]
619	619
620	620	The Traffic for the End node in the server, use TTNv3 as example
621	621
622	622
623		-**4. Data Page in LoRaWAN server**
624	624
	685	+(% style="color:blue" %)**4. Data Page in LoRaWAN server**
	686	+
625	625	(((
626	626	(((
627	627	(((
628	628	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.
629	629
	692	+
630	630	[[image:image-20220526141956-40.png]]
631	631	)))
632	632	)))
...	...	@@ -635,6 +635,7 @@
635	635	The data for the end device set in server
636	636
637	637
	701	+
638	638	[[image:image-20220526142033-41.png]]
639	639
640	640	Check if OTAA Keys match the keys in device