Skip to Content
Last modified by Mengting Qiu on 2025/07/14 09:59
From version 32.5
edited by Xiaoling
on 2022/06/02 15:25
Change comment: There is no comment for this version
To version 58.38
edited by Xiaoling
on 2022/06/06 11:56
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -6,12 +6,18 @@
6 6  **RS485-LN – RS485 to LoRaWAN Converter User Manual**
7 7  
8 8  
9 +
10 +
9 9  **Table of Contents:**
10 10  
13 +{{toc/}}
11 11  
12 12  
13 13  
14 14  
18 +
19 +
20 +
15 15  = 1.Introduction =
16 16  
17 17  == 1.1 What is RS485-LN RS485 to LoRaWAN Converter ==
... ... @@ -18,23 +18,33 @@
18 18  
19 19  (((
20 20  (((
27 +(((
21 21  The Dragino RS485-LN is a (% style="color:blue" %)**RS485 to LoRaWAN Converter**(%%). It converts the RS485 signal into LoRaWAN wireless signal which simplify the IoT installation and reduce the installation/maintaining cost.
22 22  )))
30 +)))
23 23  
24 24  (((
33 +(((
25 25  RS485-LN allows user to (% style="color:blue" %)**monitor / control RS485 devices**(%%) and reach extremely long ranges. It provides ultra-long range spread spectrum communication and high interference immunity whilst minimizing current consumption. It targets professional wireless sensor network applications such as irrigation systems, smart metering, smart cities, smartphone detection, building automation, and so on.
26 26  )))
36 +)))
27 27  
28 28  (((
39 +(((
29 29  (% style="color:blue" %)**For data uplink**(%%), RS485-LN sends user-defined commands to RS485 devices and gets the return from the RS485 devices. RS485-LN will process these returns according to user-define rules to get the final payload and upload to LoRaWAN server.
30 30  )))
42 +)))
31 31  
32 32  (((
45 +(((
33 33  (% style="color:blue" %)**For data downlink**(%%), RS485-LN runs in LoRaWAN Class C. When there downlink commands from LoRaWAN server, RS485-LN will forward the commands from LoRaWAN server to RS485 devices.
47 +)))
34 34  
49 +(((
35 35  (% style="color:blue" %)**Demo Dashboard for RS485-LN**(%%) connect to two energy meters: [[https:~~/~~/app.datacake.de/dashboard/d/58844a26-378d-4c5a-aaf5-b5b5b153447a>>url:https://app.datacake.de/dashboard/d/58844a26-378d-4c5a-aaf5-b5b5b153447a]]
36 36  )))
37 37  )))
53 +)))
38 38  
39 39  [[image:1653267211009-519.png||height="419" width="724"]]
40 40  
... ... @@ -41,6 +41,7 @@
41 41  
42 42  == 1.2 Specifications ==
43 43  
60 +
44 44  **Hardware System:**
45 45  
46 46  * STM32L072CZT6 MCU
... ... @@ -73,7 +73,7 @@
73 73  * Preamble detection.
74 74  * 127 dB Dynamic Range RSSI.
75 75  * Automatic RF Sense and CAD with ultra-fast AFC.
76 -* Packet engine up to 256 bytes with CRC.
93 +* Packet engine up to 256 bytes with CRC
77 77  
78 78  == 1.3 Features ==
79 79  
... ... @@ -99,15 +99,22 @@
99 99  
100 100  [[RS485-LN Image files – Download link and Change log>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/]]
101 101  
119 +
102 102  == 1.6 Hardware Change log ==
103 103  
104 104  (((
105 105  (((
124 +(((
106 106  v1.2: Add External Interrupt Pin.
126 +)))
107 107  
128 +(((
108 108  v1.0: Release
109 109  )))
131 +
132 +
110 110  )))
134 +)))
111 111  
112 112  = 2. Power ON Device =
113 113  
... ... @@ -122,6 +122,8 @@
122 122  )))
123 123  
124 124  [[image:1653268091319-405.png]]
149 +
150 +
125 125  )))
126 126  
127 127  = 3. Operation Mode =
... ... @@ -129,9 +129,13 @@
129 129  == 3.1 How it works? ==
130 130  
131 131  (((
158 +(((
132 132  The RS485-LN is configured as LoRaWAN OTAA Class C 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-LN. It will auto join the network via OTAA.
133 133  )))
134 134  
162 +
163 +)))
164 +
135 135  == 3.2 Example to join LoRaWAN network ==
136 136  
137 137  Here shows an example for how to join the TTN V3 Network. Below is the network structure, we use [[LG308>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/140-lg308.html]] as LoRaWAN gateway here. 
... ... @@ -138,15 +138,20 @@
138 138  
139 139  [[image:1653268155545-638.png||height="334" width="724"]]
140 140  
171 +
141 141  (((
173 +(((
142 142  The RS485-LN in this example connected to two RS485 devices for demonstration, user can connect to other RS485 devices via the same method. The connection is as below:
175 +)))
143 143  
177 +(((
144 144  485A+ and 485B- of the sensor are connected to RS485A and RA485B of RS485-LN respectively.
179 +)))
145 145  
146 146  [[image:1653268227651-549.png||height="592" width="720"]]
147 147  
148 148  (((
149 -The LG308 is already set to connect to [[TTN V3 network >>path:eu1.cloud.thethings.network/]]. So what we need to now is only configure the TTN V3:
184 +The LG308 is already set to connect to [[TTN V3 network >>path:https://www.thethingsnetwork.org/]]. So what we need to now is only configure the TTN V3:
150 150  )))
151 151  
152 152  (((
... ... @@ -193,15 +193,18 @@
193 193  
194 194  [[image:1652953568895-172.png||height="232" width="724"]]
195 195  
231 +
196 196  == 3.3 Configure Commands to read data ==
197 197  
198 198  (((
199 199  (((
200 -There are plenty of RS485 devices in the market and each device has different command to read the valid data. To support these devices in flexible, RS485-LN supports flexible command set. User can use [[AT Commands>>path:#AT_COMMAND]] or LoRaWAN Downlink Command to configure what commands RS485-LN should send for each sampling and how to handle the return from RS485 devices.
236 +There are plenty of RS485 devices in the market and each device has different command to read the valid data. To support these devices in flexible, RS485-LN supports flexible command set. User can use [[AT Commands>>||anchor="H3.5ConfigureRS485-BLviaATorDownlink"]] or LoRaWAN Downlink Command to configure what commands RS485-LN should send for each sampling and how to handle the return from RS485 devices.
201 201  )))
202 202  
203 203  (((
204 204  (% style="color:red" %)Note: below description and commands are for firmware version >v1.1, if you have firmware version v1.0. Please check the [[user manual v1.0>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/&file=RS485-LN_UserManual_v1.0.1.pdf]] or upgrade the firmware to v1.1
241 +
242 +
205 205  )))
206 206  )))
207 207  
... ... @@ -209,19 +209,19 @@
209 209  
210 210  To use RS485-LN to read data from RS485 sensors, connect the RS485-LN A/B traces to the sensors. And user need to make sure RS485-LN use the match UART setting to access the sensors. The related commands for UART settings are:
211 211  
212 -(% border="1" style="background-color:#ffffcc; color:green; width:795px" %)
213 -|(((
250 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
251 +|=(% style="width: 110px;" %)(((
214 214  **AT Commands**
215 -)))|(% style="width:285px" %)(((
253 +)))|=(% style="width: 190px;" %)(((
216 216  **Description**
217 -)))|(% style="width:347px" %)(((
255 +)))|=(% style="width: 190px;" %)(((
218 218  **Example**
219 219  )))
220 -|(((
258 +|(% style="width:110px" %)(((
221 221  AT+BAUDR
222 -)))|(% style="width:285px" %)(((
260 +)))|(% style="width:190px" %)(((
223 223  Set the baud rate (for RS485 connection). Default Value is: 9600.
224 -)))|(% style="width:347px" %)(((
262 +)))|(% style="width:190px" %)(((
225 225  (((
226 226  AT+BAUDR=9600
227 227  )))
... ... @@ -230,11 +230,11 @@
230 230  Options: (1200,2400,4800,14400,19200,115200)
231 231  )))
232 232  )))
233 -|(((
271 +|(% style="width:110px" %)(((
234 234  AT+PARITY
235 -)))|(% style="width:285px" %)(((
273 +)))|(% style="width:190px" %)(((
236 236  Set UART parity (for RS485 connection)
237 -)))|(% style="width:347px" %)(((
275 +)))|(% style="width:190px" %)(((
238 238  (((
239 239  AT+PARITY=0
240 240  )))
... ... @@ -243,9 +243,9 @@
243 243  Option: 0: no parity, 1: odd parity, 2: even parity
244 244  )))
245 245  )))
246 -|(((
284 +|(% style="width:110px" %)(((
247 247  AT+STOPBIT
248 -)))|(% style="width:285px" %)(((
286 +)))|(% style="width:190px" %)(((
249 249  (((
250 250  Set serial stopbit (for RS485 connection)
251 251  )))
... ... @@ -253,7 +253,7 @@
253 253  (((
254 254  
255 255  )))
256 -)))|(% style="width:347px" %)(((
294 +)))|(% style="width:190px" %)(((
257 257  (((
258 258  AT+STOPBIT=0 for 1bit
259 259  )))
... ... @@ -275,90 +275,47 @@
275 275  )))
276 276  )))
277 277  
278 -(% border="1" style="background-color:#ffffcc; color:green; width:806px" %)
279 -|**AT Commands**|(% style="width:418px" %)**Description**|(% style="width:256px" %)**Example**
280 -|AT+CFGDEV|(% style="width:418px" %)(((
316 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
317 +|=(% style="width: 110px;" %)**AT Commands**|=(% style="width: 190px;" %)**Description**|=(% style="width: 190px;" %)**Example**
318 +|AT+CFGDEV|(% style="width:110px" %)(((
281 281  This command is used to configure the RS485/TTL devices; they won’t be used during sampling.
282 282  
283 283  AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,
284 284  
285 285  mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
286 -)))|(% style="width:256px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
324 +)))|(% style="width:190px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
287 287  
288 288  === 3.3.3 Configure read commands for each sampling ===
289 289  
290 290  (((
291 -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.
292 -)))
329 +During each sampling, we need confirm what commands we need to send to the RS485 sensors to read data. After the RS485 sensors send back the value, it normally include some bytes and we only need a few from them for a shorten payload.
293 293  
294 -(((
295 -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.
296 -)))
297 -
298 -(((
299 299  To save the LoRaWAN network bandwidth, we might need to read data from different sensors and combine their valid value into a short payload.
300 -)))
301 301  
302 -(((
303 303  This section describes how to achieve above goals.
304 -)))
305 305  
306 -(((
307 -During each sampling, the RS485-BL can support 15 commands to read sensors. And combine the return to one or several uplink payloads.
308 -)))
335 +During each sampling, the RS485-LN can support 15 commands to read sensors. And combine the return to one or several uplink payloads.
309 309  
310 -(((
311 -**Command from RS485-BL to Sensor:**
312 -)))
313 313  
314 -(((
315 -RS485-BL can send out pre-set max 15 strings via **AT+COMMAD1**, **ATCOMMAND2**,…, to **AT+COMMANDF** . All commands are of same grammar.
316 -)))
338 +**Each RS485 commands include two parts:**
317 317  
318 -(((
319 -**Handle return from sensors to RS485-BL**:
320 -)))
340 +~1. What commands RS485-LN will send to the RS485 sensors. There are total 15 commands from **AT+COMMAD1**, **ATCOMMAND2**,…, to **AT+COMMANDF**. All commands are of same grammar.
321 321  
322 -(((
323 -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**
324 -)))
342 +2. How to get wanted value the from RS485 sensors returns from by 1). There are total 15 AT Commands to handle the return, commands are **AT+DATACUT1**,**AT+DATACUT2**,…, **AT+DATACUTF** corresponding to the commands from 1). All commands are of same grammar.
325 325  
326 -* (((
327 -**AT+DATACUT**
328 -)))
344 +3. 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
329 329  
330 -(((
331 -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.
332 -)))
333 333  
334 -* (((
335 -**AT+SEARCH**
336 -)))
337 -
338 -(((
339 -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.
340 -)))
341 -
342 -(((
343 -**Define wait timeout:**
344 -)))
345 -
346 -(((
347 -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
348 -)))
349 -
350 -(((
351 351  After we got the valid value from each RS485 commands, we need to combine them together with the command **AT+DATAUP**.
352 -)))
353 353  
354 -**Examples:**
355 355  
356 356  Below are examples for the how above AT Commands works.
357 357  
358 -**AT+COMMANDx : **This command will be sent to RS485/TTL devices during each sampling, Max command length is 14 bytes. The grammar is:
359 359  
360 -(% border="1" class="table-bordered" %)
361 -|(((
353 +**AT+COMMANDx : **This command will be sent to RS485 devices during each sampling, Max command length is 14 bytes. The grammar is:
354 +
355 +(% border="1" style="background-color:#4bacc6; color:white; width:499px" %)
356 +|(% style="width:496px" %)(((
362 362  **AT+COMMANDx=xx xx xx xx xx xx xx xx xx xx xx xx,m**
363 363  
364 364  **xx xx xx xx xx xx xx xx xx xx xx xx: The RS485 command to be sent**
... ... @@ -366,49 +366,15 @@
366 366  **m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command**
367 367  )))
368 368  
369 -(((
370 370  For example, if we have a RS485 sensor. The command to get sensor value is: 01 03 0B B8 00 02 46 0A. Where 01 03 0B B8 00 02 is the Modbus command to read the register 0B B8 where stored the sensor value. The 46 0A is the CRC-16/MODBUS which calculate manually.
371 -)))
372 372  
373 -(((
374 -In the RS485-BL, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
375 -)))
366 +In the RS485-LN, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
376 376  
377 -(((
378 -**AT+SEARCHx**: This command defines how to handle the return from AT+COMMANDx.
379 -)))
380 380  
381 -(% border="1" class="table-bordered" %)
382 -|(((
383 -**AT+SEARCHx=aa,xx xx xx xx xx**
384 -
385 -* **aa: 1: prefix match mode; 2: prefix and suffix match mode**
386 -* **xx xx xx xx xx: match string. Max 5 bytes for prefix and 5 bytes for suffix**
387 -
388 -
389 -)))
390 -
391 -**Examples:**
392 -
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 -
395 -If we set AT+SEARCH1=1,1E 56 34.      (max 5 bytes for prefix)
396 -
397 -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**
398 -
399 -[[image:1653269403619-508.png]]
400 -
401 -2. For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
402 -
403 -If we set AT+SEARCH1=2, 1E 56 34+31 00 49
404 -
405 -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**
406 -
407 -[[image:1653269438444-278.png]]
408 -
409 409  **AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes.
410 410  
411 -|(((
371 +(% border="1" style="background-color:#4bacc6; color:white; width:510px" %)
372 +|(% style="width:510px" %)(((
412 412  **AT+DATACUTx=a,b,c**
413 413  
414 414  * **a: length for the return of AT+COMMAND**
... ... @@ -416,48 +416,37 @@
416 416  * **c: define the position for valid value.  **
417 417  )))
418 418  
419 -Examples:
380 +**Examples:**
420 420  
421 421  * Grab bytes:
422 422  
423 -[[image:1653269551753-223.png||height="311" width="717"]]
384 +[[image:image-20220602153621-1.png]]
424 424  
386 +
425 425  * Grab a section.
426 426  
427 -[[image:1653269568276-930.png||height="325" width="718"]]
389 +[[image:image-20220602153621-2.png]]
428 428  
391 +
429 429  * Grab different sections.
430 430  
431 -[[image:1653269593172-426.png||height="303" width="725"]]
394 +[[image:image-20220602153621-3.png]]
432 432  
433 -(% style="color:red" %)**Note:**
396 +
397 +)))
434 434  
435 -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.
436 -
437 -Example:
438 -
439 -(% style="color:red" %)AT+COMMAND1=11 01 1E D0,0
440 -
441 -(% style="color:red" %)AT+SEARCH1=1,1E 56 34
442 -
443 -(% style="color:red" %)AT+DATACUT1=0,2,1~~5
444 -
445 -(% style="color:red" %)Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
446 -
447 -(% style="color:red" %)String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
448 -
449 -(% style="color:red" %)Valid payload after DataCUT command: 2e 30 58 5f 36
450 -
451 -[[image:1653269618463-608.png]]
452 -
453 453  === 3.3.4 Compose the uplink payload ===
454 454  
455 455  (((
456 456  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.**
403 +
404 +
457 457  )))
458 458  
459 459  (((
460 -(% style="color:#4f81bd" %)**Examples: AT+DATAUP=0**
408 +(% style="color:#037691" %)**Examples: AT+DATAUP=0**
409 +
410 +
461 461  )))
462 462  
463 463  (((
... ... @@ -478,8 +478,10 @@
478 478  
479 479  [[image:1653269759169-150.png||height="513" width="716"]]
480 480  
481 -(% style="color:#4f81bd" %)**Examples: AT+DATAUP=1**
482 482  
432 +(% style="color:#037691" %)**Examples: AT+DATAUP=1**
433 +
434 +
483 483  Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**Multiply UPLINKs**.
484 484  
485 485  Final Payload is
... ... @@ -486,700 +486,1030 @@
486 486  
487 487  (% style="color:#4f81bd" %)**Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA**
488 488  
489 -1. Battery Info (2 bytes): Battery voltage
490 -1. PAYVER (1 byte): Defined by AT+PAYVER
491 -1. PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling.
492 -1. PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
493 -1. 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
494 494  
495 -[[image:1653269916228-732.png||height="433" width="711"]]
442 +1. PAYVER: Defined by AT+PAYVER
443 +1. PAYLOAD COUNT: Total how many uplinks of this sampling.
444 +1. PAYLOAD#: Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
445 +1. DATA: Valid value: max 8 bytes for each uplink so each uplink <= 11 bytes. For the last uplink, DATA will might less than 8 bytes
496 496  
447 +[[image:image-20220602155039-4.png]]
497 497  
498 -So totally there will be 3 uplinks for this sampling, each uplink includes 6 bytes DATA
499 499  
500 -DATA1=RETURN1 Valid Value = (% style="background-color:green; color:white" %)20 20 0a 33 90 41
450 +So totally there will be 3 uplinks for this sampling, each uplink include 8 bytes DATA
501 501  
502 -DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10=(% style="background-color:green; color:white" %) 02 aa 05 81 0a 20
452 +DATA1=RETURN1 Valid Value + the first two of Valid value of RETURN10= **20 20 0a 33 90 41 02 aa**
503 503  
504 -DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 = (% style="background-color:green; color:white" %)20 20 20 2d 30
454 +DATA2=3^^rd^^ ~~ 10^^th^^ byte of Valid value of RETURN10= **05 81 0a 20 20 20 20 2d**
505 505  
506 -Below are the uplink payloads:
456 +DATA3=the rest of Valid value of RETURN10= **30**
507 507  
508 -[[image:1653270130359-810.png]]
509 509  
459 +(% style="color:red" %)Notice: In firmware v1.3, the Max bytes has been changed according to the max bytes in different Frequency Bands for lowest SF. As below:
510 510  
511 -(% style="color:red" %)**Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:**
461 + ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink.
512 512  
513 - ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink ( so 51 -5 = 46 max valid date)
463 + * For AU915/AS923 bands, if UplinkDwell time=0, max 11 bytes for each uplink.
514 514  
515 - * For AU915/AS923 bands, if UplinkDwell time=1, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date).
465 + * For US915 band, max 11 bytes for each uplink.
516 516  
517 - * For US915 band, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date).
467 + ~* For all other bands: max 51 bytes for each uplink.
518 518  
519 - ~* For all other bands: max 51 bytes for each uplink  ( so 51 -5 = 46 max valid date).
520 520  
521 -=== 3.3.5 Uplink on demand ===
470 +Below are the uplink payloads:
522 522  
523 -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.
472 +[[image:1654157178836-407.png]]
524 524  
525 -Downlink control command:
526 526  
527 -[[0x08 command>>path:#downlink_08]]: Poll an uplink with current command set in RS485-BL.
475 +=== 3.3.5 Uplink on demand ===
528 528  
529 -[[0xA8 command>>path:#downlink_A8]]: Send a command to RS485-BL and uplink the output from sensors.
477 +Except uplink periodically, RS485-LN is able to uplink on demand. The server send downlink command to RS485-LN and RS485 will uplink data base on the command.
530 530  
479 +Downlink control command:
531 531  
481 +**0x08 command**: Poll an uplink with current command set in RS485-LN.
532 532  
533 -1.
534 -11.
535 -111. Uplink on Interrupt
483 +**0xA8 command**: Send a command to RS485-LN and uplink the output from sensors.
536 536  
537 -Put the interrupt sensor between 3.3v_out and GPIO ext.[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image022.png]]
538 538  
539 -AT+INTMOD=0  Disable Interrupt
540 540  
541 -AT+INTMOD=1  Interrupt trigger by rising or falling edge.
487 +=== 3.3.6 Uplink on Interrupt ===
542 542  
543 -AT+INTMOD=2  Interrupt trigger by falling edge. ( Default Value)
489 +RS485-LN support external Interrupt uplink since hardware v1.2 release.
544 544  
545 -AT+INTMOD=3  Interrupt trigger by rising edge.
491 +[[image:1654157342174-798.png]]
546 546  
493 +Connect the Interrupt pin to RS485-LN INT port and connect the GND pin to V- port. When there is a high voltage (Max 24v) on INT pin. Device will send an uplink packet.
547 547  
548 -1.
549 -11. Uplink Payload
550 550  
551 -|**Size(bytes)**|**2**|**1**|**Length depends on the return from the commands**
552 -|Value|(((
553 -Battery(mV)
496 +== 3.4 Uplink Payload ==
554 554  
555 -&
556 556  
557 -Interrupt _Flag
558 -)))|(((
559 -PAYLOAD_VER
499 +[[image:image-20220606110929-1.png]]
560 560  
561 -
562 -)))|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.
563 -
564 564  Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors.
565 565  
566 566  
567 -function Decoder(bytes, port) {
504 +== 3.5 Configure RS485-BL via AT or Downlink ==
568 568  
569 -~/~/Payload Formats of RS485-BL Deceive
506 +(((
507 +User can configure RS485-LN via AT Commands or LoRaWAN Downlink Commands
508 +)))
570 570  
571 -return {
572 -
573 - ~/~/Battery,units:V
574 -
575 - BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000,
576 -
577 - ~/~/GPIO_EXTI 
578 -
579 - EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE",
580 -
581 - ~/~/payload of version
582 -
583 - Pay_ver:bytes[2],
584 -
585 - };
586 -
587 - }
588 -
589 -
590 -
591 -
592 -
593 -
594 -
595 -TTN V3 uplink screen shot.
596 -
597 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]
598 -
599 -1.
600 -11. Configure RS485-BL via AT or Downlink
601 -
602 -User can configure RS485-BL via [[AT Commands >>path:#_​Using_the_AT]]or LoRaWAN Downlink Commands
603 -
510 +(((
604 604  There are two kinds of Commands:
512 +)))
605 605  
606 -* **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
514 +* (((
515 +(% 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]]
516 +)))
607 607  
608 -* **Sensor Related Commands**: These commands are special designed for RS485-BL.  User can see these commands below:
518 +* (((
519 +(% style="color:#4f81bd" %)**Sensor Related Commands**(%%): These commands are special designed for RS485-LN.  User can see these commands below:
520 +)))
609 609  
610 -1.
611 -11.
612 -111. Common Commands:
522 +(((
523 +
524 +)))
613 613  
614 -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]]
615 615  
527 +=== 3.5.1 Common Commands ===
616 616  
617 -1.
618 -11.
619 -111. Sensor related commands:
529 +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]]
620 620  
621 -==== Choose Device Type (RS485 or TTL) ====
622 622  
623 -RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect.
532 +=== 3.5.2 Sensor related commands ===
624 624  
625 -* AT Command
534 +Response feature is added to the server's downlink, a special package with a FPort of 200 will be uploaded immediately after receiving the data sent by the server.
626 626  
627 -**AT+MOD=1** ~/~/ Set to support RS485-MODBUS type sensors. User can connect multiply RS485 , Modbus sensors to the A / B pins.
536 +[[image:image-20220602163333-5.png||height="263" width="1160"]]
628 628  
629 -**AT+MOD=2** ~/~/ Set to support TTL Level sensors, User can connect one TTL Sensor to the TXD/RXD/GND pins.
538 +The first byte of this package represents whether the configuration is successful, 00 represents failure, 01 represents success. Except for the first byte, the other is the previous downlink. (All commands except A8 type commands are applicable)
630 630  
631 631  
632 -* Downlink Payload
541 +=== 3.5.3 Sensor related commands ===
633 633  
634 -**0A aa**     à same as AT+MOD=aa
635 635  
636 636  
637 637  
638 -==== [[RS485 Debug Command>>path:#downlink_A8]] (AT+CFGDEV) ====
546 +==== **RS485 Debug Command** ====
639 639  
640 -This command is used to configure the RS485 or TTL sensors; they won’t be used during sampling.
548 +(((
549 +This command is used to configure the RS485 devices; they won’t be used during sampling.
550 +)))
641 641  
642 -* AT Command
552 +* (((
553 +**AT Command**
554 +)))
643 643  
644 -AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
556 +(% class="box infomessage" %)
557 +(((
558 +(((
559 +**AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m**
560 +)))
561 +)))
645 645  
646 -m: 0: no CRC; 1: add CRC-16/MODBUS in the end of this command.
563 +(((
564 +m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
565 +)))
647 647  
567 +* (((
568 +**Downlink Payload**
569 +)))
648 648  
649 -
650 -* Downlink Payload
651 -
571 +(((
652 652  Format: A8 MM NN XX XX XX XX YY
573 +)))
653 653  
575 +(((
654 654  Where:
577 +)))
655 655  
656 -* MM: 1: add CRC-16/MODBUS ; 0: no CRC
657 -* NN: The length of RS485 command
658 -* XX XX XX XX: RS485 command total NN bytes
659 -* YY: How many bytes will be uplink from the return of this RS485 command, if YY=0, RS485-BL will execute the downlink command without uplink; if YY>0, RS485-BL will uplink total YY bytes from the output of this RS485 command
579 +* (((
580 +MM: 1: add CRC-16/MODBUS ; 0: no CRC
581 +)))
582 +* (((
583 +NN: The length of RS485 command
584 +)))
585 +* (((
586 +XX XX XX XX: RS485 command total NN bytes
587 +)))
588 +* (((
589 +(((
590 +YY: How many bytes will be uplink from the return of this RS485 command,
591 +)))
660 660  
661 -**Example 1:**
593 +* (((
594 +if YY=0, RS485-LN will execute the downlink command without uplink;
595 +)))
596 +* (((
597 +if YY>0, RS485-LN will uplink total YY bytes from the output of this RS485 command; Fport=200
598 +)))
599 +* (((
600 +if YY=FF, RS485-LN will uplink RS485 output with the downlink command content; Fport=200.
601 +)))
602 +)))
662 662  
604 +(((
605 +**Example 1** ~-~-> Configure without ask for uplink (YY=0)
606 +)))
607 +
608 +(((
663 663  To connect a Modbus Alarm with below commands.
610 +)))
664 664  
665 -* 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.
612 +* (((
613 +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.
614 +)))
666 666  
667 -* 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.
616 +* (((
617 +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.
618 +)))
668 668  
620 +(((
669 669  So if user want to use downlink command to control to RS485 Alarm, he can use:
622 +)))
670 670  
671 -**A8 01 06 0A 05 00 04 00 01 00**: to activate the RS485 Alarm
624 +(((
625 +(% style="color:#4f81bd" %)**A8 01 06 0A 05 00 04 00 01 00**(%%): to activate the RS485 Alarm
626 +)))
672 672  
673 -**A8 01 06 0A 05 00 04 00 00 00**: to deactivate the RS485 Alarm
628 +(((
629 +(% style="color:#4f81bd" %)**A8 01 06 0A 05 00 04 00 00 00**(%%): to deactivate the RS485 Alarm
630 +)))
674 674  
632 +(((
675 675  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.
634 +)))
676 676  
636 +(((
637 +
638 +)))
677 677  
678 -**Example 2:**
640 +(((
641 +**Example 2** ~-~-> Configure with requesting uplink and original downlink command (**YY=FF**)
642 +)))
679 679  
680 -Check TTL Sensor return:
644 +(((
645 +User in IoT server send a downlink command: (% style="color:#4f81bd" %)**A8 01 06 0A 08 00 04 00 01 YY**
646 +)))
681 681  
682 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image024.png]]
648 +(((
649 +
650 +)))
683 683  
652 +(((
653 +RS485-LN got this downlink command and send (% style="color:#4f81bd" %)**0A 08 00 04 00 01 **(%%)to Modbus network. One of the RS485 sensor in the network send back Modbus reply **0A 08 00 04 00 00**. RS485-LN get this reply and combine with the original downlink command and uplink. The uplink message is:
654 +)))
684 684  
656 +(((
657 + **A8** (% style="color:#4f81bd" %)**0A 08 00 04 00  **(% style="color:red" %)**01 06** ** **(% style="color:green" %)**0A 08 00 04 00 00**
658 +)))
685 685  
660 +(((
661 + [[image:1654159460680-153.png]]
662 +)))
686 686  
687 -==== Set Payload version ====
688 688  
665 +
666 +
667 +==== **Set Payload version** ====
668 +
669 +(((
689 689  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.
671 +)))
690 690  
691 -* AT Command:
673 +* (((
674 +**AT Command:**
675 +)))
692 692  
693 -AT+PAYVER: Set PAYVER field = 1
677 +(% class="box infomessage" %)
678 +(((
679 +(((
680 +**AT+PAYVER: Set PAYVER field = 1**
681 +)))
682 +)))
694 694  
684 +* (((
685 +**Downlink Payload:**
686 +)))
695 695  
696 -* Downlink Payload:
688 +(((
689 +**0xAE 01**  ~-~-> Set PAYVER field =  0x01
690 +)))
697 697  
698 -0xAE 01   à Set PAYVER field =  0x01
692 +(((
693 +**0xAE 0F**   ~-~-> Set PAYVER field =  0x0F
694 +)))
699 699  
700 -0xAE 0F   à Set PAYVER field =  0x0F
701 701  
702 702  
703 -==== Set RS485 Sampling Commands ====
704 704  
705 -AT+COMMANDx, AT+DATACUTx and AT+SEARCHx
699 +==== **Set RS485 Sampling Commands** ====
706 706  
707 -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]].
701 +(((
702 +AT+COMMANDx or AT+DATACUTx
703 +)))
708 708  
705 +(((
706 +These three commands are used to configure how the RS485-LN polling data from Modbus device. Detail of usage please see : [[polling RS485 device>>||anchor="H3.3.3Configurereadcommandsforeachsampling"]].
707 +)))
709 709  
710 -* AT Command:
709 +(((
710 +
711 +)))
711 711  
712 -AT+COMMANDx: Configure RS485 read command to sensor.
713 +* (((
714 +**AT Command:**
715 +)))
713 713  
714 -AT+DATACUTx: Configure how to handle return from RS485 devices.
717 +(% class="box infomessage" %)
718 +(((
719 +(((
720 +**AT+COMMANDx: Configure RS485 read command to sensor.**
721 +)))
722 +)))
715 715  
716 -AT+SEARCHx: Configure search command
724 +(% class="box infomessage" %)
725 +(((
726 +(((
727 +**AT+DATACUTx: Configure how to handle return from RS485 devices.**
728 +)))
729 +)))
717 717  
731 +(((
732 +
733 +)))
718 718  
719 -* Downlink Payload:
735 +* (((
736 +**Downlink Payload:**
737 +)))
720 720  
721 -0xAF downlink command can be used to set AT+COMMANDx or AT+DATACUTx.
739 +(((
740 +**0xAF** downlink command can be used to set AT+COMMANDx or AT+DATACUTx.
741 +)))
722 722  
723 -Note: if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink.
743 +(((
744 +(% style="color:red" %)**Note**(%%): if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink.
745 +)))
724 724  
747 +(((
725 725  Format: AF MM NN LL XX XX XX XX YY
749 +)))
726 726  
751 +(((
727 727  Where:
753 +)))
728 728  
729 -* MM: the ATCOMMAND or AT+DATACUT to be set. Value from 01 ~~ 0F,
730 -* NN: 0: no CRC; 1: add CRC-16/MODBUS ; 2: set the AT+DATACUT value.
731 -* LL: The length of AT+COMMAND or AT+DATACUT command
732 -* XX XX XX XX: AT+COMMAND or AT+DATACUT command
733 -* 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.
755 +* (((
756 +MM: the ATCOMMAND or AT+DATACUT to be set. Value from 01 ~~ 0F,
757 +)))
758 +* (((
759 +NN:  0: no CRC; 1: add CRC-16/MODBUS ; 2: set the AT+DATACUT value.
760 +)))
761 +* (((
762 +LL:  The length of AT+COMMAND or AT+DATACUT command
763 +)))
764 +* (((
765 +XX XX XX XX: AT+COMMAND or AT+DATACUT command
766 +)))
767 +* (((
768 +YY:  If YY=0, RS485-BL will execute the downlink command without uplink; if YY=1, RS485-LN will execute an uplink after got this command.
769 +)))
734 734  
735 -Example:
771 +(((
772 +**Example:**
773 +)))
736 736  
737 -**AF 03 01 06 0A 05 00 04 00 01 00**: Same as AT+COMMAND3=0A 05 00 04 00 01,1
775 +(((
776 +(% 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
777 +)))
738 738  
739 -**AF 03 02 06 10 01 05 06 09 0A 00**: Same as AT+DATACUT3=**16**,**1**,**5+6+9+10**
779 +(((
780 +(% 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**
781 +)))
740 740  
741 -**AF 03 02 06 0B 02 05 07 08 0A 00**: Same as AT+DATACUT3=**11**,**2**,**5~~7+8~~10**
783 +(((
784 +(% 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**
785 +)))
742 742  
743 743  
744 -0xAB downlink command can be used for set AT+SEARCHx
745 745  
746 -Example: **AB aa 01 03 xx xx xx** (03 here means there are total 3 bytes after 03) So
747 747  
748 -* AB aa 01 03 xx xx xx  same as AT+SEARCHaa=1,xx xx xx
749 -* 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
790 +==== **Fast command to handle MODBUS device** ====
750 750  
751 -**AB aa 02 03 xx xx xx 02 yy yy**  same as **AT+SEARCHaa=2,xx xx xx+yy yy**
792 +(((
793 +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]].
794 +)))
752 752  
796 +(((
797 +This command is valid since v1.3 firmware version
798 +)))
753 753  
754 -==== Fast command to handle MODBUS device ====
800 +(((
801 +AT+MBFUN 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.
802 +)))
755 755  
756 -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]].
804 +(((
805 +
806 +)))
757 757  
758 -This command is valid since v1.3 firmware version
808 +(((
809 +**Example:**
810 +)))
759 759  
812 +* (((
813 +AT+MBFUN=1 and AT+DATACUT1/AT+DATACUT2 are not configure (0,0,0). So RS485-LN.
814 +)))
815 +* (((
816 +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.
817 +)))
818 +* (((
819 +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.
820 +)))
760 760  
761 -AT+MBFUN has only two value:
822 +[[image:image-20220602165351-6.png]]
762 762  
763 -* AT+MBFUN=1: Enable Modbus reading. And get response base on the MODBUS return
824 +[[image:image-20220602165351-7.png]]
764 764  
765 -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.
766 766  
767 -* AT+MBFUN=0: Disable Modbus fast reading.
768 768  
769 -Example:
770 770  
771 -* AT+MBFUN=1 and AT+DATACUT1/AT+DATACUT2 are not configure (0,0,0).
772 -* 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.
773 -* 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.
829 +==== **RS485 command timeout** ====
774 774  
775 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image025.png]]
831 +(((
832 +Some Modbus device has slow action to send replies. This command is used to configure the RS485-LN to use longer time to wait for their action.
833 +)))
776 776  
835 +(((
836 +Default value: 0, range:  0 ~~ 65 seconds
837 +)))
777 777  
778 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image026.png]]
839 +* (((
840 +**AT Command:**
841 +)))
779 779  
843 +(% class="box infomessage" %)
844 +(((
845 +(((
846 +**AT+CMDDLaa=hex(bb cc)*1000**
847 +)))
848 +)))
780 780  
781 -* Downlink Commands:
850 +(((
851 +**Example:**
852 +)))
782 782  
783 -A9 aa -à Same as AT+MBFUN=aa
854 +(((
855 +**AT+CMDDL1=1000** to send the open time to 1000ms
856 +)))
784 784  
858 +(((
859 +
860 +)))
785 785  
786 -==== RS485 command timeout ====
862 +* (((
863 +**Downlink Payload:**
864 +)))
787 787  
788 -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.
866 +(((
867 +**0x AA aa bb cc**
868 +)))
789 789  
790 -Default value: 0, range:  0 ~~ 5 seconds
870 +(((
871 +Same as: AT+CMDDLaa=hex(bb cc)*1000
872 +)))
791 791  
874 +(((
875 + **Example:**
876 +)))
792 792  
793 -* AT Command:
878 +(((
879 + 0xAA 01 00 01  ~-~-> Same as **AT+CMDDL1=1000 ms**
880 +)))
794 794  
795 -AT+CMDDLaa=hex(bb cc)
796 796  
797 -Example:
798 798  
799 -**AT+CMDDL1=1000** to send the open time to 1000ms
800 800  
885 +==== **Uplink payload mode** ====
801 801  
802 -* Downlink Payload:
887 +(((
888 +Define to use one uplink or multiple uplinks for the sampling.
889 +)))
803 803  
804 -0x AA aa bb cc
891 +(((
892 +The use of this command please see: [[Compose Uplink payload>>||anchor="H3.3.4Composetheuplinkpayload"]]
893 +)))
805 805  
806 -Same as: AT+CMDDLaa=hex(bb cc)
895 +* (((
896 +**AT Command:**
897 +)))
807 807  
808 - Example:
899 +(% class="box infomessage" %)
900 +(((
901 +(((
902 +**AT+DATAUP=0**
903 +)))
904 +)))
809 809  
810 - 0xAA 01 03 E8  à Same as **AT+CMDDL1=1000 ms**
906 +(% class="box infomessage" %)
907 +(((
908 +(((
909 +**AT+DATAUP=1**
910 +)))
911 +)))
811 811  
913 +(((
914 +
915 +)))
812 812  
813 -==== [[Uplink>>path:#downlink_A8]] payload mode ====
917 +* (((
918 +**Downlink Payload:**
919 +)))
814 814  
815 -Define to use one uplink or multiple uplinks for the sampling.
921 +(((
922 +**0xAD 00**  **~-~->** Same as AT+DATAUP=0
923 +)))
816 816  
817 -The use of this command please see: [[Compose Uplink payload>>path:#DataUP]]
925 +(((
926 +**0xAD 01**  **~-~->** Same as AT+DATAUP=1
927 +)))
818 818  
819 -* AT Command:
820 820  
821 -AT+DATAUP=0
822 822  
823 -AT+DATAUP=1
824 824  
932 +==== **Manually trigger an Uplink** ====
825 825  
826 -* Downlink Payload:
934 +(((
935 +Ask device to send an uplink immediately.
936 +)))
827 827  
828 -0xAD 00   à Same as AT+DATAUP=0
938 +* (((
939 +**AT Command:**
940 +)))
829 829  
830 -0xAD 01   à Same as AT+DATAUP=1
942 +(((
943 +No AT Command for this, user can press the [[ACT button>>||anchor="H3.7Buttons"]] for 1 second for the same.
944 +)))
831 831  
946 +(((
947 +
948 +)))
832 832  
833 -==== Manually trigger an Uplink ====
950 +* (((
951 +**Downlink Payload:**
952 +)))
834 834  
835 -Ask device to send an uplink immediately.
954 +(((
955 +**0x08 FF**, RS485-LN will immediately send an uplink.
956 +)))
836 836  
837 -* Downlink Payload:
838 838  
839 -0x08 FF, RS485-BL will immediately send an uplink.
840 840  
841 841  
842 -==== Clear RS485 Command ====
961 +==== **Clear RS485 Command** ====
843 843  
963 +(((
844 844  The AT+COMMANDx and AT+DATACUTx settings are stored in special location, user can use below command to clear them.
965 +)))
845 845  
967 +* (((
968 +**AT Command:**
969 +)))
846 846  
847 -* AT Command:
848 -
971 +(((
849 849  **AT+CMDEAR=mm,nn**   mm: start position of erase ,nn: stop position of erase
973 +)))
850 850  
975 +(((
851 851  Etc. AT+CMDEAR=1,10 means erase AT+COMMAND1/AT+DATACUT1 to AT+COMMAND10/AT+DATACUT10
977 +)))
852 852  
979 +(((
853 853  Example screen shot after clear all RS485 commands. 
981 +)))
854 854  
983 +(((
984 +
985 +)))
855 855  
856 -
987 +(((
857 857  The uplink screen shot is:
989 +)))
858 858  
859 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]
991 +[[image:1654160691922-496.png]]
860 860  
861 861  
862 -* Downlink Payload:
994 +* (((
995 +**Downlink Payload:**
996 +)))
863 863  
864 -0x09 aa bb same as AT+CMDEAR=aa,bb
998 +(((
999 +**0x09 aa bb** same as AT+CMDEAR=aa,bb
1000 +)))
865 865  
866 866  
867 -==== Set Serial Communication Parameters ====
868 868  
1004 +
1005 +==== **Set Serial Communication Parameters** ====
1006 +
1007 +(((
869 869  Set the Rs485 serial communication parameters:
1009 +)))
870 870  
871 -* AT Command:
1011 +* (((
1012 +**AT Command:**
1013 +)))
872 872  
1015 +(((
873 873  Set Baud Rate:
1017 +)))
874 874  
875 -AT+BAUDR=9600    ~/~/ Options: (1200,2400,4800,14400,19200,115200)
1019 +(% class="box infomessage" %)
1020 +(((
1021 +(((
1022 +**AT+BAUDR=9600**    ~/~/ Options: (1200,2400,4800,14400,19200,115200)
1023 +)))
1024 +)))
876 876  
1026 +(((
1027 +Set UART Parity
1028 +)))
877 877  
878 -Set UART parity
1030 +(% class="box infomessage" %)
1031 +(((
1032 +(((
1033 +**AT+PARITY=0**    ~/~/ Option: 0: no parity, 1: odd parity, 2: even parity
1034 +)))
1035 +)))
879 879  
880 -AT+PARITY=0    ~/~/ Option: 0: no parity, 1: odd parity, 2: even parity
881 -
882 -
1037 +(((
883 883  Set STOPBIT
1039 +)))
884 884  
885 -AT+STOPBIT=0    ~/~/ Option: 0 for 1bit; 1 for 1.5 bit ; 2 for 2 bits
1041 +(% class="box infomessage" %)
1042 +(((
1043 +(((
1044 +**AT+STOPBIT=0**    ~/~/ Option: 0 for 1bit; 1 for 1.5 bit ; 2 for 2 bits
1045 +)))
1046 +)))
886 886  
1048 +(((
1049 +
1050 +)))
887 887  
888 -* Downlink Payload:
1052 +* (((
1053 +**Downlink Payload:**
1054 +)))
889 889  
890 -A7 01 aa bb: Same  AT+BAUDR=hex(aa bb)*100
1056 +(((
1057 +**A7 01 aa bb**: Same  AT+BAUDR=hex(aa bb)*100
1058 +)))
891 891  
892 -Example:
1060 +(((
1061 +**Example:**
1062 +)))
893 893  
894 -* A7 01 00 60   same as AT+BAUDR=9600
895 -* A7 01 04 80  same as AT+BAUDR=115200
1064 +* (((
1065 +A7 01 00 60   same as AT+BAUDR=9600
1066 +)))
1067 +* (((
1068 +A7 01 04 80  same as AT+BAUDR=115200
1069 +)))
896 896  
1071 +(((
897 897  A7 02 aa: Same as  AT+PARITY=aa  (aa value: 00 , 01 or 02)
1073 +)))
898 898  
1075 +(((
899 899  A7 03 aa: Same as  AT+STOPBIT=aa  (aa value: 00 , 01 or 02)
1077 +)))
900 900  
901 901  
902 -==== Control output power duration ====
903 903  
904 -User can set the output power duration before each sampling.
905 905  
906 -* AT Command:
1082 +== 3.6 Listening mode for RS485 network ==
907 907  
908 -Example:
1084 +(((
1085 +This feature support since firmware v1.4
1086 +)))
909 909  
910 -AT+3V3T=1000 ~/~/ 3V3 output power will open 1s before each sampling.
1088 +(((
1089 +RS485-LN supports listening mode, it can listen the RS485 network packets and send them via LoRaWAN uplink. Below is the structure. The blue arrow shows the RS485 network packets to RS485-LN.
1090 +)))
911 911  
912 -AT+5VT=1000 ~/~/ +5V output power will open 1s before each sampling.
1092 +[[image:image-20220602171200-8.png||height="567" width="1007"]]
913 913  
1094 +(((
1095 +To enable the listening mode, use can run the command AT+RXMODE.
1096 +)))
914 914  
915 -* LoRaWAN Downlink Command:
1098 +(((
1099 +
1100 +)))
916 916  
917 -07 01 aa bb  Same as AT+5VT=(aa bb)
1102 +(% border="1" cellspacing="10" style="background-color:#ffffcc; width:500px" %)
1103 +|=(% style="width: 161px;" %)(((
1104 +**Command example:**
1105 +)))|=(% style="width: 337px;" %)(((
1106 +**Function**
1107 +)))
1108 +|(% style="width:161px" %)(((
1109 +AT+RXMODE=1,10
1110 +)))|(% style="width:337px" %)(((
1111 +Enable listening mode 1, if RS485-LN has received more than 10 RS485 commands from the network. RS485-LN will send these commands via LoRaWAN uplinks.
1112 +)))
1113 +|(% style="width:161px" %)(((
1114 +AT+RXMODE=2,500
1115 +)))|(% style="width:337px" %)(((
1116 +Enable listening mode 2, RS485-LN will capture and send a 500ms content once from the first detect of character. Max value is 65535 ms
1117 +)))
1118 +|(% style="width:161px" %)(((
1119 +AT+RXMODE=0,0
1120 +)))|(% style="width:337px" %)(((
1121 +Disable listening mode. This is the default settings.
1122 +)))
1123 +|(% style="width:161px" %)(((
1124 +
1125 +)))|(% style="width:337px" %)(((
1126 +A6 aa bb cc  same as AT+RXMODE=aa,(bb<<8 | cc)
1127 +)))
918 918  
919 -07 02 aa bb  Same as AT+3V3T=(aa bb)
1129 +(((
1130 +**Downlink Command:**
1131 +)))
920 920  
1133 +(((
1134 +**0xA6 aa bb cc ** same as AT+RXMODE=aa,(bb<<8 | cc)
1135 +)))
921 921  
1137 +(((
1138 +
1139 +)))
922 922  
1141 +(((
1142 +**Example**:
1143 +)))
923 923  
924 -1.
925 -11. Buttons
1145 +(((
1146 +The RS485-LN is set to AT+RXMODE=2,1000
1147 +)))
926 926  
927 -|**Button**|**Feature**
928 -|**RST**|Reboot RS485-BL
1149 +(((
1150 +There is a two Modbus commands in the RS485 network as below:
1151 +)))
929 929  
930 -1.
931 -11. +3V3 Output
1153 +(((
1154 +The Modbus master send a command: (% style="background-color:#ffc000" %)01 03 00 00 00 02 c4 0b
1155 +)))
932 932  
933 -RS485-BL has a Controllable +3V3 output, user can use this output to power external sensor.
1157 +(((
1158 +And Modbus slave reply with: (% style="background-color:green" %)01 03 04 00 00 00 00 fa 33
1159 +)))
934 934  
935 -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. 
1161 +(((
1162 +RS485-LN will capture both and send the uplink: (% style="background-color:#ffc000" %)01 03 00 00 00 02 c4 0b  (% style="background-color:green" %)01 03 04 00 00 00 00 fa 33
1163 +)))
936 936  
1165 +(((
1166 +[[image:image-20220602171200-9.png]]
1167 +)))
937 937  
938 -The +3V3 output time can be controlled by AT Command.
1169 +(((
1170 +
1171 +)))
939 939  
940 -**AT+3V3T=1000**
1173 +(((
1174 +(% style="color:red" %)Notice: Listening mode can work with the default polling mode of RS485-LN. When RS485-LN is in to send the RS485 commands (from AT+COMMANDx), the listening mode will be interrupt for a while.
1175 +)))
941 941  
942 -Means set +3v3 valid time to have 1000ms. So, the real +3v3 output will actually have 1000ms + sampling time for other sensors.
943 943  
1178 +== 3.7 Buttons ==
944 944  
945 -By default, the AT+3V3T=0. This is a special case, means the +3V3 output is always on at any time
946 946  
1181 +(% border="1" cellspacing="10" style="background-color:#f7faff; width:400px" %)
1182 +|=(% style="width: 50px;" %)**Button**|=(% style="width: 350px;" %)**Feature**
1183 +|(% style="width:50px" %)**ACT**|(% style="width:350px" %)If RS485 joined in network, press this button for more than 1 second, RS485 will upload a packet, and the SYS LED will give a (% style="color:blue" %)**Blue blink**
1184 +|(% style="width:50px" %)**RST**|(% style="width:350px" %)Reboot RS485
1185 +|(% style="width:50px" %)**PRO**|(% style="width:350px" %)Use for upload image, see [[How to Update Image>>||anchor="H6.1Howtoupgradetheimage3F"]]
947 947  
948 -1.
949 -11. +5V Output
950 950  
951 -RS485-BL has a Controllable +5V output, user can use this output to power external sensor.
1188 +== 3.8 LEDs ==
952 952  
953 -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. 
954 954  
1191 +(% border="1" cellspacing="10" style="background-color:#f7faff; width:430px" %)
1192 +|=(% style="width: 50px;" %)**LEDs**|=(% style="width: 380px;" %)**Feature**
1193 +|**PWR**|Always on if there is power
1194 +|**SYS**|After device is powered on, the SYS will (% style="color:green" %)**fast blink in GREEN**(%%) for 5 times, means RS485-LN start to join LoRaWAN network. If join success, SYS will be (% style="color:green" %)**on GREEN for 5 seconds** (%%)**. **SYS will (% style="color:green" %)**blink Blue**(%%) on every upload and (% style="color:green" %)**blink Green**(%%) once receive a downlink message.
955 955  
956 -The 5V output time can be controlled by AT Command.
957 957  
958 -**AT+5VT=1000**
959 959  
960 -Means set 5V valid time to have 1000ms. So, the real 5V output will actually have 1000ms + sampling time for other sensors.
1198 += 4. Case Study =
961 961  
1200 +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]]
962 962  
963 -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.
964 964  
1203 += 5. Use AT Command =
965 965  
1205 +== 5.1 Access AT Command ==
966 966  
1207 +(((
1208 +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.
1209 +)))
967 967  
968 -1.
969 -11. LEDs
1211 +[[image:1654162355560-817.png]]
970 970  
971 -|**LEDs**|**Feature**
972 -|**LED1**|Blink when device transmit a packet.
973 973  
974 -1.
975 -11. Switch Jumper
1214 +(((
1215 +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:
1216 +)))
976 976  
977 -|**Switch Jumper**|**Feature**
978 -|**SW1**|(((
979 -ISP position: Upgrade firmware via UART
1218 +[[image:1654162368066-342.png]]
980 980  
981 -Flash position: Configure device, check running status.
982 -)))
983 -|**SW2**|(((
984 -5V position: set to compatible with 5v I/O.
985 985  
986 -3.3v position: set to compatible with 3.3v I/O.,
1221 +(((
1222 +More detail AT Command manual can be found at [[AT Command Manual>>https://www.dragino.com/downloads/index.php?dir=LT_LoRa_IO_Controller/LT33222-L/]]
987 987  )))
988 988  
989 -+3.3V: is always ON
990 990  
991 -+5V: Only open before every sampling. The time is by default, it is AT+5VT=0.  Max open time. 5000 ms.
992 992  
993 -1. Case Study
1227 +== 5.2 Common AT Command Sequence ==
994 994  
995 -User can check this URL for some case studies.
1229 +=== 5.2.1 Multi-channel ABP mode (Use with SX1301/LG308) ===
996 996  
997 -[[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]]
1231 +If device has not joined network yet:
998 998  
1233 +(% class="box infomessage" %)
1234 +(((
1235 +**AT+FDR**
1236 +)))
999 999  
1238 +(% class="box infomessage" %)
1239 +(((
1240 +**AT+NJM=0**
1241 +)))
1000 1000  
1243 +(% class="box infomessage" %)
1244 +(((
1245 +**ATZ**
1246 +)))
1001 1001  
1002 -1. Use AT Command
1003 -11. Access AT Command
1004 1004  
1005 -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.
1249 +If device already joined network:
1006 1006  
1007 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image027.png]]
1251 +(% class="box infomessage" %)
1252 +(((
1253 +**AT+NJM=0**
1254 +)))
1008 1008  
1256 +(% class="box infomessage" %)
1257 +(((
1258 +**ATZ**
1259 +)))
1009 1009  
1010 -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:
1011 1011  
1012 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image028.png]]
1262 +=== 5.5.2 Single-channel ABP mode (Use with LG01/LG02) ===
1013 1013  
1014 1014  
1265 +(% style="background-color:#dcdcdc" %)**AT+FDR** (%%) Reset Parameters to Factory Default, Keys Reserve
1015 1015  
1016 -More detail AT Command manual can be found at [[AT Command Manual>>path:#AT_COMMAND]]
1267 +(% style="background-color:#dcdcdc" %)**AT+NJM=0 **(%%)Set to ABP mode
1017 1017  
1269 +(% style="background-color:#dcdcdc" %)**AT+ADR=0** (%%)Set the Adaptive Data Rate Off
1018 1018  
1271 +(% style="background-color:#dcdcdc" %)**AT+DR=5**   (%%)Set Data Rate
1019 1019  
1020 -1.
1021 -11. Common AT Command Sequence
1022 -111. Multi-channel ABP mode (Use with SX1301/LG308)
1273 +(% style="background-color:#dcdcdc" %)**AT+TDC=60000** (%%) Set transmit interval to 60 seconds
1023 1023  
1024 -If device has not joined network yet:
1275 +(% style="background-color:#dcdcdc" %)**AT+CHS=868400000**(%%) Set transmit frequency to 868.4Mhz
1025 1025  
1026 -AT+FDR
1277 +(% style="background-color:#dcdcdc" %)**AT+RX2FQ=868400000** (%%) Set RX2Frequency to 868.4Mhz (according to the result from server)
1027 1027  
1028 -AT+NJM=0
1279 +(% style="background-color:#dcdcdc" %)**AT+RX2DR=5**  (%%) Set RX2DR to match the downlink DR from server. see below
1029 1029  
1030 -ATZ
1281 +(% 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.
1031 1031  
1283 +(% style="background-color:#dcdcdc" %)**ATZ**       (%%) Reset MCU
1032 1032  
1033 -If device already joined network:
1034 1034  
1035 -AT+NJM=0
1286 +(% style="color:red" %)**Note:**
1036 1036  
1037 -ATZ
1288 +(% style="color:red" %)1. Make sure the device is set to ABP mode in the IoT Server.
1289 +2. Make sure the LG01/02 gateway RX frequency is exactly the same as AT+CHS setting.
1290 +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.
1291 +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
1038 1038  
1039 -1.
1040 -11.
1041 -111. Single-channel ABP mode (Use with LG01/LG02)
1293 +[[image:1654162478620-421.png]]
1042 1042  
1043 -AT+FDR   Reset Parameters to Factory Default, Keys Reserve
1044 1044  
1045 -AT+NJM=0 Set to ABP mode
1296 += 6. FAQ =
1046 1046  
1047 -AT+ADR=0 Set the Adaptive Data Rate Off
1298 +== 6.1 How to upgrade the image? ==
1048 1048  
1049 -AT+DR=5  Set Data Rate
1300 +(((
1301 +The RS485-LN LoRaWAN Controller is shipped with a 3.5mm cable, the cable is used to upload image to RS485-LN to:
1302 +)))
1050 1050  
1051 -AT+TDC=60000  Set transmit interval to 60 seconds
1304 +* (((
1305 +Support new features
1306 +)))
1307 +* (((
1308 +For bug fix
1309 +)))
1310 +* (((
1311 +Change LoRaWAN bands.
1312 +)))
1052 1052  
1053 -AT+CHS=868400000 Set transmit frequency to 868.4Mhz
1314 +(((
1315 +Below shows the hardware connection for how to upload an image to RS485-LN:
1316 +)))
1054 1054  
1055 -AT+RX2FQ=868400000 Set RX2Frequency to 868.4Mhz (according to the result from server)
1318 +[[image:1654162535040-878.png]]
1056 1056  
1057 -AT+RX2DR=5  Set RX2DR to match the downlink DR from server. see below
1320 +**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]].
1058 1058  
1059 -AT+DADDR=26 01 1A F1 Set Device Address to 26 01 1A F1, this ID can be found in the LoRa Server portal.
1322 +**Step2**: Download the [[LT Image files>>url:http://www.dragino.com/downloads/index.php?dir=LT_LoRa_IO_Controller/LT33222-L/image/]].
1060 1060  
1061 -ATZ          Reset MCU
1324 +**Step3: **Open flashloader; choose the correct COM port to update.
1062 1062  
1063 -**Note:**
1326 +(((
1327 +(((
1328 +(% style="color:blue" %) Hold down the PRO button and then momentarily press the RST reset button and the SYS led will change from OFF to ON, While SYS LED is RED ON, it means the RS485-LN is ready to be program.
1329 +)))
1330 +)))
1064 1064  
1065 -1. Make sure the device is set to ABP mode in the IoT Server.
1066 -1. Make sure the LG01/02 gateway RX frequency is exactly the same as AT+CHS setting.
1067 -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.
1068 -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
1069 1069  
1070 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image029.png]]
1333 +[[image:image-20220602175818-12.png]]
1071 1071  
1072 1072  
1073 -1. FAQ
1074 -11. How to upgrade the image?
1336 +[[image:image-20220602175848-13.png]]
1075 1075  
1076 -The RS485-BL LoRaWAN Controller is shipped with a 3.5mm cable, the cable is used to upload image to RS485-BL to:
1077 1077  
1078 -* Support new features
1079 -* For bug fix
1080 -* Change LoRaWAN bands.
1339 +[[image:image-20220602175912-14.png]]
1081 1081  
1082 -Below shows the hardware connection for how to upload an image to RS485-BL:
1083 1083  
1084 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image030.png]]
1342 +**Notice**: In case user has lost the program cable. User can hand made one from a 3.5mm cable. The pin mapping is:
1085 1085  
1086 -**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]].
1344 +[[image:image-20220602175638-10.png]]
1087 1087  
1088 -**Step2**: Download the [[LT Image files>>url:http://www.dragino.com/downloads/index.php?dir=LT_LoRa_IO_Controller/LT33222-L/image/]].
1089 1089  
1090 -**Step3: **Open flashloader; choose the correct COM port to update.
1347 +== 6.2 How to change the LoRa Frequency Bands/Region? ==
1091 1091  
1349 +User can follow the introduction for [[how to upgrade image>>||anchor="H6.1Howtoupgradetheimage3F"]]. When download the images, choose the required image file for download.
1092 1092  
1093 -|(((
1094 -HOLD PRO then press the RST button, SYS will be ON, then click next
1095 -)))
1096 1096  
1097 -|(((
1098 -Board detected
1099 -)))
1352 +== 6.3 How many RS485-Slave can RS485-BL connects? ==
1100 1100  
1101 -|(((
1102 -
1103 -)))
1354 +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"]].
1104 1104  
1105 -[[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]]
1106 1106  
1357 +== 6.4 Compatible question to ChirpStack and TTI LoRaWAN server ? ==
1107 1107  
1359 +When user need to use with ChirpStack or TTI. Please set AT+RPL=4.
1108 1108  
1109 -[[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]]
1361 +Detail info check this link: [[Set Packet Receiving Response Level>>doc:Main.End Device AT Commands and Downlink Command.WebHome||anchor="H7.23SetPacketReceivingResponseLevel"]]
1110 1110  
1111 1111  
1112 -[[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]]
1364 += 7. Trouble Shooting =
1113 1113  
1366 +== 7.1 Downlink doesn’t work, how to solve it? ==
1114 1114  
1115 -1.
1116 -11. How to change the LoRa Frequency Bands/Region?
1368 +Please see this link for debug: [[LoRaWAN Communication Debug>>doc:Main.LoRaWAN Communication Debug.WebHome]]
1117 1117  
1118 -User can follow the introduction for [[how to upgrade image>>path:#upgrade_image]]. When download the images, choose the required image file for download.
1119 1119  
1371 +== 7.2 Why I can’t join TTN V3 in US915 /AU915 bands? ==
1120 1120  
1373 +It might about the channels mapping. Please see for detail: [[Notice of Frequency band>>doc:Main.LoRaWAN Communication Debug.WebHome||anchor="H2.NoticeofUS9152FCN4702FAU915Frequencyband"]]
1121 1121  
1122 -1.
1123 -11. How many RS485-Slave can RS485-BL connects?
1124 1124  
1125 -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]].
1376 += 8. Order Info =
1126 1126  
1378 +(% style="color:blue" %)**Part Number: RS485-LN-XXX**
1127 1127  
1380 +(% style="color:blue" %)**XXX:**
1128 1128  
1382 +* (% style="color:blue" %)**EU433**(%%): frequency bands EU433
1383 +* (% style="color:blue" %)**EU868**(%%): frequency bands EU868
1384 +* (% style="color:blue" %)**KR920**(%%): frequency bands KR920
1385 +* (% style="color:blue" %)**CN470**(%%): frequency bands CN470
1386 +* (% style="color:blue" %)**AS923**(%%): frequency bands AS923
1387 +* (% style="color:blue" %)**AU915**(%%): frequency bands AU915
1388 +* (% style="color:blue" %)**US915**(%%): frequency bands US915
1389 +* (% style="color:blue" %)**IN865**(%%): frequency bands IN865
1390 +* (% style="color:blue" %)**RU864**(%%): frequency bands RU864
1391 +* (% style="color:blue" %)**KZ865**(%%): frequency bands KZ865
1129 1129  
1130 -1. Trouble Shooting     
1131 -11. Downlink doesn’t work, how to solve it?
1393 += 9.Packing Info =
1132 1132  
1133 -Please see this link for debug:
1134 1134  
1135 -[[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]] 
1396 +**Package Includes**:
1136 1136  
1398 +* RS485-LN x 1
1399 +* Stick Antenna for LoRa RF part x 1
1400 +* Program cable x 1
1137 1137  
1402 +**Dimension and weight**:
1138 1138  
1139 -1.
1140 -11. Why I can’t join TTN V3 in US915 /AU915 bands?
1404 +* Device Size: 13.5 x 7 x 3 cm
1405 +* Device Weight: 105g
1406 +* Package Size / pcs : 14.5 x 8 x 5 cm
1407 +* Weight / pcs : 170g
1141 1141  
1142 -It might about the channels mapping. Please see for detail.
1409 += 10. FCC Caution for RS485LN-US915 =
1143 1143  
1144 -[[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]]
1411 +(((
1412 +Any Changes or modifications not expressly approved by the party responsible for compliance could void the user's authority to operate the equipment.
1413 +)))
1145 1145  
1415 +(((
1416 +This device complies with part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) This device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation.
1417 +)))
1146 1146  
1419 +(((
1420 +
1421 +)))
1147 1147  
1148 -1. Order Info
1423 +(((
1424 +**IMPORTANT NOTE:**
1425 +)))
1149 1149  
1150 -**Part Number: RS485-BL-XXX**
1427 +(((
1428 +**Note: **This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following measures:
1429 +)))
1151 1151  
1152 -**XXX:**
1431 +(((
1432 +—Reorient or relocate the receiving antenna.
1433 +)))
1153 1153  
1154 -* **EU433**: frequency bands EU433
1155 -* **EU868**: frequency bands EU868
1156 -* **KR920**: frequency bands KR920
1157 -* **CN470**: frequency bands CN470
1158 -* **AS923**: frequency bands AS923
1159 -* **AU915**: frequency bands AU915
1160 -* **US915**: frequency bands US915
1161 -* **IN865**: frequency bands IN865
1162 -* **RU864**: frequency bands RU864
1163 -* **KZ865: **frequency bands KZ865
1435 +(((
1436 +—Increase the separation between the equipment and receiver.
1437 +)))
1164 1164  
1165 -1. Packing Info
1439 +(((
1440 +—Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.
1441 +)))
1166 1166  
1167 -**Package Includes**:
1443 +(((
1444 +—Consult the dealer or an experienced radio/TV technician for help.
1445 +)))
1168 1168  
1169 -* RS485-BL x 1
1170 -* Stick Antenna for LoRa RF part x 1
1171 -* Program cable x 1
1447 +(((
1448 +
1449 +)))
1172 1172  
1173 -**Dimension and weight**:
1451 +(((
1452 +**FCC Radiation Exposure Statement:**
1453 +)))
1174 1174  
1175 -* Device Size: 13.5 x 7 x 3 cm
1176 -* Device Weight: 105g
1177 -* Package Size / pcs : 14.5 x 8 x 5 cm
1178 -* Weight / pcs : 170g
1455 +(((
1456 +This equipment complies with FCC radiation exposure limits set forth for an uncontrolled environment.This equipment should be installed and operated with minimum distance 20cm between the radiator& your body.
1457 +)))
1179 1179  
1180 -1. Support
1181 1181  
1182 -* 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.
1183 -* 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
1460 += 11. Support =
1184 1184  
1185 -[[support@dragino.com>>url:file:///D:/市场资料/说明书/LoRa/LT系列/support@dragino.com]]
1462 +* (((
1463 +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.
1464 +)))
1465 +* (((
1466 +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]].
1467 +)))
1654157178836-407.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +179.9 KB
Content
1654157342174-798.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +31.9 KB
Content
1654158783574-851.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +40.6 KB
Content
1654159460680-153.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +24.9 KB
Content
1654160691922-496.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +109.3 KB
Content
1654162355560-817.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +670.0 KB
Content
1654162368066-342.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +192.9 KB
Content
1654162478620-421.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +158.9 KB
Content
1654162535040-878.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +670.0 KB
Content
image-20220602153621-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +23.4 KB
Content
image-20220602153621-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +22.2 KB
Content
image-20220602153621-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +22.3 KB
Content
image-20220602155039-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +24.6 KB
Content
image-20220602163333-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +48.2 KB
Content
image-20220602165351-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +10.6 KB
Content
image-20220602165351-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +19.3 KB
Content
image-20220602171200-8.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +276.1 KB
Content
image-20220602171200-9.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +10.0 KB
Content
image-20220602175638-10.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +85.5 KB
Content
image-20220602175743-11.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +85.5 KB
Content
image-20220602175818-12.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +102.5 KB
Content
image-20220602175848-13.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +250.9 KB
Content
image-20220602175912-14.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +176.1 KB
Content
image-20220606110929-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +13.9 KB
Content