Changes for page MQTT Forward Instruction
Last modified by Kilight Cao on 2024/08/31 16:26
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 1 removed)
Details
- Page properties
-
- Content
-
... ... @@ -45,15 +45,13 @@ 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 .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, 49 49 50 - 51 51 [[image:image-20220527133547-1.png]] 52 52 53 53 General MQTT structure 54 54 55 55 56 - 57 57 == 3.2 How sensor data is forwarded == 58 58 59 59 ... ... @@ -62,13 +62,10 @@ 62 62 63 63 === 3.2.1 Upstream === 64 64 65 - 66 66 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. 67 67 68 68 ((( 69 69 The data flow works as below diagram. 70 - 71 - 72 72 ))) 73 73 74 74 [[image:image-20220527134000-2.png]] ... ... @@ -101,7 +101,6 @@ 101 101 Downstream path 102 102 103 103 104 - 105 105 == 3.3 Macro Definition == 106 106 107 107 ... ... @@ -110,7 +110,6 @@ 110 110 ((( 111 111 Currently the (% style="color:#4f81bd" %)**-t (topic)**(%%) and (% style="color:#4f81bd" %)**-m (message)**(%%) support Macros. 112 112 113 - 114 114 115 115 ))) 116 116 ... ... @@ -125,6 +125,7 @@ 125 125 126 126 127 127 121 + 128 128 === 3.3.2 -m message macro === 129 129 130 130 ... ... @@ -136,6 +136,7 @@ 136 136 137 137 138 138 133 + 139 139 === 3.3.3 Example for Macro === 140 140 141 141 ... ... @@ -330,7 +330,6 @@ 330 330 331 331 == 4.3 Simulate via Dragino Command Line == 332 332 333 - 334 334 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. 335 335 336 336 In the Dragino Gateway, we use [[mosquitto client>>url:https://mosquitto.org/]] for MQTT connection. ... ... @@ -359,10 +359,8 @@ 359 359 mosquitto_sub 360 360 361 361 356 +== 4.4 Configure Dragino UI for MQTT connection == 362 362 363 -== 4.4 Configure Dragino UI for MQTT connection == 364 - 365 - 366 366 This chapter are step by step to show to configure the Dragino Menu for MQTT auto connection. 367 367 368 368 ((( ... ... @@ -369,7 +369,7 @@ 369 369 Go to (% style="color:#4f81bd" %)**Dragino Menu ~-~-> MQTT Client** 370 370 ))) 371 371 372 -[[image:image -20220714155901-1.png]]364 +[[image:https://wiki.dragino.com/images/thumb/b/bc/MQTT_Command_8.png/600px-MQTT_Command_8.png||height="249" width="600"]] 373 373 374 374 go to mqtt configure menu 375 375 ... ... @@ -383,28 +383,24 @@ 383 383 forward to MQTT 384 384 385 385 378 +=== 4.4.1 Configure the MQTT Client for Upstream === 386 386 387 - === 4.4.1 Configure theMQTT Clientfor Upstream===380 +Below screenshot is same as the publish command: 388 388 389 - 390 -**Below screenshot is same as the publish command:** 391 - 392 392 (% class="box" %) 393 393 ((( 394 - **mosquitto_pub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t CLIENTID/CHANNEL/data -m DATA384 +mosquitto_pub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t CLIENTID/CHANNEL/data -m DATA 395 395 ~/~/where the CLIENTID, CHANNEL & DATA are macro. represent for 396 396 ~/~/CLIENTID: dragino-1b7060 397 397 ~/~/CHANNEL: Remote ID in Channel settings; here is 78901 or 567456 398 -~/~/DATA: The data stores in /var/iot/channels/ **388 +~/~/DATA: The data stores in /var/iot/channels/ 399 399 ))) 400 400 401 - 402 402 [[image:image-20220527135828-12.png]] 403 403 404 404 MQTT Publish configure 405 405 406 406 407 - 408 408 [[image:image-20220527135929-13.png]] 409 409 410 410 MQTT Channel settings ... ... @@ -433,10 +433,8 @@ 433 433 MQTT Publish 434 434 435 435 424 +=== 4.4.2 Configure the MQTT Client for Downstream === 436 436 437 -=== 4.4.2 Configure the MQTT Client for Downstream === 438 - 439 - 440 440 Below screen shot equal to this subscribe command: 441 441 442 442 (% class="box" %) ... ... @@ -465,15 +465,13 @@ 465 465 downstream simulation 466 466 467 467 468 -== 4.5 454 +== 4.5 Add LoRa support to communicate with remote sensor == 469 469 470 - 471 471 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. 472 472 473 473 474 -=== 4.5.1 459 +=== 4.5.1 Use LoRa Raw protocol for communication ~-~- For LG01/LG02 === 475 475 476 - 477 477 ((( 478 478 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. 479 479 ))) ... ... @@ -484,8 +484,6 @@ 484 484 485 485 ((( 486 486 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. 487 - 488 - 489 489 ))) 490 490 491 491 ((( ... ... @@ -515,10 +515,8 @@ 515 515 Downstream Data Flow 516 516 517 517 500 +=== 4.5.2 Use LoRaWAN Protocol for communication ~-~- For LG308/LPS8/DLOS8 === 518 518 519 -=== 4.5.2 Use LoRaWAN Protocol for communication ~-~- For LG308/LPS8/DLOS8 === 520 - 521 - 522 522 ((( 523 523 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. 524 524 ))) ... ... @@ -525,17 +525,15 @@ 525 525 526 526 ((( 527 527 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. 528 - 529 - 530 -(% style="color:blue" %)**Video Instruction**(%%): (% style="color:blue" %)[[https:~~/~~/youtu.be/qJTY441-t90>>url:https://youtu.be/qJTY441-t90]] 508 +(% style="color:#4f81bd" %)**Video Instruction**(%%): (% style="color:blue" %)[[https:~~/~~/youtu.be/qJTY441-t90>>url:https://youtu.be/qJTY441-t90]] 531 531 ))) 532 532 533 533 ((( 534 -(% style="color:b lue" %)**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.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. 535 535 ))) 536 536 537 537 ((( 538 -(% style="color:b lue" %)**Step 2**(%%): Make sure your Radio settings match the End Node settings.516 +(% style="color:#4f81bd" %)**Step 2**(%%): Make sure your Radio settings match the End Node settings. 539 539 ))) 540 540 541 541 [[image:image-20220527141235-21.png]] ... ... @@ -545,7 +545,7 @@ 545 545 546 546 ((( 547 547 ((( 548 -(% style="color:b lue" %)**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.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. 549 549 ))) 550 550 ))) 551 551 ... ... @@ -553,13 +553,13 @@ 553 553 554 554 555 555 556 -(% style="color:b lue" %)**Step 4**(%%): Map the Device Address to Remote ID in MQTT server.534 +(% style="color:#4f81bd" %)**Step 4**(%%): Map the Device Address to Remote ID in MQTT server. 557 557 558 558 [[image:image-20220613190635-2.png]] 559 559 560 560 561 561 562 -(% style="color:b lue" %)**Step 5: Upstream**(%%): Save the change, we can see the log info via "sytem log", End Node and MQTT Server540 +(% style="color:#4f81bd" %)**Step 5: Upstream**(%%): Save the change, we can see the log info via "sytem log", End Node and MQTT Server 563 563 564 564 [[image:image-20220527141843-24.png]] 565 565 ... ... @@ -578,19 +578,19 @@ 578 578 579 579 580 580 581 -(% style="color:b lue" %)**Step 6: Set up subscribe**(%%)**:** Subscribe a topci for downstream.559 +(% style="color:#4f81bd" %)**Step 6: Set up subscribe**(%%)**:** Subscribe a topci for downstream. 582 582 583 583 [[image:image-20220613191426-5.png]] 584 584 585 585 586 586 587 -(% style="color:b lue" %)**Step 7: Downstream**(%%): Save the change, we can see the log info via "sytem log", End Node and MQTT Server.565 +(% style="color:#4f81bd" %)**Step 7: Downstream**(%%): Save the change, we can see the log info via "sytem log", End Node and MQTT Server. 588 588 589 589 [[image:image-20220527142239-28.png]] 590 590 591 591 592 592 593 -=== 4.5.3MQTT Downstream format ===571 +=== MQTT Downstream format === 594 594 595 595 596 596 mosquitto_pub -h $server_address -p $server_port -t $Client_ID -m "**dev_addr,imme/time,txt/hex,payload**" ... ... @@ -597,7 +597,7 @@ 597 597 598 598 (% class="box infomessage" %) 599 599 ((( 600 - **mosquitto_pub -h 10.130.2.192 -p 1883 -t dragino-1d25dc/ -m "260211D,time,txt,hello"**578 +mosquitto_pub -h 10.130.2.192 -p 1883 -t dragino-1d25dc/ -m "260211D,time,txt,hello" 601 601 ))) 602 602 603 603 mosquitto_pub -h $server_address -p $server_port -t $Client_ID -m "**dev_addr,imme/time,txt/hex,payload,txpw,txbw,SF,frequency,rxwindow**" ... ... @@ -604,7 +604,7 @@ 604 604 605 605 (% class="box infomessage" %) 606 606 ((( 607 - **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"**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" 608 608 ))) 609 609 610 610 Or use [[MQTT.fx>>https://mqttfx.jensd.de/index.php/download]] ... ... @@ -611,23 +611,17 @@ 611 611 612 612 [[image:image-20220613192816-6.png||height="440" width="1056"]] 613 613 614 - 615 615 (% 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"]]** 616 616 617 - 618 618 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]] 619 619 596 += 5. How to Debug = 620 620 621 - 622 -= 5. How to Debug = 623 - 624 - 625 625 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. 626 626 627 627 628 -= 6. 601 += 6. How to ask for Support = 629 629 630 - 631 631 If a user still not have trouble making it works. please send a mail to support@dragino.com with the below info: 632 632 633 633 * Detail of your LoRaWAN end node.
- image-20220714155901-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -75.2 KB - Content