Last modified by Karry Zhuang on 2025/03/06 16:34
<
From version < 15.4 >
edited by Xiaoling
on 2022/05/19 17:48
To version < 23.1 >
edited by Xiaoling
on 2022/05/23 09:30
>
Change comment: Uploaded new attachment "1653269403619-508.png", version {1}

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -RS485-BL – Waterproof RS485 to LoRaWAN Converter
1 +RS485-LN – RS485 to LoRaWAN Converter
Content
... ... @@ -1,12 +1,11 @@
1 1  (% style="text-align:center" %)
2 -[[image:1652947681187-144.png||height="385" width="385"]]
2 +[[image:1653266934636-343.png||height="385" width="385"]]
3 3  
4 4  
5 5  
6 +**RS485-LN – RS485 to LoRaWAN Converter User Manual**
6 6  
7 -**RS485-BL – Waterproof RS485 to LoRaWAN Converter User Manual**
8 8  
9 -
10 10  **Table of Contents:**
11 11  
12 12  
... ... @@ -15,42 +15,28 @@
15 15  
16 16  = 1.Introduction =
17 17  
18 -== 1.1 What is RS485-BL RS485 to LoRaWAN Converter ==
17 +== 1.1 What is RS485-LN RS485 to LoRaWAN Converter ==
19 19  
20 20  (((
21 -
22 -)))
23 -
24 24  (((
25 -The Dragino RS485-BL is a **RS485 / UART to LoRaWAN Converter** for Internet of Things solutions. User can connect RS485 or UART sensor to RS485-BL converter, and configure RS485-BL to periodically read sensor data and upload via LoRaWAN network to IoT server.
21 +The Dragino RS485-LN is a RS485 to LoRaWAN Converter. It converts the RS485 signal into LoRaWAN wireless signal which simplify the IoT installation and reduce the installation/maintaining cost.
26 26  )))
27 27  
28 28  (((
29 -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.
25 +RS485-LN allows user to monitor / control RS485 devices and reach extremely long ranges. It provides ultra-long range spread spectrum communication and high interference immunity whilst minimizing current consumption. It targets professional wireless sensor network applications such as irrigation systems, smart metering, smart cities, smartphone detection, building automation, and so on.
30 30  )))
31 31  
32 32  (((
33 -RS485-BL is IP67 **waterproof** and powered by **8500mAh Li-SOCI2 battery**, it is designed for long term use for several years.
29 +For data uplink, RS485-LN sends user-defined commands to RS485 devices and gets the return from the RS485 devices. RS485-LN will process these returns according to user-define rules to get the final payload and upload to LoRaWAN server.
34 34  )))
35 35  
36 36  (((
37 -RS485-BL runs standard **LoRaWAN 1.0.3 in Class A**. It can reach long transfer range and easy to integrate with LoRaWAN compatible gateway and IoT server.
33 +For data downlink, RS485-LN runs in LoRaWAN Class C. When there downlink commands from LoRaWAN server, RS485-LN will forward the commands from LoRaWAN server to RS485 devices.
38 38  )))
39 -
40 -(((
41 -For data uplink, RS485-BL sends user-defined commands to RS485 devices and gets the return from the RS485 devices. RS485-BL will process these returns data according to user-define rules to get the final payload and upload to LoRaWAN server.
42 42  )))
43 43  
44 -(((
45 -For data downlink, RS485-BL runs in LoRaWAN Class A. When there is downlink commands from LoRaWAN server, RS485-BL will forward the commands from LoRaWAN server to RS485 devices.
46 -)))
37 +[[image:1653267211009-519.png||height="419" width="724"]]
47 47  
48 -(((
49 -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.
50 -)))
51 -
52 -[[image:1652953304999-717.png||height="424" width="733"]]
53 -
54 54  == 1.2 Specifications ==
55 55  
56 56  **Hardware System:**
... ... @@ -58,19 +58,15 @@
58 58  * STM32L072CZT6 MCU
59 59  * SX1276/78 Wireless Chip 
60 60  * Power Consumption (exclude RS485 device):
61 -** Idle: 6uA@3.3v
46 +** Idle: 32mA@12v
62 62  
63 63  *
64 -** 20dB Transmit: 130mA@3.3v
49 +** 20dB Transmit: 65mA@12v
65 65  
66 66  **Interface for Model:**
67 67  
68 -* 1 x RS485 Interface
69 -* 1 x TTL Serial , 3.3v or 5v.
70 -* 1 x I2C Interface, 3.3v or 5v.
71 -* 1 x one wire interface
72 -* 1 x Interrupt Interface
73 -* 1 x Controllable 5V output, max
53 +* RS485
54 +* Power Input 7~~ 24V DC. 
74 74  
75 75  **LoRa Spec:**
76 76  
... ... @@ -79,27 +79,30 @@
79 79  ** Band 2 (LF): 410 ~~ 528 Mhz
80 80  * 168 dB maximum link budget.
81 81  * +20 dBm - 100 mW constant RF output vs.
63 +* +14 dBm high efficiency PA.
82 82  * Programmable bit rate up to 300 kbps.
83 83  * High sensitivity: down to -148 dBm.
84 84  * Bullet-proof front end: IIP3 = -12.5 dBm.
85 85  * Excellent blocking immunity.
68 +* Low RX current of 10.3 mA, 200 nA register retention.
86 86  * Fully integrated synthesizer with a resolution of 61 Hz.
87 -* LoRa modulation.
70 +* FSK, GFSK, MSK, GMSK, LoRaTM and OOK modulation.
88 88  * Built-in bit synchronizer for clock recovery.
89 89  * Preamble detection.
90 90  * 127 dB Dynamic Range RSSI.
91 -* 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.
92 92  
93 93  == 1.3 Features ==
94 94  
95 -* LoRaWAN Class A & Class C protocol (default Class A)
79 +* LoRaWAN Class A & Class C protocol (default Class C)
96 96  * Frequency Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/IN865/RU864
97 97  * AT Commands to change parameters
98 -* Remote configure parameters via LoRaWAN Downlink
82 +* Remote configure parameters via LoRa Downlink
99 99  * Firmware upgradable via program port
100 100  * Support multiply RS485 devices by flexible rules
101 101  * Support Modbus protocol
102 -* Support Interrupt uplink
86 +* Support Interrupt uplink (Since hardware version v1.2)
103 103  
104 104  == 1.4 Applications ==
105 105  
... ... @@ -112,53 +112,39 @@
112 112  
113 113  == 1.5 Firmware Change log ==
114 114  
115 -[[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/]]
116 116  
117 117  == 1.6 Hardware Change log ==
118 118  
119 119  (((
120 -v1.4
121 -)))
122 -
123 123  (((
124 -~1. Change Power IC to TPS22916
125 -)))
105 +v1.2: Add External Interrupt Pin.
126 126  
127 -
128 -(((
129 -v1.3
107 +v1.0: Release
130 130  )))
131 -
132 -(((
133 -~1. Change JP3 from KF350-8P to KF350-11P, Add one extra interface for I2C and one extra interface for one-wire
134 134  )))
135 135  
111 += 2. Power ON Device =
136 136  
137 137  (((
138 -v1.2
139 -)))
114 +The RS485-LN can be powered by 7 ~~ 24V DC power source. Connection as below
140 140  
116 +* Power Source VIN to RS485-LN VIN+
117 +* Power Source GND to RS485-LN VIN-
118 +
141 141  (((
142 -Release version ​​​​​
120 +Once there is power, the RS485-LN will be on.
143 143  )))
144 144  
145 -= 2. Pin mapping and Power ON Device =
146 -
147 -(((
148 -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]]
149 149  )))
150 150  
151 -[[image:1652953055962-143.png||height="387" width="728"]]
152 -
153 -
154 -The Left TXD and RXD are TTL interface for external sensor. TTL level is controlled by 3.3/5v Jumper.
155 -
156 156  = 3. Operation Mode =
157 157  
158 158  == 3.1 How it works? ==
159 159  
160 160  (((
161 -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.
162 162  )))
163 163  
164 164  == 3.2 Example to join LoRaWAN network ==
... ... @@ -165,27 +165,32 @@
165 165  
166 166  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 167  
168 -[[image:1652953414711-647.png||height="337" width="723"]]
138 +[[image:1653268155545-638.png||height="334" width="724"]]
169 169  
170 170  (((
171 -The RS485-BL in this example connected to two RS485 devices for demonstration, user can connect to other RS485 devices via the same method.
172 -)))
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:
173 173  
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 +
174 174  (((
175 -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:
176 176  )))
177 177  
178 178  (((
179 -**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.
180 180  )))
181 181  
182 182  (((
183 -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:
184 184  )))
158 +)))
185 185  
186 186  [[image:1652953462722-299.png]]
187 187  
188 188  (((
163 +(((
189 189  User can enter this key in their LoRaWAN Server portal. Below is TTN V3 screen shot:
190 190  )))
191 191  
... ... @@ -192,13 +192,11 @@
192 192  (((
193 193  Add APP EUI in the application.
194 194  )))
170 +)))
195 195  
196 -
197 -
198 -
199 199  [[image:image-20220519174512-1.png]]
200 200  
201 -[[image:image-20220519174512-2.png||height="328" width="731"]]
174 +[[image:image-20220519174512-2.png||height="323" width="720"]]
202 202  
203 203  [[image:image-20220519174512-3.png||height="556" width="724"]]
204 204  
... ... @@ -214,147 +214,176 @@
214 214  
215 215  
216 216  (((
217 -**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.
218 218  )))
219 219  
220 220  [[image:1652953568895-172.png||height="232" width="724"]]
221 221  
195 +== 3.3 Configure Commands to read data ==
222 222  
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.
200 +)))
223 223  
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 +)))
224 224  
225 -1.
226 -11. Configure Commands to read data
207 +=== 3.3.1 onfigure UART settings for RS485 or TTL communication ===
227 227  
228 -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.
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:
229 229  
230 -
231 -1.
232 -11.
233 -111. Configure UART settings for RS485 or TTL communication
234 -
235 -RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect.
236 -
237 -1. RS485-MODBUS mode:
238 -
239 -AT+MOD=1 ~/~/ Support RS485-MODBUS type sensors. User can connect multiply RS485 , Modbus sensors to the A / B pins.
240 -
241 -
242 -1. TTL mode:
243 -
244 -AT+MOD=2 ~/~/ Support TTL Level sensors, User can connect one TTL Sensor to the TXD/RXD/GND pins.
245 -
246 -
247 -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.
248 -
249 -
250 -|**AT Commands**|**Description**|**Example**
251 -|AT+BAUDR|Set the baud rate (for RS485 connection). Default Value is: 9600.|(((
211 +(% border="1" style="background-color:#ffffcc; color:green; width:795px" %)
212 +|(((
213 +**AT Commands**
214 +)))|(% style="width:285px" %)(((
215 +**Description**
216 +)))|(% style="width:347px" %)(((
217 +**Example**
218 +)))
219 +|(((
220 +AT+BAUDR
221 +)))|(% style="width:285px" %)(((
222 +Set the baud rate (for RS485 connection). Default Value is: 9600.
223 +)))|(% style="width:347px" %)(((
224 +(((
252 252  AT+BAUDR=9600
226 +)))
253 253  
228 +(((
254 254  Options: (1200,2400,4800,14400,19200,115200)
255 255  )))
256 -|AT+PARITY|(((
231 +)))
232 +|(((
233 +AT+PARITY
234 +)))|(% style="width:285px" %)(((
257 257  Set UART parity (for RS485 connection)
258 -
259 -Default Value is: no parity.
260 -)))|(((
236 +)))|(% style="width:347px" %)(((
237 +(((
261 261  AT+PARITY=0
239 +)))
262 262  
241 +(((
263 263  Option: 0: no parity, 1: odd parity, 2: even parity
264 264  )))
265 -|AT+STOPBIT|(((
244 +)))
245 +|(((
246 +AT+STOPBIT
247 +)))|(% style="width:285px" %)(((
248 +(((
266 266  Set serial stopbit (for RS485 connection)
250 +)))
267 267  
268 -Default Value is: 1bit.
269 -)))|(((
252 +(((
253 +
254 +)))
255 +)))|(% style="width:347px" %)(((
256 +(((
270 270  AT+STOPBIT=0 for 1bit
258 +)))
271 271  
260 +(((
272 272  AT+STOPBIT=1 for 1.5 bit
262 +)))
273 273  
264 +(((
274 274  AT+STOPBIT=2 for 2 bits
275 275  )))
267 +)))
276 276  
269 +=== 3.3.2 Configure sensors ===
277 277  
271 +(((
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.
274 +)))
275 +)))
278 278  
279 -
280 -1.
281 -11.
282 -111. Configure sensors
283 -
284 -Some sensors might need to configure before normal operation. User can configure such sensor via PC or through RS485-BL AT Commands AT+CFGDEV.
285 -
286 -
287 -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.
288 -
289 -|**AT Commands**|**Description**|**Example**
290 -|AT+CFGDEV|(((
277 +(% border="1" style="background-color:#ffffcc; color:green; width:806px" %)
278 +|**AT Commands**|(% style="width:418px" %)**Description**|(% style="width:256px" %)**Example**
279 +|AT+CFGDEV|(% style="width:418px" %)(((
291 291  This command is used to configure the RS485/TTL devices; they won’t be used during sampling.
292 292  
293 -AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
282 +AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,
294 294  
295 -m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
296 -)))|AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
284 +mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
285 +)))|(% style="width:256px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
297 297  
298 -Detail of AT+CFGDEV command see [[AT+CFGDEV detail>>path:#AT_CFGDEV]].
287 +=== 3.3.3 Configure read commands for each sampling ===
299 299  
300 -
301 -
302 -
303 -
304 -1.
305 -11.
306 -111. Configure read commands for each sampling
307 -
289 +(((
308 308  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.
291 +)))
309 309  
310 -
293 +(((
311 311  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.
295 +)))
312 312  
313 -
297 +(((
314 314  To save the LoRaWAN network bandwidth, we might need to read data from different sensors and combine their valid value into a short payload.
299 +)))
315 315  
316 -
301 +(((
317 317  This section describes how to achieve above goals.
303 +)))
318 318  
319 -
305 +(((
320 320  During each sampling, the RS485-BL can support 15 commands to read sensors. And combine the return to one or several uplink payloads.
307 +)))
321 321  
322 -
309 +(((
323 323  **Command from RS485-BL to Sensor:**
311 +)))
324 324  
313 +(((
325 325  RS485-BL can send out pre-set max 15 strings via **AT+COMMAD1**, **ATCOMMAND2**,…, to **AT+COMMANDF** . All commands are of same grammar.
315 +)))
326 326  
327 -
317 +(((
328 328  **Handle return from sensors to RS485-BL**:
319 +)))
329 329  
321 +(((
330 330  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**
323 +)))
331 331  
325 +* (((
326 +**AT+DATACUT**
327 +)))
332 332  
333 -* **AT+DATACUT**
334 -
329 +(((
335 335  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.
331 +)))
336 336  
333 +* (((
334 +**AT+SEARCH**
335 +)))
337 337  
338 -* **AT+SEARCH**
339 -
337 +(((
340 340  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.
339 +)))
341 341  
342 -
341 +(((
343 343  **Define wait timeout:**
343 +)))
344 344  
345 +(((
345 345  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
347 +)))
346 346  
347 -
349 +(((
348 348  After we got the valid value from each RS485 commands, we need to combine them together with the command **AT+DATAUP**.
351 +)))
349 349  
350 -
351 351  **Examples:**
352 352  
353 353  Below are examples for the how above AT Commands works.
354 354  
355 -
356 356  **AT+COMMANDx : **This command will be sent to RS485/TTL devices during each sampling, Max command length is 14 bytes. The grammar is:
357 357  
359 +(% border="1" class="table-bordered" %)
358 358  |(((
359 359  **AT+COMMANDx=xx xx xx xx xx xx xx xx xx xx xx xx,m**
360 360  
... ... @@ -367,9 +367,9 @@
367 367  
368 368  In the RS485-BL, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
369 369  
370 -
371 371  **AT+SEARCHx**: This command defines how to handle the return from AT+COMMANDx.
372 372  
374 +(% border="1" class="table-bordered" %)
373 373  |(((
374 374  **AT+SEARCHx=aa,xx xx xx xx xx**
375 375  
... ... @@ -387,7 +387,7 @@
387 387  
388 388  The valid data will be all bytes after 1E 56 34 , so it is 2e 30 58 5f 36 41 30 31 00 49
389 389  
390 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image013.png]]
392 +[[image:1652954654347-831.png]]
391 391  
392 392  
393 393  1. For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
1652954654347-831.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +138.7 KB
Content
1653266934636-343.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +176.5 KB
Content
1653267211009-519.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +138.7 KB
Content
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

Applications

Navigation

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