Skip to Content
Last modified by Xiaoling on 2025/04/23 15:57
From version 41.7
edited by Xiaoling
on 2022/06/06 10:56
Change comment: There is no comment for this version
To version 3.1
edited by Xiaoling
on 2022/05/19 16:08
Change comment: Uploaded new attachment "1652947681187-144.png", version {1}

Summary

Details

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