Skip to Content
Last modified by Xiaoling on 2025/04/23 15:57
From version 40.20
edited by Xiaoling
on 2022/06/06 09:44
Change comment: There is no comment for this version
To version 15.3
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 ==
... ... @@ -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:**
... ... @@ -94,8 +94,6 @@
94 94  * 127 dB Dynamic Range RSSI.
95 95  * Automatic RF Sense and CAD with ultra-fast AFC. ​​​
96 96  
97 -
98 -
99 99  == 1.3 Features ==
100 100  
101 101  * LoRaWAN Class A & Class C protocol (default Class A)
... ... @@ -107,8 +107,6 @@
107 107  * Support Modbus protocol
108 108  * Support Interrupt uplink
109 109  
110 -
111 -
112 112  == 1.4 Applications ==
113 113  
114 114  * Smart Buildings & Home Automation
... ... @@ -118,18 +118,13 @@
118 118  * Smart Cities
119 119  * Smart Factory
120 120  
121 -
122 -
123 123  == 1.5 Firmware Change log ==
124 124  
125 125  [[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);"]]
126 126  
127 -
128 128  == 1.6 Hardware Change log ==
129 129  
130 130  (((
131 -
132 -
133 133  v1.4
134 134  )))
135 135  
... ... @@ -153,8 +153,6 @@
153 153  
154 154  (((
155 155  Release version ​​​​​
156 -
157 -
158 158  )))
159 159  
160 160  = 2. Pin mapping and Power ON Device =
... ... @@ -168,7 +168,6 @@
168 168  
169 169  The Left TXD and RXD are TTL interface for external sensor. TTL level is controlled by 3.3/5v Jumper.
170 170  
171 -
172 172  = 3. Operation Mode =
173 173  
174 174  == 3.1 How it works? ==
... ... @@ -175,8 +175,6 @@
175 175  
176 176  (((
177 177  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.
178 -
179 -
180 180  )))
181 181  
182 182  == 3.2 Example to join LoRaWAN network ==
... ... @@ -212,6 +212,8 @@
212 212  )))
213 213  
214 214  
197 +
198 +
215 215  [[image:image-20220519174512-1.png]]
216 216  
217 217  [[image:image-20220519174512-2.png||height="328" width="731"]]
... ... @@ -236,191 +236,142 @@
236 236  [[image:1652953568895-172.png||height="232" width="724"]]
237 237  
238 238  
239 -== 3.3 Configure Commands to read data ==
240 240  
241 -(((
242 -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.
243 243  
244 -
245 -)))
225 +1.
226 +11. Configure Commands to read data
246 246  
247 -=== 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.
248 248  
230 +
231 +1.
232 +11.
233 +111. Configure UART settings for RS485 or TTL communication
234 +
249 249  RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect.
250 250  
251 -**~1. RS485-MODBUS mode:**
237 +1. RS485-MODBUS mode:
252 252  
253 253  AT+MOD=1 ~/~/ Support RS485-MODBUS type sensors. User can connect multiply RS485 , Modbus sensors to the A / B pins.
254 254  
255 -**2. TTL mode:**
256 256  
242 +1. TTL mode:
243 +
257 257  AT+MOD=2 ~/~/ Support TTL Level sensors, User can connect one TTL Sensor to the TXD/RXD/GND pins.
258 258  
246 +
259 259  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.
260 260  
261 -(% border="1" style="background-color:#ffffcc; color:green; width:795px" %)
262 -|(((
263 -**AT Commands**
264 -)))|(% style="width:285px" %)(((
265 -**Description**
266 -)))|(% style="width:347px" %)(((
267 -**Example**
268 -)))
269 -|(((
270 -AT+BAUDR
271 -)))|(% style="width:285px" %)(((
272 -Set the baud rate (for RS485 connection). Default Value is: 9600.
273 -)))|(% style="width:347px" %)(((
274 -(((
249 +
250 +|**AT Commands**|**Description**|**Example**
251 +|AT+BAUDR|Set the baud rate (for RS485 connection). Default Value is: 9600.|(((
275 275  AT+BAUDR=9600
276 -)))
277 277  
278 -(((
279 279  Options: (1200,2400,4800,14400,19200,115200)
280 280  )))
281 -)))
282 -|(((
283 -AT+PARITY
284 -)))|(% style="width:285px" %)(((
285 -(((
256 +|AT+PARITY|(((
286 286  Set UART parity (for RS485 connection)
287 -)))
288 288  
289 -(((
290 290  Default Value is: no parity.
291 -)))
292 -)))|(% style="width:347px" %)(((
293 -(((
260 +)))|(((
294 294  AT+PARITY=0
295 -)))
296 296  
297 -(((
298 298  Option: 0: no parity, 1: odd parity, 2: even parity
299 299  )))
300 -)))
301 -|(((
302 -AT+STOPBIT
303 -)))|(% style="width:285px" %)(((
304 -(((
265 +|AT+STOPBIT|(((
305 305  Set serial stopbit (for RS485 connection)
306 -)))
307 307  
308 -(((
309 309  Default Value is: 1bit.
310 -)))
311 -)))|(% style="width:347px" %)(((
312 -(((
269 +)))|(((
313 313  AT+STOPBIT=0 for 1bit
314 -)))
315 315  
316 -(((
317 317  AT+STOPBIT=1 for 1.5 bit
318 -)))
319 319  
320 -(((
321 321  AT+STOPBIT=2 for 2 bits
322 322  )))
323 -)))
324 324  
325 325  
326 326  
327 -=== 3.3.2 Configure sensors ===
328 328  
329 -(((
330 -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**.
331 -)))
280 +1.
281 +11.
282 +111. Configure sensors
332 332  
333 -(((
334 -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.
335 -)))
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.
336 336  
337 -(% border="1" style="background-color:#ffffcc; color:green; width:806px" %)
338 -|**AT Commands**|(% style="width:418px" %)**Description**|(% style="width:256px" %)**Example**
339 -|AT+CFGDEV|(% style="width:418px" %)(((
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|(((
340 340  This command is used to configure the RS485/TTL devices; they won’t be used during sampling.
341 341  
342 -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
343 343  
344 -mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
345 -)))|(% 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
346 346  
347 -Detail of AT+CFGDEV command see [[AT+CFGDEV detail>>||anchor="HRS485DebugCommand28AT2BCFGDEV29"]].
298 +Detail of AT+CFGDEV command see [[AT+CFGDEV detail>>path:#AT_CFGDEV]].
348 348  
349 349  
350 -=== 3.3.3 Configure read commands for each sampling ===
351 351  
352 -(((
302 +
303 +
304 +1.
305 +11.
306 +111. Configure read commands for each sampling
307 +
353 353  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.
354 -)))
355 355  
356 -(((
310 +
357 357  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.
358 -)))
359 359  
360 -(((
313 +
361 361  To save the LoRaWAN network bandwidth, we might need to read data from different sensors and combine their valid value into a short payload.
362 -)))
363 363  
364 -(((
316 +
365 365  This section describes how to achieve above goals.
366 -)))
367 367  
368 -(((
319 +
369 369  During each sampling, the RS485-BL can support 15 commands to read sensors. And combine the return to one or several uplink payloads.
370 -)))
371 371  
372 -(((
322 +
373 373  **Command from RS485-BL to Sensor:**
374 -)))
375 375  
376 -(((
377 377  RS485-BL can send out pre-set max 15 strings via **AT+COMMAD1**, **ATCOMMAND2**,…, to **AT+COMMANDF** . All commands are of same grammar.
378 -)))
379 379  
380 -(((
327 +
381 381  **Handle return from sensors to RS485-BL**:
382 -)))
383 383  
384 -(((
385 385  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**
386 -)))
387 387  
388 -* (((
389 -**AT+DATACUT**
390 -)))
391 391  
392 -(((
333 +* **AT+DATACUT**
334 +
393 393  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.
394 -)))
395 395  
396 -* (((
397 -**AT+SEARCH**
398 -)))
399 399  
400 -(((
338 +* **AT+SEARCH**
339 +
401 401  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.
402 -)))
403 403  
404 -(((
342 +
405 405  **Define wait timeout:**
406 -)))
407 407  
408 -(((
409 409  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
410 -)))
411 411  
412 -(((
347 +
413 413  After we got the valid value from each RS485 commands, we need to combine them together with the command **AT+DATAUP**.
414 -)))
415 415  
350 +
416 416  **Examples:**
417 417  
418 418  Below are examples for the how above AT Commands works.
419 419  
355 +
420 420  **AT+COMMANDx : **This command will be sent to RS485/TTL devices during each sampling, Max command length is 14 bytes. The grammar is:
421 421  
422 -(% border="1" class="table-bordered" style="background-color:#4f81bd; color:white; width:501px" %)
423 -|(% style="width:498px" %)(((
358 +|(((
424 424  **AT+COMMANDx=xx xx xx xx xx xx xx xx xx xx xx xx,m**
425 425  
426 426  **xx xx xx xx xx xx xx xx xx xx xx xx: The RS485 command to be sent**
... ... @@ -432,38 +432,41 @@
432 432  
433 433  In the RS485-BL, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
434 434  
370 +
435 435  **AT+SEARCHx**: This command defines how to handle the return from AT+COMMANDx.
436 436  
437 -(% border="1" class="table-bordered" style="background-color:#4f81bd; color:white; width:580px" %)
438 -|(% style="width:577px" %)(((
373 +|(((
439 439  **AT+SEARCHx=aa,xx xx xx xx xx**
440 440  
441 441  * **aa: 1: prefix match mode; 2: prefix and suffix match mode**
442 442  * **xx xx xx xx xx: match string. Max 5 bytes for prefix and 5 bytes for suffix**
378 +
379 +
443 443  )))
444 444  
445 -**Examples:**
382 +Examples:
446 446  
447 -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
448 448  
449 449  If we set AT+SEARCH1=1,1E 56 34.      (max 5 bytes for prefix)
450 450  
451 -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
452 452  
453 -[[image:1653271044481-711.png]]
390 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image013.png]]
454 454  
455 -2）For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
456 456  
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 +
457 457  If we set AT+SEARCH1=2, 1E 56 34+31 00 49
458 458  
459 -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
460 460  
461 -[[image:1653271276735-972.png]]
399 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image014.png]]
462 462  
401 +
463 463  **AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes.
464 464  
465 -(% style="background-color:#4f81bd; color:white; width:729px" %)
466 -|(% style="width:726px" %)(((
404 +|(((
467 467  **AT+DATACUTx=a,b,c**
468 468  
469 469  * **a: length for the return of AT+COMMAND**
... ... @@ -471,143 +471,98 @@
471 471  * **c: define the position for valid value.  **
472 472  )))
473 473  
474 -**Examples:**
412 +Examples:
475 475  
476 476  * Grab bytes:
477 477  
478 -[[image:1653271581490-837.png||height="313" width="722"]]
416 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image015.png]]
479 479  
480 -
481 481  * Grab a section.
482 482  
483 -[[image:1653271648378-342.png||height="326" width="720"]]
420 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image016.png]]
484 484  
485 -
486 486  * Grab different sections.
487 487  
488 -[[image:1653271657255-576.png||height="305" width="730"]]
424 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image017.png]]
489 489  
490 -(((
491 -(% style="color:red" %)**Note:**
492 -)))
493 493  
494 -(((
427 +Note:
428 +
495 495  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.
496 -)))
497 497  
498 -(((
499 -**Example:**
500 -)))
431 +Example:
501 501  
502 -(((
503 -(% style="color:red" %)AT+COMMAND1=11 01 1E D0,0
504 -)))
433 +AT+COMMAND1=11 01 1E D0,0
505 505  
506 -(((
507 -(% style="color:red" %)AT+SEARCH1=1,1E 56 34
508 -)))
435 +AT+SEARCH1=1,1E 56 34
509 509  
510 -(((
511 -(% style="color:red" %)AT+DATACUT1=0,2,1~~5
512 -)))
437 +AT+DATACUT1=0,2,1~~5
513 513  
514 -(((
515 -(% style="color:red" %)Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
516 -)))
439 +Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
517 517  
518 -(((
519 -(% style="color:red" %)String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
520 -)))
441 +String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
521 521  
522 -(((
523 -(% style="color:red" %)Valid payload after DataCUT command: 2e 30 58 5f 36
524 -)))
443 +Valid payload after DataCUT command: 2e 30 58 5f 36
525 525  
526 -[[image:1653271763403-806.png]]
445 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image018.png]]
527 527  
528 528  
529 -=== 3.3.4 Compose the uplink payload ===
530 530  
531 -(((
449 +
450 +1.
451 +11.
452 +111. Compose the uplink payload
453 +
532 532  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.**
533 -)))
534 534  
535 -(((
536 -(% style="color:#037691" %)**Examples: AT+DATAUP=0**
537 -)))
538 538  
539 -(((
540 -Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**A SIGNLE UPLINK**.
541 -)))
457 +**Examples: AT+DATAUP=0**
542 542  
543 -(((
459 +Compose the uplink payload with value returns in sequence and send with **A SIGNLE UPLINK**.
460 +
544 544  Final Payload is
545 -)))
546 546  
547 -(((
548 -(% style="color:#4f81bd" %)**Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx**
549 -)))
463 +Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx
550 550  
551 -(((
552 552  Where PAYVER is defined by AT+PAYVER, below is an example screen shot.
553 -)))
554 554  
555 -[[image:1653272787040-634.png||height="515" width="719"]]
467 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.png]]
556 556  
557 557  
558 558  
559 -(((
560 -(% style="color:#037691" %)**Examples: AT+DATAUP=1**
471 +**Examples: AT+DATAUP=1**
561 561  
562 -
563 -)))
473 +Compose the uplink payload with value returns in sequence and send with **Multiply UPLINKs**.
564 564  
565 -(((
566 -Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**Multiply UPLINKs**.
567 -)))
568 -
569 -(((
570 570  Final Payload is
571 -)))
572 572  
573 -(((
574 -(% style="color:#4f81bd" %)**Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA**
575 -)))
477 +Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA
576 576  
577 -1. (((
578 -Battery Info (2 bytes): Battery voltage
579 -)))
580 -1. (((
581 -PAYVER (1 byte): Defined by AT+PAYVER
582 -)))
583 -1. (((
584 -PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling.
585 -)))
586 -1. (((
587 -PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
588 -)))
589 -1. (((
590 -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
591 -)))
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
592 592  
593 -[[image:1653272817147-600.png||height="437" width="717"]]
485 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image020.png]]
594 594  
487 +
595 595  So totally there will be 3 uplinks for this sampling, each uplink includes 6 bytes DATA
596 596  
490 +DATA1=RETURN1 Valid Value = 20 20 0a 33 90 41
597 597  
598 -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
599 599  
600 -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
601 601  
602 -DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 =(% style="background-color:#4f81bd; color:white" %) 20 20 20 2d 30
603 603  
604 604  
605 605  Below are the uplink payloads:
606 606  
607 -[[image:1653272901032-107.png]]
500 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.png]]
608 608  
609 609  
610 -(% 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:
611 611  
612 612   ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink ( so 51 -5 = 46 max valid date)
613 613  
... ... @@ -619,187 +619,139 @@
619 619  
620 620  
621 621  
622 -=== 3.3.5 Uplink on demand ===
515 +1.
516 +11.
517 +111. Uplink on demand
623 623  
624 -(((
625 625  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.
626 -)))
627 627  
628 -(((
629 629  Downlink control command:
630 -)))
631 631  
632 -(((
633 -**0x08 command**: Poll an uplink with current command set in RS485-BL.
634 -)))
523 +[[0x08 command>>path:#downlink_08]]: Poll an uplink with current command set in RS485-BL.
635 635  
636 -(((
637 -**0xA8 command**: Send a command to RS485-BL and uplink the output from sensors.
525 +[[0xA8 command>>path:#downlink_A8]]: Send a command to RS485-BL and uplink the output from sensors.
638 638  
639 -
640 -)))
641 641  
642 -=== 3.3.6 Uplink on Interrupt ===
643 643  
644 -Put the interrupt sensor between 3.3v_out and GPIO ext.
529 +1.
530 +11.
531 +111. Uplink on Interrupt
645 645  
646 -[[image:1653273818896-432.png]]
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]]
647 647  
648 -
649 -(((
650 650  AT+INTMOD=0  Disable Interrupt
651 -)))
652 652  
653 -(((
654 654  AT+INTMOD=1  Interrupt trigger by rising or falling edge.
655 -)))
656 656  
657 -(((
658 658  AT+INTMOD=2  Interrupt trigger by falling edge. ( Default Value)
659 -)))
660 660  
661 -(((
662 662  AT+INTMOD=3  Interrupt trigger by rising edge.
663 663  
664 -
665 -)))
666 666  
667 -== 3.4 Uplink Payload ==
544 +1.
545 +11. Uplink Payload
668 668  
669 -(% border="1" style="background-color:#4f81bd; color:white; width:850px" %)
670 -|**Size(bytes)**|(% style="width:130px" %)**2**|(% style="width:93px" %)**1**|(% style="width:509px" %)**Length depends on the return from the commands**
671 -|Value|(% style="width:130px" %)(((
672 -(((
547 +|**Size(bytes)**|**2**|**1**|**Length depends on the return from the commands**
548 +|Value|(((
673 673  Battery(mV)
674 -)))
675 675  
676 -(((
677 677  &
678 -)))
679 679  
680 -(((
681 681  Interrupt _Flag
682 -)))
683 -)))|(% style="width:93px" %)(((
554 +)))|(((
684 684  PAYLOAD_VER
685 685  
686 686  
687 -)))|(% 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.
688 688  
689 689  Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors.
690 690  
691 -(((
692 -{{{function Decoder(bytes, port) {}}}
693 -)))
694 694  
695 -(((
696 -{{{//Payload Formats of RS485-BL Deceive}}}
697 -)))
563 +function Decoder(bytes, port) {
698 698  
699 -(((
700 -{{{return {}}}
701 -)))
565 +~/~/Payload Formats of RS485-BL Deceive
702 702  
703 -(((
704 -{{{ //Battery,units:V}}}
705 -)))
567 +return {
706 706  
707 -(((
708 -{{{ BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000,}}}
709 -)))
569 + ~/~/Battery,units:V
710 710  
711 -(((
712 -{{{ //GPIO_EXTI }}}
713 -)))
571 + BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000,
714 714  
715 -(((
716 -{{{ EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE",}}}
717 -)))
573 + ~/~/GPIO_EXTI 
718 718  
719 -(((
720 -{{{ //payload of version}}}
721 -)))
575 + EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE",
722 722  
723 -(((
724 -{{{ Pay_ver:bytes[2],}}}
725 -)))
577 + ~/~/payload of version
726 726  
727 -(((
728 -{{{ }; }}}
729 -)))
579 + Pay_ver:bytes[2],
730 730  
731 -(((
732 -**}**
581 + };
733 733  
734 -
735 -)))
583 + }
736 736  
737 -(((
738 -TTN V3 uplink screen shot.
739 -)))
740 740  
741 -[[image:1653274001211-372.png||height="192" width="732"]]
742 742  
743 743  
744 -== 3.5 Configure RS485-BL via AT or Downlink ==
745 745  
746 -User can configure RS485-BL via AT Commands or LoRaWAN Downlink Commands
747 747  
748 -There are two kinds of Commands:
749 749  
750 -* (% style="color:#4f81bd" %)**Common Commands**(%%): They should be available for each sensor, such as: change uplink interval, reset device. For firmware v1.3, user can find what common commands it supports: [[AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]
591 +TTN V3 uplink screen shot.
751 751  
752 -* (% style="color:#4f81bd" %)**Sensor Related Commands**(%%): These commands are special designed for RS485-BL.  User can see these commands below:
593 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]
753 753  
595 +1.
596 +11. Configure RS485-BL via AT or Downlink
754 754  
598 +User can configure RS485-BL via [[AT Commands >>path:#_​Using_the_AT]]or LoRaWAN Downlink Commands
755 755  
756 -=== 3.5.1 Common Commands: ===
600 +There are two kinds of Commands:
757 757  
758 -They should be available for each of Dragino Sensors, such as: change uplink interval, reset device. For firmware v1.3, user can find what common commands it supports: [[End Device AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]
602 +* **Common Commands**: They should be available for each sensor, such as: change uplink interval, reset device. For firmware v1.3, user can find what common commands it supports: http:~/~/wiki.dragino.com/index.php?title=End_Device_AT_Commands_and_Downlink_Commands
759 759  
604 +* **Sensor Related Commands**: These commands are special designed for RS485-BL.  User can see these commands below:
760 760  
761 -=== 3.5.2 Sensor related commands: ===
606 +1.
607 +11.
608 +111. Common Commands:
762 762  
610 +They should be available for each of Dragino Sensors, such as: change uplink interval, reset device. For firmware v1.3, user can find what common commands it supports: [[http:~~/~~/wiki.dragino.com/index.php?title=End_Device_AT_Commands_and_Downlink_Commands>>url:http://wiki.dragino.com/index.php?title=End_Device_AT_Commands_and_Downlink_Commands]]
763 763  
764 -==== **Choose Device Type (RS485 or TTL)** ====
765 765  
613 +1.
614 +11.
615 +111. Sensor related commands:
616 +
617 +==== Choose Device Type (RS485 or TTL) ====
618 +
766 766  RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect.
767 767  
768 -* **AT Command**
621 +* AT Command
769 769  
770 -(% class="box infomessage" %)
771 -(((
772 772  **AT+MOD=1** ~/~/ Set to support RS485-MODBUS type sensors. User can connect multiply RS485 , Modbus sensors to the A / B pins.
773 -)))
774 774  
775 -(% class="box infomessage" %)
776 -(((
777 777  **AT+MOD=2** ~/~/ Set to support TTL Level sensors, User can connect one TTL Sensor to the TXD/RXD/GND pins.
778 -)))
779 779  
780 780  
781 -* **Downlink Payload**
628 +* Downlink Payload
782 782  
783 -**0A aa**  ~-~->  same as AT+MOD=aa
630 +**0A aa**     à same as AT+MOD=aa
784 784  
785 785  
786 786  
787 -==== **RS485 Debug Command (AT+CFGDEV)** ====
634 +==== [[RS485 Debug Command>>path:#downlink_A8]] (AT+CFGDEV) ====
788 788  
789 789  This command is used to configure the RS485 or TTL sensors; they won’t be used during sampling.
790 790  
791 -* **AT Command**
638 +* AT Command
792 792  
793 -(% class="box infomessage" %)
794 -(((
795 -**AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m**
796 -)))
640 +AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
797 797  
798 798  m: 0: no CRC; 1: add CRC-16/MODBUS in the end of this command.
799 799  
800 800  
801 -* **Downlink Payload**
802 802  
646 +* Downlink Payload
647 +
803 803  Format: A8 MM NN XX XX XX XX YY
804 804  
805 805  Where:
... ... @@ -813,15 +813,15 @@
813 813  
814 814  To connect a Modbus Alarm with below commands.
815 815  
816 -* The command to active alarm is: 0A 05 00 04 00 01 **4C B0**. Where 0A 05 00 04 00 01 is the Modbus command to read the register 00 40 where stored the DI status. The 4C B0 is the CRC-16/MODBUS which calculate manually.
661 +* The command to active alarm is: 0A 05 00 04 00 01 4C B0. Where 0A 05 00 04 00 01 is the Modbus command to read the register 00 40 where stored the DI status. The 4C B0 is the CRC-16/MODBUS which calculate manually.
817 817  
818 -* The command to deactivate alarm is: 0A 05 00 04 00 00 **8D 70**. Where 0A 05 00 04 00 00 is the Modbus command to read the register 00 40 where stored the DI status. The 8D 70 is the CRC-16/MODBUS which calculate manually.
663 +* The command to deactivate alarm is: 0A 05 00 04 00 00 8D 70. Where 0A 05 00 04 00 00 is the Modbus command to read the register 00 40 where stored the DI status. The 8D 70 is the CRC-16/MODBUS which calculate manually.
819 819  
820 820  So if user want to use downlink command to control to RS485 Alarm, he can use:
821 821  
822 -(% style="color:#037691" %)**A8 01 06 0A 05 00 04 00 01 00**(%%): to activate the RS485 Alarm
667 +**A8 01 06 0A 05 00 04 00 01 00**: to activate the RS485 Alarm
823 823  
824 -(% style="color:#037691" %)**A8 01 06 0A 05 00 04 00 00 00**(%%): to deactivate the RS485 Alarm
669 +**A8 01 06 0A 05 00 04 00 00 00**: to deactivate the RS485 Alarm
825 825  
826 826  A8 is type code and 01 means add CRC-16/MODBUS at the end, the 3^^rd^^ byte is 06, means the next 6 bytes are the command to be sent to the RS485 network, the final byte 00 means this command don’t need to acquire output.
827 827  
... ... @@ -830,61 +830,48 @@
830 830  
831 831  Check TTL Sensor return:
832 832  
833 -[[image:1654132684752-193.png]]
678 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image024.png]]
834 834  
835 835  
836 836  
837 837  
838 -==== **Set Payload version** ====
683 +==== Set Payload version ====
839 839  
840 840  This is the first byte of the uplink payload. RS485-BL can connect to different sensors. User can set the PAYVER field to tell server how to decode the current payload.
841 841  
842 -* **AT Command:**
687 +* AT Command:
843 843  
844 -(% class="box infomessage" %)
845 -(((
846 -**AT+PAYVER: Set PAYVER field = 1**
847 -)))
689 +AT+PAYVER: Set PAYVER field = 1
848 848  
849 849  
850 -* **Downlink Payload:**
692 +* Downlink Payload:
851 851  
852 -**0xAE 01**  ~-~-> Set PAYVER field =  0x01
694 +0xAE 01   à Set PAYVER field =  0x01
853 853  
854 -**0xAE 0F**   ~-~-> Set PAYVER field =  0x0F
696 +0xAE 0F   à Set PAYVER field =  0x0F
855 855  
856 856  
699 +==== Set RS485 Sampling Commands ====
857 857  
858 -==== **Set RS485 Sampling Commands** ====
859 -
860 860  AT+COMMANDx, AT+DATACUTx and AT+SEARCHx
861 861  
862 -These three commands are used to configure how the RS485-BL polling data from Modbus device. Detail of usage please see : [[polling RS485 device>>||anchor="H3.3.3Configurereadcommandsforeachsampling"]].
703 +These three commands are used to configure how the RS485-BL polling data from Modbus device. Detail of usage please see : [[polling RS485 device>>path:#polling_485]].
863 863  
864 864  
865 -* **AT Command:**
706 +* AT Command:
866 866  
867 -(% class="box infomessage" %)
868 -(((
869 -**AT+COMMANDx: Configure RS485 read command to sensor.**
870 -)))
708 +AT+COMMANDx: Configure RS485 read command to sensor.
871 871  
872 -(% class="box infomessage" %)
873 -(((
874 -**AT+DATACUTx: Configure how to handle return from RS485 devices.**
875 -)))
710 +AT+DATACUTx: Configure how to handle return from RS485 devices.
876 876  
877 -(% class="box infomessage" %)
878 -(((
879 -**AT+SEARCHx: Configure search command**
880 -)))
712 +AT+SEARCHx: Configure search command
881 881  
882 882  
883 -* **Downlink Payload:**
715 +* Downlink Payload:
884 884  
885 -**0xAF** downlink command can be used to set AT+COMMANDx or AT+DATACUTx.
717 +0xAF downlink command can be used to set AT+COMMANDx or AT+DATACUTx.
886 886  
887 -(% style="color:red" %)**Note**(%%): if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink.
719 +Note: if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink.
888 888  
889 889  Format: AF MM NN LL XX XX XX XX YY
890 890  
... ... @@ -891,23 +891,23 @@
891 891  Where:
892 892  
893 893  * MM: the ATCOMMAND or AT+DATACUT to be set. Value from 01 ~~ 0F,
894 -* NN:  0: no CRC; 1: add CRC-16/MODBUS ; 2: set the AT+DATACUT value.
895 -* LL:  The length of AT+COMMAND or AT+DATACUT command
726 +* NN: 0: no CRC; 1: add CRC-16/MODBUS ; 2: set the AT+DATACUT value.
727 +* LL: The length of AT+COMMAND or AT+DATACUT command
896 896  * XX XX XX XX: AT+COMMAND or AT+DATACUT command
897 -* YY:  If YY=0, RS485-BL will execute the downlink command without uplink; if YY=1, RS485-BL will execute an uplink after got this command.
729 +* YY: If YY=0, RS485-BL will execute the downlink command without uplink; if YY=1, RS485-BL will execute an uplink after got this command.
898 898  
899 -**Example:**
731 +Example:
900 900  
901 -(% style="color:#037691" %)**AF 03 01 06 0A 05 00 04 00 01 00**(%%): Same as AT+COMMAND3=0A 05 00 04 00 01,1
733 +**AF 03 01 06 0A 05 00 04 00 01 00**: Same as AT+COMMAND3=0A 05 00 04 00 01,1
902 902  
903 -(% style="color:#037691" %)**AF 03 02 06**(% style="color:orange" %)** 10 **(% style="color:red" %)**01 **(% style="color:green" %)**05 06 09 0A**(% style="color:#037691" %)** 00**(%%): Same as AT+DATACUT3=(% style="color:orange" %)**16**(%%),(% style="color:red" %)**1**(%%),(% style="color:green" %)**5+6+9+10**
735 +**AF 03 02 06 10 01 05 06 09 0A 00**: Same as AT+DATACUT3=**16**,**1**,**5+6+9+10**
904 904  
905 -(% style="color:#037691" %)**AF 03 02 06 **(% style="color:orange" %)**0B**(% style="color:red" %)** 02 **(% style="color:green" %)**05 07 08 0A **(% style="color:#037691" %)**00**(%%): Same as AT+DATACUT3=(% style="color:orange" %)**11**(%%),(% style="color:red" %)**2**(%%),(% style="color:green" %)**5~~7+8~~10**
737 +**AF 03 02 06 0B 02 05 07 08 0A 00**: Same as AT+DATACUT3=**11**,**2**,**5~~7+8~~10**
906 906  
907 907  
908 -**0xAB** downlink command can be used for set AT+SEARCHx
740 +0xAB downlink command can be used for set AT+SEARCHx
909 909  
910 -**Example:** **AB aa 01 03 xx xx xx** (03 here means there are total 3 bytes after 03) So
742 +Example: **AB aa 01 03 xx xx xx** (03 here means there are total 3 bytes after 03) So
911 911  
912 912  * AB aa 01 03 xx xx xx  same as AT+SEARCHaa=1,xx xx xx
913 913  * AB aa 02 03 xx xx xx 02 yy yy(03 means there are 3 bytes after 03, they are xx xx xx;02 means there are 2 bytes after 02, they are yy yy) so the commands
... ... @@ -915,165 +915,145 @@
915 915  **AB aa 02 03 xx xx xx 02 yy yy**  same as **AT+SEARCHaa=2,xx xx xx+yy yy**
916 916  
917 917  
750 +==== Fast command to handle MODBUS device ====
918 918  
919 -==== **Fast command to handle MODBUS device** ====
920 -
921 921  AT+MBFUN is valid since v1.3 firmware version. The command is for fast configure to read Modbus devices. It is only valid for the devices which follow the [[MODBUS-RTU protocol>>url:https://www.modbustools.com/modbus.html]].
922 922  
923 923  This command is valid since v1.3 firmware version
924 924  
925 925  
926 -**AT+MBFUN has only two value:**
757 +AT+MBFUN has only two value:
927 927  
928 -* **AT+MBFUN=1**: Enable Modbus reading. And get response base on the MODBUS return
759 +* AT+MBFUN=1: Enable Modbus reading. And get response base on the MODBUS return
929 929  
930 930  AT+MBFUN=1, device can auto read the Modbus function code: 01, 02, 03 or 04. AT+MBFUN has lower priority vs AT+DATACUT command. If AT+DATACUT command is configured, AT+MBFUN will be ignore.
931 931  
932 -* **AT+MBFUN=0**: Disable Modbus fast reading.
763 +* AT+MBFUN=0: Disable Modbus fast reading.
933 933  
934 -**Example:**
765 +Example:
935 935  
936 936  * AT+MBFUN=1 and AT+DATACUT1/AT+DATACUT2 are not configure (0,0,0).
937 937  * AT+COMMAND1= 01 03 00 10 00 08,1 ~-~-> read slave address 01 , function code 03, start address 00 01, quantity of registers 00 08.
938 938  * AT+COMMAND2= 01 02 00 40 00 10,1 ~-~-> read slave address 01 , function code 02, start address 00 40, quantity of inputs 00 10.
939 939  
940 -[[image:1654133913295-597.png]]
771 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image025.png]]
941 941  
942 942  
943 -[[image:1654133954153-643.png]]
774 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image026.png]]
944 944  
945 945  
946 -* **Downlink Commands:**
777 +* Downlink Commands:
947 947  
948 -**A9 aa** ~-~-> Same as AT+MBFUN=aa
779 +A9 aa -à Same as AT+MBFUN=aa
949 949  
950 950  
782 +==== RS485 command timeout ====
951 951  
952 -==== **RS485 command timeout** ====
953 -
954 954  Some Modbus device has slow action to send replies. This command is used to configure the RS485-BL to use longer time to wait for their action.
955 955  
956 956  Default value: 0, range:  0 ~~ 5 seconds
957 957  
958 958  
959 -* **AT Command:**
789 +* AT Command:
960 960  
961 -(% class="box infomessage" %)
962 -(((
963 -**AT+CMDDLaa=hex(bb cc)**
964 -)))
791 +AT+CMDDLaa=hex(bb cc)
965 965  
966 -**Example:**
793 +Example:
967 967  
968 968  **AT+CMDDL1=1000** to send the open time to 1000ms
969 969  
970 970  
971 -* **Downlink Payload:**
798 +* Downlink Payload:
972 972  
973 973  0x AA aa bb cc
974 974  
975 975  Same as: AT+CMDDLaa=hex(bb cc)
976 976  
977 - **Example:**
804 + Example:
978 978  
979 - **0xAA 01 03 E8**  ~-~-> Same as **AT+CMDDL1=1000 ms**
806 + 0xAA 01 03 E8  à Same as **AT+CMDDL1=1000 ms**
980 980  
981 981  
809 +==== [[Uplink>>path:#downlink_A8]] payload mode ====
982 982  
983 -==== **Uplink payload mode** ====
984 -
985 985  Define to use one uplink or multiple uplinks for the sampling.
986 986  
987 -The use of this command please see: [[Compose Uplink payload>>||anchor="H3.3.4Composetheuplinkpayload"]]
813 +The use of this command please see: [[Compose Uplink payload>>path:#DataUP]]
988 988  
989 -* **AT Command:**
815 +* AT Command:
990 990  
991 -(% class="box infomessage" %)
992 -(((
993 -**AT+DATAUP=0**
994 -)))
817 +AT+DATAUP=0
995 995  
996 -(% class="box infomessage" %)
997 -(((
998 -**AT+DATAUP=1**
999 -)))
819 +AT+DATAUP=1
1000 1000  
1001 1001  
1002 -* **Downlink Payload:**
822 +* Downlink Payload:
1003 1003  
1004 -**0xAD 00**  **~-~->** Same as AT+DATAUP=0
824 +0xAD 00   à Same as AT+DATAUP=0
1005 1005  
1006 -**0xAD 01**  **~-~->** Same as AT+DATAUP=1
826 +0xAD 01   à Same as AT+DATAUP=1
1007 1007  
1008 1008  
829 +==== Manually trigger an Uplink ====
1009 1009  
1010 -
1011 -==== **Manually trigger an Uplink** ====
1012 -
1013 1013  Ask device to send an uplink immediately.
1014 1014  
1015 -* **Downlink Payload:**
833 +* Downlink Payload:
1016 1016  
1017 -**0x08 FF**, RS485-BL will immediately send an uplink.
835 +0x08 FF, RS485-BL will immediately send an uplink.
1018 1018  
1019 1019  
838 +==== Clear RS485 Command ====
1020 1020  
1021 -==== **Clear RS485 Command** ====
1022 -
1023 1023  The AT+COMMANDx and AT+DATACUTx settings are stored in special location, user can use below command to clear them.
1024 1024  
1025 1025  
1026 -* **AT Command:**
843 +* AT Command:
1027 1027  
1028 -(% style="color:#037691" %)**AT+CMDEAR=mm,nn** (%%) mm: start position of erase ,nn: stop position of erase Etc. AT+CMDEAR=1,10 means erase AT+COMMAND1/AT+DATACUT1 to AT+COMMAND10/AT+DATACUT10
845 +**AT+CMDEAR=mm,nn**   mm: start position of erase ,nn: stop position of erase
1029 1029  
847 +Etc. AT+CMDEAR=1,10 means erase AT+COMMAND1/AT+DATACUT1 to AT+COMMAND10/AT+DATACUT10
848 +
1030 1030  Example screen shot after clear all RS485 commands. 
1031 1031  
1032 1032  
852 +
1033 1033  The uplink screen shot is:
1034 1034  
1035 -[[image:1654134704555-320.png]]
855 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]
1036 1036  
1037 1037  
1038 -* **Downlink Payload:**
858 +* Downlink Payload:
1039 1039  
1040 -**0x09 aa bb** same as AT+CMDEAR=aa,bb
860 +0x09 aa bb same as AT+CMDEAR=aa,bb
1041 1041  
1042 1042  
863 +==== Set Serial Communication Parameters ====
1043 1043  
1044 -==== **Set Serial Communication Parameters** ====
1045 -
1046 1046  Set the Rs485 serial communication parameters:
1047 1047  
1048 -* **AT Command:**
867 +* AT Command:
1049 1049  
1050 1050  Set Baud Rate:
1051 1051  
1052 -(% class="box infomessage" %)
1053 -(((
1054 -**AT+BAUDR=9600**    ~/~/ Options: (1200,2400,4800,14400,19200,115200)
1055 -)))
871 +AT+BAUDR=9600    ~/~/ Options: (1200,2400,4800,14400,19200,115200)
1056 1056  
1057 -Set UART Parity
1058 1058  
1059 -(% class="box infomessage" %)
1060 -(((
1061 -**AT+PARITY=0**    ~/~/ Option: 0: no parity, 1: odd parity, 2: even parity
1062 -)))
874 +Set UART parity
1063 1063  
876 +AT+PARITY=0    ~/~/ Option: 0: no parity, 1: odd parity, 2: even parity
877 +
878 +
1064 1064  Set STOPBIT
1065 1065  
1066 -(% class="box infomessage" %)
1067 -(((
1068 -**AT+STOPBIT=0**    ~/~/ Option: 0 for 1bit; 1 for 1.5 bit ; 2 for 2 bits
1069 -)))
881 +AT+STOPBIT=0    ~/~/ Option: 0 for 1bit; 1 for 1.5 bit ; 2 for 2 bits
1070 1070  
1071 1071  
1072 -* **Downlink Payload:**
884 +* Downlink Payload:
1073 1073  
1074 -**A7 01 aa bb**: Same  AT+BAUDR=hex(aa bb)*100
886 +A7 01 aa bb: Same  AT+BAUDR=hex(aa bb)*100
1075 1075  
1076 -**Example:**
888 +Example:
1077 1077  
1078 1078  * A7 01 00 60   same as AT+BAUDR=9600
1079 1079  * A7 01 04 80  same as AT+BAUDR=115200
... ... @@ -1083,192 +1083,180 @@
1083 1083  A7 03 aa: Same as  AT+STOPBIT=aa  (aa value: 00 , 01 or 02)
1084 1084  
1085 1085  
898 +==== Control output power duration ====
1086 1086  
1087 -==== **Control output power duration** ====
1088 -
1089 1089  User can set the output power duration before each sampling.
1090 1090  
1091 -* **AT Command:**
902 +* AT Command:
1092 1092  
1093 -**Example:**
904 +Example:
1094 1094  
1095 -**AT+3V3T=1000**  ~/~/ 3V3 output power will open 1s before each sampling.
906 +AT+3V3T=1000 ~/~/ 3V3 output power will open 1s before each sampling.
1096 1096  
1097 -**AT+5VT=1000**  ~/~/ +5V output power will open 1s before each sampling.
908 +AT+5VT=1000 ~/~/ +5V output power will open 1s before each sampling.
1098 1098  
1099 1099  
1100 -* **LoRaWAN Downlink Command:**
911 +* LoRaWAN Downlink Command:
1101 1101  
1102 -**07 01 aa bb**  Same as AT+5VT=(aa bb)
913 +07 01 aa bb  Same as AT+5VT=(aa bb)
1103 1103  
1104 -**07 02 aa bb**  Same as AT+3V3T=(aa bb)
915 +07 02 aa bb  Same as AT+3V3T=(aa bb)
1105 1105  
1106 1106  
1107 -== 3.6 Buttons ==
1108 1108  
1109 -(% border="1" style="background-color:#ffffcc; color:green; width:233px" %)
1110 -|=(% style="width: 89px;" %)**Button**|=(% style="width: 141px;" %)**Feature**
1111 -|(% style="width:89px" %)**RST**|(% style="width:141px" %)Reboot RS485-BL
1112 1112  
920 +1.
921 +11. Buttons
1113 1113  
923 +|**Button**|**Feature**
924 +|**RST**|Reboot RS485-BL
1114 1114  
1115 -== 3.7 +3V3 Output ==
926 +1.
927 +11. +3V3 Output
1116 1116  
1117 1117  RS485-BL has a Controllable +3V3 output, user can use this output to power external sensor.
1118 1118  
1119 1119  The +3V3 output will be valid for every sampling. RS485-BL will enable +3V3 output before all sampling and disable the +3V3 after all sampling. 
1120 1120  
933 +
1121 1121  The +3V3 output time can be controlled by AT Command.
1122 1122  
936 +**AT+3V3T=1000**
1123 1123  
1124 -(% style="color:#037691" %)**AT+3V3T=1000**
1125 -
1126 -
1127 1127  Means set +3v3 valid time to have 1000ms. So, the real +3v3 output will actually have 1000ms + sampling time for other sensors.
1128 1128  
940 +
1129 1129  By default, the AT+3V3T=0. This is a special case, means the +3V3 output is always on at any time
1130 1130  
1131 1131  
1132 -== 3.8 +5V Output ==
944 +1.
945 +11. +5V Output
1133 1133  
1134 1134  RS485-BL has a Controllable +5V output, user can use this output to power external sensor.
1135 1135  
1136 1136  The +5V output will be valid for every sampling. RS485-BL will enable +5V output before all sampling and disable the +5v after all sampling. 
1137 1137  
951 +
1138 1138  The 5V output time can be controlled by AT Command.
1139 1139  
954 +**AT+5VT=1000**
1140 1140  
1141 -(% style="color:#037691" %)**AT+5VT=1000**
1142 -
1143 -
1144 1144  Means set 5V valid time to have 1000ms. So, the real 5V output will actually have 1000ms + sampling time for other sensors.
1145 1145  
958 +
1146 1146  By default, the AT+5VT=0. If the external sensor which require 5v and require more time to get stable state, user can use this command to increase the power ON duration for this sensor.
1147 1147  
1148 1148  
1149 -== 3.9 LEDs ==
1150 1150  
1151 -(% border="1" style="background-color:#ffffcc; color:green; width:332px" %)
1152 -|=**LEDs**|=(% style="width: 274px;" %)**Feature**
1153 -|**LED1**|(% style="width:274px" %)Blink when device transmit a packet.
1154 1154  
964 +1.
965 +11. LEDs
1155 1155  
967 +|**LEDs**|**Feature**
968 +|**LED1**|Blink when device transmit a packet.
1156 1156  
1157 -== 3.10 Switch Jumper ==
970 +1.
971 +11. Switch Jumper
1158 1158  
1159 -(% border="1" style="background-color:#ffffcc; color:green; width:515px" %)
1160 -|=(% style="width: 124px;" %)**Switch Jumper**|=(% style="width: 388px;" %)**Feature**
1161 -|(% style="width:124px" %)**SW1**|(% style="width:388px" %)(((
973 +|**Switch Jumper**|**Feature**
974 +|**SW1**|(((
1162 1162  ISP position: Upgrade firmware via UART
1163 1163  
1164 1164  Flash position: Configure device, check running status.
1165 1165  )))
1166 -|(% style="width:124px" %)**SW2**|(% style="width:388px" %)(((
979 +|**SW2**|(((
1167 1167  5V position: set to compatible with 5v I/O.
1168 1168  
1169 1169  3.3v position: set to compatible with 3.3v I/O.,
1170 1170  )))
1171 1171  
1172 -**+3.3V**: is always ON
985 ++3.3V: is always ON
1173 1173  
1174 -**+5V**: Only open before every sampling. The time is by default, it is AT+5VT=0.  Max open time. 5000 ms.
987 ++5V: Only open before every sampling. The time is by default, it is AT+5VT=0.  Max open time. 5000 ms.
1175 1175  
989 +1. Case Study
1176 1176  
1177 -= 4. Case Study =
991 +User can check this URL for some case studies.
1178 1178  
1179 -User can check this URL for some case studies: [[APP RS485 COMMUNICATE WITH SENSORS>>doc:Main.Application Note \: Communicate with Different Sensors ----- RS485-LN RS485-BL.WebHome]]
993 +[[http:~~/~~/wiki.dragino.com/index.php?title=APP_RS485_COMMUNICATE_WITH_SENSORS>>url:http://wiki.dragino.com/index.php?title=APP_RS485_COMMUNICATE_WITH_SENSORS]]
1180 1180  
1181 1181  
1182 -= 5. Use AT Command =
1183 1183  
1184 -== 5.1 Access AT Command ==
1185 1185  
998 +1. Use AT Command
999 +11. Access AT Command
1000 +
1186 1186  RS485-BL supports AT Command set. User can use a USB to TTL adapter plus the 3.5mm Program Cable to connect to RS485-BL to use AT command, as below.
1187 1187  
1188 -[[image:1654135840598-282.png]]
1003 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image027.png]]
1189 1189  
1190 1190  
1191 -In PC, User needs to set (% style="color:blue" %)**serial tool**(%%)(such as [[putty>>url:https://www.chiark.greenend.org.uk/~~sgtatham/putty/latest.html]], SecureCRT) baud rate to (% style="color:green" %)**9600**(%%) to access to access serial console of RS485-BL. The default password is 123456. Below is the output for reference:
1006 +In PC, User needs to set **serial tool**(such as [[putty>>url:https://www.chiark.greenend.org.uk/~~sgtatham/putty/latest.html]], SecureCRT) baud rate to **9600** to access to access serial console of RS485-BL. The default password is 123456. Below is the output for reference:
1192 1192  
1193 -[[image:1654136105500-922.png]]
1008 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image028.png]]
1194 1194  
1195 1195  
1196 -More detail AT Command manual can be found at [[AT Command Manual>>||anchor="3.5ConfigureRS485-BLviaATorDownlink"]]
1197 1197  
1012 +More detail AT Command manual can be found at [[AT Command Manual>>path:#AT_COMMAND]]
1198 1198  
1199 -== 5.2 Common AT Command Sequence ==
1200 1200  
1201 -=== 5.2.1 Multi-channel ABP mode (Use with SX1301/LG308) ===
1202 1202  
1016 +1.
1017 +11. Common AT Command Sequence
1018 +111. Multi-channel ABP mode (Use with SX1301/LG308)
1019 +
1203 1203  If device has not joined network yet:
1204 1204  
1205 -(% class="box infomessage" %)
1206 -(((
1207 -**AT+FDR**
1208 -)))
1022 +AT+FDR
1209 1209  
1210 -(% class="box infomessage" %)
1211 -(((
1212 -**AT+NJM=0**
1213 -)))
1024 +AT+NJM=0
1214 1214  
1215 -(% class="box infomessage" %)
1216 -(((
1217 -**ATZ**
1218 -)))
1026 +ATZ
1219 1219  
1220 1220  
1221 1221  If device already joined network:
1222 1222  
1223 -(% class="box infomessage" %)
1224 -(((
1225 -**AT+NJM=0**
1226 -)))
1031 +AT+NJM=0
1227 1227  
1228 -(% class="box infomessage" %)
1229 -(((
1230 -**ATZ**
1231 -)))
1033 +ATZ
1232 1232  
1035 +1.
1036 +11.
1037 +111. Single-channel ABP mode (Use with LG01/LG02)
1233 1233  
1234 -=== 5.5.2 Single-channel ABP mode (Use with LG01/LG02) ===
1039 +AT+FDR   Reset Parameters to Factory Default, Keys Reserve
1235 1235  
1041 +AT+NJM=0 Set to ABP mode
1236 1236  
1237 -(% style="background-color:#dcdcdc" %)**AT+FDR** (%%) Reset Parameters to Factory Default, Keys Reserve
1043 +AT+ADR=0 Set the Adaptive Data Rate Off
1238 1238  
1239 -(% style="background-color:#dcdcdc" %)**AT+NJM=0 **(%%)Set to ABP mode
1045 +AT+DR=5  Set Data Rate
1240 1240  
1241 -(% style="background-color:#dcdcdc" %)**AT+ADR=0** (%%)Set the Adaptive Data Rate Off
1047 +AT+TDC=60000  Set transmit interval to 60 seconds
1242 1242  
1243 -(% style="background-color:#dcdcdc" %)**AT+DR=5**  (%%)Set Data Rate
1049 +AT+CHS=868400000 Set transmit frequency to 868.4Mhz
1244 1244  
1245 -(% style="background-color:#dcdcdc" %)**AT+TDC=60000** (%%) Set transmit interval to 60 seconds
1051 +AT+RX2FQ=868400000 Set RX2Frequency to 868.4Mhz (according to the result from server)
1246 1246  
1247 -(% style="background-color:#dcdcdc" %)**AT+CHS=868400000**(%%) Set transmit frequency to 868.4Mhz
1053 +AT+RX2DR=5  Set RX2DR to match the downlink DR from server. see below
1248 1248  
1249 -(% style="background-color:#dcdcdc" %)**AT+RX2FQ=868400000** (%%) Set RX2Frequency to 868.4Mhz (according to the result from server)
1055 +AT+DADDR=26 01 1A F1 Set Device Address to 26 01 1A F1, this ID can be found in the LoRa Server portal.
1250 1250  
1251 -(% style="background-color:#dcdcdc" %)**AT+RX2DR=5**  (%%) Set RX2DR to match the downlink DR from server. see below
1057 +ATZ          Reset MCU
1252 1252  
1253 -(% style="background-color:#dcdcdc" %)**AT+DADDR=26** (%%) 01 1A F1 Set Device Address to 26 01 1A F1, this ID can be found in the LoRa Server portal.
1059 +**Note:**
1254 1254  
1255 -(% style="background-color:#dcdcdc" %)**ATZ**       (%%) Reset MCU
1061 +1. Make sure the device is set to ABP mode in the IoT Server.
1062 +1. Make sure the LG01/02 gateway RX frequency is exactly the same as AT+CHS setting.
1063 +1. Make sure SF / bandwidth setting in LG01/LG02 match the settings of AT+DR. refer [[this link>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/&file=LoRaWAN%201.0.3%20Regional%20Parameters.xlsx]] to see what DR means.
1064 +1. The command AT+RX2FQ and AT+RX2DR is to let downlink work. to set the correct parameters, user can check the actually downlink parameters to be used. As below. Which shows the RX2FQ should use 868400000 and RX2DR should be 5
1256 1256  
1066 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image029.png]]
1257 1257  
1258 -(% style="color:red" %)**Note:**
1259 1259  
1260 -(% style="color:red" %)1. Make sure the device is set to ABP mode in the IoT Server.
1261 -2. Make sure the LG01/02 gateway RX frequency is exactly the same as AT+CHS setting.
1262 -3. Make sure SF / bandwidth setting in LG01/LG02 match the settings of AT+DR. refer [[this link>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/&file=LoRaWAN%201.0.3%20Regional%20Parameters.xlsx]] to see what DR means.
1263 -4. The command AT+RX2FQ and AT+RX2DR is to let downlink work. to set the correct parameters, user can check the actually downlink parameters to be used. As below. Which shows the RX2FQ should use 868400000 and RX2DR should be 5
1069 +1. FAQ
1070 +11. How to upgrade the image?
1264 1264  
1265 -[[image:1654136435598-589.png]]
1266 -
1267 -
1268 -= 6. FAQ =
1269 -
1270 -== 6.1 How to upgrade the image? ==
1271 -
1272 1272  The RS485-BL LoRaWAN Controller is shipped with a 3.5mm cable, the cable is used to upload image to RS485-BL to:
1273 1273  
1274 1274  * Support new features
... ... @@ -1277,7 +1277,7 @@
1277 1277  
1278 1278  Below shows the hardware connection for how to upload an image to RS485-BL:
1279 1279  
1280 -[[image:1654136646995-976.png]]
1080 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image030.png]]
1281 1281  
1282 1282  **Step1:** Download [[flash loader>>url:https://www.st.com/content/st_com/en/products/development-tools/software-development-tools/stm32-software-development-tools/stm32-programmers/flasher-stm32.html]].
1283 1283  
... ... @@ -1285,95 +1285,97 @@
1285 1285  
1286 1286  **Step3: **Open flashloader; choose the correct COM port to update.
1287 1287  
1288 -[[image:image-20220602102605-1.png]]
1289 1289  
1089 +|(((
1090 +HOLD PRO then press the RST button, SYS will be ON, then click next
1091 +)))
1290 1290  
1291 -[[image:image-20220602102637-2.png]]
1093 +|(((
1094 +Board detected
1095 +)))
1292 1292  
1097 +|(((
1098 +
1099 +)))
1293 1293  
1294 -[[image:image-20220602102715-3.png]]
1101 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image031.png]] [[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image032.png]]
1295 1295  
1296 1296  
1297 1297  
1298 -== 6.2 How to change the LoRa Frequency Bands/Region? ==
1105 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image033.png]] [[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image034.png]]
1299 1299  
1300 -User can follow the introduction for [[how to upgrade image>>||anchor="H6.1Howtoupgradetheimage3F"]]. When download the images, choose the required image file for download.
1301 1301  
1108 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image035.png]] [[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image036.png]]
1302 1302  
1303 1303  
1304 -== 6.3 How many RS485-Slave can RS485-BL connects? ==
1111 +1.
1112 +11. How to change the LoRa Frequency Bands/Region?
1305 1305  
1306 -The RS485-BL can support max 32 RS485 devices. Each uplink command of RS485-BL can support max 16 different RS485 command. So RS485-BL can support max 16 RS485 devices pre-program in the device for uplink. For other devices no pre-program, user can use the [[downlink message (type code 0xA8) to poll their info>>||anchor="H3.3.3Configurereadcommandsforeachsampling"]].
1114 +User can follow the introduction for [[how to upgrade image>>path:#upgrade_image]]. When download the images, choose the required image file for download.
1307 1307  
1308 1308  
1309 1309  
1310 -= 7. Trouble Shooting =
1118 +1.
1119 +11. How many RS485-Slave can RS485-BL connects?
1311 1311  
1121 +The RS485-BL can support max 32 RS485 devices. Each uplink command of RS485-BL can support max 16 different RS485 command. So RS485-BL can support max 16 RS485 devices pre-program in the device for uplink. For other devices no pre-program, user can use the [[downlink message (type code 0xA8) to poll their info>>path:#downlink_A8]].
1312 1312  
1313 -== 7.1 Downlink doesn’t work, how to solve it? ==
1314 1314  
1315 -Please see this link for debug: [[LoRaWAN Communication Debug>>doc:Main.LoRaWAN Communication Debug.WebHome]]
1316 1316  
1317 1317  
1318 -== 7.2 Why I can’t join TTN V3 in US915 /AU915 bands? ==
1126 +1. Trouble Shooting     
1127 +11. Downlink doesn’t work, how to solve it?
1319 1319  
1320 -It might about the channels mapping. Please see for detail: [[Notice of Frequency band>>doc:Main.LoRaWAN Communication Debug.WebHome||anchor="H2.NoticeofUS9152FCN4702FAU915Frequencyband"]]
1129 +Please see this link for debug:
1321 1321  
1131 +[[http:~~/~~/wiki.dragino.com/index.php?title=Main_Page#LoRaWAN_Communication_Debug>>url:http://wiki.dragino.com/index.php?title=Main_Page#LoRaWAN_Communication_Debug]] 
1322 1322  
1323 -= 8. Order Info =
1324 1324  
1325 -(% style="color:blue" %)**Part Number: RS485-BL-XXX**
1326 1326  
1327 -(% style="color:blue" %)**XXX:**
1135 +1.
1136 +11. Why I can’t join TTN V3 in US915 /AU915 bands?
1328 1328  
1329 -* (% style="color:blue" %)**EU433**(%%): frequency bands EU433
1330 -* (% style="color:blue" %)**EU868**(%%): frequency bands EU868
1331 -* (% style="color:blue" %)**KR920**(%%): frequency bands KR920
1332 -* (% style="color:blue" %)**CN470**(%%): frequency bands CN470
1333 -* (% style="color:blue" %)**AS923**(%%): frequency bands AS923
1334 -* (% style="color:blue" %)**AU915**(%%): frequency bands AU915
1335 -* (% style="color:blue" %)**US915**(%%): frequency bands US915
1336 -* (% style="color:blue" %)**IN865**(%%): frequency bands IN865
1337 -* (% style="color:blue" %)**RU864**(%%): frequency bands RU864
1338 -* (% style="color:blue" %)**KZ865**(%%): frequency bands KZ865
1138 +It might about the channels mapping. Please see for detail.
1339 1339  
1140 +[[http:~~/~~/wiki.dragino.com/index.php?title=LoRaWAN_Communication_Debug#Notice_of_US915.2FCN470.2FAU915_Frequency_band>>url:http://wiki.dragino.com/index.php?title=LoRaWAN_Communication_Debug#Notice_of_US915.2FCN470.2FAU915_Frequency_band]]
1340 1340  
1341 -= 9. Packing Info =
1342 1342  
1343 -(((
1143 +
1144 +1. Order Info
1145 +
1146 +**Part Number: RS485-BL-XXX**
1147 +
1148 +**XXX:**
1149 +
1150 +* **EU433**: frequency bands EU433
1151 +* **EU868**: frequency bands EU868
1152 +* **KR920**: frequency bands KR920
1153 +* **CN470**: frequency bands CN470
1154 +* **AS923**: frequency bands AS923
1155 +* **AU915**: frequency bands AU915
1156 +* **US915**: frequency bands US915
1157 +* **IN865**: frequency bands IN865
1158 +* **RU864**: frequency bands RU864
1159 +* **KZ865: **frequency bands KZ865
1160 +
1161 +1. Packing Info
1162 +
1344 1344  **Package Includes**:
1345 -)))
1346 1346  
1347 -* (((
1348 -RS485-BL x 1
1349 -)))
1350 -* (((
1351 -Stick Antenna for LoRa RF part x 1
1352 -)))
1353 -* (((
1354 -Program cable x 1
1355 -)))
1165 +* RS485-BL x 1
1166 +* Stick Antenna for LoRa RF part x 1
1167 +* Program cable x 1
1356 1356  
1357 -(((
1358 1358  **Dimension and weight**:
1359 -)))
1360 1360  
1361 -* (((
1362 -Device Size: 13.5 x 7 x 3 cm
1363 -)))
1364 -* (((
1365 -Device Weight: 105g
1366 -)))
1367 -* (((
1368 -Package Size / pcs : 14.5 x 8 x 5 cm
1369 -)))
1370 -* (((
1371 -Weight / pcs : 170g
1171 +* Device Size: 13.5 x 7 x 3 cm
1172 +* Device Weight: 105g
1173 +* Package Size / pcs : 14.5 x 8 x 5 cm
1174 +* Weight / pcs : 170g
1372 1372  
1373 -
1374 -)))
1176 +1. Support
1375 1375  
1376 -= 10. Support =
1377 -
1378 1378  * Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule.
1379 -* Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[support@dragino.com>>url:file:///D:/市场资料/说明书/LoRa/LT系列/support@dragino.com]]
1179 +* Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to
1180 +
1181 +[[support@dragino.com>>url:file:///D:/市场资料/说明书/LoRa/LT系列/support@dragino.com]]
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
1654132684752-193.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -22.8 KB
Content
1654133913295-597.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -116.2 KB
Content
1654133954153-643.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -91.2 KB
Content
1654134704555-320.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -91.4 KB
Content
1654135840598-282.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -1.3 MB
Content
1654136105500-922.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -203.7 KB
Content
1654136435598-589.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -158.9 KB
Content
1654136646995-976.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -1.3 MB
Content
image-20220602102605-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -102.6 KB
Content
image-20220602102637-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -250.8 KB
Content
image-20220602102715-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -176.2 KB
Content