Skip to Content
Last modified by Xiaoling on 2025/04/23 15:57
From version 29.36
edited by Xiaoling
on 2022/06/02 08:59
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 ==
... ... @@ -25,19 +25,19 @@
25 25  )))
26 26  
27 27  (((
28 -The Dragino RS485-BL is a (% style="color:blue" %)**RS485 / UART to LoRaWAN Converter**(%%) for Internet of Things solutions. User can connect RS485 or UART sensor to RS485-BL converter, and configure RS485-BL to periodically read sensor data and upload via LoRaWAN network to IoT server.
25 +The Dragino RS485-BL is a **RS485 / UART to LoRaWAN Converter** for Internet of Things solutions. User can connect RS485 or UART sensor to RS485-BL converter, and configure RS485-BL to periodically read sensor data and upload via LoRaWAN network to IoT server.
29 29  )))
30 30  
31 31  (((
32 -RS485-BL can interface to RS485 sensor, 3.3v/5v UART sensor or interrupt sensor. RS485-BL provides (% style="color:blue" %)**a 3.3v output**(%%) and** (% style="color:blue" %)a 5v output(%%)** to power external sensors. Both output voltages are controllable to minimize the total system power consumption.
29 +RS485-BL can interface to RS485 sensor, 3.3v/5v UART sensor or interrupt sensor. RS485-BL provides **a 3.3v output** and** a 5v output** to power external sensors. Both output voltages are controllable to minimize the total system power consumption.
33 33  )))
34 34  
35 35  (((
36 -RS485-BL is IP67 (% style="color:blue" %)**waterproof**(%%) and powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), it is designed for long term use for several years.
33 +RS485-BL is IP67 **waterproof** and powered by **8500mAh Li-SOCI2 battery**, it is designed for long term use for several years.
37 37  )))
38 38  
39 39  (((
40 -RS485-BL runs standard (% style="color:blue" %)**LoRaWAN 1.0.3 in Class A**(%%). It can reach long transfer range and easy to integrate with LoRaWAN compatible gateway and IoT server.
37 +RS485-BL runs standard **LoRaWAN 1.0.3 in Class A**. It can reach long transfer range and easy to integrate with LoRaWAN compatible gateway and IoT server.
41 41  )))
42 42  
43 43  (((
... ... @@ -54,11 +54,8 @@
54 54  
55 55  [[image:1652953304999-717.png||height="424" width="733"]]
56 56  
57 -
58 -
59 59  == 1.2 Specifications ==
60 60  
61 -
62 62  **Hardware System:**
63 63  
64 64  * STM32L072CZT6 MCU
... ... @@ -65,6 +65,8 @@
65 65  * SX1276/78 Wireless Chip 
66 66  * Power Consumption (exclude RS485 device):
67 67  ** Idle: 6uA@3.3v
62 +
63 +*
68 68  ** 20dB Transmit: 130mA@3.3v
69 69  
70 70  **Interface for Model:**
... ... @@ -118,12 +118,9 @@
118 118  
119 119  [[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);"]]
120 120  
121 -
122 122  == 1.6 Hardware Change log ==
123 123  
124 124  (((
125 -
126 -
127 127  v1.4
128 128  )))
129 129  
... ... @@ -147,8 +147,6 @@
147 147  
148 148  (((
149 149  Release version ​​​​​
150 -
151 -
152 152  )))
153 153  
154 154  = 2. Pin mapping and Power ON Device =
... ... @@ -162,7 +162,6 @@
162 162  
163 163  The Left TXD and RXD are TTL interface for external sensor. TTL level is controlled by 3.3/5v Jumper.
164 164  
165 -
166 166  = 3. Operation Mode =
167 167  
168 168  == 3.1 How it works? ==
... ... @@ -169,8 +169,6 @@
169 169  
170 170  (((
171 171  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.
172 -
173 -
174 174  )))
175 175  
176 176  == 3.2 Example to join LoRaWAN network ==
... ... @@ -206,6 +206,8 @@
206 206  )))
207 207  
208 208  
197 +
198 +
209 209  [[image:image-20220519174512-1.png]]
210 210  
211 211  [[image:image-20220519174512-2.png||height="328" width="731"]]
... ... @@ -230,190 +230,142 @@
230 230  [[image:1652953568895-172.png||height="232" width="724"]]
231 231  
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 -)))
225 +1.
226 +11. Configure Commands to read data
240 240  
241 -=== 3.3.1 onfigure UART settings for RS485 or TTL communication ===
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.
242 242  
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 319  
320 -=== 3.3.2 Configure sensors ===
321 321  
322 -(((
323 -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**.
324 -)))
325 325  
326 -(((
327 -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.
328 -)))
280 +1.
281 +11.
282 +111. Configure sensors
329 329  
330 -(% border="1" style="background-color:#ffffcc; color:green; width:806px" %)
331 -|**AT Commands**|(% style="width:418px" %)**Description**|(% style="width:256px" %)**Example**
332 -|AT+CFGDEV|(% style="width:418px" %)(((
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|(((
333 333  This command is used to configure the RS485/TTL devices; they won’t be used during sampling.
334 334  
335 -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
336 336  
337 -mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
338 -)))|(% 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
339 339  
340 -Detail of AT+CFGDEV command see [[AT+CFGDEV detail>>||anchor="HRS485DebugCommand28AT2BCFGDEV29"]].
298 +Detail of AT+CFGDEV command see [[AT+CFGDEV detail>>path:#AT_CFGDEV]].
341 341  
342 342  
343 -=== 3.3.3 Configure read commands for each sampling ===
344 344  
345 -(((
302 +
303 +
304 +1.
305 +11.
306 +111. Configure read commands for each sampling
307 +
346 346  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.
347 -)))
348 348  
349 -(((
310 +
350 350  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.
351 -)))
352 352  
353 -(((
313 +
354 354  To save the LoRaWAN network bandwidth, we might need to read data from different sensors and combine their valid value into a short payload.
355 -)))
356 356  
357 -(((
316 +
358 358  This section describes how to achieve above goals.
359 -)))
360 360  
361 -(((
319 +
362 362  During each sampling, the RS485-BL can support 15 commands to read sensors. And combine the return to one or several uplink payloads.
363 -)))
364 364  
365 -(((
322 +
366 366  **Command from RS485-BL to Sensor:**
367 -)))
368 368  
369 -(((
370 370  RS485-BL can send out pre-set max 15 strings via **AT+COMMAD1**, **ATCOMMAND2**,…, to **AT+COMMANDF** . All commands are of same grammar.
371 -)))
372 372  
373 -(((
327 +
374 374  **Handle return from sensors to RS485-BL**:
375 -)))
376 376  
377 -(((
378 378  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**
379 -)))
380 380  
381 -* (((
382 -**AT+DATACUT**
383 -)))
384 384  
385 -(((
333 +* **AT+DATACUT**
334 +
386 386  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.
387 -)))
388 388  
389 -* (((
390 -**AT+SEARCH**
391 -)))
392 392  
393 -(((
338 +* **AT+SEARCH**
339 +
394 394  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.
395 -)))
396 396  
397 -(((
342 +
398 398  **Define wait timeout:**
399 -)))
400 400  
401 -(((
402 402  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
403 -)))
404 404  
405 -(((
347 +
406 406  After we got the valid value from each RS485 commands, we need to combine them together with the command **AT+DATAUP**.
407 -)))
408 408  
350 +
409 409  **Examples:**
410 410  
411 411  Below are examples for the how above AT Commands works.
412 412  
355 +
413 413  **AT+COMMANDx : **This command will be sent to RS485/TTL devices during each sampling, Max command length is 14 bytes. The grammar is:
414 414  
415 -(% border="1" class="table-bordered" style="background-color:#4f81bd; color:white; width:501px" %)
416 -|(% style="width:498px" %)(((
358 +|(((
417 417  **AT+COMMANDx=xx xx xx xx xx xx xx xx xx xx xx xx,m**
418 418  
419 419  **xx xx xx xx xx xx xx xx xx xx xx xx: The RS485 command to be sent**
... ... @@ -425,38 +425,41 @@
425 425  
426 426  In the RS485-BL, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
427 427  
370 +
428 428  **AT+SEARCHx**: This command defines how to handle the return from AT+COMMANDx.
429 429  
430 -(% border="1" class="table-bordered" style="background-color:#4f81bd; color:white; width:580px" %)
431 -|(% style="width:577px" %)(((
373 +|(((
432 432  **AT+SEARCHx=aa,xx xx xx xx xx**
433 433  
434 434  * **aa: 1: prefix match mode; 2: prefix and suffix match mode**
435 435  * **xx xx xx xx xx: match string. Max 5 bytes for prefix and 5 bytes for suffix**
378 +
379 +
436 436  )))
437 437  
438 -**Examples:**
382 +Examples:
439 439  
440 -1）For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
384 +1. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
441 441  
442 442  If we set AT+SEARCH1=1,1E 56 34.      (max 5 bytes for prefix)
443 443  
444 -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
445 445  
446 -[[image:1653271044481-711.png]]
390 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image013.png]]
447 447  
448 -2）For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
449 449  
393 +1. For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
394 +
450 450  If we set AT+SEARCH1=2, 1E 56 34+31 00 49
451 451  
452 -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
453 453  
454 -[[image:1653271276735-972.png]]
399 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image014.png]]
455 455  
401 +
456 456  **AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes.
457 457  
458 -(% style="background-color:#4f81bd; color:white; width:729px" %)
459 -|(% style="width:726px" %)(((
404 +|(((
460 460  **AT+DATACUTx=a,b,c**
461 461  
462 462  * **a: length for the return of AT+COMMAND**
... ... @@ -464,143 +464,98 @@
464 464  * **c: define the position for valid value.  **
465 465  )))
466 466  
467 -**Examples:**
412 +Examples:
468 468  
469 469  * Grab bytes:
470 470  
471 -[[image:1653271581490-837.png||height="313" width="722"]]
416 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image015.png]]
472 472  
473 -
474 474  * Grab a section.
475 475  
476 -[[image:1653271648378-342.png||height="326" width="720"]]
420 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image016.png]]
477 477  
478 -
479 479  * Grab different sections.
480 480  
481 -[[image:1653271657255-576.png||height="305" width="730"]]
424 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image017.png]]
482 482  
483 -(((
484 -(% style="color:red" %)**Note:**
485 -)))
486 486  
487 -(((
427 +Note:
428 +
488 488  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.
489 -)))
490 490  
491 -(((
492 -**Example:**
493 -)))
431 +Example:
494 494  
495 -(((
496 -(% style="color:red" %)AT+COMMAND1=11 01 1E D0,0
497 -)))
433 +AT+COMMAND1=11 01 1E D0,0
498 498  
499 -(((
500 -(% style="color:red" %)AT+SEARCH1=1,1E 56 34
501 -)))
435 +AT+SEARCH1=1,1E 56 34
502 502  
503 -(((
504 -(% style="color:red" %)AT+DATACUT1=0,2,1~~5
505 -)))
437 +AT+DATACUT1=0,2,1~~5
506 506  
507 -(((
508 -(% style="color:red" %)Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
509 -)))
439 +Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
510 510  
511 -(((
512 -(% style="color:red" %)String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
513 -)))
441 +String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
514 514  
515 -(((
516 -(% style="color:red" %)Valid payload after DataCUT command: 2e 30 58 5f 36
517 -)))
443 +Valid payload after DataCUT command: 2e 30 58 5f 36
518 518  
519 -[[image:1653271763403-806.png]]
445 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image018.png]]
520 520  
521 521  
522 -=== 3.3.4 Compose the uplink payload ===
523 523  
524 -(((
449 +
450 +1.
451 +11.
452 +111. Compose the uplink payload
453 +
525 525  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.**
526 -)))
527 527  
528 -(((
529 -(% style="color:#037691" %)**Examples: AT+DATAUP=0**
530 -)))
531 531  
532 -(((
533 -Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**A SIGNLE UPLINK**.
534 -)))
457 +**Examples: AT+DATAUP=0**
535 535  
536 -(((
459 +Compose the uplink payload with value returns in sequence and send with **A SIGNLE UPLINK**.
460 +
537 537  Final Payload is
538 -)))
539 539  
540 -(((
541 -(% style="color:#4f81bd" %)**Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx**
542 -)))
463 +Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx
543 543  
544 -(((
545 545  Where PAYVER is defined by AT+PAYVER, below is an example screen shot.
546 -)))
547 547  
548 -[[image:1653272787040-634.png||height="515" width="719"]]
467 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.png]]
549 549  
550 550  
551 551  
552 -(((
553 -(% style="color:#037691" %)**Examples: AT+DATAUP=1**
471 +**Examples: AT+DATAUP=1**
554 554  
555 -
556 -)))
473 +Compose the uplink payload with value returns in sequence and send with **Multiply UPLINKs**.
557 557  
558 -(((
559 -Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**Multiply UPLINKs**.
560 -)))
561 -
562 -(((
563 563  Final Payload is
564 -)))
565 565  
566 -(((
567 -(% style="color:#4f81bd" %)**Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA**
568 -)))
477 +Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA
569 569  
570 -1. (((
571 -Battery Info (2 bytes): Battery voltage
572 -)))
573 -1. (((
574 -PAYVER (1 byte): Defined by AT+PAYVER
575 -)))
576 -1. (((
577 -PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling.
578 -)))
579 -1. (((
580 -PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
581 -)))
582 -1. (((
583 -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
584 -)))
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
585 585  
586 -[[image:1653272817147-600.png||height="437" width="717"]]
485 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image020.png]]
587 587  
487 +
588 588  So totally there will be 3 uplinks for this sampling, each uplink includes 6 bytes DATA
589 589  
490 +DATA1=RETURN1 Valid Value = 20 20 0a 33 90 41
590 590  
591 -DATA1=RETURN1 Valid Value = (% style="background-color:#4f81bd; color:white" %) 20 20 0a 33 90 41
492 +DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= 02 aa 05 81 0a 20
592 592  
593 -DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= (% style="background-color:#4f81bd; color:white" %)02 aa 05 81 0a 20
494 +DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 = 20 20 20 2d 30
594 594  
595 -DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 =(% style="background-color:#4f81bd; color:white" %) 20 20 20 2d 30
596 596  
597 597  
598 598  Below are the uplink payloads:
599 599  
600 -[[image:1653272901032-107.png]]
500 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.png]]
601 601  
602 602  
603 -(% style="color:red" %)Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:
503 +Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:
604 604  
605 605   ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink ( so 51 -5 = 46 max valid date)
606 606  
... ... @@ -612,121 +612,88 @@
612 612  
613 613  
614 614  
615 -=== 3.3.5 Uplink on demand ===
515 +1.
516 +11.
517 +111. Uplink on demand
616 616  
617 -(((
618 618  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.
619 -)))
620 620  
621 -(((
622 622  Downlink control command:
623 -)))
624 624  
625 -(((
626 -**0x08 command**: Poll an uplink with current command set in RS485-BL.
627 -)))
523 +[[0x08 command>>path:#downlink_08]]: Poll an uplink with current command set in RS485-BL.
628 628  
629 -(((
630 -**0xA8 command**: Send a command to RS485-BL and uplink the output from sensors.
631 -)))
525 +[[0xA8 command>>path:#downlink_A8]]: Send a command to RS485-BL and uplink the output from sensors.
632 632  
633 -=== 3.3.6 Uplink on Interrupt ===
634 634  
635 -Put the interrupt sensor between 3.3v_out and GPIO ext.
636 636  
637 -[[image:1653273818896-432.png]]
529 +1.
530 +11.
531 +111. Uplink on Interrupt
638 638  
639 -(((
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 +
640 640  AT+INTMOD=0  Disable Interrupt
641 -)))
642 642  
643 -(((
644 644  AT+INTMOD=1  Interrupt trigger by rising or falling edge.
645 -)))
646 646  
647 -(((
648 648  AT+INTMOD=2  Interrupt trigger by falling edge. ( Default Value)
649 -)))
650 650  
651 -(((
652 652  AT+INTMOD=3  Interrupt trigger by rising edge.
653 -)))
654 654  
655 -== 3.4 Uplink Payload ==
656 656  
657 -(% border="1" style="background-color:#4f81bd; color:white; width:850px" %)
658 -|**Size(bytes)**|(% style="width:130px" %)**2**|(% style="width:93px" %)**1**|(% style="width:509px" %)**Length depends on the return from the commands**
659 -|Value|(% style="width:130px" %)(((
660 -(((
544 +1.
545 +11. Uplink Payload
546 +
547 +|**Size(bytes)**|**2**|**1**|**Length depends on the return from the commands**
548 +|Value|(((
661 661  Battery(mV)
662 -)))
663 663  
664 -(((
665 665  &
666 -)))
667 667  
668 -(((
669 669  Interrupt _Flag
670 -)))
671 -)))|(% style="width:93px" %)(((
554 +)))|(((
672 672  PAYLOAD_VER
673 673  
674 674  
675 -)))|(% 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.
676 676  
677 677  Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors.
678 678  
679 -(((
562 +
680 680  function Decoder(bytes, port) {
681 -)))
682 682  
683 -(((
684 684  ~/~/Payload Formats of RS485-BL Deceive
685 -)))
686 686  
687 -(((
688 688  return {
689 -)))
690 690  
691 -(((
692 692   ~/~/Battery,units:V
693 -)))
694 694  
695 -(((
696 696   BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000,
697 -)))
698 698  
699 -(((
700 700   ~/~/GPIO_EXTI 
701 -)))
702 702  
703 -(((
704 704   EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE",
705 -)))
706 706  
707 -(((
708 708   ~/~/payload of version
709 -)))
710 710  
711 -(((
712 712   Pay_ver:bytes[2],
713 -)))
714 714  
715 -(((
716 716   };
717 -)))
718 718  
719 -(((
720 720   }
721 -)))
722 722  
723 -(((
585 +
586 +
587 +
588 +
589 +
590 +
724 724  TTN V3 uplink screen shot.
725 -)))
726 726  
727 -[[image:1653274001211-372.png||height="192" width="732"]]
593 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]
728 728  
729 -== 3.5 Configure RS485-BL via AT or Downlink ==
595 +1.
596 +11. Configure RS485-BL via AT or Downlink
730 730  
731 731  User can configure RS485-BL via [[AT Commands >>path:#_​Using_the_AT]]or LoRaWAN Downlink Commands
732 732  
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