Summary

• Page properties (1 modified, 0 added, 0 removed)

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	(((
...	...	@@ -22,20 +22,34 @@
22	22
23	23
24	24	(((
	26	+(((
25	25	The Dragino NDDS75 is a (% style="color:blue" %)**NB-IoT Distance Detection Sensor**(%%) for Internet of Things solution. It is designed to measure the distance between the sensor and a flat object. The distance detection sensor is a module that uses ultrasonic sensing technology for distance measurement, and temperature compensation is performed internally to improve the reliability of data.
26		-\\The NDDS75 can be applied to scenarios such as horizontal distance measurement, liquid level measurement, parking management system, object proximity and presence detection, intelligent trash can management system, robot obstacle avoidance, automatic control, sewer, bottom water level monitoring, etc. It detects the distance between the measured object and the sensor, and uploads the value via wireless to IoT Server via NB-IoT Network.
27		-\\NarrowBand-Internet of Things (NB-IoT) is a standards-based low power wide area (LPWA) technology developed to enable a wide range of new IoT devices and services. NB-IoT significantly improves the power consumption of user devices, system capacity and spectrum efficiency, especially in deep coverage.
28		-\\NDDS75 supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP** (%%)for different application requirement.
29		-\\NDDS75 is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long term use up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method)
30		-\\To use NDDS75, user needs to check if there is NB-IoT coverage in local area and with the bands NDDS75 supports. If the local operate support it, user needs to get a NB-IoT SIM card from local operator and install NDDS75 to get NB-IoT network connection.
31	31	)))
32	32
33		-
	30	+(((
	31	+The NDDS75 can be applied to scenarios such as horizontal distance measurement, liquid level measurement, parking management system, object proximity and presence detection, intelligent trash can management system, robot obstacle avoidance, automatic control, sewer, bottom water level monitoring, etc. It detects the distance between the measured object and the sensor, and uploads the value via wireless to IoT Server via NB-IoT Network.
34	34	)))
35	35
36		-[[image:1654503236291-817.png]]
	34	+(((
	35	+NarrowBand-Internet of Things (NB-IoT) is a standards-based low power wide area (LPWA) technology developed to enable a wide range of new IoT devices and services. NB-IoT significantly improves the power consumption of user devices, system capacity and spectrum efficiency, especially in deep coverage.
	36	+)))
37	37
	38	+(((
	39	+NDDS75 supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP** (%%)for different application requirement.
	40	+)))
38	38
	42	+(((
	43	+NDDS75 is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long term use up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method)
	44	+)))
	45	+
	46	+(((
	47	+To use NDDS75, user needs to check if there is NB-IoT coverage in local area and with the bands NDDS75 supports. If the local operate support it, user needs to get a NB-IoT SIM card from local operator and install NDDS75 to get NB-IoT network connection.
	48	+)))
	49	+)))
	50	+
	51	+
	52	+)))
	53	+
39	39	[[image:1657327959271-447.png]]
40	40
41	41
...	...	@@ -58,6 +58,7 @@
58	58
59	59
60	60
	76	+
61	61	== 1.3  Specification ==
62	62
63	63
...	...	@@ -66,6 +66,8 @@
66	66	* Supply Voltage: 2.1v ~~ 3.6v
67	67	* Operating Temperature: -40 ~~ 85°C
68	68
	85	+
	86	+
69	69	(% style="color:#037691" %)**NB-IoT Spec:**
70	70
71	71	* - B1 @H-FDD: 2100MHz
...	...	@@ -75,6 +75,8 @@
75	75	* - B20 @H-FDD: 800MHz
76	76	* - B28 @H-FDD: 700MHz
77	77
	96	+
	97	+
78	78	(% style="color:#037691" %)**Battery:**
79	79
80	80	* Li/SOCI2 un-chargeable battery
...	...	@@ -83,15 +83,19 @@
83	83	* Max continuously current: 130mA
84	84	* Max boost current: 2A, 1 second
85	85
	106	+
	107	+
