Last modified by Xiaoling on 2025/04/23 15:56
<
From version < 22.1 >
edited by Xiaoling
on 2022/05/23 09:10
To version < 42.3 >
edited by Xiaoling
on 2022/06/02 16:47
>
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,25 +137,35 @@
137 137  
138 138  [[image:1653268155545-638.png||height="334" width="724"]]
139 139  
149 +
140 140  (((
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.
151 +(((
152 +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:
142 142  )))
143 143  
144 144  (((
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:
156 +485A+ and 485B- of the sensor are connected to RS485A and RA485B of RS485-LN respectively.
146 146  )))
147 147  
159 +[[image:1653268227651-549.png||height="592" width="720"]]
160 +
148 148  (((
149 -**Step 1**: Create a device in TTN V3 with the OTAA keys from RS485-BL.
162 +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:
150 150  )))
151 151  
152 152  (((
153 -Each RS485-BL is shipped with a sticker with unique device EUI:
166 +**Step 1**: Create a device in TTN V3 with the OTAA keys from RS485-LN.
154 154  )))
155 155  
169 +(((
170 +Each RS485-LN is shipped with a sticker with unique device EUI:
171 +)))
172 +)))
173 +
156 156  [[image:1652953462722-299.png]]
157 157  
158 158  (((
177 +(((
159 159  User can enter this key in their LoRaWAN Server portal. Below is TTN V3 screen shot:
160 160  )))
161 161  
... ... @@ -162,13 +162,11 @@
162 162  (((
163 163  Add APP EUI in the application.
164 164  )))
184 +)))
165 165  
166 -
167 -
168 -
169 169  [[image:image-20220519174512-1.png]]
170 170  
171 -[[image:image-20220519174512-2.png||height="328" width="731"]]
188 +[[image:image-20220519174512-2.png||height="323" width="720"]]
172 172  
173 173  [[image:image-20220519174512-3.png||height="556" width="724"]]
174 174  
... ... @@ -184,44 +184,43 @@
184 184  
185 185  
186 186  (((
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.
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.
188 188  )))
189 189  
190 190  [[image:1652953568895-172.png||height="232" width="724"]]
191 191  
209 +
192 192  == 3.3 Configure Commands to read data ==
193 193  
194 194  (((
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.
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.
196 196  )))
197 197  
198 -=== 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
199 199  
200 -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 +)))
201 201  
202 -**~1. RS485-MODBUS mode:**
224 +=== 3.3.1 onfigure UART settings for RS485 or TTL communication ===
203 203  
204 -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:
205 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 -
212 -(% border="1" style="background-color:#ffffcc; color:green; width:795px" %)
213 -|(((
228 +(% border="1" style="background-color:#ffffcc; color:green; width:782px" %)
229 +|(% style="width:128px" %)(((
214 214  **AT Commands**
215 -)))|(% style="width:285px" %)(((
231 +)))|(% style="width:305px" %)(((
216 216  **Description**
217 -)))|(% style="width:347px" %)(((
233 +)))|(% style="width:346px" %)(((
218 218  **Example**
219 219  )))
220 -|(((
236 +|(% style="width:128px" %)(((
221 221  AT+BAUDR
222 -)))|(% style="width:285px" %)(((
238 +)))|(% style="width:305px" %)(((
223 223  Set the baud rate (for RS485 connection). Default Value is: 9600.
224 -)))|(% style="width:347px" %)(((
240 +)))|(% style="width:346px" %)(((
225 225  (((
226 226  AT+BAUDR=9600
227 227  )))
... ... @@ -230,18 +230,12 @@
230 230  Options: (1200,2400,4800,14400,19200,115200)
231 231  )))
232 232  )))
233 -|(((
249 +|(% style="width:128px" %)(((
234 234  AT+PARITY
235 -)))|(% style="width:285px" %)(((
236 -(((
251 +)))|(% style="width:305px" %)(((
237 237  Set UART parity (for RS485 connection)
238 -)))
239 -
253 +)))|(% style="width:346px" %)(((
240 240  (((
241 -Default Value is: no parity.
242 -)))
243 -)))|(% style="width:347px" %)(((
244 -(((
245 245  AT+PARITY=0
246 246  )))
247 247  
... ... @@ -249,17 +249,17 @@
249 249  Option: 0: no parity, 1: odd parity, 2: even parity
250 250  )))
251 251  )))
252 -|(((
262 +|(% style="width:128px" %)(((
253 253  AT+STOPBIT
254 -)))|(% style="width:285px" %)(((
264 +)))|(% style="width:305px" %)(((
255 255  (((
256 256  Set serial stopbit (for RS485 connection)
257 257  )))
258 258  
259 259  (((
260 -Default Value is: 1bit.
270 +
261 261  )))
262 -)))|(% style="width:347px" %)(((
272 +)))|(% style="width:346px" %)(((
263 263  (((
264 264  AT+STOPBIT=0 for 1bit
265 265  )))
... ... @@ -276,12 +276,10 @@
276 276  === 3.3.2 Configure sensors ===
277 277  
278 278  (((
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 -
282 282  (((
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.
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.
284 284  )))
292 +)))
285 285  
286 286  (% border="1" style="background-color:#ffffcc; color:green; width:806px" %)
287 287  |**AT Commands**|(% style="width:418px" %)**Description**|(% style="width:256px" %)**Example**
... ... @@ -293,82 +293,37 @@
293 293  mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
294 294  )))|(% style="width:256px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
295 295  
296 -Detail of AT+CFGDEV command see [[AT+CFGDEV detail>>path:#AT_CFGDEV]].
297 -
298 298  === 3.3.3 Configure read commands for each sampling ===
299 299  
300 300  (((
301 -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.
302 -)))
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.
303 303  
304 -(((
305 -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.
306 -)))
307 -
308 -(((
309 309  To save the LoRaWAN network bandwidth, we might need to read data from different sensors and combine their valid value into a short payload.
310 -)))
311 311  
312 -(((
313 313  This section describes how to achieve above goals.
314 -)))
315 315  
316 -(((
317 -During each sampling, the RS485-BL can support 15 commands to read sensors. And combine the return to one or several uplink payloads.
318 -)))
313 +During each sampling, the RS485-LN can support 15 commands to read sensors. And combine the return to one or several uplink payloads.
319 319  
320 -(((
321 -**Command from RS485-BL to Sensor:**
322 -)))
323 323  
324 -(((
325 -RS485-BL can send out pre-set max 15 strings via **AT+COMMAD1**, **ATCOMMAND2**,…, to **AT+COMMANDF** . All commands are of same grammar.
326 -)))
316 +**Each RS485 commands include two parts:**
327 327  
328 -(((
329 -**Handle return from sensors to RS485-BL**:
330 -)))
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.
331 331  
332 -(((
333 -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**
334 -)))
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.
335 335  
336 -* (((
337 -**AT+DATACUT**
338 -)))
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
339 339  
340 -(((
341 -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.
342 -)))
343 343  
344 -* (((
345 -**AT+SEARCH**
346 -)))
347 -
348 -(((
349 -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.
350 -)))
351 -
352 -(((
353 -**Define wait timeout:**
354 -)))
355 -
356 -(((
357 -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
358 -)))
359 -
360 -(((
361 361  After we got the valid value from each RS485 commands, we need to combine them together with the command **AT+DATAUP**.
362 -)))
363 363  
364 -**Examples:**
365 365  
366 366  Below are examples for the how above AT Commands works.
367 367  
368 -**AT+COMMANDx : **This command will be sent to RS485/TTL devices during each sampling, Max command length is 14 bytes. The grammar is:
369 369  
370 -(% border="1" class="table-bordered" %)
371 -|(((
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" %)(((
372 372  **AT+COMMANDx=xx xx xx xx xx xx xx xx xx xx xx xx,m**
373 373  
374 374  **xx xx xx xx xx xx xx xx xx xx xx xx: The RS485 command to be sent**
... ... @@ -378,43 +378,13 @@
378 378  
379 379  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.
380 380  
381 -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.
382 382  
383 -**AT+SEARCHx**: This command defines how to handle the return from AT+COMMANDx.
384 384  
385 -(% border="1" class="table-bordered" %)
386 -|(((
387 -**AT+SEARCHx=aa,xx xx xx xx xx**
388 -
389 -* **aa: 1: prefix match mode; 2: prefix and suffix match mode**
390 -* **xx xx xx xx xx: match string. Max 5 bytes for prefix and 5 bytes for suffix**
391 -
392 -
393 -)))
394 -
395 -Examples:
396 -
397 -1. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
398 -
399 -If we set AT+SEARCH1=1,1E 56 34.      (max 5 bytes for prefix)
400 -
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
402 -
403 -[[image:1652954654347-831.png]]
404 -
405 -
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 -
408 -If we set AT+SEARCH1=2, 1E 56 34+31 00 49
409 -
410 -Device will search the bytes between 1E 56 34 and 31 00 49. So it is 2e 30 58 5f 36 41 30
411 -
412 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image014.png]]
413 -
414 -
415 415  **AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes.
416 416  
417 -|(((
349 +(% border="1" style="background-color:#4bacc6; color:white; width:725px" %)
350 +|(% style="width:722px" %)(((
418 418  **AT+DATACUTx=a,b,c**
419 419  
420 420  * **a: length for the return of AT+COMMAND**
... ... @@ -422,242 +422,183 @@
422 422  * **c: define the position for valid value.  **
423 423  )))
424 424  
425 -Examples:
358 +**Examples:**
426 426  
427 427  * Grab bytes:
428 428  
429 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image015.png]]
362 +[[image:image-20220602153621-1.png]]
430 430  
364 +
431 431  * Grab a section.
432 432  
433 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image016.png]]
367 +[[image:image-20220602153621-2.png]]
434 434  
369 +
435 435  * Grab different sections.
436 436  
437 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image017.png]]
372 +[[image:image-20220602153621-3.png]]
438 438  
374 +
375 +)))
439 439  
440 -Note:
377 +=== 3.3.4 Compose the uplink payload ===
441 441  
442 -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.
443 -
444 -Example:
445 -
446 -AT+COMMAND1=11 01 1E D0,0
447 -
448 -AT+SEARCH1=1,1E 56 34
449 -
450 -AT+DATACUT1=0,2,1~~5
451 -
452 -Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
453 -
454 -String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
455 -
456 -Valid payload after DataCUT command: 2e 30 58 5f 36
457 -
458 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image018.png]]
459 -
460 -
461 -
462 -
463 -1.
464 -11.
465 -111. Compose the uplink payload
466 -
379 +(((
467 467  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.**
468 468  
382 +
383 +)))
469 469  
470 -**Examples: AT+DATAUP=0**
385 +(((
386 +(% style="color:#037691" %)**Examples: AT+DATAUP=0**
471 471  
472 -Compose the uplink payload with value returns in sequence and send with **A SIGNLE UPLINK**.
388 +
389 +)))
473 473  
391 +(((
392 +Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**A SIGNLE UPLINK**.
393 +)))
394 +
395 +(((
474 474  Final Payload is
397 +)))
475 475  
476 -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 +)))
477 477  
403 +(((
478 478  Where PAYVER is defined by AT+PAYVER, below is an example screen shot.
405 +)))
479 479  
480 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.png]]
407 +[[image:1653269759169-150.png||height="513" width="716"]]
481 481  
482 482  
410 +(% style="color:#037691" %)**Examples: AT+DATAUP=1**
483 483  
484 -**Examples: AT+DATAUP=1**
485 485  
486 -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**.
487 487  
488 488  Final Payload is
489 489  
490 -Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA
417 +(% style="color:#4f81bd" %)**Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA**
491 491  
492 -1. Battery Info (2 bytes): Battery voltage
493 -1. PAYVER (1 byte): Defined by AT+PAYVER
494 -1. PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling.
495 -1. PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
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
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
497 497  
498 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image020.png]]
424 +[[image:image-20220602155039-4.png]]
499 499  
500 500  
501 -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
502 502  
503 -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**
504 504  
505 -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**
506 506  
507 -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**
508 508  
509 509  
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:
510 510  
511 -Below are the uplink payloads:
438 + ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink.
512 512  
513 -[[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.
514 514  
442 + * For US915 band, max 11 bytes for each uplink.
515 515  
516 -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.
517 517  
518 - ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink ( so 51 -5 = 46 max valid date)
519 519  
520 - * 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:
521 521  
522 - * For US915 band, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date).
449 +[[image:1654157178836-407.png]]
523 523  
524 - ~* For all other bands: max 51 bytes for each uplink  ( so 51 -5 = 46 max valid date).
525 525  
452 +=== 3.3.5 Uplink on demand ===
526 526  
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.
527 527  
528 -1.
529 -11.
530 -111. Uplink on demand
531 -
532 -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.
533 -
534 534  Downlink control command:
535 535  
536 -[[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.
537 537  
538 -[[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.
539 539  
540 540  
541 541  
542 -1.
543 -11.
544 -111. Uplink on Interrupt
464 +=== 3.3.6 Uplink on Interrupt ===
545 545  
546 -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.
547 547  
548 -AT+INTMOD=0  Disable Interrupt
468 +[[image:1654157342174-798.png]]
549 549  
550 -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.
551 551  
552 -AT+INTMOD=2  Interrupt trigger by falling edge. ( Default Value)
553 553  
554 -AT+INTMOD=3  Interrupt trigger by rising edge.
473 +== 3.4 Uplink Payload ==
555 555  
556 -
557 -1.
558 -11. Uplink Payload
559 -
560 -|**Size(bytes)**|**2**|**1**|**Length depends on the return from the commands**
561 -|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" %)(((
562 562  Battery(mV)
563 563  
564 564  &
565 565  
566 566  Interrupt _Flag
567 -)))|(((
483 +)))|(% style="width:116px" %)(((
568 568  PAYLOAD_VER
569 569  
570 570  
571 -)))|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.
572 572  
573 573  Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors.
574 574  
575 575  
576 -function Decoder(bytes, port) {
492 +== 3.5 Configure RS485-BL via AT or Downlink ==
577 577  
578 -~/~/Payload Formats of RS485-BL Deceive
494 +User can configure RS485-LN via AT Commands or LoRaWAN Downlink Commands
579 579  
580 -return {
581 -
582 - ~/~/Battery,units:V
583 -
584 - BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000,
585 -
586 - ~/~/GPIO_EXTI 
587 -
588 - EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE",
589 -
590 - ~/~/payload of version
591 -
592 - Pay_ver:bytes[2],
593 -
594 - };
595 -
596 - }
597 -
598 -
599 -
600 -
601 -
602 -
603 -
604 -TTN V3 uplink screen shot.
605 -
606 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]
607 -
608 -1.
609 -11. Configure RS485-BL via AT or Downlink
610 -
611 -User can configure RS485-BL via [[AT Commands >>path:#_​Using_the_AT]]or LoRaWAN Downlink Commands
612 -
613 613  There are two kinds of Commands:
614 614  
615 -* **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
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]]
616 616  
617 -* **Sensor Related Commands**: These commands are special designed for RS485-BL.  User can see these commands below:
500 +* (% style="color:#4f81bd" %)**Sensor Related Commands**(%%): These commands are special designed for RS485-LN.  User can see these commands below:
618 618  
619 -1.
620 -11.
621 -111. Common Commands:
502 +=== 3.5.1 Common Commands ===
622 622  
623 -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]]
504 +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]]
624 624  
625 625  
626 -1.
627 -11.
628 -111. Sensor related commands:
507 +=== 3.5.2 Sensor related commands ===
629 629  
630 -==== Choose Device Type (RS485 or TTL) ====
509 +Response feature is added to the server's downlink, a special package with a FPort of 200 will be uploaded immediately after receiving the data sent by the server.
631 631  
632 -RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect.
511 +[[image:image-20220602163333-5.png||height="263" width="1160"]]
633 633  
634 -* AT Command
513 +The first byte of this package represents whether the configuration is successful, 00 represents failure, 01 represents success. Except for the first byte, the other is the previous downlink. (All commands except A8 type commands are applicable)
635 635  
636 -**AT+MOD=1** ~/~/ Set to support RS485-MODBUS type sensors. User can connect multiply RS485 , Modbus sensors to the A / B pins.
637 637  
638 -**AT+MOD=2** ~/~/ Set to support TTL Level sensors, User can connect one TTL Sensor to the TXD/RXD/GND pins.
516 +=== 3.5.3 Sensor related commands ===
639 639  
518 +==== ====
640 640  
641 -* Downlink Payload
520 +==== **RS485 Debug Command** ====
642 642  
643 -**0A aa**     à same as AT+MOD=aa
522 +This command is used to configure the RS485 devices; they won’t be used during sampling.
644 644  
524 +* **AT Command**
645 645  
526 +(% class="box infomessage" %)
527 +(((
528 +**AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m**
529 +)))
646 646  
647 -==== [[RS485 Debug Command>>path:#downlink_A8]] (AT+CFGDEV) ====
531 +m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
648 648  
649 -This command is used to configure the RS485 or TTL sensors; they won’t be used during sampling.
533 +* **Downlink Payload**
650 650  
651 -* AT Command
652 -
653 -AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
654 -
655 -m: 0: no CRC; 1: add CRC-16/MODBUS in the end of this command.
656 -
657 -
658 -
659 -* Downlink Payload
660 -
661 661  Format: A8 MM NN XX XX XX XX YY
662 662  
663 663  Where:
... ... @@ -665,9 +665,12 @@
665 665  * MM: 1: add CRC-16/MODBUS ; 0: no CRC
666 666  * NN: The length of RS485 command
667 667  * XX XX XX XX: RS485 command total NN bytes
668 -* YY: How many bytes will be uplink from the return of this RS485 command, if YY=0, RS485-BL will execute the downlink command without uplink; if YY>0, RS485-BL will uplink total YY bytes from the output of this RS485 command
542 +* YY: How many bytes will be uplink from the return of this RS485 command,
543 +** if YY=0, RS485-LN will execute the downlink command without uplink;
544 +** if YY>0, RS485-LN will uplink total YY bytes from the output of this RS485 command; Fport=200
545 +** if YY=FF, RS485-LN will uplink RS485 output with the downlink command content; Fport=200.
669 669  
670 -**Example 1:**
547 +**Example 1** ~-~-> Configure without ask for uplink (YY=0)
671 671  
672 672  To connect a Modbus Alarm with below commands.
673 673  
... ... @@ -677,59 +677,76 @@
677 677  
678 678  So if user want to use downlink command to control to RS485 Alarm, he can use:
679 679  
680 -**A8 01 06 0A 05 00 04 00 01 00**: to activate the RS485 Alarm
557 +(% style="color:#4f81bd" %)**A8 01 06 0A 05 00 04 00 01 00**(%%): to activate the RS485 Alarm
681 681  
682 -**A8 01 06 0A 05 00 04 00 00 00**: to deactivate the RS485 Alarm
559 +(% style="color:#4f81bd" %)**A8 01 06 0A 05 00 04 00 00 00**(%%): to deactivate the RS485 Alarm
683 683  
684 684  A8 is type code and 01 means add CRC-16/MODBUS at the end, the 3^^rd^^ byte is 06, means the next 6 bytes are the command to be sent to the RS485 network, the final byte 00 means this command don’t need to acquire output.
685 685  
686 686  
687 -**Example 2:**
564 +**Example 2** ~-~-> Configure with requesting uplink and original downlink command (**YY=FF**)
688 688  
689 -Check TTL Sensor return:
566 +User in IoT server send a downlink command: (% style="color:#4f81bd" %)**A8 01 06 0A 08 00 04 00 01 YY**
690 690  
691 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image024.png]]
692 692  
569 +RS485-LN got this downlink command and send (% style="color:#4f81bd" %)**0A 08 00 04 00 01 **(%%)to Modbus network. One of the RS485 sensor in the network send back Modbus reply **0A 08 00 04 00 00**. RS485-LN get this reply and combine with the original downlink command and uplink. The uplink message is:
693 693  
571 + **A8** (% style="color:#4f81bd" %)**0A 08 00 04 00  **(% style="color:red" %)**01 06** ** **(% style="color:green" %)**0A 08 00 04 00 00**
694 694  
573 + [[image:1654159460680-153.png]]
695 695  
696 -==== Set Payload version ====
697 697  
576 +
577 +==== **Set Payload version** ====
578 +
698 698  This is the first byte of the uplink payload. RS485-BL can connect to different sensors. User can set the PAYVER field to tell server how to decode the current payload.
699 699  
700 -* AT Command:
581 +* **AT Command:**
701 701  
702 -AT+PAYVER: Set PAYVER field = 1
583 +(% class="box infomessage" %)
584 +(((
585 +**AT+PAYVER: Set PAYVER field = 1**
586 +)))
703 703  
704 704  
705 -* Downlink Payload:
589 +* **Downlink Payload:**
706 706  
707 -0xAE 01   à Set PAYVER field =  0x01
591 +**0xAE 01**  ~-~-> Set PAYVER field =  0x01
708 708  
709 -0xAE 0F   à Set PAYVER field =  0x0F
593 +**0xAE 0F**   ~-~-> Set PAYVER field =  0x0F
710 710  
711 711  
712 -==== Set RS485 Sampling Commands ====
713 713  
597 +==== **Set RS485 Sampling Commands** ====
598 +
714 714  AT+COMMANDx, AT+DATACUTx and AT+SEARCHx
715 715  
716 -These three commands are used to configure how the RS485-BL polling data from Modbus device. Detail of usage please see : [[polling RS485 device>>path:#polling_485]].
601 +These three commands are used to configure how the RS485-BL polling data from Modbus device. Detail of usage please see : [[polling RS485 device>>||anchor="H3.3.3Configurereadcommandsforeachsampling"]].
717 717  
718 718  
719 -* AT Command:
604 +* **AT Command:**
720 720  
721 -AT+COMMANDx: Configure RS485 read command to sensor.
606 +(% class="box infomessage" %)
607 +(((
608 +**AT+COMMANDx: Configure RS485 read command to sensor.**
609 +)))
722 722  
723 -AT+DATACUTx: Configure how to handle return from RS485 devices.
611 +(% class="box infomessage" %)
612 +(((
613 +**AT+DATACUTx: Configure how to handle return from RS485 devices.**
614 +)))
724 724  
725 -AT+SEARCHx: Configure search command
616 +(% class="box infomessage" %)
617 +(((
618 +**AT+SEARCHx: Configure search command**
619 +)))
726 726  
727 727  
728 -* Downlink Payload:
622 +* **Downlink Payload:**
729 729  
730 -0xAF downlink command can be used to set AT+COMMANDx or AT+DATACUTx.
624 +**0xAF** downlink command can be used to set AT+COMMANDx or AT+DATACUTx.
731 731  
732 -Note: if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink.
626 +(% style="color:red" %)**Note**(%%): if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink.
733 733  
734 734  Format: AF MM NN LL XX XX XX XX YY
735 735  
... ... @@ -736,23 +736,23 @@
736 736  Where:
737 737  
738 738  * MM: the ATCOMMAND or AT+DATACUT to be set. Value from 01 ~~ 0F,
739 -* NN: 0: no CRC; 1: add CRC-16/MODBUS ; 2: set the AT+DATACUT value.
740 -* LL: The length of AT+COMMAND or AT+DATACUT command
633 +* NN:  0: no CRC; 1: add CRC-16/MODBUS ; 2: set the AT+DATACUT value.
634 +* LL:  The length of AT+COMMAND or AT+DATACUT command
741 741  * XX XX XX XX: AT+COMMAND or AT+DATACUT command
742 -* YY: If YY=0, RS485-BL will execute the downlink command without uplink; if YY=1, RS485-BL will execute an uplink after got this command.
636 +* YY:  If YY=0, RS485-BL will execute the downlink command without uplink; if YY=1, RS485-BL will execute an uplink after got this command.
743 743  
744 -Example:
638 +**Example:**
745 745  
746 -**AF 03 01 06 0A 05 00 04 00 01 00**: Same as AT+COMMAND3=0A 05 00 04 00 01,1
640 +(% style="color:#037691" %)**AF 03 01 06 0A 05 00 04 00 01 00**(%%): Same as AT+COMMAND3=0A 05 00 04 00 01,1
747 747  
748 -**AF 03 02 06 10 01 05 06 09 0A 00**: Same as AT+DATACUT3=**16**,**1**,**5+6+9+10**
642 +(% style="color:#037691" %)**AF 03 02 06**(% style="color:orange" %)** 10 **(% style="color:red" %)**01 **(% style="color:green" %)**05 06 09 0A**(% style="color:#037691" %)** 00**(%%): Same as AT+DATACUT3=(% style="color:orange" %)**16**(%%),(% style="color:red" %)**1**(%%),(% style="color:green" %)**5+6+9+10**
749 749  
750 -**AF 03 02 06 0B 02 05 07 08 0A 00**: Same as AT+DATACUT3=**11**,**2**,**5~~7+8~~10**
644 +(% style="color:#037691" %)**AF 03 02 06 **(% style="color:orange" %)**0B**(% style="color:red" %)** 02 **(% style="color:green" %)**05 07 08 0A **(% style="color:#037691" %)**00**(%%): Same as AT+DATACUT3=(% style="color:orange" %)**11**(%%),(% style="color:red" %)**2**(%%),(% style="color:green" %)**5~~7+8~~10**
751 751  
752 752  
753 -0xAB downlink command can be used for set AT+SEARCHx
647 +**0xAB** downlink command can be used for set AT+SEARCHx
754 754  
755 -Example: **AB aa 01 03 xx xx xx** (03 here means there are total 3 bytes after 03) So
649 +**Example:** **AB aa 01 03 xx xx xx** (03 here means there are total 3 bytes after 03) So
756 756  
757 757  * AB aa 01 03 xx xx xx  same as AT+SEARCHaa=1,xx xx xx
758 758  * AB aa 02 03 xx xx xx 02 yy yy(03 means there are 3 bytes after 03, they are xx xx xx;02 means there are 2 bytes after 02, they are yy yy) so the commands
... ... @@ -760,145 +760,164 @@
760 760  **AB aa 02 03 xx xx xx 02 yy yy**  same as **AT+SEARCHaa=2,xx xx xx+yy yy**
761 761  
762 762  
763 -==== Fast command to handle MODBUS device ====
764 764  
658 +==== **Fast command to handle MODBUS device** ====
659 +
765 765  AT+MBFUN is valid since v1.3 firmware version. The command is for fast configure to read Modbus devices. It is only valid for the devices which follow the [[MODBUS-RTU protocol>>url:https://www.modbustools.com/modbus.html]].
766 766  
767 767  This command is valid since v1.3 firmware version
768 768  
769 769  
770 -AT+MBFUN has only two value:
665 +**AT+MBFUN has only two value:**
771 771  
772 -* AT+MBFUN=1: Enable Modbus reading. And get response base on the MODBUS return
667 +* **AT+MBFUN=1**: Enable Modbus reading. And get response base on the MODBUS return
773 773  
774 774  AT+MBFUN=1, device can auto read the Modbus function code: 01, 02, 03 or 04. AT+MBFUN has lower priority vs AT+DATACUT command. If AT+DATACUT command is configured, AT+MBFUN will be ignore.
775 775  
776 -* AT+MBFUN=0: Disable Modbus fast reading.
671 +* **AT+MBFUN=0**: Disable Modbus fast reading.
777 777  
778 -Example:
673 +**Example:**
779 779  
780 780  * AT+MBFUN=1 and AT+DATACUT1/AT+DATACUT2 are not configure (0,0,0).
781 781  * AT+COMMAND1= 01 03 00 10 00 08,1 ~-~-> read slave address 01 , function code 03, start address 00 01, quantity of registers 00 08.
782 782  * AT+COMMAND2= 01 02 00 40 00 10,1 ~-~-> read slave address 01 , function code 02, start address 00 40, quantity of inputs 00 10.
783 783  
784 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image025.png]]
679 +[[image:1654133913295-597.png]]
785 785  
786 786  
787 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image026.png]]
682 +[[image:1654133954153-643.png]]
788 788  
789 789  
790 -* Downlink Commands:
685 +* **Downlink Commands:**
791 791  
792 -A9 aa -à Same as AT+MBFUN=aa
687 +**A9 aa** ~-~-> Same as AT+MBFUN=aa
793 793  
794 794  
795 -==== RS485 command timeout ====
796 796  
691 +==== **RS485 command timeout** ====
692 +
797 797  Some Modbus device has slow action to send replies. This command is used to configure the RS485-BL to use longer time to wait for their action.
798 798  
799 799  Default value: 0, range:  0 ~~ 5 seconds
800 800  
801 801  
802 -* AT Command:
698 +* **AT Command:**
803 803  
804 -AT+CMDDLaa=hex(bb cc)
700 +(% class="box infomessage" %)
701 +(((
702 +**AT+CMDDLaa=hex(bb cc)**
703 +)))
805 805  
806 -Example:
705 +**Example:**
807 807  
808 808  **AT+CMDDL1=1000** to send the open time to 1000ms
809 809  
810 810  
811 -* Downlink Payload:
710 +* **Downlink Payload:**
812 812  
813 813  0x AA aa bb cc
814 814  
815 815  Same as: AT+CMDDLaa=hex(bb cc)
816 816  
817 - Example:
716 + **Example:**
818 818  
819 - 0xAA 01 03 E8  à Same as **AT+CMDDL1=1000 ms**
718 + **0xAA 01 03 E8**  ~-~-> Same as **AT+CMDDL1=1000 ms**
820 820  
821 821  
822 -==== [[Uplink>>path:#downlink_A8]] payload mode ====
823 823  
722 +==== **Uplink payload mode** ====
723 +
824 824  Define to use one uplink or multiple uplinks for the sampling.
825 825  
826 -The use of this command please see: [[Compose Uplink payload>>path:#DataUP]]
726 +The use of this command please see: [[Compose Uplink payload>>||anchor="H3.3.4Composetheuplinkpayload"]]
827 827  
828 -* AT Command:
728 +* **AT Command:**
829 829  
830 -AT+DATAUP=0
730 +(% class="box infomessage" %)
731 +(((
732 +**AT+DATAUP=0**
733 +)))
831 831  
832 -AT+DATAUP=1
735 +(% class="box infomessage" %)
736 +(((
737 +**AT+DATAUP=1**
738 +)))
833 833  
834 834  
835 -* Downlink Payload:
741 +* **Downlink Payload:**
836 836  
837 -0xAD 00   à Same as AT+DATAUP=0
743 +**0xAD 00**  **~-~->** Same as AT+DATAUP=0
838 838  
839 -0xAD 01   à Same as AT+DATAUP=1
745 +**0xAD 01**  **~-~->** Same as AT+DATAUP=1
840 840  
841 841  
842 -==== Manually trigger an Uplink ====
843 843  
749 +==== **Manually trigger an Uplink** ====
750 +
844 844  Ask device to send an uplink immediately.
845 845  
846 -* Downlink Payload:
753 +* **Downlink Payload:**
847 847  
848 -0x08 FF, RS485-BL will immediately send an uplink.
755 +**0x08 FF**, RS485-BL will immediately send an uplink.
849 849  
850 850  
851 -==== Clear RS485 Command ====
852 852  
759 +==== **Clear RS485 Command** ====
760 +
853 853  The AT+COMMANDx and AT+DATACUTx settings are stored in special location, user can use below command to clear them.
854 854  
855 855  
856 -* AT Command:
764 +* **AT Command:**
857 857  
858 -**AT+CMDEAR=mm,nn**   mm: start position of erase ,nn: stop position of erase
766 +(% style="color:#037691" %)**AT+CMDEAR=mm,nn** (%%) mm: start position of erase ,nn: stop position of erase Etc. AT+CMDEAR=1,10 means erase AT+COMMAND1/AT+DATACUT1 to AT+COMMAND10/AT+DATACUT10
859 859  
860 -Etc. AT+CMDEAR=1,10 means erase AT+COMMAND1/AT+DATACUT1 to AT+COMMAND10/AT+DATACUT10
861 -
862 862  Example screen shot after clear all RS485 commands. 
863 863  
864 864  
865 -
866 866  The uplink screen shot is:
867 867  
868 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]
773 +[[image:1654134704555-320.png]]
869 869  
870 870  
871 -* Downlink Payload:
776 +* **Downlink Payload:**
872 872  
873 -0x09 aa bb same as AT+CMDEAR=aa,bb
778 +**0x09 aa bb** same as AT+CMDEAR=aa,bb
874 874  
875 875  
876 -==== Set Serial Communication Parameters ====
877 877  
782 +==== **Set Serial Communication Parameters** ====
783 +
878 878  Set the Rs485 serial communication parameters:
879 879  
880 -* AT Command:
786 +* **AT Command:**
881 881  
882 882  Set Baud Rate:
883 883  
884 -AT+BAUDR=9600    ~/~/ Options: (1200,2400,4800,14400,19200,115200)
790 +(% class="box infomessage" %)
791 +(((
792 +**AT+BAUDR=9600**    ~/~/ Options: (1200,2400,4800,14400,19200,115200)
793 +)))
885 885  
795 +Set UART Parity
886 886  
887 -Set UART parity
797 +(% class="box infomessage" %)
798 +(((
799 +**AT+PARITY=0**    ~/~/ Option: 0: no parity, 1: odd parity, 2: even parity
800 +)))
888 888  
889 -AT+PARITY=0    ~/~/ Option: 0: no parity, 1: odd parity, 2: even parity
890 -
891 -
892 892  Set STOPBIT
893 893  
894 -AT+STOPBIT=0    ~/~/ Option: 0 for 1bit; 1 for 1.5 bit ; 2 for 2 bits
804 +(% class="box infomessage" %)
805 +(((
806 +**AT+STOPBIT=0**    ~/~/ Option: 0 for 1bit; 1 for 1.5 bit ; 2 for 2 bits
807 +)))
895 895  
896 896  
897 -* Downlink Payload:
810 +* **Downlink Payload:**
898 898  
899 -A7 01 aa bb: Same  AT+BAUDR=hex(aa bb)*100
812 +**A7 01 aa bb**: Same  AT+BAUDR=hex(aa bb)*100
900 900  
901 -Example:
814 +**Example:**
902 902  
903 903  * A7 01 00 60   same as AT+BAUDR=9600
904 904  * A7 01 04 80  same as AT+BAUDR=115200
... ... @@ -908,287 +908,22 @@
908 908  A7 03 aa: Same as  AT+STOPBIT=aa  (aa value: 00 , 01 or 02)
909 909  
910 910  
911 -==== Control output power duration ====
912 912  
825 +==== **Control output power duration** ====
826 +
913 913  User can set the output power duration before each sampling.
914 914  
915 -* AT Command:
829 +* **AT Command:**
916 916  
917 -Example:
831 +**Example:**
918 918  
919 -AT+3V3T=1000 ~/~/ 3V3 output power will open 1s before each sampling.
833 +**AT+3V3T=1000**  ~/~/ 3V3 output power will open 1s before each sampling.
920 920  
921 -AT+5VT=1000 ~/~/ +5V output power will open 1s before each sampling.
835 +**AT+5VT=1000**  ~/~/ +5V output power will open 1s before each sampling.
922 922  
923 923  
924 -* LoRaWAN Downlink Command:
838 +* **LoRaWAN Downlink Command:**
925 925  
926 -07 01 aa bb  Same as AT+5VT=(aa bb)
840 +**07 01 aa bb**  Same as AT+5VT=(aa bb)
927 927  
928 -07 02 aa bb  Same as AT+3V3T=(aa bb)
929 -
930 -
931 -
932 -
933 -1.
934 -11. Buttons
935 -
936 -|**Button**|**Feature**
937 -|**RST**|Reboot RS485-BL
938 -
939 -1.
940 -11. +3V3 Output
941 -
942 -RS485-BL has a Controllable +3V3 output, user can use this output to power external sensor.
943 -
944 -The +3V3 output will be valid for every sampling. RS485-BL will enable +3V3 output before all sampling and disable the +3V3 after all sampling. 
945 -
946 -
947 -The +3V3 output time can be controlled by AT Command.
948 -
949 -**AT+3V3T=1000**
950 -
951 -Means set +3v3 valid time to have 1000ms. So, the real +3v3 output will actually have 1000ms + sampling time for other sensors.
952 -
953 -
954 -By default, the AT+3V3T=0. This is a special case, means the +3V3 output is always on at any time
955 -
956 -
957 -1.
958 -11. +5V Output
959 -
960 -RS485-BL has a Controllable +5V output, user can use this output to power external sensor.
961 -
962 -The +5V output will be valid for every sampling. RS485-BL will enable +5V output before all sampling and disable the +5v after all sampling. 
963 -
964 -
965 -The 5V output time can be controlled by AT Command.
966 -
967 -**AT+5VT=1000**
968 -
969 -Means set 5V valid time to have 1000ms. So, the real 5V output will actually have 1000ms + sampling time for other sensors.
970 -
971 -
972 -By default, the AT+5VT=0. If the external sensor which require 5v and require more time to get stable state, user can use this command to increase the power ON duration for this sensor.
973 -
974 -
975 -
976 -
977 -1.
978 -11. LEDs
979 -
980 -|**LEDs**|**Feature**
981 -|**LED1**|Blink when device transmit a packet.
982 -
983 -1.
984 -11. Switch Jumper
985 -
986 -|**Switch Jumper**|**Feature**
987 -|**SW1**|(((
988 -ISP position: Upgrade firmware via UART
989 -
990 -Flash position: Configure device, check running status.
991 -)))
992 -|**SW2**|(((
993 -5V position: set to compatible with 5v I/O.
994 -
995 -3.3v position: set to compatible with 3.3v I/O.,
996 -)))
997 -
998 -+3.3V: is always ON
999 -
1000 -+5V: Only open before every sampling. The time is by default, it is AT+5VT=0.  Max open time. 5000 ms.
1001 -
1002 -1. Case Study
1003 -
1004 -User can check this URL for some case studies.
1005 -
1006 -[[http:~~/~~/wiki.dragino.com/index.php?title=APP_RS485_COMMUNICATE_WITH_SENSORS>>url:http://wiki.dragino.com/index.php?title=APP_RS485_COMMUNICATE_WITH_SENSORS]]
1007 -
1008 -
1009 -
1010 -
1011 -1. Use AT Command
1012 -11. Access AT Command
1013 -
1014 -RS485-BL supports AT Command set. User can use a USB to TTL adapter plus the 3.5mm Program Cable to connect to RS485-BL to use AT command, as below.
1015 -
1016 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image027.png]]
1017 -
1018 -
1019 -In PC, User needs to set **serial tool**(such as [[putty>>url:https://www.chiark.greenend.org.uk/~~sgtatham/putty/latest.html]], SecureCRT) baud rate to **9600** to access to access serial console of RS485-BL. The default password is 123456. Below is the output for reference:
1020 -
1021 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image028.png]]
1022 -
1023 -
1024 -
1025 -More detail AT Command manual can be found at [[AT Command Manual>>path:#AT_COMMAND]]
1026 -
1027 -
1028 -
1029 -1.
1030 -11. Common AT Command Sequence
1031 -111. Multi-channel ABP mode (Use with SX1301/LG308)
1032 -
1033 -If device has not joined network yet:
1034 -
1035 -AT+FDR
1036 -
1037 -AT+NJM=0
1038 -
1039 -ATZ
1040 -
1041 -
1042 -If device already joined network:
1043 -
1044 -AT+NJM=0
1045 -
1046 -ATZ
1047 -
1048 -1.
1049 -11.
1050 -111. Single-channel ABP mode (Use with LG01/LG02)
1051 -
1052 -AT+FDR   Reset Parameters to Factory Default, Keys Reserve
1053 -
1054 -AT+NJM=0 Set to ABP mode
1055 -
1056 -AT+ADR=0 Set the Adaptive Data Rate Off
1057 -
1058 -AT+DR=5  Set Data Rate
1059 -
1060 -AT+TDC=60000  Set transmit interval to 60 seconds
1061 -
1062 -AT+CHS=868400000 Set transmit frequency to 868.4Mhz
1063 -
1064 -AT+RX2FQ=868400000 Set RX2Frequency to 868.4Mhz (according to the result from server)
1065 -
1066 -AT+RX2DR=5  Set RX2DR to match the downlink DR from server. see below
1067 -
1068 -AT+DADDR=26 01 1A F1 Set Device Address to 26 01 1A F1, this ID can be found in the LoRa Server portal.
1069 -
1070 -ATZ          Reset MCU
1071 -
1072 -**Note:**
1073 -
1074 -1. Make sure the device is set to ABP mode in the IoT Server.
1075 -1. Make sure the LG01/02 gateway RX frequency is exactly the same as AT+CHS setting.
1076 -1. Make sure SF / bandwidth setting in LG01/LG02 match the settings of AT+DR. refer [[this link>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/&file=LoRaWAN%201.0.3%20Regional%20Parameters.xlsx]] to see what DR means.
1077 -1. The command AT+RX2FQ and AT+RX2DR is to let downlink work. to set the correct parameters, user can check the actually downlink parameters to be used. As below. Which shows the RX2FQ should use 868400000 and RX2DR should be 5
1078 -
1079 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image029.png]]
1080 -
1081 -
1082 -1. FAQ
1083 -11. How to upgrade the image?
1084 -
1085 -The RS485-BL LoRaWAN Controller is shipped with a 3.5mm cable, the cable is used to upload image to RS485-BL to:
1086 -
1087 -* Support new features
1088 -* For bug fix
1089 -* Change LoRaWAN bands.
1090 -
1091 -Below shows the hardware connection for how to upload an image to RS485-BL:
1092 -
1093 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image030.png]]
1094 -
1095 -**Step1:** Download [[flash loader>>url:https://www.st.com/content/st_com/en/products/development-tools/software-development-tools/stm32-software-development-tools/stm32-programmers/flasher-stm32.html]].
1096 -
1097 -**Step2**: Download the [[LT Image files>>url:http://www.dragino.com/downloads/index.php?dir=LT_LoRa_IO_Controller/LT33222-L/image/]].
1098 -
1099 -**Step3: **Open flashloader; choose the correct COM port to update.
1100 -
1101 -
1102 -|(((
1103 -HOLD PRO then press the RST button, SYS will be ON, then click next
1104 -)))
1105 -
1106 -|(((
1107 -Board detected
1108 -)))
1109 -
1110 -|(((
1111 -
1112 -)))
1113 -
1114 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image031.png]] [[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image032.png]]
1115 -
1116 -
1117 -
1118 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image033.png]] [[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image034.png]]
1119 -
1120 -
1121 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image035.png]] [[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image036.png]]
1122 -
1123 -
1124 -1.
1125 -11. How to change the LoRa Frequency Bands/Region?
1126 -
1127 -User can follow the introduction for [[how to upgrade image>>path:#upgrade_image]]. When download the images, choose the required image file for download.
1128 -
1129 -
1130 -
1131 -1.
1132 -11. How many RS485-Slave can RS485-BL connects?
1133 -
1134 -The RS485-BL can support max 32 RS485 devices. Each uplink command of RS485-BL can support max 16 different RS485 command. So RS485-BL can support max 16 RS485 devices pre-program in the device for uplink. For other devices no pre-program, user can use the [[downlink message (type code 0xA8) to poll their info>>path:#downlink_A8]].
1135 -
1136 -
1137 -
1138 -
1139 -1. Trouble Shooting     
1140 -11. Downlink doesn’t work, how to solve it?
1141 -
1142 -Please see this link for debug:
1143 -
1144 -[[http:~~/~~/wiki.dragino.com/index.php?title=Main_Page#LoRaWAN_Communication_Debug>>url:http://wiki.dragino.com/index.php?title=Main_Page#LoRaWAN_Communication_Debug]] 
1145 -
1146 -
1147 -
1148 -1.
1149 -11. Why I can’t join TTN V3 in US915 /AU915 bands?
1150 -
1151 -It might about the channels mapping. Please see for detail.
1152 -
1153 -[[http:~~/~~/wiki.dragino.com/index.php?title=LoRaWAN_Communication_Debug#Notice_of_US915.2FCN470.2FAU915_Frequency_band>>url:http://wiki.dragino.com/index.php?title=LoRaWAN_Communication_Debug#Notice_of_US915.2FCN470.2FAU915_Frequency_band]]
1154 -
1155 -
1156 -
1157 -1. Order Info
1158 -
1159 -**Part Number: RS485-BL-XXX**
1160 -
1161 -**XXX:**
1162 -
1163 -* **EU433**: frequency bands EU433
1164 -* **EU868**: frequency bands EU868
1165 -* **KR920**: frequency bands KR920
1166 -* **CN470**: frequency bands CN470
1167 -* **AS923**: frequency bands AS923
1168 -* **AU915**: frequency bands AU915
1169 -* **US915**: frequency bands US915
1170 -* **IN865**: frequency bands IN865
1171 -* **RU864**: frequency bands RU864
1172 -* **KZ865: **frequency bands KZ865
1173 -
1174 -1. Packing Info
1175 -
1176 -**Package Includes**:
1177 -
1178 -* RS485-BL x 1
1179 -* Stick Antenna for LoRa RF part x 1
1180 -* Program cable x 1
1181 -
1182 -**Dimension and weight**:
1183 -
1184 -* Device Size: 13.5 x 7 x 3 cm
1185 -* Device Weight: 105g
1186 -* Package Size / pcs : 14.5 x 8 x 5 cm
1187 -* Weight / pcs : 170g
1188 -
1189 -1. Support
1190 -
1191 -* Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule.
1192 -* Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to
1193 -
1194 -[[support@dragino.com>>url:file:///D:/市场资料/说明书/LoRa/LT系列/support@dragino.com]]
842 +**07 02 aa bb**  Same as AT+3V3T=(aa bb)
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
1654158783574-851.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +40.6 KB
Content
1654159460680-153.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +24.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
image-20220602163333-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +48.2 KB
Content

Applications

Navigation

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