Show last authors
1 (% style="text-align:center" %)
2 [[image:image-20230203113613-1.png]]
3
4
5
6
7 **Table of Contents:**
8
9
10
11
12
13
14
15
16
17 = 1.  Introduction =
18
19 == 1.1 ​ What is LMDS120 Microwave Radar DistanceSensor ==
20
21
22 (((
23 The Dragino LMDS120 is a LoRaWAN Microwave Radar distance sensor. It uses use Microwave Radar to detect the distance between sensor and different objects. Different from ultrosonic or Lidar measurement. Microwave Radar is more reliable for condensation / dusty environment. It can sense correct distance even there is water or think dust on top of the sensor.
24
25 The LMDS120 can be applied to scenarios such as horizontal distance measurement, parking management system, object proximity and presence detection, intelligent trash can management system, robot obstacle avoidance, automatic control, sewer, etc.
26
27 The LoRa wireless technology used in LMDS120 allows device to send data and reach extremely long ranges at low data-rates. It provides ultra-long range spread spectrum communication and high interference immunity whilst minimizing current consumption.
28
29 LMDS120 is powered by 8500mAh Li-SOCI2 battery, it is designed for long term use up to 5 years.
30
31 Each LMDS120 is pre-load with a set of unique keys for LoRaWAN registrations, register these keys to local LoRaWAN server and it will auto connect after power on.
32 )))
33
34
35 [[image:image-20230203114147-2.png]]
36
37
38 == ​1.2  Features ==
39
40
41 * LoRaWAN 1.0.3 Class A
42 * Ultra-low power consumption
43 * 60Ghz Microwave Radar for distance detection
44 * Monitor Battery Level
45 * Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/IN865
46 * AT Commands to change parameters
47 * Uplink on periodically
48 * Downlink to change configure
49 * 8500mAh Battery for long term use
50 * Wall Mountable
51 * Outdoor Use
52
53 == 1.3  Radar probe specification ==
54
55
56 * Measuring Method: FMCW
57 * Frequency: 60 GHz
58 * Measure Range : 15cm ~~ 1200cm
59 * Accuracy:± (3mm + S*02%). S: Measure Value
60 * Resolution: 0.01m
61 * Measurement Angle : 25 degrees horizontal and 23 degrees vertical
62
63 == 1.4  Storage & Operation Temperature ==
64
65
66 -15°C to +65°C
67
68
69 == 1.5 ​ Applications ==
70
71
72 * Horizontal distance measurement
73 * Liquid level measurement
74 * Parking management system
75 * Object proximity and presence detection
76 * Intelligent trash can management system
77 * Robot obstacle avoidance
78 * Automatic control
79 * Sewer
80 * Bottom water level monitoring
81
82
83 == 1.6  Pin mapping and power on ==
84
85
86 [[image:1655257026882-201.png]]
87
88 (% style="display:none" %) (%%)
89
90 = 2.  Operation Mode =
91
92 == 2.1  How it works ==
93
94
95 (((
96 Each LMDS120 is shipped with a worldwide unique set of OTAA keys. To use LMDS120 in a LoRaWAN network, user needs to input the OTAA keys in the LoRaWAN network server. So LMDS120 can join the LoRaWAN network and start to transmit sensor data.
97 )))
98
99
100 == 2.2  ​Example to use for LoRaWAN network ==
101
102
103 (((
104 Following is an example for how to join the [[TTN v3 LoRaWAN Network>>url:https://console.cloud.thethings.network/]]. Below is the network structure; we use the [[LG308>>url:http://www.dragino.com/products/lora/item/140-lg308.html]] as a LoRaWAN gateway in this example.
105 )))
106
107 (((
108 [[image:image-20230203115545-3.png]]
109
110 * In this user case, the LMDS120 is installed on top of river to detect the water level and send the level info to the LoRaWAN server. The LMDS120 will uplink different types of messages to the LoRaWAN server. See [[Uplink payload>>path:#Uplink_Payload]] for detail.
111 )))
112
113 (((
114 Assume the LoRaWAN Gateway DLOS8 is already set to connect to the [[TTN V3 network >>url:https://eu1.cloud.thethings.network]]. We need to add the LMDS120 device in TTN V3:
115 )))
116
117 (((
118 (((
119
120 )))
121
122 (((
123 (% style="color:blue" %)**Step 1**(%%): Create a device in TTN with the OTAA keys from LMDS120.
124 )))
125 )))
126
127 (((
128 (((
129 Each LMDS120 is shipped with a sticker with the default device keys, user can find this sticker in the box. it looks like below.
130
131 [[image:1655278302970-688.png]]
132
133
134 )))
135 )))
136
137 Users can enter these keys in the LoRaWAN Server portal. Below is the TTN V3 screenshot:
138
139 __**Add APP EUI**__ in the application.
140
141
142 [[image:image-20220610161353-4.png]]
143
144
145 [[image:image-20220610161353-5.png]]
146
147
148 [[image:image-20220610161353-6.png]]
149
150
151 [[image:image-20220610161353-7.png]]
152
153
154
155 You can also choose to create the device manually.
156
157 [[image:image-20220610161538-8.png]]
158
159
160
161 **Add APP KEY and DEV EUI**
162
163 [[image:1655278497961-944.png]]
164
165
166 (% style="color:blue" %)**Step 2**(%%):  Power on LMDS120
167
168
169 Put a Jumper on JP2 to power on the device. ( The Switch must be in FLASH position).
170
171 [[image:1655278589727-228.png]]
172
173 (((
174 Put the jumper to power on LMDS120 and it will auto-join to the TTN V3 network. After join success, it will start to upload sensor data to TTN V3 and the user can see it in the panel.
175 )))
176
177
178 == 2.3  ​Uplink Payload ==
179
180
181 Uplink payloads have two types:
182
183 * Distance Value: Use FPORT=2
184 * Other control commands: Use other FPORT fields.
185
186 The application server should parse the correct value based on FPORT settings.
187
188
189 === 2.3.1  Device Status, FPORT~=5 ===
190
191
192 (((
193 Include device configure status. Once LMDS120 Joined the network, it will uplink this message to the server.
194 )))
195
196 (((
197 Users can also use the downlink command (0x26 01) to ask LMDS120 to resend Device Status.
198 )))
199
200 (% border="1" cellspacing="4" style="background-color:#f7faff; color:black; width:510px" %)
201 |(% colspan="6" %)**Device Status (FPORT=5)**
202 |(% style="width:103px" %)**Size (bytes)**|(% style="width:72px" %)**1**|**2**|(% style="width:91px" %)**1**|(% style="width:86px" %)**1**|(% style="width:44px" %)**2**
203 |(% style="width:103px" %)**Value**|(% style="width:72px" %)Sensor Model|Firmware Version|(% style="width:91px" %)Frequency Band|(% style="width:86px" %)Sub-band|(% style="width:44px" %)BAT
204
205 [[image:image-20230203133803-4.png]]
206
207
208 * (% style="color:#037691" %)**Sensor Model**(%%)**:** For LMDS120, this value is 0x18
209
210 * (% style="color:#037691" %)**Firmware Version**(%%)**:** 0x0100, Means: v1.0.0 version
211
212 * (% style="color:#037691" %)**Frequency Band**(%%)**:**
213
214 *0x01: EU868
215
216 *0x02: US915
217
218 *0x03: IN865
219
220 *0x04: AU915
221
222 *0x05: KZ865
223
224 *0x06: RU864
225
226 *0x07: AS923
227
228 *0x08: AS923-1
229
230 *0x09: AS923-2
231
232 *0x0a: AS923-3
233
234 *0x0b: AS923-3
235
236
237
238 * (% style="color:#037691" %)**Sub-Band**(%%)**:**
239 ** AU915 and US915:value 0x00 ~~ 0x08
240 ** CN470: value 0x0B ~~ 0x0C
241 ** Other Bands: Always 0x00
242
243
244
245
246 === 2.3.2  Distance, Uplink FPORT~=2 ===
247
248
249 LMDS120 will send this uplink **after** Device Status once join the LoRaWAN network successfully. And LMDS120 will:
250
251 1. periodically send this uplink every 20 minute (TDC time), this interval [[can be changed>>||anchor="H3.1A0SetTransmitIntervalTime280x0129"]].
252 1. send this uplink while there is [[interrupt event>>||anchor="H3.5A0SetInterruptMode280x0629"]].
253
254 Uplink Payload totals 11 bytes.
255
256
257 (% border="1" cellspacing="4" style="background-color:#ffffcc; width:370px" %)
258 |=(% colspan="6" style="width: 367px;" %)**Distance Value, FPORT=2**
259 |(% style="width:72px" %)**Size(bytes)**|(% style="width:43px" %)**2**|(% style="width:76px" %)**2**|(% style="width:76px" %)**1**|(% style="width:75px" %)**2**|(% style="width:75px" %)**1**
260 |(% style="width:72px" %)**Value**|(% style="width:43px" %)[[BAT>>||anchor="H2.3.1A0DeviceStatus2CFPORT3D5"]]|(% style="width:76px" %)Distance|(% style="width:76px" %)interrupt|(% style="width:75px" %)DS18B20 temperature|(% style="width:75px" %)Sensor flag
261
262
263 [[image:image-20230203142732-5.png]]
264
265
266
267 (((
268 (% style="color:#037691" %)**Distance:**
269 )))
270
271 (((
272 Distance between sensor probe to the first object. (unit: cm)
273 )))
274
275 (((
276 For example, if the data you get from the register is __0x0D 0xC6__, the distance between the sensor and the measured object is(% style="color:#037691" %)** 0DC6(H) = 115 (D) = 115 cm.**
277 )))
278
279
280 (((
281 (% style="color:red" %)**Notice: The distance has a special value :**
282 )))
283
284 * (((
285 **0x3FFF**: Reading Invalid (exceed the valid range of the probe) or Probe not detected
286 )))
287
288 (((
289
290 )))
291
292 (((
293
294 )))
295
296
297
298 === 2.3.3  Decoder in TTN V3 ===
299
300
301 [[image:1655261164557-670.png]]
302
303 (((
304 (((
305 Please check the decoder from this link: [[https:~~/~~/github.com/dragino/dragino-end-node-decoder>>https://github.com/dragino/dragino-end-node-decoder]]
306
307
308 )))
309 )))
310
311 == 2.4  ​Show data on Datacake ==
312
313
314 (((
315 Datacake IoT platform provides a human-friendly interface to show the sensor data, once we have sensor data in TTN V3, we can use Datacake to connect to TTN V3 and see the data in Datacake. Below are the steps:
316
317
318 )))
319
320 (((
321 (% style="color:blue" %)**Step 1**(%%)**: **Link TTNv3 to [[DATACAKE>>url:https://datacake.co/]]
322 )))
323
324 (((
325 (% style="color:blue" %)**Step 2**(%%)**: **Configure LMDS200 in Datacake
326 )))
327
328
329 [[image:image-20220615163646-6.png]]
330
331
332 [[image:image-20220615163646-7.png]]
333
334
335 [[image:image-20220615163646-8.png]]
336
337
338 [[image:image-20220615163646-9.png||height="392" width="1211"]]
339
340
341 [[image:image-20220615163646-10.png]]
342
343 (% style="display:none" %) (%%)
344
345 [[image:image-20220615163646-11.png||height="434" width="1206"]](% style="display:none" %)
346
347
348 [[image:image-20220615163646-12.png||height="357" width="1202"]](% style="display:none" %)
349
350 (% style="display:none" %) (%%)
351
352 [[image:image-20220615163646-13.png]](% style="display:none" %)
353
354
355 [[image:image-20220615163646-14.png]]
356
357
358 [[image:image-20220615163646-15.png]](% style="display:none" %)
359
360
361 = 3.  Configure LMDS200 via AT Command or LoRaWAN Downlink =
362
363
364 (((
365 (((
366 Use can configure LMDS200 via AT Command or LoRaWAN Downlink.
367 )))
368 )))
369
370 * (((
371 (((
372 AT Command Connection: See [[FAQ>>||anchor="H5.A0FAQ"]].
373 )))
374 )))
375 * (((
376 (((
377 LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>doc:Main.WebHome]]
378 )))
379 )))
380
381 (((
382 (((
383
384 )))
385
386 (((
387 There are two kinds of commands to configure LMDS200, they are:
388 )))
389 )))
390
391 * (((
392 (((
393 (% style="color:#4f81bd" %)** General Commands**.
394 )))
395 )))
396
397 (((
398 (((
399 These commands are to configure:
400 )))
401 )))
402
403 * (((
404 (((
405 General system settings like: uplink interval.
406 )))
407 )))
408 * (((
409 (((
410 LoRaWAN protocol & radio related command.
411 )))
412 )))
413
414 (((
415 (((
416 They are same for all Dragino Device which support DLWS-005 LoRaWAN Stack**(Note~*~*)**. These commands can be found on the wiki: [[End Device AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]
417 )))
418 )))
419
420 (((
421 (((
422
423 )))
424 )))
425
426 * (((
427 (((
428 (% style="color:#4f81bd" %)** Commands special design for LMDS200**
429 )))
430 )))
431
432 (((
433 (((
434 These commands only valid for LMDS200, as below:
435 )))
436 )))
437
438
439 == 3.1  Set Transmit Interval Time(0x01) ==
440
441
442 Feature: Change LoRaWAN End Node Transmit Interval.
443
444 (% style="color:#037691" %)**AT Command: AT+TDC**
445
446 (% aria-label="image-20220610173409-7.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:image-20220610173409-7.png||data-widget="image"]](% title="Click and drag to resize" %)​(% aria-label="Data URI image image widget" contenteditable="false" role="region" style="background-image:url(http://wiki1.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" tabindex="-1" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||data-widget="image" draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% aria-label="Data URI image image widget" contenteditable="false" role="region" style="background-image:url(http://wiki1.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220, 220, 220, 0.5); display:none" tabindex="-1" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% aria-label="Data URI image image widget" contenteditable="false" role="region" style="background-image:url(http://wiki1.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" tabindex="-1" title="Click and drag to resize" %)​(% title="Click and drag to resize" %)​
447
448
449 (((
450 (% style="color:#037691" %)**Downlink Command: 0x01**
451 )))
452
453 (((
454 (((
455 Format: Command Code (0x01) followed by 3 bytes time value.
456
457 (((
458 If the downlink payload=0100003C, it means set the END Node's Transmit Interval to 0x00003C=60(S), while type code is 01.
459 )))
460
461 * Example 1: Downlink Payload: 0100001E ~/~/ Set Transmit Interval (TDC) = 30 seconds
462 * Example 2: Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds
463 )))
464 )))
465
466
467
468 == 3.2 Set Alarm Transmit Interval Time(0x0D) ==
469
470
471 Feature: Change LoRaWAN End Node Alarm Transmit Interval. Default Value: 1 minute
472
473 (% style="color:#037691" %)**AT Command: AT+ATDC**
474
475 [[image:image-20220615175212-2.png]]
476
477
478 (% style="color:#037691" %)**Downlink Command: 0x0D**
479
480 Format: Command Code (0x0D) followed by 1 byte for time value.
481
482 If the downlink payload=0D02, it means set the END Node's Alarm Transmit Interval to 2 minutes, while type code is 0D.
483
484
485 == 3.3 Set Alarm Distance (0xA2) ==
486
487
488 LMDS02 supports Alarm Feature, when LMDS02 detect the distance exceed the alarm settings, LMDS02 will Enter Alarm Mode and use the [[ATDC interval>>path:#Alarm_Interval]] (default is 1 minute) to uplink Distance value. Alarm mode will last for 60 uplinks (default 1 hour) and can be close by downlink command 0xA300.
489
490 (% style="color:red" %)**Note: Alarm mode only valid for the Distance 1(the Closest Object)**
491
492
493 User can set Alarm Distance to enable/disable Alarm Mode.
494
495 (% style="color:#037691" %)**AT+ALARMC=AABBCCDD**
496
497 * AABB: Hex value for Alarm low threshold, CCDD: Hex value for Alarm high threshold
498 * When 0xAABB=0, and 0xCCDD≠0, Alarm trigger when higher than max
499 * When 0xAABB≠0, and 0xCCDD =0xFFFF, Alarm trigger when lower than min
500 * When 0xAABB≠0 and 0xCCDD≠0, Alarm trigger when higher than max or lower than min
501
502 **Example:**
503
504 AT+ALARMC=006400C8   ~/~/ Alarm when < 100 or higher than 200.
505
506
507 * (% style="color:#037691" %)**Downlink Payload:**
508
509 0x(A2 00 01 00 00)  ~/~/ Same as AT+ALARMC=00010000
510
511
512 == 3.4 Enter/Exit Alarm Mode (0xA3) ==
513
514
515 Feature: Enter/Exit Alarm mode:
516
517 (% style="color:#037691" %)**AT Command: AT+ALARM=0(Exit Alarm Mode or AT+ALARM=1 (Enter Alarm Mode)**
518
519
520 (% style="color:#037691" %)**Downlink Command:**
521
522 0xA3 00  ~/~/ Exit Alarm Mode. 
523
524 0xA3 01  ~/~/ Enter Alarm Mode. Enter Alarm mode will use ATDC interval in the next 59 uplinks.
525
526
527 == 3.5  Set Interrupt Mode(0x06) ==
528
529
530 (((
531 Feature, Set Interrupt mode for GPIO_EXIT.
532 )))
533
534 (((
535 (% style="color:#037691" %)**Downlink Command: AT+INTMOD**
536 )))
537
538 [[image:image-20220610174917-9.png]]
539
540
541 (((
542 (((
543 (% style="color:#037691" %)**Downlink Command: 0x06**
544 )))
545 )))
546
547 (((
548 (((
549 Format: Command Code (0x06) followed by 3 bytes.
550 )))
551 )))
552
553 (((
554 (((
555 (((
556 This means that the interrupt mode of the end node is set to 0x000003=3 (rising edge trigger), and the type code is 06.
557 )))
558 )))
559 )))
560
561 * (((
562 (((
563 Example 1: Downlink Payload: 06000000  ~/~/ Turn off interrupt mode
564 )))
565 )))
566 * (((
567 (((
568 Example 2: Downlink Payload: 06000003  ~/~/ Set the interrupt mode to rising edge trigger
569 )))
570 )))
571
572 (((
573
574
575
576 = 4.  Battery & how to replace =
577
578 == 4.1  Battery Type ==
579
580
581 (((
582 (((
583 LMDS200 is equipped with a [[8500mAH ER26500 Li-SOCI2 battery>>url:https://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]. The battery is un-rechargeable battery with low discharge rate targeting for 8~~10 years use. This type of battery is commonly used in IoT target for long-term running, such as water meter.
584 )))
585
586 (((
587 The discharge curve is not linear so can't simply use percentage to show the battery level. Below is the battery performance.
588
589
590 )))
591
592 [[image:image-20220615165029-16.png||height="645" width="908"]]
593
594
595 Minimum Working Voltage for the LMDS200:
596
597 LMDS200:  2.45v ~~ 3.6v
598 )))
599
600
601 == 4.2  Replace Battery ==
602
603
604 Any battery with range 2.45 ~~ 3.6v can be a replacement. We recommend to use Li-SOCl2 Battery.
605
606 And make sure the positive and negative pins match.
607
608
609 == 4.3  Power Consumption Analyze ==
610
611
612 Dragino Battery powered product are all runs in Low Power mode. We have an update battery calculator which base on the measurement of the real device. User can use this calculator to check the battery life and calculate the battery life if want to use different transmit interval.
613
614 Instruction to use as below:
615
616
617 (% style="color:blue" %)**Step 1**(%%)**: **Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from:
618
619 [[https:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/]]
620
621
622 (% style="color:blue" %)**Step 2**(%%)**:** Open it and choose
623
624 * Product Model
625 * Uplink Interval
626 * Working Mode
627
628 And the Life expectation in difference case will be shown on the right.
629
630 [[image:image-20220615165329-17.png||height="388" width="1201"]]
631
632
633 (((
634 (% id="cke_bm_628908S" style="display:none" %) (%%)The battery related documents as below:
635 )))
636
637 * (((
638 [[Battery Dimension>>https://www.dragino.com/downloads/index.php?dir=datasheet/Battery/]]
639 )))
640 * (((
641 [[Lithium-Thionyl Chloride Battery  datasheet>>https://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]](% style="display:none" %)
642 )))
643 * (((
644 [[Lithium-ion Battery-Capacitor datasheet>>https://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
645 )))
646
647 [[image:image-20220615111024-1.png]]
648
649
650 === 4.3.1  Battery Note ===
651
652
653 The Li-SICO battery is designed for small current / long period application. It is not good to use a high current, short period transmit method. The recommended minimum period for use of this battery is 5 minutes. If you use a shorter period time to transmit LoRa, then the battery life may be decreased.
654
655
656 === 4.3.2  Replace the battery ===
657
658
659 (((
660 You can change the battery in the LMDS200.The type of battery is not limited as long as the output is between 3v to 3.6v. 
661 )))
662
663 (((
664 The default battery pack of LMDS200 includes a ER26500 plus super capacitor. If user can't find this pack locally, they can find ER26500 or equivalence, which will also work in most case. The SPC can enlarge the battery life for high frequency use (update period below 5 minutes).
665 )))
666
667
668 )))
669
670 = 5.  FAQ =
671
672 == 5.1  How to use AT Command to configure LMDS200 ==
673
674
675 LMDS200 UART connection photo
676
677
678 [[image:image-20220615180555-3.png||height="541" width="863"]]
679
680
681 LMDS200 supports AT Command set. User can use a USB to TTL adapter plus the 3.5mm Program Cable to connect to LMDS200 to use AT command, as below.
682
683 [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/test/WebHome/1654135840598-282.png?rev=1.1||alt="1654135840598-282.png"]]
684
685
686 In the PC, you need to set the serial baud rate to (% style="color:green" %)**9600**(%%) to access the serial console for LMDS200. LMDS200 will output system info once power on as below:
687
688 [[image:image-20220615180555-4.png]]
689
690
691 == 5.2  How to upgrade the firmware? ==
692
693
694 (((
695 A new firmware might be available for:
696 )))
697
698 * (((
699 Support new features
700 )))
701 * (((
702 For bug fix
703 )))
704 * (((
705 Change LoRaWAN bands.
706 )))
707
708 (((
709 Instruction for how to upgrade: [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H2.HardwareUpgradeMethodSupportList>>http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H2.HardwareUpgradeMethodSupportList]]
710 )))
711
712 (((
713
714 )))
715
716 (((
717 Firmware location: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LMDS200/Firmware/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LDS03A/Firmware/]]
718 )))
719
720
721 == 5.3  How to change the LoRa Frequency Bands/Region ==
722
723
724 You can follow the instructions for [[how to upgrade image>>||anchor="H5.2A0Howtoupgradethefirmware3F"]].
725 When downloading the images, choose the required image file for download. ​
726
727
728 = 6.  Trouble Shooting =
729
730 == 6.1  AT Command input doesn't work ==
731
732
733 In the case if user can see the console output but can't type input to the device. Please check if you already include the (% style="color:green" %)**ENTER**(%%) while sending out the command. Some serial tool doesn't send (% style="color:green" %)**ENTER**(%%) while press the send key, user need to add ENTER in their string.
734
735 (((
736
737 )))
738
739 = 7.  Order Info =
740
741
742 Part Number **:** (% style="color:blue" %)**LMDS200-XX**
743
744
745 (% style="color:blue" %)**XX**(%%)**: **The default frequency band
746
747 * (% style="color:red" %)**AS923 **(%%)**:** LoRaWAN AS923 band
748 * (% style="color:red" %)**AU915 **(%%)**:** LoRaWAN AU915 band
749 * (% style="color:red" %)**EU433 **(%%)**:** LoRaWAN EU433 band
750 * (% style="color:red" %)**EU868 **(%%)**:** LoRaWAN EU868 band
751 * (% style="color:red" %)**KR920 **(%%)**:** LoRaWAN KR920 band
752 * (% style="color:red" %)**US915 **(%%)**:** LoRaWAN US915 band
753 * (% style="color:red" %)**IN865 **(%%)**:**  LoRaWAN IN865 band
754 * (% style="color:red" %)**CN470 **(%%)**:** LoRaWAN CN470 band
755
756 = 8. ​ Packing Info =
757
758
759 (((
760 **Package Includes**:
761 )))
762
763 (((
764 LMDS200 LoRaWAN Microwave Radar Distance Sensor x 1
765
766
767 )))
768
769 = 9.  ​Support =
770
771
772 * 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.
773 * 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:http://../../../../../../D:%5C%E5%B8%82%E5%9C%BA%E8%B5%84%E6%96%99%5C%E8%AF%B4%E6%98%8E%E4%B9%A6%5CLoRa%5CLT%E7%B3%BB%E5%88%97%5Csupport@dragino.com]].
774
775
Copyright ©2010-2022 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0