Summary

• Page properties (1 modified, 0 added, 0 removed)
• Attachments (0 modified, 2 added, 0 removed)
  • image-20220908175246-1.png
  • image-20220908175333-2.png

Details

Page properties

Content

...	...	@@ -16,6 +16,7 @@
16	16
17	17	= 1.  Introduction =
18	18
	19	+
19	19	== 1.1 ​ What is NDDS75 Distance Detection Sensor ==
20	20
21	21	(((
...	...	@@ -56,6 +56,7 @@
56	56
57	57	== 1.2 ​ Features ==
58	58
	60	+
59	59	* NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
60	60	* Ultra low power consumption
61	61	* Distance Detection by Ultrasonic technology
...	...	@@ -72,6 +72,7 @@
72	72
73	73	== 1.3  Specification ==
74	74
	77	+
75	75	(% style="color:#037691" %)**Common DC Characteristics:**
76	76
77	77	* Supply Voltage: 2.1v ~~ 3.6v
...	...	@@ -102,6 +102,7 @@
102	102
103	103	== ​1.4  Applications ==
104	104
	108	+
105	105	* Smart Buildings & Home Automation
106	106	* Logistics and Supply Chain Management
107	107	* Smart Metering
...	...	@@ -113,6 +113,8 @@
113	113	​
114	114
115	115
	120	+
	121	+
116	116	== 1.5  Pin Definitions ==
117	117
118	118
...	...	@@ -122,8 +122,10 @@
122	122
123	123	= 2.  Use NDDS75 to communicate with IoT Server =
124	124
	131	+
125	125	== 2.1  How it works ==
126	126
	134	+
127	127	(((
128	128	The NDDS75 is equipped with a NB-IoT module, the pre-loaded firmware in NDDS75 will get environment data from sensors and send the value to local NB-IoT network via the NB-IoT module.  The NB-IoT network will forward this value to IoT server via the protocol defined by NDDS75.
129	129	)))
...	...	@@ -149,6 +149,7 @@
149	149
150	150	=== 2.2.1 Test Requirement ===
151	151
	160	+
152	152	(((
153	153	To use NDDS75 in your city, make sure meet below requirements:
154	154	)))
...	...	@@ -158,7 +158,7 @@
158	158	* Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
159	159
160	160	(((
161		-Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.  The NDDS75 will use CoAP((% style="color:red" %)120.24.4.116:5683)(%%) or raw UDP((% style="color:red" %)120.24.4.116:5601)(%%) or MQTT((% style="color:red" %)120.24.4.116:1883)(%%)or TCP((% style="color:red" %)120.24.4.116:5600)(%%)protocol to send data to the test server
	170	+Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.  The NDDS75 will use CoAP((% style="color:red" %)120.24.4.116:5683)(%%) or raw UDP((% style="color:red" %)120.24.4.116:5601)(%%) or MQTT((% style="color:red" %)120.24.4.116:1883)(%%)or TCP((% style="color:red" %)120.24.4.116:5600)(%%)protocol to send data to the test server.
162	162	)))
163	163
164	164
...	...	@@ -168,6 +168,7 @@
168	168
169	169	=== 2.2.2 Insert SIM card ===
170	170
	180	+
171	171	(((
172	172	Insert the NB-IoT Card get from your provider.
173	173	)))
...	...	@@ -183,6 +183,7 @@
183	183
184	184	=== 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
185	185
	196	+
186	186	(((
187	187	(((
188	188	User need to configure NDDS75 via serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. NDDS75 support AT Commands, user can use a USB to TTL adapter to connect to NDDS75 and use AT Commands to configure it, as below.
...	...	@@ -191,6 +191,7 @@
191	191
192	192	[[image:image-20220709092052-2.png]]
193	193
	205	+
194	194	**Connection:**
195	195
196	196	(% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
...	...	@@ -214,8 +214,9 @@
214	214
215	215	[[image:1657329814315-101.png]]
216	216
	229	+
217	217	(((
218		-(% style="color:red" %)Note: the valid AT Commands can be found at: (%%)[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/]]
	231	+(% style="color:red" %)**Note: the valid AT Commands can be found at: **(%%)**[[https:~~/~~/www.dropbox.com/sh/aaq2xcl0bzfu0yd/AAAEAHRa7Io_465ds4Y7-F3aa?dl=0>>https://www.dropbox.com/sh/aaq2xcl0bzfu0yd/AAAEAHRa7Io_465ds4Y7-F3aa?dl=0]]**
219	219	)))
220	220
221	221
...	...	@@ -222,9 +222,10 @@
222	222
223	223	=== 2.2.4 Use CoAP protocol to uplink data ===
224	224
225		-(% style="color:red" %)Note: if you don't have CoAP server, you can refer this link to set up one: (%%)[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/>>http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]]
226	226
	239	+(% style="color:red" %)**Note: if you don't have CoAP server, you can refer this link to set up one: **(%%)**[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/>>http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]]**
227	227
	241	+
228	228	(((
229	229	**Use below commands:**
230	230	)))
...	...	@@ -237,17 +237,25 @@
237	237	)))
238	238	* (((
239	239	(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
	254	+
	255	+
	256	+
240	240	)))
241	241
242	242	(((
243	243	For parameter description, please refer to AT command set
	261	+
	262	+
244	244	)))
245	245
246	246	[[image:1657330452568-615.png]]
247	247
248	248
	268	+
249	249	(((
250	250	After configure the server address and (% style="color:green" %)**reset the device**(%%) (via AT+ATZ ), NDDS75 will start to uplink sensor values to CoAP server.
	271	+
	272	+
251	251	)))
252	252
253	253	[[image:1657330472797-498.png]]
...	...	@@ -306,25 +306,31 @@
306	306
307	307	=== 2.2.8 Change Update Interval ===
308	308
	331	+
309	309	User can use below command to change the (% style="color:green" %)**uplink interval**.
310	310
311	311	* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
312	312
313	313	(((
314		-(% style="color:red" %)**NOTE:**
315		-)))
	337	+(% style="color:red" %)**NOTE 1: By default, the device will send an uplink message every 1 hour.**
316	316
317		-(((
318		-(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
	339	+
319	319	)))
320	320
	342	+(% style="color:red" %)**NOTE 2: When the firmware version is v1.3.2 and later firmware:**
321	321
	344	+(% style="color:red" %)**By default, the device will send an uplink message every 2 hours. Each Uplink Include 8 set of records in this 2 hour (15 minute interval / record).**
322	322
	346	+
	347	+
323	323	== 2.3  Uplink Payload ==
324	324
325		-In this mode, uplink payload includes in total 14 bytes
326	326
	351	+=== 2.3.1  Before Firmware 1.3.2 ===
327	327
	353	+
	354	+In this mode, uplink payload includes in total 14 bytes
	355	+
328	328	(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
329	329	|=(% style="width: 60px;" %)(((
330	330	**Size(bytes)**
...	...	@@ -338,8 +338,9 @@
338	338
339	339	[[image:1657331036973-987.png]]
340	340
	369	+
341	341	(((
342		-The payload is ASCII string, representative same HEX:
	371	+The payload is **ASCII** string, representative same HEX:
343	343	)))
344	344
345	345	(((
...	...	@@ -350,11 +350,11 @@
350	350	Device ID: 0x724031556159 = 724031556159
351	351	)))
352	352	* (((
353		-Version: 0x0064=100=1.0.0
	382	+Version:  0x0064=100=1.0.0
354	354	)))
355	355
356	356	* (((
357		-BAT: 0x0c6c = 3180 mV = 3.180V
	386	+BAT:  0x0c6c = 3180 mV = 3.180V
358	358	)))
359	359	* (((
360	360	Signal: 0x19 = 25
...	...	@@ -367,14 +367,48 @@
367	367
368	368
369	369
	399	+
370	370
371	371	)))
372	372
	403	+=== **2.3.2  Since firmware v1.3.2** ===
	404	+
	405	+
	406	+In this mode, uplink payload includes 69 bytes in total by default.
	407	+
	408	+Each time the device uploads a data package, 8 sets of recorded data will be attached. Up to 32 sets of recorded data can be uploaded.
	409	+
	410	+(% border="2" style="background-color:#ffffcc; color:green; width:896px" %)
	411	+|(% style="width:95px" %)**Size(bytes)**|(% style="width:84px" %)**8**|(% style="width:44px" %)2|(% style="width:48px" %)2|(% style="width:123px" %)1|(% style="width:55px" %)1|(% style="width:80px" %)1|(% style="width:77px" %)2|(% style="width:94px" %)4|(% style="width:77px" %)2|(% style="width:116px" %)4
	412	+|(% style="width:95px" %)**Value**|(% style="width:84px" %)Device ID|(% style="width:44px" %)Ver|(% style="width:48px" %)BAT|(% style="width:123px" %)Signal Strength|(% style="width:55px" %)MOD|(% style="width:80px" %)Interrupt|(% style="width:77px" %)Distance|(% style="width:94px" %)Timestamp|(% style="width:77px" %)Distance|(% style="width:116px" %)Timestamp.......
	413	+
	414	+If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
	415	+
	416	+[[image:image-20220908175246-1.png]]
	417	+
	418	+
	419	+The payload is ASCII string, representative same HEX:
	420	+
	421	+0x(% style="color:red" %)f867787050213317(% style="color:blue" %)0084(% style="color:green" %)0cf4(% style="color:red" %)1e(% style="color:blue" %)01(% style="color:green" %)00(% style="color:red" %)**//00396319bb32//**00396319baf0//**00396319ba3c**//00396319b988//**00396319b8d4**//00396319b820//**00396319b76c**//00396319b6b8//**00396319b604**//(%%) where:
	422	+
	423	+* (% style="color:green" %)Device ID: f867787050213317 = f867787050213317
	424	+* (% style="color:red" %)Version: 0x0084=132=1.3.2
	425	+* (% style="color:green" %)BAT: 0x0cf4 = 3316 mV = 3.316V
	426	+* (% style="color:blue" %)Singal: 0x1e = 30
	427	+* (% style="color:red" %)Mod: 0x01 = 1
	428	+* Interrupt: 0x00= 0
	429	+* Distance: 0x0039= 57 = 57
	430	+* Time stamp : 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
	431	+* Distance,Time stamp : 00396319baf0
	432	+* (% style="color:red" %) 8 sets of recorded data: Distance,Time stamp : //**00396319ba3c**//,.......
	433	+
	434	+
373	373	== 2.4  Payload Explanation and Sensor Interface ==
374	374
375	375
376	376	=== 2.4.1  Device ID ===
377	377
	440	+
378	378	(((
379	379	By default, the Device ID equal to the last 6 bytes of IMEI.
380	380	)))
...	...	@@ -381,10 +381,12 @@
381	381
382	382	(((
383	383	User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
	447	+
	448	+
384	384	)))
385	385
386	386	(((
387		-**Example:**
	452	+(% style="color:blue" %)**Example :**
388	388	)))
389	389
390	390	(((
...	...	@@ -392,13 +392,26 @@
392	392	)))
393	393
394	394	(((
395		-The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
	460	+The Device ID is stored in a none-erase area, Upgrade the firmware or run (% style="color:blue" %)**AT+FDR**(%%) won't erase Device ID.
396	396	)))
397	397
398	398
	464	+(% style="color:red" %)**NOTE: When the firmware version is v1.3.2 and later firmware:**
399	399
	466	+(% style="color:red" %)**By default, the Device ID equal to the last 15 bits of IMEI.**
	467	+
	468	+User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
	469	+
	470	+
	471	+(% style="color:blue" %)**Example :**
	472	+
	473	+AT+DEUI=868411056754138
	474	+
	475	+
	476	+
400	400	=== 2.4.2  Version Info ===
401	401
	479	+
402	402	(((
403	403	Specify the software version: 0x64=100, means firmware version 1.00.
404	404	)))
...	...	@@ -411,6 +411,7 @@
411	411
412	412	=== 2.4.3  Battery Info ===
413	413
	492	+
414	414	(((
415	415	Ex1: 0x0B45 = 2885mV
416	416	)))
...	...	@@ -423,6 +423,7 @@
423	423
424	424	=== 2.4.4  Signal Strength ===
425	425
	505	+
426	426	(((
427	427	NB-IoT Network signal Strength.
428	428	)))
...	...	@@ -455,6 +455,7 @@
455	455
456	456	=== 2.4.5  Distance ===
457	457
	538	+
458	458	Get the distance. Flat object range 280mm - 7500mm.
459	459
460	460	(((
...	...	@@ -477,6 +477,7 @@
477	477
478	478	=== 2.4.6  Digital Interrupt ===
479	479
	561	+
480	480	(((
481	481	Digital Interrupt refers to pin (% style="color:blue" %)**GPIO_EXTI**(%%), and there are different trigger methods. When there is a trigger, the NDDS75 will send a packet to the server.
482	482	)))
...	...	@@ -511,6 +511,7 @@
511	511
512	512	=== 2.4.7  ​+5V Output ===
513	513
	596	+
514	514	(((
515	515	NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling.
516	516	)))
...	...	@@ -518,10 +518,14 @@
518	518
519	519	(((
520	520	The 5V output time can be controlled by AT Command.
	604	+
	605	+
521	521	)))
522	522
523	523	(((
524	524	(% style="color:blue" %)**AT+5VT=1000**
	610	+
	611	+
525	525	)))
526	526
527	527	(((
...	...	@@ -532,6 +532,7 @@
532	532
533	533	== 2.5  Downlink Payload ==
534	534
	622	+
535	535	By default, NDDS75 prints the downlink payload to console port.
536	536
537	537	[[image:image-20220709100028-1.png]]
...	...	@@ -582,9 +582,55 @@
582	582
583	583
584	584
585		-== 2.6  ​LED Indicator ==
	673	+== 2.6  Distance alarm function(Since firmware v1.3.2) ==
586	586
587	587
	676	+(% style="color:blue" %)** ➢ AT Command:**
	677	+
	678	+(% style="color:#037691" %)** AT+ LDDSALARM=min,max**
	679	+
	680	+² When min=0, and max≠0, Alarm higher than max
	681	+
	682	+² When min≠0, and max=0, Alarm lower than min
	683	+
	684	+² When min≠0 and max≠0, Alarm higher than max or lower than min
	685	+
	686	+
	687	+(% style="color:blue" %)** Example:**
	688	+
	689	+**AT+ LDDSALARM=260,2000**  ~/~/ Alarm when distance lower than 260.
	690	+
	691	+
	692	+
	693	+== 2.7  Set the number of data to be uploaded and the recording time ==
	694	+
	695	+
	696	+(% style="color:blue" %)** ➢ AT Command:**
	697	+
	698	+(% style="color:#037691" %)** AT+TR=900** (%%) ~/~/ The unit is seconds, and the default is to record data once every 900 seconds.( The minimum can be set to 180 seconds)
	699	+
	700	+(% style="color:#037691" %)** AT+NOUD=8** (%%) ~/~/  The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
	701	+
	702	+
	703	+
	704	+== 2.8  Read or Clear cached data ==
	705	+
	706	+
	707	+(% style="color:blue" %)** ➢ AT Command:**
	708	+
	709	+(% style="color:#037691" %)** AT+CDP ** (%%) ~/~/ Read cached data
	710	+
	711	+
	712	+[[image:image-20220908175333-2.png]]
	713	+
	714	+
	715	+(% style="color:#037691" %)** AT+CDP=0**  (%%) ~/~/ Clear cached data
	716	+
	717	+
	718	+
	719	+== 2.9  ​LED Indicator ==
	720	+
	721	+
588	588	The NDDS75 has an internal LED which is to show the status of different state.
589	589
590	590
...	...	@@ -599,29 +599,29 @@
599	599
600	600
601	601
602		-== 2.7  ​Firmware Change Log ==
	736	+== 2.10  ​Firmware Change Log ==
603	603
604	604
605	605	(((
606		-Download URL & Firmware Change log
	740	+Download URL & Firmware Change log:  [[https:~~/~~/www.dropbox.com/sh/3hb94r49iszmstx/AADvSJcXxahEUfxqKWVnZx-La?dl=0>>https://www.dropbox.com/sh/3hb94r49iszmstx/AADvSJcXxahEUfxqKWVnZx-La?dl=0]]
607	607	)))
608	608
609	609	(((
610		-[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/Firmware/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/Firmware/]]
	744	+
611	611	)))
612	612
613		-
614	614	(((
615		-Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
	748	+Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
616	616	)))
617	617
618	618
619	619
620		-== 2.8  ​Battery Analysis ==
	753	+== 2.11  ​Battery Analysis ==
621	621
622		-=== 2.8.1  ​Battery Type ===
623	623
	756	+=== 2.11.1  ​Battery Type ===
624	624
	758	+
625	625	(((
626	626	The NDDS75 battery is a combination of an 8500mAh Li/SOCI2 Battery and a Super Capacitor. The battery is none-rechargeable battery type with a low discharge rate (<2% per year). This type of battery is commonly used in IoT devices such as water meter.
627	627	)))
...	...	@@ -644,8 +644,9 @@
644	644
645	645
646	646
647		-=== 2.8.2  Power consumption Analyze ===
	781	+=== 2.11.2  Power consumption Analyze ===
648	648
	783	+
649	649	(((
650	650	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.
651	651	)))
...	...	@@ -682,8 +682,9 @@
682	682
683	683
684	684
685		-=== 2.8.3  ​Battery Note ===
	820	+=== 2.11.3  ​Battery Note ===
686	686
	822	+
687	687	(((
688	688	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.
689	689	)))
...	...	@@ -690,8 +690,9 @@
690	690
691	691
692	692
693		-=== 2.8.4  Replace the battery ===
	829	+=== 2.11.4  Replace the battery ===
694	694
	831	+
695	695	(((
696	696	The default battery pack of NDDS75 includes a ER26500 plus super capacitor. If user can't find this pack locally, they can find ER26500 or equivalence without the SPC1520 capacitor, which will also work in most case. The SPC can enlarge the battery life for high frequency use (update period below 5 minutes).
697	697	)))
...	...	@@ -700,6 +700,7 @@
700	700
701	701	= 3. ​ Access NB-IoT Module =
702	702
	840	+
703	703	(((
704	704	Users can directly access the AT command set of the NB-IoT module.
705	705	)))
...	...	@@ -706,6 +706,8 @@
706	706
707	707	(((
708	708	The AT Command set can refer the BC35-G NB-IoT Module AT Command: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/>>url:https://www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/]]
	847	+
	848	+
709	709	)))
710	710
711	711	[[image:1657333200519-600.png]]
...	...	@@ -714,11 +714,13 @@
714	714
715	715	= 4.  Using the AT Commands =
716	716
	857	+
717	717	== 4.1  Access AT Commands ==
718	718
719		-See this link for detail: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/]]
720	720
	861	+See this link for detail:  [[https:~~/~~/www.dropbox.com/sh/aaq2xcl0bzfu0yd/AAAEAHRa7Io_465ds4Y7-F3aa?dl=0>>https://www.dropbox.com/sh/aaq2xcl0bzfu0yd/AAAEAHRa7Io_465ds4Y7-F3aa?dl=0]]
721	721
	863	+
722	722	AT+<CMD>?  : Help on <CMD>
723	723
724	724	AT+<CMD>         : Run <CMD>
...	...	@@ -758,7 +758,23 @@
758	758
759	759	AT+SERVADDR  : Server Address
760	760
	903	+AT+TR      : Get or Set record time"
761	761
	905	+AT+APN     : Get or set the APN
	906	+
	907	+AT+FBAND   : Get or Set whether to automatically modify the frequency band
	908	+
	909	+AT+DNSCFG  : Get or Set DNS Server
	910	+
	911	+AT+GETSENSORVALUE   : Returns the current sensor measurement
	912	+
	913	+AT+NOUD      : Get or Set the number of data to be uploaded
	914	+
	915	+AT+CDP     : Read or Clear cached data
	916	+
	917	+AT+LDDSALARM : Get or Set alarm of distance
	918	+
	919	+
762	762	(% style="color:#037691" %)**COAP Management**
763	763
764	764	AT+URI            : Resource parameters
...	...	@@ -792,6 +792,7 @@
792	792
793	793	= ​5.  FAQ =
794	794
	953	+
795	795	== 5.1 ​ How to Upgrade Firmware ==
796	796
797	797
...	...	@@ -804,7 +804,7 @@
804	804	)))
805	805
806	806	(((
807		-(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.
	966	+(% style="color:red" %)**Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.**
808	808	)))
809	809
810	810
...	...	@@ -811,6 +811,7 @@
811	811
812	812	= 6.  Trouble Shooting =
813	813
	973	+
814	814	== 6.1  ​Connection problem when uploading firmware ==
815	815
816	816
...	...	@@ -826,6 +826,7 @@
826	826
827	827	== 6.2  AT Command input doesn't work ==
828	828
	989	+
829	829	(((
830	830	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.
831	831
...	...	@@ -858,6 +858,7 @@
858	858	(((
859	859
860	860
	1022	+
861	861	(% style="color:#037691" %)**Dimension and weight**:
862	862
863	863	* Device Size: 13.0 x 5 x 4.5 cm
...	...	@@ -875,5 +875,6 @@
875	875
876	876	= 9.  Support =
877	877
	1040	+
878	878	* 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.
879	879	* 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]]

image-20220908175246-1.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.David

Size

...	...	@@ -1,0 +1,1 @@
	1	+55.7 KB

Content

image-20220908175333-2.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.David

Size

...	...	@@ -1,0 +1,1 @@
	1	+31.1 KB

Content