Skip to Content
Last modified by Xiaoling on 2025/04/23 15:57
From version 29.5
edited by Xiaoling
on 2022/06/01 18:00
Change comment: There is no comment for this version
To version 5.1
edited by Xiaoling
on 2022/05/19 17:41
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,6 +1,7 @@
1 1  (% style="text-align:center" %)
2 2  [[image:1652947681187-144.png||height="385" width="385"]]
3 3  
4 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image001.jpg]]
4 4  
5 5  
6 6  
... ... @@ -7,15 +7,12 @@
7 7  **RS485-BL – Waterproof RS485 to LoRaWAN Converter User Manual**
8 8  
9 9  
10 -
11 11  **Table of Contents:**
12 12  
13 -{{toc/}}
14 14  
15 15  
16 16  
17 17  
18 -
19 19  = 1.Introduction =
20 20  
21 21  == 1.1 What is RS485-BL RS485 to LoRaWAN Converter ==
... ... @@ -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,7 +59,7 @@
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  
... ... @@ -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,261 +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 -)))
166 166  
167 -== 3.2 Example to join LoRaWAN network ==
168 168  
169 -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. 
164 +1.
165 +11. Example to join LoRaWAN network
170 170  
171 -[[image:1652953414711-647.png||height="337" width="723"]]
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 -(((
169 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image004.png]]
170 +
171 +
174 174  The RS485-BL in this example connected to two RS485 devices for demonstration, user can connect to other RS485 devices via the same method.
175 -)))
176 176  
177 -(((
174 +
178 178  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:
179 -)))
180 180  
181 -(((
182 182  **Step 1**: Create a device in TTN V3 with the OTAA keys from RS485-BL.
183 -)))
184 184  
185 -(((
186 186  Each RS485-BL is shipped with a sticker with unique device EUI:
187 -)))
188 188  
189 -[[image:1652953462722-299.png]]
181 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image005.png]]
190 190  
191 -(((
183 +
184 +
185 +
192 192  User can enter this key in their LoRaWAN Server portal. Below is TTN V3 screen shot:
193 -)))
194 194  
195 -(((
196 196  Add APP EUI in the application.
197 -)))
198 198  
190 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image006.png]]
199 199  
192 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image007.png]]
200 200  
194 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image008.png]]
201 201  
202 -[[image:image-20220519174512-1.png]]
196 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image009.png]]
203 203  
204 -[[image:image-20220519174512-2.png||height="328" width="731"]]
205 205  
206 -[[image:image-20220519174512-3.png||height="556" width="724"]]
207 207  
208 -[[image:image-20220519174512-4.png]]
209 209  
201 +
202 +
203 +
204 +
205 +
206 +
207 +
208 +
209 +
210 +
211 +
212 +
213 +
210 210  You can also choose to create the device manually.
211 211  
212 -[[image:1652953542269-423.png||height="710" width="723"]]
216 +|(((
217 +
218 +)))
213 213  
220 +
221 +
222 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image010.png]]
223 +
214 214  Add APP KEY and DEV EUI
215 215  
216 -[[image:1652953553383-907.png||height="514" width="724"]]
226 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image011.png]]
217 217  
218 218  
219 -(((
220 220  **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.
221 -)))
222 222  
223 -[[image:1652953568895-172.png||height="232" width="724"]]
231 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image012.png]]
224 224  
225 -== 3.3 Configure Commands to read data ==
226 226  
227 -(((
234 +
235 +
236 +1.
237 +11. Configure Commands to read data
238 +
228 228  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.
229 -)))
230 230  
231 -=== 3.3.1 onfigure UART settings for RS485 or TTL communication ===
232 232  
242 +1.
243 +11.
244 +111. Configure UART settings for RS485 or TTL communication
245 +
233 233  RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect.
234 234  
235 -**~1. RS485-MODBUS mode:**
248 +1. RS485-MODBUS mode:
236 236  
237 237  AT+MOD=1 ~/~/ Support RS485-MODBUS type sensors. User can connect multiply RS485 , Modbus sensors to the A / B pins.
238 238  
239 -**2. TTL mode:**
240 240  
253 +1. TTL mode:
254 +
241 241  AT+MOD=2 ~/~/ Support TTL Level sensors, User can connect one TTL Sensor to the TXD/RXD/GND pins.
242 242  
257 +
243 243  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.
244 244  
245 -(% border="1" style="background-color:#ffffcc; color:green; width:795px" %)
246 -|(((
247 -**AT Commands**
248 -)))|(% style="width:285px" %)(((
249 -**Description**
250 -)))|(% style="width:347px" %)(((
251 -**Example**
252 -)))
253 -|(((
254 -AT+BAUDR
255 -)))|(% style="width:285px" %)(((
256 -Set the baud rate (for RS485 connection). Default Value is: 9600.
257 -)))|(% style="width:347px" %)(((
258 -(((
260 +
261 +|**AT Commands**|**Description**|**Example**
262 +|AT+BAUDR|Set the baud rate (for RS485 connection). Default Value is: 9600.|(((
259 259  AT+BAUDR=9600
260 -)))
261 261  
262 -(((
263 263  Options: (1200,2400,4800,14400,19200,115200)
264 264  )))
265 -)))
266 -|(((
267 -AT+PARITY
268 -)))|(% style="width:285px" %)(((
269 -(((
267 +|AT+PARITY|(((
270 270  Set UART parity (for RS485 connection)
271 -)))
272 272  
273 -(((
274 274  Default Value is: no parity.
275 -)))
276 -)))|(% style="width:347px" %)(((
277 -(((
271 +)))|(((
278 278  AT+PARITY=0
279 -)))
280 280  
281 -(((
282 282  Option: 0: no parity, 1: odd parity, 2: even parity
283 283  )))
284 -)))
285 -|(((
286 -AT+STOPBIT
287 -)))|(% style="width:285px" %)(((
288 -(((
276 +|AT+STOPBIT|(((
289 289  Set serial stopbit (for RS485 connection)
290 -)))
291 291  
292 -(((
293 293  Default Value is: 1bit.
294 -)))
295 -)))|(% style="width:347px" %)(((
296 -(((
280 +)))|(((
297 297  AT+STOPBIT=0 for 1bit
298 -)))
299 299  
300 -(((
301 301  AT+STOPBIT=1 for 1.5 bit
302 -)))
303 303  
304 -(((
305 305  AT+STOPBIT=2 for 2 bits
306 306  )))
307 -)))
308 308  
309 -=== 3.3.2 Configure sensors ===
310 310  
311 -(((
312 -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**.
313 -)))
314 314  
315 -(((
316 -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.
317 -)))
318 318  
319 -(% border="1" style="background-color:#ffffcc; color:green; width:806px" %)
320 -|**AT Commands**|(% style="width:418px" %)**Description**|(% style="width:256px" %)**Example**
321 -|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|(((
322 322  This command is used to configure the RS485/TTL devices; they won’t be used during sampling.
323 323  
324 -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
325 325  
326 -mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
327 -)))|(% 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
328 328  
329 329  Detail of AT+CFGDEV command see [[AT+CFGDEV detail>>path:#AT_CFGDEV]].
330 330  
331 -=== 3.3.3 Configure read commands for each sampling ===
332 332  
333 -(((
313 +
314 +
315 +
316 +1.
317 +11.
318 +111. Configure read commands for each sampling
319 +
334 334  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.
335 -)))
336 336  
337 -(((
322 +
338 338  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.
339 -)))
340 340  
341 -(((
325 +
342 342  To save the LoRaWAN network bandwidth, we might need to read data from different sensors and combine their valid value into a short payload.
343 -)))
344 344  
345 -(((
328 +
346 346  This section describes how to achieve above goals.
347 -)))
348 348  
349 -(((
331 +
350 350  During each sampling, the RS485-BL can support 15 commands to read sensors. And combine the return to one or several uplink payloads.
351 -)))
352 352  
353 -(((
334 +
354 354  **Command from RS485-BL to Sensor:**
355 -)))
356 356  
357 -(((
358 358  RS485-BL can send out pre-set max 15 strings via **AT+COMMAD1**, **ATCOMMAND2**,…, to **AT+COMMANDF** . All commands are of same grammar.
359 -)))
360 360  
361 -(((
339 +
362 362  **Handle return from sensors to RS485-BL**:
363 -)))
364 364  
365 -(((
366 366  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**
367 -)))
368 368  
369 -* (((
370 -**AT+DATACUT**
371 -)))
372 372  
373 -(((
345 +* **AT+DATACUT**
346 +
374 374  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.
375 -)))
376 376  
377 -* (((
378 -**AT+SEARCH**
379 -)))
380 380  
381 -(((
350 +* **AT+SEARCH**
351 +
382 382  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.
383 -)))
384 384  
385 -(((
354 +
386 386  **Define wait timeout:**
387 -)))
388 388  
389 -(((
390 390  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
391 -)))
392 392  
393 -(((
359 +
394 394  After we got the valid value from each RS485 commands, we need to combine them together with the command **AT+DATAUP**.
395 -)))
396 396  
362 +
397 397  **Examples:**
398 398  
399 399  Below are examples for the how above AT Commands works.
400 400  
367 +
401 401  **AT+COMMANDx : **This command will be sent to RS485/TTL devices during each sampling, Max command length is 14 bytes. The grammar is:
402 402  
403 -(% border="1" class="table-bordered" style="background-color:#4f81bd; color:white; width:501px" %)
404 -|(% style="width:498px" %)(((
370 +|(((
405 405  **AT+COMMANDx=xx xx xx xx xx xx xx xx xx xx xx xx,m**
406 406  
407 407  **xx xx xx xx xx xx xx xx xx xx xx xx: The RS485 command to be sent**
... ... @@ -413,43 +413,46 @@
413 413  
414 414  In the RS485-BL, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
415 415  
382 +
416 416  **AT+SEARCHx**: This command defines how to handle the return from AT+COMMANDx.
417 417  
418 -(% border="1" class="table-bordered" style="background-color:#4f81bd; color:white; width:580px" %)
419 -|(% style="width:577px" %)(((
385 +|(((
420 420  **AT+SEARCHx=aa,xx xx xx xx xx**
421 421  
422 422  * **aa: 1: prefix match mode; 2: prefix and suffix match mode**
423 423  * **xx xx xx xx xx: match string. Max 5 bytes for prefix and 5 bytes for suffix**
390 +
391 +
424 424  )))
425 425  
426 -**Examples:**
394 +Examples:
427 427  
428 428  1. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
429 429  
430 430  If we set AT+SEARCH1=1,1E 56 34.      (max 5 bytes for prefix)
431 431  
432 -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
433 433  
434 -[[image:1653271044481-711.png]]
402 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image013.png]]
435 435  
404 +
436 436  1. For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
437 437  
438 438  If we set AT+SEARCH1=2, 1E 56 34+31 00 49
439 439  
440 -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
441 441  
442 -[[image:1653271276735-972.png]]
411 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image014.png]]
443 443  
413 +
444 444  **AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes.
445 445  
446 -(% style="background-color:#4f81bd; color:white; width:729px" %)
447 -|(% style="width:726px" %)(((
416 +|(((
448 448  **AT+DATACUTx=a,b,c**
449 449  
450 450  * **a: length for the return of AT+COMMAND**
451 451  * **b:1: grab valid value by byte, max 6 bytes. 2: grab valid value by bytes section, max 3 sections.**
452 -* **c: define the position for valid value.  **
421 +* **c: define the position for valid value. **
453 453  )))
454 454  
455 455  Examples:
... ... @@ -456,130 +456,95 @@
456 456  
457 457  * Grab bytes:
458 458  
459 -[[image:1653271581490-837.png||height="313" width="722"]]
428 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image015.png]]
460 460  
461 461  * Grab a section.
462 462  
463 -[[image:1653271648378-342.png||height="326" width="720"]]
432 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image016.png]]
464 464  
465 465  * Grab different sections.
466 466  
467 -[[image:1653271657255-576.png||height="305" width="730"]]
436 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image017.png]]
468 468  
469 -(((
470 -(% style="color:red" %)**Note:**
471 -)))
472 472  
473 -(((
439 +Note:
440 +
474 474  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.
475 -)))
476 476  
477 -(((
478 -**Example:**
479 -)))
443 +Example:
480 480  
481 -(((
482 -(% style="color:red" %)AT+COMMAND1=11 01 1E D0,0
483 -)))
445 +AT+COMMAND1=11 01 1E D0,0
484 484  
485 -(((
486 -(% style="color:red" %)AT+SEARCH1=1,1E 56 34
487 -)))
447 +AT+SEARCH1=1,1E 56 34
488 488  
489 -(((
490 -(% style="color:red" %)AT+DATACUT1=0,2,1~~5
491 -)))
449 +AT+DATACUT1=0,2,1~~5
492 492  
493 -(((
494 -(% style="color:red" %)Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
495 -)))
451 +Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
496 496  
497 -(((
498 -(% style="color:red" %)String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
499 -)))
453 +String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
500 500  
501 -(((
502 -(% style="color:red" %)Valid payload after DataCUT command: 2e 30 58 5f 36
503 -)))
455 +Valid payload after DataCUT command: 2e 30 58 5f 36
504 504  
505 -[[image:1653271763403-806.png]]
457 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image018.png]]
506 506  
507 -=== 3.3.4 Compose the uplink payload ===
508 508  
509 -(((
460 +
461 +
462 +1.
463 +11.
464 +111. Compose the uplink payload
465 +
510 510  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.**
511 -)))
512 512  
513 -(((
514 -(% style="color:#4f81bd" %)**Examples: AT+DATAUP=0**
515 -)))
516 516  
517 -(((
518 -Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**A SIGNLE UPLINK**.
519 -)))
469 +**Examples: AT+DATAUP=0**
520 520  
521 -(((
471 +Compose the uplink payload with value returns in sequence and send with **A SIGNLE UPLINK**.
472 +
522 522  Final Payload is
523 -)))
524 524  
525 -(((
526 -(% style="color:#4f81bd" %)Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx
527 -)))
475 +Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx
528 528  
529 -(((
530 530  Where PAYVER is defined by AT+PAYVER, below is an example screen shot.
531 -)))
532 532  
533 -[[image:1653272787040-634.png||height="515" width="719"]]
479 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.png]]
534 534  
535 -(((
536 -(% style="color:#4f81bd" %)**Examples: AT+DATAUP=1**
537 -)))
538 538  
539 -(((
540 -Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**Multiply UPLINKs**.
541 -)))
542 542  
543 -(((
483 +**Examples: AT+DATAUP=1**
484 +
485 +Compose the uplink payload with value returns in sequence and send with **Multiply UPLINKs**.
486 +
544 544  Final Payload is
545 -)))
546 546  
547 -(((
548 -(% style="color:#4f81bd" %)Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA
549 -)))
489 +Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA
550 550  
551 -1. (((
552 -Battery Info (2 bytes): Battery voltage
553 -)))
554 -1. (((
555 -PAYVER (1 byte): Defined by AT+PAYVER
556 -)))
557 -1. (((
558 -PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling.
559 -)))
560 -1. (((
561 -PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
562 -)))
563 -1. (((
564 -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
565 -)))
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
566 566  
567 -[[image:1653272817147-600.png||height="437" width="717"]]
497 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image020.png]]
568 568  
499 +
569 569  So totally there will be 3 uplinks for this sampling, each uplink includes 6 bytes DATA
570 570  
571 -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
572 572  
573 -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
574 574  
575 -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
576 576  
508 +
509 +
577 577  Below are the uplink payloads:
578 578  
579 -[[image:1653272901032-107.png]]
512 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.png]]
580 580  
581 -(% style="color:red" %)Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:
582 582  
515 +Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:
516 +
583 583   ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink ( so 51 -5 = 46 max valid date)
584 584  
585 585   * For AU915/AS923 bands, if UplinkDwell time=1, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date).
... ... @@ -588,121 +588,91 @@
588 588  
589 589   ~* For all other bands: max 51 bytes for each uplink  ( so 51 -5 = 46 max valid date).
590 590  
591 -=== 3.3.5 Uplink on demand ===
592 592  
593 -(((
526 +
527 +1.
528 +11.
529 +111. Uplink on demand
530 +
594 594  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.
595 -)))
596 596  
597 -(((
598 598  Downlink control command:
599 -)))
600 600  
601 -(((
602 -**0x08 command**: Poll an uplink with current command set in RS485-BL.
603 -)))
535 +[[0x08 command>>path:#downlink_08]]: Poll an uplink with current command set in RS485-BL.
604 604  
605 -(((
606 -**0xA8 command**: Send a command to RS485-BL and uplink the output from sensors.
607 -)))
537 +[[0xA8 command>>path:#downlink_A8]]: Send a command to RS485-BL and uplink the output from sensors.
608 608  
609 -=== 3.3.6 Uplink on Interrupt ===
610 610  
611 -Put the interrupt sensor between 3.3v_out and GPIO ext.
612 612  
613 -[[image:1653273818896-432.png]]
541 +1.
542 +11.
543 +111. Uplink on Interrupt
614 614  
615 -(((
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 +
616 616  AT+INTMOD=0  Disable Interrupt
617 -)))
618 618  
619 -(((
620 620  AT+INTMOD=1  Interrupt trigger by rising or falling edge.
621 -)))
622 622  
623 -(((
624 624  AT+INTMOD=2  Interrupt trigger by falling edge. ( Default Value)
625 -)))
626 626  
627 -(((
628 628  AT+INTMOD=3  Interrupt trigger by rising edge.
629 -)))
630 630  
631 -== 3.4 Uplink Payload ==
632 632  
633 -(% border="1" style="background-color:#4f81bd; color:white; width:850px" %)
634 -|**Size(bytes)**|(% style="width:130px" %)**2**|(% style="width:93px" %)**1**|(% style="width:509px" %)**Length depends on the return from the commands**
635 -|Value|(% style="width:130px" %)(((
636 -(((
556 +1.
557 +11. Uplink Payload
558 +
559 +
560 +|**Size(bytes)**|**2**|**1**|**Length depends on the return from the commands**
561 +|Value|(((
637 637  Battery(mV)
638 -)))
639 639  
640 -(((
641 641  &
642 -)))
643 643  
644 -(((
645 645  Interrupt _Flag
646 -)))
647 -)))|(% style="width:93px" %)(((
567 +)))|(((
648 648  PAYLOAD_VER
649 649  
650 650  
651 -)))|(% 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.
652 652  
653 653  Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors.
654 654  
655 -(((
575 +
656 656  function Decoder(bytes, port) {
657 -)))
658 658  
659 -(((
660 660  ~/~/Payload Formats of RS485-BL Deceive
661 -)))
662 662  
663 -(((
664 664  return {
665 -)))
666 666  
667 -(((
668 668   ~/~/Battery,units:V
669 -)))
670 670  
671 -(((
672 672   BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000,
673 -)))
674 674  
675 -(((
676 676   ~/~/GPIO_EXTI 
677 -)))
678 678  
679 -(((
680 680   EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE",
681 -)))
682 682  
683 -(((
684 684   ~/~/payload of version
685 -)))
686 686  
687 -(((
688 688   Pay_ver:bytes[2],
689 -)))
690 690  
691 -(((
692 692   };
693 -)))
694 694  
695 -(((
696 696   }
697 -)))
698 698  
699 -(((
598 +
599 +
600 +
601 +
602 +
603 +
700 700  TTN V3 uplink screen shot.
701 -)))
702 702  
703 -[[image:1653274001211-372.png||height="192" width="732"]]
606 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]
704 704  
705 -== 3.5 Configure RS485-BL via AT or Downlink ==
608 +1.
609 +11. Configure RS485-BL via AT or Downlink
706 706  
707 707  User can configure RS485-BL via [[AT Commands >>path:#_​Using_the_AT]]or LoRaWAN Downlink Commands
708 708  
... ... @@ -712,10 +712,12 @@
712 712  
713 713  * **Sensor Related Commands**: These commands are special designed for RS485-BL.  User can see these commands below:
714 714  
619 +
715 715  1.
716 716  11.
717 717  111. Common Commands:
718 718  
624 +
719 719  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]]
720 720  
721 721  
... ... @@ -723,6 +723,7 @@
723 723  11.
724 724  111. Sensor related commands:
725 725  
632 +
726 726  ==== Choose Device Type (RS485 or TTL) ====
727 727  
728 728  RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect.
... ... @@ -763,6 +763,7 @@
763 763  * XX XX XX XX: RS485 command total NN bytes
764 764  * 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
765 765  
673 +
766 766  **Example 1:**
767 767  
768 768  To connect a Modbus Alarm with below commands.
... ... @@ -871,6 +871,7 @@
871 871  
872 872  * AT+MBFUN=0: Disable Modbus fast reading.
873 873  
782 +
874 874  Example:
875 875  
876 876  * AT+MBFUN=1 and AT+DATACUT1/AT+DATACUT2 are not configure (0,0,0).
... ... @@ -955,7 +955,7 @@
955 955  
956 956  Etc. AT+CMDEAR=1,10 means erase AT+COMMAND1/AT+DATACUT1 to AT+COMMAND10/AT+DATACUT10
957 957  
958 -Example screen shot after clear all RS485 commands. 
867 +Example screen shot after clear all RS485 commands.
959 959  
960 960  
961 961  
... ... @@ -999,6 +999,7 @@
999 999  * A7 01 00 60   same as AT+BAUDR=9600
1000 1000  * A7 01 04 80  same as AT+BAUDR=115200
1001 1001  
911 +
1002 1002  A7 02 aa: Same as  AT+PARITY=aa  (aa value: 00 , 01 or 02)
1003 1003  
1004 1004  A7 03 aa: Same as  AT+STOPBIT=aa  (aa value: 00 , 01 or 02)
... ... @@ -1029,15 +1029,17 @@
1029 1029  1.
1030 1030  11. Buttons
1031 1031  
942 +
1032 1032  |**Button**|**Feature**
1033 1033  |**RST**|Reboot RS485-BL
1034 1034  
946 +
1035 1035  1.
1036 1036  11. +3V3 Output
1037 1037  
1038 1038  RS485-BL has a Controllable +3V3 output, user can use this output to power external sensor.
1039 1039  
1040 -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.
1041 1041  
1042 1042  
1043 1043  The +3V3 output time can be controlled by AT Command.
... ... @@ -1055,7 +1055,7 @@
1055 1055  
1056 1056  RS485-BL has a Controllable +5V output, user can use this output to power external sensor.
1057 1057  
1058 -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.
1059 1059  
1060 1060  
1061 1061  The 5V output time can be controlled by AT Command.
... ... @@ -1076,6 +1076,7 @@
1076 1076  |**LEDs**|**Feature**
1077 1077  |**LED1**|Blink when device transmit a packet.
1078 1078  
991 +
1079 1079  1.
1080 1080  11. Switch Jumper
1081 1081  
... ... @@ -1097,6 +1097,7 @@
1097 1097  
1098 1098  1. Case Study
1099 1099  
1013 +
1100 1100  User can check this URL for some case studies.
1101 1101  
1102 1102  [[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]]
... ... @@ -1184,6 +1184,7 @@
1184 1184  * For bug fix
1185 1185  * Change LoRaWAN bands.
1186 1186  
1101 +
1187 1187  Below shows the hardware connection for how to upload an image to RS485-BL:
1188 1188  
1189 1189  [[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image030.png]]
... ... @@ -1227,6 +1227,7 @@
1227 1227  1.
1228 1228  11. How many RS485-Slave can RS485-BL connects?
1229 1229  
1145 +
1230 1230  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]].
1231 1231  
1232 1232  
... ... @@ -1237,7 +1237,7 @@
1237 1237  
1238 1238  Please see this link for debug:
1239 1239  
1240 -[[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]]
1241 1241  
1242 1242  
1243 1243  
... ... @@ -1252,6 +1252,7 @@
1252 1252  
1253 1253  1. Order Info
1254 1254  
1171 +
1255 1255  **Part Number: RS485-BL-XXX**
1256 1256  
1257 1257  **XXX:**
... ... @@ -1267,6 +1267,7 @@
1267 1267  * **RU864**: frequency bands RU864
1268 1268  * **KZ865: **frequency bands KZ865
1269 1269  
1187 +
1270 1270  1. Packing Info
1271 1271  
1272 1272  **Package Includes**:
... ... @@ -1275,6 +1275,7 @@
1275 1275  * Stick Antenna for LoRa RF part x 1
1276 1276  * Program cable x 1
1277 1277  
1196 +
1278 1278  **Dimension and weight**:
1279 1279  
1280 1280  * Device Size: 13.5 x 7 x 3 cm
... ... @@ -1282,6 +1282,7 @@
1282 1282  * Package Size / pcs : 14.5 x 8 x 5 cm
1283 1283  * Weight / pcs : 170g
1284 1284  
1204 +
1285 1285  1. Support
1286 1286  
1287 1287  * Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule.
1652953304999-717.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -139.7 KB
Content
1652953414711-647.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -119.3 KB
Content
1652953462722-299.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -202.7 KB
Content
1652953542269-423.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -118.5 KB
Content
1652953553383-907.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -94.0 KB
Content
1652953568895-172.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -109.3 KB
Content
1652954654347-831.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -138.7 KB
Content
1653271044481-711.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -27.8 KB
Content
1653271276735-972.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -26.6 KB
Content
1653271581490-837.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -138.7 KB
Content
1653271648378-342.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -131.4 KB
Content
1653271657255-576.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -142.6 KB
Content
1653271763403-806.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -27.7 KB
Content
1653272787040-634.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -294.0 KB
Content
1653272817147-600.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -143.3 KB
Content
1653272901032-107.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -197.8 KB
Content
1653273818896-432.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -31.6 KB
Content
1653274001211-372.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -91.4 KB
Content
image-20220519174512-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -32.2 KB
Content
image-20220519174512-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -42.7 KB
Content
image-20220519174512-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -36.3 KB
Content
image-20220519174512-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -19.1 KB
Content