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