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