Last modified by Karry Zhuang on 2025/03/06 16:34
<
From version < 19.2 >
edited by Xiaoling
on 2022/05/23 08:53
To version < 30.1 >
edited by Xiaoling
on 2022/05/23 09:38
>
Change comment: Uploaded new attachment "1653269916228-732.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -43,19 +43,15 @@
43 43  * STM32L072CZT6 MCU
44 44  * SX1276/78 Wireless Chip 
45 45  * Power Consumption (exclude RS485 device):
46 -** Idle: 6uA@3.3v
46 +** Idle: 32mA@12v
47 47  
48 48  *
49 -** 20dB Transmit: 130mA@3.3v
49 +** 20dB Transmit: 65mA@12v
50 50  
51 51  **Interface for Model:**
52 52  
53 -* 1 x RS485 Interface
54 -* 1 x TTL Serial , 3.3v or 5v.
55 -* 1 x I2C Interface, 3.3v or 5v.
56 -* 1 x one wire interface
57 -* 1 x Interrupt Interface
58 -* 1 x Controllable 5V output, max
53 +* RS485
54 +* Power Input 7~~ 24V DC. 
59 59  
60 60  **LoRa Spec:**
61 61  
... ... @@ -64,27 +64,30 @@
64 64  ** Band 2 (LF): 410 ~~ 528 Mhz
65 65  * 168 dB maximum link budget.
66 66  * +20 dBm - 100 mW constant RF output vs.
63 +* +14 dBm high efficiency PA.
67 67  * Programmable bit rate up to 300 kbps.
68 68  * High sensitivity: down to -148 dBm.
69 69  * Bullet-proof front end: IIP3 = -12.5 dBm.
70 70  * Excellent blocking immunity.
68 +* Low RX current of 10.3 mA, 200 nA register retention.
71 71  * Fully integrated synthesizer with a resolution of 61 Hz.
72 -* LoRa modulation.
70 +* FSK, GFSK, MSK, GMSK, LoRaTM and OOK modulation.
73 73  * Built-in bit synchronizer for clock recovery.
74 74  * Preamble detection.
75 75  * 127 dB Dynamic Range RSSI.
76 -* Automatic RF Sense and CAD with ultra-fast AFC. ​​​
74 +* Automatic RF Sense and CAD with ultra-fast AFC.
75 +* Packet engine up to 256 bytes with CRC.
77 77  
78 78  == 1.3 Features ==
79 79  
80 -* LoRaWAN Class A & Class C protocol (default Class A)
79 +* LoRaWAN Class A & Class C protocol (default Class C)
81 81  * Frequency Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/IN865/RU864
82 82  * AT Commands to change parameters
83 -* Remote configure parameters via LoRaWAN Downlink
82 +* Remote configure parameters via LoRa Downlink
84 84  * Firmware upgradable via program port
85 85  * Support multiply RS485 devices by flexible rules
86 86  * Support Modbus protocol
87 -* Support Interrupt uplink
86 +* Support Interrupt uplink (Since hardware version v1.2)
88 88  
89 89  == 1.4 Applications ==
90 90  
... ... @@ -97,53 +97,39 @@
97 97  
98 98  == 1.5 Firmware Change log ==
99 99  
100 -[[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/]]
101 101  
102 102  == 1.6 Hardware Change log ==
103 103  
104 104  (((
105 -v1.4
106 -)))
107 -
108 108  (((
109 -~1. Change Power IC to TPS22916
110 -)))
105 +v1.2: Add External Interrupt Pin.
111 111  
112 -
113 -(((
114 -v1.3
107 +v1.0: Release
115 115  )))
116 -
117 -(((
118 -~1. Change JP3 from KF350-8P to KF350-11P, Add one extra interface for I2C and one extra interface for one-wire
119 119  )))
120 120  
111 += 2. Power ON Device =
121 121  
122 122  (((
123 -v1.2
124 -)))
114 +The RS485-LN can be powered by 7 ~~ 24V DC power source. Connection as below
125 125  
116 +* Power Source VIN to RS485-LN VIN+
117 +* Power Source GND to RS485-LN VIN-
118 +
126 126  (((
127 -Release version ​​​​​
120 +Once there is power, the RS485-LN will be on.
128 128  )))
129 129  
130 -= 2. Pin mapping and Power ON Device =
131 -
132 -(((
133 -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]]
134 134  )))
135 135  
136 -[[image:1652953055962-143.png||height="387" width="728"]]
137 -
138 -
139 -The Left TXD and RXD are TTL interface for external sensor. TTL level is controlled by 3.3/5v Jumper.
140 -
141 141  = 3. Operation Mode =
142 142  
143 143  == 3.1 How it works? ==
144 144  
145 145  (((
146 -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.
147 147  )))
148 148  
149 149  == 3.2 Example to join LoRaWAN network ==
... ... @@ -150,27 +150,32 @@
150 150  
151 151  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. 
152 152  
153 -[[image:1652953414711-647.png||height="337" width="723"]]
138 +[[image:1653268155545-638.png||height="334" width="724"]]
154 154  
155 155  (((
156 -The RS485-BL in this example connected to two RS485 devices for demonstration, user can connect to other RS485 devices via the same method.
157 -)))
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:
158 158  
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 +
159 159  (((
160 -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:
161 161  )))
162 162  
163 163  (((
164 -**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.
165 165  )))
166 166  
167 167  (((
168 -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:
169 169  )))
158 +)))
170 170  
171 171  [[image:1652953462722-299.png]]
172 172  
173 173  (((
163 +(((
174 174  User can enter this key in their LoRaWAN Server portal. Below is TTN V3 screen shot:
175 175  )))
176 176  
... ... @@ -177,13 +177,11 @@
177 177  (((
178 178  Add APP EUI in the application.
179 179  )))
170 +)))
180 180  
181 -
182 -
183 -
184 184  [[image:image-20220519174512-1.png]]
185 185  
186 -[[image:image-20220519174512-2.png||height="328" width="731"]]
174 +[[image:image-20220519174512-2.png||height="323" width="720"]]
187 187  
188 188  [[image:image-20220519174512-3.png||height="556" width="724"]]
189 189  
... ... @@ -199,7 +199,7 @@
199 199  
200 200  
201 201  (((
202 -**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.
203 203  )))
204 204  
205 205  [[image:1652953568895-172.png||height="232" width="724"]]
... ... @@ -207,23 +207,19 @@
207 207  == 3.3 Configure Commands to read data ==
208 208  
209 209  (((
210 -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.
211 211  )))
212 212  
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 +
213 213  === 3.3.1 onfigure UART settings for RS485 or TTL communication ===
214 214  
215 -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:
216 216  
217 -**~1. RS485-MODBUS mode:**
218 -
219 -AT+MOD=1 ~/~/ Support RS485-MODBUS type sensors. User can connect multiply RS485 , Modbus sensors to the A / B pins.
220 -
221 -**2. TTL mode:**
222 -
223 -AT+MOD=2 ~/~/ Support TTL Level sensors, User can connect one TTL Sensor to the TXD/RXD/GND pins.
224 -
225 -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.
226 -
227 227  (% border="1" style="background-color:#ffffcc; color:green; width:795px" %)
228 228  |(((
229 229  **AT Commands**
... ... @@ -248,13 +248,7 @@
248 248  |(((
249 249  AT+PARITY
250 250  )))|(% style="width:285px" %)(((
251 -(((
252 252  Set UART parity (for RS485 connection)
253 -)))
254 -
255 -(((
256 -Default Value is: no parity.
257 -)))
258 258  )))|(% style="width:347px" %)(((
259 259  (((
260 260  AT+PARITY=0
... ... @@ -272,7 +272,7 @@
272 272  )))
273 273  
274 274  (((
275 -Default Value is: 1bit.
253 +
276 276  )))
277 277  )))|(% style="width:347px" %)(((
278 278  (((
... ... @@ -291,12 +291,10 @@
291 291  === 3.3.2 Configure sensors ===
292 292  
293 293  (((
294 -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**.
295 -)))
296 -
297 297  (((
298 -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.
299 299  )))
275 +)))
300 300  
301 301  (% border="1" style="background-color:#ffffcc; color:green; width:806px" %)
302 302  |**AT Commands**|(% style="width:418px" %)**Description**|(% style="width:256px" %)**Example**
... ... @@ -308,8 +308,6 @@
308 308  mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
309 309  )))|(% style="width:256px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
310 310  
311 -Detail of AT+CFGDEV command see [[AT+CFGDEV detail>>path:#AT_CFGDEV]].
312 -
313 313  === 3.3.3 Configure read commands for each sampling ===
314 314  
315 315  (((
... ... @@ -391,11 +391,17 @@
391 391  **m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command**
392 392  )))
393 393  
368 +(((
394 394  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 +)))
395 395  
372 +(((
396 396  In the RS485-BL, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
374 +)))
397 397  
376 +(((
398 398  **AT+SEARCHx**: This command defines how to handle the return from AT+COMMANDx.
378 +)))
399 399  
400 400  (% border="1" class="table-bordered" %)
401 401  |(((
... ... @@ -407,26 +407,24 @@
407 407  
408 408  )))
409 409  
410 -Examples:
390 +**Examples:**
411 411  
412 -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
413 413  
414 414  If we set AT+SEARCH1=1,1E 56 34.      (max 5 bytes for prefix)
415 415  
416 -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**
417 417  
418 -[[image:1652954654347-831.png]]
398 +[[image:1653269403619-508.png]]
419 419  
400 +2. For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
420 420  
421 -1. For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
422 -
423 423  If we set AT+SEARCH1=2, 1E 56 34+31 00 49
424 424  
425 -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**
426 426  
427 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image014.png]]
406 +[[image:1653269438444-278.png]]
428 428  
429 -
430 430  **AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes.
431 431  
432 432  |(((
... ... @@ -441,58 +441,63 @@
441 441  
442 442  * Grab bytes:
443 443  
444 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image015.png]]
422 +[[image:1653269551753-223.png||height="311" width="717"]]
445 445  
446 446  * Grab a section.
447 447  
448 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image016.png]]
426 +[[image:1653269568276-930.png||height="325" width="718"]]
449 449  
450 450  * Grab different sections.
451 451  
452 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image017.png]]
430 +[[image:1653269593172-426.png||height="303" width="725"]]
453 453  
432 +(% style="color:red" %)**Note:**
454 454  
455 -Note:
456 -
457 457  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.
458 458  
459 459  Example:
460 460  
461 -AT+COMMAND1=11 01 1E D0,0
438 +(% style="color:red" %)AT+COMMAND1=11 01 1E D0,0
462 462  
463 -AT+SEARCH1=1,1E 56 34
440 +(% style="color:red" %)AT+SEARCH1=1,1E 56 34
464 464  
465 -AT+DATACUT1=0,2,1~~5
442 +(% style="color:red" %)AT+DATACUT1=0,2,1~~5
466 466  
467 -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
468 468  
469 -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
470 470  
471 -Valid payload after DataCUT command: 2e 30 58 5f 36
448 +(% style="color:red" %)Valid payload after DataCUT command: 2e 30 58 5f 36
472 472  
473 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image018.png]]
450 +[[image:1653269618463-608.png]]
474 474  
452 +=== 3.3.4 Compose the uplink payload ===
475 475  
476 -
477 -
478 -1.
479 -11.
480 -111. Compose the uplink payload
481 -
454 +(((
482 482  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 +)))
483 483  
458 +(((
459 +(% style="color:#4f81bd" %)**Examples: AT+DATAUP=0**
460 +)))
484 484  
485 -**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 +)))
486 486  
487 -Compose the uplink payload with value returns in sequence and send with **A SIGNLE UPLINK**.
488 -
466 +(((
489 489  Final Payload is
468 +)))
490 490  
491 -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 +)))
492 492  
474 +(((
493 493  Where PAYVER is defined by AT+PAYVER, below is an example screen shot.
476 +)))
494 494  
495 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.png]]
478 +[[image:1653269759169-150.png||height="513" width="716"]]
496 496  
497 497  
498 498  
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
1653269916228-732.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +143.3 KB
Content

Applications

Navigation

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