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