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
...	...	@@ -335,9 +335,8 @@
335	335	)))
336	336	)))
337	337
338		-== 4.1  Step1 ==
	336	+== 4.1 Step1 ==
339	339
340		-
341	341	(((
342	342	(((
343	343	Create a device in TTN with the OTAA keys from LSE01.
...	...	@@ -361,15 +361,11 @@
361	361	[[image:image-20220526140044-18.png]]
362	362
363	363
	361	+== 4.2 Step2 ==
364	364
365		-== 4.2  Step2 ==
366		-
367		-
368	368	(((
369	369	(((
370	370	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		-
373	373	)))
374	374	)))
375	375
...	...	@@ -376,45 +376,34 @@
376	376	[[image:image-20220526140132-19.png]]
377	377
378	378
	372	+== 4.3 Step3 ==
379	379
380		-== 4.3  Step3 ==
381		-
382		-
383	383	Add APP EUI in the application:
384	384
385		-
386	386	[[image:image-20220526140205-20.png]]
387	387
388	388
	379	+== 4.4 Step4 ==
389	389
390		-== 4.4  Step4 ==
391		-
392		-
393	393	Add APP KEY and DEV EUI:
394	394
395		-
396	396	[[image:image-20220526140251-21.png]]
397	397
398	398
	386	+= 5. TTN V3 integrated into MQTT server =
399	399
400		-= 5.  TTN V3 integrated into MQTT server =
	388	+== 5.1 Introduction ==
401	401
402		-
403		-== 5.1  Introduction ==
404		-
405		-
406	406	(((
407	407	(((
408	408	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.
409	409
410		-
411	411
412	412	)))
413	413	)))
414	414
415		-== 5.2  Create device steps at MQTT ==
	398	+== 5.2 Create device steps at MQTT ==
416	416
417		-
418	418	(((
419	419	(((
420	420	The user creates a new API KEY after creating a device on TTN V3.
...	...	@@ -430,8 +430,6 @@
430	430	(((
431	431	(((
432	432	Fill in Broker Address and Broker port.
433		-
434		-
435	435	)))
436	436	)))
437	437
...	...	@@ -440,10 +440,8 @@
440	440	Fill in the username and password into MQTT.
441	441
442	442
443		-
444	444	[[image:image-20220526140420-23.png]]
445	445
446		-
447	447	The Application Server publishes uplink traffic on the following topics:
448	448
449	449	(% class="box" %)
...	...	@@ -460,18 +460,13 @@
460	460	)))
461	461
462	462	(((
463		-
464		-
465	465	(((
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		-
	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}.
469	469	)))
470	470	)))
471	471
472	472	[[image:image-20220526140452-24.png]]
473	473
474		-
475	475	(((
476	476	(((
477	477	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.
...	...	@@ -488,11 +488,7 @@
488	488
489	489	(((
490	490	(((
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		-
	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.
496	496	)))
497	497	)))
498	498
...	...	@@ -506,23 +506,17 @@
506	506
507	507	(((
508	508	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		-
511	511	)))
512	512
513	513	(((
514		-(% style="color:red" %)**Note**: **Use this handy tool to convert hexadecimal to base64.**
515		-
516		-
	481	+**Note**: Use this handy tool to convert hexadecimal to base64.
517	517	)))
518	518
519	519	[[image:image-20220526140936-27.png]]
520	520
521	521
	487	+== 5.3 Send Downlink message ==
522	522
523		-== 5.3  Send Downlink message ==
524		-
525		-
526	526	(((
527	527	How to configure downlink in TTN V3?
528	528	)))
...	...	@@ -532,9 +532,7 @@
532	532	)))
533	533
534	534	(((
535		-(% style="color:blue" %)**Downlink command: 01 00 00 5A**
536		-
537		-
	498	+Downlink command:01 00 00 5A
538	538	)))
539	539
540	540	[[image:image-20220526141021-28.png]]
...	...	@@ -542,7 +542,6 @@
542	542	downlink
543	543
544	544
545		-
546	546	After sending, you can view it in live data.
547	547
548	548	[[image:image-20220526141052-29.png]]
...	...	@@ -550,15 +550,12 @@
550	550	downlink
551	551
552	552
553		-
554	554	(((
555	555	When downlink is successfully sent, the downlink information can be received on the serial port.
556	556	)))
557	557
558	558	(((
559		-(% style="color:red" %)**Note**:** If the downlink byte sent is longer, the number of bytes will be displayed.**
560		-
561		-
	518	+**Note**: If the downlink byte sent is longer, the number of bytes will be displayed.
562	562	)))
563	563
564	564	[[image:image-20220526141116-30.png]]
...	...	@@ -574,13 +574,13 @@
574	574
575	575	(((
576	576	(((
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**
	534	+If the equipment uses CLASS A. You can set **AT+RPL=2** or send the downlink command: **2102**
578	578	)))
579	579	)))
580	580
581	581	(((
582	582	(((
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**
	540	+If the equipment uses CLASS C. You can set** AT+RPL=4** or send the downlink command: **2104**
584	584	)))
585	585	)))
586	586
...	...	@@ -587,8 +587,6 @@
587	587	(((
588	588	(((
589	589	When the device successfully receives the downlink, the server will receive a confirmation packet of 00.
590		-
591		-
592	592	)))
593	593	)))
594	594
...	...	@@ -597,10 +597,8 @@
597	597	downlink
598	598
599	599
	555	+= 6. Request Remote Support =
600	600
601		-= 6.  Request Remote Support =
602		-
603		-
604	604	(((
605	605	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.
606	606	\\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:**
...	...	@@ -612,24 +612,19 @@
612	612	* End Node traffic (from server UI) to shows end node activity in server. (Normally possible)
613	613	* 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)
614	614
	568	+**~1. End Device Join Screen shot, we can check:**
615	615
616		-(% style="color:blue" %)**1. End Device Join Screen shot, we can check:**
617		-
618	618	* If the device is sending join request to server?
619	619	* What frequency the device is sending?
620	620
621		-
622	622	[[image:image-20220526141308-33.png]]
623	623
624	624	Console Output from End device to see the transmit frequency
625	625
	577	+User can run **AT+CFG **command to print configuration information.
626	626
627		-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)
628	628
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		-
633	633	[[image:image-20220526141612-36.png]]
634	634
635	635
...	...	@@ -636,17 +636,13 @@
636	636	Console Output from End device to see the transmit frequency
637	637
638	638
	587	+**2. Gateway packet traffic in gateway web or ssh. we can check:**
639	639
640		-(% style="color:blue" %)**2. Gateway packet traffic in gateway web or ssh. we can check:**
641		-
642	642	* (((
643	643	If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency)
644	644	)))
645	645	* (((
646	646	If the gateway gets the Join Accept message from server and transmit it via LoRa?
647		-
648		-
649		-
650	650	)))
651	651
652	652	[[image:image-20220526141739-37.png]]
...	...	@@ -654,9 +654,8 @@
654	654	Console Output from Gateway to see packets between end node and server.
655	655
656	656
	601	+**3. Gateway Traffic Page in LoRaWAN Server**
657	657
658		-(% style="color:blue" %)**3. Gateway Traffic Page in LoRaWAN Server**
659		-
660	660	* (((
661	661	If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings.
662	662	)))
...	...	@@ -665,9 +665,6 @@
665	665	)))
666	666	* (((
667	667	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		-
671	671	)))
672	672
673	673	[[image:image-20220526141823-38.png||height="501" width="1144"]]
...	...	@@ -675,21 +675,18 @@
675	675	The Traffic for the End node in the server, use TTNv3 as example
676	676
677	677
678		-
679	679	[[image:image-20220526141917-39.png]]
680	680
681	681	The Traffic for the End node in the server, use TTNv3 as example
682	682
683	683
	623	+**4. Data Page in LoRaWAN server**
684	684
685		-(% style="color:blue" %)**4. Data Page in LoRaWAN server**
686		-
687	687	(((
688	688	(((
689	689	(((
690	690	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.
691	691
692		-
693	693	[[image:image-20220526141956-40.png]]
694	694	)))
695	695	)))
...	...	@@ -698,7 +698,6 @@
698	698	The data for the end device set in server
699	699
700	700
701		-
702	702	[[image:image-20220526142033-41.png]]
703	703
704	704	Check if OTAA Keys match the keys in device