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