Skip to Content
Last modified by Xiaoling on 2025/04/23 15:57
From version 6.1
edited by Xiaoling
on 2022/05/19 17:41
Change comment: Uploaded new attachment "1652953304999-717.png", version {1}
To version 38.2
edited by Xiaoling
on 2022/06/02 10:26
Change comment: There is no comment for this version

Summary

Details

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