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