Skip to Content
Last modified by Xiaoling on 2025/04/23 15:57
From version 29.11
edited by Xiaoling
on 2022/06/01 18:01
Change comment: There is no comment for this version
To version 15.3
edited by Xiaoling
on 2022/05/19 17:47
Change comment: There is no comment for this version

Summary

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 ==
... ... @@ -113,13 +113,10 @@
113 113  * Smart Cities
114 114  * Smart Factory
115 115  
116 -
117 -
118 118  == 1.5 Firmware Change log ==
119 119  
120 120  [[RS485-BL Image files – Download link and Change log>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/RS485-BL/Firmware/||style="background-color: rgb(255, 255, 255);"]]
121 121  
122 -
123 123  == 1.6 Hardware Change log ==
124 124  
125 125  (((
... ... @@ -146,8 +146,6 @@
146 146  
147 147  (((
148 148  Release version ​​​​​
149 -
150 -
151 151  )))
152 152  
153 153  = 2. Pin mapping and Power ON Device =
... ... @@ -161,7 +161,6 @@
161 161  
162 162  The Left TXD and RXD are TTL interface for external sensor. TTL level is controlled by 3.3/5v Jumper.
163 163  
164 -
165 165  = 3. Operation Mode =
166 166  
167 167  == 3.1 How it works? ==
... ... @@ -168,8 +168,6 @@
168 168  
169 169  (((
170 170  The RS485-BL is configured as LoRaWAN OTAA Class A 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-BL. It will auto join the network via OTAA.
171 -
172 -
173 173  )))
174 174  
175 175  == 3.2 Example to join LoRaWAN network ==
... ... @@ -230,188 +230,143 @@
230 230  
231 231  [[image:1652953568895-172.png||height="232" width="724"]]
232 232  
233 -== 3.3 Configure Commands to read data ==
234 234  
235 -(((
236 -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>>||anchor="H3.5ConfigureRS485-BLviaATorDownlink"]] Command to configure how RS485-BL should read the sensor and how to handle the return from RS485 or TTL sensors.
237 237  
238 -
239 -)))
240 240  
241 -=== 3.3.1 onfigure UART settings for RS485 or TTL communication ===
225 +1.
226 +11. Configure Commands to read data
242 242  
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 +
231 +1.
232 +11.
233 +111. Configure UART settings for RS485 or TTL communication
234 +
243 243  RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect.
244 244  
245 -**~1. RS485-MODBUS mode:**
237 +1. RS485-MODBUS mode:
246 246  
247 247  AT+MOD=1 ~/~/ Support RS485-MODBUS type sensors. User can connect multiply RS485 , Modbus sensors to the A / B pins.
248 248  
249 -**2. TTL mode:**
250 250  
242 +1. TTL mode:
243 +
251 251  AT+MOD=2 ~/~/ Support TTL Level sensors, User can connect one TTL Sensor to the TXD/RXD/GND pins.
252 252  
246 +
253 253  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.
254 254  
255 -(% border="1" style="background-color:#ffffcc; color:green; width:795px" %)
256 -|(((
257 -**AT Commands**
258 -)))|(% style="width:285px" %)(((
259 -**Description**
260 -)))|(% style="width:347px" %)(((
261 -**Example**
262 -)))
263 -|(((
264 -AT+BAUDR
265 -)))|(% style="width:285px" %)(((
266 -Set the baud rate (for RS485 connection). Default Value is: 9600.
267 -)))|(% style="width:347px" %)(((
268 -(((
249 +
250 +|**AT Commands**|**Description**|**Example**
251 +|AT+BAUDR|Set the baud rate (for RS485 connection). Default Value is: 9600.|(((
269 269  AT+BAUDR=9600
270 -)))
271 271  
272 -(((
273 273  Options: (1200,2400,4800,14400,19200,115200)
274 274  )))
275 -)))
276 -|(((
277 -AT+PARITY
278 -)))|(% style="width:285px" %)(((
279 -(((
256 +|AT+PARITY|(((
280 280  Set UART parity (for RS485 connection)
281 -)))
282 282  
283 -(((
284 284  Default Value is: no parity.
285 -)))
286 -)))|(% style="width:347px" %)(((
287 -(((
260 +)))|(((
288 288  AT+PARITY=0
289 -)))
290 290  
291 -(((
292 292  Option: 0: no parity, 1: odd parity, 2: even parity
293 293  )))
294 -)))
295 -|(((
296 -AT+STOPBIT
297 -)))|(% style="width:285px" %)(((
298 -(((
265 +|AT+STOPBIT|(((
299 299  Set serial stopbit (for RS485 connection)
300 -)))
301 301  
302 -(((
303 303  Default Value is: 1bit.
304 -)))
305 -)))|(% style="width:347px" %)(((
306 -(((
269 +)))|(((
307 307  AT+STOPBIT=0 for 1bit
308 -)))
309 309  
310 -(((
311 311  AT+STOPBIT=1 for 1.5 bit
312 -)))
313 313  
314 -(((
315 315  AT+STOPBIT=2 for 2 bits
316 316  )))
317 -)))
318 318  
319 -=== 3.3.2 Configure sensors ===
320 320  
321 -(((
322 -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**.
323 -)))
324 324  
325 -(((
326 -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.
327 -)))
328 328  
329 -(% border="1" style="background-color:#ffffcc; color:green; width:806px" %)
330 -|**AT Commands**|(% style="width:418px" %)**Description**|(% style="width:256px" %)**Example**
331 -|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|(((
332 332  This command is used to configure the RS485/TTL devices; they won’t be used during sampling.
333 333  
334 -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
335 335  
336 -mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
337 -)))|(% style="width:256px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
295 +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
338 338  
339 339  Detail of AT+CFGDEV command see [[AT+CFGDEV detail>>path:#AT_CFGDEV]].
340 340  
341 -=== 3.3.3 Configure read commands for each sampling ===
342 342  
343 -(((
301 +
302 +
303 +
304 +1.
305 +11.
306 +111. Configure read commands for each sampling
307 +
344 344  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.
345 -)))
346 346  
347 -(((
310 +
348 348  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.
349 -)))
350 350  
351 -(((
313 +
352 352  To save the LoRaWAN network bandwidth, we might need to read data from different sensors and combine their valid value into a short payload.
353 -)))
354 354  
355 -(((
316 +
356 356  This section describes how to achieve above goals.
357 -)))
358 358  
359 -(((
319 +
360 360  During each sampling, the RS485-BL can support 15 commands to read sensors. And combine the return to one or several uplink payloads.
361 -)))
362 362  
363 -(((
322 +
364 364  **Command from RS485-BL to Sensor:**
365 -)))
366 366  
367 -(((
368 368  RS485-BL can send out pre-set max 15 strings via **AT+COMMAD1**, **ATCOMMAND2**,…, to **AT+COMMANDF** . All commands are of same grammar.
369 -)))
370 370  
371 -(((
327 +
372 372  **Handle return from sensors to RS485-BL**:
373 -)))
374 374  
375 -(((
376 376  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**
377 -)))
378 378  
379 -* (((
380 -**AT+DATACUT**
381 -)))
382 382  
383 -(((
333 +* **AT+DATACUT**
334 +
384 384  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.
385 -)))
386 386  
387 -* (((
388 -**AT+SEARCH**
389 -)))
390 390  
391 -(((
338 +* **AT+SEARCH**
339 +
392 392  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.
393 -)))
394 394  
395 -(((
342 +
396 396  **Define wait timeout:**
397 -)))
398 398  
399 -(((
400 400  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
401 -)))
402 402  
403 -(((
347 +
404 404  After we got the valid value from each RS485 commands, we need to combine them together with the command **AT+DATAUP**.
405 -)))
406 406  
350 +
407 407  **Examples:**
408 408  
409 409  Below are examples for the how above AT Commands works.
410 410  
355 +
411 411  **AT+COMMANDx : **This command will be sent to RS485/TTL devices during each sampling, Max command length is 14 bytes. The grammar is:
412 412  
413 -(% border="1" class="table-bordered" style="background-color:#4f81bd; color:white; width:501px" %)
414 -|(% style="width:498px" %)(((
358 +|(((
415 415  **AT+COMMANDx=xx xx xx xx xx xx xx xx xx xx xx xx,m**
416 416  
417 417  **xx xx xx xx xx xx xx xx xx xx xx xx: The RS485 command to be sent**
... ... @@ -423,38 +423,41 @@
423 423  
424 424  In the RS485-BL, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
425 425  
370 +
426 426  **AT+SEARCHx**: This command defines how to handle the return from AT+COMMANDx.
427 427  
428 -(% border="1" class="table-bordered" style="background-color:#4f81bd; color:white; width:580px" %)
429 -|(% style="width:577px" %)(((
373 +|(((
430 430  **AT+SEARCHx=aa,xx xx xx xx xx**
431 431  
432 432  * **aa: 1: prefix match mode; 2: prefix and suffix match mode**
433 433  * **xx xx xx xx xx: match string. Max 5 bytes for prefix and 5 bytes for suffix**
378 +
379 +
434 434  )))
435 435  
436 -**Examples:**
382 +Examples:
437 437  
438 438  1. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
439 439  
440 440  If we set AT+SEARCH1=1,1E 56 34.      (max 5 bytes for prefix)
441 441  
442 -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
443 443  
444 -[[image:1653271044481-711.png]]
390 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image013.png]]
445 445  
392 +
446 446  1. For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
447 447  
448 448  If we set AT+SEARCH1=2, 1E 56 34+31 00 49
449 449  
450 -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
451 451  
452 -[[image:1653271276735-972.png]]
399 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image014.png]]
453 453  
401 +
454 454  **AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes.
455 455  
456 -(% style="background-color:#4f81bd; color:white; width:729px" %)
457 -|(% style="width:726px" %)(((
404 +|(((
458 458  **AT+DATACUTx=a,b,c**
459 459  
460 460  * **a: length for the return of AT+COMMAND**
... ... @@ -466,130 +466,95 @@
466 466  
467 467  * Grab bytes:
468 468  
469 -[[image:1653271581490-837.png||height="313" width="722"]]
416 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image015.png]]
470 470  
471 471  * Grab a section.
472 472  
473 -[[image:1653271648378-342.png||height="326" width="720"]]
420 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image016.png]]
474 474  
475 475  * Grab different sections.
476 476  
477 -[[image:1653271657255-576.png||height="305" width="730"]]
424 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image017.png]]
478 478  
479 -(((
480 -(% style="color:red" %)**Note:**
481 -)))
482 482  
483 -(((
427 +Note:
428 +
484 484  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.
485 -)))
486 486  
487 -(((
488 -**Example:**
489 -)))
431 +Example:
490 490  
491 -(((
492 -(% style="color:red" %)AT+COMMAND1=11 01 1E D0,0
493 -)))
433 +AT+COMMAND1=11 01 1E D0,0
494 494  
495 -(((
496 -(% style="color:red" %)AT+SEARCH1=1,1E 56 34
497 -)))
435 +AT+SEARCH1=1,1E 56 34
498 498  
499 -(((
500 -(% style="color:red" %)AT+DATACUT1=0,2,1~~5
501 -)))
437 +AT+DATACUT1=0,2,1~~5
502 502  
503 -(((
504 -(% style="color:red" %)Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
505 -)))
439 +Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
506 506  
507 -(((
508 -(% style="color:red" %)String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
509 -)))
441 +String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
510 510  
511 -(((
512 -(% style="color:red" %)Valid payload after DataCUT command: 2e 30 58 5f 36
513 -)))
443 +Valid payload after DataCUT command: 2e 30 58 5f 36
514 514  
515 -[[image:1653271763403-806.png]]
445 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image018.png]]
516 516  
517 -=== 3.3.4 Compose the uplink payload ===
518 518  
519 -(((
448 +
449 +
450 +1.
451 +11.
452 +111. Compose the uplink payload
453 +
520 520  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.**
521 -)))
522 522  
523 -(((
524 -(% style="color:#4f81bd" %)**Examples: AT+DATAUP=0**
525 -)))
526 526  
527 -(((
528 -Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**A SIGNLE UPLINK**.
529 -)))
457 +**Examples: AT+DATAUP=0**
530 530  
531 -(((
459 +Compose the uplink payload with value returns in sequence and send with **A SIGNLE UPLINK**.
460 +
532 532  Final Payload is
533 -)))
534 534  
535 -(((
536 -(% style="color:#4f81bd" %)Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx
537 -)))
463 +Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx
538 538  
539 -(((
540 540  Where PAYVER is defined by AT+PAYVER, below is an example screen shot.
541 -)))
542 542  
543 -[[image:1653272787040-634.png||height="515" width="719"]]
467 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.png]]
544 544  
545 -(((
546 -(% style="color:#4f81bd" %)**Examples: AT+DATAUP=1**
547 -)))
548 548  
549 -(((
550 -Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**Multiply UPLINKs**.
551 -)))
552 552  
553 -(((
471 +**Examples: AT+DATAUP=1**
472 +
473 +Compose the uplink payload with value returns in sequence and send with **Multiply UPLINKs**.
474 +
554 554  Final Payload is
555 -)))
556 556  
557 -(((
558 -(% style="color:#4f81bd" %)Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA
559 -)))
477 +Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA
560 560  
561 -1. (((
562 -Battery Info (2 bytes): Battery voltage
563 -)))
564 -1. (((
565 -PAYVER (1 byte): Defined by AT+PAYVER
566 -)))
567 -1. (((
568 -PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling.
569 -)))
570 -1. (((
571 -PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
572 -)))
573 -1. (((
574 -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
575 -)))
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
576 576  
577 -[[image:1653272817147-600.png||height="437" width="717"]]
485 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image020.png]]
578 578  
487 +
579 579  So totally there will be 3 uplinks for this sampling, each uplink includes 6 bytes DATA
580 580  
581 -DATA1=RETURN1 Valid Value = (% style="background-color:#4f81bd; color:white" %) 20 20 0a 33 90 41
490 +DATA1=RETURN1 Valid Value = 20 20 0a 33 90 41
582 582  
583 -DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= (% style="background-color:#4f81bd; color:white" %)02 aa 05 81 0a 20
492 +DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= 02 aa 05 81 0a 20
584 584  
585 -DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 =(% style="background-color:#4f81bd; color:white" %) 20 20 20 2d 30
494 +DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 = 20 20 20 2d 30
586 586  
496 +
497 +
587 587  Below are the uplink payloads:
588 588  
589 -[[image:1653272901032-107.png]]
500 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.png]]
590 590  
591 -(% style="color:red" %)Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:
592 592  
503 +Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:
504 +
593 593   ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink ( so 51 -5 = 46 max valid date)
594 594  
595 595   * For AU915/AS923 bands, if UplinkDwell time=1, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date).
... ... @@ -598,121 +598,90 @@
598 598  
599 599   ~* For all other bands: max 51 bytes for each uplink  ( so 51 -5 = 46 max valid date).
600 600  
601 -=== 3.3.5 Uplink on demand ===
602 602  
603 -(((
514 +
515 +1.
516 +11.
517 +111. Uplink on demand
518 +
604 604  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.
605 -)))
606 606  
607 -(((
608 608  Downlink control command:
609 -)))
610 610  
611 -(((
612 -**0x08 command**: Poll an uplink with current command set in RS485-BL.
613 -)))
523 +[[0x08 command>>path:#downlink_08]]: Poll an uplink with current command set in RS485-BL.
614 614  
615 -(((
616 -**0xA8 command**: Send a command to RS485-BL and uplink the output from sensors.
617 -)))
525 +[[0xA8 command>>path:#downlink_A8]]: Send a command to RS485-BL and uplink the output from sensors.
618 618  
619 -=== 3.3.6 Uplink on Interrupt ===
620 620  
621 -Put the interrupt sensor between 3.3v_out and GPIO ext.
622 622  
623 -[[image:1653273818896-432.png]]
529 +1.
530 +11.
531 +111. Uplink on Interrupt
624 624  
625 -(((
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 +
626 626  AT+INTMOD=0  Disable Interrupt
627 -)))
628 628  
629 -(((
630 630  AT+INTMOD=1  Interrupt trigger by rising or falling edge.
631 -)))
632 632  
633 -(((
634 634  AT+INTMOD=2  Interrupt trigger by falling edge. ( Default Value)
635 -)))
636 636  
637 -(((
638 638  AT+INTMOD=3  Interrupt trigger by rising edge.
639 -)))
640 640  
641 -== 3.4 Uplink Payload ==
642 642  
643 -(% border="1" style="background-color:#4f81bd; color:white; width:850px" %)
644 -|**Size(bytes)**|(% style="width:130px" %)**2**|(% style="width:93px" %)**1**|(% style="width:509px" %)**Length depends on the return from the commands**
645 -|Value|(% style="width:130px" %)(((
646 -(((
544 +1.
545 +11. Uplink Payload
546 +
547 +|**Size(bytes)**|**2**|**1**|**Length depends on the return from the commands**
548 +|Value|(((
647 647  Battery(mV)
648 -)))
649 649  
650 -(((
651 651  &
652 -)))
653 653  
654 -(((
655 655  Interrupt _Flag
656 -)))
657 -)))|(% style="width:93px" %)(((
554 +)))|(((
658 658  PAYLOAD_VER
659 659  
660 660  
661 -)))|(% 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.
662 662  
663 663  Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors.
664 664  
665 -(((
562 +
666 666  function Decoder(bytes, port) {
667 -)))
668 668  
669 -(((
670 670  ~/~/Payload Formats of RS485-BL Deceive
671 -)))
672 672  
673 -(((
674 674  return {
675 -)))
676 676  
677 -(((
678 678   ~/~/Battery,units:V
679 -)))
680 680  
681 -(((
682 682   BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000,
683 -)))
684 684  
685 -(((
686 686   ~/~/GPIO_EXTI 
687 -)))
688 688  
689 -(((
690 690   EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE",
691 -)))
692 692  
693 -(((
694 694   ~/~/payload of version
695 -)))
696 696  
697 -(((
698 698   Pay_ver:bytes[2],
699 -)))
700 700  
701 -(((
702 702   };
703 -)))
704 704  
705 -(((
706 706   }
707 -)))
708 708  
709 -(((
585 +
586 +
587 +
588 +
589 +
590 +
710 710  TTN V3 uplink screen shot.
711 -)))
712 712  
713 -[[image:1653274001211-372.png||height="192" width="732"]]
593 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]
714 714  
715 -== 3.5 Configure RS485-BL via AT or Downlink ==
595 +1.
596 +11. Configure RS485-BL via AT or Downlink
716 716  
717 717  User can configure RS485-BL via [[AT Commands >>path:#_​Using_the_AT]]or LoRaWAN Downlink Commands
718 718  
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