<
From version < 45.1 >
edited by Xiaoling
on 2022/07/14 15:59
To version < 49.1 >
edited by Kilight Cao
on 2022/07/29 11:38
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.Kilight
Content
... ... @@ -22,8 +22,6 @@
22 22  * LIG16
23 23  * MS14 series if installed with the same firmware. (in this case, the MQTT forward will work , but no LoRa support)
24 24  
25 -
26 -
27 27  = 2.  Firmware Change Log for MQTT feature =
28 28  
29 29  
... ... @@ -34,8 +34,6 @@
34 34  * LG02_LG08-5.3.1580178039
35 35  ** Initiate version
36 36  
37 -
38 -
39 39  = 3.  MQTT forward operating principle =
40 40  
41 41  
... ... @@ -45,7 +45,7 @@
45 45  Below shows the network structure for MQTT forwarding.
46 46  
47 47  * **For Uplink:**  The sensor sends data to LoRa Gateway via LoRa wireless, The gateway will process these data and forward to remote MQTT Broker via Internet.
48 -* **For Downlink:** The gateway subscribe a topic in the MQTT broker, when there is update on the topic, the gateway will know and broadcast the data to Local LoRa network,
44 +* **For Downlink:** The gateway subscribe a topic in the MQTT broker, when there is update on the topic, the gateway will know and broadcast the data to Local LoRa network.
49 49  
50 50  [[image:image-20220527133547-1.png]]
51 51  
... ... @@ -52,6 +52,7 @@
52 52  General MQTT structure
53 53  
54 54  
51 +
55 55  == 3.2  How sensor data is forwarded ==
56 56  
57 57  
... ... @@ -60,10 +60,13 @@
60 60  
61 61  === 3.2.1  Upstream ===
62 62  
60 +
63 63  Assume there are two sensor nodes, their ID are Node1 ID: 6734 , Node2 ID: 7456. In the remote MQTT broker there are two topics: Topic1: /channel/765800, Topic2: /channel/367860. We can set up in the gateway to map Node1 to Topic1 and Node2 to Topic2. So when there is a sensor data from Node1, the gateway will forward the data to Topic1, when there is sensor data from Node2, the gateway will forward to Topic2.
64 64  
65 65  (((
66 66  The data flow works as below diagram.
65 +
66 +
67 67  )))
68 68  
69 69  [[image:image-20220527134000-2.png]]
... ... @@ -96,6 +96,7 @@
96 96  Downstream path
97 97  
98 98  
99 +
99 99  == 3.3  Macro Definition ==
100 100  
101 101  
... ... @@ -104,6 +104,7 @@
104 104  (((
105 105  Currently the (% style="color:#4f81bd" %)**-t (topic)**(%%) and (% style="color:#4f81bd" %)**-m (message)**(%%) support Macros.
106 106  
108 +
107 107  
108 108  )))
109 109  
... ... @@ -116,9 +116,6 @@
116 116  * USERNAME: User ID (-u)
117 117  * HOSTNAME: Device Hostname
118 118  
119 -
120 -
121 -
122 122  === 3.3.2  -m message macro ===
123 123  
124 124  
... ... @@ -128,9 +128,6 @@
128 128  * META: Completely sensor data with time stamp and rssi
129 129  * JSON: Convert META to json format.
130 130  
131 -
132 -
133 -
134 134  === 3.3.3  Example for Macro ===
135 135  
136 136  
... ... @@ -325,6 +325,7 @@
325 325  
326 326  == 4.3  Simulate via Dragino Command Line ==
327 327  
324 +
328 328  For first try of MQTT connection, simulate via command line is recommend, there are many servers / connection type for MQTT. They are using different connection parameters. Simulating the connection via command line will help us rapidly connect to server and debug.
329 329  
330 330  In the Dragino Gateway, we use [[mosquitto client>>url:https://mosquitto.org/]] for MQTT connection.
... ... @@ -353,8 +353,10 @@
353 353  mosquitto_sub
354 354  
355 355  
356 -== 4.4 Configure Dragino UI for MQTT connection ==
357 357  
354 +== 4.4  Configure Dragino UI for MQTT connection ==
355 +
356 +
358 358  This chapter are step by step to show to configure the Dragino Menu for MQTT auto connection.
359 359  
360 360  (((
... ... @@ -361,7 +361,7 @@
361 361  Go to (% style="color:#4f81bd" %)**Dragino Menu ~-~-> MQTT Client**
362 362  )))
363 363  
364 -[[image:https://wiki.dragino.com/images/thumb/b/bc/MQTT_Command_8.png/600px-MQTT_Command_8.png||height="249" width="600"]]
363 +[[image:image-20220714155901-1.png]]
365 365  
366 366  go to mqtt configure menu
367 367  
... ... @@ -375,24 +375,28 @@
375 375  forward to MQTT
376 376  
377 377  
378 -=== 4.4.1 Configure the MQTT Client for Upstream ===
379 379  
380 -Below screenshot is same as the publish command:
378 +=== 4.4.1  Configure the MQTT Client for Upstream ===
381 381  
380 +
381 +**Below screenshot is same as the publish command:**
382 +
382 382  (% class="box" %)
383 383  (((
384 -mosquitto_pub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t CLIENTID/CHANNEL/data -m DATA
385 +**mosquitto_pub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t CLIENTID/CHANNEL/data -m DATA
385 385  ~/~/where the CLIENTID, CHANNEL & DATA are macro. represent for
386 386  ~/~/CLIENTID: dragino-1b7060
387 387  ~/~/CHANNEL: Remote ID in Channel settings; here is 78901 or 567456
388 -~/~/DATA: The data stores in /var/iot/channels/
389 +~/~/DATA: The data stores in /var/iot/channels/**
389 389  )))
390 390  
392 +
391 391  [[image:image-20220527135828-12.png]]
392 392  
393 393  MQTT Publish configure
394 394  
395 395  
398 +
396 396  [[image:image-20220527135929-13.png]]
397 397  
398 398  MQTT Channel settings
... ... @@ -421,8 +421,10 @@
421 421  MQTT Publish
422 422  
423 423  
424 -=== 4.4.2 Configure the MQTT Client for Downstream ===
425 425  
428 +=== 4.4.2  Configure the MQTT Client for Downstream ===
429 +
430 +
426 426  Below screen shot equal to this subscribe command:
427 427  
428 428  (% class="box" %)
... ... @@ -451,13 +451,15 @@
451 451  downstream simulation
452 452  
453 453  
454 -== 4.5 Add LoRa support to communicate with remote sensor ==
459 +== 4.5  Add LoRa support to communicate with remote sensor ==
455 455  
461 +
456 456  In above section, we have configured the UI to support MQTT upstream and downstream. We can simulate via Linux command. In this section, we will guide how to communicate with remote LoRa End Node for upstream and downstream.
457 457  
458 458  
459 -=== 4.5.1 Use LoRa Raw protocol for communication ~-~- For LG01/LG02 ===
465 +=== 4.5.1  Use LoRa Raw protocol for communication ~-~- For LG01/LG02 ===
460 460  
467 +
461 461  (((
462 462  We can use [[LoRa Shield>>url:http://www.dragino.com/products/lora/item/102-lora-shield.html]] to send LoRa Raw data to Gateway and receive data from gateway.
463 463  )))
... ... @@ -468,6 +468,8 @@
468 468  
469 469  (((
470 470  And this link is the required library: [[arduino-LoRa-master>>url:http://www.dragino.com/downloads/index.php?dir=LoraShield/]]. Unzip this library and put in Arduino library location.
478 +
479 +
471 471  )))
472 472  
473 473  (((
... ... @@ -497,8 +497,10 @@
497 497  Downstream Data Flow
498 498  
499 499  
500 -=== 4.5.2 Use LoRaWAN Protocol for communication ~-~- For LG308/LPS8/DLOS8 ===
501 501  
510 +=== 4.5.2  Use LoRaWAN Protocol for communication ~-~- For LG308/LPS8/DLOS8 ===
511 +
512 +
502 502  (((
503 503  Since firmware (% style="color:#4f81bd" %)**LG02_LG08~-~-build-v5.3.1585192026-20200326-1109,**(%%) Dragino LoRaWAN gateways support the communication to LoRaWAN (% style="color:#4f81bd" %)**ABP end node**(%%) locally without the need of LoRaWAN server. This feature allow us to integrate MQTT in the gateway to support LoRaWAN to MQTT forwarding or visa verse.
504 504  )))
... ... @@ -505,15 +505,17 @@
505 505  
506 506  (((
507 507  When use test this feature, please use the version higher then : (% style="color:#4f81bd" %)**LG02_LG08~-~-build-v5.4.1593400722-20200629-1120**(%%), in this version, the upload format is changed and readable, which is easier for integration.
508 -(% style="color:#4f81bd" %)**Video Instruction**(%%): (% style="color:blue" %)[[https:~~/~~/youtu.be/qJTY441-t90>>url:https://youtu.be/qJTY441-t90]]
519 +
520 +
521 +(% style="color:blue" %)**Video Instruction**(%%): (% style="color:blue" %)[[https:~~/~~/youtu.be/qJTY441-t90>>url:https://youtu.be/qJTY441-t90]]
509 509  )))
510 510  
511 511  (((
512 -(% style="color:#4f81bd" %)**Step 1**(%%): Refer [[Communicate with ABP End Node>>Communicate with ABP End Node without LoRaWAN Network Server --- LG308]] to know how to set up LG308 to work with LoRaWAN End node.
525 +(% style="color:blue" %)**Step 1**(%%): Refer [[Communicate with ABP End Node>>Communicate with ABP End Node without LoRaWAN Network Server --- LG308]] to know how to set up LG308 to work with LoRaWAN End node.
513 513  )))
514 514  
515 515  (((
516 -(% style="color:#4f81bd" %)**Step 2**(%%): Make sure your Radio settings match the End Node settings.
529 +(% style="color:blue" %)**Step 2**(%%): Make sure your Radio settings match the End Node settings.
517 517  )))
518 518  
519 519  [[image:image-20220527141235-21.png]]
... ... @@ -523,7 +523,7 @@
523 523  
524 524  (((
525 525  (((
526 -(% style="color:#4f81bd" %)**Step 3**(%%): Set up publish format and MQTT channel. The LG308 will store the Data from End node in (% style="color:#4f81bd" %)**HEX format**(%%) in the file.
539 +(% style="color:blue" %)**Step 3**(%%): Set up publish format and MQTT channel. The LG308 will store the Data from End node in (% style="color:#4f81bd" %)**HEX format**(%%) in the file.
527 527  )))
528 528  )))
529 529  
... ... @@ -531,13 +531,13 @@
531 531  
532 532  
533 533  
534 -(% style="color:#4f81bd" %)**Step 4**(%%): Map the Device Address to Remote ID in MQTT server.
547 +(% style="color:blue" %)**Step 4**(%%): Map the Device Address to Remote ID in MQTT server.
535 535  
536 536  [[image:image-20220613190635-2.png]]
537 537  
538 538  
539 539  
540 -(% style="color:#4f81bd" %)**Step 5: Upstream**(%%): Save the change, we can see the log info via "sytem log", End Node and MQTT Server
553 +(% style="color:blue" %)**Step 5: Upstream**(%%): Save the change, we can see the log info via "sytem log", End Node and MQTT Server
541 541  
542 542  [[image:image-20220527141843-24.png]]
543 543  
... ... @@ -556,19 +556,19 @@
556 556  
557 557  
558 558  
559 -(% style="color:#4f81bd" %)**Step 6: Set up subscribe**(%%)**:** Subscribe a topci for downstream.
572 +(% style="color:blue" %)**Step 6: Set up subscribe**(%%)**:** Subscribe a topci for downstream.
560 560  
561 561  [[image:image-20220613191426-5.png]]
562 562  
563 563  
564 564  
565 -(% style="color:#4f81bd" %)**Step 7: Downstream**(%%): Save the change, we can see the log info via "sytem log", End Node and MQTT Server.
578 +(% style="color:blue" %)**Step 7: Downstream**(%%): Save the change, we can see the log info via "sytem log", End Node and MQTT Server.
566 566  
567 567  [[image:image-20220527142239-28.png]]
568 568  
569 569  
570 570  
571 -=== MQTT Downstream format ===
584 +=== 4.5.3 MQTT Downstream format ===
572 572  
573 573  
574 574  mosquitto_pub -h $server_address -p $server_port -t $Client_ID -m "**dev_addr,imme/time,txt/hex,payload**"
... ... @@ -575,7 +575,7 @@
575 575  
576 576  (% class="box infomessage" %)
577 577  (((
578 -mosquitto_pub -h 10.130.2.192 -p 1883 -t dragino-1d25dc/ -m "260211D,time,txt,hello"
591 +**mosquitto_pub -h 10.130.2.192 -p 1883 -t dragino-1d25dc/ -m "260211D,time,txt,hello"**
579 579  )))
580 580  
581 581  mosquitto_pub -h $server_address -p $server_port -t $Client_ID -m "**dev_addr,imme/time,txt/hex,payload,txpw,txbw,SF,frequency,rxwindow**"
... ... @@ -582,7 +582,7 @@
582 582  
583 583  (% class="box infomessage" %)
584 584  (((
585 -mosquitto_pub -h 10.130.2.192 -p 1883 -t dragino-1d25dc/ -m "260211D,time,txt,hello,20,1,SF12,923300000,2 > /var/iot/push/test"
598 +**mosquitto_pub -h 10.130.2.192 -p 1883 -t dragino-1d25dc/ -m "260211D,time,txt,hello,20,1,SF12,923300000,2"**
586 586  )))
587 587  
588 588  Or use [[MQTT.fx>>https://mqttfx.jensd.de/index.php/download]]
... ... @@ -589,17 +589,23 @@
589 589  
590 590  [[image:image-20220613192816-6.png||height="440" width="1056"]]
591 591  
605 +
592 592  (% style="color:red" %)**Notice: The text use for Downstream must meet the requirement from [[LG308 Downstream Payload>>Communicate with ABP End Node without LoRaWAN Network Server --- LG308||anchor="H2.2Downstream"]]**
593 593  
608 +
594 594  Check out this link for more mosquito-related directives [[https:~~/~~/mosquitto.org/man/mosquitto_pub-1.html>>https://mosquitto.org/man/mosquitto_pub-1.html]]
595 595  
596 -= 5. How to Debug =
597 597  
612 +
613 += 5.  How to Debug =
614 +
615 +
598 598  User can login the gateway's console and run (% style="color:#4f81bd" %)**logread -f**(%%). It will shows the output when there is packet arrive.User can see if it is correct.
599 599  
600 600  
601 -= 6. How to ask for Support =
619 += 6.  How to ask for Support =
602 602  
621 +
603 603  If a user still not have trouble making it works. please send a mail to support@dragino.com with the below info:
604 604  
605 605  * Detail of your LoRaWAN end node.
Copyright ©2010-2022 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0