Skip to Content
Last modified by Xiaoling on 2025/04/23 15:57
From version 29.11
edited by Xiaoling
on 2022/06/01 18:01
Change comment: There is no comment for this version
To version 2.2
edited by Xiaoling
on 2022/05/19 16:07
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,71 +1,60 @@
1 -(% style="text-align:center" %)
2 -[[image:1652947681187-144.png||height="385" width="385"]]
1 +
3 3  
4 4  
4 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image001.jpg]]
5 5  
6 6  
7 +
7 7  **RS485-BL – Waterproof RS485 to LoRaWAN Converter User Manual**
8 8  
9 9  
10 10  
11 -**Table of Contents:**
12 12  
13 -{{toc/}}
14 14  
15 15  
16 16  
17 17  
17 +1. Introduction
18 +11. What is RS485-BL RS485 to LoRaWAN Converter
18 18  
19 -= 1.Introduction =
20 20  
21 -== 1.1 What is RS485-BL RS485 to LoRaWAN Converter ==
21 +The Dragino RS485-BL is a **RS485 / UART to LoRaWAN Converter** for Internet of Things solutions. User can connect RS485 or UART sensor to RS485-BL converter, and configure RS485-BL to periodically read sensor data and upload via LoRaWAN network to IoT server.
22 22  
23 -(((
24 -
25 -)))
26 26  
27 -(((
28 -The Dragino RS485-BL is a **RS485 / UART to LoRaWAN Converter** for Internet of Things solutions. User can connect RS485 or UART sensor to RS485-BL converter, and configure RS485-BL to periodically read sensor data and upload via LoRaWAN network to IoT server.
29 -)))
24 +RS485-BL can interface to RS485 sensor, 3.3v/5v UART sensor or interrupt sensor. RS485-BL provides **a 3.3v output** and** a 5v output** to power external sensors. Both output voltages are controllable to minimize the total system power consumption.
30 30  
31 -(((
32 -RS485-BL can interface to RS485 sensor, 3.3v/5v UART sensor or interrupt sensor. RS485-BL provides **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 -)))
34 34  
35 -(((
36 36  RS485-BL is IP67 **waterproof** and powered by **8500mAh Li-SOCI2 battery**, it is designed for long term use for several years.
37 -)))
38 38  
39 -(((
29 +
40 40  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 -)))
42 42  
43 -(((
32 +
44 44  For data uplink, RS485-BL sends user-defined commands to RS485 devices and gets the return from the RS485 devices. RS485-BL will process these returns data according to user-define rules to get the final payload and upload to LoRaWAN server.
45 -)))
46 46  
47 -(((
35 +
48 48  For data downlink, RS485-BL runs in LoRaWAN Class A. When there is downlink commands from LoRaWAN server, RS485-BL will forward the commands from LoRaWAN server to RS485 devices.
49 -)))
50 50  
51 -(((
38 +
52 52  Each RS485-BL pre-load with a set of unique keys for LoRaWAN registration, register these keys to LoRaWAN server and it will auto connect after power on.
53 -)))
54 54  
55 -[[image:1652953304999-717.png||height="424" width="733"]]
41 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image002.png]]
56 56  
57 -== 1.2 Specifications ==
58 58  
44 +1.
45 +11. Specifications
46 +
59 59  **Hardware System:**
60 60  
61 61  * STM32L072CZT6 MCU
62 -* SX1276/78 Wireless Chip 
50 +* SX1276/78 Wireless Chip
63 63  * Power Consumption (exclude RS485 device):
64 64  ** Idle: 6uA@3.3v
65 65  
66 -*
54 +*
67 67  ** 20dB Transmit: 130mA@3.3v
68 68  
57 +
69 69  **Interface for Model:**
70 70  
71 71  * 1 x RS485 Interface
... ... @@ -75,6 +75,7 @@
75 75  * 1 x Interrupt Interface
76 76  * 1 x Controllable 5V output, max
77 77  
67 +
78 78  **LoRa Spec:**
79 79  
80 80  * Frequency Range:
... ... @@ -91,10 +91,11 @@
91 91  * Built-in bit synchronizer for clock recovery.
92 92  * Preamble detection.
93 93  * 127 dB Dynamic Range RSSI.
94 -* Automatic RF Sense and CAD with ultra-fast AFC. ​​​
84 +* Automatic RF Sense and CAD with ultra-fast AFC.
95 95  
96 -== 1.3 Features ==
97 97  
87 +*
88 +*1. Features
98 98  * LoRaWAN Class A & Class C protocol (default Class A)
99 99  * Frequency Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/IN865/RU864
100 100  * AT Commands to change parameters
... ... @@ -104,8 +104,9 @@
104 104  * Support Modbus protocol
105 105  * Support Interrupt uplink
106 106  
107 -== 1.4 Applications ==
108 108  
99 +*
100 +*1. Applications
109 109  * Smart Buildings & Home Automation
110 110  * Logistics and Supply Chain Management
111 111  * Smart Metering
... ... @@ -114,304 +114,263 @@
114 114  * Smart Factory
115 115  
116 116  
109 +1.
110 +11. Firmware Change log
117 117  
118 -== 1.5 Firmware Change log ==
112 +[[RS485-BL Image files – Download link and Change log>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/RS485-BL/Firmware/]]
119 119  
120 -[[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);"]]
121 121  
115 +1.
116 +11. Hardware Change log
122 122  
123 -== 1.6 Hardware Change log ==
124 124  
125 -(((
126 126  v1.4
127 -)))
128 128  
129 -(((
130 130  ~1. Change Power IC to TPS22916
131 -)))
132 132  
133 133  
134 -(((
135 135  v1.3
136 -)))
137 137  
138 -(((
139 139  ~1. Change JP3 from KF350-8P to KF350-11P, Add one extra interface for I2C and one extra interface for one-wire
140 -)))
141 141  
142 142  
143 -(((
144 144  v1.2
145 -)))
146 146  
147 -(((
148 -Release version ​​​​​
131 +Release version
149 149  
150 -
151 -)))
152 152  
153 -= 2. Pin mapping and Power ON Device =
154 154  
155 -(((
135 +
136 +
137 +1. Pin mapping and Power ON Device
138 +
156 156  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.
157 -)))
158 158  
159 -[[image:1652953055962-143.png||height="387" width="728"]]
160 160  
142 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image003.png]]
161 161  
144 +
145 +
162 162  The Left TXD and RXD are TTL interface for external sensor. TTL level is controlled by 3.3/5v Jumper.
163 163  
164 164  
165 -= 3. Operation Mode =
166 166  
167 -== 3.1 How it works? ==
168 168  
169 -(((
151 +
152 +
153 +1. Operation Mode
154 +11. How it works?
155 +
170 170  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.
171 171  
172 -
173 -)))
174 174  
175 -== 3.2 Example to join LoRaWAN network ==
159 +1.
160 +11. Example to join LoRaWAN network
176 176  
177 -Here shows an example for how to join the TTN V3 Network. Below is the network structure, we use [[LG308>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/140-lg308.html]] as LoRaWAN gateway here. 
162 +Here shows an example for how to join the TTN V3 Network. Below is the network structure, we use [[LG308>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/140-lg308.html]] as LoRaWAN gateway here.
178 178  
179 -[[image:1652953414711-647.png||height="337" width="723"]]
164 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image004.png]]
180 180  
181 -(((
166 +
182 182  The RS485-BL in this example connected to two RS485 devices for demonstration, user can connect to other RS485 devices via the same method.
183 -)))
184 184  
185 -(((
169 +
186 186  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:
187 -)))
188 188  
189 -(((
190 190  **Step 1**: Create a device in TTN V3 with the OTAA keys from RS485-BL.
191 -)))
192 192  
193 -(((
194 194  Each RS485-BL is shipped with a sticker with unique device EUI:
195 -)))
196 196  
197 -[[image:1652953462722-299.png]]
176 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image005.png]]
198 198  
199 -(((
178 +
179 +
180 +
200 200  User can enter this key in their LoRaWAN Server portal. Below is TTN V3 screen shot:
201 -)))
202 202  
203 -(((
204 204  Add APP EUI in the application.
205 -)))
206 206  
185 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image006.png]]
207 207  
187 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image007.png]]
208 208  
189 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image008.png]]
209 209  
210 -[[image:image-20220519174512-1.png]]
191 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image009.png]]
211 211  
212 -[[image:image-20220519174512-2.png||height="328" width="731"]]
213 213  
214 -[[image:image-20220519174512-3.png||height="556" width="724"]]
215 215  
216 -[[image:image-20220519174512-4.png]]
217 217  
196 +
197 +
198 +
199 +
200 +
201 +
202 +
203 +
204 +
205 +
206 +
207 +
208 +
218 218  You can also choose to create the device manually.
219 219  
220 -[[image:1652953542269-423.png||height="710" width="723"]]
211 +|(((
212 +
213 +)))
221 221  
215 +
216 +
217 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image010.png]]
218 +
222 222  Add APP KEY and DEV EUI
223 223  
224 -[[image:1652953553383-907.png||height="514" width="724"]]
221 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image011.png]]
225 225  
226 226  
227 -(((
228 228  **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.
229 -)))
230 230  
231 -[[image:1652953568895-172.png||height="232" width="724"]]
226 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image012.png]]
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 -)))
240 240  
241 -=== 3.3.1 onfigure UART settings for RS485 or TTL communication ===
231 +1.
232 +11. Configure Commands to read data
242 242  
234 +There are plenty of RS485 and TTL level devices in the market and each device has different command to read the valid data. To support these devices in flexible, RS485-BL supports flexible command set. User can use [[AT Commands or LoRaWAN Downlink>>path:#AT_COMMAND]] Command to configure how RS485-BL should read the sensor and how to handle the return from RS485 or TTL sensors.
235 +
236 +
237 +1.
238 +11.
239 +111. Configure UART settings for RS485 or TTL communication
240 +
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:**
243 +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  
248 +1. TTL mode:
249 +
251 251  AT+MOD=2 ~/~/ Support TTL Level sensors, User can connect one TTL Sensor to the TXD/RXD/GND pins.
252 252  
252 +
253 253  RS485-BL default UART settings is **9600, no parity, stop bit 1**. If the sensor has a different settings, user can change the RS485-BL setting to match.
254 254  
255 -(% 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 -(((
255 +
256 +|**AT Commands**|**Description**|**Example**
257 +|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 -(((
262 +|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 -(((
266 +)))|(((
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 -(((
271 +|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 -(((
275 +)))|(((
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 -=== 3.3.2 Configure sensors ===
320 320  
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 -)))
324 324  
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 -)))
328 328  
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" %)(((
286 +
287 +1.
288 +11.
289 +111. Configure sensors
290 +
291 +Some sensors might need to configure before normal operation. User can configure such sensor via PC or through RS485-BL AT Commands AT+CFGDEV.
292 +
293 +
294 +When user issue an AT+CFGDEV command, Each AT+CFGDEV equals to send a command to the RS485 or TTL sensors. This command will only run when user input it and won’t run during each sampling.
295 +
296 +|**AT Commands**|**Description**|**Example**
297 +|AT+CFGDEV|(((
332 332  This command is used to configure the RS485/TTL devices; they won’t be used during sampling.
333 333  
334 -AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,
300 +AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
335 335  
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
302 +m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
303 +)))|AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
338 338  
339 339  Detail of AT+CFGDEV command see [[AT+CFGDEV detail>>path:#AT_CFGDEV]].
340 340  
341 -=== 3.3.3 Configure read commands for each sampling ===
342 342  
343 -(((
308 +
309 +
310 +
311 +1.
312 +11.
313 +111. Configure read commands for each sampling
314 +
344 344  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.
345 -)))
346 346  
347 -(((
317 +
348 348  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.
349 -)))
350 350  
351 -(((
320 +
352 352  To save the LoRaWAN network bandwidth, we might need to read data from different sensors and combine their valid value into a short payload.
353 -)))
354 354  
355 -(((
323 +
356 356  This section describes how to achieve above goals.
357 -)))
358 358  
359 -(((
326 +
360 360  During each sampling, the RS485-BL can support 15 commands to read sensors. And combine the return to one or several uplink payloads.
361 -)))
362 362  
363 -(((
329 +
364 364  **Command from RS485-BL to Sensor:**
365 -)))
366 366  
367 -(((
368 368  RS485-BL can send out pre-set max 15 strings via **AT+COMMAD1**, **ATCOMMAND2**,…, to **AT+COMMANDF** . All commands are of same grammar.
369 -)))
370 370  
371 -(((
334 +
372 372  **Handle return from sensors to RS485-BL**:
373 -)))
374 374  
375 -(((
376 376  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**
377 -)))
378 378  
379 -* (((
380 -**AT+DATACUT**
381 -)))
382 382  
383 -(((
340 +* **AT+DATACUT**
341 +
384 384  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.
385 -)))
386 386  
387 -* (((
388 -**AT+SEARCH**
389 -)))
390 390  
391 -(((
345 +* **AT+SEARCH**
346 +
392 392  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.
393 -)))
394 394  
395 -(((
349 +
396 396  **Define wait timeout:**
397 -)))
398 398  
399 -(((
400 400  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
401 -)))
402 402  
403 -(((
354 +
404 404  After we got the valid value from each RS485 commands, we need to combine them together with the command **AT+DATAUP**.
405 -)))
406 406  
357 +
407 407  **Examples:**
408 408  
409 409  Below are examples for the how above AT Commands works.
410 410  
362 +
411 411  **AT+COMMANDx : **This command will be sent to RS485/TTL devices during each sampling, Max command length is 14 bytes. The grammar is:
412 412  
413 -(% border="1" class="table-bordered" style="background-color:#4f81bd; color:white; width:501px" %)
414 -|(% style="width:498px" %)(((
365 +|(((
415 415  **AT+COMMANDx=xx xx xx xx xx xx xx xx xx xx xx xx,m**
416 416  
417 417  **xx xx xx xx xx xx xx xx xx xx xx xx: The RS485 command to be sent**
... ... @@ -423,43 +423,46 @@
423 423  
424 424  In the RS485-BL, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
425 425  
377 +
426 426  **AT+SEARCHx**: This command defines how to handle the return from AT+COMMANDx.
427 427  
428 -(% border="1" class="table-bordered" style="background-color:#4f81bd; color:white; width:580px" %)
429 -|(% style="width:577px" %)(((
380 +|(((
430 430  **AT+SEARCHx=aa,xx xx xx xx xx**
431 431  
432 432  * **aa: 1: prefix match mode; 2: prefix and suffix match mode**
433 433  * **xx xx xx xx xx: match string. Max 5 bytes for prefix and 5 bytes for suffix**
385 +
386 +
434 434  )))
435 435  
436 -**Examples:**
389 +Examples:
437 437  
438 438  1. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
439 439  
440 440  If we set AT+SEARCH1=1,1E 56 34.      (max 5 bytes for prefix)
441 441  
442 -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**
395 +The valid data will be all bytes after 1E 56 34 , so it is 2e 30 58 5f 36 41 30 31 00 49
443 443  
444 -[[image:1653271044481-711.png]]
397 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image013.png]]
445 445  
399 +
446 446  1. For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
447 447  
448 448  If we set AT+SEARCH1=2, 1E 56 34+31 00 49
449 449  
450 -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**
404 +Device will search the bytes between 1E 56 34 and 31 00 49. So it is 2e 30 58 5f 36 41 30
451 451  
452 -[[image:1653271276735-972.png]]
406 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image014.png]]
453 453  
408 +
454 454  **AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes.
455 455  
456 -(% style="background-color:#4f81bd; color:white; width:729px" %)
457 -|(% style="width:726px" %)(((
411 +|(((
458 458  **AT+DATACUTx=a,b,c**
459 459  
460 460  * **a: length for the return of AT+COMMAND**
461 461  * **b:1: grab valid value by byte, max 6 bytes. 2: grab valid value by bytes section, max 3 sections.**
462 -* **c: define the position for valid value.  **
416 +* **c: define the position for valid value. **
463 463  )))
464 464  
465 465  Examples:
... ... @@ -466,130 +466,95 @@
466 466  
467 467  * Grab bytes:
468 468  
469 -[[image:1653271581490-837.png||height="313" width="722"]]
423 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image015.png]]
470 470  
471 471  * Grab a section.
472 472  
473 -[[image:1653271648378-342.png||height="326" width="720"]]
427 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image016.png]]
474 474  
475 475  * Grab different sections.
476 476  
477 -[[image:1653271657255-576.png||height="305" width="730"]]
431 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image017.png]]
478 478  
479 -(((
480 -(% style="color:red" %)**Note:**
481 -)))
482 482  
483 -(((
434 +Note:
435 +
484 484  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.
485 -)))
486 486  
487 -(((
488 -**Example:**
489 -)))
438 +Example:
490 490  
491 -(((
492 -(% style="color:red" %)AT+COMMAND1=11 01 1E D0,0
493 -)))
440 +AT+COMMAND1=11 01 1E D0,0
494 494  
495 -(((
496 -(% style="color:red" %)AT+SEARCH1=1,1E 56 34
497 -)))
442 +AT+SEARCH1=1,1E 56 34
498 498  
499 -(((
500 -(% style="color:red" %)AT+DATACUT1=0,2,1~~5
501 -)))
444 +AT+DATACUT1=0,2,1~~5
502 502  
503 -(((
504 -(% style="color:red" %)Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
505 -)))
446 +Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
506 506  
507 -(((
508 -(% style="color:red" %)String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
509 -)))
448 +String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
510 510  
511 -(((
512 -(% style="color:red" %)Valid payload after DataCUT command: 2e 30 58 5f 36
513 -)))
450 +Valid payload after DataCUT command: 2e 30 58 5f 36
514 514  
515 -[[image:1653271763403-806.png]]
452 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image018.png]]
516 516  
517 -=== 3.3.4 Compose the uplink payload ===
518 518  
519 -(((
455 +
456 +
457 +1.
458 +11.
459 +111. Compose the uplink payload
460 +
520 520  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.**
521 -)))
522 522  
523 -(((
524 -(% style="color:#4f81bd" %)**Examples: AT+DATAUP=0**
525 -)))
526 526  
527 -(((
528 -Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**A SIGNLE UPLINK**.
529 -)))
464 +**Examples: AT+DATAUP=0**
530 530  
531 -(((
466 +Compose the uplink payload with value returns in sequence and send with **A SIGNLE UPLINK**.
467 +
532 532  Final Payload is
533 -)))
534 534  
535 -(((
536 -(% style="color:#4f81bd" %)Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx
537 -)))
470 +Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx
538 538  
539 -(((
540 540  Where PAYVER is defined by AT+PAYVER, below is an example screen shot.
541 -)))
542 542  
543 -[[image:1653272787040-634.png||height="515" width="719"]]
474 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.png]]
544 544  
545 -(((
546 -(% style="color:#4f81bd" %)**Examples: AT+DATAUP=1**
547 -)))
548 548  
549 -(((
550 -Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**Multiply UPLINKs**.
551 -)))
552 552  
553 -(((
478 +**Examples: AT+DATAUP=1**
479 +
480 +Compose the uplink payload with value returns in sequence and send with **Multiply UPLINKs**.
481 +
554 554  Final Payload is
555 -)))
556 556  
557 -(((
558 -(% style="color:#4f81bd" %)Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA
559 -)))
484 +Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA
560 560  
561 -1. (((
562 -Battery Info (2 bytes): Battery voltage
563 -)))
564 -1. (((
565 -PAYVER (1 byte): Defined by AT+PAYVER
566 -)))
567 -1. (((
568 -PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling.
569 -)))
570 -1. (((
571 -PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
572 -)))
573 -1. (((
574 -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
575 -)))
486 +1. Battery Info (2 bytes): Battery voltage
487 +1. PAYVER (1 byte): Defined by AT+PAYVER
488 +1. PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling.
489 +1. PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
490 +1. DATA: Valid value: max 6 bytes(US915 version here, [[Notice*!>>path:#max_byte]]) for each uplink so each uplink <= 11 bytes. For the last uplink, DATA will might less than 6 bytes
576 576  
577 -[[image:1653272817147-600.png||height="437" width="717"]]
492 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image020.png]]
578 578  
494 +
579 579  So totally there will be 3 uplinks for this sampling, each uplink includes 6 bytes DATA
580 580  
581 -DATA1=RETURN1 Valid Value = (% style="background-color:#4f81bd; color:white" %) 20 20 0a 33 90 41
497 +DATA1=RETURN1 Valid Value = 20 20 0a 33 90 41
582 582  
583 -DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= (% style="background-color:#4f81bd; color:white" %)02 aa 05 81 0a 20
499 +DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= 02 aa 05 81 0a 20
584 584  
585 -DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 =(% style="background-color:#4f81bd; color:white" %) 20 20 20 2d 30
501 +DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 = 20 20 20 2d 30
586 586  
503 +
504 +
587 587  Below are the uplink payloads:
588 588  
589 -[[image:1653272901032-107.png]]
507 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.png]]
590 590  
591 -(% style="color:red" %)Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:
592 592  
510 +Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:
511 +
593 593   ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink ( so 51 -5 = 46 max valid date)
594 594  
595 595   * For AU915/AS923 bands, if UplinkDwell time=1, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date).
... ... @@ -598,121 +598,91 @@
598 598  
599 599   ~* For all other bands: max 51 bytes for each uplink  ( so 51 -5 = 46 max valid date).
600 600  
601 -=== 3.3.5 Uplink on demand ===
602 602  
603 -(((
521 +
522 +1.
523 +11.
524 +111. Uplink on demand
525 +
604 604  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.
605 -)))
606 606  
607 -(((
608 608  Downlink control command:
609 -)))
610 610  
611 -(((
612 -**0x08 command**: Poll an uplink with current command set in RS485-BL.
613 -)))
530 +[[0x08 command>>path:#downlink_08]]: Poll an uplink with current command set in RS485-BL.
614 614  
615 -(((
616 -**0xA8 command**: Send a command to RS485-BL and uplink the output from sensors.
617 -)))
532 +[[0xA8 command>>path:#downlink_A8]]: Send a command to RS485-BL and uplink the output from sensors.
618 618  
619 -=== 3.3.6 Uplink on Interrupt ===
620 620  
621 -Put the interrupt sensor between 3.3v_out and GPIO ext.
622 622  
623 -[[image:1653273818896-432.png]]
536 +1.
537 +11.
538 +111. Uplink on Interrupt
624 624  
625 -(((
540 +Put the interrupt sensor between 3.3v_out and GPIO ext.[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image022.png]]
541 +
626 626  AT+INTMOD=0  Disable Interrupt
627 -)))
628 628  
629 -(((
630 630  AT+INTMOD=1  Interrupt trigger by rising or falling edge.
631 -)))
632 632  
633 -(((
634 634  AT+INTMOD=2  Interrupt trigger by falling edge. ( Default Value)
635 -)))
636 636  
637 -(((
638 638  AT+INTMOD=3  Interrupt trigger by rising edge.
639 -)))
640 640  
641 -== 3.4 Uplink Payload ==
642 642  
643 -(% border="1" style="background-color:#4f81bd; color:white; width:850px" %)
644 -|**Size(bytes)**|(% style="width:130px" %)**2**|(% style="width:93px" %)**1**|(% style="width:509px" %)**Length depends on the return from the commands**
645 -|Value|(% style="width:130px" %)(((
646 -(((
551 +1.
552 +11. Uplink Payload
553 +
554 +
555 +|**Size(bytes)**|**2**|**1**|**Length depends on the return from the commands**
556 +|Value|(((
647 647  Battery(mV)
648 -)))
649 649  
650 -(((
651 651  &
652 -)))
653 653  
654 -(((
655 655  Interrupt _Flag
656 -)))
657 -)))|(% style="width:93px" %)(((
562 +)))|(((
658 658  PAYLOAD_VER
659 659  
660 660  
661 -)))|(% 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.
566 +)))|If the valid payload is too long and exceed the maximum support payload length in server, server will show payload not provided in the LoRaWAN server.
662 662  
663 663  Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors.
664 664  
665 -(((
570 +
666 666  function Decoder(bytes, port) {
667 -)))
668 668  
669 -(((
670 670  ~/~/Payload Formats of RS485-BL Deceive
671 -)))
672 672  
673 -(((
674 674  return {
675 -)))
676 676  
677 -(((
678 678   ~/~/Battery,units:V
679 -)))
680 680  
681 -(((
682 682   BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000,
683 -)))
684 684  
685 -(((
686 686   ~/~/GPIO_EXTI 
687 -)))
688 688  
689 -(((
690 690   EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE",
691 -)))
692 692  
693 -(((
694 694   ~/~/payload of version
695 -)))
696 696  
697 -(((
698 698   Pay_ver:bytes[2],
699 -)))
700 700  
701 -(((
702 702   };
703 -)))
704 704  
705 -(((
706 706   }
707 -)))
708 708  
709 -(((
593 +
594 +
595 +
596 +
597 +
598 +
710 710  TTN V3 uplink screen shot.
711 -)))
712 712  
713 -[[image:1653274001211-372.png||height="192" width="732"]]
601 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]
714 714  
715 -== 3.5 Configure RS485-BL via AT or Downlink ==
603 +1.
604 +11. Configure RS485-BL via AT or Downlink
716 716  
717 717  User can configure RS485-BL via [[AT Commands >>path:#_​Using_the_AT]]or LoRaWAN Downlink Commands
718 718  
... ... @@ -722,17 +722,20 @@
722 722  
723 723  * **Sensor Related Commands**: These commands are special designed for RS485-BL.  User can see these commands below:
724 724  
725 -1.
726 -11.
614 +
615 +1.
616 +11.
727 727  111. Common Commands:
728 728  
619 +
729 729  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]]
730 730  
731 731  
732 -1.
733 -11.
623 +1.
624 +11.
734 734  111. Sensor related commands:
735 735  
627 +
736 736  ==== Choose Device Type (RS485 or TTL) ====
737 737  
738 738  RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect.
... ... @@ -773,6 +773,7 @@
773 773  * XX XX XX XX: RS485 command total NN bytes
774 774  * 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
775 775  
668 +
776 776  **Example 1:**
777 777  
778 778  To connect a Modbus Alarm with below commands.
... ... @@ -881,6 +881,7 @@
881 881  
882 882  * AT+MBFUN=0: Disable Modbus fast reading.
883 883  
777 +
884 884  Example:
885 885  
886 886  * AT+MBFUN=1 and AT+DATACUT1/AT+DATACUT2 are not configure (0,0,0).
... ... @@ -965,7 +965,7 @@
965 965  
966 966  Etc. AT+CMDEAR=1,10 means erase AT+COMMAND1/AT+DATACUT1 to AT+COMMAND10/AT+DATACUT10
967 967  
968 -Example screen shot after clear all RS485 commands. 
862 +Example screen shot after clear all RS485 commands.
969 969  
970 970  
971 971  
... ... @@ -1009,6 +1009,7 @@
1009 1009  * A7 01 00 60   same as AT+BAUDR=9600
1010 1010  * A7 01 04 80  same as AT+BAUDR=115200
1011 1011  
906 +
1012 1012  A7 02 aa: Same as  AT+PARITY=aa  (aa value: 00 , 01 or 02)
1013 1013  
1014 1014  A7 03 aa: Same as  AT+STOPBIT=aa  (aa value: 00 , 01 or 02)
... ... @@ -1036,18 +1036,20 @@
1036 1036  
1037 1037  
1038 1038  
1039 -1.
934 +1.
1040 1040  11. Buttons
1041 1041  
937 +
1042 1042  |**Button**|**Feature**
1043 1043  |**RST**|Reboot RS485-BL
1044 1044  
1045 -1.
941 +
942 +1.
1046 1046  11. +3V3 Output
1047 1047  
1048 1048  RS485-BL has a Controllable +3V3 output, user can use this output to power external sensor.
1049 1049  
1050 -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. 
947 +The +3V3 output will be valid for every sampling. RS485-BL will enable +3V3 output before all sampling and disable the +3V3 after all sampling.
1051 1051  
1052 1052  
1053 1053  The +3V3 output time can be controlled by AT Command.
... ... @@ -1060,12 +1060,12 @@
1060 1060  By default, the AT+3V3T=0. This is a special case, means the +3V3 output is always on at any time
1061 1061  
1062 1062  
1063 -1.
960 +1.
1064 1064  11. +5V Output
1065 1065  
1066 1066  RS485-BL has a Controllable +5V output, user can use this output to power external sensor.
1067 1067  
1068 -The +5V output will be valid for every sampling. RS485-BL will enable +5V output before all sampling and disable the +5v after all sampling. 
965 +The +5V output will be valid for every sampling. RS485-BL will enable +5V output before all sampling and disable the +5v after all sampling.
1069 1069  
1070 1070  
1071 1071  The 5V output time can be controlled by AT Command.
... ... @@ -1080,13 +1080,14 @@
1080 1080  
1081 1081  
1082 1082  
1083 -1.
980 +1.
1084 1084  11. LEDs
1085 1085  
1086 1086  |**LEDs**|**Feature**
1087 1087  |**LED1**|Blink when device transmit a packet.
1088 1088  
1089 -1.
986 +
987 +1.
1090 1090  11. Switch Jumper
1091 1091  
1092 1092  |**Switch Jumper**|**Feature**
... ... @@ -1107,6 +1107,7 @@
1107 1107  
1108 1108  1. Case Study
1109 1109  
1008 +
1110 1110  User can check this URL for some case studies.
1111 1111  
1112 1112  [[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]]
... ... @@ -1132,7 +1132,7 @@
1132 1132  
1133 1133  
1134 1134  
1135 -1.
1034 +1.
1136 1136  11. Common AT Command Sequence
1137 1137  111. Multi-channel ABP mode (Use with SX1301/LG308)
1138 1138  
... ... @@ -1151,8 +1151,8 @@
1151 1151  
1152 1152  ATZ
1153 1153  
1154 -1.
1155 -11.
1053 +1.
1054 +11.
1156 1156  111. Single-channel ABP mode (Use with LG01/LG02)
1157 1157  
1158 1158  AT+FDR   Reset Parameters to Factory Default, Keys Reserve
... ... @@ -1194,6 +1194,7 @@
1194 1194  * For bug fix
1195 1195  * Change LoRaWAN bands.
1196 1196  
1096 +
1197 1197  Below shows the hardware connection for how to upload an image to RS485-BL:
1198 1198  
1199 1199  [[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image030.png]]
... ... @@ -1227,7 +1227,7 @@
1227 1227  [[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]]
1228 1228  
1229 1229  
1230 -1.
1130 +1.
1231 1231  11. How to change the LoRa Frequency Bands/Region?
1232 1232  
1233 1233  User can follow the introduction for [[how to upgrade image>>path:#upgrade_image]]. When download the images, choose the required image file for download.
... ... @@ -1234,9 +1234,10 @@
1234 1234  
1235 1235  
1236 1236  
1237 -1.
1137 +1.
1238 1238  11. How many RS485-Slave can RS485-BL connects?
1239 1239  
1140 +
1240 1240  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]].
1241 1241  
1242 1242  
... ... @@ -1247,11 +1247,11 @@
1247 1247  
1248 1248  Please see this link for debug:
1249 1249  
1250 -[[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]] 
1151 +[[http:~~/~~/wiki.dragino.com/index.php?title=Main_Page#LoRaWAN_Communication_Debug>>url:http://wiki.dragino.com/index.php?title=Main_Page#LoRaWAN_Communication_Debug]]
1251 1251  
1252 1252  
1253 1253  
1254 -1.
1155 +1.
1255 1255  11. Why I can’t join TTN V3 in US915 /AU915 bands?
1256 1256  
1257 1257  It might about the channels mapping. Please see for detail.
... ... @@ -1262,6 +1262,7 @@
1262 1262  
1263 1263  1. Order Info
1264 1264  
1166 +
1265 1265  **Part Number: RS485-BL-XXX**
1266 1266  
1267 1267  **XXX:**
... ... @@ -1277,6 +1277,7 @@
1277 1277  * **RU864**: frequency bands RU864
1278 1278  * **KZ865: **frequency bands KZ865
1279 1279  
1182 +
1280 1280  1. Packing Info
1281 1281  
1282 1282  **Package Includes**:
... ... @@ -1285,6 +1285,7 @@
1285 1285  * Stick Antenna for LoRa RF part x 1
1286 1286  * Program cable x 1
1287 1287  
1191 +
1288 1288  **Dimension and weight**:
1289 1289  
1290 1290  * Device Size: 13.5 x 7 x 3 cm
... ... @@ -1292,6 +1292,7 @@
1292 1292  * Package Size / pcs : 14.5 x 8 x 5 cm
1293 1293  * Weight / pcs : 170g
1294 1294  
1199 +
1295 1295  1. Support
1296 1296  
1297 1297  * 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.
1652947681187-144.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -166.9 KB
Content
1652953055962-143.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -753.5 KB
Content
1652953304999-717.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -139.7 KB
Content
1652953414711-647.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -119.3 KB
Content
1652953462722-299.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -202.7 KB
Content
1652953542269-423.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -118.5 KB
Content
1652953553383-907.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -94.0 KB
Content
1652953568895-172.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -109.3 KB
Content
1652954654347-831.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -138.7 KB
Content
1653271044481-711.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -27.8 KB
Content
1653271276735-972.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -26.6 KB
Content
1653271581490-837.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -138.7 KB
Content
1653271648378-342.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -131.4 KB
Content
1653271657255-576.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -142.6 KB
Content
1653271763403-806.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -27.7 KB
Content
1653272787040-634.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -294.0 KB
Content
1653272817147-600.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -143.3 KB
Content
1653272901032-107.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -197.8 KB
Content
1653273818896-432.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -31.6 KB
Content
1653274001211-372.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -91.4 KB
Content
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