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