Changes for page RS485-BL – Waterproof RS485 to LoRaWAN Converter
Last modified by Xiaoling on 2025/04/23 15:57
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 12 removed)
Details
- Page properties
-
- Content
-
... ... @@ -7,15 +7,12 @@ 7 7 **RS485-BL – Waterproof RS485 to LoRaWAN Converter User Manual** 8 8 9 9 10 - 11 11 **Table of Contents:** 12 12 13 -{{toc/}} 14 14 15 15 16 16 17 17 18 - 19 19 = 1.Introduction = 20 20 21 21 == 1.1 What is RS485-BL RS485 to LoRaWAN Converter == ... ... @@ -63,7 +63,7 @@ 63 63 * Power Consumption (exclude RS485 device): 64 64 ** Idle: 6uA@3.3v 65 65 66 -* 63 +* 67 67 ** 20dB Transmit: 130mA@3.3v 68 68 69 69 **Interface for Model:** ... ... @@ -222,186 +222,143 @@ 222 222 223 223 [[image:1652953568895-172.png||height="232" width="724"]] 224 224 225 -== 3.3 Configure Commands to read data == 226 226 227 -((( 223 + 224 + 225 +1. 226 +11. Configure Commands to read data 227 + 228 228 There are plenty of RS485 and TTL level devices in the market and each device has different command to read the valid data. To support these devices in flexible, RS485-BL supports flexible command set. User can use [[AT Commands or LoRaWAN Downlink>>path:#AT_COMMAND]] Command to configure how RS485-BL should read the sensor and how to handle the return from RS485 or TTL sensors. 229 -))) 230 230 231 -=== 3.3.1 onfigure UART settings for RS485 or TTL communication === 232 232 231 +1. 232 +11. 233 +111. Configure UART settings for RS485 or TTL communication 234 + 233 233 RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect. 234 234 235 - **~1. RS485-MODBUS mode:**237 +1. RS485-MODBUS mode: 236 236 237 237 AT+MOD=1 ~/~/ Support RS485-MODBUS type sensors. User can connect multiply RS485 , Modbus sensors to the A / B pins. 238 238 239 -**2. TTL mode:** 240 240 242 +1. TTL mode: 243 + 241 241 AT+MOD=2 ~/~/ Support TTL Level sensors, User can connect one TTL Sensor to the TXD/RXD/GND pins. 242 242 246 + 243 243 RS485-BL default UART settings is **9600, no parity, stop bit 1**. If the sensor has a different settings, user can change the RS485-BL setting to match. 244 244 245 -(% border="1" style="background-color:#ffffcc; color:green; width:795px" %) 246 -|((( 247 -**AT Commands** 248 -)))|(% style="width:285px" %)((( 249 -**Description** 250 -)))|(% style="width:347px" %)((( 251 -**Example** 252 -))) 253 -|((( 254 -AT+BAUDR 255 -)))|(% style="width:285px" %)((( 256 -Set the baud rate (for RS485 connection). Default Value is: 9600. 257 -)))|(% style="width:347px" %)((( 258 -((( 249 + 250 +|**AT Commands**|**Description**|**Example** 251 +|AT+BAUDR|Set the baud rate (for RS485 connection). Default Value is: 9600.|((( 259 259 AT+BAUDR=9600 260 -))) 261 261 262 -((( 263 263 Options: (1200,2400,4800,14400,19200,115200) 264 264 ))) 265 -))) 266 -|((( 267 -AT+PARITY 268 -)))|(% style="width:285px" %)((( 269 -((( 256 +|AT+PARITY|((( 270 270 Set UART parity (for RS485 connection) 271 -))) 272 272 273 -((( 274 274 Default Value is: no parity. 275 -))) 276 -)))|(% style="width:347px" %)((( 277 -((( 260 +)))|((( 278 278 AT+PARITY=0 279 -))) 280 280 281 -((( 282 282 Option: 0: no parity, 1: odd parity, 2: even parity 283 283 ))) 284 -))) 285 -|((( 286 -AT+STOPBIT 287 -)))|(% style="width:285px" %)((( 288 -((( 265 +|AT+STOPBIT|((( 289 289 Set serial stopbit (for RS485 connection) 290 -))) 291 291 292 -((( 293 293 Default Value is: 1bit. 294 -))) 295 -)))|(% style="width:347px" %)((( 296 -((( 269 +)))|((( 297 297 AT+STOPBIT=0 for 1bit 298 -))) 299 299 300 -((( 301 301 AT+STOPBIT=1 for 1.5 bit 302 -))) 303 303 304 -((( 305 305 AT+STOPBIT=2 for 2 bits 306 306 ))) 307 -))) 308 308 309 -=== 3.3.2 Configure sensors === 310 310 311 -((( 312 -Some sensors might need to configure before normal operation. User can configure such sensor via PC or through RS485-BL AT Commands (% style="color:#4f81bd" %)**AT+CFGDEV**. 313 -))) 314 314 315 -((( 316 -When user issue an (% style="color:#4f81bd" %)**AT+CFGDEV**(%%) command, Each (% style="color:#4f81bd" %)**AT+CFGDEV**(%%) equals to send a command to the RS485 or TTL sensors. This command will only run when user input it and won’t run during each sampling. 317 -))) 318 318 319 -(% border="1" style="background-color:#ffffcc; color:green; width:806px" %) 320 -|**AT Commands**|(% style="width:418px" %)**Description**|(% style="width:256px" %)**Example** 321 -|AT+CFGDEV|(% style="width:418px" %)((( 280 +1. 281 +11. 282 +111. Configure sensors 283 + 284 +Some sensors might need to configure before normal operation. User can configure such sensor via PC or through RS485-BL AT Commands AT+CFGDEV. 285 + 286 + 287 +When user issue an AT+CFGDEV command, Each AT+CFGDEV equals to send a command to the RS485 or TTL sensors. This command will only run when user input it and won’t run during each sampling. 288 + 289 +|**AT Commands**|**Description**|**Example** 290 +|AT+CFGDEV|((( 322 322 This command is used to configure the RS485/TTL devices; they won’t be used during sampling. 323 323 324 -AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx, 293 +AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m 325 325 326 -m m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command327 -)))| (% style="width:256px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m295 +m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command 296 +)))|AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m 328 328 329 329 Detail of AT+CFGDEV command see [[AT+CFGDEV detail>>path:#AT_CFGDEV]]. 330 330 331 -=== 3.3.3 Configure read commands for each sampling === 332 332 333 -((( 301 + 302 + 303 + 304 +1. 305 +11. 306 +111. Configure read commands for each sampling 307 + 334 334 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. 335 -))) 336 336 337 - (((310 + 338 338 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. 339 -))) 340 340 341 - (((313 + 342 342 To save the LoRaWAN network bandwidth, we might need to read data from different sensors and combine their valid value into a short payload. 343 -))) 344 344 345 - (((316 + 346 346 This section describes how to achieve above goals. 347 -))) 348 348 349 - (((319 + 350 350 During each sampling, the RS485-BL can support 15 commands to read sensors. And combine the return to one or several uplink payloads. 351 -))) 352 352 353 - (((322 + 354 354 **Command from RS485-BL to Sensor:** 355 -))) 356 356 357 -((( 358 358 RS485-BL can send out pre-set max 15 strings via **AT+COMMAD1**, **ATCOMMAND2**,…, to **AT+COMMANDF** . All commands are of same grammar. 359 -))) 360 360 361 - (((327 + 362 362 **Handle return from sensors to RS485-BL**: 363 -))) 364 364 365 -((( 366 366 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** 367 -))) 368 368 369 -* ((( 370 -**AT+DATACUT** 371 -))) 372 372 373 -((( 333 +* **AT+DATACUT** 334 + 374 374 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. 375 -))) 376 376 377 -* ((( 378 -**AT+SEARCH** 379 -))) 380 380 381 -((( 338 +* **AT+SEARCH** 339 + 382 382 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. 383 -))) 384 384 385 - (((342 + 386 386 **Define wait timeout:** 387 -))) 388 388 389 -((( 390 390 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 391 -))) 392 392 393 - (((347 + 394 394 After we got the valid value from each RS485 commands, we need to combine them together with the command **AT+DATAUP**. 395 -))) 396 396 350 + 397 397 **Examples:** 398 398 399 399 Below are examples for the how above AT Commands works. 400 400 355 + 401 401 **AT+COMMANDx : **This command will be sent to RS485/TTL devices during each sampling, Max command length is 14 bytes. The grammar is: 402 402 403 -(% border="1" class="table-bordered" style="background-color:#4f81bd; color:white; width:501px" %) 404 -|(% style="width:498px" %)((( 358 +|((( 405 405 **AT+COMMANDx=xx xx xx xx xx xx xx xx xx xx xx xx,m** 406 406 407 407 **xx xx xx xx xx xx xx xx xx xx xx xx: The RS485 command to be sent** ... ... @@ -413,38 +413,41 @@ 413 413 414 414 In the RS485-BL, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same. 415 415 370 + 416 416 **AT+SEARCHx**: This command defines how to handle the return from AT+COMMANDx. 417 417 418 -(% border="1" class="table-bordered" style="background-color:#4f81bd; color:white; width:580px" %) 419 -|(% style="width:577px" %)((( 373 +|((( 420 420 **AT+SEARCHx=aa,xx xx xx xx xx** 421 421 422 422 * **aa: 1: prefix match mode; 2: prefix and suffix match mode** 423 423 * **xx xx xx xx xx: match string. Max 5 bytes for prefix and 5 bytes for suffix** 378 + 379 + 424 424 ))) 425 425 426 - **Examples:**382 +Examples: 427 427 428 428 1. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49 429 429 430 430 If we set AT+SEARCH1=1,1E 56 34. (max 5 bytes for prefix) 431 431 432 -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**388 +The valid data will be all bytes after 1E 56 34 , so it is 2e 30 58 5f 36 41 30 31 00 49 433 433 434 -[[image: 1653271044481-711.png]]390 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image013.png]] 435 435 392 + 436 436 1. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49 437 437 438 438 If we set AT+SEARCH1=2, 1E 56 34+31 00 49 439 439 440 -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**397 +Device will search the bytes between 1E 56 34 and 31 00 49. So it is 2e 30 58 5f 36 41 30 441 441 442 -[[image: 1653271276735-972.png]]399 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image014.png]] 443 443 401 + 444 444 **AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes. 445 445 446 -(% style="background-color:#4f81bd; color:white; width:729px" %) 447 -|(% style="width:726px" %)((( 404 +|((( 448 448 **AT+DATACUTx=a,b,c** 449 449 450 450 * **a: length for the return of AT+COMMAND** ... ... @@ -456,130 +456,95 @@ 456 456 457 457 * Grab bytes: 458 458 459 -[[image: 1653271581490-837.png||height="313" width="722"]]416 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image015.png]] 460 460 461 461 * Grab a section. 462 462 463 -[[image: 1653271648378-342.png||height="326" width="720"]]420 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image016.png]] 464 464 465 465 * Grab different sections. 466 466 467 -[[image: 1653271657255-576.png||height="305" width="730"]]424 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image017.png]] 468 468 469 -((( 470 -(% style="color:red" %)**Note:** 471 -))) 472 472 473 -((( 427 +Note: 428 + 474 474 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. 475 -))) 476 476 477 -((( 478 -**Example:** 479 -))) 431 +Example: 480 480 481 -((( 482 -(% style="color:red" %)AT+COMMAND1=11 01 1E D0,0 483 -))) 433 +AT+COMMAND1=11 01 1E D0,0 484 484 485 -((( 486 -(% style="color:red" %)AT+SEARCH1=1,1E 56 34 487 -))) 435 +AT+SEARCH1=1,1E 56 34 488 488 489 -((( 490 -(% style="color:red" %)AT+DATACUT1=0,2,1~~5 491 -))) 437 +AT+DATACUT1=0,2,1~~5 492 492 493 -((( 494 -(% style="color:red" %)Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49 495 -))) 439 +Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49 496 496 497 -((( 498 -(% style="color:red" %)String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49 499 -))) 441 +String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49 500 500 501 -((( 502 -(% style="color:red" %)Valid payload after DataCUT command: 2e 30 58 5f 36 503 -))) 443 +Valid payload after DataCUT command: 2e 30 58 5f 36 504 504 505 -[[image: 1653271763403-806.png]]445 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image018.png]] 506 506 507 -=== 3.3.4 Compose the uplink payload === 508 508 509 -((( 448 + 449 + 450 +1. 451 +11. 452 +111. Compose the uplink payload 453 + 510 510 Through AT+COMMANDx and AT+DATACUTx we got valid value from each RS485 commands, Assume these valid value are RETURN1, RETURN2, .., to RETURNx. The next step is how to compose the LoRa Uplink Payload by these RETURNs. The command is **AT+DATAUP.** 511 -))) 512 512 513 -((( 514 -(% style="color:#4f81bd" %)**Examples: AT+DATAUP=0** 515 -))) 516 516 517 -((( 518 -Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**A SIGNLE UPLINK**. 519 -))) 457 +**Examples: AT+DATAUP=0** 520 520 521 -((( 459 +Compose the uplink payload with value returns in sequence and send with **A SIGNLE UPLINK**. 460 + 522 522 Final Payload is 523 -))) 524 524 525 -((( 526 -(% style="color:#4f81bd" %)Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx 527 -))) 463 +Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx 528 528 529 -((( 530 530 Where PAYVER is defined by AT+PAYVER, below is an example screen shot. 531 -))) 532 532 533 -[[image: 1653272787040-634.png||height="515" width="719"]]467 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.png]] 534 534 535 -((( 536 -(% style="color:#4f81bd" %)**Examples: AT+DATAUP=1** 537 -))) 538 538 539 -((( 540 -Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**Multiply UPLINKs**. 541 -))) 542 542 543 -((( 471 +**Examples: AT+DATAUP=1** 472 + 473 +Compose the uplink payload with value returns in sequence and send with **Multiply UPLINKs**. 474 + 544 544 Final Payload is 545 -))) 546 546 547 -((( 548 -(% style="color:#4f81bd" %)Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA 549 -))) 477 +Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA 550 550 551 -1. ((( 552 -Battery Info (2 bytes): Battery voltage 553 -))) 554 -1. ((( 555 -PAYVER (1 byte): Defined by AT+PAYVER 556 -))) 557 -1. ((( 558 -PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling. 559 -))) 560 -1. ((( 561 -PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT) 562 -))) 563 -1. ((( 564 -DATA: Valid value: max 6 bytes(US915 version here, Notice*!) for each uplink so each uplink <= 11 bytes. For the last uplink, DATA will might less than 6 bytes 565 -))) 479 +1. Battery Info (2 bytes): Battery voltage 480 +1. PAYVER (1 byte): Defined by AT+PAYVER 481 +1. PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling. 482 +1. PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT) 483 +1. DATA: Valid value: max 6 bytes(US915 version here, [[Notice*!>>path:#max_byte]]) for each uplink so each uplink <= 11 bytes. For the last uplink, DATA will might less than 6 bytes 566 566 567 -[[image: 1653272817147-600.png||height="437" width="717"]]485 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image020.png]] 568 568 487 + 569 569 So totally there will be 3 uplinks for this sampling, each uplink includes 6 bytes DATA 570 570 571 -DATA1=RETURN1 Valid Value = (% style="background-color:#4f81bd; color:white" %)20 20 0a 33 90 41490 +DATA1=RETURN1 Valid Value = 20 20 0a 33 90 41 572 572 573 -DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= (% style="background-color:#4f81bd; color:white" %)02 aa 05 81 0a 20492 +DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= 02 aa 05 81 0a 20 574 574 575 -DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 = (%style="background-color:#4f81bd; color:white" %)20 20 20 2d 30494 +DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 = 20 20 20 2d 30 576 576 496 + 497 + 577 577 Below are the uplink payloads: 578 578 579 -[[image: 1653272901032-107.png]]500 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.png]] 580 580 581 -(% style="color:red" %)Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below: 582 582 503 +Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below: 504 + 583 583 ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink ( so 51 -5 = 46 max valid date) 584 584 585 585 * For AU915/AS923 bands, if UplinkDwell time=1, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date). ... ... @@ -588,121 +588,90 @@ 588 588 589 589 ~* For all other bands: max 51 bytes for each uplink ( so 51 -5 = 46 max valid date). 590 590 591 -=== 3.3.5 Uplink on demand === 592 592 593 -((( 514 + 515 +1. 516 +11. 517 +111. Uplink on demand 518 + 594 594 Except uplink periodically, RS485-BL is able to uplink on demand. The server sends downlink command to RS485-BL and RS485 will uplink data base on the command. 595 -))) 596 596 597 -((( 598 598 Downlink control command: 599 -))) 600 600 601 -((( 602 -**0x08 command**: Poll an uplink with current command set in RS485-BL. 603 -))) 523 +[[0x08 command>>path:#downlink_08]]: Poll an uplink with current command set in RS485-BL. 604 604 605 -((( 606 -**0xA8 command**: Send a command to RS485-BL and uplink the output from sensors. 607 -))) 525 +[[0xA8 command>>path:#downlink_A8]]: Send a command to RS485-BL and uplink the output from sensors. 608 608 609 -=== 3.3.6 Uplink on Interrupt === 610 610 611 -Put the interrupt sensor between 3.3v_out and GPIO ext. 612 612 613 -[[image:1653273818896-432.png]] 529 +1. 530 +11. 531 +111. Uplink on Interrupt 614 614 615 -((( 533 +Put the interrupt sensor between 3.3v_out and GPIO ext.[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image022.png]] 534 + 616 616 AT+INTMOD=0 Disable Interrupt 617 -))) 618 618 619 -((( 620 620 AT+INTMOD=1 Interrupt trigger by rising or falling edge. 621 -))) 622 622 623 -((( 624 624 AT+INTMOD=2 Interrupt trigger by falling edge. ( Default Value) 625 -))) 626 626 627 -((( 628 628 AT+INTMOD=3 Interrupt trigger by rising edge. 629 -))) 630 630 631 -== 3.4 Uplink Payload == 632 632 633 -(% border="1" style="background-color:#4f81bd; color:white; width:850px" %) 634 -|**Size(bytes)**|(% style="width:130px" %)**2**|(% style="width:93px" %)**1**|(% style="width:509px" %)**Length depends on the return from the commands** 635 -|Value|(% style="width:130px" %)((( 636 -((( 544 +1. 545 +11. Uplink Payload 546 + 547 +|**Size(bytes)**|**2**|**1**|**Length depends on the return from the commands** 548 +|Value|((( 637 637 Battery(mV) 638 -))) 639 639 640 -((( 641 641 & 642 -))) 643 643 644 -((( 645 645 Interrupt _Flag 646 -))) 647 -)))|(% style="width:93px" %)((( 554 +)))|((( 648 648 PAYLOAD_VER 649 649 650 650 651 -)))| (% style="width:509px" %)If the valid payload is too long and exceed the maximum support payload length in server, server will show payload not provided in the LoRaWAN server.558 +)))|If the valid payload is too long and exceed the maximum support payload length in server, server will show payload not provided in the LoRaWAN server. 652 652 653 653 Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors. 654 654 655 - (((562 + 656 656 function Decoder(bytes, port) { 657 -))) 658 658 659 -((( 660 660 ~/~/Payload Formats of RS485-BL Deceive 661 -))) 662 662 663 -((( 664 664 return { 665 -))) 666 666 667 -((( 668 668 ~/~/Battery,units:V 669 -))) 670 670 671 -((( 672 672 BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000, 673 -))) 674 674 675 -((( 676 676 ~/~/GPIO_EXTI 677 -))) 678 678 679 -((( 680 680 EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE", 681 -))) 682 682 683 -((( 684 684 ~/~/payload of version 685 -))) 686 686 687 -((( 688 688 Pay_ver:bytes[2], 689 -))) 690 690 691 -((( 692 692 }; 693 -))) 694 694 695 -((( 696 696 } 697 -))) 698 698 699 -((( 585 + 586 + 587 + 588 + 589 + 590 + 700 700 TTN V3 uplink screen shot. 701 -))) 702 702 703 -[[image: 1653274001211-372.png||height="192" width="732"]]593 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]] 704 704 705 -== 3.5 Configure RS485-BL via AT or Downlink == 595 +1. 596 +11. Configure RS485-BL via AT or Downlink 706 706 707 707 User can configure RS485-BL via [[AT Commands >>path:#_Using_the_AT]]or LoRaWAN Downlink Commands 708 708 ... ... @@ -712,15 +712,15 @@ 712 712 713 713 * **Sensor Related Commands**: These commands are special designed for RS485-BL. User can see these commands below: 714 714 715 -1. 716 -11. 606 +1. 607 +11. 717 717 111. Common Commands: 718 718 719 719 They should be available for each of Dragino Sensors, such as: change uplink interval, reset device. For firmware v1.3, user can find what common commands it supports: [[http:~~/~~/wiki.dragino.com/index.php?title=End_Device_AT_Commands_and_Downlink_Commands>>url:http://wiki.dragino.com/index.php?title=End_Device_AT_Commands_and_Downlink_Commands]] 720 720 721 721 722 -1. 723 -11. 613 +1. 614 +11. 724 724 111. Sensor related commands: 725 725 726 726 ==== Choose Device Type (RS485 or TTL) ==== ... ... @@ -1026,13 +1026,13 @@ 1026 1026 1027 1027 1028 1028 1029 -1. 920 +1. 1030 1030 11. Buttons 1031 1031 1032 1032 |**Button**|**Feature** 1033 1033 |**RST**|Reboot RS485-BL 1034 1034 1035 -1. 926 +1. 1036 1036 11. +3V3 Output 1037 1037 1038 1038 RS485-BL has a Controllable +3V3 output, user can use this output to power external sensor. ... ... @@ -1050,7 +1050,7 @@ 1050 1050 By default, the AT+3V3T=0. This is a special case, means the +3V3 output is always on at any time 1051 1051 1052 1052 1053 -1. 944 +1. 1054 1054 11. +5V Output 1055 1055 1056 1056 RS485-BL has a Controllable +5V output, user can use this output to power external sensor. ... ... @@ -1070,13 +1070,13 @@ 1070 1070 1071 1071 1072 1072 1073 -1. 964 +1. 1074 1074 11. LEDs 1075 1075 1076 1076 |**LEDs**|**Feature** 1077 1077 |**LED1**|Blink when device transmit a packet. 1078 1078 1079 -1. 970 +1. 1080 1080 11. Switch Jumper 1081 1081 1082 1082 |**Switch Jumper**|**Feature** ... ... @@ -1122,7 +1122,7 @@ 1122 1122 1123 1123 1124 1124 1125 -1. 1016 +1. 1126 1126 11. Common AT Command Sequence 1127 1127 111. Multi-channel ABP mode (Use with SX1301/LG308) 1128 1128 ... ... @@ -1141,8 +1141,8 @@ 1141 1141 1142 1142 ATZ 1143 1143 1144 -1. 1145 -11. 1035 +1. 1036 +11. 1146 1146 111. Single-channel ABP mode (Use with LG01/LG02) 1147 1147 1148 1148 AT+FDR Reset Parameters to Factory Default, Keys Reserve ... ... @@ -1217,7 +1217,7 @@ 1217 1217 [[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image035.png]] [[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image036.png]] 1218 1218 1219 1219 1220 -1. 1111 +1. 1221 1221 11. How to change the LoRa Frequency Bands/Region? 1222 1222 1223 1223 User can follow the introduction for [[how to upgrade image>>path:#upgrade_image]]. When download the images, choose the required image file for download. ... ... @@ -1224,7 +1224,7 @@ 1224 1224 1225 1225 1226 1226 1227 -1. 1118 +1. 1228 1228 11. How many RS485-Slave can RS485-BL connects? 1229 1229 1230 1230 The RS485-BL can support max 32 RS485 devices. Each uplink command of RS485-BL can support max 16 different RS485 command. So RS485-BL can support max 16 RS485 devices pre-program in the device for uplink. For other devices no pre-program, user can use the [[downlink message (type code 0xA8) to poll their info>>path:#downlink_A8]]. ... ... @@ -1241,7 +1241,7 @@ 1241 1241 1242 1242 1243 1243 1244 -1. 1135 +1. 1245 1245 11. Why I can’t join TTN V3 in US915 /AU915 bands? 1246 1246 1247 1247 It might about the channels mapping. Please see for detail.
- 1652954654347-831.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -138.7 KB - Content
- 1653271044481-711.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -27.8 KB - Content
- 1653271276735-972.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -26.6 KB - Content
- 1653271581490-837.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -138.7 KB - Content
- 1653271648378-342.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -131.4 KB - Content
- 1653271657255-576.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -142.6 KB - Content
- 1653271763403-806.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -27.7 KB - Content
- 1653272787040-634.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -294.0 KB - Content
- 1653272817147-600.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -143.3 KB - Content
- 1653272901032-107.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -197.8 KB - Content
- 1653273818896-432.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -31.6 KB - Content
- 1653274001211-372.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -91.4 KB - Content