Skip to Content
Last modified by Xiaoling on 2025/04/23 15:57
From version 15.2
edited by Xiaoling
on 2022/05/19 17:47
Change comment: There is no comment for this version
To version 34.1
edited by Xiaoling
on 2022/06/02 10:10
Change comment: Uploaded new attachment "1654135840598-282.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -7,12 +7,15 @@
7 7  **RS485-BL – Waterproof RS485 to LoRaWAN Converter User Manual**
8 8  
9 9  
10 +
10 10  **Table of Contents:**
11 11  
13 +{{toc/}}
12 12  
13 13  
14 14  
15 15  
18 +
16 16  = 1.Introduction =
17 17  
18 18  == 1.1 What is RS485-BL RS485 to LoRaWAN Converter ==
... ... @@ -22,19 +22,19 @@
22 22  )))
23 23  
24 24  (((
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.
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.
26 26  )))
27 27  
28 28  (((
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.
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.
30 30  )))
31 31  
32 32  (((
33 -RS485-BL is IP67 **waterproof** and powered by **8500mAh Li-SOCI2 battery**, it is designed for long term use for several years.
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.
34 34  )))
35 35  
36 36  (((
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.
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.
38 38  )))
39 39  
40 40  (((
... ... @@ -51,8 +51,11 @@
51 51  
52 52  [[image:1652953304999-717.png||height="424" width="733"]]
53 53  
57 +
58 +
54 54  == 1.2 Specifications ==
55 55  
61 +
56 56  **Hardware System:**
57 57  
58 58  * STM32L072CZT6 MCU
... ... @@ -59,8 +59,6 @@
59 59  * SX1276/78 Wireless Chip 
60 60  * Power Consumption (exclude RS485 device):
61 61  ** Idle: 6uA@3.3v
62 -
63 -*
64 64  ** 20dB Transmit: 130mA@3.3v
65 65  
66 66  **Interface for Model:**
... ... @@ -114,9 +114,12 @@
114 114  
115 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);"]]
116 116  
121 +
117 117  == 1.6 Hardware Change log ==
118 118  
119 119  (((
125 +
126 +
120 120  v1.4
121 121  )))
122 122  
... ... @@ -140,6 +140,8 @@
140 140  
141 141  (((
142 142  Release version ​​​​​
150 +
151 +
143 143  )))
144 144  
145 145  = 2. Pin mapping and Power ON Device =
... ... @@ -153,6 +153,7 @@
153 153  
154 154  The Left TXD and RXD are TTL interface for external sensor. TTL level is controlled by 3.3/5v Jumper.
155 155  
165 +
156 156  = 3. Operation Mode =
157 157  
158 158  == 3.1 How it works? ==
... ... @@ -159,6 +159,8 @@
159 159  
160 160  (((
161 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.
172 +
173 +
162 162  )))
163 163  
164 164  == 3.2 Example to join LoRaWAN network ==
... ... @@ -167,23 +167,33 @@
167 167  
168 168  [[image:1652953414711-647.png||height="337" width="723"]]
169 169  
182 +(((
170 170  The RS485-BL in this example connected to two RS485 devices for demonstration, user can connect to other RS485 devices via the same method.
184 +)))
171 171  
186 +(((
172 172  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:
188 +)))
173 173  
190 +(((
174 174  **Step 1**: Create a device in TTN V3 with the OTAA keys from RS485-BL.
192 +)))
175 175  
194 +(((
176 176  Each RS485-BL is shipped with a sticker with unique device EUI:
196 +)))
177 177  
178 178  [[image:1652953462722-299.png]]
179 179  
200 +(((
180 180  User can enter this key in their LoRaWAN Server portal. Below is TTN V3 screen shot:
202 +)))
181 181  
204 +(((
182 182  Add APP EUI in the application.
206 +)))
183 183  
184 184  
185 -
186 -
187 187  [[image:image-20220519174512-1.png]]
188 188  
189 189  [[image:image-20220519174512-2.png||height="328" width="731"]]
... ... @@ -208,142 +208,189 @@
208 208  [[image:1652953568895-172.png||height="232" width="724"]]
209 209  
210 210  
233 +== 3.3 Configure Commands to read data ==
211 211  
235 +(((
236 +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.
212 212  
213 -1.
214 -11. Configure Commands to read data
238 +
239 +)))
215 215  
216 -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.
241 +=== 3.3.1 onfigure UART settings for RS485 or TTL communication ===
217 217  
218 -
219 -1.
220 -11.
221 -111. Configure UART settings for RS485 or TTL communication
222 -
223 223  RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect.
224 224  
225 -1. RS485-MODBUS mode:
245 +**~1. RS485-MODBUS mode:**
226 226  
227 227  AT+MOD=1 ~/~/ Support RS485-MODBUS type sensors. User can connect multiply RS485 , Modbus sensors to the A / B pins.
228 228  
249 +**2. TTL mode:**
229 229  
230 -1. TTL mode:
231 -
232 232  AT+MOD=2 ~/~/ Support TTL Level sensors, User can connect one TTL Sensor to the TXD/RXD/GND pins.
233 233  
234 -
235 235  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.
236 236  
237 -
238 -|**AT Commands**|**Description**|**Example**
239 -|AT+BAUDR|Set the baud rate (for RS485 connection). Default Value is: 9600.|(((
255 +(% border="1" style="background-color:#ffffcc; color:green; width:795px" %)
256 +|(((
257 +**AT Commands**
258 +)))|(% style="width:285px" %)(((
259 +**Description**
260 +)))|(% style="width:347px" %)(((
261 +**Example**
262 +)))
263 +|(((
264 +AT+BAUDR
265 +)))|(% style="width:285px" %)(((
266 +Set the baud rate (for RS485 connection). Default Value is: 9600.
267 +)))|(% style="width:347px" %)(((
268 +(((
240 240  AT+BAUDR=9600
270 +)))
241 241  
272 +(((
242 242  Options: (1200,2400,4800,14400,19200,115200)
243 243  )))
244 -|AT+PARITY|(((
275 +)))
276 +|(((
277 +AT+PARITY
278 +)))|(% style="width:285px" %)(((
279 +(((
245 245  Set UART parity (for RS485 connection)
281 +)))
246 246  
283 +(((
247 247  Default Value is: no parity.
248 -)))|(((
285 +)))
286 +)))|(% style="width:347px" %)(((
287 +(((
249 249  AT+PARITY=0
289 +)))
250 250  
291 +(((
251 251  Option: 0: no parity, 1: odd parity, 2: even parity
252 252  )))
253 -|AT+STOPBIT|(((
294 +)))
295 +|(((
296 +AT+STOPBIT
297 +)))|(% style="width:285px" %)(((
298 +(((
254 254  Set serial stopbit (for RS485 connection)
300 +)))
255 255  
302 +(((
256 256  Default Value is: 1bit.
257 -)))|(((
304 +)))
305 +)))|(% style="width:347px" %)(((
306 +(((
258 258  AT+STOPBIT=0 for 1bit
308 +)))
259 259  
310 +(((
260 260  AT+STOPBIT=1 for 1.5 bit
312 +)))
261 261  
314 +(((
262 262  AT+STOPBIT=2 for 2 bits
263 263  )))
317 +)))
264 264  
319 +=== 3.3.2 Configure sensors ===
265 265  
321 +(((
322 +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**.
323 +)))
266 266  
325 +(((
326 +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.
327 +)))
267 267  
268 -1.
269 -11.
270 -111. Configure sensors
271 -
272 -Some sensors might need to configure before normal operation. User can configure such sensor via PC or through RS485-BL AT Commands AT+CFGDEV.
273 -
274 -
275 -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.
276 -
277 -|**AT Commands**|**Description**|**Example**
278 -|AT+CFGDEV|(((
329 +(% border="1" style="background-color:#ffffcc; color:green; width:806px" %)
330 +|**AT Commands**|(% style="width:418px" %)**Description**|(% style="width:256px" %)**Example**
331 +|AT+CFGDEV|(% style="width:418px" %)(((
279 279  This command is used to configure the RS485/TTL devices; they won’t be used during sampling.
280 280  
281 -AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
334 +AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,
282 282  
283 -m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
284 -)))|AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
336 +mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
337 +)))|(% style="width:256px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
285 285  
286 -Detail of AT+CFGDEV command see [[AT+CFGDEV detail>>path:#AT_CFGDEV]].
339 +Detail of AT+CFGDEV command see [[AT+CFGDEV detail>>||anchor="HRS485DebugCommand28AT2BCFGDEV29"]].
287 287  
288 288  
342 +=== 3.3.3 Configure read commands for each sampling ===
289 289  
290 -
291 -
292 -1.
293 -11.
294 -111. Configure read commands for each sampling
295 -
344 +(((
296 296  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.
346 +)))
297 297  
298 -
348 +(((
299 299  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.
350 +)))
300 300  
301 -
352 +(((
302 302  To save the LoRaWAN network bandwidth, we might need to read data from different sensors and combine their valid value into a short payload.
354 +)))
303 303  
304 -
356 +(((
305 305  This section describes how to achieve above goals.
358 +)))
306 306  
307 -
360 +(((
308 308  During each sampling, the RS485-BL can support 15 commands to read sensors. And combine the return to one or several uplink payloads.
362 +)))
309 309  
310 -
364 +(((
311 311  **Command from RS485-BL to Sensor:**
366 +)))
312 312  
368 +(((
313 313  RS485-BL can send out pre-set max 15 strings via **AT+COMMAD1**, **ATCOMMAND2**,…, to **AT+COMMANDF** . All commands are of same grammar.
370 +)))
314 314  
315 -
372 +(((
316 316  **Handle return from sensors to RS485-BL**:
374 +)))
317 317  
376 +(((
318 318  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**
378 +)))
319 319  
380 +* (((
381 +**AT+DATACUT**
382 +)))
320 320  
321 -* **AT+DATACUT**
322 -
384 +(((
323 323  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.
386 +)))
324 324  
388 +* (((
389 +**AT+SEARCH**
390 +)))
325 325  
326 -* **AT+SEARCH**
327 -
392 +(((
328 328  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.
394 +)))
329 329  
330 -
396 +(((
331 331  **Define wait timeout:**
398 +)))
332 332  
400 +(((
333 333  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
402 +)))
334 334  
335 -
404 +(((
336 336  After we got the valid value from each RS485 commands, we need to combine them together with the command **AT+DATAUP**.
406 +)))
337 337  
338 -
339 339  **Examples:**
340 340  
341 341  Below are examples for the how above AT Commands works.
342 342  
343 -
344 344  **AT+COMMANDx : **This command will be sent to RS485/TTL devices during each sampling, Max command length is 14 bytes. The grammar is:
345 345  
346 -|(((
414 +(% border="1" class="table-bordered" style="background-color:#4f81bd; color:white; width:501px" %)
415 +|(% style="width:498px" %)(((
347 347  **AT+COMMANDx=xx xx xx xx xx xx xx xx xx xx xx xx,m**
348 348  
349 349  **xx xx xx xx xx xx xx xx xx xx xx xx: The RS485 command to be sent**
... ... @@ -355,41 +355,38 @@
355 355  
356 356  In the RS485-BL, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
357 357  
358 -
359 359  **AT+SEARCHx**: This command defines how to handle the return from AT+COMMANDx.
360 360  
361 -|(((
429 +(% border="1" class="table-bordered" style="background-color:#4f81bd; color:white; width:580px" %)
430 +|(% style="width:577px" %)(((
362 362  **AT+SEARCHx=aa,xx xx xx xx xx**
363 363  
364 364  * **aa: 1: prefix match mode; 2: prefix and suffix match mode**
365 365  * **xx xx xx xx xx: match string. Max 5 bytes for prefix and 5 bytes for suffix**
366 -
367 -
368 368  )))
369 369  
370 -Examples:
437 +**Examples:**
371 371  
372 -1. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
439 +1）For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
373 373  
374 374  If we set AT+SEARCH1=1,1E 56 34.      (max 5 bytes for prefix)
375 375  
376 -The valid data will be all bytes after 1E 56 34 , so it is 2e 30 58 5f 36 41 30 31 00 49
443 +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**
377 377  
378 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image013.png]]
445 +[[image:1653271044481-711.png]]
379 379  
447 +2）For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
380 380  
381 -1. For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
382 -
383 383  If we set AT+SEARCH1=2, 1E 56 34+31 00 49
384 384  
385 -Device will search the bytes between 1E 56 34 and 31 00 49. So it is 2e 30 58 5f 36 41 30
451 +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**
386 386  
387 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image014.png]]
453 +[[image:1653271276735-972.png]]
388 388  
389 -
390 390  **AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes.
391 391  
392 -|(((
457 +(% style="background-color:#4f81bd; color:white; width:729px" %)
458 +|(% style="width:726px" %)(((
393 393  **AT+DATACUTx=a,b,c**
394 394  
395 395  * **a: length for the return of AT+COMMAND**
... ... @@ -397,98 +397,143 @@
397 397  * **c: define the position for valid value.  **
398 398  )))
399 399  
400 -Examples:
466 +**Examples:**
401 401  
402 402  * Grab bytes:
403 403  
404 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image015.png]]
470 +[[image:1653271581490-837.png||height="313" width="722"]]
405 405  
472 +
406 406  * Grab a section.
407 407  
408 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image016.png]]
475 +[[image:1653271648378-342.png||height="326" width="720"]]
409 409  
477 +
410 410  * Grab different sections.
411 411  
412 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image017.png]]
480 +[[image:1653271657255-576.png||height="305" width="730"]]
413 413  
482 +(((
483 +(% style="color:red" %)**Note:**
484 +)))
414 414  
415 -Note:
416 -
486 +(((
417 417  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.
488 +)))
418 418  
419 -Example:
490 +(((
491 +**Example:**
492 +)))
420 420  
421 -AT+COMMAND1=11 01 1E D0,0
494 +(((
495 +(% style="color:red" %)AT+COMMAND1=11 01 1E D0,0
496 +)))
422 422  
423 -AT+SEARCH1=1,1E 56 34
498 +(((
499 +(% style="color:red" %)AT+SEARCH1=1,1E 56 34
500 +)))
424 424  
425 -AT+DATACUT1=0,2,1~~5
502 +(((
503 +(% style="color:red" %)AT+DATACUT1=0,2,1~~5
504 +)))
426 426  
427 -Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
506 +(((
507 +(% style="color:red" %)Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
508 +)))
428 428  
429 -String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
510 +(((
511 +(% style="color:red" %)String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
512 +)))
430 430  
431 -Valid payload after DataCUT command: 2e 30 58 5f 36
514 +(((
515 +(% style="color:red" %)Valid payload after DataCUT command: 2e 30 58 5f 36
516 +)))
432 432  
433 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image018.png]]
518 +[[image:1653271763403-806.png]]
434 434  
435 435  
521 +=== 3.3.4 Compose the uplink payload ===
436 436  
437 -
438 -1.
439 -11.
440 -111. Compose the uplink payload
441 -
523 +(((
442 442  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.**
525 +)))
443 443  
527 +(((
528 +(% style="color:#037691" %)**Examples: AT+DATAUP=0**
529 +)))
444 444  
445 -**Examples: AT+DATAUP=0**
531 +(((
532 +Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**A SIGNLE UPLINK**.
533 +)))
446 446  
447 -Compose the uplink payload with value returns in sequence and send with **A SIGNLE UPLINK**.
448 -
535 +(((
449 449  Final Payload is
537 +)))
450 450  
451 -Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx
539 +(((
540 +(% style="color:#4f81bd" %)**Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx**
541 +)))
452 452  
543 +(((
453 453  Where PAYVER is defined by AT+PAYVER, below is an example screen shot.
545 +)))
454 454  
455 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.png]]
547 +[[image:1653272787040-634.png||height="515" width="719"]]
456 456  
457 457  
458 458  
459 -**Examples: AT+DATAUP=1**
551 +(((
552 +(% style="color:#037691" %)**Examples: AT+DATAUP=1**
460 460  
461 -Compose the uplink payload with value returns in sequence and send with **Multiply UPLINKs**.
554 +
555 +)))
462 462  
557 +(((
558 +Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**Multiply UPLINKs**.
559 +)))
560 +
561 +(((
463 463  Final Payload is
563 +)))
464 464  
465 -Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA
565 +(((
566 +(% style="color:#4f81bd" %)**Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA**
567 +)))
466 466  
467 -1. Battery Info (2 bytes): Battery voltage
468 -1. PAYVER (1 byte): Defined by AT+PAYVER
469 -1. PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling.
470 -1. PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
471 -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
569 +1. (((
570 +Battery Info (2 bytes): Battery voltage
571 +)))
572 +1. (((
573 +PAYVER (1 byte): Defined by AT+PAYVER
574 +)))
575 +1. (((
576 +PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling.
577 +)))
578 +1. (((
579 +PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
580 +)))
581 +1. (((
582 +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
583 +)))
472 472  
473 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image020.png]]
585 +[[image:1653272817147-600.png||height="437" width="717"]]
474 474  
475 -
476 476  So totally there will be 3 uplinks for this sampling, each uplink includes 6 bytes DATA
477 477  
478 -DATA1=RETURN1 Valid Value = 20 20 0a 33 90 41
479 479  
480 -DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= 02 aa 05 81 0a 20
590 +DATA1=RETURN1 Valid Value = (% style="background-color:#4f81bd; color:white" %) 20 20 0a 33 90 41
481 481  
482 -DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 = 20 20 20 2d 30
592 +DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= (% style="background-color:#4f81bd; color:white" %)02 aa 05 81 0a 20
483 483  
594 +DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 =(% style="background-color:#4f81bd; color:white" %) 20 20 20 2d 30
484 484  
485 485  
486 486  Below are the uplink payloads:
487 487  
488 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.png]]
599 +[[image:1653272901032-107.png]]
489 489  
490 490  
491 -Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:
602 +(% style="color:red" %)Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:
492 492  
493 493   ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink ( so 51 -5 = 46 max valid date)
494 494  
... ... @@ -500,139 +500,186 @@
500 500  
501 501  
502 502  
503 -1.
504 -11.
505 -111. Uplink on demand
614 +=== 3.3.5 Uplink on demand ===
506 506  
616 +(((
507 507  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.
618 +)))
508 508  
620 +(((
509 509  Downlink control command:
622 +)))
510 510  
511 -[[0x08 command>>path:#downlink_08]]: Poll an uplink with current command set in RS485-BL.
624 +(((
625 +**0x08 command**: Poll an uplink with current command set in RS485-BL.
626 +)))
512 512  
513 -[[0xA8 command>>path:#downlink_A8]]: Send a command to RS485-BL and uplink the output from sensors.
628 +(((
629 +**0xA8 command**: Send a command to RS485-BL and uplink the output from sensors.
514 514  
631 +
632 +)))
515 515  
634 +=== 3.3.6 Uplink on Interrupt ===
516 516  
517 -1.
518 -11.
519 -111. Uplink on Interrupt
636 +Put the interrupt sensor between 3.3v_out and GPIO ext.
520 520  
521 -Put the interrupt sensor between 3.3v_out and GPIO ext.[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image022.png]]
638 +[[image:1653273818896-432.png]]
522 522  
640 +
641 +(((
523 523  AT+INTMOD=0  Disable Interrupt
643 +)))
524 524  
645 +(((
525 525  AT+INTMOD=1  Interrupt trigger by rising or falling edge.
647 +)))
526 526  
649 +(((
527 527  AT+INTMOD=2  Interrupt trigger by falling edge. ( Default Value)
651 +)))
528 528  
653 +(((
529 529  AT+INTMOD=3  Interrupt trigger by rising edge.
530 530  
656 +
657 +)))
531 531  
532 -1.
533 -11. Uplink Payload
659 +== 3.4 Uplink Payload ==
534 534  
535 -|**Size(bytes)**|**2**|**1**|**Length depends on the return from the commands**
536 -|Value|(((
661 +(% border="1" style="background-color:#4f81bd; color:white; width:850px" %)
662 +|**Size(bytes)**|(% style="width:130px" %)**2**|(% style="width:93px" %)**1**|(% style="width:509px" %)**Length depends on the return from the commands**
663 +|Value|(% style="width:130px" %)(((
664 +(((
537 537  Battery(mV)
666 +)))
538 538  
668 +(((
539 539  &
670 +)))
540 540  
672 +(((
541 541  Interrupt _Flag
542 -)))|(((
674 +)))
675 +)))|(% style="width:93px" %)(((
543 543  PAYLOAD_VER
544 544  
545 545  
546 -)))|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.
679 +)))|(% 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.
547 547  
548 548  Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors.
549 549  
683 +(((
684 +{{{function Decoder(bytes, port) {}}}
685 +)))
550 550  
551 -function Decoder(bytes, port) {
687 +(((
688 +{{{//Payload Formats of RS485-BL Deceive}}}
689 +)))
552 552  
553 -~/~/Payload Formats of RS485-BL Deceive
691 +(((
692 +{{{return {}}}
693 +)))
554 554  
555 -return {
695 +(((
696 +{{{ //Battery,units:V}}}
697 +)))
556 556  
557 - ~/~/Battery,units:V
699 +(((
700 +{{{ BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000,}}}
701 +)))
558 558  
559 - BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000,
703 +(((
704 +{{{ //GPIO_EXTI }}}
705 +)))
560 560  
561 - ~/~/GPIO_EXTI 
707 +(((
708 +{{{ EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE",}}}
709 +)))
562 562  
563 - EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE",
711 +(((
712 +{{{ //payload of version}}}
713 +)))
564 564  
565 - ~/~/payload of version
715 +(((
716 +{{{ Pay_ver:bytes[2],}}}
717 +)))
566 566  
567 - Pay_ver:bytes[2],
719 +(((
720 +{{{ }; }}}
721 +)))
568 568  
569 - };
723 +(((
724 +}
570 570  
571 - }
726 +
727 +)))
572 572  
573 -
574 -
575 -
576 -
577 -
578 -
729 +(((
579 579  TTN V3 uplink screen shot.
731 +)))
580 580  
581 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]
733 +[[image:1653274001211-372.png||height="192" width="732"]]
582 582  
583 -1.
584 -11. Configure RS485-BL via AT or Downlink
585 585  
586 -User can configure RS485-BL via [[AT Commands >>path:#_​Using_the_AT]]or LoRaWAN Downlink Commands
736 +== 3.5 Configure RS485-BL via AT or Downlink ==
587 587  
738 +User can configure RS485-BL via AT Commands or LoRaWAN Downlink Commands
739 +
588 588  There are two kinds of Commands:
589 589  
590 -* **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
742 +* (% 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]]
591 591  
592 -* **Sensor Related Commands**: These commands are special designed for RS485-BL.  User can see these commands below:
744 +* (% style="color:#4f81bd" %)**Sensor Related Commands**(%%): These commands are special designed for RS485-BL.  User can see these commands below:
593 593  
594 -1.
595 -11.
596 -111. Common Commands:
746 +=== 3.5.1 Common Commands: ===
597 597  
598 -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]]
748 +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]]
599 599  
600 600  
601 -1.
602 -11.
603 -111. Sensor related commands:
751 +=== 3.5.2 Sensor related commands: ===
604 604  
605 -==== Choose Device Type (RS485 or TTL) ====
753 +==== ====
606 606  
755 +==== **Choose Device Type (RS485 or TTL)** ====
756 +
607 607  RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect.
608 608  
609 -* AT Command
759 +* **AT Command**
610 610  
761 +(% class="box infomessage" %)
762 +(((
611 611  **AT+MOD=1** ~/~/ Set to support RS485-MODBUS type sensors. User can connect multiply RS485 , Modbus sensors to the A / B pins.
764 +)))
612 612  
766 +(% class="box infomessage" %)
767 +(((
613 613  **AT+MOD=2** ~/~/ Set to support TTL Level sensors, User can connect one TTL Sensor to the TXD/RXD/GND pins.
769 +)))
614 614  
615 615  
616 -* Downlink Payload
772 +* **Downlink Payload**
617 617  
618 -**0A aa**     à same as AT+MOD=aa
774 +**0A aa**  ~-~->  same as AT+MOD=aa
619 619  
620 620  
621 621  
622 -==== [[RS485 Debug Command>>path:#downlink_A8]] (AT+CFGDEV) ====
778 +==== **RS485 Debug Command (AT+CFGDEV)** ====
623 623  
624 624  This command is used to configure the RS485 or TTL sensors; they won’t be used during sampling.
625 625  
626 -* AT Command
782 +* **AT Command**
627 627  
628 -AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
784 +(% class="box infomessage" %)
785 +(((
786 +**AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m**
787 +)))
629 629  
630 630  m: 0: no CRC; 1: add CRC-16/MODBUS in the end of this command.
631 631  
632 632  
792 +* **Downlink Payload**
633 633  
634 -* Downlink Payload
635 -
636 636  Format: A8 MM NN XX XX XX XX YY
637 637  
638 638  Where:
... ... @@ -646,15 +646,15 @@
646 646  
647 647  To connect a Modbus Alarm with below commands.
648 648  
649 -* 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.
807 +* 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.
650 650  
651 -* 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.
809 +* 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.
652 652  
653 653  So if user want to use downlink command to control to RS485 Alarm, he can use:
654 654  
655 -**A8 01 06 0A 05 00 04 00 01 00**: to activate the RS485 Alarm
813 +(% style="color:#037691" %)**A8 01 06 0A 05 00 04 00 01 00**(%%): to activate the RS485 Alarm
656 656  
657 -**A8 01 06 0A 05 00 04 00 00 00**: to deactivate the RS485 Alarm
815 +(% style="color:#037691" %)**A8 01 06 0A 05 00 04 00 00 00**(%%): to deactivate the RS485 Alarm
658 658  
659 659  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.
660 660  
... ... @@ -663,48 +663,60 @@
663 663  
664 664  Check TTL Sensor return:
665 665  
666 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image024.png]]
824 +[[image:1654132684752-193.png]]
667 667  
668 668  
669 669  
828 +==== **Set Payload version** ====
670 670  
671 -==== Set Payload version ====
672 -
673 673  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.
674 674  
675 -* AT Command:
832 +* **AT Command:**
676 676  
677 -AT+PAYVER: Set PAYVER field = 1
834 +(% class="box infomessage" %)
835 +(((
836 +**AT+PAYVER: Set PAYVER field = 1**
837 +)))
678 678  
679 679  
680 -* Downlink Payload:
840 +* **Downlink Payload:**
681 681  
682 -0xAE 01   à Set PAYVER field =  0x01
842 +**0xAE 01**  ~-~-> Set PAYVER field =  0x01
683 683  
684 -0xAE 0F   à Set PAYVER field =  0x0F
844 +**0xAE 0F**   ~-~-> Set PAYVER field =  0x0F
685 685  
686 686  
687 -==== Set RS485 Sampling Commands ====
688 688  
848 +==== **Set RS485 Sampling Commands** ====
849 +
689 689  AT+COMMANDx, AT+DATACUTx and AT+SEARCHx
690 690  
691 -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]].
852 +These three commands are used to configure how the RS485-BL polling data from Modbus device. Detail of usage please see : [[polling RS485 device>>||anchor="H3.3.3Configurereadcommandsforeachsampling"]].
692 692  
693 693  
694 -* AT Command:
855 +* **AT Command:**
695 695  
696 -AT+COMMANDx: Configure RS485 read command to sensor.
857 +(% class="box infomessage" %)
858 +(((
859 +**AT+COMMANDx: Configure RS485 read command to sensor.**
860 +)))
697 697  
698 -AT+DATACUTx: Configure how to handle return from RS485 devices.
862 +(% class="box infomessage" %)
863 +(((
864 +**AT+DATACUTx: Configure how to handle return from RS485 devices.**
865 +)))
699 699  
700 -AT+SEARCHx: Configure search command
867 +(% class="box infomessage" %)
868 +(((
869 +**AT+SEARCHx: Configure search command**
870 +)))
701 701  
702 702  
703 -* Downlink Payload:
873 +* **Downlink Payload:**
704 704  
705 -0xAF downlink command can be used to set AT+COMMANDx or AT+DATACUTx.
875 +**0xAF** downlink command can be used to set AT+COMMANDx or AT+DATACUTx.
706 706  
707 -Note: if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink.
877 +(% style="color:red" %)**Note**(%%): if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink.
708 708  
709 709  Format: AF MM NN LL XX XX XX XX YY
710 710  
... ... @@ -711,23 +711,23 @@
711 711  Where:
712 712  
713 713  * MM: the ATCOMMAND or AT+DATACUT to be set. Value from 01 ~~ 0F,
714 -* NN: 0: no CRC; 1: add CRC-16/MODBUS ; 2: set the AT+DATACUT value.
715 -* LL: The length of AT+COMMAND or AT+DATACUT command
884 +* NN:  0: no CRC; 1: add CRC-16/MODBUS ; 2: set the AT+DATACUT value.
885 +* LL:  The length of AT+COMMAND or AT+DATACUT command
716 716  * XX XX XX XX: AT+COMMAND or AT+DATACUT command
717 -* 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.
887 +* 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.
718 718  
719 -Example:
889 +**Example:**
720 720  
721 -**AF 03 01 06 0A 05 00 04 00 01 00**: Same as AT+COMMAND3=0A 05 00 04 00 01,1
891 +(% style="color:#037691" %)**AF 03 01 06 0A 05 00 04 00 01 00**(%%): Same as AT+COMMAND3=0A 05 00 04 00 01,1
722 722  
723 -**AF 03 02 06 10 01 05 06 09 0A 00**: Same as AT+DATACUT3=**16**,**1**,**5+6+9+10**
893 +(% style="color:#037691" %)**AF 03 02 06**(% style="color:orange" %)** 10 **(% style="color:red" %)**01 **(% style="color:green" %)**05 06 09 0A**(% style="color:#037691" %)** 00**(%%): Same as AT+DATACUT3=(% style="color:orange" %)**16**(%%),(% style="color:red" %)**1**(%%),(% style="color:green" %)**5+6+9+10**
724 724  
725 -**AF 03 02 06 0B 02 05 07 08 0A 00**: Same as AT+DATACUT3=**11**,**2**,**5~~7+8~~10**
895 +(% style="color:#037691" %)**AF 03 02 06 **(% style="color:orange" %)**0B**(% style="color:red" %)** 02 **(% style="color:green" %)**05 07 08 0A **(% style="color:#037691" %)**00**(%%): Same as AT+DATACUT3=(% style="color:orange" %)**11**(%%),(% style="color:red" %)**2**(%%),(% style="color:green" %)**5~~7+8~~10**
726 726  
727 727  
728 -0xAB downlink command can be used for set AT+SEARCHx
898 +**0xAB** downlink command can be used for set AT+SEARCHx
729 729  
730 -Example: **AB aa 01 03 xx xx xx** (03 here means there are total 3 bytes after 03) So
900 +**Example:** **AB aa 01 03 xx xx xx** (03 here means there are total 3 bytes after 03) So
731 731  
732 732  * AB aa 01 03 xx xx xx  same as AT+SEARCHaa=1,xx xx xx
733 733  * 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
... ... @@ -735,145 +735,164 @@
735 735  **AB aa 02 03 xx xx xx 02 yy yy**  same as **AT+SEARCHaa=2,xx xx xx+yy yy**
736 736  
737 737  
738 -==== Fast command to handle MODBUS device ====
739 739  
909 +==== **Fast command to handle MODBUS device** ====
910 +
740 740  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]].
741 741  
742 742  This command is valid since v1.3 firmware version
743 743  
744 744  
745 -AT+MBFUN has only two value:
916 +**AT+MBFUN has only two value:**
746 746  
747 -* AT+MBFUN=1: Enable Modbus reading. And get response base on the MODBUS return
918 +* **AT+MBFUN=1**: Enable Modbus reading. And get response base on the MODBUS return
748 748  
749 749  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.
750 750  
751 -* AT+MBFUN=0: Disable Modbus fast reading.
922 +* **AT+MBFUN=0**: Disable Modbus fast reading.
752 752  
753 -Example:
924 +**Example:**
754 754  
755 755  * AT+MBFUN=1 and AT+DATACUT1/AT+DATACUT2 are not configure (0,0,0).
756 756  * 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.
757 757  * 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.
758 758  
759 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image025.png]]
930 +[[image:1654133913295-597.png]]
760 760  
761 761  
762 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image026.png]]
933 +[[image:1654133954153-643.png]]
763 763  
764 764  
765 -* Downlink Commands:
936 +* **Downlink Commands:**
766 766  
767 -A9 aa -à Same as AT+MBFUN=aa
938 +**A9 aa** ~-~-> Same as AT+MBFUN=aa
768 768  
769 769  
770 -==== RS485 command timeout ====
771 771  
942 +==== **RS485 command timeout** ====
943 +
772 772  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.
773 773  
774 774  Default value: 0, range:  0 ~~ 5 seconds
775 775  
776 776  
777 -* AT Command:
949 +* **AT Command:**
778 778  
779 -AT+CMDDLaa=hex(bb cc)
951 +(% class="box infomessage" %)
952 +(((
953 +**AT+CMDDLaa=hex(bb cc)**
954 +)))
780 780  
781 -Example:
956 +**Example:**
782 782  
783 783  **AT+CMDDL1=1000** to send the open time to 1000ms
784 784  
785 785  
786 -* Downlink Payload:
961 +* **Downlink Payload:**
787 787  
788 788  0x AA aa bb cc
789 789  
790 790  Same as: AT+CMDDLaa=hex(bb cc)
791 791  
792 - Example:
967 + **Example:**
793 793  
794 - 0xAA 01 03 E8  à Same as **AT+CMDDL1=1000 ms**
969 + **0xAA 01 03 E8**  ~-~-> Same as **AT+CMDDL1=1000 ms**
795 795  
796 796  
797 -==== [[Uplink>>path:#downlink_A8]] payload mode ====
798 798  
973 +==== **Uplink payload mode** ====
974 +
799 799  Define to use one uplink or multiple uplinks for the sampling.
800 800  
801 -The use of this command please see: [[Compose Uplink payload>>path:#DataUP]]
977 +The use of this command please see: [[Compose Uplink payload>>||anchor="H3.3.4Composetheuplinkpayload"]]
802 802  
803 -* AT Command:
979 +* **AT Command:**
804 804  
805 -AT+DATAUP=0
981 +(% class="box infomessage" %)
982 +(((
983 +**AT+DATAUP=0**
984 +)))
806 806  
807 -AT+DATAUP=1
986 +(% class="box infomessage" %)
987 +(((
988 +**AT+DATAUP=1**
989 +)))
808 808  
809 809  
810 -* Downlink Payload:
992 +* **Downlink Payload:**
811 811  
812 -0xAD 00   à Same as AT+DATAUP=0
994 +**0xAD 00**  **~-~->** Same as AT+DATAUP=0
813 813  
814 -0xAD 01   à Same as AT+DATAUP=1
996 +**0xAD 01**  **~-~->** Same as AT+DATAUP=1
815 815  
816 816  
817 -==== Manually trigger an Uplink ====
818 818  
1000 +==== **Manually trigger an Uplink** ====
1001 +
819 819  Ask device to send an uplink immediately.
820 820  
821 -* Downlink Payload:
1004 +* **Downlink Payload:**
822 822  
823 -0x08 FF, RS485-BL will immediately send an uplink.
1006 +**0x08 FF**, RS485-BL will immediately send an uplink.
824 824  
825 825  
826 -==== Clear RS485 Command ====
827 827  
1010 +==== **Clear RS485 Command** ====
1011 +
828 828  The AT+COMMANDx and AT+DATACUTx settings are stored in special location, user can use below command to clear them.
829 829  
830 830  
831 -* AT Command:
1015 +* **AT Command:**
832 832  
833 -**AT+CMDEAR=mm,nn**   mm: start position of erase ,nn: stop position of erase
1017 +(% style="color:#037691" %)**AT+CMDEAR=mm,nn** (%%) mm: start position of erase ,nn: stop position of erase Etc. AT+CMDEAR=1,10 means erase AT+COMMAND1/AT+DATACUT1 to AT+COMMAND10/AT+DATACUT10
834 834  
835 -Etc. AT+CMDEAR=1,10 means erase AT+COMMAND1/AT+DATACUT1 to AT+COMMAND10/AT+DATACUT10
836 -
837 837  Example screen shot after clear all RS485 commands. 
838 838  
839 839  
840 -
841 841  The uplink screen shot is:
842 842  
843 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]
1024 +[[image:1654134704555-320.png]]
844 844  
845 845  
846 -* Downlink Payload:
1027 +* **Downlink Payload:**
847 847  
848 -0x09 aa bb same as AT+CMDEAR=aa,bb
1029 +**0x09 aa bb** same as AT+CMDEAR=aa,bb
849 849  
850 850  
851 -==== Set Serial Communication Parameters ====
852 852  
1033 +==== **Set Serial Communication Parameters** ====
1034 +
853 853  Set the Rs485 serial communication parameters:
854 854  
855 -* AT Command:
1037 +* **AT Command:**
856 856  
857 857  Set Baud Rate:
858 858  
859 -AT+BAUDR=9600    ~/~/ Options: (1200,2400,4800,14400,19200,115200)
1041 +(% class="box infomessage" %)
1042 +(((
1043 +**AT+BAUDR=9600**    ~/~/ Options: (1200,2400,4800,14400,19200,115200)
1044 +)))
860 860  
1046 +Set UART Parity
861 861  
862 -Set UART parity
1048 +(% class="box infomessage" %)
1049 +(((
1050 +**AT+PARITY=0**    ~/~/ Option: 0: no parity, 1: odd parity, 2: even parity
1051 +)))
863 863  
864 -AT+PARITY=0    ~/~/ Option: 0: no parity, 1: odd parity, 2: even parity
865 -
866 -
867 867  Set STOPBIT
868 868  
869 -AT+STOPBIT=0    ~/~/ Option: 0 for 1bit; 1 for 1.5 bit ; 2 for 2 bits
1055 +(% class="box infomessage" %)
1056 +(((
1057 +**AT+STOPBIT=0**    ~/~/ Option: 0 for 1bit; 1 for 1.5 bit ; 2 for 2 bits
1058 +)))
870 870  
871 871  
872 -* Downlink Payload:
1061 +* **Downlink Payload:**
873 873  
874 -A7 01 aa bb: Same  AT+BAUDR=hex(aa bb)*100
1063 +**A7 01 aa bb**: Same  AT+BAUDR=hex(aa bb)*100
875 875  
876 -Example:
1065 +**Example:**
877 877  
878 878  * A7 01 00 60   same as AT+BAUDR=9600
879 879  * A7 01 04 80  same as AT+BAUDR=115200
... ... @@ -883,108 +883,102 @@
883 883  A7 03 aa: Same as  AT+STOPBIT=aa  (aa value: 00 , 01 or 02)
884 884  
885 885  
886 -==== Control output power duration ====
887 887  
1076 +==== **Control output power duration** ====
1077 +
888 888  User can set the output power duration before each sampling.
889 889  
890 -* AT Command:
1080 +* **AT Command:**
891 891  
892 -Example:
1082 +**Example:**
893 893  
894 -AT+3V3T=1000 ~/~/ 3V3 output power will open 1s before each sampling.
1084 +**AT+3V3T=1000**  ~/~/ 3V3 output power will open 1s before each sampling.
895 895  
896 -AT+5VT=1000 ~/~/ +5V output power will open 1s before each sampling.
1086 +**AT+5VT=1000**  ~/~/ +5V output power will open 1s before each sampling.
897 897  
898 898  
899 -* LoRaWAN Downlink Command:
1089 +* **LoRaWAN Downlink Command:**
900 900  
901 -07 01 aa bb  Same as AT+5VT=(aa bb)
1091 +**07 01 aa bb**  Same as AT+5VT=(aa bb)
902 902  
903 -07 02 aa bb  Same as AT+3V3T=(aa bb)
1093 +**07 02 aa bb**  Same as AT+3V3T=(aa bb)
904 904  
905 905  
1096 +== 3.6 Buttons ==
906 906  
1098 +(% border="1" style="background-color:#ffffcc; color:green; width:233px" %)
1099 +|=(% style="width: 89px;" %)**Button**|=(% style="width: 141px;" %)**Feature**
1100 +|(% style="width:89px" %)**RST**|(% style="width:141px" %)Reboot RS485-BL
907 907  
908 -1.
909 -11. Buttons
1102 +== 3.7 +3V3 Output ==
910 910  
911 -|**Button**|**Feature**
912 -|**RST**|Reboot RS485-BL
913 -
914 -1.
915 -11. +3V3 Output
916 -
917 917  RS485-BL has a Controllable +3V3 output, user can use this output to power external sensor.
918 918  
919 919  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. 
920 920  
921 -
922 922  The +3V3 output time can be controlled by AT Command.
923 923  
924 -**AT+3V3T=1000**
925 925  
926 -Means set +3v3 valid time to have 1000ms. So, the real +3v3 output will actually have 1000ms + sampling time for other sensors.
1111 +(% style="color:#037691" %)**AT+3V3T=1000**
927 927  
928 928  
1114 +Means set +3v3 valid time to have 1000ms. So, the real +3v3 output will actually have 1000ms + sampling time for other sensors.
1115 +
929 929  By default, the AT+3V3T=0. This is a special case, means the +3V3 output is always on at any time
930 930  
931 931  
932 -1.
933 -11. +5V Output
1119 +== 3.8 +5V Output ==
934 934  
935 935  RS485-BL has a Controllable +5V output, user can use this output to power external sensor.
936 936  
937 937  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. 
938 938  
939 -
940 940  The 5V output time can be controlled by AT Command.
941 941  
942 -**AT+5VT=1000**
943 943  
944 -Means set 5V valid time to have 1000ms. So, the real 5V output will actually have 1000ms + sampling time for other sensors.
1128 +(% style="color:#037691" %)**AT+5VT=1000**
945 945  
946 946  
1131 +Means set 5V valid time to have 1000ms. So, the real 5V output will actually have 1000ms + sampling time for other sensors.
1132 +
947 947  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.
948 948  
949 949  
1136 +== 3.9 LEDs ==
950 950  
1138 +(% border="1" style="background-color:#ffffcc; color:green; width:332px" %)
1139 +|=**LEDs**|=(% style="width: 274px;" %)**Feature**
1140 +|**LED1**|(% style="width:274px" %)Blink when device transmit a packet.
951 951  
952 -1.
953 -11. LEDs
1142 +== 3.10 Switch Jumper ==
954 954  
955 -|**LEDs**|**Feature**
956 -|**LED1**|Blink when device transmit a packet.
957 -
958 -1.
959 -11. Switch Jumper
960 -
961 -|**Switch Jumper**|**Feature**
962 -|**SW1**|(((
1144 +(% border="1" style="background-color:#ffffcc; color:green; width:515px" %)
1145 +|=(% style="width: 124px;" %)**Switch Jumper**|=(% style="width: 388px;" %)**Feature**
1146 +|(% style="width:124px" %)**SW1**|(% style="width:388px" %)(((
963 963  ISP position: Upgrade firmware via UART
964 964  
965 965  Flash position: Configure device, check running status.
966 966  )))
967 -|**SW2**|(((
1151 +|(% style="width:124px" %)**SW2**|(% style="width:388px" %)(((
968 968  5V position: set to compatible with 5v I/O.
969 969  
970 970  3.3v position: set to compatible with 3.3v I/O.,
971 971  )))
972 972  
973 -+3.3V: is always ON
1157 +**+3.3V**: is always ON
974 974  
975 -+5V: Only open before every sampling. The time is by default, it is AT+5VT=0.  Max open time. 5000 ms.
1159 +**+5V**: Only open before every sampling. The time is by default, it is AT+5VT=0.  Max open time. 5000 ms.
976 976  
977 -1. Case Study
978 978  
979 -User can check this URL for some case studies.
1162 += 4. Case Study =
980 980  
981 -[[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]]
1164 +User can check this URL for some case studies: [[APP RS485 COMMUNICATE WITH SENSORS>>doc:Main.Application Note \: Communicate with Different Sensors ----- RS485-LN RS485-BL.WebHome]]
982 982  
983 983  
984 984  
1168 += 5. Use AT Command =
985 985  
986 -1. Use AT Command
987 -11. Access AT Command
1170 +== 5.1 Access AT Command ==
988 988  
989 989  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.
990 990  
... ... @@ -1001,7 +1001,7 @@
1001 1001  
1002 1002  
1003 1003  
1004 -1.
1187 +1.
1005 1005  11. Common AT Command Sequence
1006 1006  111. Multi-channel ABP mode (Use with SX1301/LG308)
1007 1007  
... ... @@ -1020,8 +1020,8 @@
1020 1020  
1021 1021  ATZ
1022 1022  
1023 -1.
1024 -11.
1206 +1.
1207 +11.
1025 1025  111. Single-channel ABP mode (Use with LG01/LG02)
1026 1026  
1027 1027  AT+FDR   Reset Parameters to Factory Default, Keys Reserve
... ... @@ -1096,7 +1096,7 @@
1096 1096  [[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]]
1097 1097  
1098 1098  
1099 -1.
1282 +1.
1100 1100  11. How to change the LoRa Frequency Bands/Region?
1101 1101  
1102 1102  User can follow the introduction for [[how to upgrade image>>path:#upgrade_image]]. When download the images, choose the required image file for download.
... ... @@ -1103,7 +1103,7 @@
1103 1103  
1104 1104  
1105 1105  
1106 -1.
1289 +1.
1107 1107  11. How many RS485-Slave can RS485-BL connects?
1108 1108  
1109 1109  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]].
... ... @@ -1120,7 +1120,7 @@
1120 1120  
1121 1121  
1122 1122  
1123 -1.
1306 +1.
1124 1124  11. Why I can’t join TTN V3 in US915 /AU915 bands?
1125 1125  
1126 1126  It might about the channels mapping. Please see for detail.
1652954654347-831.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +138.7 KB
Content
1653271044481-711.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +27.8 KB
Content
1653271276735-972.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +26.6 KB
Content
1653271581490-837.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +138.7 KB
Content
1653271648378-342.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +131.4 KB
Content
1653271657255-576.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +142.6 KB
Content
1653271763403-806.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +27.7 KB
Content
1653272787040-634.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +294.0 KB
Content
1653272817147-600.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +143.3 KB
Content
1653272901032-107.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +197.8 KB
Content
1653273818896-432.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +31.6 KB
Content
1653274001211-372.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +91.4 KB
Content
1654132684752-193.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +22.8 KB
Content
1654133913295-597.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +116.2 KB
Content
1654133954153-643.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +91.2 KB
Content
1654134704555-320.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +91.4 KB
Content
1654135840598-282.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +1.3 MB
Content