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,281 +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 - 127 -Above screen shots shows below format: 128 - 129 -* -t: CLIENTID/CHANNEL/data 130 -* -m: DATA 131 - 132 -When there is a LoRa sensor arrive. it will be store at the /var/iot/channels as below: 133 - 134 -[[image:image-20220527134332-5.png]] 135 - 136 -Sensor Data 137 - 138 - 139 -((( 140 -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. 141 -))) 142 - 143 - 144 -== 3.4 Modify the MQTT to support more options == 145 - 146 -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: 147 - 148 -(% class="box" %) 149 -((( 150 -root@dragino-1ec39c:~~# mosquitto_pub ~-~-help 151 -mosquitto_pub is a simple mqtt client that will publish a message on a single topic and exit. 152 -mosquitto_pub version 1.6.4 running on libmosquitto 1.6.4. 153 -\\Usage: mosquitto_pub {[-h host] [-p port] [-u username] [-P password] -t topic | -L URL} 154 - {-f file | -l | -n | -m message} 155 - [-c] [-k keepalive] [-q qos] [-r] [~-~-repeat N] [~-~-repeat-delay time] 156 - [-A bind_address] 157 - [-i id] [-I id_prefix] 158 - [-d] [~-~-quiet] 159 - [-M max_inflight] 160 - [-u username [-P password]] 161 - [~-~-will-topic [~-~-will-payload payload] [~-~-will-qos qos] [~-~-will-retain]] 162 - [{~-~-cafile file | ~-~-capath dir} [~-~-cert file] [~-~-key file] 163 - [~-~-ciphers ciphers] [~-~-insecure] 164 - [~-~-tls-alpn protocol] 165 - [~-~-tls-engine engine] [~-~-keyform keyform] [~-~-tls-engine-kpass-sha1]] 166 - [~-~-psk hex-key ~-~-psk-identity identity [~-~-ciphers ciphers]] 167 - [~-~-proxy socks-url] 168 - [~-~-property command identifier value] 169 - [-D command identifier value] 170 - mosquitto_pub ~-~-help 171 -\\-A : bind the outgoing socket to this host/ip address. Use to control which interface 172 - the client communicates over. 173 --d : enable debug messages. 174 --D : Define MQTT v5 properties. See the documentation for more details. 175 --f : send the contents of a file as the message. 176 --h : mqtt host to connect to. Defaults to localhost. 177 --i : id to use for this client. Defaults to mosquitto_pub_ appended with the process id. 178 --I : define the client id as id_prefix appended with the process id. Useful for when the 179 - broker is using the clientid_prefixes option. 180 --k : keep alive in seconds for this client. Defaults to 60. 181 --L : specify user, password, hostname, port and topic as a URL in the form: 182 - mqtt(s):~/~/[username[:password]@]host[:port]/topic 183 --l : read messages from stdin, sending a separate message for each line. 184 --m : message payload to send. 185 --M : the maximum inflight messages for QoS 1/2.. 186 --n : send a null (zero length) message. 187 --p : network port to connect to. Defaults to 1883 for plain MQTT and 8883 for MQTT over TLS. 188 --P : provide a password 189 --q : quality of service level to use for all messages. Defaults to 0. 190 --r : message should be retained. 191 --s : read message from stdin, sending the entire input as a message. 192 --t : mqtt topic to publish to. 193 --u : provide a username 194 --V : specify the version of the MQTT protocol to use when connecting. 195 - Can be mqttv5, mqttv311 or mqttv31. Defaults to mqttv311. 196 -~-~-help : display this message. 197 -~-~-repeat : if publish mode is -f, -m, or -s, then repeat the publish N times. 198 -~-~-repeat-delay : if using ~-~-repeat, wait time seconds between publishes. Defaults to 0. 199 -~-~-quiet : (% style="color:red" %)don't print error messages. 200 -~-~-will-payload : payload for the client Will, which is sent by the broker in case of 201 - unexpected disconnection. If not given and will-topic is set, a zero 202 - length message will be sent. 203 -~-~-will-qos : QoS level for the client Will. 204 -~-~-will-retain : if given, make the client Will retained. 205 -~-~-will-topic : the topic on which to publish the client Will. 206 -~-~-cafile : path to a file containing trusted CA certificates to enable encrypted 207 - communication. 208 -~-~-capath : path to a directory containing trusted CA certificates to enable encrypted 209 - communication. 210 -~-~-cert : client certificate for authentication, if required by server. 211 -~-~-key : client private key for authentication, if required by server. 212 -~-~-keyform : keyfile type, can be either "pem" or "engine". 213 -~-~-ciphers : openssl compatible list of TLS ciphers to support. 214 -~-~-tls-version : TLS protocol version, can be one of tlsv1.3 tlsv1.2 or tlsv1.1. 215 - Defaults to tlsv1.2 if available. 216 -~-~-insecure : do not check that the server certificate hostname matches the remote 217 - hostname. Using this option means that you cannot be sure that the 218 - remote host is the server you wish to connect to and so is insecure. 219 - Do not use this option in a production environment. 220 -~-~-tls-engine : If set, enables the use of a TLS engine device. 221 -~-~-tls-engine-kpass-sha1 : SHA1 of the key password to be used with the selected SSL engine. 222 -~-~-psk : pre-shared-key in hexadecimal (no leading 0x) to enable TLS-PSK mode. 223 -~-~-psk-identity : client identity string for TLS-PSK mode. 224 -~-~-proxy : SOCKS5 proxy URL of the form: 225 - socks5h:~/~/[username[:password]@]hostname[:port] 226 - Only "none" and "username" authentication is supported. 227 -\\See https:~/~/mosquitto.org/ for more information. 228 -))) 229 - 230 - 231 -((( 232 -and modify the /usr/bin/mqtt_process.sh script, the location to change the command option is below lines: 233 -))) 234 - 235 -(% class="box" %) 236 -((( 237 -//# Call MQTT Publish command 238 -\\# 1. Case with User, Password and Client ID present (e.g. Azure) 239 -if [ ! -z "$pass" ] && [ ! -z "$user" ] && [ ! -z "$clientID" ]; then 240 -case="1" 241 -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" 242 -\\# 2. Case with Certificate, Key and ClientID present (e.g. AWS) 243 -elif [ ! -z "$certfile" ] && [ ! -z "$key" ] && [ ! -z "$clientID" ]; then 244 -case="2" 245 -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" 246 -\\# 3. Case with no User, Certificate or ClientID present 247 -elif [ -z "$user" ] && [ -z "$certfile" ] && [ -z "$clientID" ]; then 248 -case="3" 249 -mosquitto_pub $D -h $server -p $port -q $pub_qos -t $pub_topic $PUB_FLAG "$mqtt_data" 250 -\\# 4. Case with no User, Certificate, but with ClientID present 251 -elif [ -z "$user" ] && [ -z "$certfile" ] && [ ! -z "$clientID" ]; then 252 -case="4" 253 -mosquitto_pub $D -h $server -p $port -q $pub_qos -i $clientID -t $pub_topic $PUB_FLAG "$mqtt_data" 254 -\\# 5. Case with User and ClientID present, but no Password and no Certificate present 255 -elif [ -z "$pass" ] && [ -z "$certfile" ] && [ ! -z "$user" ] && [ ! -z "$clientID" ]; then 256 -case="5" 257 -mosquitto_pub $D -h $server -p $port -q $pub_qos -i $clientID -t $pub_topic -u $user $PUB_FLAG "$mqtt_data" 258 -\\# 6. Case with User and Password present, but no ClientID and no Certificate present 259 -elif [ ! -z "$user" ] && [ ! -z "$pass" ] && [ -z "$clientID" ] && [ -z "$certfile" ]; then 260 -case="6" 261 -mosquitto_pub $D -h $server -p $port -q $pub_qos -t $pub_topic -u $user -P "$pass" $PUB_FLAG "$mqtt_data" 262 -\\# 0. Else - invalid parameters, just log 263 -else 264 -case="(% style="color:red" %)Invalid parameters" (%%) 265 -logger (% style="color:red" %)"[IoT.MQTT]:Invalid Parameters - mosquitto_pub not called."(%%) 266 -fi// 267 -))) 268 - 269 - 270 -= 4. Example to communicate to a simple MQTT server = 271 - 272 -== 4.1 Overview == 273 - 274 274 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/]]. 275 275 276 276 277 -== 4.2 Simulate via MQTT.fx utility ==38 +== 2.2 Simulate via MQTT.fx utility == 278 278 40 + 279 279 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. 280 280 281 281 ((( ... ... @@ -301,153 +301,32 @@ 301 301 Downstream: Subscribe a topic to get downstream 302 302 303 303 304 -== 4.3 Simulate via Dragino Command Line == 305 305 306 - 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 = 307 307 308 -In the Dragino Gateway, we use [[mosquitto client>>url:https://mosquitto.org/]] for MQTT connection. 309 309 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. 310 310 311 -(% style="color:#4f81bd" %)**For Upstream** 312 312 313 -command is [[mosquitto_pub>>url:https://mosquitto.org/man/mosquitto_pub-1.html]] 314 314 315 - 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 == 316 316 317 -Note: 192.168.199.148 is MQTT broker address, the gateway and the MQTT broker PC are in the same network. 318 318 319 -[[image:image-20220527135310-9.png]] 320 - 321 -mosquitto_pub 322 - 323 - 324 -(% style="color:#4f81bd" %)**For Downstream** 325 - 326 -Use [[mosquitto_sub>>url:https://mosquitto.org/man/mosquitto_sub-1.html]] to subscribe the change on the topic. 327 - 328 -[[image:image-20220527135440-10.png]] 329 - 330 -mosquitto_sub 331 - 332 - 333 -== 4.4 Configure Dragino UI for MQTT connection == 334 - 335 -This chapter are step by step to show to configure the Dragino Menu for MQTT auto connection. 336 - 337 337 ((( 338 - 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. 339 339 ))) 340 340 341 -[[image:https://wiki.dragino.com/images/thumb/b/bc/MQTT_Command_8.png/600px-MQTT_Command_8.png||height="249" width="600"]] 342 - 343 -go to mqtt configure menu 344 - 345 - 346 346 ((( 347 - 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/]]** 348 348 ))) 349 349 350 -[[image:image-20220527135742-11.png]] 351 - 352 -forward to MQTT 353 - 354 - 355 -=== 4.4.1 Configure the MQTT Client for Upstream === 356 - 357 -Below screenshot is same as the publish command: 358 - 359 -(% class="box" %) 360 360 ((( 361 -mosquitto_pub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t CLIENTID/CHANNEL/data -m DATA 362 -~/~/where the CLIENTID, CHANNEL & DATA are macro. represent for 363 -~/~/CLIENTID: dragino-1b7060 364 -~/~/CHANNEL: Remote ID in Channel settings; here is 78901 or 567456 365 -~/~/DATA: The data stores in /var/iot/channels/ 366 -))) 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. 367 367 368 -[[image:image-20220527135828-12.png]] 369 - 370 -MQTT Publish configure 371 - 372 - 373 -[[image:image-20220527135929-13.png]] 374 - 375 -MQTT Channel settings 376 - 377 - 378 -((( 379 -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 + 380 380 ))) 381 381 382 -(% class="box" %) 383 383 ((( 384 -mosquitto_pub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t dragino-1b7060/78901/data -m temp=46 385 -))) 386 - 387 -((( 388 -to MQTT broker. 389 -))) 390 - 391 - 392 -((( 393 -Below is a simulation to put this data to active the MQTT publish. 394 -))) 395 - 396 -[[image:image-20220527140023-14.png]] 397 - 398 -MQTT Publish 399 - 400 - 401 -=== 4.4.2 Configure the MQTT Client for Downstream === 402 - 403 -Below screen shot equal to this subscribe command: 404 - 405 -(% class="box" %) 406 -((( 407 -mosquitto_sub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t command. 408 -))) 409 - 410 -[[image:image-20220527140100-15.png]] 411 - 412 -MQTT Subscribe 413 - 414 - 415 -((( 416 -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: 417 -))) 418 - 419 -[[image:image-20220527140148-16.png]] 420 - 421 -LoRa Broadcast parameters. 422 - 423 - 424 -And below is the subscribe simulation: 425 - 426 -[[image:image-20220527140238-17.png]] 427 - 428 -downstream simulation 429 - 430 - 431 -== 4.5 Add LoRa support to communicate with remote sensor == 432 - 433 -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. 434 - 435 - 436 -=== 4.5.1 Use LoRa Raw protocol for communication ~-~- For LG01/LG02 === 437 - 438 -((( 439 -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. 440 -))) 441 - 442 -((( 443 -The example Sketch for LoRa Shield +Arduino is here: [[LoRa_Shield_Sketch_For_MQTT>>url:http://www.dragino.com/downloads/index.php?dir=LoraShield/]] 444 -))) 445 - 446 -((( 447 -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. 448 -))) 449 - 450 -((( 451 451 What does the Arduino Sketch do? The Arduino Sketch will: 452 452 ))) 453 453 ... ... @@ -472,8 +472,9 @@ 472 472 Downstream Data Flow 473 473 474 474 475 -== =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 == 476 476 118 + 477 477 ((( 478 478 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. 479 479 ))) ... ... @@ -480,15 +480,17 @@ 480 480 481 481 ((( 482 482 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. 483 -(% 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]] 484 484 ))) 485 485 486 486 ((( 487 -(% 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. 488 488 ))) 489 489 490 490 ((( 491 -(% 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. 492 492 ))) 493 493 494 494 [[image:image-20220527141235-21.png]] ... ... @@ -498,29 +498,23 @@ 498 498 499 499 ((( 500 500 ((( 501 -(% 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. 502 502 ))) 503 503 ))) 504 504 505 -[[image:image-20220 527141450-22.png]]149 +[[image:image-20220613191345-4.png]] 506 506 507 -Publish mush use META as data format for LG308 508 508 152 +(% style="color:blue" %)**Step 4**(%%): Map the Device Address to Remote ID in MQTT server. 509 509 510 - (% style="color:#4f81bd" %)**Step 4**(%%): Map theDevice Address to RemoteID in MQTT server.154 +[[image:image-20220613190635-2.png]] 511 511 512 -[[image:image-20220527141727-23.png]] 513 513 514 - MapDevAddrtoremoteID157 +(% style="color:blue" %)**Step 5: Upstream**(%%): Save the change, we can see the log info via "sytem log", End Node and MQTT Server 515 515 516 - 517 -(% style="color:#4f81bd" %)**Step 5: Upstream**(%%): Save the change, we can see the log info via "sytem log", End Node and MQTT Server 518 - 519 519 [[image:image-20220527141843-24.png]] 520 520 521 -Upstream Process 522 522 523 - 524 524 [[image:image-20220527141933-25.png]] 525 525 526 526 Choose ASCII Format ... ... @@ -531,29 +531,46 @@ 531 531 LHT65 Decoder 532 532 533 533 534 -(% 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. 535 535 536 -[[image:image-20220 527142115-27.png]]174 +[[image:image-20220613191426-5.png]] 537 537 538 -Subscribe to a topic 539 539 177 +(% style="color:blue" %)**Step 7: Downstream**(%%): Save the change, we can see the log info via "sytem log", End Node and MQTT Server. 540 540 541 -(% style="color:#4f81bd" %)**Step 7: Downstream**(%%): Save the change, we can see the log info via "sytem log", End Node and MQTT Server. 542 - 543 543 [[image:image-20220527142239-28.png]] 544 544 545 -Downstream Flow 546 546 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 + 547 547 (% 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"]]** 548 548 199 +Or use [[MQTT.fx>>https://mqttfx.jensd.de/index.php/download]] 549 549 550 - = 5.How to Debug =201 +[[image:image-20220613192816-6.png||height="440" width="1056"]] 551 551 552 -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. 553 553 204 +== 3.3 Use LoRaWAN Protocol for communication ~-~- For LPS8V2 == 554 554 555 -= 6. How to ask for Support = 556 556 207 + 208 + 209 += 4. How to ask for Support = 210 + 211 + 557 557 If a user still not have trouble making it works. please send a mail to support@dragino.com with the below info: 558 558 559 559 * 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