Summary

• Page properties (1 modified, 0 added, 0 removed)
• Attachments (0 modified, 3 added, 0 removed)
  • image-20220908175246-1.png
  • image-20220908175333-2.png
  • image-20221009001114-1.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,23 +22,30 @@
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.
	28	+)))
26	26
27		-
	30	+(((
28	28	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.
	32	+)))
29	29
30		-
	34	+(((
31	31	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	+)))
32	32
33		-
	38	+(((
34	34	NDDS75 supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP** (%%)for different application requirement.
	40	+)))
35	35
36		-
	42	+(((
37	37	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	+)))
38	38
39		-
	46	+(((
40	40	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.
41	41	)))
	49	+)))
42	42
43	43
44	44	)))
...	...	@@ -64,6 +64,7 @@
64	64	* 8500mAh Battery for long term use
65	65
66	66
	75	+
67	67	== 1.3  Specification ==
68	68
69	69
...	...	@@ -74,12 +74,12 @@
74	74
75	75	(% style="color:#037691" %)**NB-IoT Spec:**
76	76
77		-* - B1 @H-FDD: 2100MHz
78		-* - B3 @H-FDD: 1800MHz
79		-* - B8 @H-FDD: 900MHz
80		-* - B5 @H-FDD: 850MHz
81		-* - B20 @H-FDD: 800MHz
82		-* - B28 @H-FDD: 700MHz
	86	+* B1 @H-FDD: 2100MHz
	87	+* B3 @H-FDD: 1800MHz
	88	+* B8 @H-FDD: 900MHz
	89	+* B5 @H-FDD: 850MHz
	90	+* B20 @H-FDD: 800MHz
	91	+* B28 @H-FDD: 700MHz
83	83
84	84	(% style="color:#037691" %)**Battery:**
85	85
...	...	@@ -95,8 +95,10 @@
95	95	* Max transmit power: 350mA@3.3v
96	96
97	97
	107	+
98	98	== ​1.4  Applications ==
99	99
	110	+
100	100	* Smart Buildings & Home Automation
101	101	* Logistics and Supply Chain Management
102	102	* Smart Metering
...	...	@@ -108,6 +108,7 @@
108	108	​
109	109
110	110
	122	+
111	111	== 1.5  Pin Definitions ==
112	112
113	113
...	...	@@ -117,8 +117,10 @@
117	117
118	118	= 2.  Use NDDS75 to communicate with IoT Server =
119	119
	132	+
120	120	== 2.1  How it works ==
121	121
	135	+
122	122	(((
123	123	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.
124	124	)))
...	...	@@ -144,16 +144,17 @@
144	144
145	145	=== 2.2.1 Test Requirement ===
146	146
	161	+
147	147	(((
148	148	To use NDDS75 in your city, make sure meet below requirements:
149	149	)))
150	150
151	151	* Your local operator has already distributed a NB-IoT Network there.
152		-* The local NB-IoT network used the band that NSE01 supports.
	167	+* The local NB-IoT network used the band that NDDS75 supports.
153	153	* Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
154	154
155	155	(((
156		-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
	171	+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.
157	157	)))
158	158
159	159
...	...	@@ -163,6 +163,7 @@
163	163
164	164	=== 2.2.2 Insert SIM card ===
165	165
	181	+
166	166	(((
167	167	Insert the NB-IoT Card get from your provider.
168	168	)))
...	...	@@ -178,6 +178,7 @@
178	178
179	179	=== 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
180	180
	197	+
