Last modified by Xiaoling on 2025/04/23 15:56
<
From version < 32.4 >
edited by Xiaoling
on 2022/06/02 15:24
To version < 46.1 >
edited by Xiaoling
on 2022/06/02 17:12
>
Change comment: Uploaded new attachment "image-20220602171200-8.png", version {1}

Summary

Details

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

Applications

Navigation

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