Show last authors
1 (% aria-label="1653266934636-343.png image widget" contenteditable="false" role="region" tabindex="-1" %)
2 (((
3 (% data-widget="image" style="text-align:center" %)
4 [[image:1653266934636-343.png||height="385" width="385"]](% title="Click and drag to resize" %)​
5
6 (% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||height="15" role="presentation" title="Click and drag to move" width="15"]]
7 )))
8
9
10
11
12
13
14
15 **Table of Contents:**
16
17 {{toc/}}
18
19
20 (% aria-label="macro:toc widget" contenteditable="false" role="region" tabindex="-1" %)
21 (((
22 (% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||height="15" role="presentation" title="Click and drag to move" width="15"]]
23 )))
24
25
26
27
28
29
30
31 = 1. Introduction =
32
33 == 1.1 What is RS485-LN RS485 to LoRaWAN Converter ==
34
35
36 (((
37 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.
38 )))
39
40 (((
41 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, building automation, and so on.
42 )))
43
44 (((
45 (% 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.
46 )))
47
48 (((
49 (% 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.
50 )))
51
52 (((
53 (% 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]]
54 )))
55
56
57 (% aria-label="1653267211009-519.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:1653267211009-519.png||data-widget="image" height="419" width="724"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)​
58
59
60 == 1.2 Specifications ==
61
62
63 (% style="color:#037691" %)**Hardware System:**
64
65 * STM32L072xxxx MCU
66 * SX1276/78 Wireless Chip 
67 * Power Consumption (exclude RS485 device):
68 ** Idle: 32mA@12v
69 ** 20dB Transmit: 65mA@12v
70
71 (% style="color:#037691" %)**Interface for Model:**
72
73 * RS485
74 * Power Input 7~~ 24V DC. 
75
76 (% style="color:#037691" %)**LoRa Spec:**
77
78 * Frequency Range:
79 ** Band 1 (HF): 862 ~~ 1020 Mhz
80 ** Band 2 (LF): 410 ~~ 528 Mhz
81 * 168 dB maximum link budget.
82 * +20 dBm - 100 mW constant RF output vs.
83 * +14 dBm high efficiency PA.
84 * Programmable bit rate up to 300 kbps.
85 * High sensitivity: down to -148 dBm.
86 * Bullet-proof front end: IIP3 = -12.5 dBm.
87 * Excellent blocking immunity.
88 * Low RX current of 10.3 mA, 200 nA register retention.
89 * Fully integrated synthesizer with a resolution of 61 Hz.
90 * FSK, GFSK, MSK, GMSK, LoRaTM and OOK modulation.
91 * Built-in bit synchronizer for clock recovery.
92 * Preamble detection.
93 * 127 dB Dynamic Range RSSI.
94 * Automatic RF Sense and CAD with ultra-fast AFC.
95 * Packet engine up to 256 bytes with CRC
96
97 == 1.3 Features ==
98
99
100 * LoRaWAN Class A & Class C protocol (default Class C)
101 * Frequency Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/IN865/RU864/MA869
102 * AT Commands to change parameters
103 * Remote configure parameters via LoRa Downlink
104 * Firmware upgradable via program port
105 * Support multiply RS485 devices by flexible rules
106 * Support Modbus protocol
107 * Support Interrupt uplink (Since hardware version v1.2)
108
109 == 1.4 Applications ==
110
111
112 * Smart Buildings & Home Automation
113 * Logistics and Supply Chain Management
114 * Smart Metering
115 * Smart Agriculture
116 * Smart Cities
117 * Smart Factory
118
119 == 1.5 Firmware Change log ==
120
121
122 [[RS485-LN Image files – Download link and Change log>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/]]
123
124
125 == 1.6 Hardware Change log ==
126
127
128 (((
129 (((
130 (((
131 v1.2: Add External Interrupt Pin.
132 )))
133
134 (((
135 v1.0: Release
136 )))
137
138
139 )))
140 )))
141
142 = 2. Power ON Device =
143
144
145 (((
146 The RS485-LN can be powered by 7 ~~ 24V DC power source. Connection as below
147
148 * Power Source VIN to RS485-LN VIN+
149 * Power Source GND to RS485-LN VIN-
150
151 (((
152 Once there is power, the RS485-LN will be on.
153 )))
154
155 (% aria-label="1653268091319-405.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:1653268091319-405.png||data-widget="image"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)​
156
157
158 )))
159
160 = 3. Operation Mode =
161
162 == 3.1 How it works? ==
163
164
165 (((
166 (((
167 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.
168 )))
169
170
171 )))
172
173 == 3.2 Example to join LoRaWAN network ==
174
175
176 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. 
177
178
179 (% aria-label="1653268155545-638.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:1653268155545-638.png||data-widget="image" height="334" width="724"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)​
180
181
182 (((
183 (((
184 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:
185 )))
186
187 (((
188 485A+ and 485B- of the sensor are connected to RS485A and RA485B of RS485-LN respectively.
189
190
191 )))
192
193 (% aria-label="1653268227651-549.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:1653268227651-549.png||data-widget="image" height="592" width="720"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)​
194
195
196 (((
197 The LG308 is already set to connect to [[TTN V3 network >>path:https://www.thethingsnetwork.org/]]. So what we need to now is only configure the TTN V3:
198
199
200 )))
201
202 (((
203 (% style="color:blue" %)**Step 1**(%%): Create a device in TTN V3 with the OTAA keys from RS485-LN.
204 )))
205
206 (((
207 Each RS485-LN is shipped with a sticker with unique device EUI:
208 )))
209 )))
210
211 (% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]][[image:image-20230425175410-2.png]](% title="Click and drag to resize" %)​
212
213
214 (((
215 (((
216 User can enter this key in their LoRaWAN Server portal. Below is TTN V3 screen shot:
217
218
219 )))
220
221 (((
222 **Add APP EUI in the application.**
223 )))
224 )))
225
226 (% aria-label="image-20220519174512-1.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:image-20220519174512-1.png||data-widget="image"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)​
227
228 (% aria-label="image-20220519174512-2.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:image-20220519174512-2.png||data-widget="image" height="323" width="720"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)​
229
230 (% aria-label="image-20220519174512-3.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:image-20220519174512-3.png||data-widget="image" height="556" width="724"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)​
231
232 (% aria-label="image-20220519174512-4.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:image-20220519174512-4.png||data-widget="image"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]]
233
234
235 (% title="Click and drag to resize" %)​
236
237 You can also choose to create the device manually.
238
239 (% aria-label="1652953542269-423.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:1652953542269-423.png||data-widget="image" height="710" width="723"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)​
240
241
242
243 **Add APP KEY and DEV EUI**
244
245 (% aria-label="1652953553383-907.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:1652953553383-907.png||data-widget="image" height="514" width="724"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)​
246
247
248 (((
249 (% style="color:blue" %)**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.
250
251
252 )))
253
254 (% aria-label="1652953568895-172.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:1652953568895-172.png||data-widget="image" height="232" width="724"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)​
255
256
257 == 3.3 Configure Device to Read RS485 Sensors ==
258
259
260 There are plenty of RS485 and TTL level devices in the market and each device has different commands to read the valid data. To support these devices in most flexible, RS485-LN supports flexible command set. User can use [[Dragino RS485 Tool>>url:https://www.dropbox.com/sh/us9qecn39fwt8n1/AABREdqUCzEmJMRrfuWuXasoa?dl=0]],  [[AT Commands or LoRaWAN Downlink>>url:http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/RS485-LB_Waterproof_RS485UART_to_LoRaWAN_Converter/#H3.5ConfigureRS485-LBviaATorDownlink]] Command to configure how RS485-LN should read the sensor and how to handle the return from RS485 or TTL sensors.
261
262
263 (((
264 (((
265 (((
266 (% 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**
267 )))
268
269
270 === 3.3.1 Method 1 ~-~- via RS485 Configure Tool ===
271
272
273 Use the RS485 Configure tool is the recommand method. Please see the instruction of how to use the tool:
274
275 * **[[RS485 Configure Tool Instruction>>url:http://wiki.dragino.com/xwiki/bin/view/Main/RS485_Configure_Tool/]]**
276
277 [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/RS485-LB_Waterproof_RS485UART_to_LoRaWAN_Converter/WebHome/image-20231127144411-1.png?width=494&height=368&rev=1.1||alt="image-20231127144411-1.png" height="368" width="494"]]
278
279
280 === 3.3.2  Method 2 ~-~- via AT Commands ===
281 )))
282 )))
283
284 ==== 3.3.2.1 Configure UART settings for RS485 communication ====
285
286 To use RS485-LN to read data from RS485 sensors, connect the RS485-LN A/B traces to the sensors. The related commands for UART settings are:
287
288 (% border="1" cellspacing="5" style="background-color:#f2f2f2; width:510px" %)
289 |=(% style="width: 126px; background-color:#D9E2F3;color:#0070C0" %)(((
290 **AT Commands**
291 )))|=(% style="width: 187px; background-color:#D9E2F3;color:#0070C0" %)(((
292 **Description**
293 )))|=(% style="width: 197px;background-color:#D9E2F3;color:#0070C0" %)(((
294 **Example**
295 )))
296 |(% style="width:126px" %)(((
297
298
299 (((
300 AT+BAUDR
301 )))
302 )))|(% style="width:177px" %)(((
303 Set the baud rate (for RS485 connection). Default Value is: 9600.
304 )))|(% style="width:193px" %)(((
305 (((
306 AT+BAUDR=9600
307 )))
308
309 (((
310 Options: (1200,2400,4800,
311 14400,19200,115200)
312 )))
313 )))
314 |(% style="width:126px" %)(((
315 AT+PARITY
316 )))|(% style="width:177px" %)(((
317 Set UART parity (for RS485 connection)
318 )))|(% style="width:193px" %)(((
319 (((
320 AT+PARITY=0
321 )))
322
323 (((
324 Option: 0: no parity,
325 1: odd parity,
326 2: even parity
327 )))
328 )))
329 |(% style="width:126px" %)(((
330 AT+STOPBIT
331 )))|(% style="width:177px" %)(((
332 (((
333 Set serial stopbit (for RS485 connection)
334 )))
335 )))|(% style="width:193px" %)(((
336 (((
337 AT+STOPBIT=0 for 1bit
338 )))
339
340 (((
341 AT+STOPBIT=1 for 1.5 bit
342 )))
343
344 (((
345 AT+STOPBIT=2 for 2 bits
346 )))
347 )))
348
349 === 3.3.3 Configure sensors ===
350
351
352 (((
353 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.
354 )))
355
356 (% border="1" cellspacing="5" style="background-color:#f2f2f2; width:510px" %)
357 |=(% style="width: 122px; background-color:#D9E2F3;color:#0070C0" %)**AT Commands**|=(% style="width: 198px; background-color:#D9E2F3;color:#0070C0" %)**Description**|=(% style="width: 190px;background-color:#D9E2F3;color:#0070C0" %)**Example**
358 |(% style="width:122px" %)AT+CFGDEV|(% style="width:196px" %)(((
359 (((
360 This command is used to configure the RS485/TTL devices; they won’t be used during sampling.
361 )))
362
363 (((
364 AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,
365 )))
366
367 (((
368 mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
369 )))
370 )))|(% style="width:190px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
371
372 === 3.3.4 Configure read commands for each sampling ===
373
374
375 (((
376 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.
377
378 To save the LoRaWAN network bandwidth, we might need to read data from different sensors and combine their valid value into a short payload.
379
380 This section describes how to achieve above goals.
381
382 During each sampling, the RS485-LN can support 15 commands to read sensors. And combine the return to one or several uplink payloads.
383
384
385 (% style="color:#037691" %)**Each RS485 commands include two parts:**
386
387
388 ~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.
389
390 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.
391
392 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
393
394
395 After we got the valid value from each RS485 commands, we need to combine them together with the command **AT+DATAUP**.
396
397 Below are examples for the how above AT Commands works.
398
399
400 (% style="color:#037691" %)**AT+COMMANDx **(%%)**: **This command will be sent to RS485 devices during each sampling, Max command length is 14 bytes. The grammar is:
401
402 (% border="1" style="background-color:#f2f2f2; width:499px" %)
403 |(% style="width:496px" %)(((
404 **AT+COMMANDx=xx xx xx xx xx xx xx xx xx xx xx xx,m**
405
406 **xx xx xx xx xx xx xx xx xx xx xx xx: The RS485 command to be sent**
407
408 **m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command**
409 )))
410
411 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.
412
413 In the RS485-LN, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
414
415
416 If a single command exceeds 14 bytes, you can use the command splicing function.
417
418 When AT+CMDDLx=1, the commands of AT+COMMANDx and AT+COMMAND(x+1) will be merged.
419
420
421 **Examples:** To send 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F data it should be configured:
422
423 AT+COMMAND1=00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D,0
424
425 AT+COMMAND1=1
426
427 AT+COMMAND2=0E 0F,0
428
429
430 (% style="color:#037691" %)**AT+DATACUTx **(%%)**: **This command defines how to handle the return from AT+COMMANDx, max return length is 100 bytes.
431
432 (% border="1" style="background-color:#f2f2f2; width:510px" %)
433 |(% style="width:510px" %)(((
434 **AT+DATACUTx=a,b,c**
435
436 * **a: length for the return of AT+COMMAND**
437 * **b:1: grab valid value by byte, max 6 bytes. 2: grab valid value by bytes section, max 3 sections.**
438 * **c: define the position for valid value.  **
439 )))
440
441 **Examples:**
442
443
444 * (% style="color:#037691" %)**Grab bytes**
445
446 (% aria-label="image-20220602153621-1.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:image-20220602153621-1.png||data-widget="image"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)​
447
448
449
450 * (% style="color:#037691" %)**Grab a section**
451
452 (% aria-label="image-20220602153621-2.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:image-20220602153621-2.png||data-widget="image"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)​
453
454
455
456 * (% style="color:#037691" %)**Grab different sections**
457
458 (% aria-label="image-20220602153621-3.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:image-20220602153621-3.png||data-widget="image"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)​
459
460
461 )))
462
463 === 3.3.5 Compose the uplink payload ===
464
465
466 (((
467 Through AT+COMMANDx and AT+DATACUTx we got valid value from each RS485 commands, Assume these valid value are RETURN1, RETURN2, .., to RETURNx. The next step is how to compose the LoRa Uplink Payload by these RETURNs. The command is **AT+DATAUP.**
468
469
470 )))
471
472 (((
473 (% style="color:#037691" %)**Examples: AT+DATAUP=0**
474
475
476 )))
477
478 (((
479 Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**A SIGNLE UPLINK**.
480 )))
481
482 (((
483 Final Payload is (% style="color:#4f81bd" %)**Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx**
484 )))
485
486 (((
487 Where PAYVER is defined by AT+PAYVER, below is an example screen shot.
488
489
490 )))
491
492 [[image:image-20220929111027-1.png||height="509" width="685"]](% title="Click and drag to resize" %)​
493
494
495 (% style="color:#037691" %)**Examples: AT+DATAUP=1**
496
497
498 Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**Multiply UPLINKs**.
499
500 Final Payload is (% style="color:#4f81bd" %)**PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA**
501
502
503 ~1. PAYVER: Defined by AT+PAYVER
504
505 2. PAYLOAD COUNT: Total how many uplinks of this sampling.
506
507 3. PAYLOAD#: Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
508
509 4. 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
510
511
512 (% aria-label="image-20220602155039-4.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:image-20220602155039-4.png||data-widget="image"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)​
513
514
515 So totally there will be 3 uplinks for this sampling, each uplink include 8 bytes DATA
516
517 DATA1=RETURN1 Valid Value + the first two of Valid value of RETURN10= **20 20 0a 33 90 41 02 aa**
518
519 DATA2=3^^rd^^ ~~ 10^^th^^ byte of Valid value of RETURN10= **05 81 0a 20 20 20 20 2d**
520
521 DATA3=the rest of Valid value of RETURN10= **30**
522
523
524 (% 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:**
525
526
527 ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink.
528
529 * For AU915/AS923 bands, if UplinkDwell time=0, max 11 bytes for each uplink.
530
531 * For US915 band, max 11 bytes for each uplink.
532
533 ~* For all other bands: max 51 bytes for each uplink.
534
535
536 (% style="color:red" %)** When AT+DATAUP=1, the maximum number of segments is 15, and the maximum total number of bytes is 1500;**
537
538 (% style="color:red" %)** When AT+DATAUP=1 and AT+ADR=0, the maximum number of bytes of each payload is determined by the DR value. (Since v1.4.0)**
539
540
541
542 Below are the uplink payloads:
543
544
545 (% aria-label="1654157178836-407.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:1654157178836-407.png||data-widget="image"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)​
546
547
548 === 3.3.6 Uplink on demand ===
549
550
551 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.
552
553 (% style="color:blue" %)**Downlink control command:**
554
555 (% style="color:#4472c4" %)** 0x08 command**(%%): Poll an uplink with current command set in RS485-LN.
556
557 (% style="color:#4472c4" %)** 0xA8 command**(%%): Send a command to RS485-LN and uplink the output from sensors.
558
559
560 === 3.3.7 Uplink on Interrupt ===
561
562
563 RS485-LN support external Interrupt uplink since hardware v1.2 release.
564
565 (% aria-label="1654157342174-798.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:1654157342174-798.png||data-widget="image"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)​
566
567 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.
568
569
570 == 3.4 Uplink Payload ==
571
572
573 (% border="1" cellspacing="5" style="background-color:#f2f2f2; width:510px" %)
574 |(% style="background-color:#d9e2f3; color:#0070c0; width:70px" %)(((
575 **Size(bytes)**
576 )))|(% style="background-color:#d9e2f3; color:#0070c0; width:80px" %)**1**|(% style="background-color:#d9e2f3; color:#0070c0; width:360px" %)(((
577 **Length depends on the return from the commands**
578 )))
579 |(% style="width:90px" %)(((
580 Value
581 )))|(% style="width:114px" %)(((
582 PAYLOAD_VER
583 )))|(% style="width:353px" %)(((
584 If the valid payload is too long and exceed the maximum
585
586 support payload length in server, server will show payload not
587
588 provided in the LoRaWAN server.
589 )))
590
591 (% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](%%)Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors.
592
593
594 == 3.5 Configure RS485-LN via AT or Downlink ==
595
596
597 (((
598 User can configure RS485-LN via AT Commands or LoRaWAN Downlink Commands
599 )))
600
601 (((
602 There are two kinds of Commands:
603 )))
604
605 * (((
606 (% 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: [[AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]
607 )))
608
609 * (((
610 (% style="color:#4f81bd" %)**Sensor Related Commands**(%%): These commands are special designed for RS485-LN.  User can see these commands below:
611 )))
612
613 (((
614
615 )))
616
617
618 === 3.5.1 Common Commands ===
619
620
621 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]]
622
623
624 === 3.5.2 Downlink Response(Since firmware v1.4) ===
625
626
627 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.
628
629
630 (% aria-label="image-20220602163333-5.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:image-20220602163333-5.png||data-widget="image" height="263" width="1160"]]
631
632 (% title="Click and drag to resize" %)​
633
634 The first byte of this package represents whether the configuration is successful, 00 represents failure, 01 represents success. Except for the first byte, the other is the previous downlink. (All commands except A8 type commands are applicable)
635
636
637 === 3.5.3 Sensor related commands ===
638
639
640
641 ==== (% style="color:blue" %)**RS485 Debug Command**(%%) ====
642
643
644 (((
645 This command is used to configure the RS485 devices; they won't be used during sampling. Max Length of AT+CFGDEV is **40 bytes**.
646 )))
647
648 (((
649 * (% style="color:#037691" %)**AT Command**
650
651 (((
652 (% style="color:#4472c4" %)** AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m**  (%%) m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
653 )))
654 )))
655
656 (((
657
658 )))
659
660 * (((
661 (% style="color:#037691" %)**Downlink Payload**
662 )))
663
664 (((
665 Format: (% style="color:#4472c4" %)** A8 MM NN XX XX XX XX YY**
666 )))
667
668 (((
669 Where:
670 )))
671
672 * (((
673 MM: 1: add CRC-16/MODBUS ; 0: no CRC
674 )))
675 * (((
676 NN: The length of RS485 command
677 )))
678 * (((
679 XX XX XX XX: RS485 command total NN bytes
680 )))
681 * (((
682 (((
683 YY: How many bytes will be uplink from the return of this RS485 command,
684 )))
685
686 * (((
687 if YY=0, RS485-LN will execute the downlink command without uplink;
688 )))
689 * (((
690 if YY>0, RS485-LN will uplink total YY bytes from the output of this RS485 command; Fport=200
691 )))
692 * (((
693 if YY=FF, RS485-LN will uplink RS485 output with the downlink command content; Fport=200.
694 )))
695 )))
696
697 (((
698
699
700 (% style="color:blue" %)**Example 1:**  (%%) ~-~-> Configure without ask for uplink (YY=0)
701 )))
702
703 (((
704 To connect a Modbus Alarm with below commands.
705 )))
706
707 * (((
708 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.
709 )))
710
711 * (((
712 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.
713 )))
714
715 (((
716
717
718 So if user want to use downlink command to control to RS485 Alarm, he can use:
719 )))
720
721 (((
722 (% style="color:#4f81bd" %)**A8 01 06 0A 05 00 04 00 01 00**(%%): to activate the RS485 Alarm
723 )))
724
725 (((
726 (% style="color:#4f81bd" %)**A8 01 06 0A 05 00 04 00 00 00**(%%): to deactivate the RS485 Alarm
727 )))
728
729 (((
730 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.
731 )))
732
733 (((
734
735 )))
736
737 (((
738 (% style="color:blue" %)**Example 2:**  (%%) ~-~-> Configure with requesting uplink and original downlink command (**YY=FF**)
739 )))
740
741 (((
742 User in IoT server send a downlink command: (% style="color:#4f81bd" %)**A8 01 06 0A 08 00 04 00 01 YY**
743 )))
744
745 (((
746
747 )))
748
749 (((
750 (((
751 RS485-LN got this downlink command and send (% style="color:#4f81bd" %)**0A 08 00 04 00 01 **(%%)to Modbus network. One of the RS485 sensor in the network send back Modbus reply **0A 08 00 04 00 00**. RS485-LN get this reply and combine with the original downlink command and uplink. The uplink message is:  **A8** (% style="color:#4f81bd" %)**0A 08 00 04 00  **(% style="color:red" %)**01 06** ** **(% style="color:green" %)**0A 08 00 04 00 00**
752 )))
753
754
755 )))
756
757 (((
758 (% aria-label="1654159460680-153.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:1654159460680-153.png||data-widget="image"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)​
759 )))
760
761
762
763 ==== (% style="color:blue" %)**Set Payload version**(%%) ====
764
765
766 (((
767 This is the first byte of the uplink payload. RS485-LN can connect to different sensors. User can set the PAYVER field to tell server how to decode the current payload.
768 )))
769
770 (((
771 * (% style="color:#037691" %)**AT Command:**
772
773 (% style="color:#4472c4" %)** AT+PAYVER:    ** (%%) Set PAYVER field = 1
774
775
776 )))
777
778 * (((
779 (% style="color:#037691" %)**Downlink Payload:**
780 )))
781
782 (((
783 (% style="color:#4472c4" %)** 0xAE 01** (%%) ~-~->  Set PAYVER field =  0x01
784 )))
785
786 (((
787 (% style="color:#4472c4" %)** 0xAE 0F**   (%%) ~-~->  Set PAYVER field =  0x0F
788 )))
789
790
791 **1 )  Add the interrupt flag at the highest bit of the Payver byte, that is, Byte7 of the first byte. (Since v1.4.0)**
792
793
794 [[image:image-20220824145428-2.png||height="168" width="1300"]]
795
796
797
798 **2 )  if the data intercepted by AT+DATACUT or AT+MBFUN is empty, it will display NULL, and the payload will be filled with n FFs.**
799
800
801 [[image:image-20220824145428-3.png||height="308" width="1200"]]
802
803
804
805 ==== (% style="color:blue" %)**Set RS485 Sampling Commands**(%%) ====
806
807
808 (((
809 AT+COMMANDx or AT+DATACUTx
810 )))
811
812 (((
813 These three commands are used to configure how the RS485-LN polling data from Modbus device. Detail of usage please see : [[polling RS485 device>>||anchor="H3.3.3Configurereadcommandsforeachsampling"]].
814 )))
815
816 (((
817
818 )))
819
820 * (((
821 (% style="color:#037691" %)**AT Command:**
822 )))
823
824 (% style="color:#4472c4" %)** AT+COMMANDx:    ** (%%) Configure RS485 read command to sensor.
825
826 (% style="color:#4472c4" %)** AT+DATACUTx:        **(%%) Configure how to handle return from RS485 devices.
827
828
829 * (((
830 (% style="color:#037691" %)**Downlink Payload:**
831 )))
832
833 (((
834 (% style="color:#4472c4" %)** 0xAF**(%%) downlink command can be used to set AT+COMMANDx or AT+DATACUTx.
835
836
837 )))
838
839 (((
840 (% style="color:red" %)**Note : if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink.**
841
842
843 )))
844
845 (((
846 Format: (% style="color:#4472c4" %)** AF MM NN LL XX XX XX XX YY**
847 )))
848
849 (((
850 Where:
851 )))
852
853 * (((
854 MM: the ATCOMMAND or AT+DATACUT to be set. Value from 01 ~~ 0F,
855 )))
856 * (((
857 NN:  0: no CRC; 1: add CRC-16/MODBUS ; 2: set the AT+DATACUT value.
858 )))
859 * (((
860 LL:  The length of AT+COMMAND or AT+DATACUT command
861 )))
862 * (((
863 XX XX XX XX: AT+COMMAND or AT+DATACUT command
864 )))
865 * (((
866 YY:  If YY=0, RS485-LN will execute the downlink command without uplink; if YY=1, RS485-LN will execute an uplink after got this command.
867 )))
868
869 (((
870
871
872 **Example:**
873 )))
874
875 (((
876 (% style="color:#037691" %)**AF 03 01 06 0A 05 00 04 00 01 00**(%%): Same as AT+COMMAND3=0A 05 00 04 00 01,1
877 )))
878
879 (((
880 (% style="color:#037691" %)**AF 03 02 06**(% style="color:orange" %)** 10 **(% style="color:red" %)**01 **(% style="color:green" %)**05 06 09 0A**(% style="color:#037691" %)** 00**(%%): Same as AT+DATACUT3=(% style="color:orange" %)**16**(%%),(% style="color:red" %)**1**(%%),(% style="color:green" %)**5+6+9+10**
881 )))
882
883 (((
884 (% style="color:#037691" %)**AF 03 02 06 **(% style="color:orange" %)**0B**(% style="color:red" %)** 02 **(% style="color:green" %)**05 07 08 0A **(% style="color:#037691" %)**00**(%%): Same as AT+DATACUT3=(% style="color:orange" %)**11**(%%),(% style="color:red" %)**2**(%%),(% style="color:green" %)**5~~7+8~~10**
885 )))
886
887
888
889 ==== (% style="color:blue" %)**Fast command to handle MODBUS device**(%%) ====
890
891
892 (((
893 (% style="color:#4472c4" %)** 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]].
894 )))
895
896 (((
897 This command is valid since v1.3 firmware version
898 )))
899
900 (((
901 AT+MBFUN can auto read the Modbus function code: 01, 02, 03 or 04. AT+MBFUN has lower priority vs AT+DATACUT command. If AT+DATACUT command is configured, AT+MBFUN will be ignore.
902 )))
903
904 (((
905
906 )))
907
908 (((
909 **Example:**
910 )))
911
912 * (((
913 AT+MBFUN=1 and AT+DATACUT1/AT+DATACUT2  are not configure (0,0,0). So RS485-LN.
914 )))
915 * (((
916 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.
917 )))
918 * (((
919 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.
920
921
922 )))
923
924 (% aria-label="image-20220602165351-6.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:image-20220602165351-6.png||data-widget="image"]]
925
926 (% title="Click and drag to resize" %)​
927
928 (% aria-label="image-20220602165351-7.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:image-20220602165351-7.png||data-widget="image"]](% title="Click and drag to resize" %)​
929
930 * (((
931 (% style="color:#037691" %)**Downlink Command:**
932 )))
933
934 **~ (% style="color:#4472c4" %)A9 aa(%%)** ~-~-> Same as AT+MBFUN=aa
935
936
937 ==== (% style="color:blue" %)**RS485 command timeout**(%%) ====
938
939
940 (((
941 Some Modbus device has slow action to send replies. This command is used to configure the RS485-LN to use longer time to wait for their action.
942 )))
943
944 (((
945 Default value: 0, range:  0 ~~ 65 seconds
946 )))
947
948 (((
949 * (% style="color:#037691" %)** AT Command:**
950
951 (% style="color:#4472c4" %)** AT+CMDDLaa=hex(bb cc)*1000**
952 )))
953
954 (((
955
956
957 **Example:**
958 )))
959
960 (((
961 (% style="color:#4472c4" %)** AT+CMDDL1=1000** (%%)to send the open time to 1000ms
962 )))
963
964 (((
965
966 )))
967
968 * (((
969 (% style="color:#037691" %)** Downlink Payload:**
970 )))
971
972 (((
973 (% style="color:#4472c4" %)** 0x AA aa bb cc**(%%) Same as: AT+CMDDLaa=hex (bb cc)
974 )))
975
976 (((
977
978
979 **Example:**
980 )))
981
982 (((
983 **0xAA 01 03 E8**  ~-~-> Same as  **AT+CMDDL1=1000 ms**
984 )))
985
986
987
988 ==== (% style="color:blue" %)**Uplink payload mode**(%%) ====
989
990
991 (((
992 Define to use one uplink or multiple uplinks for the sampling.
993 )))
994
995 (((
996 The use of this command please see: [[Compose Uplink payload>>||anchor="H3.3.4Composetheuplinkpayload"]]
997
998
999 )))
1000
1001 (((
1002 * (% style="color:#037691" %)** AT Command:**
1003
1004 (% style="color:#4472c4" %)** AT+DATAUP=0**
1005
1006 (% style="color:#4472c4" %)** AT+DATAUP=1**
1007
1008
1009 )))
1010
1011 (% style="color:#4472c4" %)** 0xAD 01 00 00 14** (%%) **~-~->** Same as AT+DATAUP=1,20000  ~/~/  (00 00 14 is 20 seconds)
1012
1013 Each uplink is sent to the server at 20-second intervals when segmented.
1014
1015
1016 * (((
1017 (% style="color:#037691" %)** Downlink Payload:**
1018 )))
1019
1020 (% style="color:#4472c4" %)** 0xAD 00** (%%) **~-~->** Same as AT+DATAUP=0
1021
1022 (% style="color:#4472c4" %)** 0xAD 01**  (%%) **~-~->** Same as AT+DATAUP=1  ~/~/Each uplink is sent to the server one after the other as it is segmented.
1023
1024
1025 (Since firmware v1.4.0)
1026
1027 * (((
1028 (% style="color:#037691" %)** AT Command:**
1029 )))
1030
1031 (% style="color:#4472c4" %)** AT+DATAUP=1,Timeout**
1032
1033
1034 * (((
1035 (% style="color:#037691" %)** Downlink Payload:**
1036 )))
1037
1038 (% style="color:#4472c4" %)** 0xAD 01 00 00 14** (%%) **~-~->** Same as AT+DATAUP=1,20000  ~/~/  (00 00 14 is 20 seconds)
1039
1040 Each uplink is sent to the server at 20-second intervals when segmented.
1041
1042
1043 ==== (% style="color:blue" %)**Cut data separation processing(Since Version 1.4.2)**(%%) ====
1044
1045
1046 AT+NEWLINE command, which only takes effect when AT+DATAUP=1 or AT+DATAUP=1, timeout.
1047
1048 When not set, each part of AT+DATAUP is sent according to the maximum number of bytes of DR.
1049
1050 When setting, each part of AT+DATAUP is sent according to the value set by AT+NEWLINE.
1051
1052
1053 * (((
1054 (% style="color:#037691" %)** AT Command:**
1055 )))
1056
1057 (% style="color:#4472c4" %)//**AT+NEWLINE=ALL**//(%%)//   //The data cut out by each AT+COMMANDx command is sent separately as an uplink.
1058
1059 (% style="color:#4472c4" %)//**AT+NEWLINE=ALL**//(%%)//   equal:  (% style="color:#4472c4" %)**AT+NEWLINE=1+2+3+4+5+6+7+8+9+10+11+12+13+14+15**//
1060
1061
1062 (% style="color:#4472c4" %)//**AT+NEWLINE=a+b+c**//(%%)//  //The data returned by all commands is divided into three parts, COMMAND(1~~a) is the first part, COMMAND(a+1~~b) is the second part,COMMAND(b+1~~c) is the third part.
1063
1064
1065 (% style="color:#4472c4" %)//**AT+NEWLINE=NULL**//(%%)//  //Turn off the functionality of this AT command.
1066
1067
1068 * (((
1069 (% style="color:#037691" %)** Downlink Payload:**
1070 )))
1071
1072 //AT+NEWLINE=ALL  ~-~-->  (% style="color:#4472c4" %)**0xAC 01**//
1073
1074 // AT+NEWLINE= NULL  ~-~-->  (% style="color:#4472c4" %)**0xAC 00**//
1075
1076 //AT+NEWLINE= a+b+c   ~-~-->  (% style="color:#4472c4" %)**0xAC number of bytes a b c**//
1077
1078 //AT+NEWLINE= 1+5+15 ~-~-->  (% style="color:#4472c4" %)**0xAC 03 01 05 0F**//
1079
1080
1081 ==== (% style="color:blue" %)**Manually trigger an Uplink**(%%) ====
1082
1083
1084 (((
1085 Ask device to send an uplink immediately.
1086 )))
1087
1088 * (((
1089 (% style="color:#037691" %)** AT Command:**
1090 )))
1091
1092 (((
1093 No AT Command for this, user can press the [[ACT button>>||anchor="H3.7Buttons"]] for 1 second for the same.
1094 )))
1095
1096 (((
1097
1098 )))
1099
1100 * (((
1101 (% style="color:#037691" %)** Downlink Payload:**
1102 )))
1103
1104 (((
1105 (% style="color:#4472c4" %)** 0x08 FF**(%%), RS485-LN will immediately send an uplink.
1106 )))
1107
1108
1109
1110 ==== (% style="color:blue" %)**Clear RS485 Command**(%%) ====
1111
1112
1113 (((
1114 The AT+COMMANDx and AT+DATACUTx settings are stored in special location, user can use below command to clear them.
1115
1116
1117 )))
1118
1119 * (((
1120 (% style="color:#037691" %)** AT Command:**
1121 )))
1122
1123 (((
1124 (% style="color:#4472c4" %)** AT+CMDEAR=mm,nn** (%%) mm: start position of erase ,nn: stop position of erase
1125 )))
1126
1127 (((
1128
1129
1130 Etc. AT+CMDEAR=1,10 means erase AT+COMMAND1/AT+DATACUT1 to AT+COMMAND10/AT+DATACUT10
1131 )))
1132
1133 (((
1134 Example screen shot after clear all RS485 commands. 
1135 )))
1136
1137 (((
1138
1139 )))
1140
1141 (((
1142 The uplink screen shot is:
1143 )))
1144
1145 (% aria-label="1654160691922-496.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:1654160691922-496.png||data-widget="image"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)​
1146
1147
1148 * (((
1149 (% style="color:#037691" %)** Downlink Payload:**
1150 )))
1151
1152 (((
1153 (% style="color:#4472c4" %)** 0x09 aa bb** (%%) same as AT+CMDEAR=aa,bb
1154 )))
1155
1156
1157
1158 ==== (% style="color:blue" %)**Set Serial Communication Parameters**(%%) ====
1159
1160
1161 (((
1162 Set the Rs485 serial communication parameters:
1163 )))
1164
1165 (((
1166 (% style="color:#037691" %)**AT Command:**
1167 )))
1168
1169 (((
1170 * Set Baud Rate
1171 )))
1172
1173 (% style="color:#4472c4" %)** AT+BAUDR=9600** (%%) ~/~/  Options: (200~~115200)  When using low baud rate or receiving multiple bytes, you need to use AT+CMDDL to increase the receive timeout (the default receive timeout is 400ms), otherwise data will be lost
1174
1175
1176 (((
1177 * Set UART Parity
1178 )))
1179
1180 (% style="color:#4472c4" %)** AT+PARITY=0** (%%) ~/~/  Option: 0: no parity, 1: odd parity, 2: even parity
1181
1182
1183 (((
1184 * Set STOPBIT
1185 )))
1186
1187 (% style="color:#4472c4" %)** AT+STOPBIT=0** (%%) ~/~/  Option: 0 for 1bit; 1 for 1.5 bit ; 2 for 2 bits
1188
1189
1190 (((
1191 (% style="color:#037691" %)**Downlink Payload:**
1192 )))
1193
1194 (((
1195 (% style="color:#4472c4" %)** A7 01 aa bb**:   (%%) Same  AT+BAUDR=hex(aa bb)*100
1196 )))
1197
1198 (((
1199 **Example:**
1200 )))
1201
1202 * (((
1203 A7 01 00 60  same as AT+BAUDR=9600
1204 )))
1205 * (((
1206 A7 01 04 80  same as AT+BAUDR=115200
1207 )))
1208
1209 (((
1210 * A7 02 aa:  Same as  AT+PARITY=aa  (aa value: 00 , 01 or 02)
1211 )))
1212
1213 (((
1214 * A7 03 aa:  Same as  AT+STOPBIT=aa  (aa value: 00 , 01 or 02)
1215 )))
1216
1217
1218
1219
1220 ==== (% style="color:blue" %)**Configure Databit (Since Version 1.4.0)**(%%) ====
1221
1222
1223 * (((
1224 (% style="color:#037691" %)** AT Command:**
1225 )))
1226
1227 (% style="color:#4472c4" %)** AT+DATABIT=7    **(%%)~/~/ Set the data bits to 7
1228
1229 (% style="color:#4472c4" %)** AT+DATABIT=8    **(%%)~/~/ Set the data bits to 8
1230
1231 * (((
1232 (% style="color:#037691" %)**Downlink Payload:**
1233 )))
1234
1235 (% style="color:#4472c4" %)** A7 04 07**(%%): Same as  AT+DATABIT=7
1236
1237 (% style="color:#4472c4" %)** A7 04 08**(%%): Same as  AT+DATABIT=8
1238
1239
1240
1241 ==== (% style="color:blue" %)**Encrypted payload(Since Version 1.4.0)**(%%) ====
1242
1243 (((
1244
1245 )))
1246
1247 * (((
1248 (% style="color:#037691" %)** AT Command:**
1249 )))
1250
1251 (% style="color:#4472c4" %)** AT+DECRYPT=1  ** (%%) ~/~/ The payload is uploaded without encryption
1252
1253 (% style="color:#4472c4" %)** AT+DECRYPT=0  ** (%%) ~/~/ Encrypt when uploading payload (default)
1254
1255
1256
1257 ==== (% style="color:blue" %)**Get sensor value(Since Version 1.4.0)**(%%) ====
1258
1259
1260 * (((
1261 (% style="color:#037691" %)** AT Command:**
1262 )))
1263
1264 (% style="color:#4472c4" %)** AT+GETSENSORVALUE=0  **(%%) ~/~/ The serial port gets the reading of the current sensor
1265
1266 (% style="color:#4472c4" %)** AT+GETSENSORVALUE=1  **(%%) ~/~/ The serial port gets the current sensor reading and uploads it.
1267
1268
1269
1270 ==== (% style="color:blue" %)**Resets the downlink packet count(Since Version 1.4.0)**(%%) ====
1271
1272
1273 * (((
1274 (% style="color:#037691" %)** AT Command:**
1275 )))
1276
1277 (% style="color:#4472c4" %)** AT+DISFCNTCHECK=0  **(%%) ~/~/  When the downlink packet count sent by the server is less than the node downlink packet count or exceeds 16384, the node will no longer receive downlink packets (default)
1278
1279 (% style="color:#4472c4" %)** AT+DISFCNTCHECK=1  **(%%) ~/~/  When the downlink packet count sent by the server is less than the node downlink packet count or exceeds 16384, the node resets the downlink packet count and keeps it consistent with the server downlink packet count.
1280
1281
1282
1283 ==== (% style="color:blue" %)**When the limit bytes are exceeded, upload in batches(Since Version 1.4.0)**(%%) ====
1284
1285
1286 * (((
1287 (% style="color:#037691" %)** AT Command:**
1288 )))
1289
1290 (% style="color:#4472c4" %)** AT+DISMACANS=0**  (%%) ~/~/  When the MACANS of the reply server plus the payload exceeds the maximum number of bytes of 11 bytes (DR0 of US915, DR2 of AS923, DR2 of AU195), the node will send a packet with a payload of 00 and a port of 4. (default)
1291
1292 (% style="color:#4472c4" %)** AT+DISMACANS=1**   (%%) ~/~/  When the MACANS of the reply server plus the payload exceeds the maximum number of bytes of the DR, the node will ignore the MACANS and not reply, and only upload the payload part.
1293
1294
1295 * (((
1296 (% style="color:#037691" %)** Downlink Payload:**
1297 )))
1298
1299 (% style="color:#4472c4" %)** 0x21 00 01 ** (%%) ~/~/ Set  the DISMACANS=1
1300
1301
1302
1303 ==== (% style="color:blue" %)**Copy downlink to uplink (Since Version 1.4.0)**(%%) ====
1304
1305
1306 * (((
1307 (% style="color:#037691" %)** AT Command:**
1308 )))
1309
1310 (% style="color:#4472c4" %)** AT+RPL=5**  (%%) ~/~/ After receiving the package from the server, it will immediately upload the content of the package to the server, the port number is 100.
1311
1312 Example:**aa xx xx xx xx**         ~/~/ aa indicates whether the configuration has changed, 00 is yes, 01 is no; xx xx xx xx are the bytes sent.
1313
1314
1315 [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LSN50%20%26%20LSN50-V2%20-%20LoRaWAN%20Sensor%20Node%20User%20Manual/WebHome/image-20220823173747-6.png?width=1124&height=165&rev=1.1||alt="image-20220823173747-6.png"]]
1316
1317 For example, sending 11 22 33 44 55 66 77 will return invalid configuration 00 11 22 33 44 55 66 77.
1318
1319
1320
1321 [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LSN50%20%26%20LSN50-V2%20-%20LoRaWAN%20Sensor%20Node%20User%20Manual/WebHome/image-20220823173833-7.png?width=1124&height=149&rev=1.1||alt="image-20220823173833-7.png"]]
1322
1323 For example, if 01 00 02 58 is issued, a valid configuration of 01 01 00 02 58 will be returned.
1324
1325
1326
1327 ==== (% style="color:blue" %)**Query version number and frequency band 、TDC(Since Version 1.4.0)**(%%) ====
1328
1329
1330 (((
1331 * (% style="color:#037691" %)**Downlink Payload:**
1332
1333 (% style="color:#4472c4" %)** 26 01  ** (%%) ~/~/  Downlink 26 01 can query device upload frequency, frequency band, software version number, TDC time.
1334 )))
1335
1336
1337 Example:
1338
1339
1340 [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LSN50%20%26%20LSN50-V2%20-%20LoRaWAN%20Sensor%20Node%20User%20Manual/WebHome/image-20220823173929-8.png?width=1205&height=76&rev=1.1||alt="image-20220823173929-8.png"]]
1341
1342
1343
1344 ==== (% style="color:blue" %)** Monitor RS485 communication of other devices(Since Version 1.4.0)**(%%) ====
1345
1346
1347 * (((
1348 (% style="color:#037691" %)** AT Command:**
1349 )))
1350
1351 (% style="color:#4472c4" %)**AT+RXMODE=1,10**    (%%) ~/~/ When the RS485-LN receives more than 10 bytes from the RS485, it immediately sends the uplink of the received data.
1352
1353 (% style="color:#4472c4" %)**AT+RXMODE=2,500    ** (%%) ~/~/  RS485-LN uploads data as uplink from the first byte received by RS485 to the data received within 500ms after that.
1354
1355 (% style="color:#4472c4" %)**AT+RXMODE=0,0  ** (%%) ~/~/  Disable this mode (default)
1356
1357
1358 * (((
1359 (% style="color:#037691" %)**Downlink Payload:**
1360 )))
1361
1362 (% style="color:#4472c4" %)** A6 aa bb bb               ** (%%) ~/~/ same as AT+RXMODE=aa,bb
1363
1364 [[image:image-20220824144240-1.png]]
1365
1366
1367 == 3.6 Listening mode for RS485 network ==
1368
1369
1370 (((
1371 This feature support since firmware v1.4
1372 )))
1373
1374 (((
1375 RS485-LN supports listening mode, it can listen the RS485 network packets and send them via LoRaWAN uplink. Below is the structure. The blue arrow shows the RS485 network packets to RS485-LN.
1376
1377
1378 )))
1379
1380 (% aria-label="image-20220602171200-8.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:image-20220602171200-8.png||data-widget="image" height="567" width="1007"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]]
1381
1382 (% title="Click and drag to resize" %)​
1383
1384 (((
1385 To enable the listening mode, use can run the command (% style="color:#4472c4" %)** AT+RXMODE**.
1386 )))
1387
1388 (% border="1" cellspacing="5" style="background-color:#f2f2f2; width:510px" %)
1389 |=(% style="width: 156px; background-color:#D9E2F3;color:#0070C0" %)(((
1390 **Command example**
1391 )))|=(% style="width: 355px; background-color:#D9E2F3;color:#0070C0" %)(((
1392 **Function**
1393 )))
1394 |(% style="width:156px" %)(((
1395 AT+RXMODE=1,10
1396 )))|(% style="width:352px" %)(((
1397 Enable listening mode 1, if RS485-LN has received more than 10 RS485 commands from the network. RS485-LN will send these commands via LoRaWAN uplinks.
1398 )))
1399 |(% style="width:156px" %)(((
1400 AT+RXMODE=2,500
1401 )))|(% style="width:352px" %)(((
1402 Enable listening mode 2, RS485-LN will capture and send a 500ms content once from the first detect of character. Max value is 65535 ms
1403 )))
1404 |(% style="width:156px" %)(((
1405 AT+RXMODE=0,0
1406 )))|(% style="width:352px" %)(((
1407 Disable listening mode. This is the default settings.
1408 )))
1409 |(% style="width:156px" %)(((
1410
1411 )))|(% style="width:352px" %)(((
1412 A6 aa bb cc  same as AT+RXMODE=aa,(bb<<8 | cc)
1413 )))
1414
1415 (((
1416
1417
1418 (% style="color:#037691" %)**Downlink Command:**
1419 )))
1420
1421 (((
1422 (% style="color:#4472c4" %)** 0xA6 aa bb cc **(%%) same as AT+RXMODE=aa,(bb<<8 | cc)
1423 )))
1424
1425 (((
1426
1427 )))
1428
1429 (((
1430 **Example**:
1431 )))
1432
1433 (((
1434 The RS485-LN is set to AT+RXMODE=2,1000
1435 )))
1436
1437 (((
1438 There is a two Modbus commands in the RS485 network as below:
1439 )))
1440
1441 (((
1442 The Modbus master send a command: (% style="background-color:#ffc000" %)**01 03 00 00 00 02 c4 0b**
1443 )))
1444
1445 (((
1446 And Modbus slave reply with: (% style="background-color:green" %)**01 03 04 00 00 00 00 fa 33**
1447 )))
1448
1449 (((
1450 RS485-LN will capture both and send the uplink: (% style="background-color:#ffc000" %)**01 03 00 00 00 02 c4 0b  **(% style="background-color:green" %)**01 03 04 00 00 00 00 fa 33**
1451
1452
1453 )))
1454
1455 (((
1456 (% aria-label="image-20220602171200-9.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:image-20220602171200-9.png||data-widget="image"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)​
1457 )))
1458
1459
1460
1461 (((
1462 (% style="color:red" %)**Notice: Listening mode can work with the default polling mode of RS485-LN. When RS485-LN is in to send the RS485 commands (from AT+COMMANDx), the listening mode will be interrupt for a while.**
1463 )))
1464
1465
1466 == 3.7 Buttons ==
1467
1468
1469 (% border="1.5" cellspacing="4" style="background-color:#f2f2f2; width:430px" %)
1470 |=(% style="width: 50px;background-color:#D9E2F3;color:#0070C0" %)**Button**|=(% style="width: 380px;background-color:#D9E2F3;color:#0070C0" %)**Feature**
1471 |(% style="width:50px" %)ACT|(% style="width:361px" %)If RS485 joined in network, press this button for more than 1 second, RS485 will upload a packet, and the SYS LED will give a (% style="color:blue" %)**Blue blink**
1472 |(% style="width:50px" %)RST|(% style="width:361px" %)Reboot RS485
1473 |(% style="width:50px" %)PRO|(% style="width:361px" %)Use for upload image, see [[How to Update Image>>||anchor="H6.1Howtoupgradetheimage3F"]]
1474
1475 == 3.8 LEDs ==
1476
1477
1478 (% border="1.5" cellspacing="4" style="background-color:#f2f2f2; width:430px" %)
1479 |=(% style="width: 50px;background-color:#D9E2F3;color:#0070C0" %)**LEDs**|=(% style="width: 380px;background-color:#D9E2F3;color:#0070C0" %)**Feature**
1480 |PWR|Always on if there is power
1481 |SYS|After device is powered on, the SYS will (% style="color:green" %)**fast blink in GREEN**(%%) for 5 times, means RS485-LN start to join LoRaWAN network. If join success, SYS will be (% style="color:green" %)**on GREEN for 5 seconds** (%%)**. **SYS will (% style="color:green" %)**blink Blue**(%%) on every upload and (% style="color:green" %)**blink Green**(%%) once receive a downlink message.
1482
1483 = 4. Case Study =
1484
1485
1486 User can check this URL for some case studies: [[APP RS485 COMMUNICATE WITH SENSORS>>doc:Main.Application Note \: Communicate with Different Sensors ----- RS485-LN RS485-BL.WebHome]]
1487
1488
1489 = 5. Use AT Command =
1490
1491 == 5.1 Access AT Command ==
1492
1493
1494 (((
1495 RS485-LN supports AT Command set. User can use a USB to TTL adapter plus the 3.5mm Program Cable to connect to RS485-LN to use AT command, as below.
1496
1497
1498 )))
1499
1500 (% aria-label="1654162355560-817.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:1654162355560-817.png||data-widget="image"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)​
1501
1502
1503
1504 (((
1505 In PC, User needs to set (% style="color:blue" %)**serial tool**(%%)(such as [[putty>>url:https://www.chiark.greenend.org.uk/~~sgtatham/putty/latest.html]], SecureCRT) baud rate to (% style="color:green" %)**9600**(%%) to access to access serial console of RS485-LN. The default password is 123456. Below is the output for reference:
1506
1507
1508 )))
1509
1510 (% aria-label="1654162368066-342.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:1654162368066-342.png||data-widget="image"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)​
1511
1512
1513 (((
1514 More detail AT Command manual can be found at [[AT Command Manual>>https://www.dragino.com/downloads/index.php?dir=LT_LoRa_IO_Controller/LT33222-L/]]
1515 )))
1516
1517
1518 == 5.2 Common AT Command Sequence ==
1519
1520 === 5.2.1 Multi-channel ABP mode (Use with SX1301/LG308) ===
1521
1522
1523 If device has not joined network yet:
1524
1525 * (% style="color:#037691" %)**AT+FDR**
1526 * (% style="color:#037691" %)**AT+NJM=0**
1527 * (% style="color:#037691" %)**ATZ**
1528
1529 (((
1530
1531
1532 If device already joined network:
1533
1534 * (% style="color:#037691" %)**AT+NJM=0**
1535 * (% style="color:#037691" %)**ATZ**
1536 )))
1537
1538
1539
1540 === 5.5.2 Single-channel ABP mode (Use with LG01/LG02) ===
1541
1542
1543 (% style="background-color:#dcdcdc" %)**AT+FDR** (%%) Reset Parameters to Factory Default, Keys Reserve
1544
1545 (% style="background-color:#dcdcdc" %)**AT+NJM=0 **(%%) Set to ABP mode
1546
1547 (% style="background-color:#dcdcdc" %)**AT+ADR=0** (%%) Set the Adaptive Data Rate Off
1548
1549 (% style="background-color:#dcdcdc" %)**AT+DR=5**   (%%) Set Data Rate
1550
1551 (% style="background-color:#dcdcdc" %)**AT+TDC=60000** (%%) Set transmit interval to 60 seconds
1552
1553 (% style="background-color:#dcdcdc" %)**AT+CHS=868400000**(%%)  Set transmit frequency to 868.4Mhz
1554
1555 (% style="background-color:#dcdcdc" %)**AT+RX2FQ=868400000** (%%) Set RX2Frequency to 868.4Mhz (according to the result from server)
1556
1557 (% style="background-color:#dcdcdc" %)**AT+RX2DR=5**  (%%) Set RX2DR to match the downlink DR from server. see below
1558
1559 (% style="background-color:#dcdcdc" %)**AT+DADDR=26** (%%) 01 1A F1 Set Device Address to 26 01 1A F1, this ID can be found in the LoRa Server portal.
1560
1561 (% style="background-color:#dcdcdc" %)**ATZ**       (%%) Reset MCU
1562
1563
1564 (% style="color:red" %)**Note:**
1565
1566 (((
1567 (% style="color:red" %)1. Make sure the device is set to ABP mode in the IoT Server.
1568 2. Make sure the LG01/02 gateway RX frequency is exactly the same as AT+CHS setting.
1569 3. 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.
1570 4. 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
1571
1572
1573 )))
1574
1575 (% aria-label="1654162478620-421.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:1654162478620-421.png||data-widget="image"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)​
1576
1577
1578 = 6. FAQ =
1579
1580 == 6.1 How to upgrade the image? ==
1581
1582
1583 (((
1584 The RS485-LN LoRaWAN Controller is shipped with a 3.5mm cable, the cable is used to upload image to RS485-LN to:
1585 )))
1586
1587 * (((
1588 Support new features
1589 )))
1590 * (((
1591 For bug fix
1592 )))
1593 * (((
1594 Change LoRaWAN bands.
1595 )))
1596
1597 (((
1598 Below shows the hardware connection for how to upload an image to RS485-LN:
1599 )))
1600
1601 (% aria-label="1654162535040-878.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:1654162535040-878.png||data-widget="image"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]]
1602
1603 (% title="Click and drag to resize" %)​
1604
1605 (((
1606 (% style="color:blue" %)**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]].
1607
1608
1609 )))
1610
1611 (((
1612 (% style="color:blue" %)**Step2**(%%)**:** Download the [[LT Image files>>url:https://www.dropbox.com/sh/g99v0fxcltn9r1y/AACP33wo_ZQLsxW2MJ70oUoba/RS485-LN/Firmware?dl=0&subfolder_nav_tracking=1]].
1613
1614
1615 )))
1616
1617 (((
1618 (% style="color:blue" %)**Step3**(%%)**: **Open flashloader; choose the correct COM port to update.
1619
1620
1621 )))
1622
1623 (((
1624 (((
1625 (((
1626 (% style="color:blue" %) Hold down the PRO button and then momentarily press the RST reset button and the SYS led will change from OFF to ON, While SYS LED is RED ON, it means the RS485-LN is ready to be program.
1627 )))
1628 )))
1629 )))
1630
1631
1632 (% aria-label="image-20220602175818-12.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:image-20220602175818-12.png||data-widget="image"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)​
1633
1634
1635 (% aria-label="image-20220602175848-13.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:image-20220602175848-13.png||data-widget="image"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)​
1636
1637
1638 (% aria-label="image-20220602175912-14.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:image-20220602175912-14.png||data-widget="image"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)​
1639
1640
1641
1642 (% style="color:red" %)**Users can select the new burning software STM32Cubeprogramer for firmware upgrade and follow the same connection steps to enter burning mode (until SYS LED is RED ON):**
1643
1644 [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H4.2.FirmwareupgradeusingSTM32Cubeprogramer>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H4.2.FirmwareupgradeusingSTM32Cubeprogramer]]
1645
1646
1647 (% style="color:red" %)**Notice**: **In case user has lost the program cable. User can hand made one from a 3.5mm cable. The pin mapping is:**
1648
1649 (% aria-label="image-20220602175638-10.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:image-20220602175638-10.png||data-widget="image"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)​
1650
1651
1652 == 6.2 How to change the LoRa Frequency Bands/Region? ==
1653
1654
1655 User can follow the introduction for [[how to upgrade image>>||anchor="H6.1Howtoupgradetheimage3F"]]. When download the images, choose the required image file for download.
1656
1657
1658 == 6.3 How many RS485-Slave can RS485-LN connects? ==
1659
1660
1661 The RS485-LN can support max 32 RS485 devices. Each uplink command of RS485-LN can support max 16 different RS485 command. So RS485-LN 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>>||anchor="H3.3.3Configurereadcommandsforeachsampling"]].
1662
1663
1664 == 6.4 Compatible question to ChirpStack and TTI LoRaWAN server ? ==
1665
1666
1667 When user need to use with ChirpStack or TTI. Please set AT+RPL=4.
1668
1669 Detail info check this link: [[Set Packet Receiving Response Level>>doc:Main.End Device AT Commands and Downlink Command.WebHome||anchor="H7.23SetPacketReceivingResponseLevel"]]
1670
1671
1672 == 6.5 Can i use point to point communication for RS485-LN? ==
1673
1674
1675 Yes, please updating point-to-point [[firmware>>https://www.dropbox.com/sh/g99v0fxcltn9r1y/AACP33wo_ZQLsxW2MJ70oUoba/RS485-LN/Firmware?dl=0&subfolder_nav_tracking=1]],then refer [[Point to Point Communication for RS485-LN>>Point to Point Communication for RS485-LN]].
1676
1677
1678 == 6.6 How to Use RS485-LN  to connect to RS232 devices? ==
1679
1680
1681 [[Use RS485-BL or RS485-LN to connect to RS232 devices. - DRAGINO>>url:http://8.211.40.43:8080/xwiki/bin/view/Main/RS485%20to%20RS232/]]
1682
1683
1684 == 6.7 How to judge whether there is a problem with the set COMMAND ==
1685
1686 === 6.7.1 Introduce: ===
1687
1688
1689 Users can use below the structure to fast debug the communication between RS485BL and RS485-LN. The principle is to put the PC in the RS485 network and sniff the packet between Modbus MTU and RS485-BL/LN. We can use this way to:
1690
1691 1. Test if Modbus-MTU works with PC commands.
1692 1. Check if RS485-LN sent the expected command to Mobus-MTU
1693 1. Check if Modbus-MTU return back the expected result to RS485-LN.
1694 1. If both b) and c) has issue, we can compare PC’s output and RS485-LN output.
1695
1696 [[image:image-20221130104310-1.png||height="380" width="680"]]
1697
1698
1699 Example Connection:
1700
1701 [[image:image-20221130104310-2.png]]
1702
1703
1704 === 6.7.2 Set up PC to monitor RS485 network With Serial tool ===
1705
1706
1707 (% style="color:red" %)**Note: Receive and send set to hex mode**
1708
1709 [[image:image-20221130104310-3.png||height="616" width="714"]]
1710
1711
1712 === 6.7.3 With ModRSsim2: ===
1713
1714
1715 (% style="color:blue" %)**(1) Select serial port MODBUS RS-232**
1716
1717 [[image:image-20221130104310-4.png||height="390" width="865"]]
1718
1719
1720 (% style="color:blue" %)**(2) Click the serial port icon**
1721
1722 [[image:image-20221130104310-5.png||height="392" width="870"]]
1723
1724
1725 (% style="color:blue" %)**(3) After selecting the correct serial port and baud rate, click ok**
1726
1727 [[image:image-20221130104310-6.png]]
1728
1729
1730 (% style="color:blue" %)**(4) Click the comms.**
1731
1732 [[image:image-20221130104310-7.png||height="376" width="835"]]
1733
1734 (% class="wikigeneratedid" id="HRunRS485-LN2FBLcommandandmonitorifitiscorrect." %)
1735 **Run RS485-LN/BL command and monitor if it is correct.**
1736
1737
1738 === 6.7.4 Example – Test the CFGDEV command ===
1739
1740
1741 RS485-LN sent below command:
1742
1743 (% style="color:blue" %)**AT+CFGDEV=01 03 00 20 00 01,1**(%%) to RS485 network, and PC is able to get this command and return commands from MTU to show in the serial tool.
1744
1745
1746 We can see the output from the Serial port tool to analyze. And check if they are expected result.
1747
1748 [[image:image-20221130104310-8.png||height="214" width="797"]]
1749
1750
1751 We can also use (% style="color:blue" %)**ModRSsim2**(%%) to see the output.
1752
1753 [[image:image-20221130104310-9.png||height="531" width="729"]]
1754
1755
1756 === 6.7.5 Example – Test CMD command sets. ===
1757
1758
1759 Run (% style="color:blue" %)**AT+SENSORVALUE=1**(%%) to test the CMD commands set in RS485-LN.
1760
1761
1762 (% style="color:blue" %)**Serial port tool:**
1763
1764 [[image:image-20221130104310-10.png||height="339" width="844"]]
1765
1766
1767 (% style="color:blue" %)**ModRSsim2:**
1768
1769 [[image:image-20221130104310-11.png||height="281" width="962"]]
1770
1771
1772 === 6.7.6 Test with PC ===
1773
1774
1775 If there is still have problem to set up correctly the commands between RS485-LN and MTU. User can test the correct RS485 command set in PC and compare with the RS485 command sent out via RS485-LN. as long as both commands are the same, the MTU should return correct result.
1776
1777
1778 Or User can send the working commands set in PC serial tool to Dragino Support to check what should be configured in RS485-LN.
1779
1780 (% style="color:blue" %)**Connection method:**
1781
1782 [[image:image-20221130104310-12.png]]
1783
1784
1785 (% style="color:blue" %)**Link situation:**
1786
1787 [[image:image-20221130104310-13.png||height="458" width="486"]]
1788
1789
1790 [[image:image-20221130104310-14.png||height="371" width="823"]]
1791
1792
1793 == 6.8 Where to get the decoder for RS485-LN? ==
1794
1795
1796 The decoder for RS485-LN needs to be written by yourself. Because the sensor to which the user is connected is custom, the read device data bytes also need custom parsing, so there is no universal decoder. We can only provide [[templates>>https://github.com/dragino/dragino-end-node-decoder/tree/main/RS485-LN]] for decoders (no intermediate data parsing part involved)
1797
1798
1799 == 6.9 How to configure RS485 commands more conveniently? ==
1800
1801
1802 Dragino has developed an application for the RS485 series of products.
1803
1804 It can help you configure RS485 sensors more conveniently
1805 Please refer to the link below for specific usage:
1806
1807 [[RS485 Configure Tool - DRAGINO>>url:http://wiki.dragino.com/xwiki/bin/view/Main/RS485_Configure_Tool/#HTableofContentsFF1A]]
1808
1809
1810 = 7. Trouble Shooting =
1811
1812 == 7.1 Downlink doesn't work, how to solve it? ==
1813
1814
1815 Please see this link for debug: [[LoRaWAN Communication Debug>>doc:Main.LoRaWAN Communication Debug.WebHome]]
1816
1817
1818 == 7.2 Why I can't join TTN V3 in US915 /AU915 bands? ==
1819
1820
1821 It might about the channels mapping. Please see for detail: [[Notice of Frequency band>>doc:Main.LoRaWAN Communication Debug.WebHome||anchor="H2.NoticeofUS9152FCN4702FAU915Frequencyband"]]
1822
1823
1824 = 8. Order Info =
1825
1826
1827 (% style="color:blue" %)**Part Number: RS485-LN-XXX**
1828
1829 (% style="color:blue" %)**XXX:**
1830
1831 * (% style="color:red" %)**EU433**(%%):  frequency bands EU433
1832 * (% style="color:red" %)**EU868**(%%):  frequency bands EU868
1833 * (% style="color:red" %)**KR920**(%%):  frequency bands KR920
1834 * (% style="color:red" %)**CN470**(%%):  frequency bands CN470
1835 * (% style="color:red" %)**AS923**(%%):  frequency bands AS923
1836 * (% style="color:red" %)**AU915**(%%):  frequency bands AU915
1837 * (% style="color:red" %)**US915**(%%):  frequency bands US915
1838 * (% style="color:red" %)**IN865**(%%):  frequency bands IN865
1839 * (% style="color:red" %)**RU864**(%%):  frequency bands RU864
1840 * (% style="color:red" %)**KZ865**(%%):  frequency bands KZ865
1841
1842 = 9. Packing Info =
1843
1844
1845 **Package Includes**:
1846
1847 * RS485-LN x 1
1848 * Stick Antenna for LoRa RF part x 1
1849 * Program cable x 1
1850
1851 **Dimension and weight**:
1852
1853 * Device Size: 13.5 x 7 x 3 cm
1854 * Device Weight: 105g
1855 * Package Size / pcs : 14.5 x 8 x 5 cm
1856 * Weight / pcs : 170g
1857
1858 = 10. FCC Caution for RS485LN-US915 =
1859
1860
1861 (((
1862 Any Changes or modifications not expressly approved by the party responsible for compliance could void the user's authority to operate the equipment.
1863 )))
1864
1865 (((
1866 This device complies with part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) This device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation.
1867 )))
1868
1869 (((
1870
1871 )))
1872
1873 (((
1874 (% style="color:red" %)**IMPORTANT NOTE:**
1875 )))
1876
1877 (((
1878 (% style="color:red" %)**Note: **(%%)This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following measures:
1879 )))
1880
1881 (((
1882 —Reorient or relocate the receiving antenna.
1883 )))
1884
1885 (((
1886 —Increase the separation between the equipment and receiver.
1887 )))
1888
1889 (((
1890 —Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.
1891 )))
1892
1893 (((
1894 —Consult the dealer or an experienced radio/TV technician for help.
1895 )))
1896
1897 (((
1898
1899 )))
1900
1901 (((
1902 (% style="color:red" %)**FCC Radiation Exposure Statement:**
1903 )))
1904
1905 (((
1906 This equipment complies with FCC radiation exposure limits set forth for an uncontrolled environment.This equipment should be installed and operated with minimum distance 20cm between the radiator& your body.
1907 )))
1908
1909
1910 = 11. Support =
1911
1912
1913 * (((
1914 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.
1915 )))
1916 * (((
1917 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 [[support@dragino.com>>url:file:///D:/市场资料/说明书/LoRa/LT系列/support@dragino.com]].
1918
1919
1920
1921 )))
Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0