Last modified by Xiaoling on 2025/04/23 15:56
<
From version < 22.2 >
edited by Xiaoling
on 2022/05/23 09:11
To version < 38.4 >
edited by Xiaoling
on 2022/06/02 16:30
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -18,40 +18,42 @@
18 18  
19 19  (((
20 20  (((
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.
21 +The Dragino RS485-LN is a (% style="color:blue" %)**RS485 to LoRaWAN Converter**(%%). It converts the RS485 signal into LoRaWAN wireless signal which simplify the IoT installation and reduce the installation/maintaining cost.
22 22  )))
23 23  
24 24  (((
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.
25 +RS485-LN allows user to (% style="color:blue" %)**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.
26 26  )))
27 27  
28 28  (((
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.
29 +(% style="color:blue" %)**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.
30 30  )))
31 31  
32 32  (((
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.
33 +(% style="color:blue" %)**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.
34 +
35 +(% style="color:blue" %)**Demo Dashboard for RS485-LN**(%%) connect to two energy meters: [[https:~~/~~/app.datacake.de/dashboard/d/58844a26-378d-4c5a-aaf5-b5b5b153447a>>url:https://app.datacake.de/dashboard/d/58844a26-378d-4c5a-aaf5-b5b5b153447a]]
34 34  )))
35 35  )))
36 36  
37 37  [[image:1653267211009-519.png||height="419" width="724"]]
38 38  
41 +
39 39  == 1.2 Specifications ==
40 40  
44 +
41 41  **Hardware System:**
42 42  
43 43  * STM32L072CZT6 MCU
44 -* SX1276/78 Wireless Chip
48 +* SX1276/78 Wireless Chip 
45 45  * Power Consumption (exclude RS485 device):
46 46  ** Idle: 32mA@12v
47 -
48 -*
49 49  ** 20dB Transmit: 65mA@12v
50 50  
51 51  **Interface for Model:**
52 52  
53 53  * RS485
54 -* Power Input 7~~ 24V DC.
56 +* Power Input 7~~ 24V DC. 
55 55  
56 56  **LoRa Spec:**
57 57  
... ... @@ -98,6 +98,7 @@
98 98  
99 99  [[RS485-LN Image files – Download link and Change log>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/]]
100 100  
103 +
101 101  == 1.6 Hardware Change log ==
102 102  
103 103  (((
... ... @@ -105,6 +105,8 @@
105 105  v1.2: Add External Interrupt Pin.
106 106  
107 107  v1.0: Release
111 +
112 +
108 108  )))
109 109  )))
110 110  
... ... @@ -121,6 +121,8 @@
121 121  )))
122 122  
123 123  [[image:1653268091319-405.png]]
129 +
130 +
124 124  )))
125 125  
126 126  = 3. Operation Mode =
... ... @@ -129,6 +129,8 @@
129 129  
130 130  (((
131 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.
139 +
140 +
132 132  )))
133 133  
134 134  == 3.2 Example to join LoRaWAN network ==
... ... @@ -137,10 +137,15 @@
137 137  
138 138  [[image:1653268155545-638.png||height="334" width="724"]]
139 139  
149 +
140 140  (((
151 +(((
141 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:
153 +)))
142 142  
155 +(((
143 143  485A+ and 485B- of the sensor are connected to RS485A and RA485B of RS485-LN respectively.
157 +)))
144 144  
145 145  [[image:1653268227651-549.png||height="592" width="720"]]
146 146  
... ... @@ -160,6 +160,7 @@
160 160  [[image:1652953462722-299.png]]
161 161  
162 162  (((
177 +(((
163 163  User can enter this key in their LoRaWAN Server portal. Below is TTN V3 screen shot:
164 164  )))
165 165  
... ... @@ -166,13 +166,11 @@
166 166  (((
167 167  Add APP EUI in the application.
168 168  )))
184 +)))
169 169  
170 -
171 -
172 -
173 173  [[image:image-20220519174512-1.png]]
174 174  
175 -[[image:image-20220519174512-2.png||height="328" width="731"]]
188 +[[image:image-20220519174512-2.png||height="323" width="720"]]
176 176  
177 177  [[image:image-20220519174512-3.png||height="556" width="724"]]
178 178  
... ... @@ -188,44 +188,43 @@
188 188  
189 189  
190 190  (((
191 -**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.
204 +**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.
192 192  )))
193 193  
194 194  [[image:1652953568895-172.png||height="232" width="724"]]
195 195  
209 +
196 196  == 3.3 Configure Commands to read data ==
197 197  
198 198  (((
199 -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.
213 +(((
214 +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 200  )))
201 201  
202 -=== 3.3.1 onfigure UART settings for RS485 or TTL communication ===
217 +(((
218 +(% 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
203 203  
204 -RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect.
220 +
221 +)))
222 +)))
205 205  
206 -**~1. RS485-MODBUS mode:**
224 +=== 3.3.1 onfigure UART settings for RS485 or TTL communication ===
207 207  
208 -AT+MOD=1 ~/~/ Support RS485-MODBUS type sensors. User can connect multiply RS485 , Modbus sensors to the A / B pins.
226 +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:
209 209  
210 -**2. TTL mode:**
211 -
212 -AT+MOD=2 ~/~/ Support TTL Level sensors, User can connect one TTL Sensor to the TXD/RXD/GND pins.
213 -
214 -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.
215 -
216 -(% border="1" style="background-color:#ffffcc; color:green; width:795px" %)
217 -|(((
228 +(% border="1" style="background-color:#ffffcc; color:green; width:782px" %)
229 +|(% style="width:128px" %)(((
218 218  **AT Commands**
219 -)))|(% style="width:285px" %)(((
231 +)))|(% style="width:305px" %)(((
220 220  **Description**
221 -)))|(% style="width:347px" %)(((
233 +)))|(% style="width:346px" %)(((
222 222  **Example**
223 223  )))
224 -|(((
236 +|(% style="width:128px" %)(((
225 225  AT+BAUDR
226 -)))|(% style="width:285px" %)(((
238 +)))|(% style="width:305px" %)(((
227 227  Set the baud rate (for RS485 connection). Default Value is: 9600.
228 -)))|(% style="width:347px" %)(((
240 +)))|(% style="width:346px" %)(((
229 229  (((
230 230  AT+BAUDR=9600
231 231  )))
... ... @@ -234,18 +234,12 @@
234 234  Options: (1200,2400,4800,14400,19200,115200)
235 235  )))
236 236  )))
237 -|(((
249 +|(% style="width:128px" %)(((
238 238  AT+PARITY
239 -)))|(% style="width:285px" %)(((
240 -(((
251 +)))|(% style="width:305px" %)(((
241 241  Set UART parity (for RS485 connection)
242 -)))
243 -
253 +)))|(% style="width:346px" %)(((
244 244  (((
245 -Default Value is: no parity.
246 -)))
247 -)))|(% style="width:347px" %)(((
248 -(((
249 249  AT+PARITY=0
250 250  )))
251 251  
... ... @@ -253,17 +253,17 @@
253 253  Option: 0: no parity, 1: odd parity, 2: even parity
254 254  )))
255 255  )))
256 -|(((
262 +|(% style="width:128px" %)(((
257 257  AT+STOPBIT
258 -)))|(% style="width:285px" %)(((
264 +)))|(% style="width:305px" %)(((
259 259  (((
260 260  Set serial stopbit (for RS485 connection)
261 261  )))
262 262  
263 263  (((
264 -Default Value is: 1bit.
270 +
265 265  )))
266 -)))|(% style="width:347px" %)(((
272 +)))|(% style="width:346px" %)(((
267 267  (((
268 268  AT+STOPBIT=0 for 1bit
269 269  )))
... ... @@ -280,12 +280,10 @@
280 280  === 3.3.2 Configure sensors ===
281 281  
282 282  (((
283 -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**.
284 -)))
285 -
286 286  (((
287 -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.
290 +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.
288 288  )))
292 +)))
289 289  
290 290  (% border="1" style="background-color:#ffffcc; color:green; width:806px" %)
291 291  |**AT Commands**|(% style="width:418px" %)**Description**|(% style="width:256px" %)**Example**
... ... @@ -297,82 +297,37 @@
297 297  mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
298 298  )))|(% style="width:256px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
299 299  
300 -Detail of AT+CFGDEV command see [[AT+CFGDEV detail>>path:#AT_CFGDEV]].
301 -
302 302  === 3.3.3 Configure read commands for each sampling ===
303 303  
304 304  (((
305 -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.
306 -)))
307 +During each sampling, we need confirm what commands we need to send to the RS485 sensors to read data. After the RS485 sensors send back the value, it normally include some bytes and we only need a few from them for a shorten payload.
307 307  
308 -(((
309 -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.
310 -)))
311 -
312 -(((
313 313  To save the LoRaWAN network bandwidth, we might need to read data from different sensors and combine their valid value into a short payload.
314 -)))
315 315  
316 -(((
317 317  This section describes how to achieve above goals.
318 -)))
319 319  
320 -(((
321 -During each sampling, the RS485-BL can support 15 commands to read sensors. And combine the return to one or several uplink payloads.
322 -)))
313 +During each sampling, the RS485-LN can support 15 commands to read sensors. And combine the return to one or several uplink payloads.
323 323  
324 -(((
325 -**Command from RS485-BL to Sensor:**
326 -)))
327 327  
328 -(((
329 -RS485-BL can send out pre-set max 15 strings via **AT+COMMAD1**, **ATCOMMAND2**,…, to **AT+COMMANDF** . All commands are of same grammar.
330 -)))
316 +**Each RS485 commands include two parts:**
331 331  
332 -(((
333 -**Handle return from sensors to RS485-BL**:
334 -)))
318 +~1. What commands RS485-LN will send to the RS485 sensors. There are total 15 commands from **AT+COMMAD1**, **ATCOMMAND2**,…, to **AT+COMMANDF**. All commands are of same grammar.
335 335  
336 -(((
337 -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**
338 -)))
320 +2. How to get wanted value the from RS485 sensors returns from by 1). There are total 15 AT Commands to handle the return, commands are **AT+DATACUT1**,**AT+DATACUT2**,…, **AT+DATACUTF** corresponding to the commands from 1). All commands are of same grammar.
339 339  
340 -* (((
341 -**AT+DATACUT**
342 -)))
322 +3. 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
343 343  
344 -(((
345 -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.
346 -)))
347 347  
348 -* (((
349 -**AT+SEARCH**
350 -)))
351 -
352 -(((
353 -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.
354 -)))
355 -
356 -(((
357 -**Define wait timeout:**
358 -)))
359 -
360 -(((
361 -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
362 -)))
363 -
364 -(((
365 365  After we got the valid value from each RS485 commands, we need to combine them together with the command **AT+DATAUP**.
366 -)))
367 367  
368 -**Examples:**
369 369  
370 370  Below are examples for the how above AT Commands works.
371 371  
372 -**AT+COMMANDx : **This command will be sent to RS485/TTL devices during each sampling, Max command length is 14 bytes. The grammar is:
373 373  
374 -(% border="1" class="table-bordered" %)
375 -|(((
331 +**AT+COMMANDx : **This command will be sent to RS485 devices during each sampling, Max command length is 14 bytes. The grammar is:
332 +
333 +(% border="1" style="background-color:#4bacc6; color:white; width:499px" %)
334 +|(% style="width:496px" %)(((
376 376  **AT+COMMANDx=xx xx xx xx xx xx xx xx xx xx xx xx,m**
377 377  
378 378  **xx xx xx xx xx xx xx xx xx xx xx xx: The RS485 command to be sent**
... ... @@ -382,43 +382,13 @@
382 382  
383 383  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.
384 384  
385 -In the RS485-BL, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
344 +In the RS485-LN, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
386 386  
387 -**AT+SEARCHx**: This command defines how to handle the return from AT+COMMANDx.
388 388  
389 -(% border="1" class="table-bordered" %)
390 -|(((
391 -**AT+SEARCHx=aa,xx xx xx xx xx**
392 -
393 -* **aa: 1: prefix match mode; 2: prefix and suffix match mode**
394 -* **xx xx xx xx xx: match string. Max 5 bytes for prefix and 5 bytes for suffix**
395 -
396 -
397 -)))
398 -
399 -Examples:
400 -
401 -1. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
402 -
403 -If we set AT+SEARCH1=1,1E 56 34.      (max 5 bytes for prefix)
404 -
405 -The valid data will be all bytes after 1E 56 34 , so it is 2e 30 58 5f 36 41 30 31 00 49
406 -
407 -[[image:1652954654347-831.png]]
408 -
409 -
410 -1. For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
411 -
412 -If we set AT+SEARCH1=2, 1E 56 34+31 00 49
413 -
414 -Device will search the bytes between 1E 56 34 and 31 00 49. So it is 2e 30 58 5f 36 41 30
415 -
416 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image014.png]]
417 -
418 -
419 419  **AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes.
420 420  
421 -|(((
349 +(% border="1" style="background-color:#4bacc6; color:white; width:725px" %)
350 +|(% style="width:722px" %)(((
422 422  **AT+DATACUTx=a,b,c**
423 423  
424 424  * **a: length for the return of AT+COMMAND**
... ... @@ -426,211 +426,159 @@
426 426  * **c: define the position for valid value.  **
427 427  )))
428 428  
429 -Examples:
358 +**Examples:**
430 430  
431 431  * Grab bytes:
432 432  
433 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image015.png]]
362 +[[image:image-20220602153621-1.png]]
434 434  
364 +
435 435  * Grab a section.
436 436  
437 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image016.png]]
367 +[[image:image-20220602153621-2.png]]
438 438  
369 +
439 439  * Grab different sections.
440 440  
441 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image017.png]]
372 +[[image:image-20220602153621-3.png]]
442 442  
374 +
375 +)))
443 443  
444 -Note:
377 +=== 3.3.4 Compose the uplink payload ===
445 445  
446 -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.
447 -
448 -Example:
449 -
450 -AT+COMMAND1=11 01 1E D0,0
451 -
452 -AT+SEARCH1=1,1E 56 34
453 -
454 -AT+DATACUT1=0,2,1~~5
455 -
456 -Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
457 -
458 -String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
459 -
460 -Valid payload after DataCUT command: 2e 30 58 5f 36
461 -
462 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image018.png]]
463 -
464 -
465 -
466 -
467 -1.
468 -11.
469 -111. Compose the uplink payload
470 -
379 +(((
471 471  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.**
472 472  
382 +
383 +)))
473 473  
474 -**Examples: AT+DATAUP=0**
385 +(((
386 +(% style="color:#037691" %)**Examples: AT+DATAUP=0**
475 475  
476 -Compose the uplink payload with value returns in sequence and send with **A SIGNLE UPLINK**.
388 +
389 +)))
477 477  
391 +(((
392 +Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**A SIGNLE UPLINK**.
393 +)))
394 +
395 +(((
478 478  Final Payload is
397 +)))
479 479  
480 -Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx
399 +(((
400 +(% style="color:#4f81bd" %)**Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx**
401 +)))
481 481  
403 +(((
482 482  Where PAYVER is defined by AT+PAYVER, below is an example screen shot.
405 +)))
483 483  
484 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.png]]
407 +[[image:1653269759169-150.png||height="513" width="716"]]
485 485  
486 486  
410 +(% style="color:#037691" %)**Examples: AT+DATAUP=1**
487 487  
488 -**Examples: AT+DATAUP=1**
489 489  
490 -Compose the uplink payload with value returns in sequence and send with **Multiply UPLINKs**.
413 +Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**Multiply UPLINKs**.
491 491  
492 492  Final Payload is
493 493  
494 -Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA
417 +(% style="color:#4f81bd" %)**Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA**
495 495  
496 -1. Battery Info (2 bytes): Battery voltage
497 -1. PAYVER (1 byte): Defined by AT+PAYVER
498 -1. PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling.
499 -1. PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
500 -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
419 +1. PAYVER: Defined by AT+PAYVER
420 +1. PAYLOAD COUNT: Total how many uplinks of this sampling.
421 +1. PAYLOAD#: Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
422 +1. DATA: Valid value: max 8 bytes for each uplink so each uplink <= 11 bytes. For the last uplink, DATA will might less than 8 bytes
501 501  
502 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image020.png]]
424 +[[image:image-20220602155039-4.png]]
503 503  
504 504  
505 -So totally there will be 3 uplinks for this sampling, each uplink includes 6 bytes DATA
427 +So totally there will be 3 uplinks for this sampling, each uplink include 8 bytes DATA
506 506  
507 -DATA1=RETURN1 Valid Value = 20 20 0a 33 90 41
429 +DATA1=RETURN1 Valid Value + the first two of Valid value of RETURN10= **20 20 0a 33 90 41 02 aa**
508 508  
509 -DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= 02 aa 05 81 0a 20
431 +DATA2=3^^rd^^ ~~ 10^^th^^ byte of Valid value of RETURN10= **05 81 0a 20 20 20 20 2d**
510 510  
511 -DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 = 20 20 20 2d 30
433 +DATA3=the rest of Valid value of RETURN10= **30**
512 512  
513 513  
436 +(% style="color:red" %)Notice: In firmware v1.3, the Max bytes has been changed according to the max bytes in different Frequency Bands for lowest SF. As below:
514 514  
515 -Below are the uplink payloads:
438 + ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink.
516 516  
517 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.png]]
440 + * For AU915/AS923 bands, if UplinkDwell time=0, max 11 bytes for each uplink.
518 518  
442 + * For US915 band, max 11 bytes for each uplink.
519 519  
520 -Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:
444 + ~* For all other bands: max 51 bytes for each uplink.
521 521  
522 - ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink ( so 51 -5 = 46 max valid date)
523 523  
524 - * For AU915/AS923 bands, if UplinkDwell time=1, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date).
447 +Below are the uplink payloads:
525 525  
526 - * For US915 band, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date).
449 +[[image:1654157178836-407.png]]
527 527  
528 - ~* For all other bands: max 51 bytes for each uplink  ( so 51 -5 = 46 max valid date).
529 529  
452 +=== 3.3.5 Uplink on demand ===
530 530  
454 +Except uplink periodically, RS485-LN is able to uplink on demand. The server send downlink command to RS485-LN and RS485 will uplink data base on the command.
531 531  
532 -1.
533 -11.
534 -111. Uplink on demand
535 -
536 -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.
537 -
538 538  Downlink control command:
539 539  
540 -[[0x08 command>>path:#downlink_08]]: Poll an uplink with current command set in RS485-BL.
458 +**0x08 command**: Poll an uplink with current command set in RS485-LN.
541 541  
542 -[[0xA8 command>>path:#downlink_A8]]: Send a command to RS485-BL and uplink the output from sensors.
460 +**0xA8 command**: Send a command to RS485-LN and uplink the output from sensors.
543 543  
544 544  
545 545  
546 -1.
547 -11.
548 -111. Uplink on Interrupt
464 +=== 3.3.6 Uplink on Interrupt ===
549 549  
550 -Put the interrupt sensor between 3.3v_out and GPIO ext.[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image022.png]]
466 +RS485-LN support external Interrupt uplink since hardware v1.2 release.
551 551  
552 -AT+INTMOD=0  Disable Interrupt
468 +[[image:1654157342174-798.png]]
553 553  
554 -AT+INTMOD=1  Interrupt trigger by rising or falling edge.
470 +Connect the Interrupt pin to RS485-LN INT port and connect the GND pin to V- port. When there is a high voltage (Max 24v) on INT pin. Device will send an uplink packet.
555 555  
556 -AT+INTMOD=2  Interrupt trigger by falling edge. ( Default Value)
557 557  
558 -AT+INTMOD=3  Interrupt trigger by rising edge.
473 +== 3.4 Uplink Payload ==
559 559  
560 -
561 -1.
562 -11. Uplink Payload
563 -
564 -|**Size(bytes)**|**2**|**1**|**Length depends on the return from the commands**
565 -|Value|(((
475 +(% border="1" style="background-color:#4bacc6; color:white; width:734px" %)
476 +|**Size(bytes)**|(% style="width:120px" %)**2**|(% style="width:116px" %)**1**|(% style="width:386px" %)**Length depends on the return from the commands**
477 +|Value|(% style="width:120px" %)(((
566 566  Battery(mV)
567 567  
568 568  &
569 569  
570 570  Interrupt _Flag
571 -)))|(((
483 +)))|(% style="width:116px" %)(((
572 572  PAYLOAD_VER
573 573  
574 574  
575 -)))|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.
487 +)))|(% style="width:386px" %)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.
576 576  
577 577  Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors.
578 578  
579 579  
580 -function Decoder(bytes, port) {
492 +== 3.5 Configure RS485-BL via AT or Downlink ==
581 581  
582 -~/~/Payload Formats of RS485-BL Deceive
494 +User can configure RS485-LN via AT Commands or LoRaWAN Downlink Commands
583 583  
584 -return {
496 +There are two kinds of Commands:
585 585  
586 - ~/~/Battery,units:V
498 +* (% style="color:#4f81bd" %)**Common Commands**(%%): They should be available for each sensor, such as: change uplink interval, reset device. For firmware v1.3, user can find what common commands it supports: [[End Device AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]
587 587  
588 - BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000,
500 +* (% style="color:#4f81bd" %)**Sensor Related Commands**(%%): These commands are special designed for RS485-LN.  User can see these commands below:
589 589  
590 - ~/~/GPIO_EXTI 
591 591  
592 - EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE",
593 593  
594 - ~/~/payload of version
504 +=== 3.5.1 Common Commands ===
595 595  
596 - Pay_ver:bytes[2],
506 +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: [[End Device AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]
597 597  
598 - };
599 599  
600 - }
509 +=== 3.5.2 Sensor related commands: ===
601 601  
602 -
603 -
604 -
605 -
606 -
607 -
608 -TTN V3 uplink screen shot.
609 -
610 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]
611 -
612 -1.
613 -11. Configure RS485-BL via AT or Downlink
614 -
615 -User can configure RS485-BL via [[AT Commands >>path:#_​Using_the_AT]]or LoRaWAN Downlink Commands
616 -
617 -There are two kinds of Commands:
618 -
619 -* **Common Commands**: They should be available for each sensor, 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
620 -
621 -* **Sensor Related Commands**: These commands are special designed for RS485-BL.  User can see these commands below:
622 -
623 -1.
624 -11.
625 -111. Common Commands:
626 -
627 -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]]
628 -
629 -
630 -1.
631 -11.
632 -111. Sensor related commands:
633 -
634 634  ==== Choose Device Type (RS485 or TTL) ====
635 635  
636 636  RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect.
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
1653270130359-810.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +197.8 KB
Content
1654157178836-407.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +179.9 KB
Content
1654157342174-798.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +31.9 KB
Content
image-20220602153621-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +23.4 KB
Content
image-20220602153621-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +22.2 KB
Content
image-20220602153621-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +22.3 KB
Content
image-20220602155039-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +24.6 KB
Content

Applications

Navigation

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