Summary

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

Details

Page properties

Content

...	...	@@ -84,16 +84,15 @@
84	84	The Dragino gateway has supports the Secondary server settings.
85	85
86	86
87		-
88	88	=== 2.2.2  Below list the support products and Requirements: ===
89	89
90	90
91	91	(((
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]]
	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]]
93	93	)))
94	94
95	95	(((
96		-2.  Firmware version since :  [[lgw~~-~~-build-v5.4.1644658774>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LIG16/Firmware/Release/]]
	95	+2. Firmware version since :[[lgw~~-~~-build-v5.4.1644658774>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LIG16/Firmware/Release/]]
97	97	)))
98	98
99	99
...	...	@@ -110,7 +110,6 @@
110	110
111	111	The users is needing to download and install the helium gateway-rs then click the button of Save&Apply
112	112
113		-
114	114	[[image:image-20220526135049-6.png]]
115	115
116	116	Download and Install gateway-rs
...	...	@@ -122,7 +122,6 @@
122	122
123	123	Back to the page of Semtech UDP check the secondary server settings and click the button of Save&Apply
124	124
125		-
126	126	​​​​[[image:image-20220526135125-7.png]]
127	127
128	128	Configuration of helium
...	...	@@ -336,9 +336,8 @@
336	336	)))
337	337	)))
338	338
339		-== 4.1  Step1 ==
	336	+== 4.1 Step1 ==
