Summary

• Page properties (1 modified, 0 added, 0 removed)
• Attachments (0 modified, 3 added, 0 removed)
  • image-20220709110451-3.png
  • 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	(((
...	...	@@ -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
...	...	@@ -57,6 +57,7 @@
57	57	* 8500mAh Battery for long term use
58	58
59	59
	75	+
60	60	== 1.3  Specification ==
61	61
62	62
...	...	@@ -85,12 +85,13 @@
85	85	(% style="color:#037691" %)**Power Consumption**
86	86
87	87	* STOP Mode: 10uA @ 3.3v
88		-* Max transmit power: [[350mA@3.3v>>mailto:350mA@3.3v]]
	104	+* Max transmit power: 350mA@3.3v
89	89
90	90
91	91
92	92	== ​1.4  Applications ==
93	93
	110	+
94	94	* Smart Buildings & Home Automation
95	95	* Logistics and Supply Chain Management
96	96	* Smart Metering
...	...	@@ -103,6 +103,7 @@
103	103
104	104
105	105
	123	+
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
	133	+
115	115	== 2.1  How it works ==
116	116
	136	+
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,17 @@
139	139
140	140	=== 2.2.1 Test Requirement ===
141	141
	162	+
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.
	168	+* 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
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
	172	+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
	182	+
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
	198	+
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,15 +181,16 @@
181	181
182	182	[[image:image-20220709092052-2.png]]
183	183
184		-**Connection:**
185	185
186		- (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
	208	+(% style="color:blue" %)**Connection:**
187	187
188		- (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
	210	+ (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND**
189	189
190		- (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
	212	+**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)**
191	191
	214	+**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)**
192	192
	216	+
193	193	In the PC, use below serial tool settings:
194	194
195	195	* Baud:  (% style="color:green" %)**9600**
...	...	@@ -204,8 +204,9 @@
204	204
205	205	[[image:1657329814315-101.png]]
206	206
	231	+
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/]]
	233	+(% 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,22 +212,43 @@
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
	241	+(% 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
	243	+
	244	+(((
218	218	**Use below commands:**
	246	+)))
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
	248	+* (((
	249	+(% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
	250	+)))
	251	+* (((
	252	+(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/  to set CoAP server address and port
	253	+)))
	254	+* (((
	255	+(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/  Set COAP resource path
223	223
	257	+
	258	+
	259	+)))
	260	+
	261	+(((
224	224	For parameter description, please refer to AT command set
225	225
	264	+
	265	+)))
	266	+
226	226	[[image:1657330452568-615.png]]
227	227
228	228
	270	+
	271	+(((
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.
230	230
	274	+
	275	+)))
	276	+
231	231	[[image:1657330472797-498.png]]
232	232
233	233
...	...	@@ -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
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
	284	+* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
	285	+* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/  to set UDP server address and port
	286	+* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessary
241	241
	288	+
	289	+
242	242	[[image:1657330501006-241.png]]
243	243
244	244
...	...	@@ -249,13 +249,13 @@
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
257		-* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/Set the sending topic of MQTT
258		-* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/Set the subscription topic of MQTT
	300	+* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
	301	+* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/  Set MQTT server address and port
	302	+* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/  Set up the CLIENT of MQTT
	303	+* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/  Set the username of MQTT
	304	+* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/  Set the password of MQTT
	305	+* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/  Set the sending topic of MQTT
	306	+* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/  Set the subscription topic of MQTT
259	259
260	260	[[image:1657249978444-674.png]]
261	261
...	...	@@ -272,8 +272,8 @@
272	272	=== 2.2.7 Use TCP protocol to uplink data ===
273	273
274	274
275		-* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
276		-* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
	323	+* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
	324	+* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/  to set TCP server address and port
277	277
278	278	[[image:image-20220709093918-1.png]]
279	279
...	...	@@ -284,30 +284,39 @@
284	284
285	285	=== 2.2.8 Change Update Interval ===
286	286
	335	+
287	287	User can use below command to change the (% style="color:green" %)**uplink interval**.
288	288
289		-* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
	338	+* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/  Set Update Interval to 600s
290	290
291	291	(((
	341	+
	342	+
	343	+
292	292	(% style="color:red" %)**NOTE:**
293		-)))
294	294
295		-(((
296		-(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
	346	+(% style="color:red" %)**1. By default, the device will send an uplink message every 1 hour.**
	347	+
	348	+(% style="color:red" %)**2. When the firmware version is v1.3.2 and later firmware:**
297	297	)))
298	298
	351	+(% 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).**
299	299
300	300
	354	+
301	301	== 2.3  Uplink Payload ==
302	302
303		-In this mode, uplink payload includes in total 14 bytes
304	304
	358	+=== 2.3.1  Before Firmware v1.3.2 ===
305	305
306		-(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
307		-|=(% style="width: 80px;" %)(((
	360	+
	361	+In this mode, uplink payload includes in total 14 bytes
	362	+
	363	+(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
	364	+|=(% 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**
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.8A0DigitalInterrupt"]]
	366	+)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1**
	367	+|(% 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	(((
313	313	If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
...	...	@@ -316,8 +316,9 @@
316	316
317	317	[[image:1657331036973-987.png]]
318	318
	376	+
319	319	(((
320		-The payload is ASCII string, representative same HEX:
	378	+The payload is **ASCII** string, representative same HEX:
321	321	)))
322	322
323	323	(((
...	...	@@ -328,11 +328,11 @@
328	328	Device ID: 0x724031556159 = 724031556159
329	329	)))
330	330	* (((
331		-Version: 0x0064=100=1.0.0
	389	+Version:  0x0064=100=1.0.0
332	332	)))
333	333
334	334	* (((
335		-BAT: 0x0c6c = 3180 mV = 3.180V
	393	+BAT:  0x0c6c = 3180 mV = 3.180V
336	336	)))
337	337	* (((
338	338	Signal: 0x19 = 25
...	...	@@ -342,14 +342,52 @@
342	342	)))
343	343	* (((
344	344	Interrupt: 0x00 = 0
	403	+
	404	+
	405	+
	406	+
	407	+
345	345	)))
346	346
	410	+=== **2.3.2  Since firmware v1.3.2** ===
347	347
	412	+
	413	+In this mode, uplink payload includes 69 bytes in total by default.
	414	+
	415	+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.
	416	+
	417	+(% border="2" style="background-color:#ffffcc; color:green; width:896px" %)
	418	+|(% 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
	419	+|(% 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.......
	420	+
	421	+If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
	422	+
	423	+[[image:image-20220908175246-1.png]]
	424	+
	425	+
	426	+The payload is ASCII string, representative same HEX:
	427	+
	428	+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:
	429	+
	430	+* (% style="color:green" %)Device ID: f867787050213317 = f867787050213317
	431	+* (% style="color:red" %)Version: 0x0084=132=1.3.2
	432	+* (% style="color:green" %)BAT: 0x0cf4 = 3316 mV = 3.316V
	433	+* (% style="color:blue" %)Singal: 0x1e = 30
	434	+* (% style="color:red" %)Mod: 0x01 = 1
	435	+* Interrupt: 0x00= 0
	436	+* Distance: 0x0039= 57 = 57
	437	+* Time stamp : 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
	438	+* Distance,Time stamp : 00396319baf0
	439	+* (% style="color:red" %) 8 sets of recorded data: Distance,Time stamp : //**00396319ba3c**//,.......
	440	+
	441	+
	442	+
348	348	== 2.4  Payload Explanation and Sensor Interface ==
349	349
350	350
351	351	=== 2.4.1  Device ID ===
352	352
	448	+
353	353	(((
354	354	By default, the Device ID equal to the last 6 bytes of IMEI.
355	355	)))
...	...	@@ -356,10 +356,12 @@
356	356
357	357	(((
358	358	User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
	455	+
	456	+
359	359	)))
360	360
361	361	(((
362		-**Example:**
	460	+(% style="color:blue" %)**Example :**
363	363	)))
364	364
365	365	(((
...	...	@@ -367,13 +367,26 @@
367	367	)))
368	368
369	369	(((
370		-The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
	468	+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.
371	371	)))
372	372
373	373
	472	+(% style="color:red" %)**NOTE: When the firmware version is v1.3.2 and later firmware:**
374	374
	474	+(% style="color:red" %)**By default, the Device ID equal to the last 15 bits of IMEI.**
	475	+
	476	+User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
	477	+
	478	+
	479	+(% style="color:blue" %)**Example :**
	480	+
	481	+AT+DEUI=868411056754138
	482	+
	483	+
	484	+
375	375	=== 2.4.2  Version Info ===
376	376
	487	+
377	377	(((
378	378	Specify the software version: 0x64=100, means firmware version 1.00.
379	379	)))
...	...	@@ -386,9 +386,6 @@
386	386
387	387	=== 2.4.3  Battery Info ===
388	388
389		-(((
390		-Check the battery voltage for LSE01.
391		-)))
392	392
393	393	(((
394	394	Ex1: 0x0B45 = 2885mV
...	...	@@ -402,6 +402,7 @@
402	402
403	403	=== 2.4.4  Signal Strength ===
404	404
	513	+
405	405	(((
406	406	NB-IoT Network signal Strength.
407	407	)))
...	...	@@ -434,9 +434,12 @@
434	434
435	435	=== 2.4.5  Distance ===
436	436
	546	+
437	437	Get the distance. Flat object range 280mm - 7500mm.
438	438
	549	+(((
439	439	For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
	551	+)))
440	440
441	441	(((
442	442	(((
...	...	@@ -454,6 +454,7 @@
454	454
455	455	=== 2.4.6  Digital Interrupt ===
456	456
	569	+
457	457	(((
458	458	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.
459	459	)))
...	...	@@ -463,7 +463,7 @@
463	463	)))
464	464
465	465	(((
466		-(% style="color:blue" %)**AT+INTMOD=3 **(%%) ~/~/(more info about INMOD please refer [[**AT Command Manual**>>url:https://www.dragino.com/downloads/downloads/NB-IoT/NBSN95/DRAGINO_NBSN95-NB_AT%20Commands_v1.1.0.pdf]])**.**
	579	+(% style="color:blue" %)**AT+INTMOD=3 **(%%) ~/~/  (more info about INMOD please refer [[**AT Command Manual**>>url:https://www.dragino.com/downloads/downloads/NB-IoT/NBSN95/DRAGINO_NBSN95-NB_AT%20Commands_v1.1.0.pdf]])**.**
467	467	)))
468	468
469	469
...	...	@@ -488,6 +488,7 @@
488	488
489	489	=== 2.4.7  ​+5V Output ===
490	490
	604	+
491	491	(((
492	492	NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling.
493	493	)))
...	...	@@ -495,10 +495,14 @@
495	495
496	496	(((
497	497	The 5V output time can be controlled by AT Command.
	612	+
	613	+
498	498	)))
499	499
500	500	(((
501	501	(% style="color:blue" %)**AT+5VT=1000**
	618	+
	619	+
502	502	)))
503	503
504	504	(((
...	...	@@ -509,6 +509,7 @@
509	509
510	510	== 2.5  Downlink Payload ==
511	511
	630	+
512	512	By default, NDDS75 prints the downlink payload to console port.
513	513
514	514	[[image:image-20220709100028-1.png]]
...	...	@@ -559,9 +559,52 @@
559	559
560	560
561	561
562		-== 2.6  ​LED Indicator ==
	681	+== 2.6  Distance alarm function(Since firmware v1.3.2) ==
563	563
564	564
	684	+(% style="color:blue" %)** ➢ AT Command:**
	685	+
	686	+(% style="color:#037691" %)** AT+ LDDSALARM=min,max**
	687	+
	688	+² When min=0, and max≠0, Alarm higher than max
	689	+
	690	+² When min≠0, and max=0, Alarm lower than min
	691	+
	692	+² When min≠0 and max≠0, Alarm higher than max or lower than min
	693	+
	694	+
	695	+(% style="color:blue" %)** Example:**
	696	+
	697	+**AT+ LDDSALARM=260,2000**  ~/~/ Alarm when distance lower than 260.
	698	+
	699	+
	700	+
	701	+== 2.7  Set the number of data to be uploaded and the recording time ==
	702	+
	703	+
	704	+(% style="color:blue" %)** ➢ AT Command:**
	705	+
	706	+* (% 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)
	707	+* (% 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.
	708	+
	709	+
	710	+
	711	+
	712	+== 2.8  Read or Clear cached data ==
	713	+
	714	+
	715	+(% style="color:blue" %)** ➢ AT Command:**
	716	+
	717	+* (% style="color:#037691" %)** AT+CDP ** (%%) ~/~/  Read cached data
	718	+* (% style="color:#037691" %)** AT+CDP=0**  (%%) ~/~/  Clear cached data
	719	+
	720	+[[image:image-20220908175333-2.png]]
	721	+
	722	+
	723	+
	724	+== 2.9  ​LED Indicator ==
	725	+
	726	+
565	565	The NDDS75 has an internal LED which is to show the status of different state.
566	566
567	567
...	...	@@ -576,23 +576,27 @@
576	576
577	577
578	578
579		-== 2.7  ​Firmware Change Log ==
	741	+== 2.10  ​Firmware Change Log ==
580	580
581	581
582		-Download URL & Firmware Change log
	744	+(((
	745	+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]]
	746	+)))
583	583
584	584	(((
585		-[[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/]]
	749	+
586	586	)))
587	587
	752	+(((
	753	+Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
	754	+)))
588	588
589		-Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
590	590
591	591
	758	+== 2.11  ​Battery Analysis ==
592	592
593		-== 2.8  ​Battery Analysis ==
594	594
595		-=== 2.8.1  ​Battery Type ===
	761	+=== 2.11.1  ​Battery Type ===
596	596
597	597
598	598	(((
...	...	@@ -617,8 +617,9 @@
617	617
618	618
619	619
620		-=== 2.8.2  Power consumption Analyze ===
	786	+=== 2.11.2  Power consumption Analyze ===
621	621
	788	+
622	622	(((
623	623	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.
624	624	)))
...	...	@@ -651,12 +651,13 @@
651	651	And the Life expectation in difference case will be shown on the right.
652	652	)))
653	653
654		-[[image:image-20220708141352-7.jpeg]]
	821	+[[image:image-20220709110451-3.png]]
655	655
656	656
657	657
658		-=== 2.8.3  ​Battery Note ===
	825	+=== 2.11.3  ​Battery Note ===
659	659
	827	+
660	660	(((
661	661	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.
662	662	)))
...	...	@@ -663,8 +663,9 @@
663	663
664	664
665	665
666		-=== 2.8.4  Replace the battery ===
	834	+=== 2.11.4  Replace the battery ===
667	667
	836	+
668	668	(((
669	669	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).
670	670	)))
...	...	@@ -673,6 +673,7 @@
673	673
674	674	= 3. ​ Access NB-IoT Module =
675	675
	845	+
676	676	(((
677	677	Users can directly access the AT command set of the NB-IoT module.
678	678	)))
...	...	@@ -679,6 +679,8 @@
679	679
680	680	(((
681	681	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/]]
	852	+
	853	+
682	682	)))
683	683
684	684	[[image:1657333200519-600.png]]
...	...	@@ -687,84 +687,103 @@
687	687
688	688	= 4.  Using the AT Commands =
689	689
	862	+
690	690	== 4.1  Access AT Commands ==
691	691
692		-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/]]
693	693
	866	+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]]
694	694
695		-AT+<CMD>?  : Help on <CMD>
696	696
697		-AT+<CMD>         : Run <CMD>
	869	+AT+<CMD>?  :  Help on <CMD>
698	698
699		-AT+<CMD>=<value> : Set the value
	871	+AT+<CMD>         :  Run <CMD>
700	700
701		-AT+<CMD>=?  : Get the value
	873	+AT+<CMD>=<value> :  Set the value
702	702
	875	+AT+<CMD>=?  :  Get the value
703	703
	877	+
704	704	(% style="color:#037691" %)**General Commands**(%%)
705	705
706		-AT  : Attention
	880	+AT  :  Attention
707	707
708		-AT?  : Short Help
	882	+AT?  :  Short Help
709	709
710		-ATZ  : MCU Reset
	884	+ATZ  :  MCU Reset
711	711
712		-AT+TDC  : Application Data Transmission Interval
	886	+AT+TDC  :  Application Data Transmission Interval
713	713
714		-AT+CFG  : Print all configurations
	888	+AT+CFG  :  Print all configurations
715	715
716		-AT+CFGMOD           : Working mode selection
	890	+AT+CFGMOD           :  Working mode selection
717	717
718		-AT+INTMOD            : Set the trigger interrupt mode
	892	+AT+INTMOD            :  Set the trigger interrupt mode
719	719
720		-AT+5VT  : Set extend the time of 5V power
	894	+AT+5VT  :  Set extend the time of 5V power
721	721
722		-AT+PRO  : Choose agreement
	896	+AT+PRO  :  Choose agreement
723	723
724		-AT+WEIGRE  : Get weight or set weight to 0
	898	+AT+WEIGRE  :  Get weight or set weight to 0
725	725
726		-AT+WEIGAP  : Get or Set the GapValue of weight
	900	+AT+WEIGAP  :  Get or Set the GapValue of weight
727	727
728		-AT+RXDL  : Extend the sending and receiving time
	902	+AT+RXDL  :  Extend the sending and receiving time
729	729
730		-AT+CNTFAC  : Get or set counting parameters
	904	+AT+CNTFAC  :  Get or set counting parameters
731	731
732		-AT+SERVADDR  : Server Address
	906	+AT+SERVADDR  :  Server Address
733	733
	908	+AT+TR  :  Get or Set record time"
734	734
	910	+AT+APN     :  Get or set the APN
	911	+
	912	+AT+FBAND  :  Get or Set whether to automatically modify the frequency band
	913	+
	914	+AT+DNSCFG  : Get or Set DNS Server
	915	+
	916	+AT+GETSENSORVALUE   :  Returns the current sensor measurement
	917	+
	918	+AT+NOUD  :  Get or Set the number of data to be uploaded
	919	+
	920	+AT+CDP     :  Read or Clear cached data
	921	+
	922	+AT+LDDSALARM :  Get or Set alarm of distance
	923	+
	924	+
735	735	(% style="color:#037691" %)**COAP Management**
736	736
737		-AT+URI            : Resource parameters
	927	+AT+URI            :  Resource parameters
738	738
739	739
740	740	(% style="color:#037691" %)**UDP Management**
741	741
742		-AT+CFM          : Upload confirmation mode (only valid for UDP)
	932	+AT+CFM          :  Upload confirmation mode (only valid for UDP)
743	743
744	744
745	745	(% style="color:#037691" %)**MQTT Management**
746	746
747		-AT+CLIENT               : Get or Set MQTT client
	937	+AT+CLIENT  :  Get or Set MQTT client
748	748
749		-AT+UNAME  : Get or Set MQTT Username
	939	+AT+UNAME  :  Get or Set MQTT Username
750	750
751		-AT+PWD                  : Get or Set MQTT password
	941	+AT+PWD  :  Get or Set MQTT password
752	752
753		-AT+PUBTOPIC  : Get or Set MQTT publish topic
	943	+AT+PUBTOPIC  :  Get or Set MQTT publish topic
754	754
755		-AT+SUBTOPIC  : Get or Set MQTT subscription topic
	945	+AT+SUBTOPIC  :  Get or Set MQTT subscription topic
756	756
757	757
758	758	(% style="color:#037691" %)**Information**
759	759
760		-AT+FDR  : Factory Data Reset
	950	+AT+FDR  :  Factory Data Reset
761	761
762		-AT+PWORD  : Serial Access Password
	952	+AT+PWORD  :  Serial Access Password
763	763
764	764
765	765
766	766	= ​5.  FAQ =
767	767
	958	+
768	768	== 5.1 ​ How to Upgrade Firmware ==
769	769
770	770
...	...	@@ -777,7 +777,7 @@
777	777	)))
778	778
779	779	(((
780		-(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.
	971	+(% style="color:red" %)**Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.**
781	781	)))
782	782
783	783
...	...	@@ -784,6 +784,7 @@
784	784
785	785	= 6.  Trouble Shooting =
786	786
	978	+
787	787	== 6.1  ​Connection problem when uploading firmware ==
788	788
789	789
...	...	@@ -799,6 +799,7 @@
799	799
800	800	== 6.2  AT Command input doesn't work ==
801	801
	994	+
802	802	(((
803	803	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.
804	804
...	...	@@ -824,7 +824,7 @@
824	824
825	825	(% style="color:#037691" %)**Package Includes**:
826	826
827		-* NSE01 NB-IoT Distance Detect Sensor Node x 1
	1020	+* NDDS75 NB-IoT Distance Detect Sensor Node x 1
828	828	* External antenna x 1
829	829	)))
830	830
...	...	@@ -831,9 +831,9 @@
831	831	(((
832	832
833	833
	1027	+
834	834	(% style="color:#037691" %)**Dimension and weight**:
835	835
836		-
837	837	* Device Size: 13.0 x 5 x 4.5 cm
838	838	* Device Weight: 150g
839	839	* Package Size / pcs : 15 x 12x 5.5 cm
...	...	@@ -849,5 +849,6 @@
849	849
850	850	= 9.  Support =
851	851
	1045	+
852	852	* 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.
853	853	* 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-20220709110451-3.png

Author

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

Size

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

Content

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