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