Skip to Content
Last modified by Xiaoling on 2025/04/23 15:57
From version 29.33
edited by Xiaoling
on 2022/06/02 08:58
Change comment: There is no comment for this version
To version 4.2
edited by Xiaoling
on 2022/05/19 17:41
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,6 +1,7 @@
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]]
4 4  
5 5  
6 6  
... ... @@ -7,15 +7,12 @@
7 7  **RS485-BL – Waterproof RS485 to LoRaWAN Converter User Manual**
8 8  
9 9  
10 -
11 11  **Table of Contents:**
12 12  
13 -{{toc/}}
14 14  
15 15  
16 16  
17 17  
18 -
19 19  = 1.Introduction =
20 20  
21 21  == 1.1 What is RS485-BL RS485 to LoRaWAN Converter ==
... ... @@ -25,19 +25,19 @@
25 25  )))
26 26  
27 27  (((
28 -The Dragino RS485-BL is a (% style="color:blue" %)**RS485 / UART to LoRaWAN Converter**(%%) for Internet of Things solutions. User can connect RS485 or UART sensor to RS485-BL converter, and configure RS485-BL to periodically read sensor data and upload via LoRaWAN network to IoT server.
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.
29 29  )))
30 30  
31 31  (((
32 -RS485-BL can interface to RS485 sensor, 3.3v/5v UART sensor or interrupt sensor. RS485-BL provides (% style="color:blue" %)**a 3.3v output**(%%) and** (% style="color:blue" %)a 5v output(%%)** to power external sensors. Both output voltages are controllable to minimize the total system power consumption.
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.
33 33  )))
34 34  
35 35  (((
36 -RS485-BL is IP67 (% style="color:blue" %)**waterproof**(%%) and powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), it is designed for long term use for several years.
34 +RS485-BL is IP67 **waterproof** and powered by **8500mAh Li-SOCI2 battery**, it is designed for long term use for several years.
37 37  )))
38 38  
39 39  (((
40 -RS485-BL runs standard (% style="color:blue" %)**LoRaWAN 1.0.3 in Class A**(%%). It can reach long transfer range and easy to integrate with LoRaWAN compatible gateway and IoT server.
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.
41 41  )))
42 42  
43 43  (((
... ... @@ -52,19 +52,18 @@
52 52  Each RS485-BL pre-load with a set of unique keys for LoRaWAN registration, register these keys to LoRaWAN server and it will auto connect after power on.
53 53  )))
54 54  
55 -[[image:1652953304999-717.png||height="424" width="733"]]
53 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image002.png]]
56 56  
57 -
58 -
59 59  == 1.2 Specifications ==
60 60  
61 -
62 62  **Hardware System:**
63 63  
64 64  * STM32L072CZT6 MCU
65 -* SX1276/78 Wireless Chip 
60 +* SX1276/78 Wireless Chip
66 66  * Power Consumption (exclude RS485 device):
67 67  ** Idle: 6uA@3.3v
63 +
64 +*
68 68  ** 20dB Transmit: 130mA@3.3v
69 69  
70 70  **Interface for Model:**
... ... @@ -114,16 +114,13 @@
114 114  * Smart Cities
115 115  * Smart Factory
116 116  
117 -== 1.5 Firmware Change log ==
114 +== 1.5 Firmware Change log ==
118 118  
119 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);"]]
120 120  
121 -
122 122  == 1.6 Hardware Change log ==
123 123  
124 124  (((
125 -
126 -
127 127  v1.4
128 128  )))
129 129  
... ... @@ -147,273 +147,233 @@
147 147  
148 148  (((
149 149  Release version ​​​​​
150 -
151 -
152 152  )))
153 153  
154 154  = 2. Pin mapping and Power ON Device =
155 155  
156 -(((
157 157  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 -)))
159 159  
160 160  [[image:1652953055962-143.png||height="387" width="728"]]
161 161  
152 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image003.png]]
162 162  
163 163  The Left TXD and RXD are TTL interface for external sensor. TTL level is controlled by 3.3/5v Jumper.
164 164  
165 165  
166 -= 3. Operation Mode =
167 167  
168 -== 3.1 How it works? ==
158 +3. Operation Mode
159 +3.1 How it works?
169 169  
170 -(((
171 171  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.
172 172  
173 -
174 -)))
175 175  
176 -== 3.2 Example to join LoRaWAN network ==
164 +1.
165 +11. Example to join LoRaWAN network
177 177  
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. 
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.
179 179  
180 -[[image:1652953414711-647.png||height="337" width="723"]]
169 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image004.png]]
181 181  
182 -(((
171 +
183 183  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 -)))
185 185  
186 -(((
174 +
187 187  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 -)))
189 189  
190 -(((
191 191  **Step 1**: Create a device in TTN V3 with the OTAA keys from RS485-BL.
192 -)))
193 193  
194 -(((
195 195  Each RS485-BL is shipped with a sticker with unique device EUI:
196 -)))
197 197  
198 -[[image:1652953462722-299.png]]
181 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image005.png]]
199 199  
200 -(((
183 +
184 +
185 +
201 201  User can enter this key in their LoRaWAN Server portal. Below is TTN V3 screen shot:
202 -)))
203 203  
204 -(((
205 205  Add APP EUI in the application.
206 -)))
207 207  
190 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image006.png]]
208 208  
209 -[[image:image-20220519174512-1.png]]
192 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image007.png]]
210 210  
211 -[[image:image-20220519174512-2.png||height="328" width="731"]]
194 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image008.png]]
212 212  
213 -[[image:image-20220519174512-3.png||height="556" width="724"]]
196 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image009.png]]
214 214  
215 -[[image:image-20220519174512-4.png]]
216 216  
199 +
200 +
201 +
202 +
203 +
204 +
205 +
206 +
207 +
208 +
209 +
210 +
211 +
212 +
213 +
217 217  You can also choose to create the device manually.
218 218  
219 -[[image:1652953542269-423.png||height="710" width="723"]]
216 +|(((
217 +
218 +)))
220 220  
220 +
221 +
222 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image010.png]]
223 +
221 221  Add APP KEY and DEV EUI
222 222  
223 -[[image:1652953553383-907.png||height="514" width="724"]]
226 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image011.png]]
224 224  
225 225  
226 -(((
227 227  **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 -)))
229 229  
230 -[[image:1652953568895-172.png||height="232" width="724"]]
231 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image012.png]]
231 231  
232 232  
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.
237 237  
238 -
239 -)))
236 +1.
237 +11. Configure Commands to read data
240 240  
241 -=== 3.3.1 onfigure UART settings for RS485 or TTL communication ===
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.
242 242  
241 +
242 +1.
243 +11.
244 +111. Configure UART settings for RS485 or TTL communication
245 +
243 243  RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect.
244 244  
245 -**~1. RS485-MODBUS mode:**
248 +1. RS485-MODBUS mode:
246 246  
247 247  AT+MOD=1 ~/~/ Support RS485-MODBUS type sensors. User can connect multiply RS485 , Modbus sensors to the A / B pins.
248 248  
249 -**2. TTL mode:**
250 250  
253 +1. TTL mode:
254 +
251 251  AT+MOD=2 ~/~/ Support TTL Level sensors, User can connect one TTL Sensor to the TXD/RXD/GND pins.
252 252  
257 +
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 -(% 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 -(((
260 +
261 +|**AT Commands**|**Description**|**Example**
262 +|AT+BAUDR|Set the baud rate (for RS485 connection). Default Value is: 9600.|(((
269 269  AT+BAUDR=9600
270 -)))
271 271  
272 -(((
273 273  Options: (1200,2400,4800,14400,19200,115200)
274 274  )))
275 -)))
276 -|(((
277 -AT+PARITY
278 -)))|(% style="width:285px" %)(((
279 -(((
267 +|AT+PARITY|(((
280 280  Set UART parity (for RS485 connection)
281 -)))
282 282  
283 -(((
284 284  Default Value is: no parity.
285 -)))
286 -)))|(% style="width:347px" %)(((
287 -(((
271 +)))|(((
288 288  AT+PARITY=0
289 -)))
290 290  
291 -(((
292 292  Option: 0: no parity, 1: odd parity, 2: even parity
293 293  )))
294 -)))
295 -|(((
296 -AT+STOPBIT
297 -)))|(% style="width:285px" %)(((
298 -(((
276 +|AT+STOPBIT|(((
299 299  Set serial stopbit (for RS485 connection)
300 -)))
301 301  
302 -(((
303 303  Default Value is: 1bit.
304 -)))
305 -)))|(% style="width:347px" %)(((
306 -(((
280 +)))|(((
307 307  AT+STOPBIT=0 for 1bit
308 -)))
309 309  
310 -(((
311 311  AT+STOPBIT=1 for 1.5 bit
312 -)))
313 313  
314 -(((
315 315  AT+STOPBIT=2 for 2 bits
316 316  )))
317 -)))
318 318  
319 319  
320 -=== 3.3.2 Configure sensors ===
321 321  
322 -(((
323 -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**.
324 -)))
325 325  
326 -(((
327 -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.
328 -)))
329 329  
330 -(% border="1" style="background-color:#ffffcc; color:green; width:806px" %)
331 -|**AT Commands**|(% style="width:418px" %)**Description**|(% style="width:256px" %)**Example**
332 -|AT+CFGDEV|(% style="width:418px" %)(((
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|(((
333 333  This command is used to configure the RS485/TTL devices; they won’t be used during sampling.
334 334  
335 -AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,
305 +AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
336 336  
337 -mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
338 -)))|(% style="width:256px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
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
339 339  
340 -Detail of AT+CFGDEV command see [[AT+CFGDEV detail>>||anchor="HRS485DebugCommand28AT2BCFGDEV29"]].
310 +Detail of AT+CFGDEV command see [[AT+CFGDEV detail>>path:#AT_CFGDEV]].
341 341  
342 342  
343 -=== 3.3.3 Configure read commands for each sampling ===
344 344  
345 -(((
314 +
315 +
316 +1.
317 +11.
318 +111. Configure read commands for each sampling
319 +
346 346  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.
347 -)))
348 348  
349 -(((
322 +
350 350  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.
351 -)))
352 352  
353 -(((
325 +
354 354  To save the LoRaWAN network bandwidth, we might need to read data from different sensors and combine their valid value into a short payload.
355 -)))
356 356  
357 -(((
328 +
358 358  This section describes how to achieve above goals.
359 -)))
360 360  
361 -(((
331 +
362 362  During each sampling, the RS485-BL can support 15 commands to read sensors. And combine the return to one or several uplink payloads.
363 -)))
364 364  
365 -(((
334 +
366 366  **Command from RS485-BL to Sensor:**
367 -)))
368 368  
369 -(((
370 370  RS485-BL can send out pre-set max 15 strings via **AT+COMMAD1**, **ATCOMMAND2**,…, to **AT+COMMANDF** . All commands are of same grammar.
371 -)))
372 372  
373 -(((
339 +
374 374  **Handle return from sensors to RS485-BL**:
375 -)))
376 376  
377 -(((
378 378  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**
379 -)))
380 380  
381 -* (((
382 -**AT+DATACUT**
383 -)))
384 384  
385 -(((
345 +* **AT+DATACUT**
346 +
386 386  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.
387 -)))
388 388  
389 -* (((
390 -**AT+SEARCH**
391 -)))
392 392  
393 -(((
350 +* **AT+SEARCH**
351 +
394 394  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.
395 -)))
396 396  
397 -(((
354 +
398 398  **Define wait timeout:**
399 -)))
400 400  
401 -(((
402 402  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
403 -)))
404 404  
405 -(((
359 +
406 406  After we got the valid value from each RS485 commands, we need to combine them together with the command **AT+DATAUP**.
407 -)))
408 408  
362 +
409 409  **Examples:**
410 410  
411 411  Below are examples for the how above AT Commands works.
412 412  
367 +
413 413  **AT+COMMANDx : **This command will be sent to RS485/TTL devices during each sampling, Max command length is 14 bytes. The grammar is:
414 414  
415 -(% border="1" class="table-bordered" style="background-color:#4f81bd; color:white; width:501px" %)
416 -|(% style="width:498px" %)(((
370 +|(((
417 417  **AT+COMMANDx=xx xx xx xx xx xx xx xx xx xx xx xx,m**
418 418  
419 419  **xx xx xx xx xx xx xx xx xx xx xx xx: The RS485 command to be sent**
... ... @@ -425,180 +425,141 @@
425 425  
426 426  In the RS485-BL, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
427 427  
382 +
428 428  **AT+SEARCHx**: This command defines how to handle the return from AT+COMMANDx.
429 429  
430 -(% border="1" class="table-bordered" style="background-color:#4f81bd; color:white; width:580px" %)
431 -|(% style="width:577px" %)(((
385 +|(((
432 432  **AT+SEARCHx=aa,xx xx xx xx xx**
433 433  
434 434  * **aa: 1: prefix match mode; 2: prefix and suffix match mode**
435 435  * **xx xx xx xx xx: match string. Max 5 bytes for prefix and 5 bytes for suffix**
390 +
391 +
436 436  )))
437 437  
438 -**Examples:**
394 +Examples:
439 439  
440 -1）For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
396 +1. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
441 441  
442 442  If we set AT+SEARCH1=1,1E 56 34.      (max 5 bytes for prefix)
443 443  
444 -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**
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
445 445  
446 -[[image:1653271044481-711.png]]
402 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image013.png]]
447 447  
448 -2）For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
449 449  
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 +
450 450  If we set AT+SEARCH1=2, 1E 56 34+31 00 49
451 451  
452 -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**
409 +Device will search the bytes between 1E 56 34 and 31 00 49. So it is 2e 30 58 5f 36 41 30
453 453  
454 -[[image:1653271276735-972.png]]
411 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image014.png]]
455 455  
413 +
456 456  **AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes.
457 457  
458 -(% style="background-color:#4f81bd; color:white; width:729px" %)
459 -|(% style="width:726px" %)(((
416 +|(((
460 460  **AT+DATACUTx=a,b,c**
461 461  
462 462  * **a: length for the return of AT+COMMAND**
463 463  * **b:1: grab valid value by byte, max 6 bytes. 2: grab valid value by bytes section, max 3 sections.**
464 -* **c: define the position for valid value.  **
421 +* **c: define the position for valid value. **
465 465  )))
466 466  
467 -**Examples:**
424 +Examples:
468 468  
469 469  * Grab bytes:
470 470  
471 -[[image:1653271581490-837.png||height="313" width="722"]]
428 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image015.png]]
472 472  
473 -
474 474  * Grab a section.
475 475  
476 -[[image:1653271648378-342.png||height="326" width="720"]]
432 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image016.png]]
477 477  
478 -
479 479  * Grab different sections.
480 480  
481 -[[image:1653271657255-576.png||height="305" width="730"]]
436 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image017.png]]
482 482  
483 -(((
484 -(% style="color:red" %)**Note:**
485 -)))
486 486  
487 -(((
439 +Note:
440 +
488 488  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.
489 -)))
490 490  
491 -(((
492 -**Example:**
493 -)))
443 +Example:
494 494  
495 -(((
496 -(% style="color:red" %)AT+COMMAND1=11 01 1E D0,0
497 -)))
445 +AT+COMMAND1=11 01 1E D0,0
498 498  
499 -(((
500 -(% style="color:red" %)AT+SEARCH1=1,1E 56 34
501 -)))
447 +AT+SEARCH1=1,1E 56 34
502 502  
503 -(((
504 -(% style="color:red" %)AT+DATACUT1=0,2,1~~5
505 -)))
449 +AT+DATACUT1=0,2,1~~5
506 506  
507 -(((
508 -(% style="color:red" %)Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
509 -)))
451 +Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
510 510  
511 -(((
512 -(% style="color:red" %)String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
513 -)))
453 +String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
514 514  
515 -(((
516 -(% style="color:red" %)Valid payload after DataCUT command: 2e 30 58 5f 36
517 -)))
455 +Valid payload after DataCUT command: 2e 30 58 5f 36
518 518  
519 -[[image:1653271763403-806.png]]
457 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image018.png]]
520 520  
521 521  
522 -=== 3.3.4 Compose the uplink payload ===
523 523  
524 -(((
461 +
462 +1.
463 +11.
464 +111. Compose the uplink payload
465 +
525 525  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.**
526 -)))
527 527  
528 -(((
529 -(% style="color:#037691" %)**Examples: AT+DATAUP=0**
530 -)))
531 531  
532 -(((
533 -Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**A SIGNLE UPLINK**.
534 -)))
469 +**Examples: AT+DATAUP=0**
535 535  
536 -(((
471 +Compose the uplink payload with value returns in sequence and send with **A SIGNLE UPLINK**.
472 +
537 537  Final Payload is
538 -)))
539 539  
540 -(((
541 -(% style="color:#4f81bd" %)**Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx**
542 -)))
475 +Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx
543 543  
544 -(((
545 545  Where PAYVER is defined by AT+PAYVER, below is an example screen shot.
546 -)))
547 547  
548 -[[image:1653272787040-634.png||height="515" width="719"]]
479 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.png]]
549 549  
550 550  
551 551  
552 -(((
553 -(% style="color:#037691" %)**Examples: AT+DATAUP=1**
483 +**Examples: AT+DATAUP=1**
554 554  
555 -
556 -)))
485 +Compose the uplink payload with value returns in sequence and send with **Multiply UPLINKs**.
557 557  
558 -(((
559 -Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**Multiply UPLINKs**.
560 -)))
561 -
562 -(((
563 563  Final Payload is
564 -)))
565 565  
566 -(((
567 -(% style="color:#4f81bd" %)**Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA**
568 -)))
489 +Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA
569 569  
570 -1. (((
571 -Battery Info (2 bytes): Battery voltage
572 -)))
573 -1. (((
574 -PAYVER (1 byte): Defined by AT+PAYVER
575 -)))
576 -1. (((
577 -PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling.
578 -)))
579 -1. (((
580 -PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
581 -)))
582 -1. (((
583 -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
584 -)))
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
585 585  
586 -[[image:1653272817147-600.png||height="437" width="717"]]
497 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image020.png]]
587 587  
499 +
588 588  So totally there will be 3 uplinks for this sampling, each uplink includes 6 bytes DATA
589 589  
590 -DATA1=RETURN1 Valid Value = (% style="background-color:#4f81bd; color:white" %) 20 20 0a 33 90 41
502 +DATA1=RETURN1 Valid Value = 20 20 0a 33 90 41
591 591  
592 -DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= (% style="background-color:#4f81bd; color:white" %)02 aa 05 81 0a 20
504 +DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= 02 aa 05 81 0a 20
593 593  
594 -DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 =(% style="background-color:#4f81bd; color:white" %) 20 20 20 2d 30
506 +DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 = 20 20 20 2d 30
595 595  
508 +
509 +
596 596  Below are the uplink payloads:
597 597  
598 -[[image:1653272901032-107.png]]
512 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.png]]
599 599  
600 -(% style="color:red" %)Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:
601 601  
515 +Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:
516 +
602 602   ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink ( so 51 -5 = 46 max valid date)
603 603  
604 604   * For AU915/AS923 bands, if UplinkDwell time=1, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date).
... ... @@ -607,121 +607,91 @@
607 607  
608 608   ~* For all other bands: max 51 bytes for each uplink  ( so 51 -5 = 46 max valid date).
609 609  
610 -=== 3.3.5 Uplink on demand ===
611 611  
612 -(((
526 +
527 +1.
528 +11.
529 +111. Uplink on demand
530 +
613 613  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.
614 -)))
615 615  
616 -(((
617 617  Downlink control command:
618 -)))
619 619  
620 -(((
621 -**0x08 command**: Poll an uplink with current command set in RS485-BL.
622 -)))
535 +[[0x08 command>>path:#downlink_08]]: Poll an uplink with current command set in RS485-BL.
623 623  
624 -(((
625 -**0xA8 command**: Send a command to RS485-BL and uplink the output from sensors.
626 -)))
537 +[[0xA8 command>>path:#downlink_A8]]: Send a command to RS485-BL and uplink the output from sensors.
627 627  
628 -=== 3.3.6 Uplink on Interrupt ===
629 629  
630 -Put the interrupt sensor between 3.3v_out and GPIO ext.
631 631  
632 -[[image:1653273818896-432.png]]
541 +1.
542 +11.
543 +111. Uplink on Interrupt
633 633  
634 -(((
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]]
546 +
635 635  AT+INTMOD=0  Disable Interrupt
636 -)))
637 637  
638 -(((
639 639  AT+INTMOD=1  Interrupt trigger by rising or falling edge.
640 -)))
641 641  
642 -(((
643 643  AT+INTMOD=2  Interrupt trigger by falling edge. ( Default Value)
644 -)))
645 645  
646 -(((
647 647  AT+INTMOD=3  Interrupt trigger by rising edge.
648 -)))
649 649  
650 -== 3.4 Uplink Payload ==
651 651  
652 -(% border="1" style="background-color:#4f81bd; color:white; width:850px" %)
653 -|**Size(bytes)**|(% style="width:130px" %)**2**|(% style="width:93px" %)**1**|(% style="width:509px" %)**Length depends on the return from the commands**
654 -|Value|(% style="width:130px" %)(((
655 -(((
556 +1.
557 +11. Uplink Payload
558 +
559 +
560 +|**Size(bytes)**|**2**|**1**|**Length depends on the return from the commands**
561 +|Value|(((
656 656  Battery(mV)
657 -)))
658 658  
659 -(((
660 660  &
661 -)))
662 662  
663 -(((
664 664  Interrupt _Flag
665 -)))
666 -)))|(% style="width:93px" %)(((
567 +)))|(((
667 667  PAYLOAD_VER
668 668  
669 669  
670 -)))|(% 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.
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.
671 671  
672 672  Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors.
673 673  
674 -(((
575 +
675 675  function Decoder(bytes, port) {
676 -)))
677 677  
678 -(((
679 679  ~/~/Payload Formats of RS485-BL Deceive
680 -)))
681 681  
682 -(((
683 683  return {
684 -)))
685 685  
686 -(((
687 687   ~/~/Battery,units:V
688 -)))
689 689  
690 -(((
691 691   BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000,
692 -)))
693 693  
694 -(((
695 695   ~/~/GPIO_EXTI 
696 -)))
697 697  
698 -(((
699 699   EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE",
700 -)))
701 701  
702 -(((
703 703   ~/~/payload of version
704 -)))
705 705  
706 -(((
707 707   Pay_ver:bytes[2],
708 -)))
709 709  
710 -(((
711 711   };
712 -)))
713 713  
714 -(((
715 715   }
716 -)))
717 717  
718 -(((
598 +
599 +
600 +
601 +
602 +
603 +
719 719  TTN V3 uplink screen shot.
720 -)))
721 721  
722 -[[image:1653274001211-372.png||height="192" width="732"]]
606 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]
723 723  
724 -== 3.5 Configure RS485-BL via AT or Downlink ==
608 +1.
609 +11. Configure RS485-BL via AT or Downlink
725 725  
726 726  User can configure RS485-BL via [[AT Commands >>path:#_​Using_the_AT]]or LoRaWAN Downlink Commands
727 727  
... ... @@ -731,17 +731,20 @@
731 731  
732 732  * **Sensor Related Commands**: These commands are special designed for RS485-BL.  User can see these commands below:
733 733  
734 -1.
735 -11.
619 +
620 +1.
621 +11.
736 736  111. Common Commands:
737 737  
624 +
738 738  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]]
739 739  
740 740  
741 -1.
742 -11.
628 +1.
629 +11.
743 743  111. Sensor related commands:
744 744  
632 +
745 745  ==== Choose Device Type (RS485 or TTL) ====
746 746  
747 747  RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect.
... ... @@ -782,6 +782,7 @@
782 782  * XX XX XX XX: RS485 command total NN bytes
783 783  * 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
784 784  
673 +
785 785  **Example 1:**
786 786  
787 787  To connect a Modbus Alarm with below commands.
... ... @@ -890,6 +890,7 @@
890 890  
891 891  * AT+MBFUN=0: Disable Modbus fast reading.
892 892  
782 +
893 893  Example:
894 894  
895 895  * AT+MBFUN=1 and AT+DATACUT1/AT+DATACUT2 are not configure (0,0,0).
... ... @@ -974,7 +974,7 @@
974 974  
975 975  Etc. AT+CMDEAR=1,10 means erase AT+COMMAND1/AT+DATACUT1 to AT+COMMAND10/AT+DATACUT10
976 976  
977 -Example screen shot after clear all RS485 commands. 
867 +Example screen shot after clear all RS485 commands.
978 978  
979 979  
980 980  
... ... @@ -1018,6 +1018,7 @@
1018 1018  * A7 01 00 60   same as AT+BAUDR=9600
1019 1019  * A7 01 04 80  same as AT+BAUDR=115200
1020 1020  
911 +
1021 1021  A7 02 aa: Same as  AT+PARITY=aa  (aa value: 00 , 01 or 02)
1022 1022  
1023 1023  A7 03 aa: Same as  AT+STOPBIT=aa  (aa value: 00 , 01 or 02)
... ... @@ -1045,18 +1045,20 @@
1045 1045  
1046 1046  
1047 1047  
1048 -1.
939 +1.
1049 1049  11. Buttons
1050 1050  
942 +
1051 1051  |**Button**|**Feature**
1052 1052  |**RST**|Reboot RS485-BL
1053 1053  
1054 -1.
946 +
947 +1.
1055 1055  11. +3V3 Output
1056 1056  
1057 1057  RS485-BL has a Controllable +3V3 output, user can use this output to power external sensor.
1058 1058  
1059 -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. 
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.
1060 1060  
1061 1061  
1062 1062  The +3V3 output time can be controlled by AT Command.
... ... @@ -1069,12 +1069,12 @@
1069 1069  By default, the AT+3V3T=0. This is a special case, means the +3V3 output is always on at any time
1070 1070  
1071 1071  
1072 -1.
965 +1.
1073 1073  11. +5V Output
1074 1074  
1075 1075  RS485-BL has a Controllable +5V output, user can use this output to power external sensor.
1076 1076  
1077 -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. 
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.
1078 1078  
1079 1079  
1080 1080  The 5V output time can be controlled by AT Command.
... ... @@ -1089,13 +1089,14 @@
1089 1089  
1090 1090  
1091 1091  
1092 -1.
985 +1.
1093 1093  11. LEDs
1094 1094  
1095 1095  |**LEDs**|**Feature**
1096 1096  |**LED1**|Blink when device transmit a packet.
1097 1097  
1098 -1.
991 +
992 +1.
1099 1099  11. Switch Jumper
1100 1100  
1101 1101  |**Switch Jumper**|**Feature**
... ... @@ -1116,6 +1116,7 @@
1116 1116  
1117 1117  1. Case Study
1118 1118  
1013 +
1119 1119  User can check this URL for some case studies.
1120 1120  
1121 1121  [[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]]
... ... @@ -1141,7 +1141,7 @@
1141 1141  
1142 1142  
1143 1143  
1144 -1.
1039 +1.
1145 1145  11. Common AT Command Sequence
1146 1146  111. Multi-channel ABP mode (Use with SX1301/LG308)
1147 1147  
... ... @@ -1160,8 +1160,8 @@
1160 1160  
1161 1161  ATZ
1162 1162  
1163 -1.
1164 -11.
1058 +1.
1059 +11.
1165 1165  111. Single-channel ABP mode (Use with LG01/LG02)
1166 1166  
1167 1167  AT+FDR   Reset Parameters to Factory Default, Keys Reserve
... ... @@ -1203,6 +1203,7 @@
1203 1203  * For bug fix
1204 1204  * Change LoRaWAN bands.
1205 1205  
1101 +
1206 1206  Below shows the hardware connection for how to upload an image to RS485-BL:
1207 1207  
1208 1208  [[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image030.png]]
... ... @@ -1236,7 +1236,7 @@
1236 1236  [[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]]
1237 1237  
1238 1238  
1239 -1.
1135 +1.
1240 1240  11. How to change the LoRa Frequency Bands/Region?
1241 1241  
1242 1242  User can follow the introduction for [[how to upgrade image>>path:#upgrade_image]]. When download the images, choose the required image file for download.
... ... @@ -1243,9 +1243,10 @@
1243 1243  
1244 1244  
1245 1245  
1246 -1.
1142 +1.
1247 1247  11. How many RS485-Slave can RS485-BL connects?
1248 1248  
1145 +
1249 1249  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]].
1250 1250  
1251 1251  
... ... @@ -1256,11 +1256,11 @@
1256 1256  
1257 1257  Please see this link for debug:
1258 1258  
1259 -[[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]] 
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]]
1260 1260  
1261 1261  
1262 1262  
1263 -1.
1160 +1.
1264 1264  11. Why I can’t join TTN V3 in US915 /AU915 bands?
1265 1265  
1266 1266  It might about the channels mapping. Please see for detail.
... ... @@ -1271,6 +1271,7 @@
1271 1271  
1272 1272  1. Order Info
1273 1273  
1171 +
1274 1274  **Part Number: RS485-BL-XXX**
1275 1275  
1276 1276  **XXX:**
... ... @@ -1286,6 +1286,7 @@
1286 1286  * **RU864**: frequency bands RU864
1287 1287  * **KZ865: **frequency bands KZ865
1288 1288  
1187 +
1289 1289  1. Packing Info
1290 1290  
1291 1291  **Package Includes**:
... ... @@ -1294,6 +1294,7 @@
1294 1294  * Stick Antenna for LoRa RF part x 1
1295 1295  * Program cable x 1
1296 1296  
1196 +
1297 1297  **Dimension and weight**:
1298 1298  
1299 1299  * Device Size: 13.5 x 7 x 3 cm
... ... @@ -1301,6 +1301,7 @@
1301 1301  * Package Size / pcs : 14.5 x 8 x 5 cm
1302 1302  * Weight / pcs : 170g
1303 1303  
1204 +
1304 1304  1. Support
1305 1305  
1306 1306  * 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.
1652953304999-717.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -139.7 KB
Content
1652953414711-647.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -119.3 KB
Content
1652953462722-299.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -202.7 KB
Content
1652953542269-423.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -118.5 KB
Content
1652953553383-907.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -94.0 KB
Content
1652953568895-172.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -109.3 KB
Content
1652954654347-831.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -138.7 KB
Content
1653271044481-711.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -27.8 KB
Content
1653271276735-972.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -26.6 KB
Content
1653271581490-837.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -138.7 KB
Content
1653271648378-342.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -131.4 KB
Content
1653271657255-576.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -142.6 KB
Content
1653271763403-806.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -27.7 KB
Content
1653272787040-634.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -294.0 KB
Content
1653272817147-600.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -143.3 KB
Content
1653272901032-107.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -197.8 KB
Content
1653273818896-432.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -31.6 KB
Content
1653274001211-372.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -91.4 KB
Content
image-20220519174512-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -32.2 KB
Content
image-20220519174512-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -42.7 KB
Content
image-20220519174512-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -36.3 KB
Content
image-20220519174512-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -19.1 KB
Content