Last modified by Karry Zhuang on 2025/03/06 16:34
<
From version < 31.3 >
edited by Xiaoling
on 2022/05/23 09:48
To version < 22.1 >
edited by Xiaoling
on 2022/05/23 09:10
>
Change comment: Uploaded new attachment "1653268227651-549.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -41,7 +41,7 @@
41 41  **Hardware System:**
42 42  
43 43  * STM32L072CZT6 MCU
44 -* SX1276/78 Wireless Chip 
44 +* SX1276/78 Wireless Chip
45 45  * Power Consumption (exclude RS485 device):
46 46  ** Idle: 32mA@12v
47 47  
... ... @@ -51,7 +51,7 @@
51 51  **Interface for Model:**
52 52  
53 53  * RS485
54 -* Power Input 7~~ 24V DC. 
54 +* Power Input 7~~ 24V DC.
55 55  
56 56  **LoRa Spec:**
57 57  
... ... @@ -138,29 +138,24 @@
138 138  [[image:1653268155545-638.png||height="334" width="724"]]
139 139  
140 140  (((
141 -The RS485-LN in this example connected to two RS485 devices for demonstration, user can connect to other RS485 devices via the same method. The connection is as below:
141 +The RS485-BL in this example connected to two RS485 devices for demonstration, user can connect to other RS485 devices via the same method.
142 +)))
142 142  
143 -485A+ and 485B- of the sensor are connected to RS485A and RA485B of RS485-LN respectively.
144 -
145 -[[image:1653268227651-549.png||height="592" width="720"]]
146 -
147 147  (((
148 -The LG308 is already set to connect to [[TTN V3 network >>path:eu1.cloud.thethings.network/]]. So what we need to now is only configure the TTN V3:
145 +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:
149 149  )))
150 150  
151 151  (((
152 -**Step 1**: Create a device in TTN V3 with the OTAA keys from RS485-LN.
149 +**Step 1**: Create a device in TTN V3 with the OTAA keys from RS485-BL.
153 153  )))
154 154  
155 155  (((
156 -Each RS485-LN is shipped with a sticker with unique device EUI:
153 +Each RS485-BL is shipped with a sticker with unique device EUI:
157 157  )))
158 -)))
159 159  
160 160  [[image:1652953462722-299.png]]
161 161  
162 162  (((
163 -(((
164 164  User can enter this key in their LoRaWAN Server portal. Below is TTN V3 screen shot:
165 165  )))
166 166  
... ... @@ -167,11 +167,13 @@
167 167  (((
168 168  Add APP EUI in the application.
169 169  )))
170 -)))
171 171  
166 +
167 +
168 +
172 172  [[image:image-20220519174512-1.png]]
173 173  
174 -[[image:image-20220519174512-2.png||height="323" width="720"]]
171 +[[image:image-20220519174512-2.png||height="328" width="731"]]
175 175  
176 176  [[image:image-20220519174512-3.png||height="556" width="724"]]
177 177  
... ... @@ -187,7 +187,7 @@
187 187  
188 188  
189 189  (((
190 -**Step 2**: Power on RS485-LN 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.
187 +**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.
191 191  )))
192 192  
193 193  [[image:1652953568895-172.png||height="232" width="724"]]
... ... @@ -195,19 +195,23 @@
195 195  == 3.3 Configure Commands to read data ==
196 196  
197 197  (((
198 -(((
199 -There are plenty of RS485 devices in the market and each device has different command to read the valid data. To support these devices in flexible, RS485-LN supports flexible command set. User can use [[AT Commands>>path:#AT_COMMAND]] or LoRaWAN Downlink Command to configure what commands RS485-LN should send for each sampling and how to handle the return from RS485 devices.
195 +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.
200 200  )))
201 201  
202 -(((
203 -(% style="color:red" %)Note: below description and commands are for firmware version >v1.1, if you have firmware version v1.0. Please check the [[user manual v1.0>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/&file=RS485-LN_UserManual_v1.0.1.pdf]] or upgrade the firmware to v1.1
204 -)))
205 -)))
206 -
207 207  === 3.3.1 onfigure UART settings for RS485 or TTL communication ===
208 208  
209 -To use RS485-LN to read data from RS485 sensors, connect the RS485-LN A/B traces to the sensors. And user need to make sure RS485-LN use the match UART setting to access the sensors. The related commands for UART settings are:
200 +RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect.
210 210  
202 +**~1. RS485-MODBUS mode:**
203 +
204 +AT+MOD=1 ~/~/ Support RS485-MODBUS type sensors. User can connect multiply RS485 , Modbus sensors to the A / B pins.
205 +
206 +**2. TTL mode:**
207 +
208 +AT+MOD=2 ~/~/ Support TTL Level sensors, User can connect one TTL Sensor to the TXD/RXD/GND pins.
209 +
210 +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.
211 +
211 211  (% border="1" style="background-color:#ffffcc; color:green; width:795px" %)
212 212  |(((
213 213  **AT Commands**
... ... @@ -232,7 +232,13 @@
232 232  |(((
233 233  AT+PARITY
234 234  )))|(% style="width:285px" %)(((
236 +(((
235 235  Set UART parity (for RS485 connection)
238 +)))
239 +
240 +(((
241 +Default Value is: no parity.
242 +)))
236 236  )))|(% style="width:347px" %)(((
237 237  (((
238 238  AT+PARITY=0
... ... @@ -250,7 +250,7 @@
250 250  )))
251 251  
252 252  (((
253 -
260 +Default Value is: 1bit.
254 254  )))
255 255  )))|(% style="width:347px" %)(((
256 256  (((
... ... @@ -269,10 +269,12 @@
269 269  === 3.3.2 Configure sensors ===
270 270  
271 271  (((
279 +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**.
280 +)))
281 +
272 272  (((
273 -Some sensors might need to configure before normal operation. User can configure such sensor via PC and RS485 adapter or through RS485-LN AT Commands (% style="color:#4f81bd" %)**AT+CFGDEV**(%%). Each (% style="color:#4f81bd" %)**AT+CFGDEV **(%%)equals to send a RS485 command to sensors. This command will only run when user input it and won’t run during each sampling.
283 +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.
274 274  )))
275 -)))
276 276  
277 277  (% border="1" style="background-color:#ffffcc; color:green; width:806px" %)
278 278  |**AT Commands**|(% style="width:418px" %)**Description**|(% style="width:256px" %)**Example**
... ... @@ -284,6 +284,8 @@
284 284  mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
285 285  )))|(% style="width:256px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
286 286  
296 +Detail of AT+CFGDEV command see [[AT+CFGDEV detail>>path:#AT_CFGDEV]].
297 +
287 287  === 3.3.3 Configure read commands for each sampling ===
288 288  
289 289  (((
... ... @@ -365,17 +365,11 @@
365 365  **m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command**
366 366  )))
367 367  
368 -(((
369 369  For example, if we have a RS485 sensor. The command to get sensor value is: 01 03 0B B8 00 02 46 0A. Where 01 03 0B B8 00 02 is the Modbus command to read the register 0B B8 where stored the sensor value. The 46 0A is the CRC-16/MODBUS which calculate manually.
370 -)))
371 371  
372 -(((
373 373  In the RS485-BL, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
374 -)))
375 375  
376 -(((
377 377  **AT+SEARCHx**: This command defines how to handle the return from AT+COMMANDx.
378 -)))
379 379  
380 380  (% border="1" class="table-bordered" %)
381 381  |(((
... ... @@ -387,24 +387,26 @@
387 387  
388 388  )))
389 389  
390 -**Examples:**
395 +Examples:
391 391  
392 -~1. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
397 +1. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
393 393  
394 394  If we set AT+SEARCH1=1,1E 56 34.      (max 5 bytes for prefix)
395 395  
396 -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**
401 +The valid data will be all bytes after 1E 56 34 , so it is 2e 30 58 5f 36 41 30 31 00 49
397 397  
398 -[[image:1653269403619-508.png]]
403 +[[image:1652954654347-831.png]]
399 399  
400 -2. For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
401 401  
406 +1. For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
407 +
402 402  If we set AT+SEARCH1=2, 1E 56 34+31 00 49
403 403  
404 -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**
410 +Device will search the bytes between 1E 56 34 and 31 00 49. So it is 2e 30 58 5f 36 41 30
405 405  
406 -[[image:1653269438444-278.png]]
412 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image014.png]]
407 407  
414 +
408 408  **AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes.
409 409  
410 410  |(((
... ... @@ -419,95 +419,94 @@
419 419  
420 420  * Grab bytes:
421 421  
422 -[[image:1653269551753-223.png||height="311" width="717"]]
429 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image015.png]]
423 423  
424 424  * Grab a section.
425 425  
426 -[[image:1653269568276-930.png||height="325" width="718"]]
433 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image016.png]]
427 427  
428 428  * Grab different sections.
429 429  
430 -[[image:1653269593172-426.png||height="303" width="725"]]
437 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image017.png]]
431 431  
432 -(% style="color:red" %)**Note:**
433 433  
440 +Note:
441 +
434 434  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.
435 435  
436 436  Example:
437 437  
438 -(% style="color:red" %)AT+COMMAND1=11 01 1E D0,0
446 +AT+COMMAND1=11 01 1E D0,0
439 439  
440 -(% style="color:red" %)AT+SEARCH1=1,1E 56 34
448 +AT+SEARCH1=1,1E 56 34
441 441  
442 -(% style="color:red" %)AT+DATACUT1=0,2,1~~5
450 +AT+DATACUT1=0,2,1~~5
443 443  
444 -(% style="color:red" %)Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
452 +Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
445 445  
446 -(% style="color:red" %)String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
454 +String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
447 447  
448 -(% style="color:red" %)Valid payload after DataCUT command: 2e 30 58 5f 36
456 +Valid payload after DataCUT command: 2e 30 58 5f 36
449 449  
450 -[[image:1653269618463-608.png]]
458 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image018.png]]
451 451  
452 -=== 3.3.4 Compose the uplink payload ===
453 453  
454 -(((
461 +
462 +
463 +1.
464 +11.
465 +111. Compose the uplink payload
466 +
455 455  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.**
456 -)))
457 457  
458 -(((
459 -(% style="color:#4f81bd" %)**Examples: AT+DATAUP=0**
460 -)))
461 461  
462 -(((
463 -Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**A SIGNLE UPLINK**.
464 -)))
470 +**Examples: AT+DATAUP=0**
465 465  
466 -(((
472 +Compose the uplink payload with value returns in sequence and send with **A SIGNLE UPLINK**.
473 +
467 467  Final Payload is
468 -)))
469 469  
470 -(((
471 -(% style="color:#4f81bd" %)**Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx**
472 -)))
476 +Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx
473 473  
474 -(((
475 475  Where PAYVER is defined by AT+PAYVER, below is an example screen shot.
476 -)))
477 477  
478 -[[image:1653269759169-150.png||height="513" width="716"]]
480 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.png]]
479 479  
480 -(% style="color:#4f81bd" %)**Examples: AT+DATAUP=1**
481 481  
482 -Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**Multiply UPLINKs**.
483 483  
484 +**Examples: AT+DATAUP=1**
485 +
486 +Compose the uplink payload with value returns in sequence and send with **Multiply UPLINKs**.
487 +
484 484  Final Payload is
485 485  
486 -(% style="color:#4f81bd" %)**Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA**
490 +Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA
487 487  
488 488  1. Battery Info (2 bytes): Battery voltage
489 489  1. PAYVER (1 byte): Defined by AT+PAYVER
490 490  1. PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling.
491 491  1. PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
492 -1. 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
496 +1. DATA: Valid value: max 6 bytes(US915 version here, [[Notice*!>>path:#max_byte]]) for each uplink so each uplink <= 11 bytes. For the last uplink, DATA will might less than 6 bytes
493 493  
494 -[[image:1653269916228-732.png||height="433" width="711"]]
498 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image020.png]]
495 495  
496 496  
497 497  So totally there will be 3 uplinks for this sampling, each uplink includes 6 bytes DATA
498 498  
499 -DATA1=RETURN1 Valid Value = (% style="background-color:green; color:white" %)20 20 0a 33 90 41
503 +DATA1=RETURN1 Valid Value = 20 20 0a 33 90 41
500 500  
501 -DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10=(% style="background-color:green; color:white" %) 02 aa 05 81 0a 20
505 +DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= 02 aa 05 81 0a 20
502 502  
503 -DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 = (% style="background-color:green; color:white" %)20 20 20 2d 30
507 +DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 = 20 20 20 2d 30
504 504  
509 +
510 +
505 505  Below are the uplink payloads:
506 506  
507 -[[image:1653270130359-810.png]]
513 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.png]]
508 508  
509 509  
510 -(% style="color:red" %)**Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:**
516 +Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:
511 511  
512 512   ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink ( so 51 -5 = 46 max valid date)
513 513  
... ... @@ -517,8 +517,12 @@
517 517  
518 518   ~* For all other bands: max 51 bytes for each uplink  ( so 51 -5 = 46 max valid date).
519 519  
520 -=== 3.3.5 Uplink on demand ===
521 521  
527 +
528 +1.
529 +11.
530 +111. Uplink on demand
531 +
522 522  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.
523 523  
524 524  Downlink control command:
1653269403619-508.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -27.8 KB
Content
1653269438444-278.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -26.6 KB
Content
1653269551753-223.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -138.7 KB
Content
1653269568276-930.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -131.4 KB
Content
1653269593172-426.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -142.6 KB
Content
1653269618463-608.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -27.7 KB
Content
1653269759169-150.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -294.0 KB
Content
1653269916228-732.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -143.3 KB
Content
1653270130359-810.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -197.8 KB
Content

Applications

Navigation

Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0