Skip to Content
Last modified by Xiaoling on 2025/04/23 15:57
From version 29.21
edited by Xiaoling
on 2022/06/01 18:08
Change comment: There is no comment for this version
To version 15.1
edited by Xiaoling
on 2022/05/19 17:46
Change comment: Uploaded new attachment "1652953568895-172.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -7,15 +7,12 @@
7 7  **RS485-BL – Waterproof RS485 to LoRaWAN Converter User Manual**
8 8  
9 9  
10 -
11 11  **Table of Contents:**
12 12  
13 -{{toc/}}
14 14  
15 15  
16 16  
17 17  
18 -
19 19  = 1.Introduction =
20 20  
21 21  == 1.1 What is RS485-BL RS485 to LoRaWAN Converter ==
... ... @@ -25,19 +25,19 @@
25 25  )))
26 26  
27 27  (((
28 -The Dragino RS485-BL is a (% style="color:blue" %)**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.
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.
29 29  )))
30 30  
31 31  (((
32 -RS485-BL can interface to RS485 sensor, 3.3v/5v UART sensor or interrupt sensor. RS485-BL provides (% style="color:blue" %)**a 3.3v output**(%%) and** (% style="color:blue" %)a 5v output(%%)** to power external sensors. Both output voltages are controllable to minimize the total system power consumption.
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.
33 33  )))
34 34  
35 35  (((
36 -RS485-BL is IP67 (% style="color:blue" %)**waterproof**(%%) and powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), it is designed for long term use for several years.
33 +RS485-BL is IP67 **waterproof** and powered by **8500mAh Li-SOCI2 battery**, it is designed for long term use for several years.
37 37  )))
38 38  
39 39  (((
40 -RS485-BL runs standard (% style="color:blue" %)**LoRaWAN 1.0.3 in Class A**(%%). It can reach long transfer range and easy to integrate with LoRaWAN compatible gateway and IoT server.
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.
41 41  )))
42 42  
43 43  (((
... ... @@ -54,11 +54,8 @@
54 54  
55 55  [[image:1652953304999-717.png||height="424" width="733"]]
56 56  
57 -
58 -
59 59  == 1.2 Specifications ==
60 60  
61 -
62 62  **Hardware System:**
63 63  
64 64  * STM32L072CZT6 MCU
... ... @@ -65,9 +65,10 @@
65 65  * SX1276/78 Wireless Chip 
66 66  * Power Consumption (exclude RS485 device):
67 67  ** Idle: 6uA@3.3v
62 +
63 +*
68 68  ** 20dB Transmit: 130mA@3.3v
69 69  
70 -
71 71  **Interface for Model:**
72 72  
73 73  * 1 x RS485 Interface
... ... @@ -77,7 +77,6 @@
77 77  * 1 x Interrupt Interface
78 78  * 1 x Controllable 5V output, max
79 79  
80 -
81 81  **LoRa Spec:**
82 82  
83 83  * Frequency Range:
... ... @@ -96,7 +96,6 @@
96 96  * 127 dB Dynamic Range RSSI.
97 97  * Automatic RF Sense and CAD with ultra-fast AFC. ​​​
98 98  
99 -
100 100  == 1.3 Features ==
101 101  
102 102  * LoRaWAN Class A & Class C protocol (default Class A)
... ... @@ -108,7 +108,6 @@
108 108  * Support Modbus protocol
109 109  * Support Interrupt uplink
110 110  
111 -
112 112  == 1.4 Applications ==
113 113  
114 114  * Smart Buildings & Home Automation
... ... @@ -118,17 +118,13 @@
118 118  * Smart Cities
119 119  * Smart Factory
120 120  
121 -
122 122  == 1.5 Firmware Change log ==
123 123  
124 124  [[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);"]]
125 125  
126 -
127 127  == 1.6 Hardware Change log ==
128 128  
129 129  (((
130 -
131 -
132 132  v1.4
133 133  )))
134 134  
... ... @@ -152,8 +152,6 @@
152 152  
153 153  (((
154 154  Release version ​​​​​
155 -
156 -
157 157  )))
158 158  
159 159  = 2. Pin mapping and Power ON Device =
... ... @@ -167,7 +167,6 @@
167 167  
168 168  The Left TXD and RXD are TTL interface for external sensor. TTL level is controlled by 3.3/5v Jumper.
169 169  
170 -
171 171  = 3. Operation Mode =
172 172  
173 173  == 3.1 How it works? ==
... ... @@ -174,8 +174,6 @@
174 174  
175 175  (((
176 176  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.
177 -
178 -
179 179  )))
180 180  
181 181  == 3.2 Example to join LoRaWAN network ==
... ... @@ -184,241 +184,204 @@
184 184  
185 185  [[image:1652953414711-647.png||height="337" width="723"]]
186 186  
187 -(((
170 +
188 188  The RS485-BL in this example connected to two RS485 devices for demonstration, user can connect to other RS485 devices via the same method.
189 -)))
190 190  
191 -(((
173 +
192 192  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:
193 -)))
194 194  
195 -(((
196 196  **Step 1**: Create a device in TTN V3 with the OTAA keys from RS485-BL.
197 -)))
198 198  
199 -(((
200 200  Each RS485-BL is shipped with a sticker with unique device EUI:
201 -)))
202 202  
203 -[[image:1652953462722-299.png]]
180 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image005.png]]
204 204  
205 -(((
182 +
183 +
184 +
206 206  User can enter this key in their LoRaWAN Server portal. Below is TTN V3 screen shot:
207 -)))
208 208  
209 -(((
210 210  Add APP EUI in the application.
211 -)))
212 212  
189 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image006.png]]
213 213  
214 -[[image:image-20220519174512-1.png]]
191 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image007.png]]
215 215  
216 -[[image:image-20220519174512-2.png||height="328" width="731"]]
193 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image008.png]]
217 217  
218 -[[image:image-20220519174512-3.png||height="556" width="724"]]
195 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image009.png]]
219 219  
220 -[[image:image-20220519174512-4.png]]
221 221  
198 +
199 +
200 +
201 +
202 +
203 +
204 +
205 +
206 +
207 +
208 +
209 +
210 +
211 +
212 +
222 222  You can also choose to create the device manually.
223 223  
224 -[[image:1652953542269-423.png||height="710" width="723"]]
215 +|(((
216 +
217 +)))
225 225  
219 +
220 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image010.png]]
221 +
226 226  Add APP KEY and DEV EUI
227 227  
228 -[[image:1652953553383-907.png||height="514" width="724"]]
224 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image011.png]]
229 229  
230 230  
231 -(((
232 232  **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.
233 -)))
234 234  
235 -[[image:1652953568895-172.png||height="232" width="724"]]
229 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image012.png]]
236 236  
237 237  
238 -== 3.3 Configure Commands to read data ==
239 239  
240 -(((
241 -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>>||anchor="H3.5ConfigureRS485-BLviaATorDownlink"]] Command to configure how RS485-BL should read the sensor and how to handle the return from RS485 or TTL sensors.
242 242  
243 -
244 -)))
234 +1.
235 +11. Configure Commands to read data
245 245  
246 -=== 3.3.1 onfigure UART settings for RS485 or TTL communication ===
237 +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.
247 247  
239 +
240 +1.
241 +11.
242 +111. Configure UART settings for RS485 or TTL communication
243 +
248 248  RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect.
249 249  
250 -**~1. RS485-MODBUS mode:**
246 +1. RS485-MODBUS mode:
251 251  
252 252  AT+MOD=1 ~/~/ Support RS485-MODBUS type sensors. User can connect multiply RS485 , Modbus sensors to the A / B pins.
253 253  
254 -**2. TTL mode:**
255 255  
251 +1. TTL mode:
252 +
256 256  AT+MOD=2 ~/~/ Support TTL Level sensors, User can connect one TTL Sensor to the TXD/RXD/GND pins.
257 257  
255 +
258 258  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.
259 259  
260 -(% border="1" style="background-color:#ffffcc; color:green; width:795px" %)
261 -|(((
262 -**AT Commands**
263 -)))|(% style="width:285px" %)(((
264 -**Description**
265 -)))|(% style="width:347px" %)(((
266 -**Example**
267 -)))
268 -|(((
269 -AT+BAUDR
270 -)))|(% style="width:285px" %)(((
271 -Set the baud rate (for RS485 connection). Default Value is: 9600.
272 -)))|(% style="width:347px" %)(((
273 -(((
258 +
259 +|**AT Commands**|**Description**|**Example**
260 +|AT+BAUDR|Set the baud rate (for RS485 connection). Default Value is: 9600.|(((
274 274  AT+BAUDR=9600
275 -)))
276 276  
277 -(((
278 278  Options: (1200,2400,4800,14400,19200,115200)
279 279  )))
280 -)))
281 -|(((
282 -AT+PARITY
283 -)))|(% style="width:285px" %)(((
284 -(((
265 +|AT+PARITY|(((
285 285  Set UART parity (for RS485 connection)
286 -)))
287 287  
288 -(((
289 289  Default Value is: no parity.
290 -)))
291 -)))|(% style="width:347px" %)(((
292 -(((
269 +)))|(((
293 293  AT+PARITY=0
294 -)))
295 295  
296 -(((
297 297  Option: 0: no parity, 1: odd parity, 2: even parity
298 298  )))
299 -)))
300 -|(((
301 -AT+STOPBIT
302 -)))|(% style="width:285px" %)(((
303 -(((
274 +|AT+STOPBIT|(((
304 304  Set serial stopbit (for RS485 connection)
305 -)))
306 306  
307 -(((
308 308  Default Value is: 1bit.
309 -)))
310 -)))|(% style="width:347px" %)(((
311 -(((
278 +)))|(((
312 312  AT+STOPBIT=0 for 1bit
313 -)))
314 314  
315 -(((
316 316  AT+STOPBIT=1 for 1.5 bit
317 -)))
318 318  
319 -(((
320 320  AT+STOPBIT=2 for 2 bits
321 321  )))
322 -)))
323 323  
324 324  
325 325  
326 -=== 3.3.2 Configure sensors ===
327 327  
328 -(((
329 -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**.
330 -)))
289 +1.
290 +11.
291 +111. Configure sensors
331 331  
332 -(((
333 -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.
334 -)))
293 +Some sensors might need to configure before normal operation. User can configure such sensor via PC or through RS485-BL AT Commands AT+CFGDEV.
335 335  
336 -(% border="1" style="background-color:#ffffcc; color:green; width:806px" %)
337 -|**AT Commands**|(% style="width:418px" %)**Description**|(% style="width:256px" %)**Example**
338 -|AT+CFGDEV|(% style="width:418px" %)(((
295 +
296 +When user issue an AT+CFGDEV command, Each 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.
297 +
298 +|**AT Commands**|**Description**|**Example**
299 +|AT+CFGDEV|(((
339 339  This command is used to configure the RS485/TTL devices; they won’t be used during sampling.
340 340  
341 -AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,
302 +AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
342 342  
343 -mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
344 -)))|(% style="width:256px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
304 +m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
305 +)))|AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
345 345  
346 346  Detail of AT+CFGDEV command see [[AT+CFGDEV detail>>path:#AT_CFGDEV]].
347 347  
348 -=== 3.3.3 Configure read commands for each sampling ===
349 349  
350 -(((
310 +
311 +
312 +
313 +1.
314 +11.
315 +111. Configure read commands for each sampling
316 +
351 351  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.
352 -)))
353 353  
354 -(((
319 +
355 355  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.
356 -)))
357 357  
358 -(((
322 +
359 359  To save the LoRaWAN network bandwidth, we might need to read data from different sensors and combine their valid value into a short payload.
360 -)))
361 361  
362 -(((
325 +
363 363  This section describes how to achieve above goals.
364 -)))
365 365  
366 -(((
328 +
367 367  During each sampling, the RS485-BL can support 15 commands to read sensors. And combine the return to one or several uplink payloads.
368 -)))
369 369  
370 -(((
331 +
371 371  **Command from RS485-BL to Sensor:**
372 -)))
373 373  
374 -(((
375 375  RS485-BL can send out pre-set max 15 strings via **AT+COMMAD1**, **ATCOMMAND2**,…, to **AT+COMMANDF** . All commands are of same grammar.
376 -)))
377 377  
378 -(((
336 +
379 379  **Handle return from sensors to RS485-BL**:
380 -)))
381 381  
382 -(((
383 383  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**
384 -)))
385 385  
386 -* (((
387 -**AT+DATACUT**
388 -)))
389 389  
390 -(((
342 +* **AT+DATACUT**
343 +
391 391  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.
392 -)))
393 393  
394 -* (((
395 -**AT+SEARCH**
396 -)))
397 397  
398 -(((
347 +* **AT+SEARCH**
348 +
399 399  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.
400 -)))
401 401  
402 -(((
351 +
403 403  **Define wait timeout:**
404 -)))
405 405  
406 -(((
407 407  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
408 -)))
409 409  
410 -(((
356 +
411 411  After we got the valid value from each RS485 commands, we need to combine them together with the command **AT+DATAUP**.
412 -)))
413 413  
359 +
414 414  **Examples:**
415 415  
416 416  Below are examples for the how above AT Commands works.
417 417  
364 +
418 418  **AT+COMMANDx : **This command will be sent to RS485/TTL devices during each sampling, Max command length is 14 bytes. The grammar is:
419 419  
420 -(% border="1" class="table-bordered" style="background-color:#4f81bd; color:white; width:501px" %)
421 -|(% style="width:498px" %)(((
367 +|(((
422 422  **AT+COMMANDx=xx xx xx xx xx xx xx xx xx xx xx xx,m**
423 423  
424 424  **xx xx xx xx xx xx xx xx xx xx xx xx: The RS485 command to be sent**
... ... @@ -430,38 +430,41 @@
430 430  
431 431  In the RS485-BL, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
432 432  
379 +
433 433  **AT+SEARCHx**: This command defines how to handle the return from AT+COMMANDx.
434 434  
435 -(% border="1" class="table-bordered" style="background-color:#4f81bd; color:white; width:580px" %)
436 -|(% style="width:577px" %)(((
382 +|(((
437 437  **AT+SEARCHx=aa,xx xx xx xx xx**
438 438  
439 439  * **aa: 1: prefix match mode; 2: prefix and suffix match mode**
440 440  * **xx xx xx xx xx: match string. Max 5 bytes for prefix and 5 bytes for suffix**
387 +
388 +
441 441  )))
442 442  
443 -**Examples:**
391 +Examples:
444 444  
445 445  1. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
446 446  
447 447  If we set AT+SEARCH1=1,1E 56 34.      (max 5 bytes for prefix)
448 448  
449 -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**
397 +The valid data will be all bytes after 1E 56 34 , so it is 2e 30 58 5f 36 41 30 31 00 49
450 450  
451 -[[image:1653271044481-711.png]]
399 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image013.png]]
452 452  
401 +
453 453  1. For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
454 454  
455 455  If we set AT+SEARCH1=2, 1E 56 34+31 00 49
456 456  
457 -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**
406 +Device will search the bytes between 1E 56 34 and 31 00 49. So it is 2e 30 58 5f 36 41 30
458 458  
459 -[[image:1653271276735-972.png]]
408 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image014.png]]
460 460  
410 +
461 461  **AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes.
462 462  
463 -(% style="background-color:#4f81bd; color:white; width:729px" %)
464 -|(% style="width:726px" %)(((
413 +|(((
465 465  **AT+DATACUTx=a,b,c**
466 466  
467 467  * **a: length for the return of AT+COMMAND**
... ... @@ -473,130 +473,95 @@
473 473  
474 474  * Grab bytes:
475 475  
476 -[[image:1653271581490-837.png||height="313" width="722"]]
425 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image015.png]]
477 477  
478 478  * Grab a section.
479 479  
480 -[[image:1653271648378-342.png||height="326" width="720"]]
429 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image016.png]]
481 481  
482 482  * Grab different sections.
483 483  
484 -[[image:1653271657255-576.png||height="305" width="730"]]
433 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image017.png]]
485 485  
486 -(((
487 -(% style="color:red" %)**Note:**
488 -)))
489 489  
490 -(((
436 +Note:
437 +
491 491  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.
492 -)))
493 493  
494 -(((
495 -**Example:**
496 -)))
440 +Example:
497 497  
498 -(((
499 -(% style="color:red" %)AT+COMMAND1=11 01 1E D0,0
500 -)))
442 +AT+COMMAND1=11 01 1E D0,0
501 501  
502 -(((
503 -(% style="color:red" %)AT+SEARCH1=1,1E 56 34
504 -)))
444 +AT+SEARCH1=1,1E 56 34
505 505  
506 -(((
507 -(% style="color:red" %)AT+DATACUT1=0,2,1~~5
508 -)))
446 +AT+DATACUT1=0,2,1~~5
509 509  
510 -(((
511 -(% style="color:red" %)Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
512 -)))
448 +Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
513 513  
514 -(((
515 -(% style="color:red" %)String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
516 -)))
450 +String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
517 517  
518 -(((
519 -(% style="color:red" %)Valid payload after DataCUT command: 2e 30 58 5f 36
520 -)))
452 +Valid payload after DataCUT command: 2e 30 58 5f 36
521 521  
522 -[[image:1653271763403-806.png]]
454 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image018.png]]
523 523  
524 -=== 3.3.4 Compose the uplink payload ===
525 525  
526 -(((
457 +
458 +
459 +1.
460 +11.
461 +111. Compose the uplink payload
462 +
527 527  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.**
528 -)))
529 529  
530 -(((
531 -(% style="color:#4f81bd" %)**Examples: AT+DATAUP=0**
532 -)))
533 533  
534 -(((
535 -Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**A SIGNLE UPLINK**.
536 -)))
466 +**Examples: AT+DATAUP=0**
537 537  
538 -(((
468 +Compose the uplink payload with value returns in sequence and send with **A SIGNLE UPLINK**.
469 +
539 539  Final Payload is
540 -)))
541 541  
542 -(((
543 -(% style="color:#4f81bd" %)Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx
544 -)))
472 +Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx
545 545  
546 -(((
547 547  Where PAYVER is defined by AT+PAYVER, below is an example screen shot.
548 -)))
549 549  
550 -[[image:1653272787040-634.png||height="515" width="719"]]
476 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.png]]
551 551  
552 -(((
553 -(% style="color:#4f81bd" %)**Examples: AT+DATAUP=1**
554 -)))
555 555  
556 -(((
557 -Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**Multiply UPLINKs**.
558 -)))
559 559  
560 -(((
480 +**Examples: AT+DATAUP=1**
481 +
482 +Compose the uplink payload with value returns in sequence and send with **Multiply UPLINKs**.
483 +
561 561  Final Payload is
562 -)))
563 563  
564 -(((
565 -(% style="color:#4f81bd" %)Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA
566 -)))
486 +Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA
567 567  
568 -1. (((
569 -Battery Info (2 bytes): Battery voltage
570 -)))
571 -1. (((
572 -PAYVER (1 byte): Defined by AT+PAYVER
573 -)))
574 -1. (((
575 -PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling.
576 -)))
577 -1. (((
578 -PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
579 -)))
580 -1. (((
581 -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
582 -)))
488 +1. Battery Info (2 bytes): Battery voltage
489 +1. PAYVER (1 byte): Defined by AT+PAYVER
490 +1. PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling.
491 +1. PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
492 +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
583 583  
584 -[[image:1653272817147-600.png||height="437" width="717"]]
494 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image020.png]]
585 585  
496 +
586 586  So totally there will be 3 uplinks for this sampling, each uplink includes 6 bytes DATA
587 587  
588 -DATA1=RETURN1 Valid Value = (% style="background-color:#4f81bd; color:white" %) 20 20 0a 33 90 41
499 +DATA1=RETURN1 Valid Value = 20 20 0a 33 90 41
589 589  
590 -DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= (% style="background-color:#4f81bd; color:white" %)02 aa 05 81 0a 20
501 +DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= 02 aa 05 81 0a 20
591 591  
592 -DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 =(% style="background-color:#4f81bd; color:white" %) 20 20 20 2d 30
503 +DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 = 20 20 20 2d 30
593 593  
505 +
506 +
594 594  Below are the uplink payloads:
595 595  
596 -[[image:1653272901032-107.png]]
509 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.png]]
597 597  
598 -(% style="color:red" %)Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:
599 599  
512 +Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:
513 +
600 600   ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink ( so 51 -5 = 46 max valid date)
601 601  
602 602   * For AU915/AS923 bands, if UplinkDwell time=1, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date).
... ... @@ -605,121 +605,90 @@
605 605  
606 606   ~* For all other bands: max 51 bytes for each uplink  ( so 51 -5 = 46 max valid date).
607 607  
608 -=== 3.3.5 Uplink on demand ===
609 609  
610 -(((
523 +
524 +1.
525 +11.
526 +111. Uplink on demand
527 +
611 611  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.
612 -)))
613 613  
614 -(((
615 615  Downlink control command:
616 -)))
617 617  
618 -(((
619 -**0x08 command**: Poll an uplink with current command set in RS485-BL.
620 -)))
532 +[[0x08 command>>path:#downlink_08]]: Poll an uplink with current command set in RS485-BL.
621 621  
622 -(((
623 -**0xA8 command**: Send a command to RS485-BL and uplink the output from sensors.
624 -)))
534 +[[0xA8 command>>path:#downlink_A8]]: Send a command to RS485-BL and uplink the output from sensors.
625 625  
626 -=== 3.3.6 Uplink on Interrupt ===
627 627  
628 -Put the interrupt sensor between 3.3v_out and GPIO ext.
629 629  
630 -[[image:1653273818896-432.png]]
538 +1.
539 +11.
540 +111. Uplink on Interrupt
631 631  
632 -(((
542 +Put the interrupt sensor between 3.3v_out and GPIO ext.[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image022.png]]
543 +
633 633  AT+INTMOD=0  Disable Interrupt
634 -)))
635 635  
636 -(((
637 637  AT+INTMOD=1  Interrupt trigger by rising or falling edge.
638 -)))
639 639  
640 -(((
641 641  AT+INTMOD=2  Interrupt trigger by falling edge. ( Default Value)
642 -)))
643 643  
644 -(((
645 645  AT+INTMOD=3  Interrupt trigger by rising edge.
646 -)))
647 647  
648 -== 3.4 Uplink Payload ==
649 649  
650 -(% border="1" style="background-color:#4f81bd; color:white; width:850px" %)
651 -|**Size(bytes)**|(% style="width:130px" %)**2**|(% style="width:93px" %)**1**|(% style="width:509px" %)**Length depends on the return from the commands**
652 -|Value|(% style="width:130px" %)(((
653 -(((
553 +1.
554 +11. Uplink Payload
555 +
556 +|**Size(bytes)**|**2**|**1**|**Length depends on the return from the commands**
557 +|Value|(((
654 654  Battery(mV)
655 -)))
656 656  
657 -(((
658 658  &
659 -)))
660 660  
661 -(((
662 662  Interrupt _Flag
663 -)))
664 -)))|(% style="width:93px" %)(((
563 +)))|(((
665 665  PAYLOAD_VER
666 666  
667 667  
668 -)))|(% style="width:509px" %)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.
567 +)))|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.
669 669  
670 670  Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors.
671 671  
672 -(((
571 +
673 673  function Decoder(bytes, port) {
674 -)))
675 675  
676 -(((
677 677  ~/~/Payload Formats of RS485-BL Deceive
678 -)))
679 679  
680 -(((
681 681  return {
682 -)))
683 683  
684 -(((
685 685   ~/~/Battery,units:V
686 -)))
687 687  
688 -(((
689 689   BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000,
690 -)))
691 691  
692 -(((
693 693   ~/~/GPIO_EXTI 
694 -)))
695 695  
696 -(((
697 697   EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE",
698 -)))
699 699  
700 -(((
701 701   ~/~/payload of version
702 -)))
703 703  
704 -(((
705 705   Pay_ver:bytes[2],
706 -)))
707 707  
708 -(((
709 709   };
710 -)))
711 711  
712 -(((
713 713   }
714 -)))
715 715  
716 -(((
594 +
595 +
596 +
597 +
598 +
599 +
717 717  TTN V3 uplink screen shot.
718 -)))
719 719  
720 -[[image:1653274001211-372.png||height="192" width="732"]]
602 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]
721 721  
722 -== 3.5 Configure RS485-BL via AT or Downlink ==
604 +1.
605 +11. Configure RS485-BL via AT or Downlink
723 723  
724 724  User can configure RS485-BL via [[AT Commands >>path:#_​Using_the_AT]]or LoRaWAN Downlink Commands
725 725  
... ... @@ -729,15 +729,15 @@
729 729  
730 730  * **Sensor Related Commands**: These commands are special designed for RS485-BL.  User can see these commands below:
731 731  
732 -1.
733 -11.
615 +1.
616 +11.
734 734  111. Common Commands:
735 735  
736 736  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]]
737 737  
738 738  
739 -1.
740 -11.
622 +1.
623 +11.
741 741  111. Sensor related commands:
742 742  
743 743  ==== Choose Device Type (RS485 or TTL) ====
... ... @@ -1043,13 +1043,13 @@
1043 1043  
1044 1044  
1045 1045  
1046 -1.
929 +1.
1047 1047  11. Buttons
1048 1048  
1049 1049  |**Button**|**Feature**
1050 1050  |**RST**|Reboot RS485-BL
1051 1051  
1052 -1.
935 +1.
1053 1053  11. +3V3 Output
1054 1054  
1055 1055  RS485-BL has a Controllable +3V3 output, user can use this output to power external sensor.
... ... @@ -1067,7 +1067,7 @@
1067 1067  By default, the AT+3V3T=0. This is a special case, means the +3V3 output is always on at any time
1068 1068  
1069 1069  
1070 -1.
953 +1.
1071 1071  11. +5V Output
1072 1072  
1073 1073  RS485-BL has a Controllable +5V output, user can use this output to power external sensor.
... ... @@ -1087,13 +1087,13 @@
1087 1087  
1088 1088  
1089 1089  
1090 -1.
973 +1.
1091 1091  11. LEDs
1092 1092  
1093 1093  |**LEDs**|**Feature**
1094 1094  |**LED1**|Blink when device transmit a packet.
1095 1095  
1096 -1.
979 +1.
1097 1097  11. Switch Jumper
1098 1098  
1099 1099  |**Switch Jumper**|**Feature**
... ... @@ -1139,7 +1139,7 @@
1139 1139  
1140 1140  
1141 1141  
1142 -1.
1025 +1.
1143 1143  11. Common AT Command Sequence
1144 1144  111. Multi-channel ABP mode (Use with SX1301/LG308)
1145 1145  
... ... @@ -1158,8 +1158,8 @@
1158 1158  
1159 1159  ATZ
1160 1160  
1161 -1.
1162 -11.
1044 +1.
1045 +11.
1163 1163  111. Single-channel ABP mode (Use with LG01/LG02)
1164 1164  
1165 1165  AT+FDR   Reset Parameters to Factory Default, Keys Reserve
... ... @@ -1234,7 +1234,7 @@
1234 1234  [[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]]
1235 1235  
1236 1236  
1237 -1.
1120 +1.
1238 1238  11. How to change the LoRa Frequency Bands/Region?
1239 1239  
1240 1240  User can follow the introduction for [[how to upgrade image>>path:#upgrade_image]]. When download the images, choose the required image file for download.
... ... @@ -1241,7 +1241,7 @@
1241 1241  
1242 1242  
1243 1243  
1244 -1.
1127 +1.
1245 1245  11. How many RS485-Slave can RS485-BL connects?
1246 1246  
1247 1247  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]].
... ... @@ -1258,7 +1258,7 @@
1258 1258  
1259 1259  
1260 1260  
1261 -1.
1144 +1.
1262 1262  11. Why I can’t join TTN V3 in US915 /AU915 bands?
1263 1263  
1264 1264  It might about the channels mapping. Please see for detail.
1652954654347-831.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -138.7 KB
Content
1653271044481-711.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -27.8 KB
Content
1653271276735-972.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -26.6 KB
Content
1653271581490-837.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -138.7 KB
Content
1653271648378-342.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -131.4 KB
Content
1653271657255-576.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -142.6 KB
Content
1653271763403-806.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -27.7 KB
Content
1653272787040-634.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -294.0 KB
Content
1653272817147-600.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -143.3 KB
Content
1653272901032-107.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -197.8 KB
Content
1653273818896-432.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -31.6 KB
Content
1653274001211-372.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -91.4 KB
Content