Skip to Content
Last modified by Mengting Qiu on 2025/07/14 09:59
From version 22.6
edited by Xiaoling
on 2022/05/23 09:17
Change comment: There is no comment for this version
To version 57.31
edited by Xiaoling
on 2022/06/06 09:23
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,26 +18,30 @@
18 18  
19 19  (((
20 20  (((
21 -The Dragino RS485-LN is a RS485 to LoRaWAN Converter. It converts the RS485 signal into LoRaWAN wireless signal which simplify the IoT installation and reduce the installation/maintaining cost.
27 +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  )))
23 23  
24 24  (((
25 -RS485-LN allows user to 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.
31 +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  )))
27 27  
28 28  (((
29 -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.
35 +(% 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  )))
31 31  
32 32  (((
33 -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.
39 +(% 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.
40 +
41 +(% 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]]
34 34  )))
35 35  )))
36 36  
37 37  [[image:1653267211009-519.png||height="419" width="724"]]
38 38  
47 +
39 39  == 1.2 Specifications ==
40 40  
50 +
41 41  **Hardware System:**
42 42  
43 43  * STM32L072CZT6 MCU
... ... @@ -44,8 +44,6 @@
44 44  * SX1276/78 Wireless Chip 
45 45  * Power Consumption (exclude RS485 device):
46 46  ** Idle: 32mA@12v
47 -
48 -*
49 49  ** 20dB Transmit: 65mA@12v
50 50  
51 51  **Interface for Model:**
... ... @@ -72,7 +72,7 @@
72 72  * Preamble detection.
73 73  * 127 dB Dynamic Range RSSI.
74 74  * Automatic RF Sense and CAD with ultra-fast AFC.
75 -* Packet engine up to 256 bytes with CRC.
83 +* Packet engine up to 256 bytes with CRC
76 76  
77 77  == 1.3 Features ==
78 78  
... ... @@ -98,6 +98,7 @@
98 98  
99 99  [[RS485-LN Image files – Download link and Change log>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/]]
100 100  
109 +
101 101  == 1.6 Hardware Change log ==
102 102  
103 103  (((
... ... @@ -105,6 +105,8 @@
105 105  v1.2: Add External Interrupt Pin.
106 106  
107 107  v1.0: Release
117 +
118 +
108 108  )))
109 109  )))
110 110  
... ... @@ -121,6 +121,8 @@
121 121  )))
122 122  
123 123  [[image:1653268091319-405.png]]
135 +
136 +
124 124  )))
125 125  
126 126  = 3. Operation Mode =
... ... @@ -129,6 +129,8 @@
129 129  
130 130  (((
131 131  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.
145 +
146 +
132 132  )))
133 133  
134 134  == 3.2 Example to join LoRaWAN network ==
... ... @@ -137,15 +137,20 @@
137 137  
138 138  [[image:1653268155545-638.png||height="334" width="724"]]
139 139  
155 +
140 140  (((
157 +(((
141 141  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:
159 +)))
142 142  
161 +(((
143 143  485A+ and 485B- of the sensor are connected to RS485A and RA485B of RS485-LN respectively.
163 +)))
144 144  
145 145  [[image:1653268227651-549.png||height="592" width="720"]]
146 146  
147 147  (((
148 -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:
168 +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:
149 149  )))
150 150  
151 151  (((
... ... @@ -192,15 +192,18 @@
192 192  
193 193  [[image:1652953568895-172.png||height="232" width="724"]]
194 194  
215 +
195 195  == 3.3 Configure Commands to read data ==
196 196  
197 197  (((
198 198  (((
199 -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.
220 +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.
200 200  )))
201 201  
202 202  (((
203 203  (% 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
225 +
226 +
204 204  )))
205 205  )))
206 206  
... ... @@ -208,19 +208,19 @@
208 208  
209 209  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:
210 210  
211 -(% border="1" style="background-color:#ffffcc; color:green; width:795px" %)
212 -|(((
234 +(% border="1" style="background-color:#ffffcc; color:green; width:782px" %)
235 +|(% style="width:128px" %)(((
213 213  **AT Commands**
214 -)))|(% style="width:285px" %)(((
237 +)))|(% style="width:305px" %)(((
215 215  **Description**
216 -)))|(% style="width:347px" %)(((
239 +)))|(% style="width:346px" %)(((
217 217  **Example**
218 218  )))
219 -|(((
242 +|(% style="width:128px" %)(((
220 220  AT+BAUDR
221 -)))|(% style="width:285px" %)(((
244 +)))|(% style="width:305px" %)(((
222 222  Set the baud rate (for RS485 connection). Default Value is: 9600.
223 -)))|(% style="width:347px" %)(((
246 +)))|(% style="width:346px" %)(((
224 224  (((
225 225  AT+BAUDR=9600
226 226  )))
... ... @@ -229,11 +229,11 @@
229 229  Options: (1200,2400,4800,14400,19200,115200)
230 230  )))
231 231  )))
232 -|(((
255 +|(% style="width:128px" %)(((
233 233  AT+PARITY
234 -)))|(% style="width:285px" %)(((
257 +)))|(% style="width:305px" %)(((
235 235  Set UART parity (for RS485 connection)
236 -)))|(% style="width:347px" %)(((
259 +)))|(% style="width:346px" %)(((
237 237  (((
238 238  AT+PARITY=0
239 239  )))
... ... @@ -242,9 +242,9 @@
242 242  Option: 0: no parity, 1: odd parity, 2: even parity
243 243  )))
244 244  )))
245 -|(((
268 +|(% style="width:128px" %)(((
246 246  AT+STOPBIT
247 -)))|(% style="width:285px" %)(((
270 +)))|(% style="width:305px" %)(((
248 248  (((
249 249  Set serial stopbit (for RS485 connection)
250 250  )))
... ... @@ -252,7 +252,7 @@
252 252  (((
253 253  
254 254  )))
255 -)))|(% style="width:347px" %)(((
278 +)))|(% style="width:346px" %)(((
256 256  (((
257 257  AT+STOPBIT=0 for 1bit
258 258  )))
... ... @@ -269,12 +269,10 @@
269 269  === 3.3.2 Configure sensors ===
270 270  
271 271  (((
272 -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**.
273 -)))
274 -
275 275  (((
276 -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.
296 +Some sensors might need to configure before normal operation. User can configure such sensor via PC and RS485 adapter or through RS485-LN AT Commands (% style="color:#4f81bd" %)**AT+CFGDEV**(%%). Each (% style="color:#4f81bd" %)**AT+CFGDEV **(%%)equals to send a RS485 command to sensors. This command will only run when user input it and won’t run during each sampling.
277 277  )))
298 +)))
278 278  
279 279  (% border="1" style="background-color:#ffffcc; color:green; width:806px" %)
280 280  |**AT Commands**|(% style="width:418px" %)**Description**|(% style="width:256px" %)**Example**
... ... @@ -286,82 +286,37 @@
286 286  mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
287 287  )))|(% style="width:256px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
288 288  
289 -Detail of AT+CFGDEV command see [[AT+CFGDEV detail>>path:#AT_CFGDEV]].
290 -
291 291  === 3.3.3 Configure read commands for each sampling ===
292 292  
293 293  (((
294 -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.
295 -)))
313 +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.
296 296  
297 -(((
298 -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.
299 -)))
300 -
301 -(((
302 302  To save the LoRaWAN network bandwidth, we might need to read data from different sensors and combine their valid value into a short payload.
303 -)))
304 304  
305 -(((
306 306  This section describes how to achieve above goals.
307 -)))
308 308  
309 -(((
310 -During each sampling, the RS485-BL can support 15 commands to read sensors. And combine the return to one or several uplink payloads.
311 -)))
319 +During each sampling, the RS485-LN can support 15 commands to read sensors. And combine the return to one or several uplink payloads.
312 312  
313 -(((
314 -**Command from RS485-BL to Sensor:**
315 -)))
316 316  
317 -(((
318 -RS485-BL can send out pre-set max 15 strings via **AT+COMMAD1**, **ATCOMMAND2**,…, to **AT+COMMANDF** . All commands are of same grammar.
319 -)))
322 +**Each RS485 commands include two parts:**
320 320  
321 -(((
322 -**Handle return from sensors to RS485-BL**:
323 -)))
324 +~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.
324 324  
325 -(((
326 -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**
327 -)))
326 +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.
328 328  
329 -* (((
330 -**AT+DATACUT**
331 -)))
328 +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
332 332  
333 -(((
334 -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.
335 -)))
336 336  
337 -* (((
338 -**AT+SEARCH**
339 -)))
340 -
341 -(((
342 -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.
343 -)))
344 -
345 -(((
346 -**Define wait timeout:**
347 -)))
348 -
349 -(((
350 -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
351 -)))
352 -
353 -(((
354 354  After we got the valid value from each RS485 commands, we need to combine them together with the command **AT+DATAUP**.
355 -)))
356 356  
357 -**Examples:**
358 358  
359 359  Below are examples for the how above AT Commands works.
360 360  
361 -**AT+COMMANDx : **This command will be sent to RS485/TTL devices during each sampling, Max command length is 14 bytes. The grammar is:
362 362  
363 -(% border="1" class="table-bordered" %)
364 -|(((
337 +**AT+COMMANDx : **This command will be sent to RS485 devices during each sampling, Max command length is 14 bytes. The grammar is:
338 +
339 +(% border="1" style="background-color:#4bacc6; color:white; width:499px" %)
340 +|(% style="width:496px" %)(((
365 365  **AT+COMMANDx=xx xx xx xx xx xx xx xx xx xx xx xx,m**
366 366  
367 367  **xx xx xx xx xx xx xx xx xx xx xx xx: The RS485 command to be sent**
... ... @@ -371,43 +371,13 @@
371 371  
372 372  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.
373 373  
374 -In the RS485-BL, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
350 +In the RS485-LN, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
375 375  
376 -**AT+SEARCHx**: This command defines how to handle the return from AT+COMMANDx.
377 377  
378 -(% border="1" class="table-bordered" %)
379 -|(((
380 -**AT+SEARCHx=aa,xx xx xx xx xx**
381 -
382 -* **aa: 1: prefix match mode; 2: prefix and suffix match mode**
383 -* **xx xx xx xx xx: match string. Max 5 bytes for prefix and 5 bytes for suffix**
384 -
385 -
386 -)))
387 -
388 -Examples:
389 -
390 -1. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
391 -
392 -If we set AT+SEARCH1=1,1E 56 34.      (max 5 bytes for prefix)
393 -
394 -The valid data will be all bytes after 1E 56 34 , so it is 2e 30 58 5f 36 41 30 31 00 49
395 -
396 -[[image:1652954654347-831.png]]
397 -
398 -
399 -1. For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
400 -
401 -If we set AT+SEARCH1=2, 1E 56 34+31 00 49
402 -
403 -Device will search the bytes between 1E 56 34 and 31 00 49. So it is 2e 30 58 5f 36 41 30
404 -
405 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image014.png]]
406 -
407 -
408 408  **AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes.
409 409  
410 -|(((
355 +(% border="1" style="background-color:#4bacc6; color:white; width:725px" %)
356 +|(% style="width:722px" %)(((
411 411  **AT+DATACUTx=a,b,c**
412 412  
413 413  * **a: length for the return of AT+COMMAND**
... ... @@ -415,242 +415,184 @@
415 415  * **c: define the position for valid value.  **
416 416  )))
417 417  
418 -Examples:
364 +**Examples:**
419 419  
420 420  * Grab bytes:
421 421  
422 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image015.png]]
368 +[[image:image-20220602153621-1.png]]
423 423  
370 +
424 424  * Grab a section.
425 425  
426 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image016.png]]
373 +[[image:image-20220602153621-2.png]]
427 427  
375 +
428 428  * Grab different sections.
429 429  
430 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image017.png]]
378 +[[image:image-20220602153621-3.png]]
431 431  
380 +
381 +)))
432 432  
433 -Note:
383 +=== 3.3.4 Compose the uplink payload ===
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 -AT+COMMAND1=11 01 1E D0,0
440 -
441 -AT+SEARCH1=1,1E 56 34
442 -
443 -AT+DATACUT1=0,2,1~~5
444 -
445 -Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
446 -
447 -String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
448 -
449 -Valid payload after DataCUT command: 2e 30 58 5f 36
450 -
451 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image018.png]]
452 -
453 -
454 -
455 -
456 -1.
457 -11.
458 -111. Compose the uplink payload
459 -
385 +(((
460 460  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.**
461 461  
388 +
389 +)))
462 462  
463 -**Examples: AT+DATAUP=0**
391 +(((
392 +(% style="color:#037691" %)**Examples: AT+DATAUP=0**
464 464  
465 -Compose the uplink payload with value returns in sequence and send with **A SIGNLE UPLINK**.
394 +
395 +)))
466 466  
397 +(((
398 +Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**A SIGNLE UPLINK**.
399 +)))
400 +
401 +(((
467 467  Final Payload is
403 +)))
468 468  
469 -Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx
405 +(((
406 +(% style="color:#4f81bd" %)**Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx**
407 +)))
470 470  
409 +(((
471 471  Where PAYVER is defined by AT+PAYVER, below is an example screen shot.
411 +)))
472 472  
473 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.png]]
413 +[[image:1653269759169-150.png||height="513" width="716"]]
474 474  
475 475  
416 +(% style="color:#037691" %)**Examples: AT+DATAUP=1**
476 476  
477 -**Examples: AT+DATAUP=1**
478 478  
479 -Compose the uplink payload with value returns in sequence and send with **Multiply UPLINKs**.
419 +Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**Multiply UPLINKs**.
480 480  
481 481  Final Payload is
482 482  
483 -Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA
423 +(% style="color:#4f81bd" %)**Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA**
484 484  
485 -1. Battery Info (2 bytes): Battery voltage
486 -1. PAYVER (1 byte): Defined by AT+PAYVER
487 -1. PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling.
488 -1. PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
489 -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
490 490  
491 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image020.png]]
426 +1. PAYVER: Defined by AT+PAYVER
427 +1. PAYLOAD COUNT: Total how many uplinks of this sampling.
428 +1. PAYLOAD#: Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
429 +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
492 492  
431 +[[image:image-20220602155039-4.png]]
493 493  
494 -So totally there will be 3 uplinks for this sampling, each uplink includes 6 bytes DATA
495 495  
496 -DATA1=RETURN1 Valid Value = 20 20 0a 33 90 41
434 +So totally there will be 3 uplinks for this sampling, each uplink include 8 bytes DATA
497 497  
498 -DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= 02 aa 05 81 0a 20
436 +DATA1=RETURN1 Valid Value + the first two of Valid value of RETURN10= **20 20 0a 33 90 41 02 aa**
499 499  
500 -DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 = 20 20 20 2d 30
438 +DATA2=3^^rd^^ ~~ 10^^th^^ byte of Valid value of RETURN10= **05 81 0a 20 20 20 20 2d**
501 501  
440 +DATA3=the rest of Valid value of RETURN10= **30**
502 502  
503 503  
504 -Below are the uplink payloads:
443 +(% 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:
505 505  
506 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.png]]
445 + ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink.
507 507  
447 + * For AU915/AS923 bands, if UplinkDwell time=0, max 11 bytes for each uplink.
508 508  
509 -Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:
449 + * For US915 band, max 11 bytes for each uplink.
510 510  
511 - ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink ( so 51 -5 = 46 max valid date)
451 + ~* For all other bands: max 51 bytes for each uplink.
512 512  
513 - * For AU915/AS923 bands, if UplinkDwell time=1, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date).
514 514  
515 - * For US915 band, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date).
454 +Below are the uplink payloads:
516 516  
517 - ~* For all other bands: max 51 bytes for each uplink  ( so 51 -5 = 46 max valid date).
456 +[[image:1654157178836-407.png]]
518 518  
519 519  
459 +=== 3.3.5 Uplink on demand ===
520 520  
521 -1.
522 -11.
523 -111. Uplink on demand
461 +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.
524 524  
525 -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.
526 -
527 527  Downlink control command:
528 528  
529 -[[0x08 command>>path:#downlink_08]]: Poll an uplink with current command set in RS485-BL.
465 +**0x08 command**: Poll an uplink with current command set in RS485-LN.
530 530  
531 -[[0xA8 command>>path:#downlink_A8]]: Send a command to RS485-BL and uplink the output from sensors.
467 +**0xA8 command**: Send a command to RS485-LN and uplink the output from sensors.
532 532  
533 533  
534 534  
535 -1.
536 -11.
537 -111. Uplink on Interrupt
471 +=== 3.3.6 Uplink on Interrupt ===
538 538  
539 -Put the interrupt sensor between 3.3v_out and GPIO ext.[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image022.png]]
473 +RS485-LN support external Interrupt uplink since hardware v1.2 release.
540 540  
541 -AT+INTMOD=0  Disable Interrupt
475 +[[image:1654157342174-798.png]]
542 542  
543 -AT+INTMOD=1  Interrupt trigger by rising or falling edge.
477 +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.
544 544  
545 -AT+INTMOD=2  Interrupt trigger by falling edge. ( Default Value)
546 546  
547 -AT+INTMOD=3  Interrupt trigger by rising edge.
480 +== 3.4 Uplink Payload ==
548 548  
549 -
550 -1.
551 -11. Uplink Payload
552 -
553 -|**Size(bytes)**|**2**|**1**|**Length depends on the return from the commands**
554 -|Value|(((
482 +(% border="1" style="background-color:#4bacc6; color:white; width:734px" %)
483 +|**Size(bytes)**|(% style="width:120px" %)**2**|(% style="width:116px" %)**1**|(% style="width:386px" %)**Length depends on the return from the commands**
484 +|Value|(% style="width:120px" %)(((
555 555  Battery(mV)
556 556  
557 557  &
558 558  
559 559  Interrupt _Flag
560 -)))|(((
490 +)))|(% style="width:116px" %)(((
561 561  PAYLOAD_VER
562 562  
563 563  
564 -)))|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.
494 +)))|(% style="width:386px" %)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.
565 565  
566 566  Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors.
567 567  
568 568  
569 -function Decoder(bytes, port) {
499 +== 3.5 Configure RS485-BL via AT or Downlink ==
570 570  
571 -~/~/Payload Formats of RS485-BL Deceive
501 +User can configure RS485-LN via AT Commands or LoRaWAN Downlink Commands
572 572  
573 -return {
574 -
575 - ~/~/Battery,units:V
576 -
577 - BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000,
578 -
579 - ~/~/GPIO_EXTI 
580 -
581 - EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE",
582 -
583 - ~/~/payload of version
584 -
585 - Pay_ver:bytes[2],
586 -
587 - };
588 -
589 - }
590 -
591 -
592 -
593 -
594 -
595 -
596 -
597 -TTN V3 uplink screen shot.
598 -
599 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]
600 -
601 -1.
602 -11. Configure RS485-BL via AT or Downlink
603 -
604 -User can configure RS485-BL via [[AT Commands >>path:#_​Using_the_AT]]or LoRaWAN Downlink Commands
605 -
606 606  There are two kinds of Commands:
607 607  
608 -* **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
505 +* (% 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]]
609 609  
610 -* **Sensor Related Commands**: These commands are special designed for RS485-BL.  User can see these commands below:
507 +* (% style="color:#4f81bd" %)**Sensor Related Commands**(%%): These commands are special designed for RS485-LN.  User can see these commands below:
611 611  
612 -1.
613 -11.
614 -111. Common Commands:
509 +=== 3.5.1 Common Commands ===
615 615  
616 -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]]
511 +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]]
617 617  
618 618  
619 -1.
620 -11.
621 -111. Sensor related commands:
514 +=== 3.5.2 Sensor related commands ===
622 622  
623 -==== Choose Device Type (RS485 or TTL) ====
516 +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.
624 624  
625 -RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect.
518 +[[image:image-20220602163333-5.png||height="263" width="1160"]]
626 626  
627 -* AT Command
520 +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)
628 628  
629 -**AT+MOD=1** ~/~/ Set to support RS485-MODBUS type sensors. User can connect multiply RS485 , Modbus sensors to the A / B pins.
630 630  
631 -**AT+MOD=2** ~/~/ Set to support TTL Level sensors, User can connect one TTL Sensor to the TXD/RXD/GND pins.
523 +=== 3.5.3 Sensor related commands ===
632 632  
633 633  
634 -* Downlink Payload
635 635  
636 -**0A aa**     à same as AT+MOD=aa
527 +==== **RS485 Debug Command** ====
637 637  
529 +This command is used to configure the RS485 devices; they won’t be used during sampling.
638 638  
531 +* **AT Command**
639 639  
640 -==== [[RS485 Debug Command>>path:#downlink_A8]] (AT+CFGDEV) ====
533 +(% class="box infomessage" %)
534 +(((
535 +**AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m**
536 +)))
641 641  
642 -This command is used to configure the RS485 or TTL sensors; they won’t be used during sampling.
538 +m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
643 643  
644 -* AT Command
540 +* **Downlink Payload**
645 645  
646 -AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
647 -
648 -m: 0: no CRC; 1: add CRC-16/MODBUS in the end of this command.
649 -
650 -
651 -
652 -* Downlink Payload
653 -
654 654  Format: A8 MM NN XX XX XX XX YY
655 655  
656 656  Where:
... ... @@ -658,9 +658,12 @@
658 658  * MM: 1: add CRC-16/MODBUS ; 0: no CRC
659 659  * NN: The length of RS485 command
660 660  * XX XX XX XX: RS485 command total NN bytes
661 -* 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
549 +* YY: How many bytes will be uplink from the return of this RS485 command,
550 +** if YY=0, RS485-LN will execute the downlink command without uplink;
551 +** if YY>0, RS485-LN will uplink total YY bytes from the output of this RS485 command; Fport=200
552 +** if YY=FF, RS485-LN will uplink RS485 output with the downlink command content; Fport=200.
662 662  
663 -**Example 1:**
554 +**Example 1** ~-~-> Configure without ask for uplink (YY=0)
664 664  
665 665  To connect a Modbus Alarm with below commands.
666 666  
... ... @@ -670,184 +670,190 @@
670 670  
671 671  So if user want to use downlink command to control to RS485 Alarm, he can use:
672 672  
673 -**A8 01 06 0A 05 00 04 00 01 00**: to activate the RS485 Alarm
564 +(% style="color:#4f81bd" %)**A8 01 06 0A 05 00 04 00 01 00**(%%): to activate the RS485 Alarm
674 674  
675 -**A8 01 06 0A 05 00 04 00 00 00**: to deactivate the RS485 Alarm
566 +(% style="color:#4f81bd" %)**A8 01 06 0A 05 00 04 00 00 00**(%%): to deactivate the RS485 Alarm
676 676  
677 677  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.
678 678  
679 679  
680 -**Example 2:**
571 +**Example 2** ~-~-> Configure with requesting uplink and original downlink command (**YY=FF**)
681 681  
682 -Check TTL Sensor return:
573 +User in IoT server send a downlink command: (% style="color:#4f81bd" %)**A8 01 06 0A 08 00 04 00 01 YY**
683 683  
684 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image024.png]]
685 685  
576 +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:
686 686  
578 + **A8** (% style="color:#4f81bd" %)**0A 08 00 04 00  **(% style="color:red" %)**01 06** ** **(% style="color:green" %)**0A 08 00 04 00 00**
687 687  
580 + [[image:1654159460680-153.png]]
688 688  
689 -==== Set Payload version ====
690 690  
691 -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.
692 692  
693 -* AT Command:
584 +==== **Set Payload version** ====
694 694  
695 -AT+PAYVER: Set PAYVER field = 1
586 +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.
696 696  
588 +* **AT Command:**
697 697  
698 -* Downlink Payload:
590 +(% class="box infomessage" %)
591 +(((
592 +**AT+PAYVER: Set PAYVER field = 1**
593 +)))
699 699  
700 -0xAE 01   à Set PAYVER field =  0x01
595 +* **Downlink Payload:**
701 701  
702 -0xAE 0F   à Set PAYVER field =  0x0F
597 +**0xAE 01**  ~-~-> Set PAYVER field =  0x01
703 703  
599 +**0xAE 0F**   ~-~-> Set PAYVER field =  0x0F
704 704  
705 -==== Set RS485 Sampling Commands ====
706 706  
707 -AT+COMMANDx, AT+DATACUTx and AT+SEARCHx
708 708  
709 -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]].
603 +==== **Set RS485 Sampling Commands** ====
710 710  
605 +AT+COMMANDx or AT+DATACUTx
711 711  
712 -* AT Command:
607 +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"]].
713 713  
714 -AT+COMMANDx: Configure RS485 read command to sensor.
715 715  
716 -AT+DATACUTx: Configure how to handle return from RS485 devices.
610 +* **AT Command:**
717 717  
718 -AT+SEARCHx: Configure search command
612 +(% class="box infomessage" %)
613 +(((
614 +**AT+COMMANDx: Configure RS485 read command to sensor.**
615 +)))
719 719  
617 +(% class="box infomessage" %)
618 +(((
619 +**AT+DATACUTx: Configure how to handle return from RS485 devices.**
620 +)))
720 720  
721 -* Downlink Payload:
722 722  
723 -0xAF downlink command can be used to set AT+COMMANDx or AT+DATACUTx.
623 +* **Downlink Payload:**
724 724  
725 -Note: if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink.
625 +**0xAF** downlink command can be used to set AT+COMMANDx or AT+DATACUTx.
726 726  
627 +(% style="color:red" %)**Note**(%%): if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink.
628 +
727 727  Format: AF MM NN LL XX XX XX XX YY
728 728  
729 729  Where:
730 730  
731 731  * MM: the ATCOMMAND or AT+DATACUT to be set. Value from 01 ~~ 0F,
732 -* NN: 0: no CRC; 1: add CRC-16/MODBUS ; 2: set the AT+DATACUT value.
733 -* LL: The length of AT+COMMAND or AT+DATACUT command
634 +* NN:  0: no CRC; 1: add CRC-16/MODBUS ; 2: set the AT+DATACUT value.
635 +* LL:  The length of AT+COMMAND or AT+DATACUT command
734 734  * XX XX XX XX: AT+COMMAND or AT+DATACUT command
735 -* 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.
637 +* 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.
736 736  
737 -Example:
639 +**Example:**
738 738  
739 -**AF 03 01 06 0A 05 00 04 00 01 00**: Same as AT+COMMAND3=0A 05 00 04 00 01,1
641 +(% 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
740 740  
741 -**AF 03 02 06 10 01 05 06 09 0A 00**: Same as AT+DATACUT3=**16**,**1**,**5+6+9+10**
643 +(% 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**
742 742  
743 -**AF 03 02 06 0B 02 05 07 08 0A 00**: Same as AT+DATACUT3=**11**,**2**,**5~~7+8~~10**
645 +(% 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**
744 744  
745 745  
746 -0xAB downlink command can be used for set AT+SEARCHx
747 747  
748 -Example: **AB aa 01 03 xx xx xx** (03 here means there are total 3 bytes after 03) So
649 +==== **Fast command to handle MODBUS device** ====
749 749  
750 -* AB aa 01 03 xx xx xx  same as AT+SEARCHaa=1,xx xx xx
751 -* 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
752 -
753 -**AB aa 02 03 xx xx xx 02 yy yy**  same as **AT+SEARCHaa=2,xx xx xx+yy yy**
754 -
755 -
756 -==== Fast command to handle MODBUS device ====
757 -
758 758  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]].
759 759  
760 760  This command is valid since v1.3 firmware version
761 761  
655 +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.
762 762  
763 -AT+MBFUN has only two value:
764 764  
765 -* AT+MBFUN=1: Enable Modbus reading. And get response base on the MODBUS return
658 +**Example:**
766 766  
767 -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.
768 -
769 -* AT+MBFUN=0: Disable Modbus fast reading.
770 -
771 -Example:
772 -
773 -* AT+MBFUN=1 and AT+DATACUT1/AT+DATACUT2 are not configure (0,0,0).
660 +* AT+MBFUN=1 and AT+DATACUT1/AT+DATACUT2 are not configure (0,0,0). So RS485-LN.
774 774  * 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.
775 775  * 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.
776 776  
777 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image025.png]]
664 +[[image:image-20220602165351-6.png]]
778 778  
666 +[[image:image-20220602165351-7.png]]
779 779  
780 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image026.png]]
781 781  
782 782  
783 -* Downlink Commands:
670 +==== **RS485 command timeout** ====
784 784  
785 -A9 aa -à Same as AT+MBFUN=aa
672 +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.
786 786  
674 +Default value: 0, range:  0 ~~ 65 seconds
787 787  
788 -==== RS485 command timeout ====
676 +* **AT Command:**
789 789  
790 -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.
678 +(% class="box infomessage" %)
679 +(((
680 +**AT+CMDDLaa=hex(bb cc)*1000**
681 +)))
791 791  
792 -Default value: 0, range:  0 ~~ 5 seconds
683 +**Example:**
793 793  
685 +**AT+CMDDL1=1000** to send the open time to 1000ms
794 794  
795 -* AT Command:
796 796  
797 -AT+CMDDLaa=hex(bb cc)
688 +* **Downlink Payload:**
798 798  
799 -Example:
690 +**0x AA aa bb cc**
800 800  
801 -**AT+CMDDL1=1000** to send the open time to 1000ms
692 +Same as: AT+CMDDLaa=hex(bb cc)*1000
802 802  
694 + **Example:**
803 803  
804 -* Downlink Payload:
696 + 0xAA 01 00 01  ~-~-> Same as **AT+CMDDL1=1000 ms**
805 805  
806 -0x AA aa bb cc
807 807  
808 -Same as: AT+CMDDLaa=hex(bb cc)
809 809  
810 - Example:
700 +==== **Uplink payload mode** ====
811 811  
812 - 0xAA 01 03 E8  à Same as **AT+CMDDL1=1000 ms**
702 +Define to use one uplink or multiple uplinks for the sampling.
813 813  
704 +The use of this command please see: [[Compose Uplink payload>>||anchor="H3.3.4Composetheuplinkpayload"]]
814 814  
815 -==== [[Uplink>>path:#downlink_A8]] payload mode ====
706 +* **AT Command:**
816 816  
817 -Define to use one uplink or multiple uplinks for the sampling.
708 +(% class="box infomessage" %)
709 +(((
710 +**AT+DATAUP=0**
711 +)))
818 818  
819 -The use of this command please see: [[Compose Uplink payload>>path:#DataUP]]
713 +(% class="box infomessage" %)
714 +(((
715 +**AT+DATAUP=1**
716 +)))
820 820  
821 -* AT Command:
822 822  
823 -AT+DATAUP=0
719 +* **Downlink Payload:**
824 824  
825 -AT+DATAUP=1
721 +**0xAD 00**  **~-~->** Same as AT+DATAUP=0
826 826  
723 +**0xAD 01**  **~-~->** Same as AT+DATAUP=1
827 827  
828 -* Downlink Payload:
829 829  
830 -0xAD 00   à Same as AT+DATAUP=0
831 831  
832 -0xAD 01   à Same as AT+DATAUP=1
727 +==== **Manually trigger an Uplink** ====
833 833  
729 +Ask device to send an uplink immediately.
834 834  
835 -==== Manually trigger an Uplink ====
731 +* **AT Command:**
836 836  
837 -Ask device to send an uplink immediately.
733 +No AT Command for this, user can press the [[ACT button>>||anchor="H3.7Buttons"]] for 1 second for the same.
838 838  
839 -* Downlink Payload:
840 840  
841 -0x08 FF, RS485-BL will immediately send an uplink.
736 +* **Downlink Payload:**
842 842  
738 +**0x08 FF**, RS485-LN will immediately send an uplink.
843 843  
844 -==== Clear RS485 Command ====
845 845  
846 -The AT+COMMANDx and AT+DATACUTx settings are stored in special location, user can use below command to clear them.
847 847  
742 +==== **Clear RS485 Command** ====
848 848  
849 -* AT Command:
744 +The AT+COMMANDx and AT+DATACUTx settings are stored in special location, user can use below command to clear them.
850 850  
746 +* **AT Command:**
747 +
851 851  **AT+CMDEAR=mm,nn**   mm: start position of erase ,nn: stop position of erase
852 852  
853 853  Etc. AT+CMDEAR=1,10 means erase AT+COMMAND1/AT+DATACUT1 to AT+COMMAND10/AT+DATACUT10
... ... @@ -855,43 +855,50 @@
855 855  Example screen shot after clear all RS485 commands. 
856 856  
857 857  
858 -
859 859  The uplink screen shot is:
860 860  
861 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]
757 +[[image:1654160691922-496.png]]
862 862  
863 863  
864 -* Downlink Payload:
760 +* **Downlink Payload:**
865 865  
866 -0x09 aa bb same as AT+CMDEAR=aa,bb
762 +**0x09 aa bb** same as AT+CMDEAR=aa,bb
867 867  
868 868  
869 -==== Set Serial Communication Parameters ====
870 870  
766 +==== **Set Serial Communication Parameters** ====
767 +
871 871  Set the Rs485 serial communication parameters:
872 872  
873 -* AT Command:
770 +* **AT Command:**
874 874  
875 875  Set Baud Rate:
876 876  
877 -AT+BAUDR=9600    ~/~/ Options: (1200,2400,4800,14400,19200,115200)
774 +(% class="box infomessage" %)
775 +(((
776 +**AT+BAUDR=9600**    ~/~/ Options: (1200,2400,4800,14400,19200,115200)
777 +)))
878 878  
779 +Set UART Parity
879 879  
880 -Set UART parity
781 +(% class="box infomessage" %)
782 +(((
783 +**AT+PARITY=0**    ~/~/ Option: 0: no parity, 1: odd parity, 2: even parity
784 +)))
881 881  
882 -AT+PARITY=0    ~/~/ Option: 0: no parity, 1: odd parity, 2: even parity
883 -
884 -
885 885  Set STOPBIT
886 886  
887 -AT+STOPBIT=0    ~/~/ Option: 0 for 1bit; 1 for 1.5 bit ; 2 for 2 bits
788 +(% class="box infomessage" %)
789 +(((
790 +**AT+STOPBIT=0**    ~/~/ Option: 0 for 1bit; 1 for 1.5 bit ; 2 for 2 bits
791 +)))
888 888  
889 889  
890 -* Downlink Payload:
794 +* **Downlink Payload:**
891 891  
892 -A7 01 aa bb: Same  AT+BAUDR=hex(aa bb)*100
796 +**A7 01 aa bb**: Same  AT+BAUDR=hex(aa bb)*100
893 893  
894 -Example:
798 +**Example:**
895 895  
896 896  * A7 01 00 60   same as AT+BAUDR=9600
897 897  * A7 01 04 80  same as AT+BAUDR=115200
... ... @@ -901,189 +901,171 @@
901 901  A7 03 aa: Same as  AT+STOPBIT=aa  (aa value: 00 , 01 or 02)
902 902  
903 903  
904 -==== Control output power duration ====
808 +== 3.6 Listening mode for RS485 network ==
905 905  
906 -User can set the output power duration before each sampling.
810 +This feature support since firmware v1.4
907 907  
908 -* AT Command:
812 +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.
909 909  
910 -Example:
814 +[[image:image-20220602171200-8.png||height="567" width="1007"]]
911 911  
912 -AT+3V3T=1000 ~/~/ 3V3 output power will open 1s before each sampling.
816 +To enable the listening mode, use can run the command AT+RXMODE.
913 913  
914 -AT+5VT=1000 ~/~/ +5V output power will open 1s before each sampling.
915 915  
819 +(% border="1" style="background-color:#ffffcc; width:500px" %)
820 +|=(% style="width: 161px;" %)**Command example:**|=(% style="width: 337px;" %)**Function**
821 +|(% style="width:161px" %)AT+RXMODE=1,10 |(% style="width:337px" %)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.
822 +|(% style="width:161px" %)AT+RXMODE=2,500|(% style="width:337px" %)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
823 +|(% style="width:161px" %)AT+RXMODE=0,0|(% style="width:337px" %)Disable listening mode. This is the default settings.
824 +|(% style="width:161px" %) |(% style="width:337px" %)A6 aa bb cc  same as AT+RXMODE=aa,(bb<<8 ~| cc)
916 916  
917 -* LoRaWAN Downlink Command:
826 +**Downlink Command:**
918 918  
919 -07 01 aa bb  Same as AT+5VT=(aa bb)
828 +**0xA6 aa bb cc ** same as AT+RXMODE=aa,(bb<<8 | cc)
920 920  
921 -07 02 aa bb  Same as AT+3V3T=(aa bb)
922 922  
831 +**Example**:
923 923  
833 +The RS485-LN is set to AT+RXMODE=2,1000
924 924  
835 +There is a two Modbus commands in the RS485 network as below:
925 925  
926 -1.
927 -11. Buttons
837 +The Modbus master send a command: (% style="background-color:#ffc000" %)01 03 00 00 00 02 c4 0b
928 928  
929 -|**Button**|**Feature**
930 -|**RST**|Reboot RS485-BL
839 +And Modbus slave reply with: (% style="background-color:green" %)01 03 04 00 00 00 00 fa 33
931 931  
932 -1.
933 -11. +3V3 Output
841 +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
934 934  
935 -RS485-BL has a Controllable +3V3 output, user can use this output to power external sensor.
843 +[[image:image-20220602171200-9.png]]
936 936  
937 -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. 
938 938  
846 +(% 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.
939 939  
940 -The +3V3 output time can be controlled by AT Command.
941 941  
942 -**AT+3V3T=1000**
849 +== 3.7 Buttons ==
943 943  
944 -Means set +3v3 valid time to have 1000ms. So, the real +3v3 output will actually have 1000ms + sampling time for other sensors.
945 945  
852 +(% border="1" style="background-color:#f7faff; width:500px" %)
853 +|=**Button**|=(% style="width: 1420px;" %)**Feature**
854 +|**ACT**|(% style="width:1420px" %)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**
855 +|**RST**|(% style="width:1420px" %)Reboot RS485
856 +|**PRO**|(% style="width:1420px" %)Use for upload image, see [[How to Update Image>>||anchor="H6.1Howtoupgradetheimage3F"]]
946 946  
947 -By default, the AT+3V3T=0. This is a special case, means the +3V3 output is always on at any time
948 948  
949 949  
950 -1.
951 -11. +5V Output
860 +== 3.8 LEDs ==
952 952  
953 -RS485-BL has a Controllable +5V output, user can use this output to power external sensor.
862 +(% border="1" style="background-color:#f7faff; width:500px" %)
863 +|=**LEDs**|=**Feature**
864 +|**PWR**|Always on if there is power
865 +|**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.
954 954  
955 -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. 
956 956  
957 957  
958 -The 5V output time can be controlled by AT Command.
869 += 4. Case Study =
959 959  
960 -**AT+5VT=1000**
871 +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]]
961 961  
962 -Means set 5V valid time to have 1000ms. So, the real 5V output will actually have 1000ms + sampling time for other sensors.
963 963  
874 += 5. Use AT Command =
964 964  
965 -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.
876 +== 5.1 Access AT Command ==
966 966  
878 +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.
967 967  
880 +[[image:1654162355560-817.png]]
968 968  
969 969  
970 -1.
971 -11. LEDs
883 +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:
972 972  
973 -|**LEDs**|**Feature**
974 -|**LED1**|Blink when device transmit a packet.
885 +[[image:1654162368066-342.png]]
975 975  
976 -1.
977 -11. Switch Jumper
978 978  
979 -|**Switch Jumper**|**Feature**
980 -|**SW1**|(((
981 -ISP position: Upgrade firmware via UART
888 +More detail AT Command manual can be found at [[AT Command Manual>>||anchor="3.5ConfigureRS485-BLviaATorDownlink"]]
982 982  
983 -Flash position: Configure device, check running status.
984 -)))
985 -|**SW2**|(((
986 -5V position: set to compatible with 5v I/O.
987 987  
988 -3.3v position: set to compatible with 3.3v I/O.,
989 -)))
891 +== 5.2 Common AT Command Sequence ==
990 990  
991 -+3.3V: is always ON
893 +=== 5.2.1 Multi-channel ABP mode (Use with SX1301/LG308) ===
992 992  
993 -+5V: Only open before every sampling. The time is by default, it is AT+5VT=0.  Max open time. 5000 ms.
895 +If device has not joined network yet:
994 994  
995 -1. Case Study
897 +(% class="box infomessage" %)
898 +(((
899 +**AT+FDR**
900 +)))
996 996  
997 -User can check this URL for some case studies.
902 +(% class="box infomessage" %)
903 +(((
904 +**AT+NJM=0**
905 +)))
998 998  
999 -[[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]]
907 +(% class="box infomessage" %)
908 +(((
909 +**ATZ**
910 +)))
1000 1000  
1001 1001  
913 +If device already joined network:
1002 1002  
915 +(% class="box infomessage" %)
916 +(((
917 +**AT+NJM=0**
918 +)))
1003 1003  
1004 -1. Use AT Command
1005 -11. Access AT Command
920 +(% class="box infomessage" %)
921 +(((
922 +**ATZ**
923 +)))
1006 1006  
1007 -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.
1008 1008  
1009 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image027.png]]
926 +=== 5.5.2 Single-channel ABP mode (Use with LG01/LG02) ===
1010 1010  
1011 1011  
1012 -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:
929 +(% style="background-color:#dcdcdc" %)**AT+FDR** (%%) Reset Parameters to Factory Default, Keys Reserve
1013 1013  
1014 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image028.png]]
931 +(% style="background-color:#dcdcdc" %)**AT+NJM=0 **(%%)Set to ABP mode
1015 1015  
933 +(% style="background-color:#dcdcdc" %)**AT+ADR=0** (%%)Set the Adaptive Data Rate Off
1016 1016  
935 +(% style="background-color:#dcdcdc" %)**AT+DR=5**   (%%)Set Data Rate
1017 1017  
1018 -More detail AT Command manual can be found at [[AT Command Manual>>path:#AT_COMMAND]]
937 +(% style="background-color:#dcdcdc" %)**AT+TDC=60000** (%%) Set transmit interval to 60 seconds
1019 1019  
939 +(% style="background-color:#dcdcdc" %)**AT+CHS=868400000**(%%) Set transmit frequency to 868.4Mhz
1020 1020  
941 +(% style="background-color:#dcdcdc" %)**AT+RX2FQ=868400000** (%%) Set RX2Frequency to 868.4Mhz (according to the result from server)
1021 1021  
1022 -1.
1023 -11. Common AT Command Sequence
1024 -111. Multi-channel ABP mode (Use with SX1301/LG308)
943 +(% style="background-color:#dcdcdc" %)**AT+RX2DR=5**  (%%) Set RX2DR to match the downlink DR from server. see below
1025 1025  
1026 -If device has not joined network yet:
945 +(% 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.
1027 1027  
1028 -AT+FDR
947 +(% style="background-color:#dcdcdc" %)**ATZ**       (%%) Reset MCU
1029 1029  
1030 -AT+NJM=0
1031 1031  
1032 -ATZ
950 +(% style="color:red" %)**Note:**
1033 1033  
952 +(% style="color:red" %)1. Make sure the device is set to ABP mode in the IoT Server.
953 +2. Make sure the LG01/02 gateway RX frequency is exactly the same as AT+CHS setting.
954 +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.
955 +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
1034 1034  
1035 -If device already joined network:
957 +[[image:1654162478620-421.png]]
1036 1036  
1037 -AT+NJM=0
1038 1038  
1039 -ATZ
960 += 6. FAQ =
1040 1040  
1041 -1.
1042 -11.
1043 -111. Single-channel ABP mode (Use with LG01/LG02)
962 +== 6.1 How to upgrade the image? ==
1044 1044  
1045 -AT+FDR   Reset Parameters to Factory Default, Keys Reserve
964 +The RS485-LN LoRaWAN Controller is shipped with a 3.5mm cable, the cable is used to upload image to RS485-LN to:
1046 1046  
1047 -AT+NJM=0 Set to ABP mode
1048 -
1049 -AT+ADR=0 Set the Adaptive Data Rate Off
1050 -
1051 -AT+DR=5  Set Data Rate
1052 -
1053 -AT+TDC=60000  Set transmit interval to 60 seconds
1054 -
1055 -AT+CHS=868400000 Set transmit frequency to 868.4Mhz
1056 -
1057 -AT+RX2FQ=868400000 Set RX2Frequency to 868.4Mhz (according to the result from server)
1058 -
1059 -AT+RX2DR=5  Set RX2DR to match the downlink DR from server. see below
1060 -
1061 -AT+DADDR=26 01 1A F1 Set Device Address to 26 01 1A F1, this ID can be found in the LoRa Server portal.
1062 -
1063 -ATZ          Reset MCU
1064 -
1065 -**Note:**
1066 -
1067 -1. Make sure the device is set to ABP mode in the IoT Server.
1068 -1. Make sure the LG01/02 gateway RX frequency is exactly the same as AT+CHS setting.
1069 -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.
1070 -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
1071 -
1072 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image029.png]]
1073 -
1074 -
1075 -1. FAQ
1076 -11. How to upgrade the image?
1077 -
1078 -The RS485-BL LoRaWAN Controller is shipped with a 3.5mm cable, the cable is used to upload image to RS485-BL to:
1079 -
1080 1080  * Support new features
1081 1081  * For bug fix
1082 1082  * Change LoRaWAN bands.
1083 1083  
1084 -Below shows the hardware connection for how to upload an image to RS485-BL:
970 +Below shows the hardware connection for how to upload an image to RS485-LN:
1085 1085  
1086 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image030.png]]
972 +[[image:1654162535040-878.png]]
1087 1087  
1088 1088  **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]].
1089 1089  
... ... @@ -1091,84 +1091,75 @@
1091 1091  
1092 1092  **Step3: **Open flashloader; choose the correct COM port to update.
1093 1093  
980 +(% 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.
1094 1094  
1095 -|(((
1096 -HOLD PRO then press the RST button, SYS will be ON, then click next
1097 -)))
1098 1098  
1099 -|(((
1100 -Board detected
1101 -)))
983 +[[image:image-20220602175818-12.png]]
1102 1102  
1103 -|(((
1104 -
1105 -)))
1106 1106  
1107 -[[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]]
986 +[[image:image-20220602175848-13.png]]
1108 1108  
1109 1109  
989 +[[image:image-20220602175912-14.png]]
1110 1110  
1111 -[[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]]
1112 1112  
992 +**Notice**: In case user has lost the program cable. User can hand made one from a 3.5mm cable. The pin mapping is:
1113 1113  
1114 -[[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]]
994 +[[image:image-20220602175638-10.png]]
1115 1115  
1116 1116  
1117 -1.
1118 -11. How to change the LoRa Frequency Bands/Region?
997 +== 6.2 How to change the LoRa Frequency Bands/Region? ==
1119 1119  
1120 -User can follow the introduction for [[how to upgrade image>>path:#upgrade_image]]. When download the images, choose the required image file for download.
999 +User can follow the introduction for [[how to upgrade image>>||anchor="H6.1Howtoupgradetheimage3F"]]. When download the images, choose the required image file for download.
1121 1121  
1122 1122  
1002 +== 6.3 How many RS485-Slave can RS485-BL connects? ==
1123 1123  
1124 -1.
1125 -11. How many RS485-Slave can RS485-BL connects?
1004 +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"]].
1126 1126  
1127 -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]].
1128 1128  
1007 +== 6.4 Compatible question to ChirpStack and TTI LoRaWAN server ? ==
1129 1129  
1009 +When user need to use with ChirpStack or TTI. Please set AT+RPL=4.
1130 1130  
1011 +Detail info check this link: [[Set Packet Receiving Response Level>>doc:Main.End Device AT Commands and Downlink Command.WebHome||anchor="H7.23SetPacketReceivingResponseLevel"]]
1131 1131  
1132 -1. Trouble Shooting     
1133 -11. Downlink doesn’t work, how to solve it?
1134 1134  
1135 -Please see this link for debug:
1014 += 7. Trouble Shooting =
1136 1136  
1137 -[[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]] 
1016 +== 7.1 Downlink doesn’t work, how to solve it? ==
1138 1138  
1018 +Please see this link for debug: [[LoRaWAN Communication Debug>>doc:Main.LoRaWAN Communication Debug.WebHome]]
1139 1139  
1140 1140  
1141 -1.
1142 -11. Why I can’t join TTN V3 in US915 /AU915 bands?
1021 +== 7.2 Why I can’t join TTN V3 in US915 /AU915 bands? ==
1143 1143  
1144 -It might about the channels mapping. Please see for detail.
1023 +It might about the channels mapping. Please see for detail: [[Notice of Frequency band>>doc:Main.LoRaWAN Communication Debug.WebHome||anchor="H2.NoticeofUS9152FCN4702FAU915Frequencyband"]]
1145 1145  
1146 -[[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]]
1147 1147  
1026 += 8. Order Info =
1148 1148  
1028 +(% style="color:blue" %)**Part Number: RS485-LN-XXX**
1149 1149  
1150 -1. Order Info
1030 +(% style="color:blue" %)**XXX:**
1151 1151  
1152 -**Part Number: RS485-BL-XXX**
1032 +* (% style="color:blue" %)**EU433**(%%): frequency bands EU433
1033 +* (% style="color:blue" %)**EU868**(%%): frequency bands EU868
1034 +* (% style="color:blue" %)**KR920**(%%): frequency bands KR920
1035 +* (% style="color:blue" %)**CN470**(%%): frequency bands CN470
1036 +* (% style="color:blue" %)**AS923**(%%): frequency bands AS923
1037 +* (% style="color:blue" %)**AU915**(%%): frequency bands AU915
1038 +* (% style="color:blue" %)**US915**(%%): frequency bands US915
1039 +* (% style="color:blue" %)**IN865**(%%): frequency bands IN865
1040 +* (% style="color:blue" %)**RU864**(%%): frequency bands RU864
1041 +* (% style="color:blue" %)**KZ865**(%%): frequency bands KZ865
1153 1153  
1154 -**XXX:**
1043 += 9.Packing Info =
1155 1155  
1156 -* **EU433**: frequency bands EU433
1157 -* **EU868**: frequency bands EU868
1158 -* **KR920**: frequency bands KR920
1159 -* **CN470**: frequency bands CN470
1160 -* **AS923**: frequency bands AS923
1161 -* **AU915**: frequency bands AU915
1162 -* **US915**: frequency bands US915
1163 -* **IN865**: frequency bands IN865
1164 -* **RU864**: frequency bands RU864
1165 -* **KZ865: **frequency bands KZ865
1166 1166  
1167 -1. Packing Info
1168 -
1169 1169  **Package Includes**:
1170 1170  
1171 -* RS485-BL x 1
1048 +* RS485-LN x 1
1172 1172  * Stick Antenna for LoRa RF part x 1
1173 1173  * Program cable x 1
1174 1174  
... ... @@ -1179,9 +1179,32 @@
1179 1179  * Package Size / pcs : 14.5 x 8 x 5 cm
1180 1180  * Weight / pcs : 170g
1181 1181  
1182 -1. Support
1059 += 10. FCC Caution for RS485LN-US915 =
1183 1183  
1184 -* 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.
1185 -* 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
1061 +Any Changes or modifications not expressly approved by the party responsible for compliance could void the user's authority to operate the equipment.
1186 1186  
1187 -[[support@dragino.com>>url:file:///D:/市场资料/说明书/LoRa/LT系列/support@dragino.com]]
1063 +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.
1064 +
1065 +
1066 +**IMPORTANT NOTE:**
1067 +
1068 +**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:
1069 +
1070 +—Reorient or relocate the receiving antenna.
1071 +
1072 +—Increase the separation between the equipment and receiver.
1073 +
1074 +—Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.
1075 +
1076 +—Consult the dealer or an experienced radio/TV technician for help.
1077 +
1078 +
1079 +**FCC Radiation Exposure Statement:**
1080 +
1081 +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.
1082 +
1083 +
1084 += 11. Support =
1085 +
1086 +* 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.
1087 +* 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]].
1653269403619-508.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +27.8 KB
Content
1653269438444-278.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +26.6 KB
Content
1653269551753-223.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +138.7 KB
Content
1653269568276-930.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +131.4 KB
Content
1653269593172-426.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +142.6 KB
Content
1653269618463-608.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +27.7 KB
Content
1653269759169-150.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +294.0 KB
Content
1653269916228-732.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +143.3 KB
Content
1653270130359-810.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +197.8 KB
Content
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