Last modified by Karry Zhuang on 2025/03/06 16:34
<
From version < 32.10 >
edited by Xiaoling
on 2022/06/02 15:26
To version < 38.2 >
edited by Xiaoling
on 2022/06/02 16:10
>
Change comment: There is no comment for this version

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,8 +100,6 @@
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/]]
... ... @@ -132,6 +132,8 @@
132 132  )))
133 133  
134 134  [[image:1653268091319-405.png]]
129 +
130 +
135 135  )))
136 136  
137 137  = 3. Operation Mode =
... ... @@ -140,6 +140,8 @@
140 140  
141 141  (((
142 142  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 +
143 143  )))
144 144  
145 145  == 3.2 Example to join LoRaWAN network ==
... ... @@ -148,10 +148,15 @@
148 148  
149 149  [[image:1653268155545-638.png||height="334" width="724"]]
150 150  
149 +
151 151  (((
151 +(((
152 152  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 +)))
153 153  
155 +(((
154 154  485A+ and 485B- of the sensor are connected to RS485A and RA485B of RS485-LN respectively.
157 +)))
155 155  
156 156  [[image:1653268227651-549.png||height="592" width="720"]]
157 157  
... ... @@ -203,6 +203,7 @@
203 203  
204 204  [[image:1652953568895-172.png||height="232" width="724"]]
205 205  
209 +
206 206  == 3.3 Configure Commands to read data ==
207 207  
208 208  (((
... ... @@ -212,6 +212,8 @@
212 212  
213 213  (((
214 214  (% 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 +
215 215  )))
216 216  )))
217 217  
... ... @@ -219,19 +219,19 @@
219 219  
220 220  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:
221 221  
222 -(% border="1" style="background-color:#ffffcc; color:green; width:795px" %)
223 -|(((
228 +(% border="1" style="background-color:#ffffcc; color:green; width:782px" %)
229 +|(% style="width:128px" %)(((
224 224  **AT Commands**
225 -)))|(% style="width:285px" %)(((
231 +)))|(% style="width:305px" %)(((
226 226  **Description**
227 -)))|(% style="width:347px" %)(((
233 +)))|(% style="width:346px" %)(((
228 228  **Example**
229 229  )))
230 -|(((
236 +|(% style="width:128px" %)(((
231 231  AT+BAUDR
232 -)))|(% style="width:285px" %)(((
238 +)))|(% style="width:305px" %)(((
233 233  Set the baud rate (for RS485 connection). Default Value is: 9600.
234 -)))|(% style="width:347px" %)(((
240 +)))|(% style="width:346px" %)(((
235 235  (((
236 236  AT+BAUDR=9600
237 237  )))
... ... @@ -240,11 +240,11 @@
240 240  Options: (1200,2400,4800,14400,19200,115200)
241 241  )))
242 242  )))
243 -|(((
249 +|(% style="width:128px" %)(((
244 244  AT+PARITY
245 -)))|(% style="width:285px" %)(((
251 +)))|(% style="width:305px" %)(((
246 246  Set UART parity (for RS485 connection)
247 -)))|(% style="width:347px" %)(((
253 +)))|(% style="width:346px" %)(((
248 248  (((
249 249  AT+PARITY=0
250 250  )))
... ... @@ -253,9 +253,9 @@
253 253  Option: 0: no parity, 1: odd parity, 2: even parity
254 254  )))
255 255  )))
256 -|(((
262 +|(% style="width:128px" %)(((
257 257  AT+STOPBIT
258 -)))|(% style="width:285px" %)(((
264 +)))|(% style="width:305px" %)(((
259 259  (((
260 260  Set serial stopbit (for RS485 connection)
261 261  )))
... ... @@ -263,7 +263,7 @@
263 263  (((
264 264  
265 265  )))
266 -)))|(% style="width:347px" %)(((
272 +)))|(% style="width:346px" %)(((
267 267  (((
268 268  AT+STOPBIT=0 for 1bit
269 269  )))
... ... @@ -298,77 +298,34 @@
298 298  === 3.3.3 Configure read commands for each sampling ===
299 299  
300 300  (((
301 -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.
302 -)))
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.
303 303  
304 -(((
305 -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.
306 -)))
307 -
308 -(((
309 309  To save the LoRaWAN network bandwidth, we might need to read data from different sensors and combine their valid value into a short payload.
310 -)))
311 311  
312 -(((
313 313  This section describes how to achieve above goals.
314 -)))
315 315  
316 -(((
317 -During each sampling, the RS485-BL can support 15 commands to read sensors. And combine the return to one or several uplink payloads.
318 -)))
313 +During each sampling, the RS485-LN can support 15 commands to read sensors. And combine the return to one or several uplink payloads.
319 319  
320 -(((
321 -**Command from RS485-BL to Sensor:**
322 -)))
323 323  
324 -(((
325 -RS485-BL can send out pre-set max 15 strings via **AT+COMMAD1**, **ATCOMMAND2**,…, to **AT+COMMANDF** . All commands are of same grammar.
326 -)))
316 +**Each RS485 commands include two parts:**
327 327  
328 -(((
329 -**Handle return from sensors to RS485-BL**:
330 -)))
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.
331 331  
332 -(((
333 -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**
334 -)))
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.
335 335  
336 -* (((
337 -**AT+DATACUT**
338 -)))
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
339 339  
340 -(((
341 -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.
342 -)))
343 343  
344 -* (((
345 -**AT+SEARCH**
346 -)))
347 -
348 -(((
349 -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.
350 -)))
351 -
352 -(((
353 -**Define wait timeout:**
354 -)))
355 -
356 -(((
357 -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
358 -)))
359 -
360 -(((
361 361  After we got the valid value from each RS485 commands, we need to combine them together with the command **AT+DATAUP**.
362 -)))
363 363  
364 -**Examples:**
365 365  
366 366  Below are examples for the how above AT Commands works.
367 367  
368 -**AT+COMMANDx : **This command will be sent to RS485/TTL devices during each sampling, Max command length is 14 bytes. The grammar is:
369 369  
370 -(% border="1" class="table-bordered" %)
371 -|(((
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" %)(((
372 372  **AT+COMMANDx=xx xx xx xx xx xx xx xx xx xx xx xx,m**
373 373  
374 374  **xx xx xx xx xx xx xx xx xx xx xx xx: The RS485 command to be sent**
... ... @@ -376,49 +376,15 @@
376 376  **m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command**
377 377  )))
378 378  
379 -(((
380 380  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.
381 -)))
382 382  
383 -(((
384 -In the RS485-BL, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
385 -)))
344 +In the RS485-LN, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
386 386  
387 -(((
388 -**AT+SEARCHx**: This command defines how to handle the return from AT+COMMANDx.
389 -)))
390 390  
391 -(% border="1" class="table-bordered" %)
392 -|(((
393 -**AT+SEARCHx=aa,xx xx xx xx xx**
394 -
395 -* **aa: 1: prefix match mode; 2: prefix and suffix match mode**
396 -* **xx xx xx xx xx: match string. Max 5 bytes for prefix and 5 bytes for suffix**
397 -
398 -
399 -)))
400 -
401 -**Examples:**
402 -
403 -~1. 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=1,1E 56 34.      (max 5 bytes for prefix)
406 -
407 -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**
408 -
409 -[[image:1653269403619-508.png]]
410 -
411 -2. For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
412 -
413 -If we set AT+SEARCH1=2, 1E 56 34+31 00 49
414 -
415 -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**
416 -
417 -[[image:1653269438444-278.png]]
418 -
419 419  **AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes.
420 420  
421 -|(((
349 +(% border="1" style="background-color:#4bacc6; color:white; width:725px" %)
350 +|(% style="width:722px" %)(((
422 422  **AT+DATACUTx=a,b,c**
423 423  
424 424  * **a: length for the return of AT+COMMAND**
... ... @@ -426,48 +426,37 @@
426 426  * **c: define the position for valid value.  **
427 427  )))
428 428  
429 -Examples:
358 +**Examples:**
430 430  
431 431  * Grab bytes:
432 432  
433 -[[image:1653269551753-223.png||height="311" width="717"]]
362 +[[image:image-20220602153621-1.png]]
434 434  
364 +
435 435  * Grab a section.
436 436  
437 -[[image:1653269568276-930.png||height="325" width="718"]]
367 +[[image:image-20220602153621-2.png]]
438 438  
369 +
439 439  * Grab different sections.
440 440  
441 -[[image:1653269593172-426.png||height="303" width="725"]]
372 +[[image:image-20220602153621-3.png]]
442 442  
443 -(% style="color:red" %)**Note:**
374 +
375 +)))
444 444  
445 -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.
446 -
447 -Example:
448 -
449 -(% style="color:red" %)AT+COMMAND1=11 01 1E D0,0
450 -
451 -(% style="color:red" %)AT+SEARCH1=1,1E 56 34
452 -
453 -(% style="color:red" %)AT+DATACUT1=0,2,1~~5
454 -
455 -(% style="color:red" %)Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
456 -
457 -(% style="color:red" %)String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
458 -
459 -(% style="color:red" %)Valid payload after DataCUT command: 2e 30 58 5f 36
460 -
461 -[[image:1653269618463-608.png]]
462 -
463 463  === 3.3.4 Compose the uplink payload ===
464 464  
465 465  (((
466 466  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 +
467 467  )))
468 468  
469 469  (((
470 -(% style="color:#4f81bd" %)**Examples: AT+DATAUP=0**
386 +(% style="color:#037691" %)**Examples: AT+DATAUP=0**
387 +
388 +
471 471  )))
472 472  
473 473  (((
... ... @@ -488,8 +488,10 @@
488 488  
489 489  [[image:1653269759169-150.png||height="513" width="716"]]
490 490  
491 -(% style="color:#4f81bd" %)**Examples: AT+DATAUP=1**
492 492  
410 +(% style="color:#037691" %)**Examples: AT+DATAUP=1**
411 +
412 +
493 493  Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**Multiply UPLINKs**.
494 494  
495 495  Final Payload is
... ... @@ -496,66 +496,61 @@
496 496  
497 497  (% style="color:#4f81bd" %)**Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA**
498 498  
499 -1. Battery Info (2 bytes): Battery voltage
500 -1. PAYVER (1 byte): Defined by AT+PAYVER
501 -1. PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling.
502 -1. PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
503 -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
504 504  
505 -[[image:1653269916228-732.png||height="433" width="711"]]
424 +[[image:image-20220602155039-4.png]]
506 506  
507 507  
508 -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
509 509  
510 -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**
511 511  
512 -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**
513 513  
514 -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**
515 515  
516 -Below are the uplink payloads:
517 517  
518 -[[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:
519 519  
438 + ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink.
520 520  
521 -(% 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.
522 522  
523 - ~* 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.
524 524  
525 - * 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.
526 526  
527 - * For US915 band, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date).
528 528  
529 - ~* For all other bands: max 51 bytes for each uplink  ( so 51 -5 = 46 max valid date).
447 +Below are the uplink payloads:
530 530  
449 +[[image:1654157178836-407.png]]
450 +
451 +
531 531  === 3.3.5 Uplink on demand ===
532 532  
533 -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.
534 534  
535 535  Downlink control command:
536 536  
537 -[[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.
538 538  
539 -[[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.
540 540  
541 541  
542 542  
543 -1.
544 -11.
545 -111. Uplink on Interrupt
464 +=== 3.3.6 Uplink on Interrupt ===
546 546  
547 -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.
548 548  
549 -AT+INTMOD=0  Disable Interrupt
468 +[[image:1654157342174-798.png]]
550 550  
551 -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.
552 552  
553 -AT+INTMOD=2  Interrupt trigger by falling edge. ( Default Value)
554 554  
555 -AT+INTMOD=3  Interrupt trigger by rising edge.
556 -
557 -
558 -1.
473 +1.
559 559  11. Uplink Payload
560 560  
561 561  |**Size(bytes)**|**2**|**1**|**Length depends on the return from the commands**
... ... @@ -617,15 +617,15 @@
617 617  
618 618  * **Sensor Related Commands**: These commands are special designed for RS485-BL.  User can see these commands below:
619 619  
620 -1.
621 -11.
535 +1.
536 +11.
622 622  111. Common Commands:
623 623  
624 624  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]]
625 625  
626 626  
627 -1.
628 -11.
542 +1.
543 +11.
629 629  111. Sensor related commands:
630 630  
631 631  ==== Choose Device Type (RS485 or TTL) ====
... ... @@ -931,13 +931,13 @@
931 931  
932 932  
933 933  
934 -1.
849 +1.
935 935  11. Buttons
936 936  
937 937  |**Button**|**Feature**
938 938  |**RST**|Reboot RS485-BL
939 939  
940 -1.
855 +1.
941 941  11. +3V3 Output
942 942  
943 943  RS485-BL has a Controllable +3V3 output, user can use this output to power external sensor.
... ... @@ -955,7 +955,7 @@
955 955  By default, the AT+3V3T=0. This is a special case, means the +3V3 output is always on at any time
956 956  
957 957  
958 -1.
873 +1.
959 959  11. +5V Output
960 960  
961 961  RS485-BL has a Controllable +5V output, user can use this output to power external sensor.
... ... @@ -975,13 +975,13 @@
975 975  
976 976  
977 977  
978 -1.
893 +1.
979 979  11. LEDs
980 980  
981 981  |**LEDs**|**Feature**
982 982  |**LED1**|Blink when device transmit a packet.
983 983  
984 -1.
899 +1.
985 985  11. Switch Jumper
986 986  
987 987  |**Switch Jumper**|**Feature**
... ... @@ -1027,7 +1027,7 @@
1027 1027  
1028 1028  
1029 1029  
1030 -1.
945 +1.
1031 1031  11. Common AT Command Sequence
1032 1032  111. Multi-channel ABP mode (Use with SX1301/LG308)
1033 1033  
... ... @@ -1046,8 +1046,8 @@
1046 1046  
1047 1047  ATZ
1048 1048  
1049 -1.
1050 -11.
964 +1.
965 +11.
1051 1051  111. Single-channel ABP mode (Use with LG01/LG02)
1052 1052  
1053 1053  AT+FDR   Reset Parameters to Factory Default, Keys Reserve
... ... @@ -1122,7 +1122,7 @@
1122 1122  [[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image035.png]] [[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image036.png]]
1123 1123  
1124 1124  
1125 -1.
1040 +1.
1126 1126  11. How to change the LoRa Frequency Bands/Region?
1127 1127  
1128 1128  User can follow the introduction for [[how to upgrade image>>path:#upgrade_image]]. When download the images, choose the required image file for download.
... ... @@ -1129,7 +1129,7 @@
1129 1129  
1130 1130  
1131 1131  
1132 -1.
1047 +1.
1133 1133  11. How many RS485-Slave can RS485-BL connects?
1134 1134  
1135 1135  The RS485-BL can support max 32 RS485 devices. Each uplink command of RS485-BL can support max 16 different RS485 command. So RS485-BL can support max 16 RS485 devices pre-program in the device for uplink. For other devices no pre-program, user can use the [[downlink message (type code 0xA8) to poll their info>>path:#downlink_A8]].
... ... @@ -1146,7 +1146,7 @@
1146 1146  
1147 1147  
1148 1148  
1149 -1.
1064 +1.
1150 1150  11. Why I can’t join TTN V3 in US915 /AU915 bands?
1151 1151  
1152 1152  It might about the channels mapping. Please see for detail.
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
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