Skip to Content
Last modified by Mengting Qiu on 2025/07/14 09:59
From version 18.2
edited by Xiaoling
on 2022/05/23 08:49
Change comment: There is no comment for this version
To version 41.2
edited by Xiaoling
on 2022/06/02 16:36
Change comment: There is no comment for this version

Summary

Details

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