Skip to Content
Last modified by Xiaoling on 2025/04/23 15:57
From version 40.18
edited by Xiaoling
on 2022/06/06 09:38
Change comment: There is no comment for this version
To version 14.1
edited by Xiaoling
on 2022/05/19 17:45
Change comment: Uploaded new attachment "1652953553383-907.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,6 +65,8 @@
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 70  **Interface for Model:**
... ... @@ -94,8 +94,6 @@
94 94  * 127 dB Dynamic Range RSSI.
95 95  * Automatic RF Sense and CAD with ultra-fast AFC. ​​​
96 96  
97 -
98 -
99 99  == 1.3 Features ==
100 100  
101 101  * LoRaWAN Class A & Class C protocol (default Class A)
... ... @@ -107,8 +107,6 @@
107 107  * Support Modbus protocol
108 108  * Support Interrupt uplink
109 109  
110 -
111 -
112 112  == 1.4 Applications ==
113 113  
114 114  * Smart Buildings & Home Automation
... ... @@ -118,18 +118,13 @@
118 118  * Smart Cities
119 119  * Smart Factory
120 120  
121 -
122 -
123 123  == 1.5 Firmware Change log ==
124 124  
125 125  [[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);"]]
126 126  
127 -
128 128  == 1.6 Hardware Change log ==
129 129  
130 130  (((
131 -
132 -
133 133  v1.4
134 134  )))
135 135  
... ... @@ -153,8 +153,6 @@
153 153  
154 154  (((
155 155  Release version ​​​​​
156 -
157 -
158 158  )))
159 159  
160 160  = 2. Pin mapping and Power ON Device =
... ... @@ -168,7 +168,6 @@
168 168  
169 169  The Left TXD and RXD are TTL interface for external sensor. TTL level is controlled by 3.3/5v Jumper.
170 170  
171 -
172 172  = 3. Operation Mode =
173 173  
174 174  == 3.1 How it works? ==
... ... @@ -175,8 +175,6 @@
175 175  
176 176  (((
177 177  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.
178 -
179 -
180 180  )))
181 181  
182 182  == 3.2 Example to join LoRaWAN network ==
... ... @@ -185,242 +185,204 @@
185 185  
186 186  [[image:1652953414711-647.png||height="337" width="723"]]
187 187  
188 -(((
170 +
189 189  The RS485-BL in this example connected to two RS485 devices for demonstration, user can connect to other RS485 devices via the same method.
190 -)))
191 191  
192 -(((
173 +
193 193  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:
194 -)))
195 195  
196 -(((
197 197  **Step 1**: Create a device in TTN V3 with the OTAA keys from RS485-BL.
198 -)))
199 199  
200 -(((
201 201  Each RS485-BL is shipped with a sticker with unique device EUI:
202 -)))
203 203  
204 -[[image:1652953462722-299.png]]
180 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image005.png]]
205 205  
206 -(((
182 +
183 +
184 +
207 207  User can enter this key in their LoRaWAN Server portal. Below is TTN V3 screen shot:
208 -)))
209 209  
210 -(((
211 211  Add APP EUI in the application.
212 -)))
213 213  
189 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image006.png]]
214 214  
215 -[[image:image-20220519174512-1.png]]
191 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image007.png]]
216 216  
217 -[[image:image-20220519174512-2.png||height="328" width="731"]]
193 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image008.png]]
218 218  
219 -[[image:image-20220519174512-3.png||height="556" width="724"]]
195 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image009.png]]
220 220  
221 -[[image:image-20220519174512-4.png]]
222 222  
198 +
199 +
200 +
201 +
202 +
203 +
204 +
205 +
206 +
207 +
208 +
209 +
210 +
211 +
212 +
223 223  You can also choose to create the device manually.
224 224  
225 -[[image:1652953542269-423.png||height="710" width="723"]]
215 +|(((
216 +
217 +)))
226 226  
219 +
220 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image010.png]]
221 +
227 227  Add APP KEY and DEV EUI
228 228  
229 -[[image:1652953553383-907.png||height="514" width="724"]]
224 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image011.png]]
230 230  
231 231  
232 -(((
233 233  **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.
234 -)))
235 235  
236 -[[image:1652953568895-172.png||height="232" width="724"]]
229 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image012.png]]
237 237  
238 238  
239 -== 3.3 Configure Commands to read data ==
240 240  
241 -(((
242 -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.
243 243  
244 -
245 -)))
234 +1.
235 +11. Configure Commands to read data
246 246  
247 -=== 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.
248 248  
239 +
240 +1.
241 +11.
242 +111. Configure UART settings for RS485 or TTL communication
243 +
249 249  RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect.
250 250  
251 -**~1. RS485-MODBUS mode:**
246 +1. RS485-MODBUS mode:
252 252  
253 253  AT+MOD=1 ~/~/ Support RS485-MODBUS type sensors. User can connect multiply RS485 , Modbus sensors to the A / B pins.
254 254  
255 -**2. TTL mode:**
256 256  
251 +1. TTL mode:
252 +
257 257  AT+MOD=2 ~/~/ Support TTL Level sensors, User can connect one TTL Sensor to the TXD/RXD/GND pins.
258 258  
255 +
259 259  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.
260 260  
261 -(% border="1" style="background-color:#ffffcc; color:green; width:795px" %)
262 -|(((
263 -**AT Commands**
264 -)))|(% style="width:285px" %)(((
265 -**Description**
266 -)))|(% style="width:347px" %)(((
267 -**Example**
268 -)))
269 -|(((
270 -AT+BAUDR
271 -)))|(% style="width:285px" %)(((
272 -Set the baud rate (for RS485 connection). Default Value is: 9600.
273 -)))|(% style="width:347px" %)(((
274 -(((
258 +
259 +|**AT Commands**|**Description**|**Example**
260 +|AT+BAUDR|Set the baud rate (for RS485 connection). Default Value is: 9600.|(((
275 275  AT+BAUDR=9600
276 -)))
277 277  
278 -(((
279 279  Options: (1200,2400,4800,14400,19200,115200)
280 280  )))
281 -)))
282 -|(((
283 -AT+PARITY
284 -)))|(% style="width:285px" %)(((
285 -(((
265 +|AT+PARITY|(((
286 286  Set UART parity (for RS485 connection)
287 -)))
288 288  
289 -(((
290 290  Default Value is: no parity.
291 -)))
292 -)))|(% style="width:347px" %)(((
293 -(((
269 +)))|(((
294 294  AT+PARITY=0
295 -)))
296 296  
297 -(((
298 298  Option: 0: no parity, 1: odd parity, 2: even parity
299 299  )))
300 -)))
301 -|(((
302 -AT+STOPBIT
303 -)))|(% style="width:285px" %)(((
304 -(((
274 +|AT+STOPBIT|(((
305 305  Set serial stopbit (for RS485 connection)
306 -)))
307 307  
308 -(((
309 309  Default Value is: 1bit.
310 -)))
311 -)))|(% style="width:347px" %)(((
312 -(((
278 +)))|(((
313 313  AT+STOPBIT=0 for 1bit
314 -)))
315 315  
316 -(((
317 317  AT+STOPBIT=1 for 1.5 bit
318 -)))
319 319  
320 -(((
321 321  AT+STOPBIT=2 for 2 bits
322 322  )))
323 -)))
324 324  
325 325  
326 326  
327 -=== 3.3.2 Configure sensors ===
328 328  
329 -(((
330 -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**.
331 -)))
289 +1.
290 +11.
291 +111. Configure sensors
332 332  
333 -(((
334 -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.
335 -)))
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.
336 336  
337 -(% border="1" style="background-color:#ffffcc; color:green; width:806px" %)
338 -|**AT Commands**|(% style="width:418px" %)**Description**|(% style="width:256px" %)**Example**
339 -|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|(((
340 340  This command is used to configure the RS485/TTL devices; they won’t be used during sampling.
341 341  
342 -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
343 343  
344 -mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
345 -)))|(% 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
346 346  
347 -Detail of AT+CFGDEV command see [[AT+CFGDEV detail>>||anchor="HRS485DebugCommand28AT2BCFGDEV29"]].
307 +Detail of AT+CFGDEV command see [[AT+CFGDEV detail>>path:#AT_CFGDEV]].
348 348  
349 349  
350 -=== 3.3.3 Configure read commands for each sampling ===
351 351  
352 -(((
311 +
312 +
313 +1.
314 +11.
315 +111. Configure read commands for each sampling
316 +
353 353  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.
354 -)))
355 355  
356 -(((
319 +
357 357  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.
358 -)))
359 359  
360 -(((
322 +
361 361  To save the LoRaWAN network bandwidth, we might need to read data from different sensors and combine their valid value into a short payload.
362 -)))
363 363  
364 -(((
325 +
365 365  This section describes how to achieve above goals.
366 -)))
367 367  
368 -(((
328 +
369 369  During each sampling, the RS485-BL can support 15 commands to read sensors. And combine the return to one or several uplink payloads.
370 -)))
371 371  
372 -(((
331 +
373 373  **Command from RS485-BL to Sensor:**
374 -)))
375 375  
376 -(((
377 377  RS485-BL can send out pre-set max 15 strings via **AT+COMMAD1**, **ATCOMMAND2**,…, to **AT+COMMANDF** . All commands are of same grammar.
378 -)))
379 379  
380 -(((
336 +
381 381  **Handle return from sensors to RS485-BL**:
382 -)))
383 383  
384 -(((
385 385  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**
386 -)))
387 387  
388 -* (((
389 -**AT+DATACUT**
390 -)))
391 391  
392 -(((
342 +* **AT+DATACUT**
343 +
393 393  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.
394 -)))
395 395  
396 -* (((
397 -**AT+SEARCH**
398 -)))
399 399  
400 -(((
347 +* **AT+SEARCH**
348 +
401 401  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.
402 -)))
403 403  
404 -(((
351 +
405 405  **Define wait timeout:**
406 -)))
407 407  
408 -(((
409 409  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
410 -)))
411 411  
412 -(((
356 +
413 413  After we got the valid value from each RS485 commands, we need to combine them together with the command **AT+DATAUP**.
414 -)))
415 415  
359 +
416 416  **Examples:**
417 417  
418 418  Below are examples for the how above AT Commands works.
419 419  
364 +
420 420  **AT+COMMANDx : **This command will be sent to RS485/TTL devices during each sampling, Max command length is 14 bytes. The grammar is:
421 421  
422 -(% border="1" class="table-bordered" style="background-color:#4f81bd; color:white; width:501px" %)
423 -|(% style="width:498px" %)(((
367 +|(((
424 424  **AT+COMMANDx=xx xx xx xx xx xx xx xx xx xx xx xx,m**
425 425  
426 426  **xx xx xx xx xx xx xx xx xx xx xx xx: The RS485 command to be sent**
... ... @@ -432,38 +432,41 @@
432 432  
433 433  In the RS485-BL, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
434 434  
379 +
435 435  **AT+SEARCHx**: This command defines how to handle the return from AT+COMMANDx.
436 436  
437 -(% border="1" class="table-bordered" style="background-color:#4f81bd; color:white; width:580px" %)
438 -|(% style="width:577px" %)(((
382 +|(((
439 439  **AT+SEARCHx=aa,xx xx xx xx xx**
440 440  
441 441  * **aa: 1: prefix match mode; 2: prefix and suffix match mode**
442 442  * **xx xx xx xx xx: match string. Max 5 bytes for prefix and 5 bytes for suffix**
387 +
388 +
443 443  )))
444 444  
445 -**Examples:**
391 +Examples:
446 446  
447 -1）For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
393 +1. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
448 448  
449 449  If we set AT+SEARCH1=1,1E 56 34.      (max 5 bytes for prefix)
450 450  
451 -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
452 452  
453 -[[image:1653271044481-711.png]]
399 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image013.png]]
454 454  
455 -2）For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
456 456  
402 +1. For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
403 +
457 457  If we set AT+SEARCH1=2, 1E 56 34+31 00 49
458 458  
459 -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
460 460  
461 -[[image:1653271276735-972.png]]
408 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image014.png]]
462 462  
410 +
463 463  **AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes.
464 464  
465 -(% style="background-color:#4f81bd; color:white; width:729px" %)
466 -|(% style="width:726px" %)(((
413 +|(((
467 467  **AT+DATACUTx=a,b,c**
468 468  
469 469  * **a: length for the return of AT+COMMAND**
... ... @@ -471,143 +471,98 @@
471 471  * **c: define the position for valid value.  **
472 472  )))
473 473  
474 -**Examples:**
421 +Examples:
475 475  
476 476  * Grab bytes:
477 477  
478 -[[image:1653271581490-837.png||height="313" width="722"]]
425 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image015.png]]
479 479  
480 -
481 481  * Grab a section.
482 482  
483 -[[image:1653271648378-342.png||height="326" width="720"]]
429 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image016.png]]
484 484  
485 -
486 486  * Grab different sections.
487 487  
488 -[[image:1653271657255-576.png||height="305" width="730"]]
433 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image017.png]]
489 489  
490 -(((
491 -(% style="color:red" %)**Note:**
492 -)))
493 493  
494 -(((
436 +Note:
437 +
495 495  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.
496 -)))
497 497  
498 -(((
499 -**Example:**
500 -)))
440 +Example:
501 501  
502 -(((
503 -(% style="color:red" %)AT+COMMAND1=11 01 1E D0,0
504 -)))
442 +AT+COMMAND1=11 01 1E D0,0
505 505  
506 -(((
507 -(% style="color:red" %)AT+SEARCH1=1,1E 56 34
508 -)))
444 +AT+SEARCH1=1,1E 56 34
509 509  
510 -(((
511 -(% style="color:red" %)AT+DATACUT1=0,2,1~~5
512 -)))
446 +AT+DATACUT1=0,2,1~~5
513 513  
514 -(((
515 -(% style="color:red" %)Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
516 -)))
448 +Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
517 517  
518 -(((
519 -(% style="color:red" %)String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
520 -)))
450 +String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
521 521  
522 -(((
523 -(% style="color:red" %)Valid payload after DataCUT command: 2e 30 58 5f 36
524 -)))
452 +Valid payload after DataCUT command: 2e 30 58 5f 36
525 525  
526 -[[image:1653271763403-806.png]]
454 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image018.png]]
527 527  
528 528  
529 -=== 3.3.4 Compose the uplink payload ===
530 530  
531 -(((
458 +
459 +1.
460 +11.
461 +111. Compose the uplink payload
462 +
532 532  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.**
533 -)))
534 534  
535 -(((
536 -(% style="color:#037691" %)**Examples: AT+DATAUP=0**
537 -)))
538 538  
539 -(((
540 -Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**A SIGNLE UPLINK**.
541 -)))
466 +**Examples: AT+DATAUP=0**
542 542  
543 -(((
468 +Compose the uplink payload with value returns in sequence and send with **A SIGNLE UPLINK**.
469 +
544 544  Final Payload is
545 -)))
546 546  
547 -(((
548 -(% style="color:#4f81bd" %)**Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx**
549 -)))
472 +Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx
550 550  
551 -(((
552 552  Where PAYVER is defined by AT+PAYVER, below is an example screen shot.
553 -)))
554 554  
555 -[[image:1653272787040-634.png||height="515" width="719"]]
476 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.png]]
556 556  
557 557  
558 558  
559 -(((
560 -(% style="color:#037691" %)**Examples: AT+DATAUP=1**
480 +**Examples: AT+DATAUP=1**
561 561  
562 -
563 -)))
482 +Compose the uplink payload with value returns in sequence and send with **Multiply UPLINKs**.
564 564  
565 -(((
566 -Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**Multiply UPLINKs**.
567 -)))
568 -
569 -(((
570 570  Final Payload is
571 -)))
572 572  
573 -(((
574 -(% style="color:#4f81bd" %)**Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA**
575 -)))
486 +Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA
576 576  
577 -1. (((
578 -Battery Info (2 bytes): Battery voltage
579 -)))
580 -1. (((
581 -PAYVER (1 byte): Defined by AT+PAYVER
582 -)))
583 -1. (((
584 -PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling.
585 -)))
586 -1. (((
587 -PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
588 -)))
589 -1. (((
590 -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
591 -)))
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
592 592  
593 -[[image:1653272817147-600.png||height="437" width="717"]]
494 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image020.png]]
594 594  
496 +
595 595  So totally there will be 3 uplinks for this sampling, each uplink includes 6 bytes DATA
596 596  
499 +DATA1=RETURN1 Valid Value = 20 20 0a 33 90 41
597 597  
598 -DATA1=RETURN1 Valid Value = (% style="background-color:#4f81bd; color:white" %) 20 20 0a 33 90 41
501 +DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= 02 aa 05 81 0a 20
599 599  
600 -DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= (% style="background-color:#4f81bd; color:white" %)02 aa 05 81 0a 20
503 +DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 = 20 20 20 2d 30
601 601  
602 -DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 =(% style="background-color:#4f81bd; color:white" %) 20 20 20 2d 30
603 603  
604 604  
605 605  Below are the uplink payloads:
606 606  
607 -[[image:1653272901032-107.png]]
509 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.png]]
608 608  
609 609  
610 -(% style="color:red" %)Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:
512 +Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:
611 611  
612 612   ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink ( so 51 -5 = 46 max valid date)
613 613  
... ... @@ -619,187 +619,139 @@
619 619  
620 620  
621 621  
622 -=== 3.3.5 Uplink on demand ===
524 +1.
525 +11.
526 +111. Uplink on demand
623 623  
624 -(((
625 625  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.
626 -)))
627 627  
628 -(((
629 629  Downlink control command:
630 -)))
631 631  
632 -(((
633 -**0x08 command**: Poll an uplink with current command set in RS485-BL.
634 -)))
532 +[[0x08 command>>path:#downlink_08]]: Poll an uplink with current command set in RS485-BL.
635 635  
636 -(((
637 -**0xA8 command**: Send a command to RS485-BL and uplink the output from sensors.
534 +[[0xA8 command>>path:#downlink_A8]]: Send a command to RS485-BL and uplink the output from sensors.
638 638  
639 -
640 -)))
641 641  
642 -=== 3.3.6 Uplink on Interrupt ===
643 643  
644 -Put the interrupt sensor between 3.3v_out and GPIO ext.
538 +1.
539 +11.
540 +111. Uplink on Interrupt
645 645  
646 -[[image:1653273818896-432.png]]
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]]
647 647  
648 -
649 -(((
650 650  AT+INTMOD=0  Disable Interrupt
651 -)))
652 652  
653 -(((
654 654  AT+INTMOD=1  Interrupt trigger by rising or falling edge.
655 -)))
656 656  
657 -(((
658 658  AT+INTMOD=2  Interrupt trigger by falling edge. ( Default Value)
659 -)))
660 660  
661 -(((
662 662  AT+INTMOD=3  Interrupt trigger by rising edge.
663 663  
664 -
665 -)))
666 666  
667 -== 3.4 Uplink Payload ==
553 +1.
554 +11. Uplink Payload
668 668  
669 -(% border="1" style="background-color:#4f81bd; color:white; width:850px" %)
670 -|**Size(bytes)**|(% style="width:130px" %)**2**|(% style="width:93px" %)**1**|(% style="width:509px" %)**Length depends on the return from the commands**
671 -|Value|(% style="width:130px" %)(((
672 -(((
556 +|**Size(bytes)**|**2**|**1**|**Length depends on the return from the commands**
557 +|Value|(((
673 673  Battery(mV)
674 -)))
675 675  
676 -(((
677 677  &
678 -)))
679 679  
680 -(((
681 681  Interrupt _Flag
682 -)))
683 -)))|(% style="width:93px" %)(((
563 +)))|(((
684 684  PAYLOAD_VER
685 685  
686 686  
687 -)))|(% 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.
688 688  
689 689  Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors.
690 690  
691 -(((
692 -{{{function Decoder(bytes, port) {}}}
693 -)))
694 694  
695 -(((
696 -{{{//Payload Formats of RS485-BL Deceive}}}
697 -)))
572 +function Decoder(bytes, port) {
698 698  
699 -(((
700 -{{{return {}}}
701 -)))
574 +~/~/Payload Formats of RS485-BL Deceive
702 702  
703 -(((
704 -{{{ //Battery,units:V}}}
705 -)))
576 +return {
706 706  
707 -(((
708 -{{{ BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000,}}}
709 -)))
578 + ~/~/Battery,units:V
710 710  
711 -(((
712 -{{{ //GPIO_EXTI }}}
713 -)))
580 + BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000,
714 714  
715 -(((
716 -{{{ EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE",}}}
717 -)))
582 + ~/~/GPIO_EXTI 
718 718  
719 -(((
720 -{{{ //payload of version}}}
721 -)))
584 + EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE",
722 722  
723 -(((
724 -{{{ Pay_ver:bytes[2],}}}
725 -)))
586 + ~/~/payload of version
726 726  
727 -(((
728 -{{{ }; }}}
729 -)))
588 + Pay_ver:bytes[2],
730 730  
731 -(((
732 -}
590 + };
733 733  
734 -
735 -)))
592 + }
736 736  
737 -(((
738 -TTN V3 uplink screen shot.
739 -)))
740 740  
741 -[[image:1653274001211-372.png||height="192" width="732"]]
742 742  
743 743  
744 -== 3.5 Configure RS485-BL via AT or Downlink ==
745 745  
746 -User can configure RS485-BL via AT Commands or LoRaWAN Downlink Commands
747 747  
748 -There are two kinds of Commands:
749 749  
750 -* (% 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: [[AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]
600 +TTN V3 uplink screen shot.
751 751  
752 -* (% style="color:#4f81bd" %)**Sensor Related Commands**(%%): These commands are special designed for RS485-BL.  User can see these commands below:
602 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]
753 753  
604 +1.
605 +11. Configure RS485-BL via AT or Downlink
754 754  
607 +User can configure RS485-BL via [[AT Commands >>path:#_​Using_the_AT]]or LoRaWAN Downlink Commands
755 755  
756 -=== 3.5.1 Common Commands: ===
609 +There are two kinds of Commands:
757 757  
758 -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]]
611 +* **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
759 759  
613 +* **Sensor Related Commands**: These commands are special designed for RS485-BL.  User can see these commands below:
760 760  
761 -=== 3.5.2 Sensor related commands: ===
615 +1.
616 +11.
617 +111. Common Commands:
762 762  
619 +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]]
763 763  
764 -==== **Choose Device Type (RS485 or TTL)** ====
765 765  
622 +1.
623 +11.
624 +111. Sensor related commands:
625 +
626 +==== Choose Device Type (RS485 or TTL) ====
627 +
766 766  RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect.
767 767  
768 -* **AT Command**
630 +* AT Command
769 769  
770 -(% class="box infomessage" %)
771 -(((
772 772  **AT+MOD=1** ~/~/ Set to support RS485-MODBUS type sensors. User can connect multiply RS485 , Modbus sensors to the A / B pins.
773 -)))
774 774  
775 -(% class="box infomessage" %)
776 -(((
777 777  **AT+MOD=2** ~/~/ Set to support TTL Level sensors, User can connect one TTL Sensor to the TXD/RXD/GND pins.
778 -)))
779 779  
780 780  
781 -* **Downlink Payload**
637 +* Downlink Payload
782 782  
783 -**0A aa**  ~-~->  same as AT+MOD=aa
639 +**0A aa**     à same as AT+MOD=aa
784 784  
785 785  
786 786  
787 -==== **RS485 Debug Command (AT+CFGDEV)** ====
643 +==== [[RS485 Debug Command>>path:#downlink_A8]] (AT+CFGDEV) ====
788 788  
789 789  This command is used to configure the RS485 or TTL sensors; they won’t be used during sampling.
790 790  
791 -* **AT Command**
647 +* AT Command
792 792  
793 -(% class="box infomessage" %)
794 -(((
795 -**AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m**
796 -)))
649 +AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
797 797  
798 798  m: 0: no CRC; 1: add CRC-16/MODBUS in the end of this command.
799 799  
800 800  
801 -* **Downlink Payload**
802 802  
655 +* Downlink Payload
656 +
803 803  Format: A8 MM NN XX XX XX XX YY
804 804  
805 805  Where:
... ... @@ -813,15 +813,15 @@
813 813  
814 814  To connect a Modbus Alarm with below commands.
815 815  
816 -* 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.
670 +* 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.
817 817  
818 -* 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.
672 +* 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.
819 819  
820 820  So if user want to use downlink command to control to RS485 Alarm, he can use:
821 821  
822 -(% style="color:#037691" %)**A8 01 06 0A 05 00 04 00 01 00**(%%): to activate the RS485 Alarm
676 +**A8 01 06 0A 05 00 04 00 01 00**: to activate the RS485 Alarm
823 823  
824 -(% style="color:#037691" %)**A8 01 06 0A 05 00 04 00 00 00**(%%): to deactivate the RS485 Alarm
678 +**A8 01 06 0A 05 00 04 00 00 00**: to deactivate the RS485 Alarm
825 825  
826 826  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.
827 827  
... ... @@ -830,61 +830,48 @@
830 830  
831 831  Check TTL Sensor return:
832 832  
833 -[[image:1654132684752-193.png]]
687 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image024.png]]
834 834  
835 835  
836 836  
837 837  
838 -==== **Set Payload version** ====
692 +==== Set Payload version ====
839 839  
840 840  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.
841 841  
842 -* **AT Command:**
696 +* AT Command:
843 843  
844 -(% class="box infomessage" %)
845 -(((
846 -**AT+PAYVER: Set PAYVER field = 1**
847 -)))
698 +AT+PAYVER: Set PAYVER field = 1
848 848  
849 849  
850 -* **Downlink Payload:**
701 +* Downlink Payload:
851 851  
852 -**0xAE 01**  ~-~-> Set PAYVER field =  0x01
703 +0xAE 01   à Set PAYVER field =  0x01
853 853  
854 -**0xAE 0F**   ~-~-> Set PAYVER field =  0x0F
705 +0xAE 0F   à Set PAYVER field =  0x0F
855 855  
856 856  
708 +==== Set RS485 Sampling Commands ====
857 857  
858 -==== **Set RS485 Sampling Commands** ====
859 -
860 860  AT+COMMANDx, AT+DATACUTx and AT+SEARCHx
861 861  
862 -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"]].
712 +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]].
863 863  
864 864  
865 -* **AT Command:**
715 +* AT Command:
866 866  
867 -(% class="box infomessage" %)
868 -(((
869 -**AT+COMMANDx: Configure RS485 read command to sensor.**
870 -)))
717 +AT+COMMANDx: Configure RS485 read command to sensor.
871 871  
872 -(% class="box infomessage" %)
873 -(((
874 -**AT+DATACUTx: Configure how to handle return from RS485 devices.**
875 -)))
719 +AT+DATACUTx: Configure how to handle return from RS485 devices.
876 876  
877 -(% class="box infomessage" %)
878 -(((
879 -**AT+SEARCHx: Configure search command**
880 -)))
721 +AT+SEARCHx: Configure search command
881 881  
882 882  
883 -* **Downlink Payload:**
724 +* Downlink Payload:
884 884  
885 -**0xAF** downlink command can be used to set AT+COMMANDx or AT+DATACUTx.
726 +0xAF downlink command can be used to set AT+COMMANDx or AT+DATACUTx.
886 886  
887 -(% style="color:red" %)**Note**(%%): if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink.
728 +Note: if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink.
888 888  
889 889  Format: AF MM NN LL XX XX XX XX YY
890 890  
... ... @@ -891,23 +891,23 @@
891 891  Where:
892 892  
893 893  * MM: the ATCOMMAND or AT+DATACUT to be set. Value from 01 ~~ 0F,
894 -* NN:  0: no CRC; 1: add CRC-16/MODBUS ; 2: set the AT+DATACUT value.
895 -* LL:  The length of AT+COMMAND or AT+DATACUT command
735 +* NN: 0: no CRC; 1: add CRC-16/MODBUS ; 2: set the AT+DATACUT value.
736 +* LL: The length of AT+COMMAND or AT+DATACUT command
896 896  * XX XX XX XX: AT+COMMAND or AT+DATACUT command
897 -* 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.
738 +* 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.
898 898  
899 -**Example:**
740 +Example:
900 900  
901 -(% 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
742 +**AF 03 01 06 0A 05 00 04 00 01 00**: Same as AT+COMMAND3=0A 05 00 04 00 01,1
902 902  
903 -(% 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**
744 +**AF 03 02 06 10 01 05 06 09 0A 00**: Same as AT+DATACUT3=**16**,**1**,**5+6+9+10**
904 904  
905 -(% 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**
746 +**AF 03 02 06 0B 02 05 07 08 0A 00**: Same as AT+DATACUT3=**11**,**2**,**5~~7+8~~10**
906 906  
907 907  
908 -**0xAB** downlink command can be used for set AT+SEARCHx
749 +0xAB downlink command can be used for set AT+SEARCHx
909 909  
910 -**Example:** **AB aa 01 03 xx xx xx** (03 here means there are total 3 bytes after 03) So
751 +Example: **AB aa 01 03 xx xx xx** (03 here means there are total 3 bytes after 03) So
911 911  
912 912  * AB aa 01 03 xx xx xx  same as AT+SEARCHaa=1,xx xx xx
913 913  * 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
... ... @@ -915,164 +915,145 @@
915 915  **AB aa 02 03 xx xx xx 02 yy yy**  same as **AT+SEARCHaa=2,xx xx xx+yy yy**
916 916  
917 917  
759 +==== Fast command to handle MODBUS device ====
918 918  
919 -==== **Fast command to handle MODBUS device** ====
920 -
921 921  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]].
922 922  
923 923  This command is valid since v1.3 firmware version
924 924  
925 925  
926 -**AT+MBFUN has only two value:**
766 +AT+MBFUN has only two value:
927 927  
928 -* **AT+MBFUN=1**: Enable Modbus reading. And get response base on the MODBUS return
768 +* AT+MBFUN=1: Enable Modbus reading. And get response base on the MODBUS return
929 929  
930 930  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.
931 931  
932 -* **AT+MBFUN=0**: Disable Modbus fast reading.
772 +* AT+MBFUN=0: Disable Modbus fast reading.
933 933  
934 -**Example:**
774 +Example:
935 935  
936 936  * AT+MBFUN=1 and AT+DATACUT1/AT+DATACUT2 are not configure (0,0,0).
937 937  * 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.
938 938  * 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.
939 939  
940 -[[image:1654133913295-597.png]]
780 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image025.png]]
941 941  
942 942  
943 -[[image:1654133954153-643.png]]
783 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image026.png]]
944 944  
945 945  
946 -* **Downlink Commands:**
786 +* Downlink Commands:
947 947  
948 -**A9 aa** ~-~-> Same as AT+MBFUN=aa
788 +A9 aa -à Same as AT+MBFUN=aa
949 949  
950 950  
791 +==== RS485 command timeout ====
951 951  
952 -==== **RS485 command timeout** ====
953 -
954 954  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.
955 955  
956 956  Default value: 0, range:  0 ~~ 5 seconds
957 957  
958 958  
959 -* **AT Command:**
798 +* AT Command:
960 960  
961 -(% class="box infomessage" %)
962 -(((
963 -**AT+CMDDLaa=hex(bb cc)**
964 -)))
800 +AT+CMDDLaa=hex(bb cc)
965 965  
966 -**Example:**
802 +Example:
967 967  
968 968  **AT+CMDDL1=1000** to send the open time to 1000ms
969 969  
970 970  
971 -* **Downlink Payload:**
807 +* Downlink Payload:
972 972  
973 973  0x AA aa bb cc
974 974  
975 975  Same as: AT+CMDDLaa=hex(bb cc)
976 976  
977 - **Example:**
813 + Example:
978 978  
979 - **0xAA 01 03 E8**  ~-~-> Same as **AT+CMDDL1=1000 ms**
815 + 0xAA 01 03 E8  à Same as **AT+CMDDL1=1000 ms**
980 980  
981 981  
818 +==== [[Uplink>>path:#downlink_A8]] payload mode ====
982 982  
983 -==== **Uplink payload mode** ====
984 -
985 985  Define to use one uplink or multiple uplinks for the sampling.
986 986  
987 -The use of this command please see: [[Compose Uplink payload>>||anchor="H3.3.4Composetheuplinkpayload"]]
822 +The use of this command please see: [[Compose Uplink payload>>path:#DataUP]]
988 988  
989 -* **AT Command:**
824 +* AT Command:
990 990  
991 -(% class="box infomessage" %)
992 -(((
993 -**AT+DATAUP=0**
994 -)))
826 +AT+DATAUP=0
995 995  
996 -(% class="box infomessage" %)
997 -(((
998 -**AT+DATAUP=1**
999 -)))
828 +AT+DATAUP=1
1000 1000  
1001 1001  
1002 -* **Downlink Payload:**
831 +* Downlink Payload:
1003 1003  
1004 -**0xAD 00**  **~-~->** Same as AT+DATAUP=0
833 +0xAD 00   à Same as AT+DATAUP=0
1005 1005  
1006 -**0xAD 01**  **~-~->** Same as AT+DATAUP=1
835 +0xAD 01   à Same as AT+DATAUP=1
1007 1007  
1008 1008  
838 +==== Manually trigger an Uplink ====
1009 1009  
1010 -==== **Manually trigger an Uplink** ====
1011 -
1012 1012  Ask device to send an uplink immediately.
1013 1013  
1014 -* **Downlink Payload:**
842 +* Downlink Payload:
1015 1015  
1016 -**0x08 FF**, RS485-BL will immediately send an uplink.
844 +0x08 FF, RS485-BL will immediately send an uplink.
1017 1017  
1018 1018  
847 +==== Clear RS485 Command ====
1019 1019  
1020 -==== **Clear RS485 Command** ====
1021 -
1022 1022  The AT+COMMANDx and AT+DATACUTx settings are stored in special location, user can use below command to clear them.
1023 1023  
1024 1024  
1025 -* **AT Command:**
852 +* AT Command:
1026 1026  
1027 -(% 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
854 +**AT+CMDEAR=mm,nn**   mm: start position of erase ,nn: stop position of erase
1028 1028  
856 +Etc. AT+CMDEAR=1,10 means erase AT+COMMAND1/AT+DATACUT1 to AT+COMMAND10/AT+DATACUT10
857 +
1029 1029  Example screen shot after clear all RS485 commands. 
1030 1030  
1031 1031  
861 +
1032 1032  The uplink screen shot is:
1033 1033  
1034 -[[image:1654134704555-320.png]]
864 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]
1035 1035  
1036 1036  
1037 -* **Downlink Payload:**
867 +* Downlink Payload:
1038 1038  
1039 -**0x09 aa bb** same as AT+CMDEAR=aa,bb
869 +0x09 aa bb same as AT+CMDEAR=aa,bb
1040 1040  
1041 1041  
872 +==== Set Serial Communication Parameters ====
1042 1042  
1043 -==== **Set Serial Communication Parameters** ====
1044 -
1045 1045  Set the Rs485 serial communication parameters:
1046 1046  
1047 -* **AT Command:**
876 +* AT Command:
1048 1048  
1049 1049  Set Baud Rate:
1050 1050  
1051 -(% class="box infomessage" %)
1052 -(((
1053 -**AT+BAUDR=9600**    ~/~/ Options: (1200,2400,4800,14400,19200,115200)
1054 -)))
880 +AT+BAUDR=9600    ~/~/ Options: (1200,2400,4800,14400,19200,115200)
1055 1055  
1056 -Set UART Parity
1057 1057  
1058 -(% class="box infomessage" %)
1059 -(((
1060 -**AT+PARITY=0**    ~/~/ Option: 0: no parity, 1: odd parity, 2: even parity
1061 -)))
883 +Set UART parity
1062 1062  
885 +AT+PARITY=0    ~/~/ Option: 0: no parity, 1: odd parity, 2: even parity
886 +
887 +
1063 1063  Set STOPBIT
1064 1064  
1065 -(% class="box infomessage" %)
1066 -(((
1067 -**AT+STOPBIT=0**    ~/~/ Option: 0 for 1bit; 1 for 1.5 bit ; 2 for 2 bits
1068 -)))
890 +AT+STOPBIT=0    ~/~/ Option: 0 for 1bit; 1 for 1.5 bit ; 2 for 2 bits
1069 1069  
1070 1070  
1071 -* **Downlink Payload:**
893 +* Downlink Payload:
1072 1072  
1073 -**A7 01 aa bb**: Same  AT+BAUDR=hex(aa bb)*100
895 +A7 01 aa bb: Same  AT+BAUDR=hex(aa bb)*100
1074 1074  
1075 -**Example:**
897 +Example:
1076 1076  
1077 1077  * A7 01 00 60   same as AT+BAUDR=9600
1078 1078  * A7 01 04 80  same as AT+BAUDR=115200
... ... @@ -1082,192 +1082,180 @@
1082 1082  A7 03 aa: Same as  AT+STOPBIT=aa  (aa value: 00 , 01 or 02)
1083 1083  
1084 1084  
907 +==== Control output power duration ====
1085 1085  
1086 -==== **Control output power duration** ====
1087 -
1088 1088  User can set the output power duration before each sampling.
1089 1089  
1090 -* **AT Command:**
911 +* AT Command:
1091 1091  
1092 -**Example:**
913 +Example:
1093 1093  
1094 -**AT+3V3T=1000**  ~/~/ 3V3 output power will open 1s before each sampling.
915 +AT+3V3T=1000 ~/~/ 3V3 output power will open 1s before each sampling.
1095 1095  
1096 -**AT+5VT=1000**  ~/~/ +5V output power will open 1s before each sampling.
917 +AT+5VT=1000 ~/~/ +5V output power will open 1s before each sampling.
1097 1097  
1098 1098  
1099 -* **LoRaWAN Downlink Command:**
920 +* LoRaWAN Downlink Command:
1100 1100  
1101 -**07 01 aa bb**  Same as AT+5VT=(aa bb)
922 +07 01 aa bb  Same as AT+5VT=(aa bb)
1102 1102  
1103 -**07 02 aa bb**  Same as AT+3V3T=(aa bb)
924 +07 02 aa bb  Same as AT+3V3T=(aa bb)
1104 1104  
1105 1105  
1106 -== 3.6 Buttons ==
1107 1107  
1108 -(% border="1" style="background-color:#ffffcc; color:green; width:233px" %)
1109 -|=(% style="width: 89px;" %)**Button**|=(% style="width: 141px;" %)**Feature**
1110 -|(% style="width:89px" %)**RST**|(% style="width:141px" %)Reboot RS485-BL
1111 1111  
929 +1.
930 +11. Buttons
1112 1112  
932 +|**Button**|**Feature**
933 +|**RST**|Reboot RS485-BL
1113 1113  
1114 -== 3.7 +3V3 Output ==
935 +1.
936 +11. +3V3 Output
1115 1115  
1116 1116  RS485-BL has a Controllable +3V3 output, user can use this output to power external sensor.
1117 1117  
1118 1118  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. 
1119 1119  
942 +
1120 1120  The +3V3 output time can be controlled by AT Command.
1121 1121  
945 +**AT+3V3T=1000**
1122 1122  
1123 -(% style="color:#037691" %)**AT+3V3T=1000**
1124 -
1125 -
1126 1126  Means set +3v3 valid time to have 1000ms. So, the real +3v3 output will actually have 1000ms + sampling time for other sensors.
1127 1127  
949 +
1128 1128  By default, the AT+3V3T=0. This is a special case, means the +3V3 output is always on at any time
1129 1129  
1130 1130  
1131 -== 3.8 +5V Output ==
953 +1.
954 +11. +5V Output
1132 1132  
1133 1133  RS485-BL has a Controllable +5V output, user can use this output to power external sensor.
1134 1134  
1135 1135  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. 
1136 1136  
960 +
1137 1137  The 5V output time can be controlled by AT Command.
1138 1138  
963 +**AT+5VT=1000**
1139 1139  
1140 -(% style="color:#037691" %)**AT+5VT=1000**
1141 -
1142 -
1143 1143  Means set 5V valid time to have 1000ms. So, the real 5V output will actually have 1000ms + sampling time for other sensors.
1144 1144  
967 +
1145 1145  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.
1146 1146  
1147 1147  
1148 -== 3.9 LEDs ==
1149 1149  
1150 -(% border="1" style="background-color:#ffffcc; color:green; width:332px" %)
1151 -|=**LEDs**|=(% style="width: 274px;" %)**Feature**
1152 -|**LED1**|(% style="width:274px" %)Blink when device transmit a packet.
1153 1153  
973 +1.
974 +11. LEDs
1154 1154  
976 +|**LEDs**|**Feature**
977 +|**LED1**|Blink when device transmit a packet.
1155 1155  
1156 -== 3.10 Switch Jumper ==
979 +1.
980 +11. Switch Jumper
1157 1157  
1158 -(% border="1" style="background-color:#ffffcc; color:green; width:515px" %)
1159 -|=(% style="width: 124px;" %)**Switch Jumper**|=(% style="width: 388px;" %)**Feature**
1160 -|(% style="width:124px" %)**SW1**|(% style="width:388px" %)(((
982 +|**Switch Jumper**|**Feature**
983 +|**SW1**|(((
1161 1161  ISP position: Upgrade firmware via UART
1162 1162  
1163 1163  Flash position: Configure device, check running status.
1164 1164  )))
1165 -|(% style="width:124px" %)**SW2**|(% style="width:388px" %)(((
988 +|**SW2**|(((
1166 1166  5V position: set to compatible with 5v I/O.
1167 1167  
1168 1168  3.3v position: set to compatible with 3.3v I/O.,
1169 1169  )))
1170 1170  
1171 -**+3.3V**: is always ON
994 ++3.3V: is always ON
1172 1172  
1173 -**+5V**: Only open before every sampling. The time is by default, it is AT+5VT=0.  Max open time. 5000 ms.
996 ++5V: Only open before every sampling. The time is by default, it is AT+5VT=0.  Max open time. 5000 ms.
1174 1174  
998 +1. Case Study
1175 1175  
1176 -= 4. Case Study =
1000 +User can check this URL for some case studies.
1177 1177  
1178 -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]]
1002 +[[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]]
1179 1179  
1180 1180  
1181 -= 5. Use AT Command =
1182 1182  
1183 -== 5.1 Access AT Command ==
1184 1184  
1007 +1. Use AT Command
1008 +11. Access AT Command
1009 +
1185 1185  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.
1186 1186  
1187 -[[image:1654135840598-282.png]]
1012 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image027.png]]
1188 1188  
1189 1189  
1190 -In PC, User needs to set (% style="color:blue" %)**serial tool**(%%)(such as [[putty>>url:https://www.chiark.greenend.org.uk/~~sgtatham/putty/latest.html]], SecureCRT) baud rate to (% style="color:green" %)**9600**(%%) to access to access serial console of RS485-BL. The default password is 123456. Below is the output for reference:
1015 +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:
1191 1191  
1192 -[[image:1654136105500-922.png]]
1017 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image028.png]]
1193 1193  
1194 1194  
1195 -More detail AT Command manual can be found at [[AT Command Manual>>||anchor="3.5ConfigureRS485-BLviaATorDownlink"]]
1196 1196  
1021 +More detail AT Command manual can be found at [[AT Command Manual>>path:#AT_COMMAND]]
1197 1197  
1198 -== 5.2 Common AT Command Sequence ==
1199 1199  
1200 -=== 5.2.1 Multi-channel ABP mode (Use with SX1301/LG308) ===
1201 1201  
1025 +1.
1026 +11. Common AT Command Sequence
1027 +111. Multi-channel ABP mode (Use with SX1301/LG308)
1028 +
1202 1202  If device has not joined network yet:
1203 1203  
1204 -(% class="box infomessage" %)
1205 -(((
1206 -**AT+FDR**
1207 -)))
1031 +AT+FDR
1208 1208  
1209 -(% class="box infomessage" %)
1210 -(((
1211 -**AT+NJM=0**
1212 -)))
1033 +AT+NJM=0
1213 1213  
1214 -(% class="box infomessage" %)
1215 -(((
1216 -**ATZ**
1217 -)))
1035 +ATZ
1218 1218  
1219 1219  
1220 1220  If device already joined network:
1221 1221  
1222 -(% class="box infomessage" %)
1223 -(((
1224 -**AT+NJM=0**
1225 -)))
1040 +AT+NJM=0
1226 1226  
1227 -(% class="box infomessage" %)
1228 -(((
1229 -**ATZ**
1230 -)))
1042 +ATZ
1231 1231  
1044 +1.
1045 +11.
1046 +111. Single-channel ABP mode (Use with LG01/LG02)
1232 1232  
1233 -=== 5.5.2 Single-channel ABP mode (Use with LG01/LG02) ===
1048 +AT+FDR   Reset Parameters to Factory Default, Keys Reserve
1234 1234  
1050 +AT+NJM=0 Set to ABP mode
1235 1235  
1236 -(% style="background-color:#dcdcdc" %)**AT+FDR** (%%) Reset Parameters to Factory Default, Keys Reserve
1052 +AT+ADR=0 Set the Adaptive Data Rate Off
1237 1237  
1238 -(% style="background-color:#dcdcdc" %)**AT+NJM=0 **(%%)Set to ABP mode
1054 +AT+DR=5  Set Data Rate
1239 1239  
1240 -(% style="background-color:#dcdcdc" %)**AT+ADR=0** (%%)Set the Adaptive Data Rate Off
1056 +AT+TDC=60000  Set transmit interval to 60 seconds
1241 1241  
1242 -(% style="background-color:#dcdcdc" %)**AT+DR=5**  (%%)Set Data Rate
1058 +AT+CHS=868400000 Set transmit frequency to 868.4Mhz
1243 1243  
1244 -(% style="background-color:#dcdcdc" %)**AT+TDC=60000** (%%) Set transmit interval to 60 seconds
1060 +AT+RX2FQ=868400000 Set RX2Frequency to 868.4Mhz (according to the result from server)
1245 1245  
1246 -(% style="background-color:#dcdcdc" %)**AT+CHS=868400000**(%%) Set transmit frequency to 868.4Mhz
1062 +AT+RX2DR=5  Set RX2DR to match the downlink DR from server. see below
1247 1247  
1248 -(% style="background-color:#dcdcdc" %)**AT+RX2FQ=868400000** (%%) Set RX2Frequency to 868.4Mhz (according to the result from server)
1064 +AT+DADDR=26 01 1A F1 Set Device Address to 26 01 1A F1, this ID can be found in the LoRa Server portal.
1249 1249  
1250 -(% style="background-color:#dcdcdc" %)**AT+RX2DR=5**  (%%) Set RX2DR to match the downlink DR from server. see below
1066 +ATZ          Reset MCU
1251 1251  
1252 -(% style="background-color:#dcdcdc" %)**AT+DADDR=26** (%%) 01 1A F1 Set Device Address to 26 01 1A F1, this ID can be found in the LoRa Server portal.
1068 +**Note:**
1253 1253  
1254 -(% style="background-color:#dcdcdc" %)**ATZ**       (%%) Reset MCU
1070 +1. Make sure the device is set to ABP mode in the IoT Server.
1071 +1. Make sure the LG01/02 gateway RX frequency is exactly the same as AT+CHS setting.
1072 +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.
1073 +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
1255 1255  
1075 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image029.png]]
1256 1256  
1257 -(% style="color:red" %)**Note:**
1258 1258  
1259 -(% style="color:red" %)1. Make sure the device is set to ABP mode in the IoT Server.
1260 -2. Make sure the LG01/02 gateway RX frequency is exactly the same as AT+CHS setting.
1261 -3. 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.
1262 -4. 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
1078 +1. FAQ
1079 +11. How to upgrade the image?
1263 1263  
1264 -[[image:1654136435598-589.png]]
1265 -
1266 -
1267 -= 6. FAQ =
1268 -
1269 -== 6.1 How to upgrade the image? ==
1270 -
1271 1271  The RS485-BL LoRaWAN Controller is shipped with a 3.5mm cable, the cable is used to upload image to RS485-BL to:
1272 1272  
1273 1273  * Support new features
... ... @@ -1276,7 +1276,7 @@
1276 1276  
1277 1277  Below shows the hardware connection for how to upload an image to RS485-BL:
1278 1278  
1279 -[[image:1654136646995-976.png]]
1089 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image030.png]]
1280 1280  
1281 1281  **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]].
1282 1282  
... ... @@ -1284,95 +1284,97 @@
1284 1284  
1285 1285  **Step3: **Open flashloader; choose the correct COM port to update.
1286 1286  
1287 -[[image:image-20220602102605-1.png]]
1288 1288  
1098 +|(((
1099 +HOLD PRO then press the RST button, SYS will be ON, then click next
1100 +)))
1289 1289  
1290 -[[image:image-20220602102637-2.png]]
1102 +|(((
1103 +Board detected
1104 +)))
1291 1291  
1106 +|(((
1107 +
1108 +)))
1292 1292  
1293 -[[image:image-20220602102715-3.png]]
1110 +[[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]]
1294 1294  
1295 1295  
1296 1296  
1297 -== 6.2 How to change the LoRa Frequency Bands/Region? ==
1114 +[[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]]
1298 1298  
1299 -User can follow the introduction for [[how to upgrade image>>||anchor="H6.1Howtoupgradetheimage3F"]]. When download the images, choose the required image file for download.
1300 1300  
1117 +[[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]]
1301 1301  
1302 1302  
1303 -== 6.3 How many RS485-Slave can RS485-BL connects? ==
1120 +1.
1121 +11. How to change the LoRa Frequency Bands/Region?
1304 1304  
1305 -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>>||anchor="H3.3.3Configurereadcommandsforeachsampling"]].
1123 +User can follow the introduction for [[how to upgrade image>>path:#upgrade_image]]. When download the images, choose the required image file for download.
1306 1306  
1307 1307  
1308 1308  
1309 -= 7. Trouble Shooting =
1127 +1.
1128 +11. How many RS485-Slave can RS485-BL connects?
1310 1310  
1130 +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]].
1311 1311  
1312 -== 7.1 Downlink doesn’t work, how to solve it? ==
1313 1313  
1314 -Please see this link for debug: [[LoRaWAN Communication Debug>>doc:Main.LoRaWAN Communication Debug.WebHome]]
1315 1315  
1316 1316  
1317 -== 7.2 Why I can’t join TTN V3 in US915 /AU915 bands? ==
1135 +1. Trouble Shooting     
1136 +11. Downlink doesn’t work, how to solve it?
1318 1318  
1319 -It might about the channels mapping. Please see for detail: [[Notice of Frequency band>>doc:Main.LoRaWAN Communication Debug.WebHome||anchor="H2.NoticeofUS9152FCN4702FAU915Frequencyband"]]
1138 +Please see this link for debug:
1320 1320  
1140 +[[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]] 
1321 1321  
1322 -= 8. Order Info =
1323 1323  
1324 -(% style="color:blue" %)**Part Number: RS485-BL-XXX**
1325 1325  
1326 -(% style="color:blue" %)**XXX:**
1144 +1.
1145 +11. Why I can’t join TTN V3 in US915 /AU915 bands?
1327 1327  
1328 -* (% style="color:blue" %)**EU433**(%%): frequency bands EU433
1329 -* (% style="color:blue" %)**EU868**(%%): frequency bands EU868
1330 -* (% style="color:blue" %)**KR920**(%%): frequency bands KR920
1331 -* (% style="color:blue" %)**CN470**(%%): frequency bands CN470
1332 -* (% style="color:blue" %)**AS923**(%%): frequency bands AS923
1333 -* (% style="color:blue" %)**AU915**(%%): frequency bands AU915
1334 -* (% style="color:blue" %)**US915**(%%): frequency bands US915
1335 -* (% style="color:blue" %)**IN865**(%%): frequency bands IN865
1336 -* (% style="color:blue" %)**RU864**(%%): frequency bands RU864
1337 -* (% style="color:blue" %)**KZ865**(%%): frequency bands KZ865
1147 +It might about the channels mapping. Please see for detail.
1338 1338  
1149 +[[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]]
1339 1339  
1340 -= 9. Packing Info =
1341 1341  
1342 -(((
1152 +
1153 +1. Order Info
1154 +
1155 +**Part Number: RS485-BL-XXX**
1156 +
1157 +**XXX:**
1158 +
1159 +* **EU433**: frequency bands EU433
1160 +* **EU868**: frequency bands EU868
1161 +* **KR920**: frequency bands KR920
1162 +* **CN470**: frequency bands CN470
1163 +* **AS923**: frequency bands AS923
1164 +* **AU915**: frequency bands AU915
1165 +* **US915**: frequency bands US915
1166 +* **IN865**: frequency bands IN865
1167 +* **RU864**: frequency bands RU864
1168 +* **KZ865: **frequency bands KZ865
1169 +
1170 +1. Packing Info
1171 +
1343 1343  **Package Includes**:
1344 -)))
1345 1345  
1346 -* (((
1347 -RS485-BL x 1
1348 -)))
1349 -* (((
1350 -Stick Antenna for LoRa RF part x 1
1351 -)))
1352 -* (((
1353 -Program cable x 1
1354 -)))
1174 +* RS485-BL x 1
1175 +* Stick Antenna for LoRa RF part x 1
1176 +* Program cable x 1
1355 1355  
1356 -(((
1357 1357  **Dimension and weight**:
1358 -)))
1359 1359  
1360 -* (((
1361 -Device Size: 13.5 x 7 x 3 cm
1362 -)))
1363 -* (((
1364 -Device Weight: 105g
1365 -)))
1366 -* (((
1367 -Package Size / pcs : 14.5 x 8 x 5 cm
1368 -)))
1369 -* (((
1370 -Weight / pcs : 170g
1180 +* Device Size: 13.5 x 7 x 3 cm
1181 +* Device Weight: 105g
1182 +* Package Size / pcs : 14.5 x 8 x 5 cm
1183 +* Weight / pcs : 170g
1371 1371  
1372 -
1373 -)))
1185 +1. Support
1374 1374  
1375 -= 10. Support =
1376 -
1377 1377  * 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.
1378 -* 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 [[support@dragino.com>>url:file:///D:/市场资料/说明书/LoRa/LT系列/support@dragino.com]]
1188 +* 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
1189 +
1190 +[[support@dragino.com>>url:file:///D:/市场资料/说明书/LoRa/LT系列/support@dragino.com]]
1652953568895-172.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -109.3 KB
Content
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
1654132684752-193.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -22.8 KB
Content
1654133913295-597.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -116.2 KB
Content
1654133954153-643.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -91.2 KB
Content
1654134704555-320.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -91.4 KB
Content
1654135840598-282.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -1.3 MB
Content
1654136105500-922.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -203.7 KB
Content
1654136435598-589.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -158.9 KB
Content
1654136646995-976.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -1.3 MB
Content
image-20220602102605-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -102.6 KB
Content
image-20220602102637-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -250.8 KB
Content
image-20220602102715-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -176.2 KB
Content