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

Summary

Details

Page properties
Content
... ... @@ -1,6 +1,7 @@
1 1  (% style="text-align:center" %)
2 2  [[image:1652947681187-144.png||height="385" width="385"]]
3 3  
4 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image001.jpg]]
4 4  
5 5  
6 6  
... ... @@ -7,15 +7,12 @@
7 7  **RS485-BL – Waterproof RS485 to LoRaWAN Converter User Manual**
8 8  
9 9  
10 -
11 11  **Table of Contents:**
12 12  
13 -{{toc/}}
14 14  
15 15  
16 16  
17 17  
18 -
19 19  = 1.Introduction =
20 20  
21 21  == 1.1 What is RS485-BL RS485 to LoRaWAN Converter ==
... ... @@ -29,7 +29,7 @@
29 29  )))
30 30  
31 31  (((
32 -RS485-BL can interface to RS485 sensor, 3.3v/5v UART sensor or interrupt sensor. RS485-BL provides **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 +RS485-BL can interface to RS485 sensor, 3.3v/5v UART sensor or interrupt sensor. RS485-BL provides **a 3.3v output** and** a 5v output** to power external sensors. Both output voltages are controllable to minimize the total system power consumption.
33 33  )))
34 34  
35 35  (((
... ... @@ -52,7 +52,7 @@
52 52  Each RS485-BL pre-load with a set of unique keys for LoRaWAN registration, register these keys to LoRaWAN server and it will auto connect after power on.
53 53  )))
54 54  
55 -[[image:1652953304999-717.png||height="424" width="733"]]
53 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image002.png]]
56 56  
57 57  == 1.2 Specifications ==
58 58  
... ... @@ -59,11 +59,11 @@
59 59  **Hardware System:**
60 60  
61 61  * STM32L072CZT6 MCU
62 -* SX1276/78 Wireless Chip 
60 +* SX1276/78 Wireless Chip
63 63  * Power Consumption (exclude RS485 device):
64 64  ** Idle: 6uA@3.3v
65 65  
66 -*
64 +*
67 67  ** 20dB Transmit: 130mA@3.3v
68 68  
69 69  **Interface for Model:**
... ... @@ -113,7 +113,7 @@
113 113  * Smart Cities
114 114  * Smart Factory
115 115  
116 -== 1.5 Firmware Change log ==
114 +== 1.5 Firmware Change log ==
117 117  
118 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/||style="background-color: rgb(255, 255, 255);"]]
119 119  
... ... @@ -147,265 +147,229 @@
147 147  
148 148  = 2. Pin mapping and Power ON Device =
149 149  
150 -(((
151 151  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.
152 -)))
153 153  
154 154  [[image:1652953055962-143.png||height="387" width="728"]]
155 155  
152 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image003.png]]
156 156  
157 157  The Left TXD and RXD are TTL interface for external sensor. TTL level is controlled by 3.3/5v Jumper.
158 158  
159 -= 3. Operation Mode =
160 160  
161 -== 3.1 How it works? ==
162 162  
163 -(((
158 +3. Operation Mode
159 +3.1 How it works?
160 +
164 164  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.
165 165  
166 -
167 -)))
168 168  
169 -== 3.2 Example to join LoRaWAN network ==
164 +1.
165 +11. Example to join LoRaWAN network
170 170  
171 -Here shows an example for how to join the TTN V3 Network. Below is the network structure, we use [[LG308>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/140-lg308.html]] as LoRaWAN gateway here. 
167 +Here shows an example for how to join the TTN V3 Network. Below is the network structure, we use [[LG308>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/140-lg308.html]] as LoRaWAN gateway here.
172 172  
173 -[[image:1652953414711-647.png||height="337" width="723"]]
169 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image004.png]]
174 174  
175 -(((
171 +
176 176  The RS485-BL in this example connected to two RS485 devices for demonstration, user can connect to other RS485 devices via the same method.
177 -)))
178 178  
179 -(((
174 +
180 180  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:
181 -)))
182 182  
183 -(((
184 184  **Step 1**: Create a device in TTN V3 with the OTAA keys from RS485-BL.
185 -)))
186 186  
187 -(((
188 188  Each RS485-BL is shipped with a sticker with unique device EUI:
189 -)))
190 190  
191 -[[image:1652953462722-299.png]]
181 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image005.png]]
192 192  
193 -(((
183 +
184 +
185 +
194 194  User can enter this key in their LoRaWAN Server portal. Below is TTN V3 screen shot:
195 -)))
196 196  
197 -(((
198 198  Add APP EUI in the application.
199 -)))
200 200  
190 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image006.png]]
201 201  
192 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image007.png]]
202 202  
194 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image008.png]]
203 203  
204 -[[image:image-20220519174512-1.png]]
196 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image009.png]]
205 205  
206 -[[image:image-20220519174512-2.png||height="328" width="731"]]
207 207  
208 -[[image:image-20220519174512-3.png||height="556" width="724"]]
209 209  
210 -[[image:image-20220519174512-4.png]]
211 211  
201 +
202 +
203 +
204 +
205 +
206 +
207 +
208 +
209 +
210 +
211 +
212 +
213 +
212 212  You can also choose to create the device manually.
213 213  
214 -[[image:1652953542269-423.png||height="710" width="723"]]
216 +|(((
217 +
218 +)))
215 215  
220 +
221 +
222 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image010.png]]
223 +
216 216  Add APP KEY and DEV EUI
217 217  
218 -[[image:1652953553383-907.png||height="514" width="724"]]
226 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image011.png]]
219 219  
220 220  
221 -(((
222 222  **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.
223 -)))
224 224  
225 -[[image:1652953568895-172.png||height="232" width="724"]]
231 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image012.png]]
226 226  
227 -== 3.3 Configure Commands to read data ==
228 228  
229 -(((
230 -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.
231 231  
232 -
233 -)))
234 234  
235 -=== 3.3.1 onfigure UART settings for RS485 or TTL communication ===
236 +1.
237 +11. Configure Commands to read data
236 236  
239 +There are plenty of RS485 and TTL level devices in the market and each device has different command to read the valid data. To support these devices in flexible, RS485-BL supports flexible command set. User can use [[AT Commands or LoRaWAN Downlink>>path:#AT_COMMAND]] Command to configure how RS485-BL should read the sensor and how to handle the return from RS485 or TTL sensors.
240 +
241 +
242 +1.
243 +11.
244 +111. Configure UART settings for RS485 or TTL communication
245 +
237 237  RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect.
238 238  
239 -**~1. RS485-MODBUS mode:**
248 +1. RS485-MODBUS mode:
240 240  
241 241  AT+MOD=1 ~/~/ Support RS485-MODBUS type sensors. User can connect multiply RS485 , Modbus sensors to the A / B pins.
242 242  
243 -**2. TTL mode:**
244 244  
253 +1. TTL mode:
254 +
245 245  AT+MOD=2 ~/~/ Support TTL Level sensors, User can connect one TTL Sensor to the TXD/RXD/GND pins.
246 246  
257 +
247 247  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.
248 248  
249 -(% border="1" style="background-color:#ffffcc; color:green; width:795px" %)
250 -|(((
251 -**AT Commands**
252 -)))|(% style="width:285px" %)(((
253 -**Description**
254 -)))|(% style="width:347px" %)(((
255 -**Example**
256 -)))
257 -|(((
258 -AT+BAUDR
259 -)))|(% style="width:285px" %)(((
260 -Set the baud rate (for RS485 connection). Default Value is: 9600.
261 -)))|(% style="width:347px" %)(((
262 -(((
260 +
261 +|**AT Commands**|**Description**|**Example**
262 +|AT+BAUDR|Set the baud rate (for RS485 connection). Default Value is: 9600.|(((
263 263  AT+BAUDR=9600
264 -)))
265 265  
266 -(((
267 267  Options: (1200,2400,4800,14400,19200,115200)
268 268  )))
269 -)))
270 -|(((
271 -AT+PARITY
272 -)))|(% style="width:285px" %)(((
273 -(((
267 +|AT+PARITY|(((
274 274  Set UART parity (for RS485 connection)
275 -)))
276 276  
277 -(((
278 278  Default Value is: no parity.
279 -)))
280 -)))|(% style="width:347px" %)(((
281 -(((
271 +)))|(((
282 282  AT+PARITY=0
283 -)))
284 284  
285 -(((
286 286  Option: 0: no parity, 1: odd parity, 2: even parity
287 287  )))
288 -)))
289 -|(((
290 -AT+STOPBIT
291 -)))|(% style="width:285px" %)(((
292 -(((
276 +|AT+STOPBIT|(((
293 293  Set serial stopbit (for RS485 connection)
294 -)))
295 295  
296 -(((
297 297  Default Value is: 1bit.
298 -)))
299 -)))|(% style="width:347px" %)(((
300 -(((
280 +)))|(((
301 301  AT+STOPBIT=0 for 1bit
302 -)))
303 303  
304 -(((
305 305  AT+STOPBIT=1 for 1.5 bit
306 -)))
307 307  
308 -(((
309 309  AT+STOPBIT=2 for 2 bits
310 310  )))
311 -)))
312 312  
313 -=== 3.3.2 Configure sensors ===
314 314  
315 -(((
316 -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**.
317 -)))
318 318  
319 -(((
320 -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.
321 -)))
322 322  
323 -(% border="1" style="background-color:#ffffcc; color:green; width:806px" %)
324 -|**AT Commands**|(% style="width:418px" %)**Description**|(% style="width:256px" %)**Example**
325 -|AT+CFGDEV|(% style="width:418px" %)(((
291 +
292 +1.
293 +11.
294 +111. Configure sensors
295 +
296 +Some sensors might need to configure before normal operation. User can configure such sensor via PC or through RS485-BL AT Commands AT+CFGDEV.
297 +
298 +
299 +When user issue an AT+CFGDEV command, Each AT+CFGDEV equals to send a command to the RS485 or TTL sensors. This command will only run when user input it and won’t run during each sampling.
300 +
301 +|**AT Commands**|**Description**|**Example**
302 +|AT+CFGDEV|(((
326 326  This command is used to configure the RS485/TTL devices; they won’t be used during sampling.
327 327  
328 -AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,
305 +AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
329 329  
330 -mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
331 -)))|(% style="width:256px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
307 +m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
308 +)))|AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
332 332  
333 333  Detail of AT+CFGDEV command see [[AT+CFGDEV detail>>path:#AT_CFGDEV]].
334 334  
335 -=== 3.3.3 Configure read commands for each sampling ===
336 336  
337 -(((
313 +
314 +
315 +
316 +1.
317 +11.
318 +111. Configure read commands for each sampling
319 +
338 338  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.
339 -)))
340 340  
341 -(((
322 +
342 342  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.
343 -)))
344 344  
345 -(((
325 +
346 346  To save the LoRaWAN network bandwidth, we might need to read data from different sensors and combine their valid value into a short payload.
347 -)))
348 348  
349 -(((
328 +
350 350  This section describes how to achieve above goals.
351 -)))
352 352  
353 -(((
331 +
354 354  During each sampling, the RS485-BL can support 15 commands to read sensors. And combine the return to one or several uplink payloads.
355 -)))
356 356  
357 -(((
334 +
358 358  **Command from RS485-BL to Sensor:**
359 -)))
360 360  
361 -(((
362 362  RS485-BL can send out pre-set max 15 strings via **AT+COMMAD1**, **ATCOMMAND2**,…, to **AT+COMMANDF** . All commands are of same grammar.
363 -)))
364 364  
365 -(((
339 +
366 366  **Handle return from sensors to RS485-BL**:
367 -)))
368 368  
369 -(((
370 370  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**
371 -)))
372 372  
373 -* (((
374 -**AT+DATACUT**
375 -)))
376 376  
377 -(((
345 +* **AT+DATACUT**
346 +
378 378  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.
379 -)))
380 380  
381 -* (((
382 -**AT+SEARCH**
383 -)))
384 384  
385 -(((
350 +* **AT+SEARCH**
351 +
386 386  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.
387 -)))
388 388  
389 -(((
354 +
390 390  **Define wait timeout:**
391 -)))
392 392  
393 -(((
394 394  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
395 -)))
396 396  
397 -(((
359 +
398 398  After we got the valid value from each RS485 commands, we need to combine them together with the command **AT+DATAUP**.
399 -)))
400 400  
362 +
401 401  **Examples:**
402 402  
403 403  Below are examples for the how above AT Commands works.
404 404  
367 +
405 405  **AT+COMMANDx : **This command will be sent to RS485/TTL devices during each sampling, Max command length is 14 bytes. The grammar is:
406 406  
407 -(% border="1" class="table-bordered" style="background-color:#4f81bd; color:white; width:501px" %)
408 -|(% style="width:498px" %)(((
370 +|(((
409 409  **AT+COMMANDx=xx xx xx xx xx xx xx xx xx xx xx xx,m**
410 410  
411 411  **xx xx xx xx xx xx xx xx xx xx xx xx: The RS485 command to be sent**
... ... @@ -417,43 +417,46 @@
417 417  
418 418  In the RS485-BL, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
419 419  
382 +
420 420  **AT+SEARCHx**: This command defines how to handle the return from AT+COMMANDx.
421 421  
422 -(% border="1" class="table-bordered" style="background-color:#4f81bd; color:white; width:580px" %)
423 -|(% style="width:577px" %)(((
385 +|(((
424 424  **AT+SEARCHx=aa,xx xx xx xx xx**
425 425  
426 426  * **aa: 1: prefix match mode; 2: prefix and suffix match mode**
427 427  * **xx xx xx xx xx: match string. Max 5 bytes for prefix and 5 bytes for suffix**
390 +
391 +
428 428  )))
429 429  
430 -**Examples:**
394 +Examples:
431 431  
432 432  1. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
433 433  
434 434  If we set AT+SEARCH1=1,1E 56 34.      (max 5 bytes for prefix)
435 435  
436 -The valid data will be all bytes after 1E 56 34 , so it is (% style="background-color:yellow" %)**2e 30 58 5f 36 41 30 31 00 49**
400 +The valid data will be all bytes after 1E 56 34 , so it is 2e 30 58 5f 36 41 30 31 00 49
437 437  
438 -[[image:1653271044481-711.png]]
402 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image013.png]]
439 439  
404 +
440 440  1. For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
441 441  
442 442  If we set AT+SEARCH1=2, 1E 56 34+31 00 49
443 443  
444 -Device will search the bytes between 1E 56 34 and 31 00 49. So it is(% style="background-color:yellow" %) **2e 30 58 5f 36 41 30**
409 +Device will search the bytes between 1E 56 34 and 31 00 49. So it is 2e 30 58 5f 36 41 30
445 445  
446 -[[image:1653271276735-972.png]]
411 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image014.png]]
447 447  
413 +
448 448  **AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes.
449 449  
450 -(% style="background-color:#4f81bd; color:white; width:729px" %)
451 -|(% style="width:726px" %)(((
416 +|(((
452 452  **AT+DATACUTx=a,b,c**
453 453  
454 454  * **a: length for the return of AT+COMMAND**
455 455  * **b:1: grab valid value by byte, max 6 bytes. 2: grab valid value by bytes section, max 3 sections.**
456 -* **c: define the position for valid value.  **
421 +* **c: define the position for valid value. **
457 457  )))
458 458  
459 459  Examples:
... ... @@ -460,130 +460,95 @@
460 460  
461 461  * Grab bytes:
462 462  
463 -[[image:1653271581490-837.png||height="313" width="722"]]
428 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image015.png]]
464 464  
465 465  * Grab a section.
466 466  
467 -[[image:1653271648378-342.png||height="326" width="720"]]
432 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image016.png]]
468 468  
469 469  * Grab different sections.
470 470  
471 -[[image:1653271657255-576.png||height="305" width="730"]]
436 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image017.png]]
472 472  
473 -(((
474 -(% style="color:red" %)**Note:**
475 -)))
476 476  
477 -(((
439 +Note:
440 +
478 478  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.
479 -)))
480 480  
481 -(((
482 -**Example:**
483 -)))
443 +Example:
484 484  
485 -(((
486 -(% style="color:red" %)AT+COMMAND1=11 01 1E D0,0
487 -)))
445 +AT+COMMAND1=11 01 1E D0,0
488 488  
489 -(((
490 -(% style="color:red" %)AT+SEARCH1=1,1E 56 34
491 -)))
447 +AT+SEARCH1=1,1E 56 34
492 492  
493 -(((
494 -(% style="color:red" %)AT+DATACUT1=0,2,1~~5
495 -)))
449 +AT+DATACUT1=0,2,1~~5
496 496  
497 -(((
498 -(% style="color:red" %)Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
499 -)))
451 +Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
500 500  
501 -(((
502 -(% style="color:red" %)String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
503 -)))
453 +String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
504 504  
505 -(((
506 -(% style="color:red" %)Valid payload after DataCUT command: 2e 30 58 5f 36
507 -)))
455 +Valid payload after DataCUT command: 2e 30 58 5f 36
508 508  
509 -[[image:1653271763403-806.png]]
457 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image018.png]]
510 510  
511 -=== 3.3.4 Compose the uplink payload ===
512 512  
513 -(((
460 +
461 +
462 +1.
463 +11.
464 +111. Compose the uplink payload
465 +
514 514  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.**
515 -)))
516 516  
517 -(((
518 -(% style="color:#4f81bd" %)**Examples: AT+DATAUP=0**
519 -)))
520 520  
521 -(((
522 -Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**A SIGNLE UPLINK**.
523 -)))
469 +**Examples: AT+DATAUP=0**
524 524  
525 -(((
471 +Compose the uplink payload with value returns in sequence and send with **A SIGNLE UPLINK**.
472 +
526 526  Final Payload is
527 -)))
528 528  
529 -(((
530 -(% style="color:#4f81bd" %)Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx
531 -)))
475 +Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx
532 532  
533 -(((
534 534  Where PAYVER is defined by AT+PAYVER, below is an example screen shot.
535 -)))
536 536  
537 -[[image:1653272787040-634.png||height="515" width="719"]]
479 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.png]]
538 538  
539 -(((
540 -(% style="color:#4f81bd" %)**Examples: AT+DATAUP=1**
541 -)))
542 542  
543 -(((
544 -Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**Multiply UPLINKs**.
545 -)))
546 546  
547 -(((
483 +**Examples: AT+DATAUP=1**
484 +
485 +Compose the uplink payload with value returns in sequence and send with **Multiply UPLINKs**.
486 +
548 548  Final Payload is
549 -)))
550 550  
551 -(((
552 -(% style="color:#4f81bd" %)Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA
553 -)))
489 +Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA
554 554  
555 -1. (((
556 -Battery Info (2 bytes): Battery voltage
557 -)))
558 -1. (((
559 -PAYVER (1 byte): Defined by AT+PAYVER
560 -)))
561 -1. (((
562 -PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling.
563 -)))
564 -1. (((
565 -PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
566 -)))
567 -1. (((
568 -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
569 -)))
491 +1. Battery Info (2 bytes): Battery voltage
492 +1. PAYVER (1 byte): Defined by AT+PAYVER
493 +1. PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling.
494 +1. PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
495 +1. DATA: Valid value: max 6 bytes(US915 version here, [[Notice*!>>path:#max_byte]]) for each uplink so each uplink <= 11 bytes. For the last uplink, DATA will might less than 6 bytes
570 570  
571 -[[image:1653272817147-600.png||height="437" width="717"]]
497 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image020.png]]
572 572  
499 +
573 573  So totally there will be 3 uplinks for this sampling, each uplink includes 6 bytes DATA
574 574  
575 -DATA1=RETURN1 Valid Value = (% style="background-color:#4f81bd; color:white" %) 20 20 0a 33 90 41
502 +DATA1=RETURN1 Valid Value = 20 20 0a 33 90 41
576 576  
577 -DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= (% style="background-color:#4f81bd; color:white" %)02 aa 05 81 0a 20
504 +DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= 02 aa 05 81 0a 20
578 578  
579 -DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 =(% style="background-color:#4f81bd; color:white" %) 20 20 20 2d 30
506 +DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 = 20 20 20 2d 30
580 580  
508 +
509 +
581 581  Below are the uplink payloads:
582 582  
583 -[[image:1653272901032-107.png]]
512 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.png]]
584 584  
585 -(% style="color:red" %)Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:
586 586  
515 +Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:
516 +
587 587   ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink ( so 51 -5 = 46 max valid date)
588 588  
589 589   * For AU915/AS923 bands, if UplinkDwell time=1, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date).
... ... @@ -592,121 +592,91 @@
592 592  
593 593   ~* For all other bands: max 51 bytes for each uplink  ( so 51 -5 = 46 max valid date).
594 594  
595 -=== 3.3.5 Uplink on demand ===
596 596  
597 -(((
526 +
527 +1.
528 +11.
529 +111. Uplink on demand
530 +
598 598  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.
599 -)))
600 600  
601 -(((
602 602  Downlink control command:
603 -)))
604 604  
605 -(((
606 -**0x08 command**: Poll an uplink with current command set in RS485-BL.
607 -)))
535 +[[0x08 command>>path:#downlink_08]]: Poll an uplink with current command set in RS485-BL.
608 608  
609 -(((
610 -**0xA8 command**: Send a command to RS485-BL and uplink the output from sensors.
611 -)))
537 +[[0xA8 command>>path:#downlink_A8]]: Send a command to RS485-BL and uplink the output from sensors.
612 612  
613 -=== 3.3.6 Uplink on Interrupt ===
614 614  
615 -Put the interrupt sensor between 3.3v_out and GPIO ext.
616 616  
617 -[[image:1653273818896-432.png]]
541 +1.
542 +11.
543 +111. Uplink on Interrupt
618 618  
619 -(((
545 +Put the interrupt sensor between 3.3v_out and GPIO ext.[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image022.png]]
546 +
620 620  AT+INTMOD=0  Disable Interrupt
621 -)))
622 622  
623 -(((
624 624  AT+INTMOD=1  Interrupt trigger by rising or falling edge.
625 -)))
626 626  
627 -(((
628 628  AT+INTMOD=2  Interrupt trigger by falling edge. ( Default Value)
629 -)))
630 630  
631 -(((
632 632  AT+INTMOD=3  Interrupt trigger by rising edge.
633 -)))
634 634  
635 -== 3.4 Uplink Payload ==
636 636  
637 -(% border="1" style="background-color:#4f81bd; color:white; width:850px" %)
638 -|**Size(bytes)**|(% style="width:130px" %)**2**|(% style="width:93px" %)**1**|(% style="width:509px" %)**Length depends on the return from the commands**
639 -|Value|(% style="width:130px" %)(((
640 -(((
556 +1.
557 +11. Uplink Payload
558 +
559 +
560 +|**Size(bytes)**|**2**|**1**|**Length depends on the return from the commands**
561 +|Value|(((
641 641  Battery(mV)
642 -)))
643 643  
644 -(((
645 645  &
646 -)))
647 647  
648 -(((
649 649  Interrupt _Flag
650 -)))
651 -)))|(% style="width:93px" %)(((
567 +)))|(((
652 652  PAYLOAD_VER
653 653  
654 654  
655 -)))|(% style="width:509px" %)If the valid payload is too long and exceed the maximum support payload length in server, server will show payload not provided in the LoRaWAN server.
571 +)))|If the valid payload is too long and exceed the maximum support payload length in server, server will show payload not provided in the LoRaWAN server.
656 656  
657 657  Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors.
658 658  
659 -(((
575 +
660 660  function Decoder(bytes, port) {
661 -)))
662 662  
663 -(((
664 664  ~/~/Payload Formats of RS485-BL Deceive
665 -)))
666 666  
667 -(((
668 668  return {
669 -)))
670 670  
671 -(((
672 672   ~/~/Battery,units:V
673 -)))
674 674  
675 -(((
676 676   BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000,
677 -)))
678 678  
679 -(((
680 680   ~/~/GPIO_EXTI 
681 -)))
682 682  
683 -(((
684 684   EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE",
685 -)))
686 686  
687 -(((
688 688   ~/~/payload of version
689 -)))
690 690  
691 -(((
692 692   Pay_ver:bytes[2],
693 -)))
694 694  
695 -(((
696 696   };
697 -)))
698 698  
699 -(((
700 700   }
701 -)))
702 702  
703 -(((
598 +
599 +
600 +
601 +
602 +
603 +
704 704  TTN V3 uplink screen shot.
705 -)))
706 706  
707 -[[image:1653274001211-372.png||height="192" width="732"]]
606 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]
708 708  
709 -== 3.5 Configure RS485-BL via AT or Downlink ==
608 +1.
609 +11. Configure RS485-BL via AT or Downlink
710 710  
711 711  User can configure RS485-BL via [[AT Commands >>path:#_​Using_the_AT]]or LoRaWAN Downlink Commands
712 712  
... ... @@ -716,17 +716,20 @@
716 716  
717 717  * **Sensor Related Commands**: These commands are special designed for RS485-BL.  User can see these commands below:
718 718  
719 -1.
720 -11.
619 +
620 +1.
621 +11.
721 721  111. Common Commands:
722 722  
624 +
723 723  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]]
724 724  
725 725  
726 -1.
727 -11.
628 +1.
629 +11.
728 728  111. Sensor related commands:
729 729  
632 +
730 730  ==== Choose Device Type (RS485 or TTL) ====
731 731  
732 732  RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect.
... ... @@ -767,6 +767,7 @@
767 767  * XX XX XX XX: RS485 command total NN bytes
768 768  * 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
769 769  
673 +
770 770  **Example 1:**
771 771  
772 772  To connect a Modbus Alarm with below commands.
... ... @@ -875,6 +875,7 @@
875 875  
876 876  * AT+MBFUN=0: Disable Modbus fast reading.
877 877  
782 +
878 878  Example:
879 879  
880 880  * AT+MBFUN=1 and AT+DATACUT1/AT+DATACUT2 are not configure (0,0,0).
... ... @@ -959,7 +959,7 @@
959 959  
960 960  Etc. AT+CMDEAR=1,10 means erase AT+COMMAND1/AT+DATACUT1 to AT+COMMAND10/AT+DATACUT10
961 961  
962 -Example screen shot after clear all RS485 commands. 
867 +Example screen shot after clear all RS485 commands.
963 963  
964 964  
965 965  
... ... @@ -1003,6 +1003,7 @@
1003 1003  * A7 01 00 60   same as AT+BAUDR=9600
1004 1004  * A7 01 04 80  same as AT+BAUDR=115200
1005 1005  
911 +
1006 1006  A7 02 aa: Same as  AT+PARITY=aa  (aa value: 00 , 01 or 02)
1007 1007  
1008 1008  A7 03 aa: Same as  AT+STOPBIT=aa  (aa value: 00 , 01 or 02)
... ... @@ -1030,18 +1030,20 @@
1030 1030  
1031 1031  
1032 1032  
1033 -1.
939 +1.
1034 1034  11. Buttons
1035 1035  
942 +
1036 1036  |**Button**|**Feature**
1037 1037  |**RST**|Reboot RS485-BL
1038 1038  
1039 -1.
946 +
947 +1.
1040 1040  11. +3V3 Output
1041 1041  
1042 1042  RS485-BL has a Controllable +3V3 output, user can use this output to power external sensor.
1043 1043  
1044 -The +3V3 output will be valid for every sampling. RS485-BL will enable +3V3 output before all sampling and disable the +3V3 after all sampling. 
952 +The +3V3 output will be valid for every sampling. RS485-BL will enable +3V3 output before all sampling and disable the +3V3 after all sampling.
1045 1045  
1046 1046  
1047 1047  The +3V3 output time can be controlled by AT Command.
... ... @@ -1054,12 +1054,12 @@
1054 1054  By default, the AT+3V3T=0. This is a special case, means the +3V3 output is always on at any time
1055 1055  
1056 1056  
1057 -1.
965 +1.
1058 1058  11. +5V Output
1059 1059  
1060 1060  RS485-BL has a Controllable +5V output, user can use this output to power external sensor.
1061 1061  
1062 -The +5V output will be valid for every sampling. RS485-BL will enable +5V output before all sampling and disable the +5v after all sampling. 
970 +The +5V output will be valid for every sampling. RS485-BL will enable +5V output before all sampling and disable the +5v after all sampling.
1063 1063  
1064 1064  
1065 1065  The 5V output time can be controlled by AT Command.
... ... @@ -1074,13 +1074,14 @@
1074 1074  
1075 1075  
1076 1076  
1077 -1.
985 +1.
1078 1078  11. LEDs
1079 1079  
1080 1080  |**LEDs**|**Feature**
1081 1081  |**LED1**|Blink when device transmit a packet.
1082 1082  
1083 -1.
991 +
992 +1.
1084 1084  11. Switch Jumper
1085 1085  
1086 1086  |**Switch Jumper**|**Feature**
... ... @@ -1101,6 +1101,7 @@
1101 1101  
1102 1102  1. Case Study
1103 1103  
1013 +
1104 1104  User can check this URL for some case studies.
1105 1105  
1106 1106  [[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]]
... ... @@ -1126,7 +1126,7 @@
1126 1126  
1127 1127  
1128 1128  
1129 -1.
1039 +1.
1130 1130  11. Common AT Command Sequence
1131 1131  111. Multi-channel ABP mode (Use with SX1301/LG308)
1132 1132  
... ... @@ -1145,8 +1145,8 @@
1145 1145  
1146 1146  ATZ
1147 1147  
1148 -1.
1149 -11.
1058 +1.
1059 +11.
1150 1150  111. Single-channel ABP mode (Use with LG01/LG02)
1151 1151  
1152 1152  AT+FDR   Reset Parameters to Factory Default, Keys Reserve
... ... @@ -1188,6 +1188,7 @@
1188 1188  * For bug fix
1189 1189  * Change LoRaWAN bands.
1190 1190  
1101 +
1191 1191  Below shows the hardware connection for how to upload an image to RS485-BL:
1192 1192  
1193 1193  [[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image030.png]]
... ... @@ -1221,7 +1221,7 @@
1221 1221  [[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]]
1222 1222  
1223 1223  
1224 -1.
1135 +1.
1225 1225  11. How to change the LoRa Frequency Bands/Region?
1226 1226  
1227 1227  User can follow the introduction for [[how to upgrade image>>path:#upgrade_image]]. When download the images, choose the required image file for download.
... ... @@ -1228,9 +1228,10 @@
1228 1228  
1229 1229  
1230 1230  
1231 -1.
1142 +1.
1232 1232  11. How many RS485-Slave can RS485-BL connects?
1233 1233  
1145 +
1234 1234  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]].
1235 1235  
1236 1236  
... ... @@ -1241,11 +1241,11 @@
1241 1241  
1242 1242  Please see this link for debug:
1243 1243  
1244 -[[http:~~/~~/wiki.dragino.com/index.php?title=Main_Page#LoRaWAN_Communication_Debug>>url:http://wiki.dragino.com/index.php?title=Main_Page#LoRaWAN_Communication_Debug]] 
1156 +[[http:~~/~~/wiki.dragino.com/index.php?title=Main_Page#LoRaWAN_Communication_Debug>>url:http://wiki.dragino.com/index.php?title=Main_Page#LoRaWAN_Communication_Debug]]
1245 1245  
1246 1246  
1247 1247  
1248 -1.
1160 +1.
1249 1249  11. Why I can’t join TTN V3 in US915 /AU915 bands?
1250 1250  
1251 1251  It might about the channels mapping. Please see for detail.
... ... @@ -1256,6 +1256,7 @@
1256 1256  
1257 1257  1. Order Info
1258 1258  
1171 +
1259 1259  **Part Number: RS485-BL-XXX**
1260 1260  
1261 1261  **XXX:**
... ... @@ -1271,6 +1271,7 @@
1271 1271  * **RU864**: frequency bands RU864
1272 1272  * **KZ865: **frequency bands KZ865
1273 1273  
1187 +
1274 1274  1. Packing Info
1275 1275  
1276 1276  **Package Includes**:
... ... @@ -1279,6 +1279,7 @@
1279 1279  * Stick Antenna for LoRa RF part x 1
1280 1280  * Program cable x 1
1281 1281  
1196 +
1282 1282  **Dimension and weight**:
1283 1283  
1284 1284  * Device Size: 13.5 x 7 x 3 cm
... ... @@ -1286,6 +1286,7 @@
1286 1286  * Package Size / pcs : 14.5 x 8 x 5 cm
1287 1287  * Weight / pcs : 170g
1288 1288  
1204 +
1289 1289  1. Support
1290 1290  
1291 1291  * Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule.
1652953414711-647.png
Author
... ... @@ -1,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