Skip to Content
Last modified by Mengting Qiu on 2025/07/14 09:59
From version 20.2
edited by Xiaoling
on 2022/05/23 09:08
Change comment: There is no comment for this version
To version 41.4
edited by Xiaoling
on 2022/06/02 16:36
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -18,40 +18,42 @@
18 18  
19 19  (((
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.
21 +The Dragino RS485-LN is a (% style="color:blue" %)**RS485 to LoRaWAN Converter**(%%). It converts the RS485 signal into LoRaWAN wireless signal which simplify the IoT installation and reduce the installation/maintaining cost.
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.
25 +RS485-LN allows user to (% style="color:blue" %)**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.
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.
29 +(% style="color:blue" %)**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.
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.
33 +(% style="color:blue" %)**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.
34 +
35 +(% style="color:blue" %)**Demo Dashboard for RS485-LN**(%%) connect to two energy meters: [[https:~~/~~/app.datacake.de/dashboard/d/58844a26-378d-4c5a-aaf5-b5b5b153447a>>url:https://app.datacake.de/dashboard/d/58844a26-378d-4c5a-aaf5-b5b5b153447a]]
34 34  )))
35 35  )))
36 36  
37 37  [[image:1653267211009-519.png||height="419" width="724"]]
38 38  
41 +
39 39  == 1.2 Specifications ==
40 40  
44 +
41 41  **Hardware System:**
42 42  
43 43  * STM32L072CZT6 MCU
44 -* SX1276/78 Wireless Chip
48 +* SX1276/78 Wireless Chip 
45 45  * Power Consumption (exclude RS485 device):
46 46  ** Idle: 32mA@12v
47 -
48 -*
49 49  ** 20dB Transmit: 65mA@12v
50 50  
51 51  **Interface for Model:**
52 52  
53 53  * RS485
54 -* Power Input 7~~ 24V DC.
56 +* Power Input 7~~ 24V DC. 
55 55  
56 56  **LoRa Spec:**
57 57  
... ... @@ -74,6 +74,7 @@
74 74  * Automatic RF Sense and CAD with ultra-fast AFC.
75 75  * Packet engine up to 256 bytes with CRC.
76 76  
79 +
77 77  == 1.3 Features ==
78 78  
79 79  * LoRaWAN Class A & Class C protocol (default Class C)
... ... @@ -85,6 +85,7 @@
85 85  * Support Modbus protocol
86 86  * Support Interrupt uplink (Since hardware version v1.2)
87 87  
91 +
88 88  == 1.4 Applications ==
89 89  
90 90  * Smart Buildings & Home Automation
... ... @@ -94,10 +94,12 @@
94 94  * Smart Cities
95 95  * Smart Factory
96 96  
101 +
97 97  == 1.5 Firmware Change log ==
98 98  
99 99  [[RS485-LN Image files – Download link and Change log>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/]]
100 100  
106 +
101 101  == 1.6 Hardware Change log ==
102 102  
103 103  (((
... ... @@ -105,6 +105,8 @@
105 105  v1.2: Add External Interrupt Pin.
106 106  
107 107  v1.0: Release
114 +
115 +
108 108  )))
109 109  )))
110 110  
... ... @@ -116,9 +116,13 @@
116 116  * Power Source VIN to RS485-LN VIN+
117 117  * Power Source GND to RS485-LN VIN-
118 118  
127 +(((
119 119  Once there is power, the RS485-LN will be on.
129 +)))
120 120  
121 121  [[image:1653268091319-405.png]]
132 +
133 +
122 122  )))
123 123  
124 124  = 3. Operation Mode =
... ... @@ -126,7 +126,9 @@
126 126  == 3.1 How it works? ==
127 127  
128 128  (((
129 -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.
141 +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.
142 +
143 +
130 130  )))
131 131  
132 132  == 3.2 Example to join LoRaWAN network ==
... ... @@ -133,27 +133,37 @@
133 133  
134 134  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. 
135 135  
136 -[[image:1652953414711-647.png||height="337" width="723"]]
150 +[[image:1653268155545-638.png||height="334" width="724"]]
137 137  
152 +
138 138  (((
139 -The RS485-BL in this example connected to two RS485 devices for demonstration, user can connect to other RS485 devices via the same method.
154 +(((
155 +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:
140 140  )))
141 141  
142 142  (((
143 -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:
159 +485A+ and 485B- of the sensor are connected to RS485A and RA485B of RS485-LN respectively.
144 144  )))
145 145  
162 +[[image:1653268227651-549.png||height="592" width="720"]]
163 +
146 146  (((
147 -**Step 1**: Create a device in TTN V3 with the OTAA keys from RS485-BL.
165 +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:
148 148  )))
149 149  
150 150  (((
151 -Each RS485-BL is shipped with a sticker with unique device EUI:
169 +**Step 1**: Create a device in TTN V3 with the OTAA keys from RS485-LN.
152 152  )))
153 153  
172 +(((
173 +Each RS485-LN is shipped with a sticker with unique device EUI:
174 +)))
175 +)))
176 +
154 154  [[image:1652953462722-299.png]]
155 155  
156 156  (((
180 +(((
157 157  User can enter this key in their LoRaWAN Server portal. Below is TTN V3 screen shot:
158 158  )))
159 159  
... ... @@ -160,13 +160,11 @@
160 160  (((
161 161  Add APP EUI in the application.
162 162  )))
187 +)))
163 163  
164 -
165 -
166 -
167 167  [[image:image-20220519174512-1.png]]
168 168  
169 -[[image:image-20220519174512-2.png||height="328" width="731"]]
191 +[[image:image-20220519174512-2.png||height="323" width="720"]]
170 170  
171 171  [[image:image-20220519174512-3.png||height="556" width="724"]]
172 172  
... ... @@ -182,44 +182,43 @@
182 182  
183 183  
184 184  (((
185 -**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.
207 +**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.
186 186  )))
187 187  
188 188  [[image:1652953568895-172.png||height="232" width="724"]]
189 189  
212 +
190 190  == 3.3 Configure Commands to read data ==
191 191  
192 192  (((
193 -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.
216 +(((
217 +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.
194 194  )))
195 195  
196 -=== 3.3.1 onfigure UART settings for RS485 or TTL communication ===
220 +(((
221 +(% 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
197 197  
198 -RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect.
223 +
224 +)))
225 +)))
199 199  
200 -**~1. RS485-MODBUS mode:**
227 +=== 3.3.1 onfigure UART settings for RS485 or TTL communication ===
201 201  
202 -AT+MOD=1 ~/~/ Support RS485-MODBUS type sensors. User can connect multiply RS485 , Modbus sensors to the A / B pins.
229 +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:
203 203  
204 -**2. TTL mode:**
205 -
206 -AT+MOD=2 ~/~/ Support TTL Level sensors, User can connect one TTL Sensor to the TXD/RXD/GND pins.
207 -
208 -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.
209 -
210 -(% border="1" style="background-color:#ffffcc; color:green; width:795px" %)
211 -|(((
231 +(% border="1" style="background-color:#ffffcc; color:green; width:782px" %)
232 +|(% style="width:128px" %)(((
212 212  **AT Commands**
213 -)))|(% style="width:285px" %)(((
234 +)))|(% style="width:305px" %)(((
214 214  **Description**
215 -)))|(% style="width:347px" %)(((
236 +)))|(% style="width:346px" %)(((
216 216  **Example**
217 217  )))
218 -|(((
239 +|(% style="width:128px" %)(((
219 219  AT+BAUDR
220 -)))|(% style="width:285px" %)(((
241 +)))|(% style="width:305px" %)(((
221 221  Set the baud rate (for RS485 connection). Default Value is: 9600.
222 -)))|(% style="width:347px" %)(((
243 +)))|(% style="width:346px" %)(((
223 223  (((
224 224  AT+BAUDR=9600
225 225  )))
... ... @@ -228,18 +228,12 @@
228 228  Options: (1200,2400,4800,14400,19200,115200)
229 229  )))
230 230  )))
231 -|(((
252 +|(% style="width:128px" %)(((
232 232  AT+PARITY
233 -)))|(% style="width:285px" %)(((
234 -(((
254 +)))|(% style="width:305px" %)(((
235 235  Set UART parity (for RS485 connection)
236 -)))
237 -
256 +)))|(% style="width:346px" %)(((
238 238  (((
239 -Default Value is: no parity.
240 -)))
241 -)))|(% style="width:347px" %)(((
242 -(((
243 243  AT+PARITY=0
244 244  )))
245 245  
... ... @@ -247,17 +247,17 @@
247 247  Option: 0: no parity, 1: odd parity, 2: even parity
248 248  )))
249 249  )))
250 -|(((
265 +|(% style="width:128px" %)(((
251 251  AT+STOPBIT
252 -)))|(% style="width:285px" %)(((
267 +)))|(% style="width:305px" %)(((
253 253  (((
254 254  Set serial stopbit (for RS485 connection)
255 255  )))
256 256  
257 257  (((
258 -Default Value is: 1bit.
273 +
259 259  )))
260 -)))|(% style="width:347px" %)(((
275 +)))|(% style="width:346px" %)(((
261 261  (((
262 262  AT+STOPBIT=0 for 1bit
263 263  )))
... ... @@ -274,12 +274,10 @@
274 274  === 3.3.2 Configure sensors ===
275 275  
276 276  (((
277 -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**.
278 -)))
279 -
280 280  (((
281 -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.
293 +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.
282 282  )))
295 +)))
283 283  
284 284  (% border="1" style="background-color:#ffffcc; color:green; width:806px" %)
285 285  |**AT Commands**|(% style="width:418px" %)**Description**|(% style="width:256px" %)**Example**
... ... @@ -291,82 +291,37 @@
291 291  mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
292 292  )))|(% style="width:256px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
293 293  
294 -Detail of AT+CFGDEV command see [[AT+CFGDEV detail>>path:#AT_CFGDEV]].
295 -
296 296  === 3.3.3 Configure read commands for each sampling ===
297 297  
298 298  (((
299 -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.
300 -)))
310 +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.
301 301  
302 -(((
303 -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.
304 -)))
305 -
306 -(((
307 307  To save the LoRaWAN network bandwidth, we might need to read data from different sensors and combine their valid value into a short payload.
308 -)))
309 309  
310 -(((
311 311  This section describes how to achieve above goals.
312 -)))
313 313  
314 -(((
315 -During each sampling, the RS485-BL can support 15 commands to read sensors. And combine the return to one or several uplink payloads.
316 -)))
316 +During each sampling, the RS485-LN can support 15 commands to read sensors. And combine the return to one or several uplink payloads.
317 317  
318 -(((
319 -**Command from RS485-BL to Sensor:**
320 -)))
321 321  
322 -(((
323 -RS485-BL can send out pre-set max 15 strings via **AT+COMMAD1**, **ATCOMMAND2**,…, to **AT+COMMANDF** . All commands are of same grammar.
324 -)))
319 +**Each RS485 commands include two parts:**
325 325  
326 -(((
327 -**Handle return from sensors to RS485-BL**:
328 -)))
321 +~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.
329 329  
330 -(((
331 -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**
332 -)))
323 +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.
333 333  
334 -* (((
335 -**AT+DATACUT**
336 -)))
325 +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
337 337  
338 -(((
339 -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.
340 -)))
341 341  
342 -* (((
343 -**AT+SEARCH**
344 -)))
345 -
346 -(((
347 -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.
348 -)))
349 -
350 -(((
351 -**Define wait timeout:**
352 -)))
353 -
354 -(((
355 -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
356 -)))
357 -
358 -(((
359 359  After we got the valid value from each RS485 commands, we need to combine them together with the command **AT+DATAUP**.
360 -)))
361 361  
362 -**Examples:**
363 363  
364 364  Below are examples for the how above AT Commands works.
365 365  
366 -**AT+COMMANDx : **This command will be sent to RS485/TTL devices during each sampling, Max command length is 14 bytes. The grammar is:
367 367  
368 -(% border="1" class="table-bordered" %)
369 -|(((
334 +**AT+COMMANDx : **This command will be sent to RS485 devices during each sampling, Max command length is 14 bytes. The grammar is:
335 +
336 +(% border="1" style="background-color:#4bacc6; color:white; width:499px" %)
337 +|(% style="width:496px" %)(((
370 370  **AT+COMMANDx=xx xx xx xx xx xx xx xx xx xx xx xx,m**
371 371  
372 372  **xx xx xx xx xx xx xx xx xx xx xx xx: The RS485 command to be sent**
... ... @@ -376,43 +376,13 @@
376 376  
377 377  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.
378 378  
379 -In the RS485-BL, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
347 +In the RS485-LN, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
380 380  
381 -**AT+SEARCHx**: This command defines how to handle the return from AT+COMMANDx.
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 2e 30 58 5f 36 41 30 31 00 49
400 -
401 -[[image:1652954654347-831.png]]
402 -
403 -
404 -1. For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
405 -
406 -If we set AT+SEARCH1=2, 1E 56 34+31 00 49
407 -
408 -Device will search the bytes between 1E 56 34 and 31 00 49. So it is 2e 30 58 5f 36 41 30
409 -
410 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image014.png]]
411 -
412 -
413 413  **AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes.
414 414  
415 -|(((
352 +(% border="1" style="background-color:#4bacc6; color:white; width:725px" %)
353 +|(% style="width:722px" %)(((
416 416  **AT+DATACUTx=a,b,c**
417 417  
418 418  * **a: length for the return of AT+COMMAND**
... ... @@ -420,773 +420,166 @@
420 420  * **c: define the position for valid value.  **
421 421  )))
422 422  
423 -Examples:
361 +**Examples:**
424 424  
425 425  * Grab bytes:
426 426  
427 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image015.png]]
365 +[[image:image-20220602153621-1.png]]
428 428  
367 +
429 429  * Grab a section.
430 430  
431 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image016.png]]
370 +[[image:image-20220602153621-2.png]]
432 432  
372 +
433 433  * Grab different sections.
434 434  
435 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image017.png]]
375 +[[image:image-20220602153621-3.png]]
436 436  
377 +
378 +)))
437 437  
438 -Note:
380 +=== 3.3.4 Compose the uplink payload ===
439 439  
440 -AT+SEARCHx and AT+DATACUTx can be used together, if both commands are set, RS485-BL will first process AT+SEARCHx on the return string and get a temporary string, and then process AT+DATACUTx on this temporary string to get the final payload. In this case, AT+DATACUTx need to set to format AT+DATACUTx=0,xx,xx where the return bytes set to 0.
441 -
442 -Example:
443 -
444 -AT+COMMAND1=11 01 1E D0,0
445 -
446 -AT+SEARCH1=1,1E 56 34
447 -
448 -AT+DATACUT1=0,2,1~~5
449 -
450 -Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
451 -
452 -String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
453 -
454 -Valid payload after DataCUT command: 2e 30 58 5f 36
455 -
456 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image018.png]]
457 -
458 -
459 -
460 -
461 -1.
462 -11.
463 -111. Compose the uplink payload
464 -
382 +(((
465 465  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.**
466 466  
385 +
386 +)))
467 467  
468 -**Examples: AT+DATAUP=0**
388 +(((
389 +(% style="color:#037691" %)**Examples: AT+DATAUP=0**
469 469  
470 -Compose the uplink payload with value returns in sequence and send with **A SIGNLE UPLINK**.
391 +
392 +)))
471 471  
394 +(((
395 +Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**A SIGNLE UPLINK**.
396 +)))
397 +
398 +(((
472 472  Final Payload is
400 +)))
473 473  
474 -Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx
402 +(((
403 +(% style="color:#4f81bd" %)**Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx**
404 +)))
475 475  
406 +(((
476 476  Where PAYVER is defined by AT+PAYVER, below is an example screen shot.
408 +)))
477 477  
478 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.png]]
410 +[[image:1653269759169-150.png||height="513" width="716"]]
479 479  
480 480  
413 +(% style="color:#037691" %)**Examples: AT+DATAUP=1**
481 481  
482 -**Examples: AT+DATAUP=1**
483 483  
484 -Compose the uplink payload with value returns in sequence and send with **Multiply UPLINKs**.
416 +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 487  
488 -Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA
420 +(% 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*!>>path:#max_byte]]) for each uplink so each uplink <= 11 bytes. For the last uplink, DATA will might less than 6 bytes
422 +1. PAYVER: Defined by AT+PAYVER
423 +1. PAYLOAD COUNT: Total how many uplinks of this sampling.
424 +1. PAYLOAD#: Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
425 +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:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image020.png]]
427 +[[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
430 +So totally there will be 3 uplinks for this sampling, each uplink include 8 bytes DATA
500 500  
501 -DATA1=RETURN1 Valid Value = 20 20 0a 33 90 41
432 +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= 02 aa 05 81 0a 20
434 +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 = 20 20 20 2d 30
436 +DATA3=the rest of Valid value of RETURN10= **30**
506 506  
507 507  
439 +(% 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:
508 508  
509 -Below are the uplink payloads:
441 + ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink.
510 510  
511 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.png]]
443 + * For AU915/AS923 bands, if UplinkDwell time=0, max 11 bytes for each uplink.
512 512  
445 + * For US915 band, max 11 bytes for each uplink.
513 513  
514 -Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:
447 + ~* For all other bands: max 51 bytes for each uplink.
515 515  
516 - ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink ( so 51 -5 = 46 max valid date)
517 517  
518 - * For AU915/AS923 bands, if UplinkDwell time=1, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date).
450 +Below are the uplink payloads:
519 519  
520 - * For US915 band, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date).
452 +[[image:1654157178836-407.png]]
521 521  
522 - ~* For all other bands: max 51 bytes for each uplink  ( so 51 -5 = 46 max valid date).
523 523  
455 +=== 3.3.5 Uplink on demand ===
524 524  
457 +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 -1.
527 -11.
528 -111. Uplink on demand
529 -
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.
531 -
532 532  Downlink control command:
533 533  
534 -[[0x08 command>>path:#downlink_08]]: Poll an uplink with current command set in RS485-BL.
461 +**0x08 command**: Poll an uplink with current command set in RS485-LN.
535 535  
536 -[[0xA8 command>>path:#downlink_A8]]: Send a command to RS485-BL and uplink the output from sensors.
463 +**0xA8 command**: Send a command to RS485-LN and uplink the output from sensors.
537 537  
538 538  
539 539  
540 -1.
541 -11.
542 -111. Uplink on Interrupt
467 +=== 3.3.6 Uplink on Interrupt ===
543 543  
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]]
469 +RS485-LN support external Interrupt uplink since hardware v1.2 release.
545 545  
546 -AT+INTMOD=0  Disable Interrupt
471 +[[image:1654157342174-798.png]]
547 547  
548 -AT+INTMOD=1  Interrupt trigger by rising or falling edge.
473 +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.
549 549  
550 -AT+INTMOD=2  Interrupt trigger by falling edge. ( Default Value)
551 551  
552 -AT+INTMOD=3  Interrupt trigger by rising edge.
476 +== 3.4 Uplink Payload ==
553 553  
554 -
555 -1.
556 -11. Uplink Payload
557 -
558 -|**Size(bytes)**|**2**|**1**|**Length depends on the return from the commands**
559 -|Value|(((
478 +(% border="1" style="background-color:#4bacc6; color:white; width:734px" %)
479 +|**Size(bytes)**|(% style="width:120px" %)**2**|(% style="width:116px" %)**1**|(% style="width:386px" %)**Length depends on the return from the commands**
480 +|Value|(% style="width:120px" %)(((
560 560  Battery(mV)
561 561  
562 562  &
563 563  
564 564  Interrupt _Flag
565 -)))|(((
486 +)))|(% style="width:116px" %)(((
566 566  PAYLOAD_VER
567 567  
568 568  
569 -)))|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.
490 +)))|(% 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.
570 570  
571 571  Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors.
572 572  
573 573  
574 -function Decoder(bytes, port) {
495 +== 3.5 Configure RS485-BL via AT or Downlink ==
575 575  
576 -~/~/Payload Formats of RS485-BL Deceive
497 +User can configure RS485-LN via AT Commands or LoRaWAN Downlink Commands
577 577  
578 -return {
579 -
580 - ~/~/Battery,units:V
581 -
582 - BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000,
583 -
584 - ~/~/GPIO_EXTI 
585 -
586 - EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE",
587 -
588 - ~/~/payload of version
589 -
590 - Pay_ver:bytes[2],
591 -
592 - };
593 -
594 - }
595 -
596 -
597 -
598 -
599 -
600 -
601 -
602 -TTN V3 uplink screen shot.
603 -
604 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]
605 -
606 -1.
607 -11. Configure RS485-BL via AT or Downlink
608 -
609 -User can configure RS485-BL via [[AT Commands >>path:#_​Using_the_AT]]or LoRaWAN Downlink Commands
610 -
611 611  There are two kinds of Commands:
612 612  
613 -* **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
501 +* (% 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]]
614 614  
615 -* **Sensor Related Commands**: These commands are special designed for RS485-BL.  User can see these commands below:
503 +* (% style="color:#4f81bd" %)**Sensor Related Commands**(%%): These commands are special designed for RS485-LN.  User can see these commands below:
616 616  
617 -1.
618 -11.
619 -111. Common Commands:
505 +=== 3.5.1 Common Commands ===
620 620  
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]]
507 +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]]
622 622  
623 623  
624 -1.
625 -11.
626 -111. Sensor related commands:
510 +=== 3.5.2 Sensor related commands ===
627 627  
628 -==== Choose Device Type (RS485 or TTL) ====
512 +Response feature is added to the server's downlink, a special package with a FPort of 200 will be uploaded immediately after receiving the data sent by the server.
629 629  
630 -RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect.
514 +[[image:image-20220602163333-5.png||height="263" width="1160"]]
631 631  
632 -* AT Command
516 +The first byte of this package represents whether the configuration is successful, 00 represents failure, 01 represents success. Except for the first byte, the other is the previous downlink. (All commands except A8 type commands are applicable)
633 633  
634 -**AT+MOD=1** ~/~/ Set to support RS485-MODBUS type sensors. User can connect multiply RS485 , Modbus sensors to the A / B pins.
635 635  
636 -**AT+MOD=2** ~/~/ Set to support TTL Level sensors, User can connect one TTL Sensor to the TXD/RXD/GND pins.
519 +3.5.3 Sensor related commands
637 637  
521 +==== ====
638 638  
639 -* Downlink Payload
640 -
641 -**0A aa**     à same as AT+MOD=aa
642 -
643 -
644 -
645 -==== [[RS485 Debug Command>>path:#downlink_A8]] (AT+CFGDEV) ====
646 -
647 -This command is used to configure the RS485 or TTL sensors; they won’t be used during sampling.
648 -
649 -* AT Command
650 -
651 -AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
652 -
653 -m: 0: no CRC; 1: add CRC-16/MODBUS in the end of this command.
654 -
655 -
656 -
657 -* Downlink Payload
658 -
659 -Format: A8 MM NN XX XX XX XX YY
660 -
661 -Where:
662 -
663 -* MM: 1: add CRC-16/MODBUS ; 0: no CRC
664 -* NN: The length of RS485 command
665 -* XX XX XX XX: RS485 command total NN bytes
666 -* YY: How many bytes will be uplink from the return of this RS485 command, if YY=0, RS485-BL will execute the downlink command without uplink; if YY>0, RS485-BL will uplink total YY bytes from the output of this RS485 command
667 -
668 -**Example 1:**
669 -
670 -To connect a Modbus Alarm with below commands.
671 -
672 -* The command to active alarm is: 0A 05 00 04 00 01 4C B0. Where 0A 05 00 04 00 01 is the Modbus command to read the register 00 40 where stored the DI status. The 4C B0 is the CRC-16/MODBUS which calculate manually.
673 -
674 -* The command to deactivate alarm is: 0A 05 00 04 00 00 8D 70. Where 0A 05 00 04 00 00 is the Modbus command to read the register 00 40 where stored the DI status. The 8D 70 is the CRC-16/MODBUS which calculate manually.
675 -
676 -So if user want to use downlink command to control to RS485 Alarm, he can use:
677 -
678 -**A8 01 06 0A 05 00 04 00 01 00**: to activate the RS485 Alarm
679 -
680 -**A8 01 06 0A 05 00 04 00 00 00**: to deactivate the RS485 Alarm
681 -
682 -A8 is type code and 01 means add CRC-16/MODBUS at the end, the 3^^rd^^ byte is 06, means the next 6 bytes are the command to be sent to the RS485 network, the final byte 00 means this command don’t need to acquire output.
683 -
684 -
685 -**Example 2:**
686 -
687 -Check TTL Sensor return:
688 -
689 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image024.png]]
690 -
691 -
692 -
693 -
694 -==== Set Payload version ====
695 -
696 -This is the first byte of the uplink payload. RS485-BL can connect to different sensors. User can set the PAYVER field to tell server how to decode the current payload.
697 -
698 -* AT Command:
699 -
700 -AT+PAYVER: Set PAYVER field = 1
701 -
702 -
703 -* Downlink Payload:
704 -
705 -0xAE 01   à Set PAYVER field =  0x01
706 -
707 -0xAE 0F   à Set PAYVER field =  0x0F
708 -
709 -
710 -==== Set RS485 Sampling Commands ====
711 -
712 -AT+COMMANDx, AT+DATACUTx and AT+SEARCHx
713 -
714 -These three commands are used to configure how the RS485-BL polling data from Modbus device. Detail of usage please see : [[polling RS485 device>>path:#polling_485]].
715 -
716 -
717 -* AT Command:
718 -
719 -AT+COMMANDx: Configure RS485 read command to sensor.
720 -
721 -AT+DATACUTx: Configure how to handle return from RS485 devices.
722 -
723 -AT+SEARCHx: Configure search command
724 -
725 -
726 -* Downlink Payload:
727 -
728 -0xAF downlink command can be used to set AT+COMMANDx or AT+DATACUTx.
729 -
730 -Note: if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink.
731 -
732 -Format: AF MM NN LL XX XX XX XX YY
733 -
734 -Where:
735 -
736 -* MM: the ATCOMMAND or AT+DATACUT to be set. Value from 01 ~~ 0F,
737 -* NN: 0: no CRC; 1: add CRC-16/MODBUS ; 2: set the AT+DATACUT value.
738 -* LL: The length of AT+COMMAND or AT+DATACUT command
739 -* XX XX XX XX: AT+COMMAND or AT+DATACUT command
740 -* YY: If YY=0, RS485-BL will execute the downlink command without uplink; if YY=1, RS485-BL will execute an uplink after got this command.
741 -
742 -Example:
743 -
744 -**AF 03 01 06 0A 05 00 04 00 01 00**: Same as AT+COMMAND3=0A 05 00 04 00 01,1
745 -
746 -**AF 03 02 06 10 01 05 06 09 0A 00**: Same as AT+DATACUT3=**16**,**1**,**5+6+9+10**
747 -
748 -**AF 03 02 06 0B 02 05 07 08 0A 00**: Same as AT+DATACUT3=**11**,**2**,**5~~7+8~~10**
749 -
750 -
751 -0xAB downlink command can be used for set AT+SEARCHx
752 -
753 -Example: **AB aa 01 03 xx xx xx** (03 here means there are total 3 bytes after 03) So
754 -
755 -* AB aa 01 03 xx xx xx  same as AT+SEARCHaa=1,xx xx xx
756 -* AB aa 02 03 xx xx xx 02 yy yy(03 means there are 3 bytes after 03, they are xx xx xx;02 means there are 2 bytes after 02, they are yy yy) so the commands
757 -
758 -**AB aa 02 03 xx xx xx 02 yy yy**  same as **AT+SEARCHaa=2,xx xx xx+yy yy**
759 -
760 -
761 -==== Fast command to handle MODBUS device ====
762 -
763 -AT+MBFUN is valid since v1.3 firmware version. The command is for fast configure to read Modbus devices. It is only valid for the devices which follow the [[MODBUS-RTU protocol>>url:https://www.modbustools.com/modbus.html]].
764 -
765 -This command is valid since v1.3 firmware version
766 -
767 -
768 -AT+MBFUN has only two value:
769 -
770 -* AT+MBFUN=1: Enable Modbus reading. And get response base on the MODBUS return
771 -
772 -AT+MBFUN=1, device can auto read the Modbus function code: 01, 02, 03 or 04. AT+MBFUN has lower priority vs AT+DATACUT command. If AT+DATACUT command is configured, AT+MBFUN will be ignore.
773 -
774 -* AT+MBFUN=0: Disable Modbus fast reading.
775 -
776 -Example:
777 -
778 -* AT+MBFUN=1 and AT+DATACUT1/AT+DATACUT2 are not configure (0,0,0).
779 -* AT+COMMAND1= 01 03 00 10 00 08,1 ~-~-> read slave address 01 , function code 03, start address 00 01, quantity of registers 00 08.
780 -* AT+COMMAND2= 01 02 00 40 00 10,1 ~-~-> read slave address 01 , function code 02, start address 00 40, quantity of inputs 00 10.
781 -
782 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image025.png]]
783 -
784 -
785 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image026.png]]
786 -
787 -
788 -* Downlink Commands:
789 -
790 -A9 aa -à Same as AT+MBFUN=aa
791 -
792 -
793 -==== RS485 command timeout ====
794 -
795 -Some Modbus device has slow action to send replies. This command is used to configure the RS485-BL to use longer time to wait for their action.
796 -
797 -Default value: 0, range:  0 ~~ 5 seconds
798 -
799 -
800 -* AT Command:
801 -
802 -AT+CMDDLaa=hex(bb cc)
803 -
804 -Example:
805 -
806 -**AT+CMDDL1=1000** to send the open time to 1000ms
807 -
808 -
809 -* Downlink Payload:
810 -
811 -0x AA aa bb cc
812 -
813 -Same as: AT+CMDDLaa=hex(bb cc)
814 -
815 - Example:
816 -
817 - 0xAA 01 03 E8  à Same as **AT+CMDDL1=1000 ms**
818 -
819 -
820 -==== [[Uplink>>path:#downlink_A8]] payload mode ====
821 -
822 -Define to use one uplink or multiple uplinks for the sampling.
823 -
824 -The use of this command please see: [[Compose Uplink payload>>path:#DataUP]]
825 -
826 -* AT Command:
827 -
828 -AT+DATAUP=0
829 -
830 -AT+DATAUP=1
831 -
832 -
833 -* Downlink Payload:
834 -
835 -0xAD 00   à Same as AT+DATAUP=0
836 -
837 -0xAD 01   à Same as AT+DATAUP=1
838 -
839 -
840 -==== Manually trigger an Uplink ====
841 -
842 -Ask device to send an uplink immediately.
843 -
844 -* Downlink Payload:
845 -
846 -0x08 FF, RS485-BL will immediately send an uplink.
847 -
848 -
849 -==== Clear RS485 Command ====
850 -
851 -The AT+COMMANDx and AT+DATACUTx settings are stored in special location, user can use below command to clear them.
852 -
853 -
854 -* AT Command:
855 -
856 -**AT+CMDEAR=mm,nn**   mm: start position of erase ,nn: stop position of erase
857 -
858 -Etc. AT+CMDEAR=1,10 means erase AT+COMMAND1/AT+DATACUT1 to AT+COMMAND10/AT+DATACUT10
859 -
860 -Example screen shot after clear all RS485 commands. 
861 -
862 -
863 -
864 -The uplink screen shot is:
865 -
866 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]
867 -
868 -
869 -* Downlink Payload:
870 -
871 -0x09 aa bb same as AT+CMDEAR=aa,bb
872 -
873 -
874 -==== Set Serial Communication Parameters ====
875 -
876 -Set the Rs485 serial communication parameters:
877 -
878 -* AT Command:
879 -
880 -Set Baud Rate:
881 -
882 -AT+BAUDR=9600    ~/~/ Options: (1200,2400,4800,14400,19200,115200)
883 -
884 -
885 -Set UART parity
886 -
887 -AT+PARITY=0    ~/~/ Option: 0: no parity, 1: odd parity, 2: even parity
888 -
889 -
890 -Set STOPBIT
891 -
892 -AT+STOPBIT=0    ~/~/ Option: 0 for 1bit; 1 for 1.5 bit ; 2 for 2 bits
893 -
894 -
895 -* Downlink Payload:
896 -
897 -A7 01 aa bb: Same  AT+BAUDR=hex(aa bb)*100
898 -
899 -Example:
900 -
901 -* A7 01 00 60   same as AT+BAUDR=9600
902 -* A7 01 04 80  same as AT+BAUDR=115200
903 -
904 -A7 02 aa: Same as  AT+PARITY=aa  (aa value: 00 , 01 or 02)
905 -
906 -A7 03 aa: Same as  AT+STOPBIT=aa  (aa value: 00 , 01 or 02)
907 -
908 -
909 -==== Control output power duration ====
910 -
911 -User can set the output power duration before each sampling.
912 -
913 -* AT Command:
914 -
915 -Example:
916 -
917 -AT+3V3T=1000 ~/~/ 3V3 output power will open 1s before each sampling.
918 -
919 -AT+5VT=1000 ~/~/ +5V output power will open 1s before each sampling.
920 -
921 -
922 -* LoRaWAN Downlink Command:
923 -
924 -07 01 aa bb  Same as AT+5VT=(aa bb)
925 -
926 -07 02 aa bb  Same as AT+3V3T=(aa bb)
927 -
928 -
929 -
930 -
931 -1.
932 -11. Buttons
933 -
934 -|**Button**|**Feature**
935 -|**RST**|Reboot RS485-BL
936 -
937 -1.
938 -11. +3V3 Output
939 -
940 -RS485-BL has a Controllable +3V3 output, user can use this output to power external sensor.
941 -
942 -The +3V3 output will be valid for every sampling. RS485-BL will enable +3V3 output before all sampling and disable the +3V3 after all sampling. 
943 -
944 -
945 -The +3V3 output time can be controlled by AT Command.
946 -
947 -**AT+3V3T=1000**
948 -
949 -Means set +3v3 valid time to have 1000ms. So, the real +3v3 output will actually have 1000ms + sampling time for other sensors.
950 -
951 -
952 -By default, the AT+3V3T=0. This is a special case, means the +3V3 output is always on at any time
953 -
954 -
955 -1.
956 -11. +5V Output
957 -
958 -RS485-BL has a Controllable +5V output, user can use this output to power external sensor.
959 -
960 -The +5V output will be valid for every sampling. RS485-BL will enable +5V output before all sampling and disable the +5v after all sampling. 
961 -
962 -
963 -The 5V output time can be controlled by AT Command.
964 -
965 -**AT+5VT=1000**
966 -
967 -Means set 5V valid time to have 1000ms. So, the real 5V output will actually have 1000ms + sampling time for other sensors.
968 -
969 -
970 -By default, the AT+5VT=0. If the external sensor which require 5v and require more time to get stable state, user can use this command to increase the power ON duration for this sensor.
971 -
972 -
973 -
974 -
975 -1.
976 -11. LEDs
977 -
978 -|**LEDs**|**Feature**
979 -|**LED1**|Blink when device transmit a packet.
980 -
981 -1.
982 -11. Switch Jumper
983 -
984 -|**Switch Jumper**|**Feature**
985 -|**SW1**|(((
986 -ISP position: Upgrade firmware via UART
987 -
988 -Flash position: Configure device, check running status.
989 -)))
990 -|**SW2**|(((
991 -5V position: set to compatible with 5v I/O.
992 -
993 -3.3v position: set to compatible with 3.3v I/O.,
994 -)))
995 -
996 -+3.3V: is always ON
997 -
998 -+5V: Only open before every sampling. The time is by default, it is AT+5VT=0.  Max open time. 5000 ms.
999 -
1000 -1. Case Study
1001 -
1002 -User can check this URL for some case studies.
1003 -
1004 -[[http:~~/~~/wiki.dragino.com/index.php?title=APP_RS485_COMMUNICATE_WITH_SENSORS>>url:http://wiki.dragino.com/index.php?title=APP_RS485_COMMUNICATE_WITH_SENSORS]]
1005 -
1006 -
1007 -
1008 -
1009 -1. Use AT Command
1010 -11. Access AT Command
1011 -
1012 -RS485-BL supports AT Command set. User can use a USB to TTL adapter plus the 3.5mm Program Cable to connect to RS485-BL to use AT command, as below.
1013 -
1014 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image027.png]]
1015 -
1016 -
1017 -In PC, User needs to set **serial tool**(such as [[putty>>url:https://www.chiark.greenend.org.uk/~~sgtatham/putty/latest.html]], SecureCRT) baud rate to **9600** to access to access serial console of RS485-BL. The default password is 123456. Below is the output for reference:
1018 -
1019 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image028.png]]
1020 -
1021 -
1022 -
1023 -More detail AT Command manual can be found at [[AT Command Manual>>path:#AT_COMMAND]]
1024 -
1025 -
1026 -
1027 -1.
1028 -11. Common AT Command Sequence
1029 -111. Multi-channel ABP mode (Use with SX1301/LG308)
1030 -
1031 -If device has not joined network yet:
1032 -
1033 -AT+FDR
1034 -
1035 -AT+NJM=0
1036 -
1037 -ATZ
1038 -
1039 -
1040 -If device already joined network:
1041 -
1042 -AT+NJM=0
1043 -
1044 -ATZ
1045 -
1046 -1.
1047 -11.
1048 -111. Single-channel ABP mode (Use with LG01/LG02)
1049 -
1050 -AT+FDR   Reset Parameters to Factory Default, Keys Reserve
1051 -
1052 -AT+NJM=0 Set to ABP mode
1053 -
1054 -AT+ADR=0 Set the Adaptive Data Rate Off
1055 -
1056 -AT+DR=5  Set Data Rate
1057 -
1058 -AT+TDC=60000  Set transmit interval to 60 seconds
1059 -
1060 -AT+CHS=868400000 Set transmit frequency to 868.4Mhz
1061 -
1062 -AT+RX2FQ=868400000 Set RX2Frequency to 868.4Mhz (according to the result from server)
1063 -
1064 -AT+RX2DR=5  Set RX2DR to match the downlink DR from server. see below
1065 -
1066 -AT+DADDR=26 01 1A F1 Set Device Address to 26 01 1A F1, this ID can be found in the LoRa Server portal.
1067 -
1068 -ATZ          Reset MCU
1069 -
1070 -**Note:**
1071 -
1072 -1. Make sure the device is set to ABP mode in the IoT Server.
1073 -1. Make sure the LG01/02 gateway RX frequency is exactly the same as AT+CHS setting.
1074 -1. Make sure SF / bandwidth setting in LG01/LG02 match the settings of AT+DR. refer [[this link>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/&file=LoRaWAN%201.0.3%20Regional%20Parameters.xlsx]] to see what DR means.
1075 -1. The command AT+RX2FQ and AT+RX2DR is to let downlink work. to set the correct parameters, user can check the actually downlink parameters to be used. As below. Which shows the RX2FQ should use 868400000 and RX2DR should be 5
1076 -
1077 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image029.png]]
1078 -
1079 -
1080 -1. FAQ
1081 -11. How to upgrade the image?
1082 -
1083 -The RS485-BL LoRaWAN Controller is shipped with a 3.5mm cable, the cable is used to upload image to RS485-BL to:
1084 -
1085 -* Support new features
1086 -* For bug fix
1087 -* Change LoRaWAN bands.
1088 -
1089 -Below shows the hardware connection for how to upload an image to RS485-BL:
1090 -
1091 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image030.png]]
1092 -
1093 -**Step1:** Download [[flash loader>>url:https://www.st.com/content/st_com/en/products/development-tools/software-development-tools/stm32-software-development-tools/stm32-programmers/flasher-stm32.html]].
1094 -
1095 -**Step2**: Download the [[LT Image files>>url:http://www.dragino.com/downloads/index.php?dir=LT_LoRa_IO_Controller/LT33222-L/image/]].
1096 -
1097 -**Step3: **Open flashloader; choose the correct COM port to update.
1098 -
1099 -
1100 -|(((
1101 -HOLD PRO then press the RST button, SYS will be ON, then click next
1102 -)))
1103 -
1104 -|(((
1105 -Board detected
1106 -)))
1107 -
1108 -|(((
1109 -
1110 -)))
1111 -
1112 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image031.png]] [[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image032.png]]
1113 -
1114 -
1115 -
1116 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image033.png]] [[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image034.png]]
1117 -
1118 -
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 -
1121 -
1122 -1.
1123 -11. How to change the LoRa Frequency Bands/Region?
1124 -
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 -
1127 -
1128 -
1129 -1.
1130 -11. How many RS485-Slave can RS485-BL connects?
1131 -
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]].
1133 -
1134 -
1135 -
1136 -
1137 -1. Trouble Shooting     
1138 -11. Downlink doesn’t work, how to solve it?
1139 -
1140 -Please see this link for debug:
1141 -
1142 -[[http:~~/~~/wiki.dragino.com/index.php?title=Main_Page#LoRaWAN_Communication_Debug>>url:http://wiki.dragino.com/index.php?title=Main_Page#LoRaWAN_Communication_Debug]] 
1143 -
1144 -
1145 -
1146 -1.
1147 -11. Why I can’t join TTN V3 in US915 /AU915 bands?
1148 -
1149 -It might about the channels mapping. Please see for detail.
1150 -
1151 -[[http:~~/~~/wiki.dragino.com/index.php?title=LoRaWAN_Communication_Debug#Notice_of_US915.2FCN470.2FAU915_Frequency_band>>url:http://wiki.dragino.com/index.php?title=LoRaWAN_Communication_Debug#Notice_of_US915.2FCN470.2FAU915_Frequency_band]]
1152 -
1153 -
1154 -
1155 -1. Order Info
1156 -
1157 -**Part Number: RS485-BL-XXX**
1158 -
1159 -**XXX:**
1160 -
1161 -* **EU433**: frequency bands EU433
1162 -* **EU868**: frequency bands EU868
1163 -* **KR920**: frequency bands KR920
1164 -* **CN470**: frequency bands CN470
1165 -* **AS923**: frequency bands AS923
1166 -* **AU915**: frequency bands AU915
1167 -* **US915**: frequency bands US915
1168 -* **IN865**: frequency bands IN865
1169 -* **RU864**: frequency bands RU864
1170 -* **KZ865: **frequency bands KZ865
1171 -
1172 -1. Packing Info
1173 -
1174 -**Package Includes**:
1175 -
1176 -* RS485-BL x 1
1177 -* Stick Antenna for LoRa RF part x 1
1178 -* Program cable x 1
1179 -
1180 -**Dimension and weight**:
1181 -
1182 -* Device Size: 13.5 x 7 x 3 cm
1183 -* Device Weight: 105g
1184 -* Package Size / pcs : 14.5 x 8 x 5 cm
1185 -* Weight / pcs : 170g
1186 -
1187 -1. Support
1188 -
1189 -* Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule.
1190 -* Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to
1191 -
1192 -[[support@dragino.com>>url:file:///D:/市场资料/说明书/LoRa/LT系列/support@dragino.com]]
523 +==== ====
1653268155545-638.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +113.7 KB
Content
1653268227651-549.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +1.3 MB
Content
1653269403619-508.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +27.8 KB
Content
1653269438444-278.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +26.6 KB
Content
1653269551753-223.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +138.7 KB
Content
1653269568276-930.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +131.4 KB
Content
1653269593172-426.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +142.6 KB
Content
1653269618463-608.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +27.7 KB
Content
1653269759169-150.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +294.0 KB
Content
1653269916228-732.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +143.3 KB
Content
1653270130359-810.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +197.8 KB
Content
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