Last modified by Karry Zhuang on 2025/03/06 16:34
<
From version < 19.3 >
edited by Xiaoling
on 2022/05/23 08:55
To version < 29.3 >
edited by Xiaoling
on 2022/05/23 09:37
>
Change comment: There is no comment for this version

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  
... ... @@ -76,14 +76,14 @@
76 76  
77 77  == 1.3 Features ==
78 78  
79 -* LoRaWAN Class A & Class C protocol (default Class A)
79 +* LoRaWAN Class A & Class C protocol (default Class C)
80 80  * Frequency Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/IN865/RU864
81 81  * AT Commands to change parameters
82 -* Remote configure parameters via LoRaWAN Downlink
82 +* Remote configure parameters via LoRa Downlink
83 83  * Firmware upgradable via program port
84 84  * Support multiply RS485 devices by flexible rules
85 85  * Support Modbus protocol
86 -* Support Interrupt uplink
86 +* Support Interrupt uplink (Since hardware version v1.2)
87 87  
88 88  == 1.4 Applications ==
89 89  
... ... @@ -96,53 +96,39 @@
96 96  
97 97  == 1.5 Firmware Change log ==
98 98  
99 -[[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);"]]
99 +[[RS485-LN Image files – Download link and Change log>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/]]
100 100  
101 101  == 1.6 Hardware Change log ==
102 102  
103 103  (((
104 -v1.4
105 -)))
106 -
107 107  (((
108 -~1. Change Power IC to TPS22916
109 -)))
105 +v1.2: Add External Interrupt Pin.
110 110  
111 -
112 -(((
113 -v1.3
107 +v1.0: Release
114 114  )))
115 -
116 -(((
117 -~1. Change JP3 from KF350-8P to KF350-11P, Add one extra interface for I2C and one extra interface for one-wire
118 118  )))
119 119  
111 += 2. Power ON Device =
120 120  
121 121  (((
122 -v1.2
123 -)))
114 +The RS485-LN can be powered by 7 ~~ 24V DC power source. Connection as below
124 124  
116 +* Power Source VIN to RS485-LN VIN+
117 +* Power Source GND to RS485-LN VIN-
118 +
125 125  (((
126 -Release version ​​​​​
120 +Once there is power, the RS485-LN will be on.
127 127  )))
128 128  
129 -= 2. Pin mapping and Power ON Device =
130 -
131 -(((
132 -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.
123 +[[image:1653268091319-405.png]]
133 133  )))
134 134  
135 -[[image:1652953055962-143.png||height="387" width="728"]]
136 -
137 -
138 -The Left TXD and RXD are TTL interface for external sensor. TTL level is controlled by 3.3/5v Jumper.
139 -
140 140  = 3. Operation Mode =
141 141  
142 142  == 3.1 How it works? ==
143 143  
144 144  (((
145 -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.
131 +The RS485-LN is configured as LoRaWAN OTAA Class C 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-LN. It will auto join the network via OTAA.
146 146  )))
147 147  
148 148  == 3.2 Example to join LoRaWAN network ==
... ... @@ -149,27 +149,32 @@
149 149  
150 150  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. 
151 151  
152 -[[image:1652953414711-647.png||height="337" width="723"]]
138 +[[image:1653268155545-638.png||height="334" width="724"]]
153 153  
154 154  (((
155 -The RS485-BL in this example connected to two RS485 devices for demonstration, user can connect to other RS485 devices via the same method.
156 -)))
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:
157 157  
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 +
158 158  (((
159 -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:
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:
160 160  )))
161 161  
162 162  (((
163 -**Step 1**: Create a device in TTN V3 with the OTAA keys from RS485-BL.
152 +**Step 1**: Create a device in TTN V3 with the OTAA keys from RS485-LN.
164 164  )))
165 165  
166 166  (((
167 -Each RS485-BL is shipped with a sticker with unique device EUI:
156 +Each RS485-LN is shipped with a sticker with unique device EUI:
168 168  )))
158 +)))
169 169  
170 170  [[image:1652953462722-299.png]]
171 171  
172 172  (((
163 +(((
173 173  User can enter this key in their LoRaWAN Server portal. Below is TTN V3 screen shot:
174 174  )))
175 175  
... ... @@ -176,13 +176,11 @@
176 176  (((
177 177  Add APP EUI in the application.
178 178  )))
170 +)))
179 179  
180 -
181 -
182 -
183 183  [[image:image-20220519174512-1.png]]
184 184  
185 -[[image:image-20220519174512-2.png||height="328" width="731"]]
174 +[[image:image-20220519174512-2.png||height="323" width="720"]]
186 186  
187 187  [[image:image-20220519174512-3.png||height="556" width="724"]]
188 188  
... ... @@ -198,7 +198,7 @@
198 198  
199 199  
200 200  (((
201 -**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.
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.
202 202  )))
203 203  
204 204  [[image:1652953568895-172.png||height="232" width="724"]]
... ... @@ -206,23 +206,19 @@
206 206  == 3.3 Configure Commands to read data ==
207 207  
208 208  (((
209 -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.
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.
210 210  )))
211 211  
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 +
212 212  === 3.3.1 onfigure UART settings for RS485 or TTL communication ===
213 213  
214 -RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect.
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:
215 215  
216 -**~1. RS485-MODBUS mode:**
217 -
218 -AT+MOD=1 ~/~/ Support RS485-MODBUS type sensors. User can connect multiply RS485 , Modbus sensors to the A / B pins.
219 -
220 -**2. TTL mode:**
221 -
222 -AT+MOD=2 ~/~/ Support TTL Level sensors, User can connect one TTL Sensor to the TXD/RXD/GND pins.
223 -
224 -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.
225 -
226 226  (% border="1" style="background-color:#ffffcc; color:green; width:795px" %)
227 227  |(((
228 228  **AT Commands**
... ... @@ -247,13 +247,7 @@
247 247  |(((
248 248  AT+PARITY
249 249  )))|(% style="width:285px" %)(((
250 -(((
251 251  Set UART parity (for RS485 connection)
252 -)))
253 -
254 -(((
255 -Default Value is: no parity.
256 -)))
257 257  )))|(% style="width:347px" %)(((
258 258  (((
259 259  AT+PARITY=0
... ... @@ -271,7 +271,7 @@
271 271  )))
272 272  
273 273  (((
274 -Default Value is: 1bit.
253 +
275 275  )))
276 276  )))|(% style="width:347px" %)(((
277 277  (((
... ... @@ -290,12 +290,10 @@
290 290  === 3.3.2 Configure sensors ===
291 291  
292 292  (((
293 -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**.
294 -)))
295 -
296 296  (((
297 -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.
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.
298 298  )))
275 +)))
299 299  
300 300  (% border="1" style="background-color:#ffffcc; color:green; width:806px" %)
301 301  |**AT Commands**|(% style="width:418px" %)**Description**|(% style="width:256px" %)**Example**
... ... @@ -307,8 +307,6 @@
307 307  mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
308 308  )))|(% style="width:256px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
309 309  
310 -Detail of AT+CFGDEV command see [[AT+CFGDEV detail>>path:#AT_CFGDEV]].
311 -
312 312  === 3.3.3 Configure read commands for each sampling ===
313 313  
314 314  (((
... ... @@ -390,11 +390,17 @@
390 390  **m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command**
391 391  )))
392 392  
368 +(((
393 393  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 +)))
394 394  
372 +(((
395 395  In the RS485-BL, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
374 +)))
396 396  
376 +(((
397 397  **AT+SEARCHx**: This command defines how to handle the return from AT+COMMANDx.
378 +)))
398 398  
399 399  (% border="1" class="table-bordered" %)
400 400  |(((
... ... @@ -406,26 +406,24 @@
406 406  
407 407  )))
408 408  
409 -Examples:
390 +**Examples:**
410 410  
411 -1. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
392 +~1. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
412 412  
413 413  If we set AT+SEARCH1=1,1E 56 34.      (max 5 bytes for prefix)
414 414  
415 -The valid data will be all bytes after 1E 56 34 , so it is 2e 30 58 5f 36 41 30 31 00 49
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**
416 416  
417 -[[image:1652954654347-831.png]]
398 +[[image:1653269403619-508.png]]
418 418  
400 +2. For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
419 419  
420 -1. For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
421 -
422 422  If we set AT+SEARCH1=2, 1E 56 34+31 00 49
423 423  
424 -Device will search the bytes between 1E 56 34 and 31 00 49. So it is 2e 30 58 5f 36 41 30
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**
425 425  
426 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image014.png]]
406 +[[image:1653269438444-278.png]]
427 427  
428 -
429 429  **AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes.
430 430  
431 431  |(((
... ... @@ -440,58 +440,63 @@
440 440  
441 441  * Grab bytes:
442 442  
443 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image015.png]]
422 +[[image:1653269551753-223.png||height="311" width="717"]]
444 444  
445 445  * Grab a section.
446 446  
447 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image016.png]]
426 +[[image:1653269568276-930.png||height="325" width="718"]]
448 448  
449 449  * Grab different sections.
450 450  
451 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image017.png]]
430 +[[image:1653269593172-426.png||height="303" width="725"]]
452 452  
432 +(% style="color:red" %)**Note:**
453 453  
454 -Note:
455 -
456 456  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.
457 457  
458 458  Example:
459 459  
460 -AT+COMMAND1=11 01 1E D0,0
438 +(% style="color:red" %)AT+COMMAND1=11 01 1E D0,0
461 461  
462 -AT+SEARCH1=1,1E 56 34
440 +(% style="color:red" %)AT+SEARCH1=1,1E 56 34
463 463  
464 -AT+DATACUT1=0,2,1~~5
442 +(% style="color:red" %)AT+DATACUT1=0,2,1~~5
465 465  
466 -Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
444 +(% style="color:red" %)Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
467 467  
468 -String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
446 +(% style="color:red" %)String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
469 469  
470 -Valid payload after DataCUT command: 2e 30 58 5f 36
448 +(% style="color:red" %)Valid payload after DataCUT command: 2e 30 58 5f 36
471 471  
472 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image018.png]]
450 +[[image:1653269618463-608.png]]
473 473  
452 +=== 3.3.4 Compose the uplink payload ===
474 474  
475 -
476 -
477 -1.
478 -11.
479 -111. Compose the uplink payload
480 -
454 +(((
481 481  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 +)))
482 482  
458 +(((
459 +(% style="color:#4f81bd" %)**Examples: AT+DATAUP=0**
460 +)))
483 483  
484 -**Examples: AT+DATAUP=0**
462 +(((
463 +Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**A SIGNLE UPLINK**.
464 +)))
485 485  
486 -Compose the uplink payload with value returns in sequence and send with **A SIGNLE UPLINK**.
487 -
466 +(((
488 488  Final Payload is
468 +)))
489 489  
490 -Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx
470 +(((
471 +(% style="color:#4f81bd" %)**Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx**
472 +)))
491 491  
474 +(((
492 492  Where PAYVER is defined by AT+PAYVER, below is an example screen shot.
476 +)))
493 493  
494 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.png]]
478 +[[image:1653269759169-150.png||height="513" width="716"]]
495 495  
496 496  
497 497  
1653268091319-405.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +399.3 KB
Content
1653268155545-638.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +113.7 KB
Content
1653268227651-549.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +1.3 MB
Content
1653269403619-508.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +27.8 KB
Content
1653269438444-278.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +26.6 KB
Content
1653269551753-223.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +138.7 KB
Content
1653269568276-930.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +131.4 KB
Content
1653269593172-426.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +142.6 KB
Content
1653269618463-608.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +27.7 KB
Content
1653269759169-150.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +294.0 KB
Content

Applications

Navigation

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