86	86	(% style="color:#037691" %)**Power Consumption**
87	87
88	88	* STOP Mode: 10uA @ 3.3v
89		-* Max transmit power: [[350mA@3.3v>>mailto:350mA@3.3v]]
	111	+* Max transmit power: 350mA@3.3v
90	90
91	91
92	92
	115	+
93	93	== ​1.4  Applications ==
94	94
	118	+
95	95	* Smart Buildings & Home Automation
96	96	* Logistics and Supply Chain Management
97	97	* Smart Metering
...	...	@@ -103,6 +103,8 @@
103	103	​
104	104
105	105
	130	+
	131	+
106	106	== 1.5  Pin Definitions ==
107	107
108	108
...	...	@@ -112,8 +112,10 @@
112	112
113	113	= 2.  Use NDDS75 to communicate with IoT Server =
114	114
	141	+
115	115	== 2.1  How it works ==
116	116
	144	+
117	117	(((
118	118	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.
119	119	)))
...	...	@@ -139,16 +139,19 @@
139	139
140	140	=== 2.2.1 Test Requirement ===
141	141
	170	+
142	142	(((
143	143	To use NDDS75 in your city, make sure meet below requirements:
144	144	)))
145	145
146	146	* Your local operator has already distributed a NB-IoT Network there.
147		-* The local NB-IoT network used the band that NSE01 supports.
	176	+* The local NB-IoT network used the band that NDDS75 supports.
148	148	* Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
149	149
	179	+
	180	+
150	150	(((
151		-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
	182	+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.
152	152	)))
153	153
154	154
...	...	@@ -158,6 +158,7 @@
158	158
159	159	=== 2.2.2 Insert SIM card ===
160	160
	192	+
161	161	(((
162	162	Insert the NB-IoT Card get from your provider.
163	163	)))
...	...	@@ -173,6 +173,7 @@
173	173
174	174	=== 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
175	175
	208	+
