Last modified by Karry Zhuang on 2025/03/06 16:34
<
From version < 32.9 >
edited by Xiaoling
on 2022/06/02 15:25
To version < 40.1 >
edited by Xiaoling
on 2022/06/02 16:33
>
Change comment: Uploaded new attachment "image-20220602163333-5.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -76,8 +76,6 @@
76 76  * Automatic RF Sense and CAD with ultra-fast AFC.
77 77  * Packet engine up to 256 bytes with CRC.
78 78  
79 -
80 -
81 81  == 1.3 Features ==
82 82  
83 83  * LoRaWAN Class A & Class C protocol (default Class C)
... ... @@ -89,8 +89,6 @@
89 89  * Support Modbus protocol
90 90  * Support Interrupt uplink (Since hardware version v1.2)
91 91  
92 -
93 -
94 94  == 1.4 Applications ==
95 95  
96 96  * Smart Buildings & Home Automation
... ... @@ -100,12 +100,11 @@
100 100  * Smart Cities
101 101  * Smart Factory
102 102  
103 -
104 -
105 105  == 1.5 Firmware Change log ==
106 106  
107 107  [[RS485-LN Image files – Download link and Change log>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/]]
108 108  
103 +
109 109  == 1.6 Hardware Change log ==
110 110  
111 111  (((
... ... @@ -113,6 +113,8 @@
113 113  v1.2: Add External Interrupt Pin.
114 114  
115 115  v1.0: Release
111 +
112 +
116 116  )))
117 117  )))
118 118  
... ... @@ -129,6 +129,8 @@
129 129  )))
130 130  
131 131  [[image:1653268091319-405.png]]
129 +
130 +
132 132  )))
133 133  
134 134  = 3. Operation Mode =
... ... @@ -137,6 +137,8 @@
137 137  
138 138  (((
139 139  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 +
140 140  )))
141 141  
142 142  == 3.2 Example to join LoRaWAN network ==
... ... @@ -145,10 +145,15 @@
145 145  
146 146  [[image:1653268155545-638.png||height="334" width="724"]]
147 147  
149 +
148 148  (((
151 +(((
149 149  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 +)))
150 150  
155 +(((
151 151  485A+ and 485B- of the sensor are connected to RS485A and RA485B of RS485-LN respectively.
157 +)))
152 152  
153 153  [[image:1653268227651-549.png||height="592" width="720"]]
154 154  
... ... @@ -200,6 +200,7 @@
200 200  
201 201  [[image:1652953568895-172.png||height="232" width="724"]]
202 202  
209 +
203 203  == 3.3 Configure Commands to read data ==
204 204  
205 205  (((
... ... @@ -209,6 +209,8 @@
209 209  
210 210  (((
211 211  (% 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 +
212 212  )))
213 213  )))
214 214  
... ... @@ -216,19 +216,19 @@
216 216  
217 217  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:
218 218  
219 -(% border="1" style="background-color:#ffffcc; color:green; width:795px" %)
220 -|(((
228 +(% border="1" style="background-color:#ffffcc; color:green; width:782px" %)
229 +|(% style="width:128px" %)(((
221 221  **AT Commands**
222 -)))|(% style="width:285px" %)(((
231 +)))|(% style="width:305px" %)(((
223 223  **Description**
224 -)))|(% style="width:347px" %)(((
233 +)))|(% style="width:346px" %)(((
225 225  **Example**
226 226  )))
227 -|(((
236 +|(% style="width:128px" %)(((
228 228  AT+BAUDR
229 -)))|(% style="width:285px" %)(((
238 +)))|(% style="width:305px" %)(((
230 230  Set the baud rate (for RS485 connection). Default Value is: 9600.
231 -)))|(% style="width:347px" %)(((
240 +)))|(% style="width:346px" %)(((
232 232  (((
233 233  AT+BAUDR=9600
234 234  )))
... ... @@ -237,11 +237,11 @@
237 237  Options: (1200,2400,4800,14400,19200,115200)
238 238  )))
239 239  )))
240 -|(((
249 +|(% style="width:128px" %)(((
241 241  AT+PARITY
242 -)))|(% style="width:285px" %)(((
251 +)))|(% style="width:305px" %)(((
243 243  Set UART parity (for RS485 connection)
244 -)))|(% style="width:347px" %)(((
253 +)))|(% style="width:346px" %)(((
245 245  (((
246 246  AT+PARITY=0
247 247  )))
... ... @@ -250,9 +250,9 @@
250 250  Option: 0: no parity, 1: odd parity, 2: even parity
251 251  )))
252 252  )))
253 -|(((
262 +|(% style="width:128px" %)(((
254 254  AT+STOPBIT
255 -)))|(% style="width:285px" %)(((
264 +)))|(% style="width:305px" %)(((
256 256  (((
257 257  Set serial stopbit (for RS485 connection)
258 258  )))
... ... @@ -260,7 +260,7 @@
260 260  (((
261 261  
262 262  )))
263 -)))|(% style="width:347px" %)(((
272 +)))|(% style="width:346px" %)(((
264 264  (((
265 265  AT+STOPBIT=0 for 1bit
266 266  )))
... ... @@ -295,77 +295,34 @@
295 295  === 3.3.3 Configure read commands for each sampling ===
296 296  
297 297  (((
298 -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.
299 -)))
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.
300 300  
301 -(((
302 -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.
303 -)))
304 -
305 -(((
306 306  To save the LoRaWAN network bandwidth, we might need to read data from different sensors and combine their valid value into a short payload.
307 -)))
308 308  
309 -(((
310 310  This section describes how to achieve above goals.
311 -)))
312 312  
313 -(((
314 -During each sampling, the RS485-BL can support 15 commands to read sensors. And combine the return to one or several uplink payloads.
315 -)))
313 +During each sampling, the RS485-LN can support 15 commands to read sensors. And combine the return to one or several uplink payloads.
316 316  
317 -(((
318 -**Command from RS485-BL to Sensor:**
319 -)))
320 320  
321 -(((
322 -RS485-BL can send out pre-set max 15 strings via **AT+COMMAD1**, **ATCOMMAND2**,…, to **AT+COMMANDF** . All commands are of same grammar.
323 -)))
316 +**Each RS485 commands include two parts:**
324 324  
325 -(((
326 -**Handle return from sensors to RS485-BL**:
327 -)))
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.
328 328  
329 -(((
330 -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**
331 -)))
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.
332 332  
333 -* (((
334 -**AT+DATACUT**
335 -)))
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
336 336  
337 -(((
338 -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.
339 -)))
340 340  
341 -* (((
342 -**AT+SEARCH**
343 -)))
344 -
345 -(((
346 -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.
347 -)))
348 -
349 -(((
350 -**Define wait timeout:**
351 -)))
352 -
353 -(((
354 -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
355 -)))
356 -
357 -(((
358 358  After we got the valid value from each RS485 commands, we need to combine them together with the command **AT+DATAUP**.
359 -)))
360 360  
361 -**Examples:**
362 362  
363 363  Below are examples for the how above AT Commands works.
364 364  
365 -**AT+COMMANDx : **This command will be sent to RS485/TTL devices during each sampling, Max command length is 14 bytes. The grammar is:
366 366  
367 -(% border="1" class="table-bordered" %)
368 -|(((
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" %)(((
369 369  **AT+COMMANDx=xx xx xx xx xx xx xx xx xx xx xx xx,m**
370 370  
371 371  **xx xx xx xx xx xx xx xx xx xx xx xx: The RS485 command to be sent**
... ... @@ -373,49 +373,15 @@
373 373  **m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command**
374 374  )))
375 375  
376 -(((
377 377  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.
378 -)))
379 379  
380 -(((
381 -In the RS485-BL, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
382 -)))
344 +In the RS485-LN, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
383 383  
384 -(((
385 -**AT+SEARCHx**: This command defines how to handle the return from AT+COMMANDx.
386 -)))
387 387  
388 -(% border="1" class="table-bordered" %)
389 -|(((
390 -**AT+SEARCHx=aa,xx xx xx xx xx**
391 -
392 -* **aa: 1: prefix match mode; 2: prefix and suffix match mode**
393 -* **xx xx xx xx xx: match string. Max 5 bytes for prefix and 5 bytes for suffix**
394 -
395 -
396 -)))
397 -
398 -**Examples:**
399 -
400 -~1. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
401 -
402 -If we set AT+SEARCH1=1,1E 56 34.      (max 5 bytes for prefix)
403 -
404 -The valid data will be all bytes after 1E 56 34 , so it is (% style="background-color:yellow" %)** 2e 30 58 5f 36 41 30 31 00 49**
405 -
406 -[[image:1653269403619-508.png]]
407 -
408 -2. For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
409 -
410 -If we set AT+SEARCH1=2, 1E 56 34+31 00 49
411 -
412 -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**
413 -
414 -[[image:1653269438444-278.png]]
415 -
416 416  **AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes.
417 417  
418 -|(((
349 +(% border="1" style="background-color:#4bacc6; color:white; width:725px" %)
350 +|(% style="width:722px" %)(((
419 419  **AT+DATACUTx=a,b,c**
420 420  
421 421  * **a: length for the return of AT+COMMAND**
... ... @@ -423,48 +423,37 @@
423 423  * **c: define the position for valid value.  **
424 424  )))
425 425  
426 -Examples:
358 +**Examples:**
427 427  
428 428  * Grab bytes:
429 429  
430 -[[image:1653269551753-223.png||height="311" width="717"]]
362 +[[image:image-20220602153621-1.png]]
431 431  
364 +
432 432  * Grab a section.
433 433  
434 -[[image:1653269568276-930.png||height="325" width="718"]]
367 +[[image:image-20220602153621-2.png]]
435 435  
369 +
436 436  * Grab different sections.
437 437  
438 -[[image:1653269593172-426.png||height="303" width="725"]]
372 +[[image:image-20220602153621-3.png]]
439 439  
440 -(% style="color:red" %)**Note:**
374 +
375 +)))
441 441  
442 -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.
443 -
444 -Example:
445 -
446 -(% style="color:red" %)AT+COMMAND1=11 01 1E D0,0
447 -
448 -(% style="color:red" %)AT+SEARCH1=1,1E 56 34
449 -
450 -(% style="color:red" %)AT+DATACUT1=0,2,1~~5
451 -
452 -(% style="color:red" %)Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
453 -
454 -(% style="color:red" %)String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
455 -
456 -(% style="color:red" %)Valid payload after DataCUT command: 2e 30 58 5f 36
457 -
458 -[[image:1653269618463-608.png]]
459 -
460 460  === 3.3.4 Compose the uplink payload ===
461 461  
462 462  (((
463 463  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 +
464 464  )))
465 465  
466 466  (((
467 -(% style="color:#4f81bd" %)**Examples: AT+DATAUP=0**
386 +(% style="color:#037691" %)**Examples: AT+DATAUP=0**
387 +
388 +
468 468  )))
469 469  
470 470  (((
... ... @@ -485,8 +485,10 @@
485 485  
486 486  [[image:1653269759169-150.png||height="513" width="716"]]
487 487  
488 -(% style="color:#4f81bd" %)**Examples: AT+DATAUP=1**
489 489  
410 +(% style="color:#037691" %)**Examples: AT+DATAUP=1**
411 +
412 +
490 490  Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**Multiply UPLINKs**.
491 491  
492 492  Final Payload is
... ... @@ -493,138 +493,98 @@
493 493  
494 494  (% style="color:#4f81bd" %)**Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA**
495 495  
496 -1. Battery Info (2 bytes): Battery voltage
497 -1. PAYVER (1 byte): Defined by AT+PAYVER
498 -1. PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling.
499 -1. PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
500 -1. DATA: Valid value: max 6 bytes(US915 version here, Notice*!) 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
501 501  
502 -[[image:1653269916228-732.png||height="433" width="711"]]
424 +[[image:image-20220602155039-4.png]]
503 503  
504 504  
505 -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
506 506  
507 -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**
508 508  
509 -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**
510 510  
511 -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**
512 512  
513 -Below are the uplink payloads:
514 514  
515 -[[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:
516 516  
438 + ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink.
517 517  
518 -(% 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.
519 519  
520 - ~* 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.
521 521  
522 - * 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.
523 523  
524 - * For US915 band, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date).
525 525  
526 - ~* For all other bands: max 51 bytes for each uplink  ( so 51 -5 = 46 max valid date).
447 +Below are the uplink payloads:
527 527  
449 +[[image:1654157178836-407.png]]
450 +
451 +
528 528  === 3.3.5 Uplink on demand ===
529 529  
530 -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.
531 531  
532 532  Downlink control command:
533 533  
534 -[[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.
535 535  
536 -[[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.
537 537  
538 538  
539 539  
540 -1.
541 -11.
542 -111. Uplink on Interrupt
464 +=== 3.3.6 Uplink on Interrupt ===
543 543  
544 -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.
545 545  
546 -AT+INTMOD=0  Disable Interrupt
468 +[[image:1654157342174-798.png]]
547 547  
548 -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.
549 549  
550 -AT+INTMOD=2  Interrupt trigger by falling edge. ( Default Value)
551 551  
552 -AT+INTMOD=3  Interrupt trigger by rising edge.
473 +== 3.4 Uplink Payload ==
553 553  
554 -
555 -1.
556 -11. Uplink Payload
557 -
558 -|**Size(bytes)**|**2**|**1**|**Length depends on the return from the commands**
559 -|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" %)(((
560 560  Battery(mV)
561 561  
562 562  &
563 563  
564 564  Interrupt _Flag
565 -)))|(((
483 +)))|(% style="width:116px" %)(((
566 566  PAYLOAD_VER
567 567  
568 568  
569 -)))|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.
570 570  
571 571  Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors.
572 572  
573 573  
574 -function Decoder(bytes, port) {
492 +== 3.5 Configure RS485-BL via AT or Downlink ==
575 575  
576 -~/~/Payload Formats of RS485-BL Deceive
494 +User can configure RS485-LN via AT Commands or LoRaWAN Downlink Commands
577 577  
578 -return {
496 +There are two kinds of Commands:
579 579  
580 - ~/~/Battery,units:V
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]]
581 581  
582 - BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000,
500 +* (% style="color:#4f81bd" %)**Sensor Related Commands**(%%): These commands are special designed for RS485-LN.  User can see these commands below:
583 583  
584 - ~/~/GPIO_EXTI 
585 585  
586 - EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE",
587 587  
588 - ~/~/payload of version
504 +=== 3.5.1 Common Commands ===
589 589  
590 - Pay_ver:bytes[2],
506 +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]]
591 591  
592 - };
593 593  
594 - }
509 +=== 3.5.2 Sensor related commands: ===
595 595  
596 -
597 -
598 -
599 -
600 -
601 -
602 -TTN V3 uplink screen shot.
603 -
604 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]
605 -
606 -1.
607 -11. Configure RS485-BL via AT or Downlink
608 -
609 -User can configure RS485-BL via [[AT Commands >>path:#_​Using_the_AT]]or LoRaWAN Downlink Commands
610 -
611 -There are two kinds of Commands:
612 -
613 -* **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
614 -
615 -* **Sensor Related Commands**: These commands are special designed for RS485-BL.  User can see these commands below:
616 -
617 -1.
618 -11.
619 -111. Common Commands:
620 -
621 -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]]
622 -
623 -
624 -1.
625 -11.
626 -111. Sensor related commands:
627 -
628 628  ==== Choose Device Type (RS485 or TTL) ====
629 629  
630 630  RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect.
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