Changes for page RS485-LN – RS485 to LoRaWAN Converter User Manual
Last modified by Karry Zhuang on 2025/03/06 16:34
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 3 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -142,6 +142,8 @@ 142 142 143 143 ((( 144 144 The RS485-LN is configured as LoRaWAN OTAA Class C mode by default. It has OTAA keys to join network. To connect a local LoRaWAN network, user just need to input the OTAA keys in the network server and power on the RS485-LN. It will auto join the network via OTAA. 145 + 146 + 145 145 ))) 146 146 147 147 == 3.2 Example to join LoRaWAN network == ... ... @@ -150,10 +150,15 @@ 150 150 151 151 [[image:1653268155545-638.png||height="334" width="724"]] 152 152 155 + 153 153 ((( 157 +((( 154 154 The RS485-LN in this example connected to two RS485 devices for demonstration, user can connect to other RS485 devices via the same method. The connection is as below: 159 +))) 155 155 161 +((( 156 156 485A+ and 485B- of the sensor are connected to RS485A and RA485B of RS485-LN respectively. 163 +))) 157 157 158 158 [[image:1653268227651-549.png||height="592" width="720"]] 159 159 ... ... @@ -205,6 +205,7 @@ 205 205 206 206 [[image:1652953568895-172.png||height="232" width="724"]] 207 207 215 + 208 208 == 3.3 Configure Commands to read data == 209 209 210 210 ((( ... ... @@ -214,6 +214,8 @@ 214 214 215 215 ((( 216 216 (% style="color:red" %)Note: below description and commands are for firmware version >v1.1, if you have firmware version v1.0. Please check the [[user manual v1.0>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/&file=RS485-LN_UserManual_v1.0.1.pdf]] or upgrade the firmware to v1.1 225 + 226 + 217 217 ))) 218 218 ))) 219 219 ... ... @@ -221,19 +221,19 @@ 221 221 222 222 To use RS485-LN to read data from RS485 sensors, connect the RS485-LN A/B traces to the sensors. And user need to make sure RS485-LN use the match UART setting to access the sensors. The related commands for UART settings are: 223 223 224 -(% border="1" style="background-color:#ffffcc; color:green; width:7 95px" %)225 -|((( 234 +(% border="1" style="background-color:#ffffcc; color:green; width:782px" %) 235 +|(% style="width:128px" %)((( 226 226 **AT Commands** 227 -)))|(% style="width: 285px" %)(((237 +)))|(% style="width:305px" %)((( 228 228 **Description** 229 -)))|(% style="width:34 7px" %)(((239 +)))|(% style="width:346px" %)((( 230 230 **Example** 231 231 ))) 232 -|((( 242 +|(% style="width:128px" %)((( 233 233 AT+BAUDR 234 -)))|(% style="width: 285px" %)(((244 +)))|(% style="width:305px" %)((( 235 235 Set the baud rate (for RS485 connection). Default Value is: 9600. 236 -)))|(% style="width:34 7px" %)(((246 +)))|(% style="width:346px" %)((( 237 237 ((( 238 238 AT+BAUDR=9600 239 239 ))) ... ... @@ -242,11 +242,11 @@ 242 242 Options: (1200,2400,4800,14400,19200,115200) 243 243 ))) 244 244 ))) 245 -|((( 255 +|(% style="width:128px" %)((( 246 246 AT+PARITY 247 -)))|(% style="width: 285px" %)(((257 +)))|(% style="width:305px" %)((( 248 248 Set UART parity (for RS485 connection) 249 -)))|(% style="width:34 7px" %)(((259 +)))|(% style="width:346px" %)((( 250 250 ((( 251 251 AT+PARITY=0 252 252 ))) ... ... @@ -255,9 +255,9 @@ 255 255 Option: 0: no parity, 1: odd parity, 2: even parity 256 256 ))) 257 257 ))) 258 -|((( 268 +|(% style="width:128px" %)((( 259 259 AT+STOPBIT 260 -)))|(% style="width: 285px" %)(((270 +)))|(% style="width:305px" %)((( 261 261 ((( 262 262 Set serial stopbit (for RS485 connection) 263 263 ))) ... ... @@ -265,7 +265,7 @@ 265 265 ((( 266 266 267 267 ))) 268 -)))|(% style="width:34 7px" %)(((278 +)))|(% style="width:346px" %)((( 269 269 ((( 270 270 AT+STOPBIT=0 for 1bit 271 271 ))) ... ... @@ -279,6 +279,8 @@ 279 279 ))) 280 280 ))) 281 281 292 + 293 + 282 282 === 3.3.2 Configure sensors === 283 283 284 284 ((( ... ... @@ -297,80 +297,41 @@ 297 297 mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command 298 298 )))|(% style="width:256px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m 299 299 300 -=== 3.3.3 Configure read commands for each sampling === 301 301 302 -((( 303 -RS485-BL is a battery powered device; it will sleep most of time. And wake up on each period and read RS485 / TTL sensor data and uplink. 304 -))) 305 305 306 -((( 307 -During each sampling, we need to confirm what commands we need to send to the sensors to read data. After the RS485/TTL sensors send back the value, it normally includes some bytes and we only need a few from them for a shorten payload. 308 -))) 314 +=== 3.3.3 Configure read commands for each sampling === 309 309 310 310 ((( 317 +During each sampling, we need confirm what commands we need to send to the RS485 sensors to read data. After the RS485 sensors send back the value, it normally include some bytes and we only need a few from them for a shorten payload. 318 + 311 311 To save the LoRaWAN network bandwidth, we might need to read data from different sensors and combine their valid value into a short payload. 312 -))) 313 313 314 -((( 315 315 This section describes how to achieve above goals. 316 -))) 317 317 318 -((( 319 -During each sampling, the RS485-BL can support 15 commands to read sensors. And combine the return to one or several uplink payloads. 320 -))) 323 +During each sampling, the RS485-LN can support 15 commands to read sensors. And combine the return to one or several uplink payloads. 321 321 322 -((( 323 -**Command from RS485-BL to Sensor:** 324 -))) 325 325 326 -((( 327 -RS485-BL can send out pre-set max 15 strings via **AT+COMMAD1**, **ATCOMMAND2**,…, to **AT+COMMANDF** . All commands are of same grammar. 328 -))) 326 +**Each RS485 commands include two parts:** 329 329 330 -((( 331 -**Handle return from sensors to RS485-BL**: 332 -))) 328 +~1. What commands RS485-LN will send to the RS485 sensors. There are total 15 commands from **AT+COMMAD1**, **ATCOMMAND2**,…, to **AT+COMMANDF**. All commands are of same grammar. 333 333 334 -((( 335 -After RS485-BL send out a string to sensor, RS485-BL will wait for the return from RS485 or TTL sensor. And user can specify how to handle the return, by **AT+DATACUT or AT+SEARCH commands** 336 -))) 330 +2. How to get wanted value the from RS485 sensors returns from by 1). There are total 15 AT Commands to handle the return, commands are **AT+DATACUT1**,**AT+DATACUT2**,…, **AT+DATACUTF** corresponding to the commands from 1). All commands are of same grammar. 337 337 338 -* ((( 339 -**AT+DATACUT** 340 -))) 332 +3. Some RS485 device might has longer delay on reply, so user can use AT+CMDDL to set the timeout for getting reply after the RS485 command is sent. For example 341 341 342 -((( 343 -When the return value from sensor have fix length and we know which position the valid value we should get, we can use AT+DATACUT command. 344 -))) 334 +**AT+CMDDL1=1000** to send the open time to 1000ms 345 345 346 -* ((( 347 -**AT+SEARCH** 348 -))) 349 349 350 -((( 351 -When the return value from sensor is dynamic length and we are not sure which bytes the valid data is, instead, we know what value the valid value following. We can use AT+SEARCH to search the valid value in the return string. 352 -))) 353 - 354 -((( 355 -**Define wait timeout:** 356 -))) 357 - 358 -((( 359 -Some RS485 device might has longer delay on reply, so user can use AT+CMDDL to set the timeout for getting reply after the RS485 command is sent. For example, AT+CMDDL1=1000 to send the open time to 1000ms 360 -))) 361 - 362 -((( 363 363 After we got the valid value from each RS485 commands, we need to combine them together with the command **AT+DATAUP**. 364 -))) 365 365 366 -**Examples:** 367 367 368 368 Below are examples for the how above AT Commands works. 369 369 370 -**AT+COMMANDx : **This command will be sent to RS485/TTL devices during each sampling, Max command length is 14 bytes. The grammar is: 371 371 372 -(% border="1" class="table-bordered" %) 373 -|((( 343 +**AT+COMMANDx : **This command will be sent to RS485 devices during each sampling, Max command length is 14 bytes. The grammar is: 344 + 345 +(% border="1" style="background-color:#4bacc6; color:white; width:499px" %) 346 +|(% style="width:496px" %)((( 374 374 **AT+COMMANDx=xx xx xx xx xx xx xx xx xx xx xx xx,m** 375 375 376 376 **xx xx xx xx xx xx xx xx xx xx xx xx: The RS485 command to be sent** ... ... @@ -378,90 +378,40 @@ 378 378 **m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command** 379 379 ))) 380 380 381 -((( 382 382 For example, if we have a RS485 sensor. The command to get sensor value is: 01 03 0B B8 00 02 46 0A. Where 01 03 0B B8 00 02 is the Modbus command to read the register 0B B8 where stored the sensor value. The 46 0A is the CRC-16/MODBUS which calculate manually. 383 -))) 384 384 385 -((( 386 -In the RS485-BL, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same. 387 -))) 356 +In the RS485-LN, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same. 388 388 389 -((( 390 -**AT+SEARCHx**: This command defines how to handle the return from AT+COMMANDx. 391 -))) 392 392 393 -(% border="1" class="table-bordered" %) 394 -|((( 395 -**AT+SEARCHx=aa,xx xx xx xx xx** 396 - 397 -* **aa: 1: prefix match mode; 2: prefix and suffix match mode** 398 -* **xx xx xx xx xx: match string. Max 5 bytes for prefix and 5 bytes for suffix** 399 - 400 - 401 -))) 402 - 403 -**Examples:** 404 - 405 -~1. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49 406 - 407 -If we set AT+SEARCH1=1,1E 56 34. (max 5 bytes for prefix) 408 - 409 -The valid data will be all bytes after 1E 56 34 , so it is (% style="background-color:yellow" %)** 2e 30 58 5f 36 41 30 31 00 49** 410 - 411 -[[image:1653269403619-508.png]] 412 - 413 -2. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49 414 - 415 -If we set AT+SEARCH1=2, 1E 56 34+31 00 49 416 - 417 -Device will search the bytes between 1E 56 34 and 31 00 49. So it is (% style="background-color:yellow" %)** 2e 30 58 5f 36 41 30** 418 - 419 -[[image:1653269438444-278.png]] 420 - 421 421 **AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes. 422 422 423 -|((( 361 +(% border="1" style="background-color:#4bacc6; color:white; width:725px" %) 362 +|(% style="width:722px" %)((( 424 424 **AT+DATACUTx=a,b,c** 425 425 426 426 * **a: length for the return of AT+COMMAND** 427 427 * **b:1: grab valid value by byte, max 6 bytes. 2: grab valid value by bytes section, max 3 sections.** 428 -* **c: define the position for valid value. 367 +* **c: define the position for valid value. ** 429 429 ))) 430 430 431 -Examples: 432 432 371 +**Examples:** 372 + 433 433 * Grab bytes: 434 434 435 -[[image: 1653269551753-223.png||height="311" width="717"]]375 +[[image:image-20220602153621-1.png]] 436 436 377 + 437 437 * Grab a section. 438 438 439 -[[image: 1653269568276-930.png||height="325" width="718"]]380 +[[image:image-20220602153621-2.png]] 440 440 382 + 441 441 * Grab different sections. 442 442 443 -[[image:1653269593172-426.png||height="303" width="725"]] 385 +[[image:image-20220602153621-3.png]] 386 +))) 444 444 445 -(% style="color:red" %)**Note:** 446 - 447 -AT+SEARCHx and AT+DATACUTx can be used together, if both commands are set, RS485-BL will first process AT+SEARCHx on the return string and get a temporary string, and then process AT+DATACUTx on this temporary string to get the final payload. In this case, AT+DATACUTx need to set to format AT+DATACUTx=0,xx,xx where the return bytes set to 0. 448 - 449 -Example: 450 - 451 -(% style="color:red" %)AT+COMMAND1=11 01 1E D0,0 452 - 453 -(% style="color:red" %)AT+SEARCH1=1,1E 56 34 454 - 455 -(% style="color:red" %)AT+DATACUT1=0,2,1~~5 456 - 457 -(% style="color:red" %)Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49 458 - 459 -(% style="color:red" %)String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49 460 - 461 -(% style="color:red" %)Valid payload after DataCUT command: 2e 30 58 5f 36 462 - 463 -[[image:1653269618463-608.png]] 464 - 465 465 === 3.3.4 Compose the uplink payload === 466 466 467 467 (((
- image-20220602153621-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +23.4 KB - Content
- image-20220602153621-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +22.2 KB - Content
- image-20220602153621-3.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +22.3 KB - Content