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