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