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