181	181	(((
182	182	(((
183	183	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.
...	...	@@ -186,15 +186,16 @@
186	186
187	187	[[image:image-20220709092052-2.png]]
188	188
189		-**Connection:**
190	190
191		- (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
	207	+(% style="color:blue" %)**Connection:**
192	192
193		- (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
	209	+ (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND**
194	194
195		- (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
	211	+**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)**
196	196
	213	+**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)**
197	197
	215	+
198	198	In the PC, use below serial tool settings:
199	199
200	200	* Baud:  (% style="color:green" %)**9600**
...	...	@@ -209,8 +209,9 @@
209	209
210	210	[[image:1657329814315-101.png]]
211	211
	230	+
212	212	(((
213		-(% 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/]]
	232	+(% 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]]**
214	214	)))
215	215
216	216
...	...	@@ -217,9 +217,10 @@
217	217
218	218	=== 2.2.4 Use CoAP protocol to uplink data ===
219	219
220		-(% 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/]]
221	221
	240	+(% 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/]]**
222	222
	242	+
223	223	(((
224	224	**Use below commands:**
225	225	)))
...	...	@@ -228,21 +228,29 @@
228	228	(% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
229	229	)))
230	230	* (((
231		-(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
	251	+(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/  to set CoAP server address and port
232	232	)))
233	233	* (((
234		-(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
	254	+(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/  Set COAP resource path
	255	+
	256	+
	257	+
235	235	)))
236	236
237	237	(((
238	238	For parameter description, please refer to AT command set
	262	+
	263	+
239	239	)))
240	240
241	241	[[image:1657330452568-615.png]]
242	242
243	243
	269	+
244	244	(((
245	245	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.
	272	+
	273	+
246	246	)))
247	247
248	248	[[image:1657330472797-498.png]]
...	...	@@ -252,9 +252,9 @@
252	252	=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
253	253
254	254
255		-* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
256		-* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
257		-* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
	283	+* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
	284	+* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/  to set UDP server address and port
	285	+* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessary
258	258
259	259	[[image:1657330501006-241.png]]
260	260
...	...	@@ -266,13 +266,13 @@
266	266	=== 2.2.6 Use MQTT protocol to uplink data ===
267	267
268	268
269		-* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
270		-* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
271		-* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
272		-* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
273		-* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
274		-* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/Set the sending topic of MQTT
275		-* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/Set the subscription topic of MQTT
	297	+* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
	298	+* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/  Set MQTT server address and port
	299	+* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/  Set up the CLIENT of MQTT
	300	+* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/  Set the username of MQTT
	301	+* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/  Set the password of MQTT
	302	+* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/  Set the sending topic of MQTT
	303	+* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/  Set the subscription topic of MQTT
276	276
277	277	[[image:1657249978444-674.png]]
278	278
...	...	@@ -289,8 +289,8 @@
289	289	=== 2.2.7 Use TCP protocol to uplink data ===
290	290
291	291
292		-* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
293		-* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
	320	+* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
	321	+* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/  to set TCP server address and port
294	294
295	295	[[image:image-20220709093918-1.png]]
296	296
...	...	@@ -301,75 +301,118 @@
301	301
302	302	=== 2.2.8 Change Update Interval ===
303	303
	332	+
304	304	User can use below command to change the (% style="color:green" %)**uplink interval**.
305	305
306		-* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
	335	+* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/  Set Update Interval to 600s
307	307
308	308	(((
	338	+
	339	+
	340	+
309	309	(% style="color:red" %)**NOTE:**
310		-)))
311	311
312		-(((
313		-(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
	343	+(% style="color:red" %)**1. By default, the device will send an uplink message every 1 hour.**
	344	+
	345	+(% style="color:red" %)**2. When the firmware version is v1.3.2 and later firmware:**
314	314	)))
315	315
	348	+(% 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).**
316	316
317	317
	351	+
318	318	== 2.3  Uplink Payload ==
319	319
320		-In this mode, uplink payload includes in total 14 bytes
321	321
	355	+=== 2.3.1  Before Firmware v1.3.2 ===
322	322
323		-(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
	357	+
	358	+In this mode, uplink payload includes in total 14 bytes
	359	+
	360	+(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
324	324	|=(% style="width: 60px;" %)(((
325	325	**Size(bytes)**
326		-)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 80px;" %)**2**|=(% style="width: 60px;" %)**1**
	363	+)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1**
327	327	|(% 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"]]
328	328
329	329	(((
330		-If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
	367	+If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
331	331	)))
332	332
333	333
334	334	[[image:1657331036973-987.png]]
335	335
336		-(((
	373	+
	374	+
	375	+The payload is **ASCII** string, representative same HEX:
	376	+
	377	+(% style="background-color:yellow" %)**0x 724031556159 0064 0c6c 19 0292 00 **
	378	+
	379	+**where :**
	380	+
	381	+* (% style="color:#037691" %)**Device ID:**(%%) 0x724031556159 = 724031556159
	382	+
	383	+* (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
	384	+
	385	+* (% style="color:#037691" %)**BAT:** (%%) 0x0c6c = 3180 mV = 3.180V
	386	+
	387	+* (% style="color:#037691" %)**Signal:**(%%)  0x19 = 25
	388	+
	389	+* (% style="color:#037691" %)**Distance:**  (%%)0x0292= 658 mm
	390	+
	391	+* (% style="color:#037691" %)**Interrupt:**(%%) 0x00 = 0
	392	+
	393	+
	394	+
	395	+=== 2.3.2  Since firmware v1.3.2 ===
	396	+
	397	+
	398	+In this mode, uplink payload includes 69 bytes in total by default.
	399	+
	400	+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.
	401	+
	402	+(% border="1" style="background-color:#ffffcc; color:green; width:490px" %)
	403	+|=(% scope="row" style="width: 60px;" %)**Size(bytes)**|(% style="width:40px" %)**8**|(% style="width:25px" %)**2**|(% style="width:25px" %)**2**|(% style="width:60px" %)**1**|(% style="width:25px" %)**1**|(% style="width:40px" %)**1**|(% style="width:40px" %)**2**|(% style="width:70px" %)**4**|(% style="width:40px" %)**2**|(% style="width:60px" %)**4**
	404	+|=(% 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.......
	405	+
	406	+If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
	407	+
	408	+[[image:image-20220908175246-1.png]]
	409	+
	410	+
337	337	The payload is ASCII string, representative same HEX:
338		-)))
339	339
340		-(((
341		-0x72403155615900640c6c19029200 where:
342		-)))
	413	+**0x (% style="color:red" %)f867787050213317 (% style="color:blue" %)0084 (% style="color:green" %)0cf4 (% style="color:#00b0f0" %)1e (% style="color:#7030a0" %)01 (% style="color:#d60093" %)00(% style="color:#a14d07" %) 0039 (% style="color:#0020b0" %)6315537b (% style="color:#663300" %)00396319baf0 00396319ba3c 00396319b988 00396319b8d4 00396319b820 00396319b76c 00396319b6b8 00396319b604 (%%)**
343	343
344		-* (((
345		-Device ID: 0x724031556159 = 724031556159
346		-)))
347		-* (((
348		-Version: 0x0064=100=1.0.0
349		-)))
	415	+**where:**
350	350
351		-* (((
352		-BAT: 0x0c6c = 3180 mV = 3.180V
353		-)))
354		-* (((
355		-Signal: 0x19 = 25
356		-)))
357		-* (((
358		-Distance: 0x0292= 658 mm
359		-)))
360		-* (((
361		-Interrupt: 0x00 = 0
	417	+* (% style="color:#037691" %)**Device ID:**(%%) f867787050213317 = f867787050213317
362	362
	419	+* (% style="color:#037691" %)**Version:**(%%) 0x0084=132=1.3.2
363	363
	421	+* (% style="color:#037691" %)**BAT:**(%%)  0x0cf4 = 3316 mV = 3.316V
364	364
365		-
366		-)))
	423	+* (% style="color:#037691" %)**Singal:**(%%)  0x1e = 30
367	367
	425	+* (% style="color:#037691" %)**Mod:**(%%)**     **0x01 = 1
	426	+
	427	+* (% style="color:#037691" %)**Interrupt:**(%%) 0x00= 0
	428	+
	429	+* (% style="color:#037691" %)**Distance:**(%%) 0x0039= 57 = 57
	430	+
	431	+* (% style="color:#037691" %)**Time stamp:**(%%) 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
	432	+
	433	+* (% style="color:#037691" %)**Distance,Time stamp:**(%%) 00396319baf0
	434	+
	435	+* (% style="color:#037691" %)**8 sets of recorded data: Distance,Time stamp :**(%%) //**00396319ba3c**//,.......
	436	+
	437	+
368	368	== 2.4  Payload Explanation and Sensor Interface ==
369	369
370	370
371	371	=== 2.4.1  Device ID ===
372	372
	443	+
373	373	(((
374	374	By default, the Device ID equal to the last 6 bytes of IMEI.
375	375	)))
...	...	@@ -376,10 +376,12 @@
376	376
377	377	(((
378	378	User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
	450	+
	451	+
379	379	)))
380	380
381	381	(((
382		-**Example:**
	455	+(% style="color:blue" %)**Example :**
383	383	)))
384	384
385	385	(((
...	...	@@ -387,13 +387,26 @@
387	387	)))
388	388
389	389	(((
390		-The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
	463	+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.
391	391	)))
392	392
393	393
	467	+(% style="color:red" %)**NOTE: When the firmware version is v1.3.2 and later firmware:**
394	394
	469	+(% style="color:red" %)**By default, the Device ID equal to the last 15 bits of IMEI.**
	470	+
	471	+User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
	472	+
	473	+
	474	+(% style="color:blue" %)**Example :**
	475	+
	476	+AT+DEUI=868411056754138
	477	+
	478	+
	479	+
395	395	=== 2.4.2  Version Info ===
396	396
	482	+
397	397	(((
398	398	Specify the software version: 0x64=100, means firmware version 1.00.
399	399	)))
...	...	@@ -406,6 +406,7 @@
406	406
407	407	=== 2.4.3  Battery Info ===
408	408
	495	+
409	409	(((
410	410	Ex1: 0x0B45 = 2885mV
411	411	)))
...	...	@@ -418,6 +418,7 @@
418	418
419	419	=== 2.4.4  Signal Strength ===
420	420
	508	+
421	421	(((
422	422	NB-IoT Network signal Strength.
423	423	)))
...	...	@@ -450,9 +450,12 @@
450	450
451	451	=== 2.4.5  Distance ===
452	452
	541	+
453	453	Get the distance. Flat object range 280mm - 7500mm.
454	454
	544	+(((
455	455	For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
	546	+)))
456	456
457	457	(((
458	458	(((
...	...	@@ -470,6 +470,7 @@
470	470
471	471	=== 2.4.6  Digital Interrupt ===
472	472
	564	+
473	473	(((
474	474	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.
475	475	)))
...	...	@@ -479,7 +479,7 @@
479	479	)))
480	480
481	481	(((
482		-(% 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]])**.**
	574	+(% 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]])**.**
483	483	)))
484	484
485	485
...	...	@@ -504,6 +504,7 @@
504	504
505	505	=== 2.4.7  ​+5V Output ===
506	506
	599	+
507	507	(((
508	508	NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling.
509	509	)))
...	...	@@ -511,10 +511,14 @@
511	511
512	512	(((
513	513	The 5V output time can be controlled by AT Command.
	607	+
	608	+
514	514	)))
515	515
516	516	(((
517	517	(% style="color:blue" %)**AT+5VT=1000**
	613	+
	614	+
518	518	)))
519	519
520	520	(((
...	...	@@ -525,6 +525,7 @@
525	525
526	526	== 2.5  Downlink Payload ==
527	527
	625	+
528	528	By default, NDDS75 prints the downlink payload to console port.
529	529
530	530	[[image:image-20220709100028-1.png]]
...	...	@@ -575,9 +575,55 @@
575	575
576	576
577	577
578		-== 2.6  ​LED Indicator ==
	676	+== 2.6  Distance alarm function(Since firmware v1.3.2) ==
579	579
580	580
	679	+(% style="color:blue" %)** ➢ AT Command:**
	680	+
	681	+(% style="color:#037691" %)** AT+ LDDSALARM=min,max**
	682	+
	683	+² When min=0, and max≠0, Alarm higher than max
	684	+
	685	+² When min≠0, and max=0, Alarm lower than min
	686	+
	687	+² When min≠0 and max≠0, Alarm higher than max or lower than min
	688	+
	689	+
	690	+(% style="color:blue" %)** Example:**
	691	+
	692	+**AT+ LDDSALARM=260,2000**  ~/~/ Alarm when distance lower than 260.
	693	+
	694	+
	695	+
	696	+== 2.7  Set the number of data to be uploaded and the recording time ==
	697	+
	698	+
	699	+(% style="color:blue" %)** ➢ AT Command:**
	700	+
	701	+* (% 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)
	702	+* (% 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.
	703	+
	704	+ The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
	705	+
	706	+[[image:image-20221009001114-1.png||height="687" width="955"]]
	707	+
	708	+
	709	+
	710	+== 2.8  Read or Clear cached data ==
	711	+
	712	+
	713	+(% style="color:blue" %)** ➢ AT Command:**
	714	+
	715	+* (% style="color:#037691" %)** AT+CDP ** (%%) ~/~/  Read cached data
	716	+* (% style="color:#037691" %)** AT+CDP=0**  (%%) ~/~/  Clear cached data
	717	+
	718	+[[image:image-20220908175333-2.png]]
	719	+
	720	+
	721	+
	722	+== 2.9  ​LED Indicator ==
	723	+
	724	+
581	581	The NDDS75 has an internal LED which is to show the status of different state.
582	582
583	583
...	...	@@ -592,23 +592,27 @@
592	592
593	593
594	594
595		-== 2.7  ​Firmware Change Log ==
	739	+== 2.10  ​Firmware Change Log ==
596	596
597	597
598		-Download URL & Firmware Change log
	742	+(((
	743	+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]]
	744	+)))
599	599
600	600	(((
601		-[[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/]]
	747	+
602	602	)))
603	603
	750	+(((
	751	+Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
	752	+)))
604	604
605		-Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
606	606
607	607
	756	+== 2.11  ​Battery Analysis ==
608	608
609		-== 2.8  ​Battery Analysis ==
610	610
611		-=== 2.8.1  ​Battery Type ===
	759	+=== 2.11.1  ​Battery Type ===
612	612
613	613
614	614	(((
...	...	@@ -633,8 +633,9 @@
633	633
634	634
635	635
636		-=== 2.8.2  Power consumption Analyze ===
	784	+=== 2.11.2  Power consumption Analyze ===
637	637
	786	+
638	638	(((
639	639	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.
640	640	)))
...	...	@@ -671,8 +671,9 @@
671	671
672	672
673	673
674		-=== 2.8.3  ​Battery Note ===
	823	+=== 2.11.3  ​Battery Note ===
675	675
	825	+
676	676	(((
677	677	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.
678	678	)))
...	...	@@ -679,8 +679,9 @@
679	679
680	680
681	681
682		-=== 2.8.4  Replace the battery ===
	832	+=== 2.11.4  Replace the battery ===
683	683
	834	+
684	684	(((
685	685	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).
686	686	)))
...	...	@@ -689,6 +689,7 @@
689	689
690	690	= 3. ​ Access NB-IoT Module =
691	691
	843	+
692	692	(((
693	693	Users can directly access the AT command set of the NB-IoT module.
694	694	)))
...	...	@@ -695,6 +695,8 @@
695	695
696	696	(((
697	697	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/]]
	850	+
	851	+
698	698	)))
699	699
700	700	[[image:1657333200519-600.png]]
...	...	@@ -703,84 +703,103 @@
703	703
704	704	= 4.  Using the AT Commands =
705	705
	860	+
706	706	== 4.1  Access AT Commands ==
707	707
708		-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/]]
709	709
	864	+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]]
710	710
711		-AT+<CMD>?  : Help on <CMD>
712	712
713		-AT+<CMD>         : Run <CMD>
	867	+AT+<CMD>?  :  Help on <CMD>
714	714
715		-AT+<CMD>=<value> : Set the value
	869	+AT+<CMD>         :  Run <CMD>
716	716
717		-AT+<CMD>=?  : Get the value
	871	+AT+<CMD>=<value> :  Set the value
718	718
	873	+AT+<CMD>=?  :  Get the value
719	719
	875	+
720	720	(% style="color:#037691" %)**General Commands**(%%)
721	721
722		-AT  : Attention
	878	+AT  :  Attention
723	723
724		-AT?  : Short Help
	880	+AT?  :  Short Help
725	725
726		-ATZ  : MCU Reset
	882	+ATZ  :  MCU Reset
727	727
728		-AT+TDC  : Application Data Transmission Interval
	884	+AT+TDC  :  Application Data Transmission Interval
729	729
730		-AT+CFG  : Print all configurations
	886	+AT+CFG  :  Print all configurations
731	731
732		-AT+CFGMOD           : Working mode selection
	888	+AT+CFGMOD           :  Working mode selection
733	733
734		-AT+INTMOD            : Set the trigger interrupt mode
	890	+AT+INTMOD            :  Set the trigger interrupt mode
735	735
736		-AT+5VT  : Set extend the time of 5V power
	892	+AT+5VT  :  Set extend the time of 5V power
737	737
738		-AT+PRO  : Choose agreement
	894	+AT+PRO  :  Choose agreement
739	739
740		-AT+WEIGRE  : Get weight or set weight to 0
	896	+AT+WEIGRE  :  Get weight or set weight to 0
741	741
742		-AT+WEIGAP  : Get or Set the GapValue of weight
	898	+AT+WEIGAP  :  Get or Set the GapValue of weight
743	743
744		-AT+RXDL  : Extend the sending and receiving time
	900	+AT+RXDL  :  Extend the sending and receiving time
745	745
746		-AT+CNTFAC  : Get or set counting parameters
	902	+AT+CNTFAC  :  Get or set counting parameters
747	747
748		-AT+SERVADDR  : Server Address
	904	+AT+SERVADDR  :  Server Address
749	749
	906	+AT+TR  :  Get or Set record time"
750	750
	908	+AT+APN     :  Get or set the APN
	909	+
	910	+AT+FBAND  :  Get or Set whether to automatically modify the frequency band
	911	+
	912	+AT+DNSCFG  : Get or Set DNS Server
	913	+
	914	+AT+GETSENSORVALUE   :  Returns the current sensor measurement
	915	+
	916	+AT+NOUD  :  Get or Set the number of data to be uploaded
	917	+
	918	+AT+CDP     :  Read or Clear cached data
	919	+
	920	+AT+LDDSALARM :  Get or Set alarm of distance
	921	+
	922	+
751	751	(% style="color:#037691" %)**COAP Management**
752	752
753		-AT+URI            : Resource parameters
	925	+AT+URI            :  Resource parameters
754	754
755	755
756	756	(% style="color:#037691" %)**UDP Management**
757	757
758		-AT+CFM          : Upload confirmation mode (only valid for UDP)
	930	+AT+CFM          :  Upload confirmation mode (only valid for UDP)
759	759
760	760
761	761	(% style="color:#037691" %)**MQTT Management**
762	762
763		-AT+CLIENT               : Get or Set MQTT client
	935	+AT+CLIENT  :  Get or Set MQTT client
764	764
765		-AT+UNAME  : Get or Set MQTT Username
	937	+AT+UNAME  :  Get or Set MQTT Username
766	766
767		-AT+PWD                  : Get or Set MQTT password
	939	+AT+PWD  :  Get or Set MQTT password
768	768
769		-AT+PUBTOPIC  : Get or Set MQTT publish topic
	941	+AT+PUBTOPIC  :  Get or Set MQTT publish topic
770	770
771		-AT+SUBTOPIC  : Get or Set MQTT subscription topic
	943	+AT+SUBTOPIC  :  Get or Set MQTT subscription topic
772	772
773	773
774	774	(% style="color:#037691" %)**Information**
775	775
776		-AT+FDR  : Factory Data Reset
	948	+AT+FDR  :  Factory Data Reset
777	777
778		-AT+PWORD  : Serial Access Password
	950	+AT+PWORD  :  Serial Access Password
779	779
780	780
781	781
782	782	= ​5.  FAQ =
783	783
	956	+
784	784	== 5.1 ​ How to Upgrade Firmware ==
785	785
786	786
...	...	@@ -793,7 +793,7 @@
793	793	)))
794	794
795	795	(((
796		-(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.
	969	+(% style="color:red" %)**Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.**
797	797	)))
798	798
799	799
...	...	@@ -800,6 +800,7 @@
800	800
801	801	= 6.  Trouble Shooting =
802	802
	976	+
803	803	== 6.1  ​Connection problem when uploading firmware ==
804	804
805	805
...	...	@@ -815,6 +815,7 @@
815	815
816	816	== 6.2  AT Command input doesn't work ==
817	817
	992	+
818	818	(((
819	819	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.
820	820
...	...	@@ -840,7 +840,7 @@
840	840
841	841	(% style="color:#037691" %)**Package Includes**:
842	842
843		-* NSE01 NB-IoT Distance Detect Sensor Node x 1
	1018	+* NDDS75 NB-IoT Distance Detect Sensor Node x 1
844	844	* External antenna x 1
845	845	)))
846	846
...	...	@@ -847,9 +847,9 @@
847	847	(((
848	848
849	849
	1025	+
850	850	(% style="color:#037691" %)**Dimension and weight**:
851	851
852		-
853	853	* Device Size: 13.0 x 5 x 4.5 cm
854	854	* Device Weight: 150g
855	855	* Package Size / pcs : 15 x 12x 5.5 cm
...	...	@@ -865,5 +865,6 @@
865	865
866	866	= 9.  Support =
867	867
	1043	+
868	868	* 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.
869	869	* 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

image-20221009001114-1.png

Author

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

Size

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

Content