Changes for page MQTT Forward Instruction
Last modified by Kilight Cao on 2024/08/31 16:26
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 1 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Xiaoling1 +XWiki.Kilight - Content
-
... ... @@ -14,269 +14,30 @@ 14 14 15 15 This MQTT forward instruction is for below devices: 16 16 17 -* Firmware Version > LG02_LG08-5.3.1580178039 [[Firmware Download>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]] 18 -* LG01N, OLG01N ((% style="color:red" %)**Warning**(%%): LG01-P LG01-S use another instruction: [[MQTT for LG01-P/LG01S>>doc:Through MQTT to upload data.WebHome]]) 17 +* LG01N, OLG01N ((% style="color:red" %)**Warning**(%%): LG01-P LG01-S use another instruction: [[MQTT for LG01-P/LG01S>>doc:Main.Through MQTT to upload data.WebHome]]) 19 19 * LG02, OLG02 20 -* LG308, DLOS8 21 -* LPS8 22 -* LIG16 19 +* LG308, DLOS8, LPS8, LIG16 23 23 * MS14 series if installed with the same firmware. (in this case, the MQTT forward will work , but no LoRa support) 21 +* LG308N, DLOS8N, LPS8N 22 +* LPS8V2 24 24 25 25 25 +The MQTT Client Utility used in Dragino is **mosquitto_pub** and **mosquitto_sub**. User can add more options to the mqtt commands. 26 26 27 +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]]** 27 27 28 -= 2. Firmware Change Log for MQTT feature = 29 29 30 += 2. Example to communicate to a simple MQTT server = 30 30 31 -((( 32 -This instruction is wrote start from LG02_LG08-5.3.1580178039. Below is related change log since this version of firmware. 33 -))) 32 +== 2.1 Overview == 34 34 35 -* LG02_LG08-5.3.1580178039 36 -** Initiate version 37 37 38 - 39 - 40 - 41 -= 3. MQTT forward operating principle = 42 - 43 -== 3.1 Network Structure == 44 - 45 -Below shows the network structure for MQTT forwarding. 46 - 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, 49 - 50 -[[image:image-20220527133547-1.png]] 51 - 52 -General MQTT structure 53 - 54 - 55 -== 3.2 How sensor data is forwarded == 56 - 57 -In this MQTT forward feature, the key point is how the gateway process the sensor data. 58 - 59 - 60 -=== 3.2.1 Upstream === 61 - 62 -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. 63 - 64 -((( 65 -The data flow works as below diagram. 66 -))) 67 - 68 -[[image:image-20220527134000-2.png]] 69 - 70 -((( 71 -Upstream path 72 -))) 73 - 74 -((( 75 -Note: The sensor data can base or LoRa or other method, as long as there are data on the file /var/iot/channels. /span> 76 -))) 77 - 78 -((( 79 - 80 -))) 81 - 82 -=== 3.2.2 Downstream === 83 - 84 -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. 85 - 86 -((( 87 -Below are the data flow for downstream. 88 -))) 89 - 90 -[[image:image-20220527134038-3.png]] 91 - 92 -Downstream path 93 - 94 - 95 -== 3.3 Macro Definition == 96 - 97 -The MQTT publish command use Macro settings to generate flexible upstream payload for MQTT publish. 98 - 99 -((( 100 -Currently the (% style="color:#4f81bd" %)**-t (topic)**(%%) and (% style="color:#4f81bd" %)**-m (message)**(%%) support Macros. 101 - 102 - 103 -))) 104 - 105 -=== 3.3.1 -t topic macro === 106 - 107 -* CHANNEL: Remote Channel ID 108 -* CLIENTID: Client ID , Same as -i 109 -* WRITE_API: Remote Channel Write API 110 -* USERNAME: User ID (-u) 111 -* HOSTNAME: Device Hostname 112 - 113 -=== 3.3.2 -m message macro === 114 - 115 -* HOSTNAME: Device Hostname 116 -* CHANNEL: Remote Channel ID 117 -* DATA: Sensor Data without time stamp and rssi 118 -* META: Completely sensor data with time stamp and rssi 119 -* JSON: Convert META to json format. 120 - 121 -=== 3.3.3 Example for Macro === 122 - 123 -[[image:image-20220527134251-4.png]] 124 - 125 -MQTT Publish configure 126 - 127 - 128 -Above screen shots shows below format: 129 - 130 -* -t: CLIENTID/CHANNEL/data 131 -* -m: DATA 132 - 133 -When there is a LoRa sensor arrive. it will be store at the /var/iot/channels as below: 134 - 135 -[[image:image-20220527134332-5.png]] 136 - 137 -Sensor Data 138 - 139 - 140 -((( 141 -According to above macro. Gateway will publish (% style="color:#4f81bd" %)**field1=22.0&field2=49.0**(%%) to topic: (% style="color:#4f81bd" %)**dragino-1b7060/78901/data**(%%), where 78901 is the remote channel for this node ID. 142 -))) 143 - 144 - 145 -== 3.4 Modify the MQTT to support more options == 146 - 147 -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: 148 - 149 -(% class="box" %) 150 -((( 151 -root@dragino-1ec39c:~~# mosquitto_pub ~-~-help 152 -mosquitto_pub is a simple mqtt client that will publish a message on a single topic and exit. 153 -mosquitto_pub version 1.6.4 running on libmosquitto 1.6.4. 154 -\\Usage: mosquitto_pub {[-h host] [-p port] [-u username] [-P password] -t topic | -L URL} 155 - {-f file | -l | -n | -m message} 156 - [-c] [-k keepalive] [-q qos] [-r] [~-~-repeat N] [~-~-repeat-delay time] 157 - [-A bind_address] 158 - [-i id] [-I id_prefix] 159 - [-d] [~-~-quiet] 160 - [-M max_inflight] 161 - [-u username [-P password]] 162 - [~-~-will-topic [~-~-will-payload payload] [~-~-will-qos qos] [~-~-will-retain]] 163 - [{~-~-cafile file | ~-~-capath dir} [~-~-cert file] [~-~-key file] 164 - [~-~-ciphers ciphers] [~-~-insecure] 165 - [~-~-tls-alpn protocol] 166 - [~-~-tls-engine engine] [~-~-keyform keyform] [~-~-tls-engine-kpass-sha1]] 167 - [~-~-psk hex-key ~-~-psk-identity identity [~-~-ciphers ciphers]] 168 - [~-~-proxy socks-url] 169 - [~-~-property command identifier value] 170 - [-D command identifier value] 171 - mosquitto_pub ~-~-help 172 -\\-A : bind the outgoing socket to this host/ip address. Use to control which interface 173 - the client communicates over. 174 --d : enable debug messages. 175 --D : Define MQTT v5 properties. See the documentation for more details. 176 --f : send the contents of a file as the message. 177 --h : mqtt host to connect to. Defaults to localhost. 178 --i : id to use for this client. Defaults to mosquitto_pub_ appended with the process id. 179 --I : define the client id as id_prefix appended with the process id. Useful for when the 180 - broker is using the clientid_prefixes option. 181 --k : keep alive in seconds for this client. Defaults to 60. 182 --L : specify user, password, hostname, port and topic as a URL in the form: 183 - mqtt(s):~/~/[username[:password]@]host[:port]/topic 184 --l : read messages from stdin, sending a separate message for each line. 185 --m : message payload to send. 186 --M : the maximum inflight messages for QoS 1/2.. 187 --n : send a null (zero length) message. 188 --p : network port to connect to. Defaults to 1883 for plain MQTT and 8883 for MQTT over TLS. 189 --P : provide a password 190 --q : quality of service level to use for all messages. Defaults to 0. 191 --r : message should be retained. 192 --s : read message from stdin, sending the entire input as a message. 193 --t : mqtt topic to publish to. 194 --u : provide a username 195 --V : specify the version of the MQTT protocol to use when connecting. 196 - Can be mqttv5, mqttv311 or mqttv31. Defaults to mqttv311. 197 -~-~-help : display this message. 198 -~-~-repeat : if publish mode is -f, -m, or -s, then repeat the publish N times. 199 -~-~-repeat-delay : if using ~-~-repeat, wait time seconds between publishes. Defaults to 0. 200 -~-~-quiet : (% style="color:red" %)don't print error messages. 201 -~-~-will-payload : payload for the client Will, which is sent by the broker in case of 202 - unexpected disconnection. If not given and will-topic is set, a zero 203 - length message will be sent. 204 -~-~-will-qos : QoS level for the client Will. 205 -~-~-will-retain : if given, make the client Will retained. 206 -~-~-will-topic : the topic on which to publish the client Will. 207 -~-~-cafile : path to a file containing trusted CA certificates to enable encrypted 208 - communication. 209 -~-~-capath : path to a directory containing trusted CA certificates to enable encrypted 210 - communication. 211 -~-~-cert : client certificate for authentication, if required by server. 212 -~-~-key : client private key for authentication, if required by server. 213 -~-~-keyform : keyfile type, can be either "pem" or "engine". 214 -~-~-ciphers : openssl compatible list of TLS ciphers to support. 215 -~-~-tls-version : TLS protocol version, can be one of tlsv1.3 tlsv1.2 or tlsv1.1. 216 - Defaults to tlsv1.2 if available. 217 -~-~-insecure : do not check that the server certificate hostname matches the remote 218 - hostname. Using this option means that you cannot be sure that the 219 - remote host is the server you wish to connect to and so is insecure. 220 - Do not use this option in a production environment. 221 -~-~-tls-engine : If set, enables the use of a TLS engine device. 222 -~-~-tls-engine-kpass-sha1 : SHA1 of the key password to be used with the selected SSL engine. 223 -~-~-psk : pre-shared-key in hexadecimal (no leading 0x) to enable TLS-PSK mode. 224 -~-~-psk-identity : client identity string for TLS-PSK mode. 225 -~-~-proxy : SOCKS5 proxy URL of the form: 226 - socks5h:~/~/[username[:password]@]hostname[:port] 227 - Only "none" and "username" authentication is supported. 228 -\\See https:~/~/mosquitto.org/ for more information. 229 -))) 230 - 231 - 232 -((( 233 -and modify the /usr/bin/mqtt_process.sh script, the location to change the command option is below lines: 234 -))) 235 - 236 -(% class="box" %) 237 -((( 238 -//# Call MQTT Publish command 239 -\\# 1. Case with User, Password and Client ID present (e.g. Azure) 240 -if [ ! -z "$pass" ] && [ ! -z "$user" ] && [ ! -z "$clientID" ]; then 241 -case="1" 242 -mosquitto_pub $D -h $server -p $port -q $pub_qos -i $clientID -t $pub_topic -u $user -P "$pass" $C $cafile $PUB_FLAG "$mqtt_data" 243 -\\# 2. Case with Certificate, Key and ClientID present (e.g. AWS) 244 -elif [ ! -z "$certfile" ] && [ ! -z "$key" ] && [ ! -z "$clientID" ]; then 245 -case="2" 246 -mosquitto_pub $D -h $server -p $port -q $pub_qos -i $clientID -t $pub_topic ~-~-cert $cert ~-~-key $key $C $cafile $PUB_FLAG "$mqtt_data" 247 -\\# 3. Case with no User, Certificate or ClientID present 248 -elif [ -z "$user" ] && [ -z "$certfile" ] && [ -z "$clientID" ]; then 249 -case="3" 250 -mosquitto_pub $D -h $server -p $port -q $pub_qos -t $pub_topic $PUB_FLAG "$mqtt_data" 251 -\\# 4. Case with no User, Certificate, but with ClientID present 252 -elif [ -z "$user" ] && [ -z "$certfile" ] && [ ! -z "$clientID" ]; then 253 -case="4" 254 -mosquitto_pub $D -h $server -p $port -q $pub_qos -i $clientID -t $pub_topic $PUB_FLAG "$mqtt_data" 255 -\\# 5. Case with User and ClientID present, but no Password and no Certificate present 256 -elif [ -z "$pass" ] && [ -z "$certfile" ] && [ ! -z "$user" ] && [ ! -z "$clientID" ]; then 257 -case="5" 258 -mosquitto_pub $D -h $server -p $port -q $pub_qos -i $clientID -t $pub_topic -u $user $PUB_FLAG "$mqtt_data" 259 -\\# 6. Case with User and Password present, but no ClientID and no Certificate present 260 -elif [ ! -z "$user" ] && [ ! -z "$pass" ] && [ -z "$clientID" ] && [ -z "$certfile" ]; then 261 -case="6" 262 -mosquitto_pub $D -h $server -p $port -q $pub_qos -t $pub_topic -u $user -P "$pass" $PUB_FLAG "$mqtt_data" 263 -\\# 0. Else - invalid parameters, just log 264 -else 265 -case="(% style="color:red" %)Invalid parameters" (%%) 266 -logger (% style="color:red" %)"[IoT.MQTT]:Invalid Parameters - mosquitto_pub not called."(%%) 267 -fi// 268 -))) 269 - 270 - 271 -= 4. Example to communicate to a simple MQTT server = 272 - 273 -== 4.1 Overview == 274 - 275 275 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/]]. 276 276 277 277 278 -== 4.2 Simulate via MQTT.fx utility ==38 +== 2.2 Simulate via MQTT.fx utility == 279 279 40 + 280 280 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. 281 281 282 282 ((( ... ... @@ -302,153 +302,32 @@ 302 302 Downstream: Subscribe a topic to get downstream 303 303 304 304 305 -== 4.3 Simulate via Dragino Command Line == 306 306 307 - Forfirsttry of MQTT connection, simulate via commandline is recommend,therearemanyservers / connection type forMQTT. They are using differentconnectionparameters. Simulating the connection viacommand line willhelpusrapidly connecttoserverand debug.67 += 3. Add LoRa support to communicate with remote sensor = 308 308 309 -In the Dragino Gateway, we use [[mosquitto client>>url:https://mosquitto.org/]] for MQTT connection. 310 310 70 +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. 311 311 312 -(% style="color:#4f81bd" %)**For Upstream** 313 313 314 -command is [[mosquitto_pub>>url:https://mosquitto.org/man/mosquitto_pub-1.html]] 315 315 316 - Example:mosquitto_pub-h 192.168.199.148-p1883-t/channel/6543-m temp=3674 +== 3.1 Use LoRa Raw protocol for communication ~-~- For LG01/LG02 == 317 317 318 -Note: 192.168.199.148 is MQTT broker address, the gateway and the MQTT broker PC are in the same network. 319 319 320 -[[image:image-20220527135310-9.png]] 321 - 322 -mosquitto_pub 323 - 324 - 325 -(% style="color:#4f81bd" %)**For Downstream** 326 - 327 -Use [[mosquitto_sub>>url:https://mosquitto.org/man/mosquitto_sub-1.html]] to subscribe the change on the topic. 328 - 329 -[[image:image-20220527135440-10.png]] 330 - 331 -mosquitto_sub 332 - 333 - 334 -== 4.4 Configure Dragino UI for MQTT connection == 335 - 336 -This chapter are step by step to show to configure the Dragino Menu for MQTT auto connection. 337 - 338 338 ((( 339 - Goto (%style="color:#4f81bd" %)**DraginoMenu~-~->MQTTClient**78 +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. 340 340 ))) 341 341 342 -[[image:https://wiki.dragino.com/images/thumb/b/bc/MQTT_Command_8.png/600px-MQTT_Command_8.png||height="249" width="600"]] 343 - 344 -go to mqtt configure menu 345 - 346 - 347 347 ((( 348 - Select (%style="color:#4f81bd"%)**ForwardtoMQTTserver**. (% style="color:red" %)**Notice**(%%): Thisoption isremoved from thelatestfirmware,inthelatest firmware,if usersubmit "SAVE & APPLY" in MQTT page, the gateway will useMQTT service.82 +The example Sketch for LoRa Shield +Arduino is here: **[[LoRa_Shield_Sketch_For_MQTT>>url:http://www.dragino.com/downloads/index.php?dir=LoraShield/]]** 349 349 ))) 350 350 351 -[[image:image-20220527135742-11.png]] 352 - 353 -forward to MQTT 354 - 355 - 356 -=== 4.4.1 Configure the MQTT Client for Upstream === 357 - 358 -Below screenshot is same as the publish command: 359 - 360 -(% class="box" %) 361 361 ((( 362 -mosquitto_pub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t CLIENTID/CHANNEL/data -m DATA 363 -~/~/where the CLIENTID, CHANNEL & DATA are macro. represent for 364 -~/~/CLIENTID: dragino-1b7060 365 -~/~/CHANNEL: Remote ID in Channel settings; here is 78901 or 567456 366 -~/~/DATA: The data stores in /var/iot/channels/ 367 -))) 86 +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. 368 368 369 -[[image:image-20220527135828-12.png]] 370 - 371 -MQTT Publish configure 372 - 373 - 374 -[[image:image-20220527135929-13.png]] 375 - 376 -MQTT Channel settings 377 - 378 - 379 -((( 380 -For example, if we put a data(temp=46) on the file /var/iot/channels/4567, because 4567 match the remote channel 78901. the gateway will run this command: 88 + 381 381 ))) 382 382 383 -(% class="box" %) 384 384 ((( 385 -mosquitto_pub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t dragino-1b7060/78901/data -m temp=46 386 -))) 387 - 388 -((( 389 -to MQTT broker. 390 -))) 391 - 392 - 393 -((( 394 -Below is a simulation to put this data to active the MQTT publish. 395 -))) 396 - 397 -[[image:image-20220527140023-14.png]] 398 - 399 -MQTT Publish 400 - 401 - 402 -=== 4.4.2 Configure the MQTT Client for Downstream === 403 - 404 -Below screen shot equal to this subscribe command: 405 - 406 -(% class="box" %) 407 -((( 408 -mosquitto_sub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t command. 409 -))) 410 - 411 -[[image:image-20220527140100-15.png]] 412 - 413 -MQTT Subscribe 414 - 415 - 416 -((( 417 -When MQTT broker receive a update on this topic, the gateway will get the update and use LoRa radio to broadcast this message. The LoRa parameters used for update is: 418 -))) 419 - 420 -[[image:image-20220527140148-16.png]] 421 - 422 -LoRa Broadcast parameters. 423 - 424 - 425 -And below is the subscribe simulation: 426 - 427 -[[image:image-20220527140238-17.png]] 428 - 429 -downstream simulation 430 - 431 - 432 -== 4.5 Add LoRa support to communicate with remote sensor == 433 - 434 -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. 435 - 436 - 437 -=== 4.5.1 Use LoRa Raw protocol for communication ~-~- For LG01/LG02 === 438 - 439 -((( 440 -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. 441 -))) 442 - 443 -((( 444 -The example Sketch for LoRa Shield +Arduino is here: [[LoRa_Shield_Sketch_For_MQTT>>url:http://www.dragino.com/downloads/index.php?dir=LoraShield/]] 445 -))) 446 - 447 -((( 448 -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. 449 -))) 450 - 451 -((( 452 452 What does the Arduino Sketch do? The Arduino Sketch will: 453 453 ))) 454 454 ... ... @@ -461,7 +461,6 @@ 461 461 LoRa Parameter should match 462 462 463 463 464 - 465 465 Below is the test result after the Arduino Sketch is running. 466 466 467 467 [[image:image-20220527140459-19.png]] ... ... @@ -469,14 +469,14 @@ 469 469 Upstream Data Flow 470 470 471 471 472 - 473 473 [[image:image-20220527140542-20.png]] 474 474 475 475 Downstream Data Flow 476 476 477 477 478 -== =4.5.2 Use LoRaWAN Protocol for communication ~-~- For LG308/LPS8/DLOS8 ===116 +== 3.2 Use LoRaWAN Protocol for communication ~-~- For LG308/LPS8/DLOS8/LG308N/LPS8N/DLOS8N == 479 479 118 + 480 480 ((( 481 481 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. 482 482 ))) ... ... @@ -483,15 +483,17 @@ 483 483 484 484 ((( 485 485 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. 486 -(% style="color:#4f81bd" %)**Video Instruction**(%%): (% style="color:blue" %)[[https:~~/~~/youtu.be/qJTY441-t90>>url:https://youtu.be/qJTY441-t90]] 125 + 126 + 127 +(% style="color:blue" %)**Video Instruction**(%%): (% style="color:blue" %)[[https:~~/~~/youtu.be/qJTY441-t90>>url:https://youtu.be/qJTY441-t90]] 487 487 ))) 488 488 489 489 ((( 490 -(% 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.131 +(% 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. 491 491 ))) 492 492 493 493 ((( 494 -(% style="color: #4f81bd" %)**Step 2**(%%): Make sure your Radio settings match the End Node settings.135 +(% style="color:blue" %)**Step 2**(%%): Make sure your Radio settings match the End Node settings. 495 495 ))) 496 496 497 497 [[image:image-20220527141235-21.png]] ... ... @@ -501,7 +501,7 @@ 501 501 502 502 ((( 503 503 ((( 504 -(% 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.145 +(% 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. 505 505 ))) 506 506 ))) 507 507 ... ... @@ -508,52 +508,42 @@ 508 508 [[image:image-20220613191345-4.png]] 509 509 510 510 152 +(% style="color:blue" %)**Step 4**(%%): Map the Device Address to Remote ID in MQTT server. 511 511 512 -(% style="color:#4f81bd" %)**Step 4**(%%): Map the Device Address to Remote ID in MQTT server. 513 - 514 514 [[image:image-20220613190635-2.png]] 515 515 516 516 157 +(% style="color:blue" %)**Step 5: Upstream**(%%): Save the change, we can see the log info via "sytem log", End Node and MQTT Server 517 517 518 -(% style="color:#4f81bd" %)**Step 5: Upstream**(%%): Save the change, we can see the log info via "sytem log", End Node and MQTT Server 519 - 520 520 [[image:image-20220527141843-24.png]] 521 521 522 522 523 - 524 - 525 525 [[image:image-20220527141933-25.png]] 526 526 527 527 Choose ASCII Format 528 528 529 529 530 - 531 531 [[image:image-20220527142028-26.png]] 532 532 533 533 LHT65 Decoder 534 534 535 535 172 +(% style="color:blue" %)**Step 6: Set up subscribe**(%%)**:** Subscribe a topci for downstream. 536 536 537 -(% style="color:#4f81bd" %)**Step 6: Set up subscribe**(%%)**:** Subscribe a topci for downstream. 538 - 539 539 [[image:image-20220613191426-5.png]] 540 540 541 541 177 +(% style="color:blue" %)**Step 7: Downstream**(%%): Save the change, we can see the log info via "sytem log", End Node and MQTT Server. 542 542 543 -(% style="color:#4f81bd" %)**Step 7: Downstream**(%%): Save the change, we can see the log info via "sytem log", End Node and MQTT Server. 544 - 545 545 [[image:image-20220527142239-28.png]] 546 546 547 547 548 548 549 -=== MQTT Downstream format === 550 - 551 - 552 552 mosquitto_pub -h $server_address -p $server_port -t $Client_ID -m "**dev_addr,imme/time,txt/hex,payload**" 553 553 554 554 (% class="box infomessage" %) 555 555 ((( 556 -mosquitto_pub -h 10.130.2.192 -p 1883 -t dragino-1d25dc/ -m "260211D,time,txt,hello" 187 +**mosquitto_pub -h 10.130.2.192 -p 1883 -t dragino-1d25dc/ -m "260211D,time,txt,hello"** 557 557 ))) 558 558 559 559 mosquitto_pub -h $server_address -p $server_port -t $Client_ID -m "**dev_addr,imme/time,txt/hex,payload,txpw,txbw,SF,frequency,rxwindow**" ... ... @@ -560,24 +560,24 @@ 560 560 561 561 (% class="box infomessage" %) 562 562 ((( 563 -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"194 +**mosquitto_pub -h 10.130.2.192 -p 1883 -t dragino-1d25dc/ -m "260211D,time,txt,hello,20,1,SF12,923300000,2"** 564 564 ))) 565 565 197 +(% 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"]]** 198 + 566 566 Or use [[MQTT.fx>>https://mqttfx.jensd.de/index.php/download]] 567 567 568 568 [[image:image-20220613192816-6.png||height="440" width="1056"]] 569 569 570 -(% 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"]]** 571 571 572 - Checkoutthislink formore mosquito-relateddirectives [[https:~~/~~/mosquitto.org/man/mosquitto_pub-1.html>>https://mosquitto.org/man/mosquitto_pub-1.html]]204 +== 3.3 Use LoRaWAN Protocol for communication ~-~- For LPS8V2 == 573 573 574 -= 5. How to Debug = 575 575 576 -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. 577 577 578 578 579 -= 6. How to ask for Support =209 += 4. How to ask for Support = 580 580 211 + 581 581 If a user still not have trouble making it works. please send a mail to support@dragino.com with the below info: 582 582 583 583 * Detail of your LoRaWAN end node.
- image-20220714155901-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +75.2 KB - Content