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