Skip to Content
Last modified by Xiaoling on 2025/04/23 15:56
From version 32.4
edited by Xiaoling
on 2022/06/02 15:24
Change comment: There is no comment for this version
To version 6.1
edited by Xiaoling
on 2022/05/19 17:41
Change comment: Uploaded new attachment "1652953304999-717.png", version {1}

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -RS485-LN – RS485 to LoRaWAN Converter
1 +RS485-BL – Waterproof RS485 to LoRaWAN Converter
Content
... ... @@ -1,11 +1,13 @@
1 1  (% style="text-align:center" %)
2 -[[image:1653266934636-343.png||height="385" width="385"]]
2 +[[image:1652947681187-144.png||height="385" width="385"]]
3 3  
4 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image001.jpg]]
4 4  
5 5  
6 -**RS485-LN – RS485 to LoRaWAN Converter User Manual**
7 7  
8 +**RS485-BL – Waterproof RS485 to LoRaWAN Converter User Manual**
8 8  
10 +
9 9  **Table of Contents:**
10 10  
11 11  
... ... @@ -14,30 +14,41 @@
14 14  
15 15  = 1.Introduction =
16 16  
17 -== 1.1 What is RS485-LN RS485 to LoRaWAN Converter ==
19 +== 1.1 What is RS485-BL RS485 to LoRaWAN Converter ==
18 18  
19 19  (((
22 +
23 +)))
24 +
20 20  (((
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.
26 +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.
22 22  )))
23 23  
24 24  (((
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.
30 +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.
26 26  )))
27 27  
28 28  (((
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.
34 +RS485-BL is IP67 **waterproof** and powered by **8500mAh Li-SOCI2 battery**, it is designed for long term use for several years.
30 30  )))
31 31  
32 32  (((
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 +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.
39 +)))
34 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]]
41 +(((
42 +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.
36 36  )))
44 +
45 +(((
46 +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.
37 37  )))
38 38  
39 -[[image:1653267211009-519.png||height="419" width="724"]]
49 +(((
50 +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.
51 +)))
40 40  
53 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image002.png]]
41 41  
42 42  == 1.2 Specifications ==
43 43  
... ... @@ -44,17 +44,21 @@
44 44  **Hardware System:**
45 45  
46 46  * STM32L072CZT6 MCU
47 -* SX1276/78 Wireless Chip 
60 +* SX1276/78 Wireless Chip
48 48  * Power Consumption (exclude RS485 device):
49 -** Idle: 32mA@12v
62 +** Idle: 6uA@3.3v
50 50  
51 51  *
52 -** 20dB Transmit: 65mA@12v
65 +** 20dB Transmit: 130mA@3.3v
53 53  
54 54  **Interface for Model:**
55 55  
56 -* RS485
57 -* Power Input 7~~ 24V DC. 
69 +* 1 x RS485 Interface
70 +* 1 x TTL Serial , 3.3v or 5v.
71 +* 1 x I2C Interface, 3.3v or 5v.
72 +* 1 x one wire interface
73 +* 1 x Interrupt Interface
74 +* 1 x Controllable 5V output, max
58 58  
59 59  **LoRa Spec:**
60 60  
... ... @@ -63,30 +63,27 @@
63 63  ** Band 2 (LF): 410 ~~ 528 Mhz
64 64  * 168 dB maximum link budget.
65 65  * +20 dBm - 100 mW constant RF output vs.
66 -* +14 dBm high efficiency PA.
67 67  * Programmable bit rate up to 300 kbps.
68 68  * High sensitivity: down to -148 dBm.
69 69  * Bullet-proof front end: IIP3 = -12.5 dBm.
70 70  * Excellent blocking immunity.
71 -* Low RX current of 10.3 mA, 200 nA register retention.
72 72  * Fully integrated synthesizer with a resolution of 61 Hz.
73 -* FSK, GFSK, MSK, GMSK, LoRaTM and OOK modulation.
88 +* LoRa modulation.
74 74  * Built-in bit synchronizer for clock recovery.
75 75  * Preamble detection.
76 76  * 127 dB Dynamic Range RSSI.
77 -* Automatic RF Sense and CAD with ultra-fast AFC.
78 -* Packet engine up to 256 bytes with CRC.
92 +* Automatic RF Sense and CAD with ultra-fast AFC. ​​​
79 79  
80 80  == 1.3 Features ==
81 81  
82 -* LoRaWAN Class A & Class C protocol (default Class C)
96 +* LoRaWAN Class A & Class C protocol (default Class A)
83 83  * Frequency Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/IN865/RU864
84 84  * AT Commands to change parameters
85 -* Remote configure parameters via LoRa Downlink
99 +* Remote configure parameters via LoRaWAN Downlink
86 86  * Firmware upgradable via program port
87 87  * Support multiply RS485 devices by flexible rules
88 88  * Support Modbus protocol
89 -* Support Interrupt uplink (Since hardware version v1.2)
103 +* Support Interrupt uplink
90 90  
91 91  == 1.4 Applications ==
92 92  
... ... @@ -97,269 +97,262 @@
97 97  * Smart Cities
98 98  * Smart Factory
99 99  
100 -== 1.5 Firmware Change log ==
114 +== 1.5 Firmware Change log ==
101 101  
102 -[[RS485-LN Image files – Download link and Change log>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/]]
116 +[[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);"]]
103 103  
104 104  == 1.6 Hardware Change log ==
105 105  
106 106  (((
107 -(((
108 -v1.2: Add External Interrupt Pin.
109 -
110 -v1.0: Release
121 +v1.4
111 111  )))
112 -)))
113 113  
114 -= 2. Power ON Device =
115 -
116 116  (((
117 -The RS485-LN can be powered by 7 ~~ 24V DC power source. Connection as below
125 +~1. Change Power IC to TPS22916
126 +)))
118 118  
119 -* Power Source VIN to RS485-LN VIN+
120 -* Power Source GND to RS485-LN VIN-
121 121  
122 122  (((
123 -Once there is power, the RS485-LN will be on.
130 +v1.3
124 124  )))
125 125  
126 -[[image:1653268091319-405.png]]
133 +(((
134 +~1. Change JP3 from KF350-8P to KF350-11P, Add one extra interface for I2C and one extra interface for one-wire
127 127  )))
128 128  
129 -= 3. Operation Mode =
130 130  
131 -== 3.1 How it works? ==
138 +(((
139 +v1.2
140 +)))
132 132  
133 133  (((
134 -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.
143 +Release version ​​​​​
135 135  )))
136 136  
137 -== 3.2 Example to join LoRaWAN network ==
146 += 2. Pin mapping and Power ON Device =
138 138  
139 -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. 
148 +The RS485-BL is powered on by 8500mAh battery. To save battery life, RS485-BL is shipped with power off. User can put the jumper to power on RS485-BL.
140 140  
141 -[[image:1653268155545-638.png||height="334" width="724"]]
150 +[[image:1652953055962-143.png||height="387" width="728"]]
142 142  
143 -(((
144 -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:
152 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image003.png]]
145 145  
146 -485A+ and 485B- of the sensor are connected to RS485A and RA485B of RS485-LN respectively.
154 +The Left TXD and RXD are TTL interface for external sensor. TTL level is controlled by 3.3/5v Jumper.
147 147  
148 -[[image:1653268227651-549.png||height="592" width="720"]]
149 149  
150 -(((
151 -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:
152 -)))
153 153  
154 -(((
155 -**Step 1**: Create a device in TTN V3 with the OTAA keys from RS485-LN.
156 -)))
158 +3. Operation Mode
159 +3.1 How it works?
157 157  
158 -(((
159 -Each RS485-LN is shipped with a sticker with unique device EUI:
160 -)))
161 -)))
161 +The RS485-BL is configured as LoRaWAN OTAA Class A mode by default. It has OTAA keys to join network. To connect a local LoRaWAN network, user just need to input the OTAA keys in the network server and power on the RS485-BL. It will auto join the network via OTAA.
162 162  
163 -[[image:1652953462722-299.png]]
164 164  
165 -(((
166 -(((
164 +1.
165 +11. Example to join LoRaWAN network
166 +
167 +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.
168 +
169 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image004.png]]
170 +
171 +
172 +The RS485-BL in this example connected to two RS485 devices for demonstration, user can connect to other RS485 devices via the same method.
173 +
174 +
175 +The LG308 is already set to connect to [[TTN V3 network >>url:https://www.thethingsnetwork.org/]]. So what we need to now is only configure the TTN V3:
176 +
177 +**Step 1**: Create a device in TTN V3 with the OTAA keys from RS485-BL.
178 +
179 +Each RS485-BL is shipped with a sticker with unique device EUI:
180 +
181 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image005.png]]
182 +
183 +
184 +
185 +
167 167  User can enter this key in their LoRaWAN Server portal. Below is TTN V3 screen shot:
168 -)))
169 169  
170 -(((
171 171  Add APP EUI in the application.
172 -)))
173 -)))
174 174  
175 -[[image:image-20220519174512-1.png]]
190 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image006.png]]
176 176  
177 -[[image:image-20220519174512-2.png||height="323" width="720"]]
192 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image007.png]]
178 178  
179 -[[image:image-20220519174512-3.png||height="556" width="724"]]
194 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image008.png]]
180 180  
181 -[[image:image-20220519174512-4.png]]
196 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image009.png]]
182 182  
183 -You can also choose to create the device manually.
184 184  
185 -[[image:1652953542269-423.png||height="710" width="723"]]
186 186  
187 -Add APP KEY and DEV EUI
188 188  
189 -[[image:1652953553383-907.png||height="514" width="724"]]
190 190  
191 191  
192 -(((
193 -**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.
194 -)))
195 195  
196 -[[image:1652953568895-172.png||height="232" width="724"]]
197 197  
198 -== 3.3 Configure Commands to read data ==
199 199  
200 -(((
201 -(((
202 -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.
203 -)))
204 204  
205 -(((
206 -(% 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
207 -)))
208 -)))
209 209  
210 -=== 3.3.1 onfigure UART settings for RS485 or TTL communication ===
211 211  
212 -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:
213 213  
214 -(% border="1" style="background-color:#ffffcc; color:green; width:795px" %)
210 +
211 +
212 +
213 +
214 +You can also choose to create the device manually.
215 +
215 215  |(((
216 -**AT Commands**
217 -)))|(% style="width:285px" %)(((
218 -**Description**
219 -)))|(% style="width:347px" %)(((
220 -**Example**
217 +
221 221  )))
222 -|(((
223 -AT+BAUDR
224 -)))|(% style="width:285px" %)(((
225 -Set the baud rate (for RS485 connection). Default Value is: 9600.
226 -)))|(% style="width:347px" %)(((
227 -(((
219 +
220 +
221 +
222 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image010.png]]
223 +
224 +Add APP KEY and DEV EUI
225 +
226 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image011.png]]
227 +
228 +
229 +**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.
230 +
231 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image012.png]]
232 +
233 +
234 +
235 +
236 +1.
237 +11. Configure Commands to read data
238 +
239 +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.
240 +
241 +
242 +1.
243 +11.
244 +111. Configure UART settings for RS485 or TTL communication
245 +
246 +RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect.
247 +
248 +1. RS485-MODBUS mode:
249 +
250 +AT+MOD=1 ~/~/ Support RS485-MODBUS type sensors. User can connect multiply RS485 , Modbus sensors to the A / B pins.
251 +
252 +
253 +1. TTL mode:
254 +
255 +AT+MOD=2 ~/~/ Support TTL Level sensors, User can connect one TTL Sensor to the TXD/RXD/GND pins.
256 +
257 +
258 +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.
259 +
260 +
261 +|**AT Commands**|**Description**|**Example**
262 +|AT+BAUDR|Set the baud rate (for RS485 connection). Default Value is: 9600.|(((
228 228  AT+BAUDR=9600
229 -)))
230 230  
231 -(((
232 232  Options: (1200,2400,4800,14400,19200,115200)
233 233  )))
234 -)))
235 -|(((
236 -AT+PARITY
237 -)))|(% style="width:285px" %)(((
267 +|AT+PARITY|(((
238 238  Set UART parity (for RS485 connection)
239 -)))|(% style="width:347px" %)(((
240 -(((
269 +
270 +Default Value is: no parity.
271 +)))|(((
241 241  AT+PARITY=0
242 -)))
243 243  
244 -(((
245 245  Option: 0: no parity, 1: odd parity, 2: even parity
246 246  )))
247 -)))
248 -|(((
249 -AT+STOPBIT
250 -)))|(% style="width:285px" %)(((
251 -(((
276 +|AT+STOPBIT|(((
252 252  Set serial stopbit (for RS485 connection)
253 -)))
254 254  
255 -(((
256 -
257 -)))
258 -)))|(% style="width:347px" %)(((
259 -(((
279 +Default Value is: 1bit.
280 +)))|(((
260 260  AT+STOPBIT=0 for 1bit
261 -)))
262 262  
263 -(((
264 264  AT+STOPBIT=1 for 1.5 bit
265 -)))
266 266  
267 -(((
268 268  AT+STOPBIT=2 for 2 bits
269 269  )))
270 -)))
271 271  
272 -=== 3.3.2 Configure sensors ===
273 273  
274 -(((
275 -(((
276 -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.
277 -)))
278 -)))
279 279  
280 -(% border="1" style="background-color:#ffffcc; color:green; width:806px" %)
281 -|**AT Commands**|(% style="width:418px" %)**Description**|(% style="width:256px" %)**Example**
282 -|AT+CFGDEV|(% style="width:418px" %)(((
290 +
291 +
292 +1.
293 +11.
294 +111. Configure sensors
295 +
296 +Some sensors might need to configure before normal operation. User can configure such sensor via PC or through RS485-BL AT Commands AT+CFGDEV.
297 +
298 +
299 +When user issue an AT+CFGDEV command, Each AT+CFGDEV equals to send a command to the RS485 or TTL sensors. This command will only run when user input it and won’t run during each sampling.
300 +
301 +|**AT Commands**|**Description**|**Example**
302 +|AT+CFGDEV|(((
283 283  This command is used to configure the RS485/TTL devices; they won’t be used during sampling.
284 284  
285 -AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,
305 +AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
286 286  
287 -mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
288 -)))|(% style="width:256px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
307 +m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
308 +)))|AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
289 289  
290 -=== 3.3.3 Configure read commands for each sampling ===
310 +Detail of AT+CFGDEV command see [[AT+CFGDEV detail>>path:#AT_CFGDEV]].
291 291  
292 -(((
312 +
313 +
314 +
315 +
316 +1.
317 +11.
318 +111. Configure read commands for each sampling
319 +
293 293  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.
294 -)))
295 295  
296 -(((
322 +
297 297  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.
298 -)))
299 299  
300 -(((
325 +
301 301  To save the LoRaWAN network bandwidth, we might need to read data from different sensors and combine their valid value into a short payload.
302 -)))
303 303  
304 -(((
328 +
305 305  This section describes how to achieve above goals.
306 -)))
307 307  
308 -(((
331 +
309 309  During each sampling, the RS485-BL can support 15 commands to read sensors. And combine the return to one or several uplink payloads.
310 -)))
311 311  
312 -(((
334 +
313 313  **Command from RS485-BL to Sensor:**
314 -)))
315 315  
316 -(((
317 317  RS485-BL can send out pre-set max 15 strings via **AT+COMMAD1**, **ATCOMMAND2**,…, to **AT+COMMANDF** . All commands are of same grammar.
318 -)))
319 319  
320 -(((
339 +
321 321  **Handle return from sensors to RS485-BL**:
322 -)))
323 323  
324 -(((
325 325  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**
326 -)))
327 327  
328 -* (((
329 -**AT+DATACUT**
330 -)))
331 331  
332 -(((
345 +* **AT+DATACUT**
346 +
333 333  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.
334 -)))
335 335  
336 -* (((
337 -**AT+SEARCH**
338 -)))
339 339  
340 -(((
350 +* **AT+SEARCH**
351 +
341 341  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.
342 -)))
343 343  
344 -(((
354 +
345 345  **Define wait timeout:**
346 -)))
347 347  
348 -(((
349 349  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
350 -)))
351 351  
352 -(((
359 +
353 353  After we got the valid value from each RS485 commands, we need to combine them together with the command **AT+DATAUP**.
354 -)))
355 355  
362 +
356 356  **Examples:**
357 357  
358 358  Below are examples for the how above AT Commands works.
359 359  
367 +
360 360  **AT+COMMANDx : **This command will be sent to RS485/TTL devices during each sampling, Max command length is 14 bytes. The grammar is:
361 361  
362 -(% border="1" class="table-bordered" %)
363 363  |(((
364 364  **AT+COMMANDx=xx xx xx xx xx xx xx xx xx xx xx xx,m**
365 365  
... ... @@ -368,19 +368,13 @@
368 368  **m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command**
369 369  )))
370 370  
371 -(((
372 372  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.
373 -)))
374 374  
375 -(((
376 376  In the RS485-BL, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
377 -)))
378 378  
379 -(((
382 +
380 380  **AT+SEARCHx**: This command defines how to handle the return from AT+COMMANDx.
381 -)))
382 382  
383 -(% border="1" class="table-bordered" %)
384 384  |(((
385 385  **AT+SEARCHx=aa,xx xx xx xx xx**
386 386  
... ... @@ -390,24 +390,26 @@
390 390  
391 391  )))
392 392  
393 -**Examples:**
394 +Examples:
394 394  
395 -~1. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
396 +1. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
396 396  
397 397  If we set AT+SEARCH1=1,1E 56 34.      (max 5 bytes for prefix)
398 398  
399 -The valid data will be all bytes after 1E 56 34 , so it is (% style="background-color:yellow" %)** 2e 30 58 5f 36 41 30 31 00 49**
400 +The valid data will be all bytes after 1E 56 34 , so it is 2e 30 58 5f 36 41 30 31 00 49
400 400  
401 -[[image:1653269403619-508.png]]
402 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image013.png]]
402 402  
403 -2. For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
404 404  
405 +1. For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
406 +
405 405  If we set AT+SEARCH1=2, 1E 56 34+31 00 49
406 406  
407 -Device will search the bytes between 1E 56 34 and 31 00 49. So it is (% style="background-color:yellow" %)** 2e 30 58 5f 36 41 30**
409 +Device will search the bytes between 1E 56 34 and 31 00 49. So it is 2e 30 58 5f 36 41 30
408 408  
409 -[[image:1653269438444-278.png]]
411 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image014.png]]
410 410  
413 +
411 411  **AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes.
412 412  
413 413  |(((
... ... @@ -415,7 +415,7 @@
415 415  
416 416  * **a: length for the return of AT+COMMAND**
417 417  * **b:1: grab valid value by byte, max 6 bytes. 2: grab valid value by bytes section, max 3 sections.**
418 -* **c: define the position for valid value.  **
421 +* **c: define the position for valid value. **
419 419  )))
420 420  
421 421  Examples:
... ... @@ -422,95 +422,94 @@
422 422  
423 423  * Grab bytes:
424 424  
425 -[[image:1653269551753-223.png||height="311" width="717"]]
428 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image015.png]]
426 426  
427 427  * Grab a section.
428 428  
429 -[[image:1653269568276-930.png||height="325" width="718"]]
432 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image016.png]]
430 430  
431 431  * Grab different sections.
432 432  
433 -[[image:1653269593172-426.png||height="303" width="725"]]
436 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image017.png]]
434 434  
435 -(% style="color:red" %)**Note:**
436 436  
439 +Note:
440 +
437 437  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.
438 438  
439 439  Example:
440 440  
441 -(% style="color:red" %)AT+COMMAND1=11 01 1E D0,0
445 +AT+COMMAND1=11 01 1E D0,0
442 442  
443 -(% style="color:red" %)AT+SEARCH1=1,1E 56 34
447 +AT+SEARCH1=1,1E 56 34
444 444  
445 -(% style="color:red" %)AT+DATACUT1=0,2,1~~5
449 +AT+DATACUT1=0,2,1~~5
446 446  
447 -(% style="color:red" %)Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
451 +Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
448 448  
449 -(% style="color:red" %)String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
453 +String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
450 450  
451 -(% style="color:red" %)Valid payload after DataCUT command: 2e 30 58 5f 36
455 +Valid payload after DataCUT command: 2e 30 58 5f 36
452 452  
453 -[[image:1653269618463-608.png]]
457 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image018.png]]
454 454  
455 -=== 3.3.4 Compose the uplink payload ===
456 456  
457 -(((
460 +
461 +
462 +1.
463 +11.
464 +111. Compose the uplink payload
465 +
458 458  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.**
459 -)))
460 460  
461 -(((
462 -(% style="color:#4f81bd" %)**Examples: AT+DATAUP=0**
463 -)))
464 464  
465 -(((
466 -Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**A SIGNLE UPLINK**.
467 -)))
469 +**Examples: AT+DATAUP=0**
468 468  
469 -(((
471 +Compose the uplink payload with value returns in sequence and send with **A SIGNLE UPLINK**.
472 +
470 470  Final Payload is
471 -)))
472 472  
473 -(((
474 -(% style="color:#4f81bd" %)**Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx**
475 -)))
475 +Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx
476 476  
477 -(((
478 478  Where PAYVER is defined by AT+PAYVER, below is an example screen shot.
479 -)))
480 480  
481 -[[image:1653269759169-150.png||height="513" width="716"]]
479 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.png]]
482 482  
483 -(% style="color:#4f81bd" %)**Examples: AT+DATAUP=1**
484 484  
485 -Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**Multiply UPLINKs**.
486 486  
483 +**Examples: AT+DATAUP=1**
484 +
485 +Compose the uplink payload with value returns in sequence and send with **Multiply UPLINKs**.
486 +
487 487  Final Payload is
488 488  
489 -(% style="color:#4f81bd" %)**Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA**
489 +Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA
490 490  
491 491  1. Battery Info (2 bytes): Battery voltage
492 492  1. PAYVER (1 byte): Defined by AT+PAYVER
493 493  1. PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling.
494 494  1. PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
495 -1. DATA: Valid value: max 6 bytes(US915 version here, Notice*!) for each uplink so each uplink <= 11 bytes. For the last uplink, DATA will might less than 6 bytes
495 +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
496 496  
497 -[[image:1653269916228-732.png||height="433" width="711"]]
497 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image020.png]]
498 498  
499 499  
500 500  So totally there will be 3 uplinks for this sampling, each uplink includes 6 bytes DATA
501 501  
502 -DATA1=RETURN1 Valid Value = (% style="background-color:green; color:white" %)20 20 0a 33 90 41
502 +DATA1=RETURN1 Valid Value = 20 20 0a 33 90 41
503 503  
504 -DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10=(% style="background-color:green; color:white" %) 02 aa 05 81 0a 20
504 +DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= 02 aa 05 81 0a 20
505 505  
506 -DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 = (% style="background-color:green; color:white" %)20 20 20 2d 30
506 +DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 = 20 20 20 2d 30
507 507  
508 +
509 +
508 508  Below are the uplink payloads:
509 509  
510 -[[image:1653270130359-810.png]]
512 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.png]]
511 511  
512 512  
513 -(% style="color:red" %)**Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:**
515 +Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:
514 514  
515 515   ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink ( so 51 -5 = 46 max valid date)
516 516  
... ... @@ -520,8 +520,12 @@
520 520  
521 521   ~* For all other bands: max 51 bytes for each uplink  ( so 51 -5 = 46 max valid date).
522 522  
523 -=== 3.3.5 Uplink on demand ===
524 524  
526 +
527 +1.
528 +11.
529 +111. Uplink on demand
530 +
525 525  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.
526 526  
527 527  Downlink control command:
... ... @@ -550,6 +550,7 @@
550 550  1.
551 551  11. Uplink Payload
552 552  
559 +
553 553  |**Size(bytes)**|**2**|**1**|**Length depends on the return from the commands**
554 554  |Value|(((
555 555  Battery(mV)
... ... @@ -598,7 +598,7 @@
598 598  
599 599  [[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]
600 600  
601 -1.
608 +1.
602 602  11. Configure RS485-BL via AT or Downlink
603 603  
604 604  User can configure RS485-BL via [[AT Commands >>path:#_​Using_the_AT]]or LoRaWAN Downlink Commands
... ... @@ -609,10 +609,12 @@
609 609  
610 610  * **Sensor Related Commands**: These commands are special designed for RS485-BL.  User can see these commands below:
611 611  
619 +
612 612  1.
613 613  11.
614 614  111. Common Commands:
615 615  
624 +
616 616  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]]
617 617  
618 618  
... ... @@ -620,6 +620,7 @@
620 620  11.
621 621  111. Sensor related commands:
622 622  
632 +
623 623  ==== Choose Device Type (RS485 or TTL) ====
624 624  
625 625  RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect.
... ... @@ -660,6 +660,7 @@
660 660  * XX XX XX XX: RS485 command total NN bytes
661 661  * 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
662 662  
673 +
663 663  **Example 1:**
664 664  
665 665  To connect a Modbus Alarm with below commands.
... ... @@ -768,6 +768,7 @@
768 768  
769 769  * AT+MBFUN=0: Disable Modbus fast reading.
770 770  
782 +
771 771  Example:
772 772  
773 773  * AT+MBFUN=1 and AT+DATACUT1/AT+DATACUT2 are not configure (0,0,0).
... ... @@ -852,7 +852,7 @@
852 852  
853 853  Etc. AT+CMDEAR=1,10 means erase AT+COMMAND1/AT+DATACUT1 to AT+COMMAND10/AT+DATACUT10
854 854  
855 -Example screen shot after clear all RS485 commands. 
867 +Example screen shot after clear all RS485 commands.
856 856  
857 857  
858 858  
... ... @@ -896,6 +896,7 @@
896 896  * A7 01 00 60   same as AT+BAUDR=9600
897 897  * A7 01 04 80  same as AT+BAUDR=115200
898 898  
911 +
899 899  A7 02 aa: Same as  AT+PARITY=aa  (aa value: 00 , 01 or 02)
900 900  
901 901  A7 03 aa: Same as  AT+STOPBIT=aa  (aa value: 00 , 01 or 02)
... ... @@ -926,15 +926,17 @@
926 926  1.
927 927  11. Buttons
928 928  
942 +
929 929  |**Button**|**Feature**
930 930  |**RST**|Reboot RS485-BL
931 931  
946 +
932 932  1.
933 933  11. +3V3 Output
934 934  
935 935  RS485-BL has a Controllable +3V3 output, user can use this output to power external sensor.
936 936  
937 -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. 
952 +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.
938 938  
939 939  
940 940  The +3V3 output time can be controlled by AT Command.
... ... @@ -952,7 +952,7 @@
952 952  
953 953  RS485-BL has a Controllable +5V output, user can use this output to power external sensor.
954 954  
955 -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. 
970 +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.
956 956  
957 957  
958 958  The 5V output time can be controlled by AT Command.
... ... @@ -973,6 +973,7 @@
973 973  |**LEDs**|**Feature**
974 974  |**LED1**|Blink when device transmit a packet.
975 975  
991 +
976 976  1.
977 977  11. Switch Jumper
978 978  
... ... @@ -994,6 +994,7 @@
994 994  
995 995  1. Case Study
996 996  
1013 +
997 997  User can check this URL for some case studies.
998 998  
999 999  [[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]]
... ... @@ -1081,6 +1081,7 @@
1081 1081  * For bug fix
1082 1082  * Change LoRaWAN bands.
1083 1083  
1101 +
1084 1084  Below shows the hardware connection for how to upload an image to RS485-BL:
1085 1085  
1086 1086  [[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image030.png]]
... ... @@ -1124,6 +1124,7 @@
1124 1124  1.
1125 1125  11. How many RS485-Slave can RS485-BL connects?
1126 1126  
1145 +
1127 1127  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]].
1128 1128  
1129 1129  
... ... @@ -1134,7 +1134,7 @@
1134 1134  
1135 1135  Please see this link for debug:
1136 1136  
1137 -[[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]] 
1156 +[[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]]
1138 1138  
1139 1139  
1140 1140  
... ... @@ -1149,6 +1149,7 @@
1149 1149  
1150 1150  1. Order Info
1151 1151  
1171 +
1152 1152  **Part Number: RS485-BL-XXX**
1153 1153  
1154 1154  **XXX:**
... ... @@ -1164,6 +1164,7 @@
1164 1164  * **RU864**: frequency bands RU864
1165 1165  * **KZ865: **frequency bands KZ865
1166 1166  
1187 +
1167 1167  1. Packing Info
1168 1168  
1169 1169  **Package Includes**:
... ... @@ -1172,6 +1172,7 @@
1172 1172  * Stick Antenna for LoRa RF part x 1
1173 1173  * Program cable x 1
1174 1174  
1196 +
1175 1175  **Dimension and weight**:
1176 1176  
1177 1177  * Device Size: 13.5 x 7 x 3 cm
... ... @@ -1179,6 +1179,7 @@
1179 1179  * Package Size / pcs : 14.5 x 8 x 5 cm
1180 1180  * Weight / pcs : 170g
1181 1181  
1204 +
1182 1182  1. Support
1183 1183  
1184 1184  * 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.
1652953414711-647.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -119.3 KB
Content
1652953462722-299.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -202.7 KB
Content
1652953542269-423.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -118.5 KB
Content
1652953553383-907.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -94.0 KB
Content
1652953568895-172.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -109.3 KB
Content
1652954654347-831.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -138.7 KB
Content
1653266934636-343.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -176.5 KB
Content
1653267211009-519.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -138.7 KB
Content
1653268091319-405.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -399.3 KB
Content
1653268155545-638.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -113.7 KB
Content
1653268227651-549.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -1.3 MB
Content
1653269403619-508.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -27.8 KB
Content
1653269438444-278.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -26.6 KB
Content
1653269551753-223.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -138.7 KB
Content
1653269568276-930.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -131.4 KB
Content
1653269593172-426.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -142.6 KB
Content
1653269618463-608.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -27.7 KB
Content
1653269759169-150.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -294.0 KB
Content
1653269916228-732.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -143.3 KB
Content
1653270130359-810.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -197.8 KB
Content
image-20220519174512-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -32.2 KB
Content
image-20220519174512-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -42.7 KB
Content
image-20220519174512-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -36.3 KB
Content
image-20220519174512-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -19.1 KB
Content