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