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

Applications

Navigation

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