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