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