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