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