176	176	(((
177	177	(((
178	178	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.
...	...	@@ -181,6 +181,7 @@
181	181
182	182	[[image:image-20220709092052-2.png]]
183	183
	217	+
184	184	**Connection:**
185	185
186	186	(% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
...	...	@@ -204,8 +204,9 @@
204	204
205	205	[[image:1657329814315-101.png]]
206	206
	241	+
207	207	(((
208		-(% 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/]]
	243	+(% 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]]**
209	209	)))
210	210
211	211
...	...	@@ -212,21 +212,38 @@
212	212
213	213	=== 2.2.4 Use CoAP protocol to uplink data ===
214	214
215		-(% 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/]]
216	216
	251	+(% 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/]]**
217	217
	253	+
	254	+(((
218	218	**Use below commands:**
	256	+)))
219	219
220		-* (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
221		-* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
222		-* (% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
	258	+* (((
	259	+(% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
	260	+)))
	261	+* (((
	262	+(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
	263	+)))
	264	+* (((
	265	+(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
223	223
	267	+
	268	+
	269	+)))
	270	+
	271	+(((
224	224	For parameter description, please refer to AT command set
	273	+)))
225	225
226	226	[[image:1657330452568-615.png]]
227	227
228	228
	278	+
	279	+(((
229	229	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.
	281	+)))
230	230
231	231	[[image:1657330472797-498.png]]
232	232
...	...	@@ -235,10 +235,12 @@
235	235	=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
236	236
237	237
238		-* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
	290	+* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
239	239	* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
240		-* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/If the server does not respond, this command is unnecessary
	292	+* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
241	241
	294	+
	295	+
242	242	[[image:1657330501006-241.png]]
243	243
244	244
...	...	@@ -249,14 +249,16 @@
249	249	=== 2.2.6 Use MQTT protocol to uplink data ===
250	250
251	251
252		-* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
253		-* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
254		-* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
255		-* (% style="color:blue" %)**AT+UNAME=UNAME                               **(%%)~/~/Set the username of MQTT
256		-* (% style="color:blue" %)**AT+PWD=PWD                                        **(%%)~/~/Set the password of MQTT
	306	+* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
	307	+* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
	308	+* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
	309	+* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
	310	+* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
257	257	* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/Set the sending topic of MQTT
258	258	* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/Set the subscription topic of MQTT
259	259
	314	+
	315	+
260	260	[[image:1657249978444-674.png]]
261	261
262	262
...	...	@@ -275,6 +275,8 @@
275	275	* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
276	276	* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
277	277
	334	+
	335	+
278	278	[[image:image-20220709093918-1.png]]
279	279
280	280
...	...	@@ -284,16 +284,15 @@
284	284
285	285	=== 2.2.8 Change Update Interval ===
286	286
	345	+
287	287	User can use below command to change the (% style="color:green" %)**uplink interval**.
288	288
289	289	* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
290	290
291		-(((
292		-(% style="color:red" %)**NOTE:**
293		-)))
294	294
	351	+
295	295	(((
296		-(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
	353	+(% style="color:red" %)**NOTE: By default, the device will send an uplink message every 1 hour.**
297	297	)))
298	298
299	299
...	...	@@ -300,13 +300,14 @@
300	300
301	301	== 2.3  Uplink Payload ==
302	302
	360	+
303	303	In this mode, uplink payload includes in total 14 bytes
304	304
305	305
306		-(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
307		-|=(% style="width: 80px;" %)(((
	364	+(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
	365	+|=(% style="width: 60px;" %)(((
308	308	**Size(bytes)**
309		-)))|=(% style="width: 80px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 110px;" %)**1**|=(% style="width: 110px;" %)**2**|=(% style="width: 70px;" %)**1**
	367	+)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1**
310	310	|(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:41px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:120px" %)[[Distance (unit: mm)>>||anchor="H2.4.5A0Distance"]]|(% style="width:80px" %)[[Interrupt>>||anchor="H2.4.6A0DigitalInterrupt"]]
311	311
312	312	(((
...	...	@@ -316,6 +316,7 @@
316	316
317	317	[[image:1657331036973-987.png]]
318	318
	377	+
319	319	(((
320	320	The payload is ASCII string, representative same HEX:
321	321	)))
...	...	@@ -353,6 +353,7 @@
353	353
354	354	=== 2.4.1  Device ID ===
355	355
	415	+
356	356	(((
357	357	By default, the Device ID equal to the last 6 bytes of IMEI.
358	358	)))
...	...	@@ -359,6 +359,8 @@
359	359
360	360	(((
361	361	User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
	422	+
	423	+
362	362	)))
363	363
364	364	(((
...	...	@@ -377,6 +377,7 @@
377	377
378	378	=== 2.4.2  Version Info ===
379	379
	442	+
380	380	(((
381	381	Specify the software version: 0x64=100, means firmware version 1.00.
382	382	)))
...	...	@@ -389,9 +389,6 @@
389	389
390	390	=== 2.4.3  Battery Info ===
391	391
392		-(((
393		-Check the battery voltage for LSE01.
394		-)))
395	395
396	396	(((
397	397	Ex1: 0x0B45 = 2885mV
...	...	@@ -405,6 +405,7 @@
405	405
406	406	=== 2.4.4  Signal Strength ===
407	407
	468	+
408	408	(((
409	409	NB-IoT Network signal Strength.
410	410	)))
...	...	@@ -437,9 +437,12 @@
437	437
438	438	=== 2.4.5  Distance ===
439	439
	501	+
440	440	Get the distance. Flat object range 280mm - 7500mm.
441	441
	504	+(((
442	442	For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
	506	+)))
443	443
444	444	(((
445	445	(((
...	...	@@ -457,6 +457,7 @@
457	457
458	458	=== 2.4.6  Digital Interrupt ===
459	459
	524	+
460	460	(((
461	461	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.
462	462	)))
...	...	@@ -491,6 +491,7 @@
491	491
492	492	=== 2.4.7  ​+5V Output ===
493	493
	559	+
494	494	(((
495	495	NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling.
496	496	)))
...	...	@@ -498,10 +498,14 @@
498	498
499	499	(((
500	500	The 5V output time can be controlled by AT Command.
	567	+
	568	+
501	501	)))
502	502
503	503	(((
504	504	(% style="color:blue" %)**AT+5VT=1000**
	573	+
	574	+
505	505	)))
506	506
507	507	(((
...	...	@@ -512,6 +512,7 @@
512	512
513	513	== 2.5  Downlink Payload ==
514	514
	585	+
515	515	By default, NDDS75 prints the downlink payload to console port.
516	516
517	517	[[image:image-20220709100028-1.png]]
...	...	@@ -582,19 +582,23 @@
582	582	== 2.7  ​Firmware Change Log ==
583	583
584	584
585		-Download URL & Firmware Change log
	656	+(((
	657	+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]]
	658	+)))
586	586
587	587	(((
588		-[[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/]]
	661	+
589	589	)))
590	590
	664	+(((
	665	+Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
	666	+)))
591	591
592		-Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
593	593
594	594
595		-
596	596	== 2.8  ​Battery Analysis ==
597	597
	672	+
598	598	=== 2.8.1  ​Battery Type ===
599	599
600	600
...	...	@@ -622,6 +622,7 @@
622	622
623	623	=== 2.8.2  Power consumption Analyze ===
624	624
	700	+
625	625	(((
626	626	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.
627	627	)))
...	...	@@ -660,6 +660,7 @@
660	660
661	661	=== 2.8.3  ​Battery Note ===
662	662
	739	+
663	663	(((
664	664	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.
665	665	)))
...	...	@@ -668,6 +668,7 @@
668	668
669	669	=== 2.8.4  Replace the battery ===
670	670
	748	+
671	671	(((
672	672	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).
673	673	)))
...	...	@@ -676,6 +676,7 @@
676	676
677	677	= 3. ​ Access NB-IoT Module =
678	678
	757	+
679	679	(((
680	680	Users can directly access the AT command set of the NB-IoT module.
681	681	)))
...	...	@@ -682,6 +682,8 @@
682	682
683	683	(((
684	684	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/]]
	764	+
	765	+
685	685	)))
686	686
687	687	[[image:1657333200519-600.png]]
...	...	@@ -690,11 +690,13 @@
690	690
691	691	= 4.  Using the AT Commands =
692	692
	774	+
693	693	== 4.1  Access AT Commands ==
694	694
695		-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/]]
696	696
	778	+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]]
697	697
	780	+
698	698	AT+<CMD>?  : Help on <CMD>
699	699
700	700	AT+<CMD>         : Run <CMD>
...	...	@@ -768,6 +768,7 @@
768	768
769	769	= ​5.  FAQ =
770	770
	854	+
771	771	== 5.1 ​ How to Upgrade Firmware ==
772	772
773	773
...	...	@@ -780,7 +780,7 @@
780	780	)))
781	781
782	782	(((
783		-(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.
	867	+(% style="color:red" %)**Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.**
784	784	)))
785	785
786	786
...	...	@@ -787,6 +787,7 @@
787	787
788	788	= 6.  Trouble Shooting =
789	789
	874	+
790	790	== 6.1  ​Connection problem when uploading firmware ==
791	791
792	792
...	...	@@ -802,6 +802,7 @@
802	802
803	803	== 6.2  AT Command input doesn't work ==
804	804
	890	+
805	805	(((
806	806	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.
807	807
...	...	@@ -827,7 +827,7 @@
827	827
828	828	(% style="color:#037691" %)**Package Includes**:
829	829
830		-* NSE01 NB-IoT Distance Detect Sensor Node x 1
	916	+* NDDS75 NB-IoT Distance Detect Sensor Node x 1
831	831	* External antenna x 1
832	832	)))
833	833
...	...	@@ -834,9 +834,9 @@
834	834	(((
835	835
836	836
	923	+
837	837	(% style="color:#037691" %)**Dimension and weight**:
838	838
839		-
840	840	* Device Size: 13.0 x 5 x 4.5 cm
841	841	* Device Weight: 150g
842	842	* Package Size / pcs : 15 x 12x 5.5 cm
...	...	@@ -852,5 +852,8 @@
852	852
853	853	= 9.  Support =
854	854
	941	+
855	855	* 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.
856	856	* 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]]
	944	+
	945	+