Last modified by Xiaoling on 2025/04/23 15:56
<
From version < 22.5 >
edited by Xiaoling
on 2022/05/23 09:15
To version < 41.1 >
edited by Xiaoling
on 2022/06/02 16:35
>
Change comment: There is no comment for this version

Summary

Details

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

Applications

Navigation

Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0