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

Summary

Details

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