Skip to Content
Version 40.16 by Xiaoling on 2022/06/06 09:36
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 === 3.3.2 Configure sensors ===
326
327 (((
328 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**.
329 )))
330
331 (((
332 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.
333 )))
334
335 (% border="1" style="background-color:#ffffcc; color:green; width:806px" %)
336 |**AT Commands**|(% style="width:418px" %)**Description**|(% style="width:256px" %)**Example**
337 |AT+CFGDEV|(% style="width:418px" %)(((
338 This command is used to configure the RS485/TTL devices; they won’t be used during sampling.
339
340 AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,
341
342 mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
343 )))|(% style="width:256px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
344
345 Detail of AT+CFGDEV command see [[AT+CFGDEV detail>>||anchor="HRS485DebugCommand28AT2BCFGDEV29"]].
346
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 2）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
479 * Grab a section.
480
481 [[image:1653271648378-342.png||height="326" width="720"]]
482
483
484 * Grab different sections.
485
486 [[image:1653271657255-576.png||height="305" width="730"]]
487
488 (((
489 (% style="color:red" %)**Note:**
490 )))
491
492 (((
493 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.
494 )))
495
496 (((
497 **Example:**
498 )))
499
500 (((
501 (% style="color:red" %)AT+COMMAND1=11 01 1E D0,0
502 )))
503
504 (((
505 (% style="color:red" %)AT+SEARCH1=1,1E 56 34
506 )))
507
508 (((
509 (% style="color:red" %)AT+DATACUT1=0,2,1~~5
510 )))
511
512 (((
513 (% style="color:red" %)Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
514 )))
515
516 (((
517 (% style="color:red" %)String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
518 )))
519
520 (((
521 (% style="color:red" %)Valid payload after DataCUT command: 2e 30 58 5f 36
522 )))
523
524 [[image:1653271763403-806.png]]
525
526
527 === 3.3.4 Compose the uplink payload ===
528
529 (((
530 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.**
531 )))
532
533 (((
534 (% style="color:#037691" %)**Examples: AT+DATAUP=0**
535 )))
536
537 (((
538 Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**A SIGNLE UPLINK**.
539 )))
540
541 (((
542 Final Payload is
543 )))
544
545 (((
546 (% style="color:#4f81bd" %)**Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx**
547 )))
548
549 (((
550 Where PAYVER is defined by AT+PAYVER, below is an example screen shot.
551 )))
552
553 [[image:1653272787040-634.png||height="515" width="719"]]
554
555
556
557 (((
558 (% style="color:#037691" %)**Examples: AT+DATAUP=1**
559
560
561 )))
562
563 (((
564 Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**Multiply UPLINKs**.
565 )))
566
567 (((
568 Final Payload is
569 )))
570
571 (((
572 (% style="color:#4f81bd" %)**Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA**
573 )))
574
575 1. (((
576 Battery Info (2 bytes): Battery voltage
577 )))
578 1. (((
579 PAYVER (1 byte): Defined by AT+PAYVER
580 )))
581 1. (((
582 PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling.
583 )))
584 1. (((
585 PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
586 )))
587 1. (((
588 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
589 )))
590
591 [[image:1653272817147-600.png||height="437" width="717"]]
592
593 So totally there will be 3 uplinks for this sampling, each uplink includes 6 bytes DATA
594
595
596 DATA1=RETURN1 Valid Value = (% style="background-color:#4f81bd; color:white" %) 20 20 0a 33 90 41
597
598 DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= (% style="background-color:#4f81bd; color:white" %)02 aa 05 81 0a 20
599
600 DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 =(% style="background-color:#4f81bd; color:white" %) 20 20 20 2d 30
601
602
603 Below are the uplink payloads:
604
605 [[image:1653272901032-107.png]]
606
607
608 (% style="color:red" %)Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:
609
610 ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink ( so 51 -5 = 46 max valid date)
611
612 * For AU915/AS923 bands, if UplinkDwell time=1, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date).
613
614 * For US915 band, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date).
615
616 ~* For all other bands: max 51 bytes for each uplink  ( so 51 -5 = 46 max valid date).
617
618
619
620 === 3.3.5 Uplink on demand ===
621
622 (((
623 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.
624 )))
625
626 (((
627 Downlink control command:
628 )))
629
630 (((
631 **0x08 command**: Poll an uplink with current command set in RS485-BL.
632 )))
633
634 (((
635 **0xA8 command**: Send a command to RS485-BL and uplink the output from sensors.
636
637
638 )))
639
640 === 3.3.6 Uplink on Interrupt ===
641
642 Put the interrupt sensor between 3.3v_out and GPIO ext.
643
644 [[image:1653273818896-432.png]]
645
646
647 (((
648 AT+INTMOD=0  Disable Interrupt
649 )))
650
651 (((
652 AT+INTMOD=1  Interrupt trigger by rising or falling edge.
653 )))
654
655 (((
656 AT+INTMOD=2  Interrupt trigger by falling edge. ( Default Value)
657 )))
658
659 (((
660 AT+INTMOD=3  Interrupt trigger by rising edge.
661
662
663 )))
664
665 == 3.4 Uplink Payload ==
666
667 (% border="1" style="background-color:#4f81bd; color:white; width:850px" %)
668 |**Size(bytes)**|(% style="width:130px" %)**2**|(% style="width:93px" %)**1**|(% style="width:509px" %)**Length depends on the return from the commands**
669 |Value|(% style="width:130px" %)(((
670 (((
671 Battery(mV)
672 )))
673
674 (((
675 &
676 )))
677
678 (((
679 Interrupt _Flag
680 )))
681 )))|(% style="width:93px" %)(((
682 PAYLOAD_VER
683
684
685 )))|(% 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.
686
687 Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors.
688
689 (((
690 {{{function Decoder(bytes, port) {}}}
691 )))
692
693 (((
694 {{{//Payload Formats of RS485-BL Deceive}}}
695 )))
696
697 (((
698 {{{return {}}}
699 )))
700
701 (((
702 {{{ //Battery,units:V}}}
703 )))
704
705 (((
706 {{{ BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000,}}}
707 )))
708
709 (((
710 {{{ //GPIO_EXTI }}}
711 )))
712
713 (((
714 {{{ EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE",}}}
715 )))
716
717 (((
718 {{{ //payload of version}}}
719 )))
720
721 (((
722 {{{ Pay_ver:bytes[2],}}}
723 )))
724
725 (((
726 {{{ }; }}}
727 )))
728
729 (((
730 }
731
732
733 )))
734
735 (((
736 TTN V3 uplink screen shot.
737 )))
738
739 [[image:1653274001211-372.png||height="192" width="732"]]
740
741
742 == 3.5 Configure RS485-BL via AT or Downlink ==
743
744 User can configure RS485-BL via AT Commands or LoRaWAN Downlink Commands
745
746 There are two kinds of Commands:
747
748 * (% 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]]
749
750 * (% style="color:#4f81bd" %)**Sensor Related Commands**(%%): These commands are special designed for RS485-BL.  User can see these commands below:
751
752
753
754 === 3.5.1 Common Commands: ===
755
756 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]]
757
758
759 === 3.5.2 Sensor related commands: ===
760
761
762 ==== **Choose Device Type (RS485 or TTL)** ====
763
764 RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect.
765
766 * **AT Command**
767
768 (% class="box infomessage" %)
769 (((
770 **AT+MOD=1** ~/~/ Set to support RS485-MODBUS type sensors. User can connect multiply RS485 , Modbus sensors to the A / B pins.
771 )))
772
773 (% class="box infomessage" %)
774 (((
775 **AT+MOD=2** ~/~/ Set to support TTL Level sensors, User can connect one TTL Sensor to the TXD/RXD/GND pins.
776 )))
777
778
779 * **Downlink Payload**
780
781 **0A aa**  ~-~->  same as AT+MOD=aa
782
783
784
785 ==== **RS485 Debug Command (AT+CFGDEV)** ====
786
787 This command is used to configure the RS485 or TTL sensors; they won’t be used during sampling.
788
789 * **AT Command**
790
791 (% class="box infomessage" %)
792 (((
793 **AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m**
794 )))
795
796 m: 0: no CRC; 1: add CRC-16/MODBUS in the end of this command.
797
798
799 * **Downlink Payload**
800
801 Format: A8 MM NN XX XX XX XX YY
802
803 Where:
804
805 * MM: 1: add CRC-16/MODBUS ; 0: no CRC
806 * NN: The length of RS485 command
807 * XX XX XX XX: RS485 command total NN bytes
808 * 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
809
810 **Example 1:**
811
812 To connect a Modbus Alarm with below commands.
813
814 * 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.
815
816 * 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.
817
818 So if user want to use downlink command to control to RS485 Alarm, he can use:
819
820 (% style="color:#037691" %)**A8 01 06 0A 05 00 04 00 01 00**(%%): to activate the RS485 Alarm
821
822 (% style="color:#037691" %)**A8 01 06 0A 05 00 04 00 00 00**(%%): to deactivate the RS485 Alarm
823
824 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.
825
826
827 **Example 2:**
828
829 Check TTL Sensor return:
830
831 [[image:1654132684752-193.png]]
832
833
834
835
836 ==== **Set Payload version** ====
837
838 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.
839
840 * **AT Command:**
841
842 (% class="box infomessage" %)
843 (((
844 **AT+PAYVER: Set PAYVER field = 1**
845 )))
846
847
848 * **Downlink Payload:**
849
850 **0xAE 01**  ~-~-> Set PAYVER field =  0x01
851
852 **0xAE 0F**   ~-~-> Set PAYVER field =  0x0F
853
854
855
856 ==== **Set RS485 Sampling Commands** ====
857
858 AT+COMMANDx, AT+DATACUTx and AT+SEARCHx
859
860 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"]].
861
862
863 * **AT Command:**
864
865 (% class="box infomessage" %)
866 (((
867 **AT+COMMANDx: Configure RS485 read command to sensor.**
868 )))
869
870 (% class="box infomessage" %)
871 (((
872 **AT+DATACUTx: Configure how to handle return from RS485 devices.**
873 )))
874
875 (% class="box infomessage" %)
876 (((
877 **AT+SEARCHx: Configure search command**
878 )))
879
880
881 * **Downlink Payload:**
882
883 **0xAF** downlink command can be used to set AT+COMMANDx or AT+DATACUTx.
884
885 (% style="color:red" %)**Note**(%%): if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink.
886
887 Format: AF MM NN LL XX XX XX XX YY
888
889 Where:
890
891 * MM: the ATCOMMAND or AT+DATACUT to be set. Value from 01 ~~ 0F,
892 * NN:  0: no CRC; 1: add CRC-16/MODBUS ; 2: set the AT+DATACUT value.
893 * LL:  The length of AT+COMMAND or AT+DATACUT command
894 * XX XX XX XX: AT+COMMAND or AT+DATACUT command
895 * 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.
896
897 **Example:**
898
899 (% 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
900
901 (% 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**
902
903 (% 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**
904
905
906 **0xAB** downlink command can be used for set AT+SEARCHx
907
908 **Example:** **AB aa 01 03 xx xx xx** (03 here means there are total 3 bytes after 03) So
909
910 * AB aa 01 03 xx xx xx  same as AT+SEARCHaa=1,xx xx xx
911 * 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
912
913 **AB aa 02 03 xx xx xx 02 yy yy**  same as **AT+SEARCHaa=2,xx xx xx+yy yy**
914
915
916
917 ==== **Fast command to handle MODBUS device** ====
918
919 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]].
920
921 This command is valid since v1.3 firmware version
922
923
924 **AT+MBFUN has only two value:**
925
926 * **AT+MBFUN=1**: Enable Modbus reading. And get response base on the MODBUS return
927
928 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.
929
930 * **AT+MBFUN=0**: Disable Modbus fast reading.
931
932 **Example:**
933
934 * AT+MBFUN=1 and AT+DATACUT1/AT+DATACUT2 are not configure (0,0,0).
935 * 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.
936 * 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.
937
938 [[image:1654133913295-597.png]]
939
940
941 [[image:1654133954153-643.png]]
942
943
944 * **Downlink Commands:**
945
946 **A9 aa** ~-~-> Same as AT+MBFUN=aa
947
948
949
950 ==== **RS485 command timeout** ====
951
952 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.
953
954 Default value: 0, range:  0 ~~ 5 seconds
955
956
957 * **AT Command:**
958
959 (% class="box infomessage" %)
960 (((
961 **AT+CMDDLaa=hex(bb cc)**
962 )))
963
964 **Example:**
965
966 **AT+CMDDL1=1000** to send the open time to 1000ms
967
968
969 * **Downlink Payload:**
970
971 0x AA aa bb cc
972
973 Same as: AT+CMDDLaa=hex(bb cc)
974
975 **Example:**
976
977 **0xAA 01 03 E8**  ~-~-> Same as **AT+CMDDL1=1000 ms**
978
979
980
981 ==== **Uplink payload mode** ====
982
983 Define to use one uplink or multiple uplinks for the sampling.
984
985 The use of this command please see: [[Compose Uplink payload>>||anchor="H3.3.4Composetheuplinkpayload"]]
986
987 * **AT Command:**
988
989 (% class="box infomessage" %)
990 (((
991 **AT+DATAUP=0**
992 )))
993
994 (% class="box infomessage" %)
995 (((
996 **AT+DATAUP=1**
997 )))
998
999
1000 * **Downlink Payload:**
1001
1002 **0xAD 00**  **~-~->** Same as AT+DATAUP=0
1003
1004 **0xAD 01**  **~-~->** Same as AT+DATAUP=1
1005
1006
1007
1008 ==== **Manually trigger an Uplink** ====
1009
1010 Ask device to send an uplink immediately.
1011
1012 * **Downlink Payload:**
1013
1014 **0x08 FF**, RS485-BL will immediately send an uplink.
1015
1016
1017
1018 ==== **Clear RS485 Command** ====
1019
1020 The AT+COMMANDx and AT+DATACUTx settings are stored in special location, user can use below command to clear them.
1021
1022
1023 * **AT Command:**
1024
1025 (% 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
1026
1027 Example screen shot after clear all RS485 commands. 
1028
1029
1030 The uplink screen shot is:
1031
1032 [[image:1654134704555-320.png]]
1033
1034
1035 * **Downlink Payload:**
1036
1037 **0x09 aa bb** same as AT+CMDEAR=aa,bb
1038
1039
1040
1041 ==== **Set Serial Communication Parameters** ====
1042
1043 Set the Rs485 serial communication parameters:
1044
1045 * **AT Command:**
1046
1047 Set Baud Rate:
1048
1049 (% class="box infomessage" %)
1050 (((
1051 **AT+BAUDR=9600**    ~/~/ Options: (1200,2400,4800,14400,19200,115200)
1052 )))
1053
1054 Set UART Parity
1055
1056 (% class="box infomessage" %)
1057 (((
1058 **AT+PARITY=0**    ~/~/ Option: 0: no parity, 1: odd parity, 2: even parity
1059 )))
1060
1061 Set STOPBIT
1062
1063 (% class="box infomessage" %)
1064 (((
1065 **AT+STOPBIT=0**    ~/~/ Option: 0 for 1bit; 1 for 1.5 bit ; 2 for 2 bits
1066 )))
1067
1068
1069 * **Downlink Payload:**
1070
1071 **A7 01 aa bb**: Same  AT+BAUDR=hex(aa bb)*100
1072
1073 **Example:**
1074
1075 * A7 01 00 60   same as AT+BAUDR=9600
1076 * A7 01 04 80  same as AT+BAUDR=115200
1077
1078 A7 02 aa: Same as  AT+PARITY=aa  (aa value: 00 , 01 or 02)
1079
1080 A7 03 aa: Same as  AT+STOPBIT=aa  (aa value: 00 , 01 or 02)
1081
1082
1083
1084 ==== **Control output power duration** ====
1085
1086 User can set the output power duration before each sampling.
1087
1088 * **AT Command:**
1089
1090 **Example:**
1091
1092 **AT+3V3T=1000**  ~/~/ 3V3 output power will open 1s before each sampling.
1093
1094 **AT+5VT=1000**  ~/~/ +5V output power will open 1s before each sampling.
1095
1096
1097 * **LoRaWAN Downlink Command:**
1098
1099 **07 01 aa bb**  Same as AT+5VT=(aa bb)
1100
1101 **07 02 aa bb**  Same as AT+3V3T=(aa bb)
1102
1103
1104 == 3.6 Buttons ==
1105
1106 (% border="1" style="background-color:#ffffcc; color:green; width:233px" %)
1107 |=(% style="width: 89px;" %)**Button**|=(% style="width: 141px;" %)**Feature**
1108 |(% style="width:89px" %)**RST**|(% style="width:141px" %)Reboot RS485-BL
1109
1110
1111
1112 == 3.7 +3V3 Output ==
1113
1114 RS485-BL has a Controllable +3V3 output, user can use this output to power external sensor.
1115
1116 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. 
1117
1118 The +3V3 output time can be controlled by AT Command.
1119
1120
1121 (% style="color:#037691" %)**AT+3V3T=1000**
1122
1123
1124 Means set +3v3 valid time to have 1000ms. So, the real +3v3 output will actually have 1000ms + sampling time for other sensors.
1125
1126 By default, the AT+3V3T=0. This is a special case, means the +3V3 output is always on at any time
1127
1128
1129 == 3.8 +5V Output ==
1130
1131 RS485-BL has a Controllable +5V output, user can use this output to power external sensor.
1132
1133 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. 
1134
1135 The 5V output time can be controlled by AT Command.
1136
1137
1138 (% style="color:#037691" %)**AT+5VT=1000**
1139
1140
1141 Means set 5V valid time to have 1000ms. So, the real 5V output will actually have 1000ms + sampling time for other sensors.
1142
1143 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.
1144
1145
1146 == 3.9 LEDs ==
1147
1148 (% border="1" style="background-color:#ffffcc; color:green; width:332px" %)
1149 |=**LEDs**|=(% style="width: 274px;" %)**Feature**
1150 |**LED1**|(% style="width:274px" %)Blink when device transmit a packet.
1151
1152
1153
1154 == 3.10 Switch Jumper ==
1155
1156 (% border="1" style="background-color:#ffffcc; color:green; width:515px" %)
1157 |=(% style="width: 124px;" %)**Switch Jumper**|=(% style="width: 388px;" %)**Feature**
1158 |(% style="width:124px" %)**SW1**|(% style="width:388px" %)(((
1159 ISP position: Upgrade firmware via UART
1160
1161 Flash position: Configure device, check running status.
1162 )))
1163 |(% style="width:124px" %)**SW2**|(% style="width:388px" %)(((
1164 5V position: set to compatible with 5v I/O.
1165
1166 3.3v position: set to compatible with 3.3v I/O.,
1167 )))
1168
1169 **+3.3V**: is always ON
1170
1171 **+5V**: Only open before every sampling. The time is by default, it is AT+5VT=0.  Max open time. 5000 ms.
1172
1173
1174 = 4. Case Study =
1175
1176 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]]
1177
1178
1179 = 5. Use AT Command =
1180
1181 == 5.1 Access AT Command ==
1182
1183 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.
1184
1185 [[image:1654135840598-282.png]]
1186
1187
1188 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:
1189
1190 [[image:1654136105500-922.png]]
1191
1192
1193 More detail AT Command manual can be found at [[AT Command Manual>>||anchor="3.5ConfigureRS485-BLviaATorDownlink"]]
1194
1195
1196 == 5.2 Common AT Command Sequence ==
1197
1198 === 5.2.1 Multi-channel ABP mode (Use with SX1301/LG308) ===
1199
1200 If device has not joined network yet:
1201
1202 (% class="box infomessage" %)
1203 (((
1204 **AT+FDR**
1205 )))
1206
1207 (% class="box infomessage" %)
1208 (((
1209 **AT+NJM=0**
1210 )))
1211
1212 (% class="box infomessage" %)
1213 (((
1214 **ATZ**
1215 )))
1216
1217
1218 If device already joined network:
1219
1220 (% class="box infomessage" %)
1221 (((
1222 **AT+NJM=0**
1223 )))
1224
1225 (% class="box infomessage" %)
1226 (((
1227 **ATZ**
1228 )))
1229
1230
1231 === 5.5.2 Single-channel ABP mode (Use with LG01/LG02) ===
1232
1233
1234 (% style="background-color:#dcdcdc" %)**AT+FDR** (%%) Reset Parameters to Factory Default, Keys Reserve
1235
1236 (% style="background-color:#dcdcdc" %)**AT+NJM=0 **(%%)Set to ABP mode
1237
1238 (% style="background-color:#dcdcdc" %)**AT+ADR=0** (%%)Set the Adaptive Data Rate Off
1239
1240 (% style="background-color:#dcdcdc" %)**AT+DR=5**  (%%)Set Data Rate
1241
1242 (% style="background-color:#dcdcdc" %)**AT+TDC=60000** (%%) Set transmit interval to 60 seconds
1243
1244 (% style="background-color:#dcdcdc" %)**AT+CHS=868400000**(%%) Set transmit frequency to 868.4Mhz
1245
1246 (% style="background-color:#dcdcdc" %)**AT+RX2FQ=868400000** (%%) Set RX2Frequency to 868.4Mhz (according to the result from server)
1247
1248 (% style="background-color:#dcdcdc" %)**AT+RX2DR=5**  (%%) Set RX2DR to match the downlink DR from server. see below
1249
1250 (% 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.
1251
1252 (% style="background-color:#dcdcdc" %)**ATZ**       (%%) Reset MCU
1253
1254
1255 (% style="color:red" %)**Note:**
1256
1257 (% style="color:red" %)1. Make sure the device is set to ABP mode in the IoT Server.
1258 2. Make sure the LG01/02 gateway RX frequency is exactly the same as AT+CHS setting.
1259 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.
1260 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
1261
1262 [[image:1654136435598-589.png]]
1263
1264
1265 = 6. FAQ =
1266
1267 == 6.1 How to upgrade the image? ==
1268
1269 The RS485-BL LoRaWAN Controller is shipped with a 3.5mm cable, the cable is used to upload image to RS485-BL to:
1270
1271 * Support new features
1272 * For bug fix
1273 * Change LoRaWAN bands.
1274
1275 Below shows the hardware connection for how to upload an image to RS485-BL:
1276
1277 [[image:1654136646995-976.png]]
1278
1279 **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]].
1280
1281 **Step2**: Download the [[LT Image files>>url:http://www.dragino.com/downloads/index.php?dir=LT_LoRa_IO_Controller/LT33222-L/image/]].
1282
1283 **Step3: **Open flashloader; choose the correct COM port to update.
1284
1285 [[image:image-20220602102605-1.png]]
1286
1287
1288 [[image:image-20220602102637-2.png]]
1289
1290
1291 [[image:image-20220602102715-3.png]]
1292
1293
1294
1295 == 6.2 How to change the LoRa Frequency Bands/Region? ==
1296
1297 User can follow the introduction for [[how to upgrade image>>||anchor="H6.1Howtoupgradetheimage3F"]]. When download the images, choose the required image file for download.
1298
1299
1300
1301 == 6.3 How many RS485-Slave can RS485-BL connects? ==
1302
1303 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"]].
1304
1305
1306
1307 = 7. Trouble Shooting =
1308
1309
1310 == 7.1 Downlink doesn’t work, how to solve it? ==
1311
1312 Please see this link for debug: [[LoRaWAN Communication Debug>>doc:Main.LoRaWAN Communication Debug.WebHome]]
1313
1314
1315 == 7.2 Why I can’t join TTN V3 in US915 /AU915 bands? ==
1316
1317 It might about the channels mapping. Please see for detail: [[Notice of Frequency band>>doc:Main.LoRaWAN Communication Debug.WebHome||anchor="H2.NoticeofUS9152FCN4702FAU915Frequencyband"]]
1318
1319
1320 = 8. Order Info =
1321
1322 (% style="color:blue" %)**Part Number: RS485-BL-XXX**
1323
1324 (% style="color:blue" %)**XXX:**
1325
1326 * (% style="color:blue" %)**EU433**(%%): frequency bands EU433
1327 * (% style="color:blue" %)**EU868**(%%): frequency bands EU868
1328 * (% style="color:blue" %)**KR920**(%%): frequency bands KR920
1329 * (% style="color:blue" %)**CN470**(%%): frequency bands CN470
1330 * (% style="color:blue" %)**AS923**(%%): frequency bands AS923
1331 * (% style="color:blue" %)**AU915**(%%): frequency bands AU915
1332 * (% style="color:blue" %)**US915**(%%): frequency bands US915
1333 * (% style="color:blue" %)**IN865**(%%): frequency bands IN865
1334 * (% style="color:blue" %)**RU864**(%%): frequency bands RU864
1335 * (% style="color:blue" %)**KZ865**(%%): frequency bands KZ865
1336
1337
1338 = 9. Packing Info =
1339
1340 (((
1341 **Package Includes**:
1342 )))
1343
1344 * (((
1345 RS485-BL x 1
1346 )))
1347 * (((
1348 Stick Antenna for LoRa RF part x 1
1349 )))
1350 * (((
1351 Program cable x 1
1352 )))
1353
1354 (((
1355 **Dimension and weight**:
1356 )))
1357
1358 * (((
1359 Device Size: 13.5 x 7 x 3 cm
1360 )))
1361 * (((
1362 Device Weight: 105g
1363 )))
1364 * (((
1365 Package Size / pcs : 14.5 x 8 x 5 cm
1366 )))
1367 * (((
1368 Weight / pcs : 170g
1369
1370
1371 )))
1372
1373 = 10. Support =
1374
1375 * 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.
1376 * 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]]