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

Summary

Details

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