Last modified by Karry Zhuang on 2025/03/06 16:34
<
From version < 30.1 >
edited by Xiaoling
on 2022/05/23 09:38
To version < 18.1 >
edited by Xiaoling
on 2022/05/23 08:48
>
Change comment: Uploaded new attachment "1653266934636-343.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -1,11 +1,12 @@
1 1  (% style="text-align:center" %)
2 -[[image:1653266934636-343.png||height="385" width="385"]]
2 +[[image:1652947681187-144.png||height="385" width="385"]]
3 3  
4 4  
5 5  
6 -**RS485-LN – RS485 to LoRaWAN Converter User Manual**
7 7  
7 +**RS485-BL – Waterproof RS485 to LoRaWAN Converter User Manual**
8 8  
9 +
9 9  **Table of Contents:**
10 10  
11 11  
... ... @@ -14,28 +14,42 @@
14 14  
15 15  = 1.Introduction =
16 16  
17 -== 1.1 What is RS485-LN RS485 to LoRaWAN Converter ==
18 +== 1.1 What is RS485-BL RS485 to LoRaWAN Converter ==
18 18  
19 19  (((
21 +
22 +)))
23 +
20 20  (((
21 -The Dragino RS485-LN is a RS485 to LoRaWAN Converter. It converts the RS485 signal into LoRaWAN wireless signal which simplify the IoT installation and reduce the installation/maintaining cost.
25 +The Dragino RS485-BL is a **RS485 / UART to LoRaWAN Converter** for Internet of Things solutions. User can connect RS485 or UART sensor to RS485-BL converter, and configure RS485-BL to periodically read sensor data and upload via LoRaWAN network to IoT server.
22 22  )))
23 23  
24 24  (((
25 -RS485-LN allows user to monitor / control RS485 devices and reach extremely long ranges. It provides ultra-long range spread spectrum communication and high interference immunity whilst minimizing current consumption. It targets professional wireless sensor network applications such as irrigation systems, smart metering, smart cities, smartphone detection, building automation, and so on.
29 +RS485-BL can interface to RS485 sensor, 3.3v/5v UART sensor or interrupt sensor. RS485-BL provides **a 3.3v output** and** a 5v output** to power external sensors. Both output voltages are controllable to minimize the total system power consumption.
26 26  )))
27 27  
28 28  (((
29 -For data uplink, RS485-LN sends user-defined commands to RS485 devices and gets the return from the RS485 devices. RS485-LN will process these returns according to user-define rules to get the final payload and upload to LoRaWAN server.
33 +RS485-BL is IP67 **waterproof** and powered by **8500mAh Li-SOCI2 battery**, it is designed for long term use for several years.
30 30  )))
31 31  
32 32  (((
33 -For data downlink, RS485-LN runs in LoRaWAN Class C. When there downlink commands from LoRaWAN server, RS485-LN will forward the commands from LoRaWAN server to RS485 devices.
37 +RS485-BL runs standard **LoRaWAN 1.0.3 in Class A**. It can reach long transfer range and easy to integrate with LoRaWAN compatible gateway and IoT server.
34 34  )))
39 +
40 +(((
41 +For data uplink, RS485-BL sends user-defined commands to RS485 devices and gets the return from the RS485 devices. RS485-BL will process these returns data according to user-define rules to get the final payload and upload to LoRaWAN server.
35 35  )))
36 36  
37 -[[image:1653267211009-519.png||height="419" width="724"]]
44 +(((
45 +For data downlink, RS485-BL runs in LoRaWAN Class A. When there is downlink commands from LoRaWAN server, RS485-BL will forward the commands from LoRaWAN server to RS485 devices.
46 +)))
38 38  
48 +(((
49 +Each RS485-BL pre-load with a set of unique keys for LoRaWAN registration, register these keys to LoRaWAN server and it will auto connect after power on.
50 +)))
51 +
52 +[[image:1652953304999-717.png||height="424" width="733"]]
53 +
39 39  == 1.2 Specifications ==
40 40  
41 41  **Hardware System:**
... ... @@ -43,15 +43,19 @@
43 43  * STM32L072CZT6 MCU
44 44  * SX1276/78 Wireless Chip 
45 45  * Power Consumption (exclude RS485 device):
46 -** Idle: 32mA@12v
61 +** Idle: 6uA@3.3v
47 47  
48 -*
49 -** 20dB Transmit: 65mA@12v
63 +*
64 +** 20dB Transmit: 130mA@3.3v
50 50  
51 51  **Interface for Model:**
52 52  
53 -* RS485
54 -* Power Input 7~~ 24V DC. 
68 +* 1 x RS485 Interface
69 +* 1 x TTL Serial , 3.3v or 5v.
70 +* 1 x I2C Interface, 3.3v or 5v.
71 +* 1 x one wire interface
72 +* 1 x Interrupt Interface
73 +* 1 x Controllable 5V output, max
55 55  
56 56  **LoRa Spec:**
57 57  
... ... @@ -60,30 +60,27 @@
60 60  ** Band 2 (LF): 410 ~~ 528 Mhz
61 61  * 168 dB maximum link budget.
62 62  * +20 dBm - 100 mW constant RF output vs.
63 -* +14 dBm high efficiency PA.
64 64  * Programmable bit rate up to 300 kbps.
65 65  * High sensitivity: down to -148 dBm.
66 66  * Bullet-proof front end: IIP3 = -12.5 dBm.
67 67  * Excellent blocking immunity.
68 -* Low RX current of 10.3 mA, 200 nA register retention.
69 69  * Fully integrated synthesizer with a resolution of 61 Hz.
70 -* FSK, GFSK, MSK, GMSK, LoRaTM and OOK modulation.
87 +* LoRa modulation.
71 71  * Built-in bit synchronizer for clock recovery.
72 72  * Preamble detection.
73 73  * 127 dB Dynamic Range RSSI.
74 -* Automatic RF Sense and CAD with ultra-fast AFC.
75 -* Packet engine up to 256 bytes with CRC.
91 +* Automatic RF Sense and CAD with ultra-fast AFC. ​​​
76 76  
77 77  == 1.3 Features ==
78 78  
79 -* LoRaWAN Class A & Class C protocol (default Class C)
95 +* LoRaWAN Class A & Class C protocol (default Class A)
80 80  * Frequency Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/IN865/RU864
81 81  * AT Commands to change parameters
82 -* Remote configure parameters via LoRa Downlink
98 +* Remote configure parameters via LoRaWAN Downlink
83 83  * Firmware upgradable via program port
84 84  * Support multiply RS485 devices by flexible rules
85 85  * Support Modbus protocol
86 -* Support Interrupt uplink (Since hardware version v1.2)
102 +* Support Interrupt uplink
87 87  
88 88  == 1.4 Applications ==
89 89  
... ... @@ -96,39 +96,53 @@
96 96  
97 97  == 1.5 Firmware Change log ==
98 98  
99 -[[RS485-LN Image files – Download link and Change log>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/]]
115 +[[RS485-BL Image files – Download link and Change log>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/RS485-BL/Firmware/||style="background-color: rgb(255, 255, 255);"]]
100 100  
101 101  == 1.6 Hardware Change log ==
102 102  
103 103  (((
120 +v1.4
121 +)))
122 +
104 104  (((
105 -v1.2: Add External Interrupt Pin.
124 +~1. Change Power IC to TPS22916
125 +)))
106 106  
107 -v1.0: Release
127 +
128 +(((
129 +v1.3
108 108  )))
131 +
132 +(((
133 +~1. Change JP3 from KF350-8P to KF350-11P, Add one extra interface for I2C and one extra interface for one-wire
109 109  )))
110 110  
111 -= 2. Power ON Device =
112 112  
113 113  (((
114 -The RS485-LN can be powered by 7 ~~ 24V DC power source. Connection as below
138 +v1.2
139 +)))
115 115  
116 -* Power Source VIN to RS485-LN VIN+
117 -* Power Source GND to RS485-LN VIN-
118 -
119 119  (((
120 -Once there is power, the RS485-LN will be on.
142 +Release version ​​​​​
121 121  )))
122 122  
123 -[[image:1653268091319-405.png]]
145 += 2. Pin mapping and Power ON Device =
146 +
147 +(((
148 +The RS485-BL is powered on by 8500mAh battery. To save battery life, RS485-BL is shipped with power off. User can put the jumper to power on RS485-BL.
124 124  )))
125 125  
151 +[[image:1652953055962-143.png||height="387" width="728"]]
152 +
153 +
154 +The Left TXD and RXD are TTL interface for external sensor. TTL level is controlled by 3.3/5v Jumper.
155 +
126 126  = 3. Operation Mode =
127 127  
128 128  == 3.1 How it works? ==
129 129  
130 130  (((
131 -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.
161 +The RS485-BL is configured as LoRaWAN OTAA Class A 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-BL. It will auto join the network via OTAA.
132 132  )))
133 133  
134 134  == 3.2 Example to join LoRaWAN network ==
... ... @@ -135,32 +135,27 @@
135 135  
136 136  Here shows an example for how to join the TTN V3 Network. Below is the network structure, we use [[LG308>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/140-lg308.html]] as LoRaWAN gateway here. 
137 137  
138 -[[image:1653268155545-638.png||height="334" width="724"]]
168 +[[image:1652953414711-647.png||height="337" width="723"]]
139 139  
140 140  (((
141 -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:
171 +The RS485-BL in this example connected to two RS485 devices for demonstration, user can connect to other RS485 devices via the same method.
172 +)))
142 142  
143 -485A+ and 485B- of the sensor are connected to RS485A and RA485B of RS485-LN respectively.
144 -
145 -[[image:1653268227651-549.png||height="592" width="720"]]
146 -
147 147  (((
148 -The LG308 is already set to connect to [[TTN V3 network >>path:eu1.cloud.thethings.network/]]. So what we need to now is only configure the TTN V3:
175 +The LG308 is already set to connect to [[TTN V3 network >>url:https://www.thethingsnetwork.org/]]. So what we need to now is only configure the TTN V3:
149 149  )))
150 150  
151 151  (((
152 -**Step 1**: Create a device in TTN V3 with the OTAA keys from RS485-LN.
179 +**Step 1**: Create a device in TTN V3 with the OTAA keys from RS485-BL.
153 153  )))
154 154  
155 155  (((
156 -Each RS485-LN is shipped with a sticker with unique device EUI:
183 +Each RS485-BL is shipped with a sticker with unique device EUI:
157 157  )))
158 -)))
159 159  
160 160  [[image:1652953462722-299.png]]
161 161  
162 162  (((
163 -(((
164 164  User can enter this key in their LoRaWAN Server portal. Below is TTN V3 screen shot:
165 165  )))
166 166  
... ... @@ -167,11 +167,13 @@
167 167  (((
168 168  Add APP EUI in the application.
169 169  )))
170 -)))
171 171  
196 +
197 +
198 +
172 172  [[image:image-20220519174512-1.png]]
173 173  
174 -[[image:image-20220519174512-2.png||height="323" width="720"]]
201 +[[image:image-20220519174512-2.png||height="328" width="731"]]
175 175  
176 176  [[image:image-20220519174512-3.png||height="556" width="724"]]
177 177  
... ... @@ -187,7 +187,7 @@
187 187  
188 188  
189 189  (((
190 -**Step 2**: Power on RS485-LN and it will auto join to the TTN V3 network. After join success, it will start to upload message to TTN V3 and user can see in the panel.
217 +**Step 2**: Power on RS485-BL and it will auto join to the TTN V3 network. After join success, it will start to upload message to TTN V3 and user can see in the panel.
191 191  )))
192 192  
193 193  [[image:1652953568895-172.png||height="232" width="724"]]
... ... @@ -195,19 +195,23 @@
195 195  == 3.3 Configure Commands to read data ==
196 196  
197 197  (((
198 -(((
199 -There are plenty of RS485 devices in the market and each device has different command to read the valid data. To support these devices in flexible, RS485-LN supports flexible command set. User can use [[AT Commands>>path:#AT_COMMAND]] or LoRaWAN Downlink Command to configure what commands RS485-LN should send for each sampling and how to handle the return from RS485 devices.
225 +There are plenty of RS485 and TTL level devices in the market and each device has different command to read the valid data. To support these devices in flexible, RS485-BL supports flexible command set. User can use [[AT Commands or LoRaWAN Downlink>>path:#AT_COMMAND]] Command to configure how RS485-BL should read the sensor and how to handle the return from RS485 or TTL sensors.
200 200  )))
201 201  
202 -(((
203 -(% 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
204 -)))
205 -)))
206 -
207 207  === 3.3.1 onfigure UART settings for RS485 or TTL communication ===
208 208  
209 -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:
230 +RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect.
210 210  
232 +**~1. RS485-MODBUS mode:**
233 +
234 +AT+MOD=1 ~/~/ Support RS485-MODBUS type sensors. User can connect multiply RS485 , Modbus sensors to the A / B pins.
235 +
236 +**2. TTL mode:**
237 +
238 +AT+MOD=2 ~/~/ Support TTL Level sensors, User can connect one TTL Sensor to the TXD/RXD/GND pins.
239 +
240 +RS485-BL default UART settings is **9600, no parity, stop bit 1**. If the sensor has a different settings, user can change the RS485-BL setting to match.
241 +
211 211  (% border="1" style="background-color:#ffffcc; color:green; width:795px" %)
212 212  |(((
213 213  **AT Commands**
... ... @@ -232,7 +232,13 @@
232 232  |(((
233 233  AT+PARITY
234 234  )))|(% style="width:285px" %)(((
266 +(((
235 235  Set UART parity (for RS485 connection)
268 +)))
269 +
270 +(((
271 +Default Value is: no parity.
272 +)))
236 236  )))|(% style="width:347px" %)(((
237 237  (((
238 238  AT+PARITY=0
... ... @@ -250,7 +250,7 @@
250 250  )))
251 251  
252 252  (((
253 -
290 +Default Value is: 1bit.
254 254  )))
255 255  )))|(% style="width:347px" %)(((
256 256  (((
... ... @@ -269,10 +269,12 @@
269 269  === 3.3.2 Configure sensors ===
270 270  
271 271  (((
309 +Some sensors might need to configure before normal operation. User can configure such sensor via PC or through RS485-BL AT Commands (% style="color:#4f81bd" %)**AT+CFGDEV**.
310 +)))
311 +
272 272  (((
273 -Some sensors might need to configure before normal operation. User can configure such sensor via PC and RS485 adapter or through RS485-LN AT Commands (% style="color:#4f81bd" %)**AT+CFGDEV**(%%). Each (% style="color:#4f81bd" %)**AT+CFGDEV **(%%)equals to send a RS485 command to sensors. This command will only run when user input it and won’t run during each sampling.
313 +When user issue an (% style="color:#4f81bd" %)**AT+CFGDEV**(%%) command, Each (% style="color:#4f81bd" %)**AT+CFGDEV**(%%) equals to send a command to the RS485 or TTL sensors. This command will only run when user input it and won’t run during each sampling.
274 274  )))
275 -)))
276 276  
277 277  (% border="1" style="background-color:#ffffcc; color:green; width:806px" %)
278 278  |**AT Commands**|(% style="width:418px" %)**Description**|(% style="width:256px" %)**Example**
... ... @@ -284,6 +284,8 @@
284 284  mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
285 285  )))|(% style="width:256px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
286 286  
326 +Detail of AT+CFGDEV command see [[AT+CFGDEV detail>>path:#AT_CFGDEV]].
327 +
287 287  === 3.3.3 Configure read commands for each sampling ===
288 288  
289 289  (((
... ... @@ -365,17 +365,11 @@
365 365  **m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command**
366 366  )))
367 367  
368 -(((
369 369  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.
370 -)))
371 371  
372 -(((
373 373  In the RS485-BL, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
374 -)))
375 375  
376 -(((
377 377  **AT+SEARCHx**: This command defines how to handle the return from AT+COMMANDx.
378 -)))
379 379  
380 380  (% border="1" class="table-bordered" %)
381 381  |(((
... ... @@ -387,24 +387,26 @@
387 387  
388 388  )))
389 389  
390 -**Examples:**
425 +Examples:
391 391  
392 -~1. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
427 +1. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
393 393  
394 394  If we set AT+SEARCH1=1,1E 56 34.      (max 5 bytes for prefix)
395 395  
396 -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**
431 +The valid data will be all bytes after 1E 56 34 , so it is 2e 30 58 5f 36 41 30 31 00 49
397 397  
398 -[[image:1653269403619-508.png]]
433 +[[image:1652954654347-831.png]]
399 399  
400 -2. For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
401 401  
436 +1. For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
437 +
402 402  If we set AT+SEARCH1=2, 1E 56 34+31 00 49
403 403  
404 -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**
440 +Device will search the bytes between 1E 56 34 and 31 00 49. So it is 2e 30 58 5f 36 41 30
405 405  
406 -[[image:1653269438444-278.png]]
442 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image014.png]]
407 407  
444 +
408 408  **AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes.
409 409  
410 410  |(((
... ... @@ -419,63 +419,58 @@
419 419  
420 420  * Grab bytes:
421 421  
422 -[[image:1653269551753-223.png||height="311" width="717"]]
459 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image015.png]]
423 423  
424 424  * Grab a section.
425 425  
426 -[[image:1653269568276-930.png||height="325" width="718"]]
463 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image016.png]]
427 427  
428 428  * Grab different sections.
429 429  
430 -[[image:1653269593172-426.png||height="303" width="725"]]
467 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image017.png]]
431 431  
432 -(% style="color:red" %)**Note:**
433 433  
470 +Note:
471 +
434 434  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.
435 435  
436 436  Example:
437 437  
438 -(% style="color:red" %)AT+COMMAND1=11 01 1E D0,0
476 +AT+COMMAND1=11 01 1E D0,0
439 439  
440 -(% style="color:red" %)AT+SEARCH1=1,1E 56 34
478 +AT+SEARCH1=1,1E 56 34
441 441  
442 -(% style="color:red" %)AT+DATACUT1=0,2,1~~5
480 +AT+DATACUT1=0,2,1~~5
443 443  
444 -(% style="color:red" %)Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
482 +Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
445 445  
446 -(% style="color:red" %)String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
484 +String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
447 447  
448 -(% style="color:red" %)Valid payload after DataCUT command: 2e 30 58 5f 36
486 +Valid payload after DataCUT command: 2e 30 58 5f 36
449 449  
450 -[[image:1653269618463-608.png]]
488 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image018.png]]
451 451  
452 -=== 3.3.4 Compose the uplink payload ===
453 453  
454 -(((
491 +
492 +
493 +1.
494 +11.
495 +111. Compose the uplink payload
496 +
455 455  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.**
456 -)))
457 457  
458 -(((
459 -(% style="color:#4f81bd" %)**Examples: AT+DATAUP=0**
460 -)))
461 461  
462 -(((
463 -Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**A SIGNLE UPLINK**.
464 -)))
500 +**Examples: AT+DATAUP=0**
465 465  
466 -(((
502 +Compose the uplink payload with value returns in sequence and send with **A SIGNLE UPLINK**.
503 +
467 467  Final Payload is
468 -)))
469 469  
470 -(((
471 -(% style="color:#4f81bd" %)**Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx**
472 -)))
506 +Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx
473 473  
474 -(((
475 475  Where PAYVER is defined by AT+PAYVER, below is an example screen shot.
476 -)))
477 477  
478 -[[image:1653269759169-150.png||height="513" width="716"]]
510 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.png]]
479 479  
480 480  
481 481  
... ... @@ -523,8 +523,8 @@
523 523  
524 524  
525 525  
526 -1.
527 -11.
558 +1.
559 +11.
528 528  111. Uplink on demand
529 529  
530 530  Except uplink periodically, RS485-BL is able to uplink on demand. The server sends downlink command to RS485-BL and RS485 will uplink data base on the command.
... ... @@ -537,8 +537,8 @@
537 537  
538 538  
539 539  
540 -1.
541 -11.
572 +1.
573 +11.
542 542  111. Uplink on Interrupt
543 543  
544 544  Put the interrupt sensor between 3.3v_out and GPIO ext.[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image022.png]]
... ... @@ -552,7 +552,7 @@
552 552  AT+INTMOD=3  Interrupt trigger by rising edge.
553 553  
554 554  
555 -1.
587 +1.
556 556  11. Uplink Payload
557 557  
558 558  |**Size(bytes)**|**2**|**1**|**Length depends on the return from the commands**
... ... @@ -614,15 +614,15 @@
614 614  
615 615  * **Sensor Related Commands**: These commands are special designed for RS485-BL.  User can see these commands below:
616 616  
617 -1.
618 -11.
649 +1.
650 +11.
619 619  111. Common Commands:
620 620  
621 621  They should be available for each of Dragino Sensors, such as: change uplink interval, reset device. For firmware v1.3, user can find what common commands it supports: [[http:~~/~~/wiki.dragino.com/index.php?title=End_Device_AT_Commands_and_Downlink_Commands>>url:http://wiki.dragino.com/index.php?title=End_Device_AT_Commands_and_Downlink_Commands]]
622 622  
623 623  
624 -1.
625 -11.
656 +1.
657 +11.
626 626  111. Sensor related commands:
627 627  
628 628  ==== Choose Device Type (RS485 or TTL) ====
... ... @@ -928,13 +928,13 @@
928 928  
929 929  
930 930  
931 -1.
963 +1.
932 932  11. Buttons
933 933  
934 934  |**Button**|**Feature**
935 935  |**RST**|Reboot RS485-BL
936 936  
937 -1.
969 +1.
938 938  11. +3V3 Output
939 939  
940 940  RS485-BL has a Controllable +3V3 output, user can use this output to power external sensor.
... ... @@ -952,7 +952,7 @@
952 952  By default, the AT+3V3T=0. This is a special case, means the +3V3 output is always on at any time
953 953  
954 954  
955 -1.
987 +1.
956 956  11. +5V Output
957 957  
958 958  RS485-BL has a Controllable +5V output, user can use this output to power external sensor.
... ... @@ -972,13 +972,13 @@
972 972  
973 973  
974 974  
975 -1.
1007 +1.
976 976  11. LEDs
977 977  
978 978  |**LEDs**|**Feature**
979 979  |**LED1**|Blink when device transmit a packet.
980 980  
981 -1.
1013 +1.
982 982  11. Switch Jumper
983 983  
984 984  |**Switch Jumper**|**Feature**
... ... @@ -1024,7 +1024,7 @@
1024 1024  
1025 1025  
1026 1026  
1027 -1.
1059 +1.
1028 1028  11. Common AT Command Sequence
1029 1029  111. Multi-channel ABP mode (Use with SX1301/LG308)
1030 1030  
... ... @@ -1043,8 +1043,8 @@
1043 1043  
1044 1044  ATZ
1045 1045  
1046 -1.
1047 -11.
1078 +1.
1079 +11.
1048 1048  111. Single-channel ABP mode (Use with LG01/LG02)
1049 1049  
1050 1050  AT+FDR   Reset Parameters to Factory Default, Keys Reserve
... ... @@ -1119,7 +1119,7 @@
1119 1119  [[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]]
1120 1120  
1121 1121  
1122 -1.
1154 +1.
1123 1123  11. How to change the LoRa Frequency Bands/Region?
1124 1124  
1125 1125  User can follow the introduction for [[how to upgrade image>>path:#upgrade_image]]. When download the images, choose the required image file for download.
... ... @@ -1126,7 +1126,7 @@
1126 1126  
1127 1127  
1128 1128  
1129 -1.
1161 +1.
1130 1130  11. How many RS485-Slave can RS485-BL connects?
1131 1131  
1132 1132  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]].
... ... @@ -1143,7 +1143,7 @@
1143 1143  
1144 1144  
1145 1145  
1146 -1.
1178 +1.
1147 1147  11. Why I can’t join TTN V3 in US915 /AU915 bands?
1148 1148  
1149 1149  It might about the channels mapping. Please see for detail.
1653267211009-519.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -138.7 KB
Content
1653268091319-405.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -399.3 KB
Content
1653268155545-638.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -113.7 KB
Content
1653268227651-549.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -1.3 MB
Content
1653269403619-508.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -27.8 KB
Content
1653269438444-278.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -26.6 KB
Content
1653269551753-223.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -138.7 KB
Content
1653269568276-930.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -131.4 KB
Content
1653269593172-426.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -142.6 KB
Content
1653269618463-608.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -27.7 KB
Content
1653269759169-150.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -294.0 KB
Content
1653269916228-732.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -143.3 KB
Content

Applications

Navigation

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