Last modified by Xiaoling on 2025/04/23 15:57

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