Version 135.2 by Xiaoling on 2024/09/28 10:44

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