340	340
341		-
342	342	(((
343	343	(((
344	344	Create a device in TTN with the OTAA keys from LSE01.
...	...	@@ -362,15 +362,11 @@
362	362	[[image:image-20220526140044-18.png]]
363	363
364	364
	361	+== 4.2 Step2 ==
365	365
366		-== 4.2  Step2 ==
367		-
368		-
369	369	(((
370	370	(((
371	371	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.
372		-
373		-
374	374	)))
375	375	)))
376	376
...	...	@@ -377,45 +377,34 @@
377	377	[[image:image-20220526140132-19.png]]
378	378
379	379
	372	+== 4.3 Step3 ==
380	380
381		-== 4.3  Step3 ==
382		-
383		-
384	384	Add APP EUI in the application:
385	385
386		-
387	387	[[image:image-20220526140205-20.png]]
388	388
389	389
	379	+== 4.4 Step4 ==
390	390
391		-== 4.4  Step4 ==
392		-
393		-
394	394	Add APP KEY and DEV EUI:
395	395
396		-
397	397	[[image:image-20220526140251-21.png]]
398	398
399	399
	386	+= 5. TTN V3 integrated into MQTT server =
400	400
401		-= 5.  TTN V3 integrated into MQTT server =
	388	+== 5.1 Introduction ==
402	402
403		-
404		-== 5.1  Introduction ==
405		-
406		-
407	407	(((
408	408	(((
409	409	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.
410	410
411		-
412	412
413	413	)))
414	414	)))
415	415
416		-== 5.2  Create device steps at MQTT ==
	398	+== 5.2 Create device steps at MQTT ==
417	417
418		-
419	419	(((
420	420	(((
421	421	The user creates a new API KEY after creating a device on TTN V3.
...	...	@@ -431,8 +431,6 @@
431	431	(((
432	432	(((
433	433	Fill in Broker Address and Broker port.
434		-
435		-
436	436	)))
437	437	)))
438	438
...	...	@@ -441,10 +441,8 @@
441	441	Fill in the username and password into MQTT.
442	442
443	443
444		-
445	445	[[image:image-20220526140420-23.png]]
446	446
447		-
448	448	The Application Server publishes uplink traffic on the following topics:
449	449
450	450	(% class="box" %)
...	...	@@ -461,18 +461,13 @@
461	461	)))
462	462
463	463	(((
464		-
465		-
466	466	(((
467		-(% 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}.**
468		-
469		-
	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}.
470	470	)))
471	471	)))
472	472
473	473	[[image:image-20220526140452-24.png]]
474	474
475		-
476	476	(((
477	477	(((
478	478	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.
...	...	@@ -489,11 +489,7 @@
489	489
490	490	(((
491	491	(((
492		-
493		-
494		-(% 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.**
495		-
496		-
	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.
497	497	)))
498	498	)))
499	499
...	...	@@ -507,23 +507,17 @@
507	507
508	508	(((
509	509	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:
510		-
511		-
512	512	)))
513	513
514	514	(((
515		-(% style="color:red" %)**Note**: **Use this handy tool to convert hexadecimal to base64.**
516		-
517		-
	481	+**Note**: Use this handy tool to convert hexadecimal to base64.
518	518	)))
519	519
520	520	[[image:image-20220526140936-27.png]]
521	521
522	522
	487	+== 5.3 Send Downlink message ==
523	523
524		-== 5.3  Send Downlink message ==
525		-
526		-
527	527	(((
528	528	How to configure downlink in TTN V3?
529	529	)))
...	...	@@ -533,9 +533,7 @@
533	533	)))
534	534
535	535	(((
536		-(% style="color:blue" %)**Downlink command: 01 00 00 5A**
537		-
538		-
	498	+Downlink command:01 00 00 5A
539	539	)))
540	540
541	541	[[image:image-20220526141021-28.png]]
...	...	@@ -543,7 +543,6 @@
543	543	downlink
544	544
545	545
546		-
547	547	After sending, you can view it in live data.
548	548
549	549	[[image:image-20220526141052-29.png]]
...	...	@@ -551,15 +551,12 @@
551	551	downlink
552	552
553	553
554		-
555	555	(((
556	556	When downlink is successfully sent, the downlink information can be received on the serial port.
557	557	)))
558	558
559	559	(((
560		-(% style="color:red" %)**Note**:** If the downlink byte sent is longer, the number of bytes will be displayed.**
561		-
562		-
	518	+**Note**: If the downlink byte sent is longer, the number of bytes will be displayed.
563	563	)))
564	564
565	565	[[image:image-20220526141116-30.png]]
...	...	@@ -575,13 +575,13 @@
575	575
576	576	(((
577	577	(((
578		-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**
	534	+If the equipment uses CLASS A. You can set **AT+RPL=2** or send the downlink command: **2102**
579	579	)))
580	580	)))
581	581
582	582	(((
583	583	(((
584		-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**
	540	+If the equipment uses CLASS C. You can set** AT+RPL=4** or send the downlink command: **2104**
585	585	)))
586	586	)))
587	587
...	...	@@ -588,8 +588,6 @@
588	588	(((
589	589	(((
590	590	When the device successfully receives the downlink, the server will receive a confirmation packet of 00.
591		-
592		-
593	593	)))
594	594	)))
595	595
...	...	@@ -598,10 +598,8 @@
598	598	downlink
599	599
600	600
	555	+= 6. Request Remote Support =
601	601
602		-= 6.  Request Remote Support =
603		-
604		-
605	605	(((
606	606	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.
607	607	\\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:**
...	...	@@ -613,24 +613,19 @@
613	613	* End Node traffic (from server UI) to shows end node activity in server. (Normally possible)
614	614	* 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)
615	615
	568	+**~1. End Device Join Screen shot, we can check:**
616	616
617		-(% style="color:blue" %)**1. End Device Join Screen shot, we can check:**
618		-
619	619	* If the device is sending join request to server?
620	620	* What frequency the device is sending?
621	621
622		-
623	623	[[image:image-20220526141308-33.png]]
624	624
625	625	Console Output from End device to see the transmit frequency
626	626
	577	+User can run **AT+CFG **command to print configuration information.
627	627
628		-User can run (% style="color:blue" %)**AT+CFG **(%%)command to print configuration information.
	579	+* Is the device in OTAA mode or ABP mode? **AT+NJM=1** (OTAA mode), **AT+NJM=0** (ABP mode)
629	629
630		-* 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)
631		-
632		-
633		-
634	634	[[image:image-20220526141612-36.png]]
635	635
636	636
...	...	@@ -637,17 +637,13 @@
637	637	Console Output from End device to see the transmit frequency
638	638
639	639
	587	+**2. Gateway packet traffic in gateway web or ssh. we can check:**
640	640
641		-(% style="color:blue" %)**2. Gateway packet traffic in gateway web or ssh. we can check:**
642		-
643	643	* (((
644	644	If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency)
645	645	)))
646	646	* (((
647	647	If the gateway gets the Join Accept message from server and transmit it via LoRa?
648		-
649		-
650		-
651	651	)))
652	652
653	653	[[image:image-20220526141739-37.png]]
...	...	@@ -655,9 +655,8 @@
655	655	Console Output from Gateway to see packets between end node and server.
656	656
657	657
	601	+**3. Gateway Traffic Page in LoRaWAN Server**
658	658
659		-(% style="color:blue" %)**3. Gateway Traffic Page in LoRaWAN Server**
660		-
661	661	* (((
662	662	If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings.
663	663	)))
...	...	@@ -666,9 +666,6 @@
666	666	)))
667	667	* (((
668	668	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.
669		-
670		-
671		-
672	672	)))
673	673
674	674	[[image:image-20220526141823-38.png||height="501" width="1144"]]
...	...	@@ -676,21 +676,18 @@
676	676	The Traffic for the End node in the server, use TTNv3 as example
677	677
678	678
679		-
680	680	[[image:image-20220526141917-39.png]]
681	681
682	682	The Traffic for the End node in the server, use TTNv3 as example
683	683
684	684
	623	+**4. Data Page in LoRaWAN server**
685	685
686		-(% style="color:blue" %)**4. Data Page in LoRaWAN server**
687		-
688	688	(((
689	689	(((
690	690	(((
691	691	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.
692	692
693		-
694	694	[[image:image-20220526141956-40.png]]
695	695	)))
696	696	)))
...	...	@@ -699,7 +699,6 @@
699	699	The data for the end device set in server
700	700
701	701
702		-
703	703	[[image:image-20220526142033-41.png]]
704	704
705	705	Check if OTAA Keys match the keys in device