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