Skip to Content
Last modified by Xiaoling on 2025/04/23 15:57
From version 3.1
edited by Xiaoling
on 2022/05/19 16:08
Change comment: Uploaded new attachment "1652947681187-144.png", version {1}
To version 38.1
edited by Xiaoling
on 2022/06/02 10:26
Change comment: Uploaded new attachment "image-20220602102605-1.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -1,60 +1,72 @@
1 -
1 +(% style="text-align:center" %)
2 +[[image:1652947681187-144.png||height="385" width="385"]]
2 2  
3 3  
4 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image001.jpg]]
5 5  
6 6  
7 -
8 8  **RS485-BL – Waterproof RS485 to LoRaWAN Converter User Manual**
9 9  
10 10  
11 11  
11 +**Table of Contents:**
12 12  
13 +{{toc/}}
13 13  
14 14  
15 15  
16 16  
17 -1. Introduction
18 -11. What is RS485-BL RS485 to LoRaWAN Converter
19 19  
19 += 1.Introduction =
20 20  
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.
21 +== 1.1 What is RS485-BL RS485 to LoRaWAN Converter ==
22 22  
23 +(((
24 +
25 +)))
23 23  
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.
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 +)))
25 25  
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 +)))
26 26  
27 -RS485-BL is IP67 **waterproof** and powered by **8500mAh Li-SOCI2 battery**, it is designed for long term use for several years.
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 +)))
28 28  
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 +)))
29 29  
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 -
43 +(((
33 33  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 +)))
34 34  
35 -
47 +(((
36 36  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 +)))
37 37  
38 -
51 +(((
39 39  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 +)))
40 40  
41 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image002.png]]
55 +[[image:1652953304999-717.png||height="424" width="733"]]
42 42  
43 43  
44 -1.
45 -11. Specifications
46 46  
59 +== 1.2 Specifications ==
60 +
61 +
47 47  **Hardware System:**
48 48  
49 49  * STM32L072CZT6 MCU
50 -* SX1276/78 Wireless Chip
65 +* SX1276/78 Wireless Chip 
51 51  * Power Consumption (exclude RS485 device):
52 52  ** Idle: 6uA@3.3v
53 -
54 -*
55 55  ** 20dB Transmit: 130mA@3.3v
56 56  
57 -
58 58  **Interface for Model:**
59 59  
60 60  * 1 x RS485 Interface
... ... @@ -64,7 +64,6 @@
64 64  * 1 x Interrupt Interface
65 65  * 1 x Controllable 5V output, max
66 66  
67 -
68 68  **LoRa Spec:**
69 69  
70 70  * Frequency Range:
... ... @@ -81,11 +81,10 @@
81 81  * Built-in bit synchronizer for clock recovery.
82 82  * Preamble detection.
83 83  * 127 dB Dynamic Range RSSI.
84 -* Automatic RF Sense and CAD with ultra-fast AFC.
95 +* Automatic RF Sense and CAD with ultra-fast AFC. ​​​
85 85  
97 +== 1.3 Features ==
86 86  
87 -*
88 -*1. Features
89 89  * LoRaWAN Class A & Class C protocol (default Class A)
90 90  * Frequency Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/IN865/RU864
91 91  * AT Commands to change parameters
... ... @@ -95,9 +95,8 @@
95 95  * Support Modbus protocol
96 96  * Support Interrupt uplink
97 97  
108 +== 1.4 Applications ==
98 98  
99 -*
100 -*1. Applications
101 101  * Smart Buildings & Home Automation
102 102  * Logistics and Supply Chain Management
103 103  * Smart Metering
... ... @@ -105,264 +105,305 @@
105 105  * Smart Cities
106 106  * Smart Factory
107 107  
117 +== 1.5 Firmware Change log ==
108 108  
109 -1.
110 -11. Firmware Change log
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);"]]
111 111  
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/]]
113 113  
122 +== 1.6 Hardware Change log ==
114 114  
115 -1.
116 -11. Hardware Change log
124 +(((
125 +
117 117  
118 -
119 119  v1.4
128 +)))
120 120  
130 +(((
121 121  ~1. Change Power IC to TPS22916
132 +)))
122 122  
123 123  
135 +(((
124 124  v1.3
137 +)))
125 125  
139 +(((
126 126  ~1. Change JP3 from KF350-8P to KF350-11P, Add one extra interface for I2C and one extra interface for one-wire
141 +)))
127 127  
128 128  
144 +(((
129 129  v1.2
146 +)))
130 130  
131 -Release version
148 +(((
149 +Release version ​​​​​
132 132  
151 +
152 +)))
133 133  
154 += 2. Pin mapping and Power ON Device =
134 134  
135 -
136 -
137 -1. Pin mapping and Power ON Device
138 -
156 +(((
139 139  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.
158 +)))
140 140  
160 +[[image:1652953055962-143.png||height="387" width="728"]]
141 141  
142 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image003.png]]
143 143  
144 -
145 -
146 146  The Left TXD and RXD are TTL interface for external sensor. TTL level is controlled by 3.3/5v Jumper.
147 147  
148 148  
166 += 3. Operation Mode =
149 149  
168 +== 3.1 How it works? ==
150 150  
151 -
152 -
153 -1. Operation Mode
154 -11. How it works?
155 -
170 +(((
156 156  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.
157 157  
173 +
174 +)))
158 158  
159 -1.
160 -11. Example to join LoRaWAN network
176 +== 3.2 Example to join LoRaWAN network ==
161 161  
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.
178 +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. 
163 163  
164 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image004.png]]
180 +[[image:1652953414711-647.png||height="337" width="723"]]
165 165  
166 -
182 +(((
167 167  The RS485-BL in this example connected to two RS485 devices for demonstration, user can connect to other RS485 devices via the same method.
184 +)))
168 168  
169 -
186 +(((
170 170  The LG308 is already set to connect to [[TTN V3 network >>url:https://www.thethingsnetwork.org/]]. So what we need to now is only configure the TTN V3:
188 +)))
171 171  
190 +(((
172 172  **Step 1**: Create a device in TTN V3 with the OTAA keys from RS485-BL.
192 +)))
173 173  
194 +(((
174 174  Each RS485-BL is shipped with a sticker with unique device EUI:
196 +)))
175 175  
176 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image005.png]]
198 +[[image:1652953462722-299.png]]
177 177  
178 -
179 -
180 -
200 +(((
181 181  User can enter this key in their LoRaWAN Server portal. Below is TTN V3 screen shot:
202 +)))
182 182  
204 +(((
183 183  Add APP EUI in the application.
206 +)))
184 184  
185 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image006.png]]
186 186  
187 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image007.png]]
209 +[[image:image-20220519174512-1.png]]
188 188  
189 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image008.png]]
211 +[[image:image-20220519174512-2.png||height="328" width="731"]]
190 190  
191 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image009.png]]
213 +[[image:image-20220519174512-3.png||height="556" width="724"]]
192 192  
215 +[[image:image-20220519174512-4.png]]
193 193  
194 -
195 -
196 -
197 -
198 -
199 -
200 -
201 -
202 -
203 -
204 -
205 -
206 -
207 -
208 -
209 209  You can also choose to create the device manually.
210 210  
211 -|(((
212 -
213 -)))
219 +[[image:1652953542269-423.png||height="710" width="723"]]
214 214  
215 -
216 -
217 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image010.png]]
218 -
219 219  Add APP KEY and DEV EUI
220 220  
221 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image011.png]]
223 +[[image:1652953553383-907.png||height="514" width="724"]]
222 222  
223 223  
226 +(((
224 224  **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.
228 +)))
225 225  
226 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image012.png]]
230 +[[image:1652953568895-172.png||height="232" width="724"]]
227 227  
228 228  
233 +== 3.3 Configure Commands to read data ==
229 229  
235 +(((
236 +There are plenty of RS485 and TTL level devices in the market and each device has different command to read the valid data. To support these devices in flexible, RS485-BL supports flexible command set. User can use [[AT Commands or LoRaWAN Downlink>>||anchor="H3.5ConfigureRS485-BLviaATorDownlink"]] Command to configure how RS485-BL should read the sensor and how to handle the return from RS485 or TTL sensors.
230 230  
231 -1.
232 -11. Configure Commands to read data
238 +
239 +)))
233 233  
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.
241 +=== 3.3.1 onfigure UART settings for RS485 or TTL communication ===
235 235  
236 -
237 -1.
238 -11.
239 -111. Configure UART settings for RS485 or TTL communication
240 -
241 241  RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect.
242 242  
243 -1. RS485-MODBUS mode:
245 +**~1. RS485-MODBUS mode:**
244 244  
245 245  AT+MOD=1 ~/~/ Support RS485-MODBUS type sensors. User can connect multiply RS485 , Modbus sensors to the A / B pins.
246 246  
249 +**2. TTL mode:**
247 247  
248 -1. TTL mode:
249 -
250 250  AT+MOD=2 ~/~/ Support TTL Level sensors, User can connect one TTL Sensor to the TXD/RXD/GND pins.
251 251  
252 -
253 253  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.
254 254  
255 -
256 -|**AT Commands**|**Description**|**Example**
257 -|AT+BAUDR|Set the baud rate (for RS485 connection). Default Value is: 9600.|(((
255 +(% border="1" style="background-color:#ffffcc; color:green; width:795px" %)
256 +|(((
257 +**AT Commands**
258 +)))|(% style="width:285px" %)(((
259 +**Description**
260 +)))|(% style="width:347px" %)(((
261 +**Example**
262 +)))
263 +|(((
264 +AT+BAUDR
265 +)))|(% style="width:285px" %)(((
266 +Set the baud rate (for RS485 connection). Default Value is: 9600.
267 +)))|(% style="width:347px" %)(((
268 +(((
258 258  AT+BAUDR=9600
270 +)))
259 259  
272 +(((
260 260  Options: (1200,2400,4800,14400,19200,115200)
261 261  )))
262 -|AT+PARITY|(((
275 +)))
276 +|(((
277 +AT+PARITY
278 +)))|(% style="width:285px" %)(((
279 +(((
263 263  Set UART parity (for RS485 connection)
281 +)))
264 264  
283 +(((
265 265  Default Value is: no parity.
266 -)))|(((
285 +)))
286 +)))|(% style="width:347px" %)(((
287 +(((
267 267  AT+PARITY=0
289 +)))
268 268  
291 +(((
269 269  Option: 0: no parity, 1: odd parity, 2: even parity
270 270  )))
271 -|AT+STOPBIT|(((
294 +)))
295 +|(((
296 +AT+STOPBIT
297 +)))|(% style="width:285px" %)(((
298 +(((
272 272  Set serial stopbit (for RS485 connection)
300 +)))
273 273  
302 +(((
274 274  Default Value is: 1bit.
275 -)))|(((
304 +)))
305 +)))|(% style="width:347px" %)(((
306 +(((
276 276  AT+STOPBIT=0 for 1bit
308 +)))
277 277  
310 +(((
278 278  AT+STOPBIT=1 for 1.5 bit
312 +)))
279 279  
314 +(((
280 280  AT+STOPBIT=2 for 2 bits
281 281  )))
317 +)))
282 282  
319 +=== 3.3.2 Configure sensors ===
283 283  
321 +(((
322 +Some sensors might need to configure before normal operation. User can configure such sensor via PC or through RS485-BL AT Commands (% style="color:#4f81bd" %)**AT+CFGDEV**.
323 +)))
284 284  
325 +(((
326 +When user issue an (% style="color:#4f81bd" %)**AT+CFGDEV**(%%) command, Each (% style="color:#4f81bd" %)**AT+CFGDEV**(%%) equals to send a command to the RS485 or TTL sensors. This command will only run when user input it and won’t run during each sampling.
327 +)))
285 285  
286 -
287 -1.
288 -11.
289 -111. Configure sensors
290 -
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|(((
329 +(% border="1" style="background-color:#ffffcc; color:green; width:806px" %)
330 +|**AT Commands**|(% style="width:418px" %)**Description**|(% style="width:256px" %)**Example**
331 +|AT+CFGDEV|(% style="width:418px" %)(((
298 298  This command is used to configure the RS485/TTL devices; they won’t be used during sampling.
299 299  
300 -AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
334 +AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,
301 301  
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
336 +mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
337 +)))|(% style="width:256px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
304 304  
305 -Detail of AT+CFGDEV command see [[AT+CFGDEV detail>>path:#AT_CFGDEV]].
339 +Detail of AT+CFGDEV command see [[AT+CFGDEV detail>>||anchor="HRS485DebugCommand28AT2BCFGDEV29"]].
306 306  
307 307  
342 +=== 3.3.3 Configure read commands for each sampling ===
308 308  
309 -
310 -
311 -1.
312 -11.
313 -111. Configure read commands for each sampling
314 -
344 +(((
315 315  RS485-BL is a battery powered device; it will sleep most of time. And wake up on each period and read RS485 / TTL sensor data and uplink.
346 +)))
316 316  
317 -
348 +(((
318 318  During each sampling, we need to confirm what commands we need to send to the sensors to read data. After the RS485/TTL sensors send back the value, it normally includes some bytes and we only need a few from them for a shorten payload.
350 +)))
319 319  
320 -
352 +(((
321 321  To save the LoRaWAN network bandwidth, we might need to read data from different sensors and combine their valid value into a short payload.
354 +)))
322 322  
323 -
356 +(((
324 324  This section describes how to achieve above goals.
358 +)))
325 325  
326 -
360 +(((
327 327  During each sampling, the RS485-BL can support 15 commands to read sensors. And combine the return to one or several uplink payloads.
362 +)))
328 328  
329 -
364 +(((
330 330  **Command from RS485-BL to Sensor:**
366 +)))
331 331  
368 +(((
332 332  RS485-BL can send out pre-set max 15 strings via **AT+COMMAD1**, **ATCOMMAND2**,…, to **AT+COMMANDF** . All commands are of same grammar.
370 +)))
333 333  
334 -
372 +(((
335 335  **Handle return from sensors to RS485-BL**:
374 +)))
336 336  
376 +(((
337 337  After RS485-BL send out a string to sensor, RS485-BL will wait for the return from RS485 or TTL sensor. And user can specify how to handle the return, by **AT+DATACUT or AT+SEARCH commands**
378 +)))
338 338  
380 +* (((
381 +**AT+DATACUT**
382 +)))
339 339  
340 -* **AT+DATACUT**
341 -
384 +(((
342 342  When the return value from sensor have fix length and we know which position the valid value we should get, we can use AT+DATACUT command.
386 +)))
343 343  
388 +* (((
389 +**AT+SEARCH**
390 +)))
344 344  
345 -* **AT+SEARCH**
346 -
392 +(((
347 347  When the return value from sensor is dynamic length and we are not sure which bytes the valid data is, instead, we know what value the valid value following. We can use AT+SEARCH to search the valid value in the return string.
394 +)))
348 348  
349 -
396 +(((
350 350  **Define wait timeout:**
398 +)))
351 351  
400 +(((
352 352  Some RS485 device might has longer delay on reply, so user can use AT+CMDDL to set the timeout for getting reply after the RS485 command is sent. For example, AT+CMDDL1=1000 to send the open time to 1000ms
402 +)))
353 353  
354 -
404 +(((
355 355  After we got the valid value from each RS485 commands, we need to combine them together with the command **AT+DATAUP**.
406 +)))
356 356  
357 -
358 358  **Examples:**
359 359  
360 360  Below are examples for the how above AT Commands works.
361 361  
362 -
363 363  **AT+COMMANDx : **This command will be sent to RS485/TTL devices during each sampling, Max command length is 14 bytes. The grammar is:
364 364  
365 -|(((
414 +(% border="1" class="table-bordered" style="background-color:#4f81bd; color:white; width:501px" %)
415 +|(% style="width:498px" %)(((
366 366  **AT+COMMANDx=xx xx xx xx xx xx xx xx xx xx xx xx,m**
367 367  
368 368  **xx xx xx xx xx xx xx xx xx xx xx xx: The RS485 command to be sent**
... ... @@ -374,140 +374,182 @@
374 374  
375 375  In the RS485-BL, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
376 376  
377 -
378 378  **AT+SEARCHx**: This command defines how to handle the return from AT+COMMANDx.
379 379  
380 -|(((
429 +(% border="1" class="table-bordered" style="background-color:#4f81bd; color:white; width:580px" %)
430 +|(% style="width:577px" %)(((
381 381  **AT+SEARCHx=aa,xx xx xx xx xx**
382 382  
383 383  * **aa: 1: prefix match mode; 2: prefix and suffix match mode**
384 384  * **xx xx xx xx xx: match string. Max 5 bytes for prefix and 5 bytes for suffix**
385 -
386 -
387 387  )))
388 388  
389 -Examples:
437 +**Examples:**
390 390  
391 -1. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
439 +1）For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
392 392  
393 393  If we set AT+SEARCH1=1,1E 56 34.      (max 5 bytes for prefix)
394 394  
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
443 +The valid data will be all bytes after 1E 56 34 , so it is (% style="background-color:yellow" %)**2e 30 58 5f 36 41 30 31 00 49**
396 396  
397 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image013.png]]
445 +[[image:1653271044481-711.png]]
398 398  
447 +2）For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
399 399  
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 -
402 402  If we set AT+SEARCH1=2, 1E 56 34+31 00 49
403 403  
404 -Device will search the bytes between 1E 56 34 and 31 00 49. So it is 2e 30 58 5f 36 41 30
451 +Device will search the bytes between 1E 56 34 and 31 00 49. So it is(% style="background-color:yellow" %) **2e 30 58 5f 36 41 30**
405 405  
406 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image014.png]]
453 +[[image:1653271276735-972.png]]
407 407  
408 -
409 409  **AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes.
410 410  
411 -|(((
457 +(% style="background-color:#4f81bd; color:white; width:729px" %)
458 +|(% style="width:726px" %)(((
412 412  **AT+DATACUTx=a,b,c**
413 413  
414 414  * **a: length for the return of AT+COMMAND**
415 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. **
463 +* **c: define the position for valid value.  **
417 417  )))
418 418  
419 -Examples:
466 +**Examples:**
420 420  
421 421  * Grab bytes:
422 422  
423 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image015.png]]
470 +[[image:1653271581490-837.png||height="313" width="722"]]
424 424  
472 +
425 425  * Grab a section.
426 426  
427 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image016.png]]
475 +[[image:1653271648378-342.png||height="326" width="720"]]
428 428  
477 +
429 429  * Grab different sections.
430 430  
431 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image017.png]]
480 +[[image:1653271657255-576.png||height="305" width="730"]]
432 432  
482 +(((
483 +(% style="color:red" %)**Note:**
484 +)))
433 433  
434 -Note:
435 -
486 +(((
436 436  AT+SEARCHx and AT+DATACUTx can be used together, if both commands are set, RS485-BL will first process AT+SEARCHx on the return string and get a temporary string, and then process AT+DATACUTx on this temporary string to get the final payload. In this case, AT+DATACUTx need to set to format AT+DATACUTx=0,xx,xx where the return bytes set to 0.
488 +)))
437 437  
438 -Example:
490 +(((
491 +**Example:**
492 +)))
439 439  
440 -AT+COMMAND1=11 01 1E D0,0
494 +(((
495 +(% style="color:red" %)AT+COMMAND1=11 01 1E D0,0
496 +)))
441 441  
442 -AT+SEARCH1=1,1E 56 34
498 +(((
499 +(% style="color:red" %)AT+SEARCH1=1,1E 56 34
500 +)))
443 443  
444 -AT+DATACUT1=0,2,1~~5
502 +(((
503 +(% style="color:red" %)AT+DATACUT1=0,2,1~~5
504 +)))
445 445  
446 -Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
506 +(((
507 +(% style="color:red" %)Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
508 +)))
447 447  
448 -String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
510 +(((
511 +(% style="color:red" %)String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
512 +)))
449 449  
450 -Valid payload after DataCUT command: 2e 30 58 5f 36
514 +(((
515 +(% style="color:red" %)Valid payload after DataCUT command: 2e 30 58 5f 36
516 +)))
451 451  
452 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image018.png]]
518 +[[image:1653271763403-806.png]]
453 453  
454 454  
521 +=== 3.3.4 Compose the uplink payload ===
455 455  
456 -
457 -1.
458 -11.
459 -111. Compose the uplink payload
460 -
523 +(((
461 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.**
525 +)))
462 462  
527 +(((
528 +(% style="color:#037691" %)**Examples: AT+DATAUP=0**
529 +)))
463 463  
464 -**Examples: AT+DATAUP=0**
531 +(((
532 +Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**A SIGNLE UPLINK**.
533 +)))
465 465  
466 -Compose the uplink payload with value returns in sequence and send with **A SIGNLE UPLINK**.
467 -
535 +(((
468 468  Final Payload is
537 +)))
469 469  
470 -Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx
539 +(((
540 +(% style="color:#4f81bd" %)**Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx**
541 +)))
471 471  
543 +(((
472 472  Where PAYVER is defined by AT+PAYVER, below is an example screen shot.
545 +)))
473 473  
474 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.png]]
547 +[[image:1653272787040-634.png||height="515" width="719"]]
475 475  
476 476  
477 477  
478 -**Examples: AT+DATAUP=1**
551 +(((
552 +(% style="color:#037691" %)**Examples: AT+DATAUP=1**
479 479  
480 -Compose the uplink payload with value returns in sequence and send with **Multiply UPLINKs**.
554 +
555 +)))
481 481  
557 +(((
558 +Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**Multiply UPLINKs**.
559 +)))
560 +
561 +(((
482 482  Final Payload is
563 +)))
483 483  
484 -Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA
565 +(((
566 +(% style="color:#4f81bd" %)**Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA**
567 +)))
485 485  
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
569 +1. (((
570 +Battery Info (2 bytes): Battery voltage
571 +)))
572 +1. (((
573 +PAYVER (1 byte): Defined by AT+PAYVER
574 +)))
575 +1. (((
576 +PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling.
577 +)))
578 +1. (((
579 +PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
580 +)))
581 +1. (((
582 +DATA: Valid value: max 6 bytes(US915 version here, Notice*!) for each uplink so each uplink <= 11 bytes. For the last uplink, DATA will might less than 6 bytes
583 +)))
491 491  
492 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image020.png]]
585 +[[image:1653272817147-600.png||height="437" width="717"]]
493 493  
494 -
495 495  So totally there will be 3 uplinks for this sampling, each uplink includes 6 bytes DATA
496 496  
497 -DATA1=RETURN1 Valid Value = 20 20 0a 33 90 41
498 498  
499 -DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= 02 aa 05 81 0a 20
590 +DATA1=RETURN1 Valid Value = (% style="background-color:#4f81bd; color:white" %) 20 20 0a 33 90 41
500 500  
501 -DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 = 20 20 20 2d 30
592 +DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= (% style="background-color:#4f81bd; color:white" %)02 aa 05 81 0a 20
502 502  
594 +DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 =(% style="background-color:#4f81bd; color:white" %) 20 20 20 2d 30
503 503  
504 504  
505 505  Below are the uplink payloads:
506 506  
507 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.png]]
599 +[[image:1653272901032-107.png]]
508 508  
509 509  
510 -Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:
602 +(% style="color:red" %)Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:
511 511  
512 512   ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink ( so 51 -5 = 46 max valid date)
513 513  
... ... @@ -519,143 +519,186 @@
519 519  
520 520  
521 521  
522 -1.
523 -11.
524 -111. Uplink on demand
614 +=== 3.3.5 Uplink on demand ===
525 525  
616 +(((
526 526  Except uplink periodically, RS485-BL is able to uplink on demand. The server sends downlink command to RS485-BL and RS485 will uplink data base on the command.
618 +)))
527 527  
620 +(((
528 528  Downlink control command:
622 +)))
529 529  
530 -[[0x08 command>>path:#downlink_08]]: Poll an uplink with current command set in RS485-BL.
624 +(((
625 +**0x08 command**: Poll an uplink with current command set in RS485-BL.
626 +)))
531 531  
532 -[[0xA8 command>>path:#downlink_A8]]: Send a command to RS485-BL and uplink the output from sensors.
628 +(((
629 +**0xA8 command**: Send a command to RS485-BL and uplink the output from sensors.
533 533  
631 +
632 +)))
534 534  
634 +=== 3.3.6 Uplink on Interrupt ===
535 535  
536 -1.
537 -11.
538 -111. Uplink on Interrupt
636 +Put the interrupt sensor between 3.3v_out and GPIO ext.
539 539  
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]]
638 +[[image:1653273818896-432.png]]
541 541  
640 +
641 +(((
542 542  AT+INTMOD=0  Disable Interrupt
643 +)))
543 543  
645 +(((
544 544  AT+INTMOD=1  Interrupt trigger by rising or falling edge.
647 +)))
545 545  
649 +(((
546 546  AT+INTMOD=2  Interrupt trigger by falling edge. ( Default Value)
651 +)))
547 547  
653 +(((
548 548  AT+INTMOD=3  Interrupt trigger by rising edge.
549 549  
656 +
657 +)))
550 550  
551 -1.
552 -11. Uplink Payload
659 +== 3.4 Uplink Payload ==
553 553  
554 -
555 -|**Size(bytes)**|**2**|**1**|**Length depends on the return from the commands**
556 -|Value|(((
661 +(% border="1" style="background-color:#4f81bd; color:white; width:850px" %)
662 +|**Size(bytes)**|(% style="width:130px" %)**2**|(% style="width:93px" %)**1**|(% style="width:509px" %)**Length depends on the return from the commands**
663 +|Value|(% style="width:130px" %)(((
664 +(((
557 557  Battery(mV)
666 +)))
558 558  
668 +(((
559 559  &
670 +)))
560 560  
672 +(((
561 561  Interrupt _Flag
562 -)))|(((
674 +)))
675 +)))|(% style="width:93px" %)(((
563 563  PAYLOAD_VER
564 564  
565 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.
679 +)))|(% style="width:509px" %)If the valid payload is too long and exceed the maximum support payload length in server, server will show payload not provided in the LoRaWAN server.
567 567  
568 568  Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors.
569 569  
683 +(((
684 +{{{function Decoder(bytes, port) {}}}
685 +)))
570 570  
571 -function Decoder(bytes, port) {
687 +(((
688 +{{{//Payload Formats of RS485-BL Deceive}}}
689 +)))
572 572  
573 -~/~/Payload Formats of RS485-BL Deceive
691 +(((
692 +{{{return {}}}
693 +)))
574 574  
575 -return {
695 +(((
696 +{{{ //Battery,units:V}}}
697 +)))
576 576  
577 - ~/~/Battery,units:V
699 +(((
700 +{{{ BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000,}}}
701 +)))
578 578  
579 - BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000,
703 +(((
704 +{{{ //GPIO_EXTI }}}
705 +)))
580 580  
581 - ~/~/GPIO_EXTI 
707 +(((
708 +{{{ EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE",}}}
709 +)))
582 582  
583 - EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE",
711 +(((
712 +{{{ //payload of version}}}
713 +)))
584 584  
585 - ~/~/payload of version
715 +(((
716 +{{{ Pay_ver:bytes[2],}}}
717 +)))
586 586  
587 - Pay_ver:bytes[2],
719 +(((
720 +{{{ }; }}}
721 +)))
588 588  
589 - };
723 +(((
724 +}
590 590  
591 - }
726 +
727 +)))
592 592  
593 -
594 -
595 -
596 -
597 -
598 -
729 +(((
599 599  TTN V3 uplink screen shot.
731 +)))
600 600  
601 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]
733 +[[image:1653274001211-372.png||height="192" width="732"]]
602 602  
603 -1.
604 -11. Configure RS485-BL via AT or Downlink
605 605  
606 -User can configure RS485-BL via [[AT Commands >>path:#_​Using_the_AT]]or LoRaWAN Downlink Commands
736 +== 3.5 Configure RS485-BL via AT or Downlink ==
607 607  
738 +User can configure RS485-BL via AT Commands or LoRaWAN Downlink Commands
739 +
608 608  There are two kinds of Commands:
609 609  
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
742 +* (% style="color:#4f81bd" %)**Common Commands**(%%): They should be available for each sensor, such as: change uplink interval, reset device. For firmware v1.3, user can find what common commands it supports: [[End Device AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]
611 611  
612 -* **Sensor Related Commands**: These commands are special designed for RS485-BL.  User can see these commands below:
744 +* (% style="color:#4f81bd" %)**Sensor Related Commands**(%%): These commands are special designed for RS485-BL.  User can see these commands below:
613 613  
746 +=== 3.5.1 Common Commands: ===
614 614  
615 -1.
616 -11.
617 -111. Common Commands:
748 +They should be available for each of Dragino Sensors, such as: change uplink interval, reset device. For firmware v1.3, user can find what common commands it supports: [[End Device AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]
618 618  
619 619  
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]]
751 +=== 3.5.2 Sensor related commands: ===
621 621  
753 +==== ====
622 622  
623 -1.
624 -11.
625 -111. Sensor related commands:
755 +==== **Choose Device Type (RS485 or TTL)** ====
626 626  
627 -
628 -==== Choose Device Type (RS485 or TTL) ====
629 -
630 630  RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect.
631 631  
632 -* AT Command
759 +* **AT Command**
633 633  
761 +(% class="box infomessage" %)
762 +(((
634 634  **AT+MOD=1** ~/~/ Set to support RS485-MODBUS type sensors. User can connect multiply RS485 , Modbus sensors to the A / B pins.
764 +)))
635 635  
766 +(% class="box infomessage" %)
767 +(((
636 636  **AT+MOD=2** ~/~/ Set to support TTL Level sensors, User can connect one TTL Sensor to the TXD/RXD/GND pins.
769 +)))
637 637  
638 638  
639 -* Downlink Payload
772 +* **Downlink Payload**
640 640  
641 -**0A aa**     à same as AT+MOD=aa
774 +**0A aa**  ~-~->  same as AT+MOD=aa
642 642  
643 643  
644 644  
645 -==== [[RS485 Debug Command>>path:#downlink_A8]] (AT+CFGDEV) ====
778 +==== **RS485 Debug Command (AT+CFGDEV)** ====
646 646  
647 647  This command is used to configure the RS485 or TTL sensors; they won’t be used during sampling.
648 648  
649 -* AT Command
782 +* **AT Command**
650 650  
651 -AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
784 +(% class="box infomessage" %)
785 +(((
786 +**AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m**
787 +)))
652 652  
653 653  m: 0: no CRC; 1: add CRC-16/MODBUS in the end of this command.
654 654  
655 655  
792 +* **Downlink Payload**
656 656  
657 -* Downlink Payload
658 -
659 659  Format: A8 MM NN XX XX XX XX YY
660 660  
661 661  Where:
... ... @@ -665,20 +665,19 @@
665 665  * XX XX XX XX: RS485 command total NN bytes
666 666  * 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
667 667  
668 -
669 669  **Example 1:**
670 670  
671 671  To connect a Modbus Alarm with below commands.
672 672  
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.
807 +* The command to active alarm is: 0A 05 00 04 00 01 **4C B0**. Where 0A 05 00 04 00 01 is the Modbus command to read the register 00 40 where stored the DI status. The 4C B0 is the CRC-16/MODBUS which calculate manually.
674 674  
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.
809 +* The command to deactivate alarm is: 0A 05 00 04 00 00 **8D 70**. Where 0A 05 00 04 00 00 is the Modbus command to read the register 00 40 where stored the DI status. The 8D 70 is the CRC-16/MODBUS which calculate manually.
676 676  
677 677  So if user want to use downlink command to control to RS485 Alarm, he can use:
678 678  
679 -**A8 01 06 0A 05 00 04 00 01 00**: to activate the RS485 Alarm
813 +(% style="color:#037691" %)**A8 01 06 0A 05 00 04 00 01 00**(%%): to activate the RS485 Alarm
680 680  
681 -**A8 01 06 0A 05 00 04 00 00 00**: to deactivate the RS485 Alarm
815 +(% style="color:#037691" %)**A8 01 06 0A 05 00 04 00 00 00**(%%): to deactivate the RS485 Alarm
682 682  
683 683  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.
684 684  
... ... @@ -687,48 +687,60 @@
687 687  
688 688  Check TTL Sensor return:
689 689  
690 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image024.png]]
824 +[[image:1654132684752-193.png]]
691 691  
692 692  
693 693  
828 +==== **Set Payload version** ====
694 694  
695 -==== Set Payload version ====
696 -
697 697  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.
698 698  
699 -* AT Command:
832 +* **AT Command:**
700 700  
701 -AT+PAYVER: Set PAYVER field = 1
834 +(% class="box infomessage" %)
835 +(((
836 +**AT+PAYVER: Set PAYVER field = 1**
837 +)))
702 702  
703 703  
704 -* Downlink Payload:
840 +* **Downlink Payload:**
705 705  
706 -0xAE 01   à Set PAYVER field =  0x01
842 +**0xAE 01**  ~-~-> Set PAYVER field =  0x01
707 707  
708 -0xAE 0F   à Set PAYVER field =  0x0F
844 +**0xAE 0F**   ~-~-> Set PAYVER field =  0x0F
709 709  
710 710  
711 -==== Set RS485 Sampling Commands ====
712 712  
848 +==== **Set RS485 Sampling Commands** ====
849 +
713 713  AT+COMMANDx, AT+DATACUTx and AT+SEARCHx
714 714  
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]].
852 +These three commands are used to configure how the RS485-BL polling data from Modbus device. Detail of usage please see : [[polling RS485 device>>||anchor="H3.3.3Configurereadcommandsforeachsampling"]].
716 716  
717 717  
718 -* AT Command:
855 +* **AT Command:**
719 719  
720 -AT+COMMANDx: Configure RS485 read command to sensor.
857 +(% class="box infomessage" %)
858 +(((
859 +**AT+COMMANDx: Configure RS485 read command to sensor.**
860 +)))
721 721  
722 -AT+DATACUTx: Configure how to handle return from RS485 devices.
862 +(% class="box infomessage" %)
863 +(((
864 +**AT+DATACUTx: Configure how to handle return from RS485 devices.**
865 +)))
723 723  
724 -AT+SEARCHx: Configure search command
867 +(% class="box infomessage" %)
868 +(((
869 +**AT+SEARCHx: Configure search command**
870 +)))
725 725  
726 726  
727 -* Downlink Payload:
873 +* **Downlink Payload:**
728 728  
729 -0xAF downlink command can be used to set AT+COMMANDx or AT+DATACUTx.
875 +**0xAF** downlink command can be used to set AT+COMMANDx or AT+DATACUTx.
730 730  
731 -Note: if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink.
877 +(% style="color:red" %)**Note**(%%): if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink.
732 732  
733 733  Format: AF MM NN LL XX XX XX XX YY
734 734  
... ... @@ -735,23 +735,23 @@
735 735  Where:
736 736  
737 737  * MM: the ATCOMMAND or AT+DATACUT to be set. Value from 01 ~~ 0F,
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
884 +* NN:  0: no CRC; 1: add CRC-16/MODBUS ; 2: set the AT+DATACUT value.
885 +* LL:  The length of AT+COMMAND or AT+DATACUT command
740 740  * XX XX XX XX: AT+COMMAND or AT+DATACUT 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.
887 +* YY:  If YY=0, RS485-BL will execute the downlink command without uplink; if YY=1, RS485-BL will execute an uplink after got this command.
742 742  
743 -Example:
889 +**Example:**
744 744  
745 -**AF 03 01 06 0A 05 00 04 00 01 00**: Same as AT+COMMAND3=0A 05 00 04 00 01,1
891 +(% style="color:#037691" %)**AF 03 01 06 0A 05 00 04 00 01 00**(%%): Same as AT+COMMAND3=0A 05 00 04 00 01,1
746 746  
747 -**AF 03 02 06 10 01 05 06 09 0A 00**: Same as AT+DATACUT3=**16**,**1**,**5+6+9+10**
893 +(% style="color:#037691" %)**AF 03 02 06**(% style="color:orange" %)** 10 **(% style="color:red" %)**01 **(% style="color:green" %)**05 06 09 0A**(% style="color:#037691" %)** 00**(%%): Same as AT+DATACUT3=(% style="color:orange" %)**16**(%%),(% style="color:red" %)**1**(%%),(% style="color:green" %)**5+6+9+10**
748 748  
749 -**AF 03 02 06 0B 02 05 07 08 0A 00**: Same as AT+DATACUT3=**11**,**2**,**5~~7+8~~10**
895 +(% style="color:#037691" %)**AF 03 02 06 **(% style="color:orange" %)**0B**(% style="color:red" %)** 02 **(% style="color:green" %)**05 07 08 0A **(% style="color:#037691" %)**00**(%%): Same as AT+DATACUT3=(% style="color:orange" %)**11**(%%),(% style="color:red" %)**2**(%%),(% style="color:green" %)**5~~7+8~~10**
750 750  
751 751  
752 -0xAB downlink command can be used for set AT+SEARCHx
898 +**0xAB** downlink command can be used for set AT+SEARCHx
753 753  
754 -Example: **AB aa 01 03 xx xx xx** (03 here means there are total 3 bytes after 03) So
900 +**Example:** **AB aa 01 03 xx xx xx** (03 here means there are total 3 bytes after 03) So
755 755  
756 756  * AB aa 01 03 xx xx xx  same as AT+SEARCHaa=1,xx xx xx
757 757  * 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
... ... @@ -759,334 +759,355 @@
759 759  **AB aa 02 03 xx xx xx 02 yy yy**  same as **AT+SEARCHaa=2,xx xx xx+yy yy**
760 760  
761 761  
762 -==== Fast command to handle MODBUS device ====
763 763  
909 +==== **Fast command to handle MODBUS device** ====
910 +
764 764  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]].
765 765  
766 766  This command is valid since v1.3 firmware version
767 767  
768 768  
769 -AT+MBFUN has only two value:
916 +**AT+MBFUN has only two value:**
770 770  
771 -* AT+MBFUN=1: Enable Modbus reading. And get response base on the MODBUS return
918 +* **AT+MBFUN=1**: Enable Modbus reading. And get response base on the MODBUS return
772 772  
773 773  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.
774 774  
775 -* AT+MBFUN=0: Disable Modbus fast reading.
922 +* **AT+MBFUN=0**: Disable Modbus fast reading.
776 776  
924 +**Example:**
777 777  
778 -Example:
779 -
780 780  * AT+MBFUN=1 and AT+DATACUT1/AT+DATACUT2 are not configure (0,0,0).
781 781  * 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.
782 782  * 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.
783 783  
784 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image025.png]]
930 +[[image:1654133913295-597.png]]
785 785  
786 786  
787 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image026.png]]
933 +[[image:1654133954153-643.png]]
788 788  
789 789  
790 -* Downlink Commands:
936 +* **Downlink Commands:**
791 791  
792 -A9 aa -à Same as AT+MBFUN=aa
938 +**A9 aa** ~-~-> Same as AT+MBFUN=aa
793 793  
794 794  
795 -==== RS485 command timeout ====
796 796  
942 +==== **RS485 command timeout** ====
943 +
797 797  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.
798 798  
799 799  Default value: 0, range:  0 ~~ 5 seconds
800 800  
801 801  
802 -* AT Command:
949 +* **AT Command:**
803 803  
804 -AT+CMDDLaa=hex(bb cc)
951 +(% class="box infomessage" %)
952 +(((
953 +**AT+CMDDLaa=hex(bb cc)**
954 +)))
805 805  
806 -Example:
956 +**Example:**
807 807  
808 808  **AT+CMDDL1=1000** to send the open time to 1000ms
809 809  
810 810  
811 -* Downlink Payload:
961 +* **Downlink Payload:**
812 812  
813 813  0x AA aa bb cc
814 814  
815 815  Same as: AT+CMDDLaa=hex(bb cc)
816 816  
817 - Example:
967 + **Example:**
818 818  
819 - 0xAA 01 03 E8  à Same as **AT+CMDDL1=1000 ms**
969 + **0xAA 01 03 E8**  ~-~-> Same as **AT+CMDDL1=1000 ms**
820 820  
821 821  
822 -==== [[Uplink>>path:#downlink_A8]] payload mode ====
823 823  
973 +==== **Uplink payload mode** ====
974 +
824 824  Define to use one uplink or multiple uplinks for the sampling.
825 825  
826 -The use of this command please see: [[Compose Uplink payload>>path:#DataUP]]
977 +The use of this command please see: [[Compose Uplink payload>>||anchor="H3.3.4Composetheuplinkpayload"]]
827 827  
828 -* AT Command:
979 +* **AT Command:**
829 829  
830 -AT+DATAUP=0
981 +(% class="box infomessage" %)
982 +(((
983 +**AT+DATAUP=0**
984 +)))
831 831  
832 -AT+DATAUP=1
986 +(% class="box infomessage" %)
987 +(((
988 +**AT+DATAUP=1**
989 +)))
833 833  
834 834  
835 -* Downlink Payload:
992 +* **Downlink Payload:**
836 836  
837 -0xAD 00   à Same as AT+DATAUP=0
994 +**0xAD 00**  **~-~->** Same as AT+DATAUP=0
838 838  
839 -0xAD 01   à Same as AT+DATAUP=1
996 +**0xAD 01**  **~-~->** Same as AT+DATAUP=1
840 840  
841 841  
842 -==== Manually trigger an Uplink ====
843 843  
1000 +==== **Manually trigger an Uplink** ====
1001 +
844 844  Ask device to send an uplink immediately.
845 845  
846 -* Downlink Payload:
1004 +* **Downlink Payload:**
847 847  
848 -0x08 FF, RS485-BL will immediately send an uplink.
1006 +**0x08 FF**, RS485-BL will immediately send an uplink.
849 849  
850 850  
851 -==== Clear RS485 Command ====
852 852  
1010 +==== **Clear RS485 Command** ====
1011 +
853 853  The AT+COMMANDx and AT+DATACUTx settings are stored in special location, user can use below command to clear them.
854 854  
855 855  
856 -* AT Command:
1015 +* **AT Command:**
857 857  
858 -**AT+CMDEAR=mm,nn**   mm: start position of erase ,nn: stop position of erase
1017 +(% style="color:#037691" %)**AT+CMDEAR=mm,nn** (%%) mm: start position of erase ,nn: stop position of erase Etc. AT+CMDEAR=1,10 means erase AT+COMMAND1/AT+DATACUT1 to AT+COMMAND10/AT+DATACUT10
859 859  
860 -Etc. AT+CMDEAR=1,10 means erase AT+COMMAND1/AT+DATACUT1 to AT+COMMAND10/AT+DATACUT10
1019 +Example screen shot after clear all RS485 commands. 
861 861  
862 -Example screen shot after clear all RS485 commands.
863 863  
864 -
865 -
866 866  The uplink screen shot is:
867 867  
868 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]
1024 +[[image:1654134704555-320.png]]
869 869  
870 870  
871 -* Downlink Payload:
1027 +* **Downlink Payload:**
872 872  
873 -0x09 aa bb same as AT+CMDEAR=aa,bb
1029 +**0x09 aa bb** same as AT+CMDEAR=aa,bb
874 874  
875 875  
876 -==== Set Serial Communication Parameters ====
877 877  
1033 +==== **Set Serial Communication Parameters** ====
1034 +
878 878  Set the Rs485 serial communication parameters:
879 879  
880 -* AT Command:
1037 +* **AT Command:**
881 881  
882 882  Set Baud Rate:
883 883  
884 -AT+BAUDR=9600    ~/~/ Options: (1200,2400,4800,14400,19200,115200)
1041 +(% class="box infomessage" %)
1042 +(((
1043 +**AT+BAUDR=9600**    ~/~/ Options: (1200,2400,4800,14400,19200,115200)
1044 +)))
885 885  
1046 +Set UART Parity
886 886  
887 -Set UART parity
1048 +(% class="box infomessage" %)
1049 +(((
1050 +**AT+PARITY=0**    ~/~/ Option: 0: no parity, 1: odd parity, 2: even parity
1051 +)))
888 888  
889 -AT+PARITY=0    ~/~/ Option: 0: no parity, 1: odd parity, 2: even parity
890 -
891 -
892 892  Set STOPBIT
893 893  
894 -AT+STOPBIT=0    ~/~/ Option: 0 for 1bit; 1 for 1.5 bit ; 2 for 2 bits
1055 +(% class="box infomessage" %)
1056 +(((
1057 +**AT+STOPBIT=0**    ~/~/ Option: 0 for 1bit; 1 for 1.5 bit ; 2 for 2 bits
1058 +)))
895 895  
896 896  
897 -* Downlink Payload:
1061 +* **Downlink Payload:**
898 898  
899 -A7 01 aa bb: Same  AT+BAUDR=hex(aa bb)*100
1063 +**A7 01 aa bb**: Same  AT+BAUDR=hex(aa bb)*100
900 900  
901 -Example:
1065 +**Example:**
902 902  
903 903  * A7 01 00 60   same as AT+BAUDR=9600
904 904  * A7 01 04 80  same as AT+BAUDR=115200
905 905  
906 -
907 907  A7 02 aa: Same as  AT+PARITY=aa  (aa value: 00 , 01 or 02)
908 908  
909 909  A7 03 aa: Same as  AT+STOPBIT=aa  (aa value: 00 , 01 or 02)
910 910  
911 911  
912 -==== Control output power duration ====
913 913  
1076 +==== **Control output power duration** ====
1077 +
914 914  User can set the output power duration before each sampling.
915 915  
916 -* AT Command:
1080 +* **AT Command:**
917 917  
918 -Example:
1082 +**Example:**
919 919  
920 -AT+3V3T=1000 ~/~/ 3V3 output power will open 1s before each sampling.
1084 +**AT+3V3T=1000**  ~/~/ 3V3 output power will open 1s before each sampling.
921 921  
922 -AT+5VT=1000 ~/~/ +5V output power will open 1s before each sampling.
1086 +**AT+5VT=1000**  ~/~/ +5V output power will open 1s before each sampling.
923 923  
924 924  
925 -* LoRaWAN Downlink Command:
1089 +* **LoRaWAN Downlink Command:**
926 926  
927 -07 01 aa bb  Same as AT+5VT=(aa bb)
1091 +**07 01 aa bb**  Same as AT+5VT=(aa bb)
928 928  
929 -07 02 aa bb  Same as AT+3V3T=(aa bb)
1093 +**07 02 aa bb**  Same as AT+3V3T=(aa bb)
930 930  
931 931  
1096 +== 3.6 Buttons ==
932 932  
1098 +(% border="1" style="background-color:#ffffcc; color:green; width:233px" %)
1099 +|=(% style="width: 89px;" %)**Button**|=(% style="width: 141px;" %)**Feature**
1100 +|(% style="width:89px" %)**RST**|(% style="width:141px" %)Reboot RS485-BL
933 933  
934 -1.
935 -11. Buttons
1102 +== 3.7 +3V3 Output ==
936 936  
937 -
938 -|**Button**|**Feature**
939 -|**RST**|Reboot RS485-BL
940 -
941 -
942 -1.
943 -11. +3V3 Output
944 -
945 945  RS485-BL has a Controllable +3V3 output, user can use this output to power external sensor.
946 946  
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.
1106 +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. 
948 948  
949 -
950 950  The +3V3 output time can be controlled by AT Command.
951 951  
952 -**AT+3V3T=1000**
953 953  
954 -Means set +3v3 valid time to have 1000ms. So, the real +3v3 output will actually have 1000ms + sampling time for other sensors.
1111 +(% style="color:#037691" %)**AT+3V3T=1000**
955 955  
956 956  
1114 +Means set +3v3 valid time to have 1000ms. So, the real +3v3 output will actually have 1000ms + sampling time for other sensors.
1115 +
957 957  By default, the AT+3V3T=0. This is a special case, means the +3V3 output is always on at any time
958 958  
959 959  
960 -1.
961 -11. +5V Output
1119 +== 3.8 +5V Output ==
962 962  
963 963  RS485-BL has a Controllable +5V output, user can use this output to power external sensor.
964 964  
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.
1123 +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. 
966 966  
967 -
968 968  The 5V output time can be controlled by AT Command.
969 969  
970 -**AT+5VT=1000**
971 971  
972 -Means set 5V valid time to have 1000ms. So, the real 5V output will actually have 1000ms + sampling time for other sensors.
1128 +(% style="color:#037691" %)**AT+5VT=1000**
973 973  
974 974  
1131 +Means set 5V valid time to have 1000ms. So, the real 5V output will actually have 1000ms + sampling time for other sensors.
1132 +
975 975  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.
976 976  
977 977  
1136 +== 3.9 LEDs ==
978 978  
1138 +(% border="1" style="background-color:#ffffcc; color:green; width:332px" %)
1139 +|=**LEDs**|=(% style="width: 274px;" %)**Feature**
1140 +|**LED1**|(% style="width:274px" %)Blink when device transmit a packet.
979 979  
980 -1.
981 -11. LEDs
1142 +== 3.10 Switch Jumper ==
982 982  
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**|(((
1144 +(% border="1" style="background-color:#ffffcc; color:green; width:515px" %)
1145 +|=(% style="width: 124px;" %)**Switch Jumper**|=(% style="width: 388px;" %)**Feature**
1146 +|(% style="width:124px" %)**SW1**|(% style="width:388px" %)(((
992 992  ISP position: Upgrade firmware via UART
993 993  
994 994  Flash position: Configure device, check running status.
995 995  )))
996 -|**SW2**|(((
1151 +|(% style="width:124px" %)**SW2**|(% style="width:388px" %)(((
997 997  5V position: set to compatible with 5v I/O.
998 998  
999 999  3.3v position: set to compatible with 3.3v I/O.,
1000 1000  )))
1001 1001  
1002 -+3.3V: is always ON
1157 +**+3.3V**: is always ON
1003 1003  
1004 -+5V: Only open before every sampling. The time is by default, it is AT+5VT=0.  Max open time. 5000 ms.
1159 +**+5V**: Only open before every sampling. The time is by default, it is AT+5VT=0.  Max open time. 5000 ms.
1005 1005  
1006 -1. Case Study
1007 1007  
1162 += 4. Case Study =
1008 1008  
1009 -User can check this URL for some case studies.
1164 +User can check this URL for some case studies: [[APP RS485 COMMUNICATE WITH SENSORS>>doc:Main.Application Note \: Communicate with Different Sensors ----- RS485-LN RS485-BL.WebHome]]
1010 1010  
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]]
1012 1012  
1167 += 5. Use AT Command =
1013 1013  
1169 +== 5.1 Access AT Command ==
1014 1014  
1015 -
1016 -1. Use AT Command
1017 -11. Access AT Command
1018 -
1019 1019  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.
1020 1020  
1021 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image027.png]]
1173 +[[image:1654135840598-282.png]]
1022 1022  
1023 1023  
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:
1176 +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:
1025 1025  
1026 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image028.png]]
1178 +[[image:1654136105500-922.png]]
1027 1027  
1028 1028  
1181 +More detail AT Command manual can be found at [[AT Command Manual>>||anchor="3.5ConfigureRS485-BLviaATorDownlink"]]
1029 1029  
1030 -More detail AT Command manual can be found at [[AT Command Manual>>path:#AT_COMMAND]]
1031 1031  
1184 +== 5.2 Common AT Command Sequence ==
1032 1032  
1186 +=== 5.2.1 Multi-channel ABP mode (Use with SX1301/LG308) ===
1033 1033  
1034 -1.
1035 -11. Common AT Command Sequence
1036 -111. Multi-channel ABP mode (Use with SX1301/LG308)
1037 -
1038 1038  If device has not joined network yet:
1039 1039  
1040 -AT+FDR
1190 +(% class="box infomessage" %)
1191 +(((
1192 +**AT+FDR**
1193 +)))
1041 1041  
1042 -AT+NJM=0
1195 +(% class="box infomessage" %)
1196 +(((
1197 +**AT+NJM=0**
1198 +)))
1043 1043  
1044 -ATZ
1200 +(% class="box infomessage" %)
1201 +(((
1202 +**ATZ**
1203 +)))
1045 1045  
1046 1046  
1047 1047  If device already joined network:
1048 1048  
1049 -AT+NJM=0
1208 +(% class="box infomessage" %)
1209 +(((
1210 +**AT+NJM=0**
1211 +)))
1050 1050  
1051 -ATZ
1213 +(% class="box infomessage" %)
1214 +(((
1215 +**ATZ**
1216 +)))
1052 1052  
1053 -1.
1054 -11.
1055 -111. Single-channel ABP mode (Use with LG01/LG02)
1056 1056  
1057 -AT+FDR   Reset Parameters to Factory Default, Keys Reserve
1219 +=== 5.5.2 Single-channel ABP mode (Use with LG01/LG02) ===
1058 1058  
1059 -AT+NJM=0 Set to ABP mode
1060 1060  
1061 -AT+ADR=0 Set the Adaptive Data Rate Off
1222 +(% style="background-color:#dcdcdc" %)**AT+FDR** (%%) Reset Parameters to Factory Default, Keys Reserve
1062 1062  
1063 -AT+DR=5  Set Data Rate
1224 +(% style="background-color:#dcdcdc" %)**AT+NJM=0 **(%%)Set to ABP mode
1064 1064  
1065 -AT+TDC=60000  Set transmit interval to 60 seconds
1226 +(% style="background-color:#dcdcdc" %)**AT+ADR=0** (%%)Set the Adaptive Data Rate Off
1066 1066  
1067 -AT+CHS=868400000 Set transmit frequency to 868.4Mhz
1228 +(% style="background-color:#dcdcdc" %)**AT+DR=5**  (%%)Set Data Rate
1068 1068  
1069 -AT+RX2FQ=868400000 Set RX2Frequency to 868.4Mhz (according to the result from server)
1230 +(% style="background-color:#dcdcdc" %)**AT+TDC=60000** (%%) Set transmit interval to 60 seconds
1070 1070  
1071 -AT+RX2DR=5  Set RX2DR to match the downlink DR from server. see below
1232 +(% style="background-color:#dcdcdc" %)**AT+CHS=868400000**(%%) Set transmit frequency to 868.4Mhz
1072 1072  
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.
1234 +(% style="background-color:#dcdcdc" %)**AT+RX2FQ=868400000** (%%) Set RX2Frequency to 868.4Mhz (according to the result from server)
1074 1074  
1075 -ATZ          Reset MCU
1236 +(% style="background-color:#dcdcdc" %)**AT+RX2DR=5**  (%%) Set RX2DR to match the downlink DR from server. see below
1076 1076  
1077 -**Note:**
1238 +(% 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.
1078 1078  
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
1240 +(% style="background-color:#dcdcdc" %)**ATZ**       (%%) Reset MCU
1083 1083  
1084 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image029.png]]
1085 1085  
1243 +(% style="color:red" %)**Note:**
1086 1086  
1087 -1. FAQ
1088 -11. How to upgrade the image?
1245 +(% style="color:red" %)1. Make sure the device is set to ABP mode in the IoT Server.
1246 +2. Make sure the LG01/02 gateway RX frequency is exactly the same as AT+CHS setting.
1247 +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.
1248 +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
1089 1089  
1250 +[[image:1654136435598-589.png]]
1251 +
1252 +
1253 += 6. FAQ =
1254 +
1255 +== 6.1 How to upgrade the image? ==
1256 +
1090 1090  The RS485-BL LoRaWAN Controller is shipped with a 3.5mm cable, the cable is used to upload image to RS485-BL to:
1091 1091  
1092 1092  * Support new features
... ... @@ -1093,10 +1093,9 @@
1093 1093  * For bug fix
1094 1094  * Change LoRaWAN bands.
1095 1095  
1096 -
1097 1097  Below shows the hardware connection for how to upload an image to RS485-BL:
1098 1098  
1099 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image030.png]]
1265 +[[image:1654136646995-976.png]]
1100 1100  
1101 1101  **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]].
1102 1102  
... ... @@ -1137,7 +1137,6 @@
1137 1137  1.
1138 1138  11. How many RS485-Slave can RS485-BL connects?
1139 1139  
1140 -
1141 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]].
1142 1142  
1143 1143  
... ... @@ -1148,7 +1148,7 @@
1148 1148  
1149 1149  Please see this link for debug:
1150 1150  
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]]
1316 +[[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]] 
1152 1152  
1153 1153  
1154 1154  
... ... @@ -1163,7 +1163,6 @@
1163 1163  
1164 1164  1. Order Info
1165 1165  
1166 -
1167 1167  **Part Number: RS485-BL-XXX**
1168 1168  
1169 1169  **XXX:**
... ... @@ -1179,7 +1179,6 @@
1179 1179  * **RU864**: frequency bands RU864
1180 1180  * **KZ865: **frequency bands KZ865
1181 1181  
1182 -
1183 1183  1. Packing Info
1184 1184  
1185 1185  **Package Includes**:
... ... @@ -1188,7 +1188,6 @@
1188 1188  * Stick Antenna for LoRa RF part x 1
1189 1189  * Program cable x 1
1190 1190  
1191 -
1192 1192  **Dimension and weight**:
1193 1193  
1194 1194  * Device Size: 13.5 x 7 x 3 cm
... ... @@ -1196,7 +1196,6 @@
1196 1196  * Package Size / pcs : 14.5 x 8 x 5 cm
1197 1197  * Weight / pcs : 170g
1198 1198  
1199 -
1200 1200  1. Support
1201 1201  
1202 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.
1652953055962-143.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +753.5 KB
Content
1652953304999-717.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +139.7 KB
Content
1652953414711-647.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +119.3 KB
Content
1652953462722-299.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +202.7 KB
Content
1652953542269-423.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +118.5 KB
Content
1652953553383-907.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +94.0 KB
Content
1652953568895-172.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +109.3 KB
Content
1652954654347-831.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +138.7 KB
Content
1653271044481-711.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +27.8 KB
Content
1653271276735-972.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +26.6 KB
Content
1653271581490-837.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +138.7 KB
Content
1653271648378-342.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +131.4 KB
Content
1653271657255-576.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +142.6 KB
Content
1653271763403-806.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +27.7 KB
Content
1653272787040-634.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +294.0 KB
Content
1653272817147-600.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +143.3 KB
Content
1653272901032-107.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +197.8 KB
Content
1653273818896-432.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +31.6 KB
Content
1653274001211-372.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +91.4 KB
Content
1654132684752-193.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +22.8 KB
Content
1654133913295-597.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +116.2 KB
Content
1654133954153-643.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +91.2 KB
Content
1654134704555-320.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +91.4 KB
Content
1654135840598-282.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +1.3 MB
Content
1654136105500-922.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +203.7 KB
Content
1654136435598-589.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +158.9 KB
Content
1654136646995-976.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +1.3 MB
Content
image-20220519174512-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +32.2 KB
Content
image-20220519174512-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +42.7 KB
Content
image-20220519174512-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +36.3 KB
Content
image-20220519174512-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +19.1 KB
Content
image-20220602102605-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +102.6 KB
Content