Last modified by Karry Zhuang on 2025/03/06 16:34
<
From version < 32.4 >
edited by Xiaoling
on 2022/06/02 15:24
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
... ... @@ -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,138 +488,98 @@
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 {
496 +There are two kinds of Commands:
574 574  
575 - ~/~/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]]
576 576  
577 - 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:
578 578  
579 - ~/~/GPIO_EXTI 
580 580  
581 - EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE",
582 582  
583 - ~/~/payload of version
504 +=== 3.5.1 Common Commands ===
584 584  
585 - 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]]
586 586  
587 - };
588 588  
589 - }
509 +=== 3.5.2 Sensor related commands: ===
590 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 -There are two kinds of Commands:
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
609 -
610 -* **Sensor Related Commands**: These commands are special designed for RS485-BL.  User can see these commands below:
611 -
612 -1.
613 -11.
614 -111. Common Commands:
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]]
617 -
618 -
619 -1.
620 -11.
621 -111. Sensor related commands:
622 -
623 623  ==== Choose Device Type (RS485 or TTL) ====
624 624  
625 625  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