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