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