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