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
-
... ... @@ -106,6 +106,7 @@ 106 106 107 107 [[RS485-LN Image files – Download link and Change log>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/]] 108 108 109 + 109 109 == 1.6 Hardware Change log == 110 110 111 111 ((( ... ... @@ -113,6 +113,8 @@ 113 113 v1.2: Add External Interrupt Pin. 114 114 115 115 v1.0: Release 117 + 118 + 116 116 ))) 117 117 ))) 118 118 ... ... @@ -129,6 +129,8 @@ 129 129 ))) 130 130 131 131 [[image:1653268091319-405.png]] 135 + 136 + 132 132 ))) 133 133 134 134 = 3. Operation Mode = ... ... @@ -137,6 +137,8 @@ 137 137 138 138 ((( 139 139 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 + 140 140 ))) 141 141 142 142 == 3.2 Example to join LoRaWAN network == ... ... @@ -145,10 +145,15 @@ 145 145 146 146 [[image:1653268155545-638.png||height="334" width="724"]] 147 147 155 + 148 148 ((( 157 +((( 149 149 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 +))) 150 150 161 +((( 151 151 485A+ and 485B- of the sensor are connected to RS485A and RA485B of RS485-LN respectively. 163 +))) 152 152 153 153 [[image:1653268227651-549.png||height="592" width="720"]] 154 154 ... ... @@ -200,6 +200,7 @@ 200 200 201 201 [[image:1652953568895-172.png||height="232" width="724"]] 202 202 215 + 203 203 == 3.3 Configure Commands to read data == 204 204 205 205 ((( ... ... @@ -209,6 +209,8 @@ 209 209 210 210 ((( 211 211 (% 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 + 212 212 ))) 213 213 ))) 214 214 ... ... @@ -216,19 +216,19 @@ 216 216 217 217 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: 218 218 219 -(% border="1" style="background-color:#ffffcc; color:green; width:7 95px" %)220 -|((( 234 +(% border="1" style="background-color:#ffffcc; color:green; width:782px" %) 235 +|(% style="width:128px" %)((( 221 221 **AT Commands** 222 -)))|(% style="width: 285px" %)(((237 +)))|(% style="width:305px" %)((( 223 223 **Description** 224 -)))|(% style="width:34 7px" %)(((239 +)))|(% style="width:346px" %)((( 225 225 **Example** 226 226 ))) 227 -|((( 242 +|(% style="width:128px" %)((( 228 228 AT+BAUDR 229 -)))|(% style="width: 285px" %)(((244 +)))|(% style="width:305px" %)((( 230 230 Set the baud rate (for RS485 connection). Default Value is: 9600. 231 -)))|(% style="width:34 7px" %)(((246 +)))|(% style="width:346px" %)((( 232 232 ((( 233 233 AT+BAUDR=9600 234 234 ))) ... ... @@ -237,11 +237,11 @@ 237 237 Options: (1200,2400,4800,14400,19200,115200) 238 238 ))) 239 239 ))) 240 -|((( 255 +|(% style="width:128px" %)((( 241 241 AT+PARITY 242 -)))|(% style="width: 285px" %)(((257 +)))|(% style="width:305px" %)((( 243 243 Set UART parity (for RS485 connection) 244 -)))|(% style="width:34 7px" %)(((259 +)))|(% style="width:346px" %)((( 245 245 ((( 246 246 AT+PARITY=0 247 247 ))) ... ... @@ -250,9 +250,9 @@ 250 250 Option: 0: no parity, 1: odd parity, 2: even parity 251 251 ))) 252 252 ))) 253 -|((( 268 +|(% style="width:128px" %)((( 254 254 AT+STOPBIT 255 -)))|(% style="width: 285px" %)(((270 +)))|(% style="width:305px" %)((( 256 256 ((( 257 257 Set serial stopbit (for RS485 connection) 258 258 ))) ... ... @@ -260,7 +260,7 @@ 260 260 ((( 261 261 262 262 ))) 263 -)))|(% style="width:34 7px" %)(((278 +)))|(% style="width:346px" %)((( 264 264 ((( 265 265 AT+STOPBIT=0 for 1bit 266 266 ))) ... ... @@ -274,6 +274,8 @@ 274 274 ))) 275 275 ))) 276 276 292 + 293 + 277 277 === 3.3.2 Configure sensors === 278 278 279 279 ((( ... ... @@ -292,80 +292,41 @@ 292 292 mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command 293 293 )))|(% style="width:256px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m 294 294 295 -=== 3.3.3 Configure read commands for each sampling === 296 296 297 -((( 298 -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. 299 -))) 300 300 301 -((( 302 -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. 303 -))) 314 +=== 3.3.3 Configure read commands for each sampling === 304 304 305 305 ((( 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 + 306 306 To save the LoRaWAN network bandwidth, we might need to read data from different sensors and combine their valid value into a short payload. 307 -))) 308 308 309 -((( 310 310 This section describes how to achieve above goals. 311 -))) 312 312 313 -((( 314 -During each sampling, the RS485-BL can support 15 commands to read sensors. And combine the return to one or several uplink payloads. 315 -))) 323 +During each sampling, the RS485-LN can support 15 commands to read sensors. And combine the return to one or several uplink payloads. 316 316 317 -((( 318 -**Command from RS485-BL to Sensor:** 319 -))) 320 320 321 -((( 322 -RS485-BL can send out pre-set max 15 strings via **AT+COMMAD1**, **ATCOMMAND2**,…, to **AT+COMMANDF** . All commands are of same grammar. 323 -))) 326 +**Each RS485 commands include two parts:** 324 324 325 -((( 326 -**Handle return from sensors to RS485-BL**: 327 -))) 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. 328 328 329 -((( 330 -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** 331 -))) 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. 332 332 333 -* ((( 334 -**AT+DATACUT** 335 -))) 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 336 336 337 -((( 338 -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. 339 -))) 334 +**AT+CMDDL1=1000** to send the open time to 1000ms 340 340 341 -* ((( 342 -**AT+SEARCH** 343 -))) 344 344 345 -((( 346 -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. 347 -))) 348 - 349 -((( 350 -**Define wait timeout:** 351 -))) 352 - 353 -((( 354 -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 355 -))) 356 - 357 -((( 358 358 After we got the valid value from each RS485 commands, we need to combine them together with the command **AT+DATAUP**. 359 -))) 360 360 361 -**Examples:** 362 362 363 363 Below are examples for the how above AT Commands works. 364 364 365 -**AT+COMMANDx : **This command will be sent to RS485/TTL devices during each sampling, Max command length is 14 bytes. The grammar is: 366 366 367 -(% border="1" class="table-bordered" %) 368 -|((( 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" %)((( 369 369 **AT+COMMANDx=xx xx xx xx xx xx xx xx xx xx xx xx,m** 370 370 371 371 **xx xx xx xx xx xx xx xx xx xx xx xx: The RS485 command to be sent** ... ... @@ -373,90 +373,40 @@ 373 373 **m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command** 374 374 ))) 375 375 376 -((( 377 377 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. 378 -))) 379 379 380 -((( 381 -In the RS485-BL, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same. 382 -))) 356 +In the RS485-LN, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same. 383 383 384 -((( 385 -**AT+SEARCHx**: This command defines how to handle the return from AT+COMMANDx. 386 -))) 387 387 388 -(% border="1" class="table-bordered" %) 389 -|((( 390 -**AT+SEARCHx=aa,xx xx xx xx xx** 391 - 392 -* **aa: 1: prefix match mode; 2: prefix and suffix match mode** 393 -* **xx xx xx xx xx: match string. Max 5 bytes for prefix and 5 bytes for suffix** 394 - 395 - 396 -))) 397 - 398 -**Examples:** 399 - 400 -~1. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49 401 - 402 -If we set AT+SEARCH1=1,1E 56 34. (max 5 bytes for prefix) 403 - 404 -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** 405 - 406 -[[image:1653269403619-508.png]] 407 - 408 -2. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49 409 - 410 -If we set AT+SEARCH1=2, 1E 56 34+31 00 49 411 - 412 -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** 413 - 414 -[[image:1653269438444-278.png]] 415 - 416 416 **AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes. 417 417 418 -|((( 361 +(% border="1" style="background-color:#4bacc6; color:white; width:725px" %) 362 +|(% style="width:722px" %)((( 419 419 **AT+DATACUTx=a,b,c** 420 420 421 421 * **a: length for the return of AT+COMMAND** 422 422 * **b:1: grab valid value by byte, max 6 bytes. 2: grab valid value by bytes section, max 3 sections.** 423 -* **c: define the position for valid value. 367 +* **c: define the position for valid value. ** 424 424 ))) 425 425 426 -Examples: 427 427 371 +**Examples:** 372 + 428 428 * Grab bytes: 429 429 430 -[[image: 1653269551753-223.png||height="311" width="717"]]375 +[[image:image-20220602153621-1.png]] 431 431 377 + 432 432 * Grab a section. 433 433 434 -[[image: 1653269568276-930.png||height="325" width="718"]]380 +[[image:image-20220602153621-2.png]] 435 435 382 + 436 436 * Grab different sections. 437 437 438 -[[image:1653269593172-426.png||height="303" width="725"]] 385 +[[image:image-20220602153621-3.png]] 386 +))) 439 439 440 -(% style="color:red" %)**Note:** 441 - 442 -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. 443 - 444 -Example: 445 - 446 -(% style="color:red" %)AT+COMMAND1=11 01 1E D0,0 447 - 448 -(% style="color:red" %)AT+SEARCH1=1,1E 56 34 449 - 450 -(% style="color:red" %)AT+DATACUT1=0,2,1~~5 451 - 452 -(% style="color:red" %)Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49 453 - 454 -(% style="color:red" %)String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49 455 - 456 -(% style="color:red" %)Valid payload after DataCUT command: 2e 30 58 5f 36 457 - 458 -[[image:1653269618463-608.png]] 459 - 460 460 === 3.3.4 Compose the uplink payload === 461 461 462 462 (((
- 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