<
From version < 46.2 >
edited by Xiaoling
on 2022/07/14 16:19
To version < 40.1 >
edited by Kilight Cao
on 2022/06/13 19:11
>
Change comment: Uploaded new attachment "image-20220613191154-3.png", version {1}

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.Kilight
Content
... ... @@ -1,17 +1,15 @@
1 -**~ Table of Contents:**
1 +**~ Contents:**
2 2  
3 3  {{toc/}}
4 4  
5 5  
6 -= 1.  Introduction =
6 += 1. Introduction =
7 7  
8 -
9 9  Dragino LoRa/LoRaWAN gateway support MQTT forwarding. It can forward the sensor data from LoRa network to MQTT server , and vice verse.
10 10  
11 11  
12 -== 1.1  Support Devices ==
11 +== 1.1 Support Devices ==
13 13  
14 -
15 15  This MQTT forward instruction is for below devices:
16 16  
17 17  * Firmware Version > LG02_LG08-5.3.1580178039 [[Firmware Download>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]]
... ... @@ -24,10 +24,8 @@
24 24  
25 25  
26 26  
25 += 2. Firmware Change Log for MQTT feature =
27 27  
28 -= 2.  Firmware Change Log for MQTT feature =
29 -
30 -
31 31  (((
32 32  This instruction is wrote start from LG02_LG08-5.3.1580178039. Below is related change log since this version of firmware.
33 33  )))
... ... @@ -37,17 +37,14 @@
37 37  
38 38  
39 39  
36 += 3. MQTT forward operating principle =
40 40  
41 -= 3.  MQTT forward operating principle =
38 +== 3.1 Network Structure ==
42 42  
43 -
44 -== 3.1  Network Structure ==
45 -
46 -
47 47  Below shows the network structure for MQTT forwarding.
48 48  
49 -* **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.
50 -* **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,
42 +* 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.
43 +* 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,
51 51  
52 52  [[image:image-20220527133547-1.png]]
53 53  
... ... @@ -54,13 +54,12 @@
54 54  General MQTT structure
55 55  
56 56  
57 -== 3.2  How sensor data is forwarded ==
50 +== 3.2 How sensor data is forwarded ==
58 58  
59 -
60 60  In this MQTT forward feature, the key point is how the gateway process the sensor data.
61 61  
62 62  
63 -=== 3.2.1  Upstream ===
55 +=== 3.2.1 Upstream ===
64 64  
65 65  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.
66 66  
... ... @@ -72,12 +72,10 @@
72 72  
73 73  (((
74 74  Upstream path
75 -
76 -
77 77  )))
78 78  
79 79  (((
80 -(% style="color:red" %)**Note: The sensor data can base or LoRa or other method, as long as there are data on the file /var/iot/channels. /span>**
70 +Note: The sensor data can base or LoRa or other method, as long as there are data on the file /var/iot/channels. /span>
81 81  )))
82 82  
83 83  (((
... ... @@ -84,9 +84,8 @@
84 84  
85 85  )))
86 86  
87 -=== 3.2.2  Downstream ===
77 +=== 3.2.2 Downstream ===
88 88  
89 -
90 90  The gateway subscribes to a topic of the remote MQTT broker topic. When there is some one publish a value on this topic. The gateway will get it and broadcast to local LoRa Network.
91 91  
92 92  (((
... ... @@ -98,9 +98,8 @@
98 98  Downstream path
99 99  
100 100  
101 -== 3.3  Macro Definition ==
90 +== 3.3 Macro Definition ==
102 102  
103 -
104 104  The MQTT publish command use Macro settings to generate flexible upstream payload for MQTT publish.
105 105  
106 106  (((
... ... @@ -109,9 +109,8 @@
109 109  
110 110  )))
111 111  
112 -=== 3.3.1  -t topic macro ===
100 +=== 3.3.1 -t topic macro ===
113 113  
114 -
115 115  * CHANNEL: Remote Channel ID
116 116  * CLIENTID: Client ID , Same as -i
117 117  * WRITE_API: Remote Channel Write API
... ... @@ -118,9 +118,10 @@
118 118  * USERNAME: User ID (-u)
119 119  * HOSTNAME: Device Hostname
120 120  
121 -=== 3.3.2  -m message macro ===
122 122  
123 123  
110 +=== 3.3.2 -m message macro ===
111 +
124 124  * HOSTNAME: Device Hostname
125 125  * CHANNEL: Remote Channel ID
126 126  * DATA: Sensor Data without time stamp and rssi
... ... @@ -127,15 +127,16 @@
127 127  * META: Completely sensor data with time stamp and rssi
128 128  * JSON: Convert META to json format.
129 129  
130 -=== 3.3.3  Example for Macro ===
131 131  
132 132  
120 +=== 3.3.3 Example for Macro ===
121 +
133 133  [[image:image-20220527134251-4.png]]
134 134  
135 135  MQTT Publish configure
136 136  
137 137  
138 -**Above screen shots shows below format:**
127 +Above screen shots shows below format:
139 139  
140 140  * -t: CLIENTID/CHANNEL/data
141 141  * -m: DATA
... ... @@ -152,10 +152,8 @@
152 152  )))
153 153  
154 154  
144 +== 3.4 Modify the MQTT to support more options ==
155 155  
156 -== 3.4  Modify the MQTT to support more options ==
157 -
158 -
159 159  The MQTT Client Utility used in Dragino is **mosquitto_pub** and **mosquitto_sub**. User can add more options to the mqtt commands. User can check the valid options by command mosquitto_pub ~-~-help. as below:
160 160  
161 161  (% class="box" %)
... ... @@ -173,9 +173,9 @@
173 173   [-u username [-P password]]
174 174   [~-~-will-topic [~-~-will-payload payload] [~-~-will-qos qos] [~-~-will-retain]]
175 175   [{~-~-cafile file | ~-~-capath dir} [~-~-cert file] [~-~-key file]
176 - [~-~-ciphers ciphers] [~-~-insecure]
177 - [~-~-tls-alpn protocol]
178 - [~-~-tls-engine engine] [~-~-keyform keyform] [~-~-tls-engine-kpass-sha1]]
163 + [~-~-ciphers ciphers] [~-~-insecure]
164 + [~-~-tls-alpn protocol]
165 + [~-~-tls-engine engine] [~-~-keyform keyform] [~-~-tls-engine-kpass-sha1]]
179 179   [~-~-psk hex-key ~-~-psk-identity identity [~-~-ciphers ciphers]]
180 180   [~-~-proxy socks-url]
181 181   [~-~-property command identifier value]
... ... @@ -280,19 +280,15 @@
280 280  )))
281 281  
282 282  
270 += 4. Example to communicate to a simple MQTT server =
283 283  
284 -= 4.  Example to communicate to a simple MQTT server =
272 +== 4.1 Overview ==
285 285  
286 -
287 -== 4.1  Overview ==
288 -
289 -
290 290  This section is an example to show how to set up LG01-N to communicate with a MQTT server. The MQTT server is a simple utility set up in a local PC. Note: User can set up same server via [[this instruction>>url:http://www.steves-internet-guide.com/install-mosquitto-broker/]].
291 291  
292 292  
293 -== 4.2  Simulate via MQTT.fx utility ==
277 +== 4.2 Simulate via MQTT.fx utility ==
294 294  
295 -
296 296  The [[MQTT.fx>>url:http://mqttfx.jensd.de/index.php/download]] is a MQTT client tool. We can use this to simulate a MQTT connection to our MQTT broker first to make sure the MQTT broker works. This will also help us understand how it works.
297 297  
298 298  (((
... ... @@ -318,15 +318,14 @@
318 318  Downstream: Subscribe a topic to get downstream
319 319  
320 320  
304 +== 4.3 Simulate via Dragino Command Line ==
321 321  
322 -== 4.3  Simulate via Dragino Command Line ==
323 -
324 324  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.
325 325  
326 326  In the Dragino Gateway, we use [[mosquitto client>>url:https://mosquitto.org/]] for MQTT connection.
327 327  
328 328  
329 -(% style="color:blue" %)**For Upstream**
311 +(% style="color:#4f81bd" %)**For Upstream**
330 330  
331 331  command is [[mosquitto_pub>>url:https://mosquitto.org/man/mosquitto_pub-1.html]]
332 332  
... ... @@ -339,9 +339,8 @@
339 339  mosquitto_pub
340 340  
341 341  
324 +(% style="color:#4f81bd" %)**For Downstream**
342 342  
343 -(% style="color:blue" %)**For Downstream**
344 -
345 345  Use [[mosquitto_sub>>url:https://mosquitto.org/man/mosquitto_sub-1.html]] to subscribe the change on the topic.
346 346  
347 347  [[image:image-20220527135440-10.png]]
... ... @@ -349,7 +349,7 @@
349 349  mosquitto_sub
350 350  
351 351  
352 -== 4.4  Configure Dragino UI for MQTT connection ==
333 +== 4.4 Configure Dragino UI for MQTT connection ==
353 353  
354 354  This chapter are step by step to show to configure the Dragino Menu for MQTT auto connection.
355 355  
... ... @@ -357,7 +357,7 @@
357 357  Go to (% style="color:#4f81bd" %)**Dragino Menu ~-~-> MQTT Client**
358 358  )))
359 359  
360 -[[image:image-20220714155901-1.png]]
341 +[[image:https://wiki.dragino.com/images/thumb/b/bc/MQTT_Command_8.png/600px-MQTT_Command_8.png||height="249" width="600"]]
361 361  
362 362  go to mqtt configure menu
363 363  
... ... @@ -371,28 +371,24 @@
371 371  forward to MQTT
372 372  
373 373  
355 +=== 4.4.1 Configure the MQTT Client for Upstream ===
374 374  
375 -=== 4.4.1  Configure the MQTT Client for Upstream ===
357 +Below screenshot is same as the publish command:
376 376  
377 -
378 -**Below screenshot is same as the publish command:**
379 -
380 380  (% class="box" %)
381 381  (((
382 -**mosquitto_pub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t CLIENTID/CHANNEL/data -m DATA
361 +mosquitto_pub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t CLIENTID/CHANNEL/data -m DATA
383 383  ~/~/where the CLIENTID, CHANNEL & DATA are macro. represent for
384 384  ~/~/CLIENTID: dragino-1b7060
385 385  ~/~/CHANNEL: Remote ID in Channel settings; here is 78901 or 567456
386 -~/~/DATA: The data stores in /var/iot/channels/**
365 +~/~/DATA: The data stores in /var/iot/channels/
387 387  )))
388 388  
389 -
390 390  [[image:image-20220527135828-12.png]]
391 391  
392 392  MQTT Publish configure
393 393  
394 394  
395 -
396 396  [[image:image-20220527135929-13.png]]
397 397  
398 398  MQTT Channel settings
... ... @@ -421,10 +421,8 @@
421 421  MQTT Publish
422 422  
423 423  
401 +=== 4.4.2 Configure the MQTT Client for Downstream ===
424 424  
425 -=== 4.4.2  Configure the MQTT Client for Downstream ===
426 -
427 -
428 428  Below screen shot equal to this subscribe command:
429 429  
430 430  (% class="box" %)
... ... @@ -453,15 +453,13 @@
453 453  downstream simulation
454 454  
455 455  
456 -== 4.5  Add LoRa support to communicate with remote sensor ==
431 +== 4.5 Add LoRa support to communicate with remote sensor ==
457 457  
458 -
459 459  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.
460 460  
461 461  
462 -=== 4.5.1  Use LoRa Raw protocol for communication ~-~- For LG01/LG02 ===
436 +=== 4.5.1 Use LoRa Raw protocol for communication ~-~- For LG01/LG02 ===
463 463  
464 -
465 465  (((
466 466  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.
467 467  )))
... ... @@ -472,8 +472,6 @@
472 472  
473 473  (((
474 474  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.
475 -
476 -
477 477  )))
478 478  
479 479  (((
... ... @@ -503,10 +503,8 @@
503 503  Downstream Data Flow
504 504  
505 505  
477 +=== 4.5.2 Use LoRaWAN Protocol for communication ~-~- For LG308/LPS8/DLOS8 ===
506 506  
507 -=== 4.5.2  Use LoRaWAN Protocol for communication ~-~- For LG308/LPS8/DLOS8 ===
508 -
509 -
510 510  (((
511 511  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.
512 512  )))
... ... @@ -513,17 +513,15 @@
513 513  
514 514  (((
515 515  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.
516 -
517 -
518 518  (% style="color:#4f81bd" %)**Video Instruction**(%%): (% style="color:blue" %)[[https:~~/~~/youtu.be/qJTY441-t90>>url:https://youtu.be/qJTY441-t90]]
519 519  )))
520 520  
521 521  (((
522 -(% style="color:blued" %)**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.
489 +(% 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.
523 523  )))
524 524  
525 525  (((
526 -(% style="color:blue" %)**Step 2**(%%): Make sure your Radio settings match the End Node settings.
493 +(% style="color:#4f81bd" %)**Step 2**(%%): Make sure your Radio settings match the End Node settings.
527 527  )))
528 528  
529 529  [[image:image-20220527141235-21.png]]
... ... @@ -533,24 +533,27 @@
533 533  
534 534  (((
535 535  (((
536 -(% 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.
503 +(% 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. And we need to config the format to (% style="color:#4f81bd" %)**META**
537 537  )))
538 538  )))
539 539  
540 -[[image:image-20220613191345-4.png]]
507 +[[image:image-20220527141450-22.png]]
541 541  
509 +Publish mush use META as data format for LG308
542 542  
543 543  
544 -(% style="color:blue" %)**Step 4**(%%): Map the Device Address to Remote ID in MQTT server.
512 +(% style="color:#4f81bd" %)**Step 4**(%%): Map the Device Address to Remote ID in MQTT server.
545 545  
546 -[[image:image-20220613190635-2.png]]
514 +[[image:image-20220527141727-23.png]]
547 547  
516 +Map Dev Addr to remote ID
548 548  
549 549  
550 -(% style="color:blue" %)**Step 5: Upstream**(%%): Save the change, we can see the log info via "sytem log", End Node and MQTT Server
519 +(% style="color:#4f81bd" %)**Step 5: Upstream**(%%): Save the change, we can see the log info via "sytem log", End Node and MQTT Server
551 551  
552 552  [[image:image-20220527141843-24.png]]
553 553  
523 +Upstream Process
554 554  
555 555  
556 556  
... ... @@ -566,56 +566,30 @@
566 566  
567 567  
568 568  
569 -(% style="color:blue" %)**Step 6: Set up subscribe**(%%)**:** Subscribe a topci for downstream.
539 +(% style="color:#4f81bd" %)**Step 6: Set up subscribe**(%%)**:** Subscribe a topci for downstream.
570 570  
571 -[[image:image-20220613191426-5.png]]
541 +[[image:image-20220527142115-27.png]]
572 572  
543 +Subscribe to a topic
573 573  
574 574  
575 -(% style="color:blue" %)**Step 7: Downstream**(%%): Save the change, we can see the log info via "sytem log", End Node and MQTT Server.
576 576  
547 +(% style="color:#4f81bd" %)**Step 7: Downstream**(%%): Save the change, we can see the log info via "sytem log", End Node and MQTT Server.
548 +
577 577  [[image:image-20220527142239-28.png]]
578 578  
551 +Downstream Flow
579 579  
580 -
581 -=== 4.5.3 MQTT Downstream format ===
582 -
583 -
584 -mosquitto_pub -h $server_address -p $server_port -t $Client_ID -m "**dev_addr,imme/time,txt/hex,payload**"
585 -
586 -(% class="box infomessage" %)
587 -(((
588 -**mosquitto_pub -h 10.130.2.192 -p 1883 -t dragino-1d25dc/ -m "260211D,time,txt,hello"**
589 -)))
590 -
591 -mosquitto_pub -h $server_address -p $server_port -t $Client_ID -m "**dev_addr,imme/time,txt/hex,payload,txpw,txbw,SF,frequency,rxwindow**"
592 -
593 -(% class="box infomessage" %)
594 -(((
595 -**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"**
596 -)))
597 -
598 -Or use [[MQTT.fx>>https://mqttfx.jensd.de/index.php/download]]
599 -
600 -[[image:image-20220613192816-6.png||height="440" width="1056"]]
601 -
602 -
603 603  (% 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"]]**
604 604  
605 605  
606 -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]]
556 += 5. How to Debug =
607 607  
608 -
609 -
610 -= 5.  How to Debug =
611 -
612 -
613 613  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.
614 614  
615 615  
616 -= 6.  How to ask for Support =
561 += 6. How to ask for Support =
617 617  
618 -
619 619  If a user still not have trouble making it works. please send a mail to support@dragino.com with the below info:
620 620  
621 621  * Detail of your LoRaWAN end node.
image-20220613191345-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -55.4 KB
Content
image-20220613191426-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -55.8 KB
Content
image-20220613192816-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -22.1 KB
Content
image-20220714155901-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -75.2 KB
Content
Copyright ©2010-2022 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0