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,14 +22,31 @@
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
	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.
	32	+)))
	33	+
	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	+
	38	+(((
	39	+NDDS75 supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP** (%%)for different application requirement.
	40	+)))
	41	+
	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	+
33	33
34	34	)))
35	35
...	...	@@ -54,7 +54,6 @@
54	54	* 8500mAh Battery for long term use
55	55
56	56
57		-
58	58	== 1.3  Specification ==
59	59
60	60
...	...	@@ -65,12 +65,12 @@
65	65
66	66	(% style="color:#037691" %)**NB-IoT Spec:**
67	67
68		-* - B1 @H-FDD: 2100MHz
69		-* - B3 @H-FDD: 1800MHz
70		-* - B8 @H-FDD: 900MHz
71		-* - B5 @H-FDD: 850MHz
72		-* - B20 @H-FDD: 800MHz
73		-* - B28 @H-FDD: 700MHz
	85	+* B1 @H-FDD: 2100MHz
	86	+* B3 @H-FDD: 1800MHz
	87	+* B8 @H-FDD: 900MHz
	88	+* B5 @H-FDD: 850MHz
	89	+* B20 @H-FDD: 800MHz
	90	+* B28 @H-FDD: 700MHz
74	74
75	75	(% style="color:#037691" %)**Battery:**
76	76
...	...	@@ -86,9 +86,9 @@
86	86	* Max transmit power: 350mA@3.3v
87	87
88	88
89		-
90	90	== ​1.4  Applications ==
91	91
	108	+
92	92	* Smart Buildings & Home Automation
93	93	* Logistics and Supply Chain Management
94	94	* Smart Metering
...	...	@@ -100,6 +100,7 @@
100	100	​
101	101
102	102
	120	+
103	103	== 1.5  Pin Definitions ==
104	104
105	105
...	...	@@ -109,8 +109,10 @@
109	109
110	110	= 2.  Use NDDS75 to communicate with IoT Server =
111	111
	130	+
112	112	== 2.1  How it works ==
113	113
	133	+
114	114	(((
115	115	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.
116	116	)))
...	...	@@ -136,16 +136,17 @@
136	136
137	137	=== 2.2.1 Test Requirement ===
138	138
	159	+
139	139	(((
140	140	To use NDDS75 in your city, make sure meet below requirements:
141	141	)))
142	142
143	143	* Your local operator has already distributed a NB-IoT Network there.
144		-* The local NB-IoT network used the band that NSE01 supports.
	165	+* The local NB-IoT network used the band that NDDS75 supports.
145	145	* Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
146	146
147	147	(((
148		-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
	169	+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.
149	149	)))
150	150
151	151
...	...	@@ -155,6 +155,7 @@
155	155
156	156	=== 2.2.2 Insert SIM card ===
157	157
	179	+
158	158	(((
159	159	Insert the NB-IoT Card get from your provider.
160	160	)))
...	...	@@ -170,6 +170,7 @@
170	170
171	171	=== 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
172	172
	195	+
173	173	(((
174	174	(((
175	175	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.
...	...	@@ -178,15 +178,16 @@
178	178
179	179	[[image:image-20220709092052-2.png]]
180	180
181		-**Connection:**
182	182
183		- (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
	205	+(% style="color:blue" %)**Connection:**
184	184
185		- (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
	207	+ (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND**
186	186
187		- (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
	209	+**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)**
188	188
	211	+**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)**
189	189
	213	+
190	190	In the PC, use below serial tool settings:
191	191
192	192	* Baud:  (% style="color:green" %)**9600**
...	...	@@ -201,8 +201,9 @@
201	201
202	202	[[image:1657329814315-101.png]]
203	203
	228	+
204	204	(((
205		-(% 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/]]
	230	+(% 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]]**
206	206	)))
207	207
208	208
...	...	@@ -209,9 +209,10 @@
209	209
210	210	=== 2.2.4 Use CoAP protocol to uplink data ===
211	211
212		-(% 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/]]
213	213
	238	+(% 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/]]**
214	214
	240	+
215	215	(((
216	216	**Use below commands:**
217	217	)))
...	...	@@ -220,21 +220,31 @@
220	220	(% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
221	221	)))
222	222	* (((
223		-(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
	249	+(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/  to set CoAP server address and port
224	224	)))
225	225	* (((
226		-(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
	252	+(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/  Set COAP resource path
	253	+
	254	+
	255	+
227	227	)))
228	228
229	229	(((
230	230	For parameter description, please refer to AT command set
	260	+
	261	+
231	231	)))
232	232
233	233	[[image:1657330452568-615.png]]
234	234
235	235
	267	+
	268	+(((
236	236	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.
237	237
	271	+
	272	+)))
	273	+
238	238	[[image:1657330472797-498.png]]
239	239
240	240
...	...	@@ -242,9 +242,9 @@
242	242	=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
243	243
244	244
245		-* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
246		-* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
247		-* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
	281	+* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
	282	+* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/  to set UDP server address and port
	283	+* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessary
248	248
249	249	[[image:1657330501006-241.png]]
250	250
...	...	@@ -256,13 +256,13 @@
256	256	=== 2.2.6 Use MQTT protocol to uplink data ===
257	257
258	258
259		-* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
260		-* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
261		-* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
262		-* (% style="color:blue" %)**AT+UNAME=UNAME                               **(%%)~/~/Set the username of MQTT
263		-* (% style="color:blue" %)**AT+PWD=PWD                                        **(%%)~/~/Set the password of MQTT
264		-* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/Set the sending topic of MQTT
265		-* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/Set the subscription topic of MQTT
	295	+* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
	296	+* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/  Set MQTT server address and port
	297	+* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/  Set up the CLIENT of MQTT
	298	+* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/  Set the username of MQTT
	299	+* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/  Set the password of MQTT
	300	+* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/  Set the sending topic of MQTT
	301	+* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/  Set the subscription topic of MQTT
266	266
267	267	[[image:1657249978444-674.png]]
268	268
...	...	@@ -279,8 +279,8 @@
279	279	=== 2.2.7 Use TCP protocol to uplink data ===
280	280
281	281
282		-* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
283		-* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
	318	+* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
	319	+* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/  to set TCP server address and port
284	284
285	285	[[image:image-20220709093918-1.png]]
286	286
...	...	@@ -291,75 +291,116 @@
291	291
292	292	=== 2.2.8 Change Update Interval ===
293	293
	330	+
294	294	User can use below command to change the (% style="color:green" %)**uplink interval**.
295	295
296		-* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
	333	+* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/  Set Update Interval to 600s
297	297
298	298	(((
	336	+
	337	+
	338	+
299	299	(% style="color:red" %)**NOTE:**
300		-)))
301	301
302		-(((
303		-(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
	341	+(% style="color:red" %)**1. By default, the device will send an uplink message every 1 hour.**
	342	+
	343	+(% style="color:red" %)**2. When the firmware version is v1.3.2 and later firmware:**
304	304	)))
305	305
	346	+(% 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).**
306	306
307	307
	349	+
308	308	== 2.3  Uplink Payload ==
309	309
310		-In this mode, uplink payload includes in total 14 bytes
311	311
	353	+=== 2.3.1  Before Firmware v1.3.2 ===
312	312
313		-(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
314		-|=(% style="width: 80px;" %)(((
	355	+
	356	+In this mode, uplink payload includes in total 14 bytes
	357	+
	358	+(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
	359	+|=(% style="width: 60px;" %)(((
315	315	**Size(bytes)**
316		-)))|=(% style="width: 80px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 110px;" %)**1**|=(% style="width: 110px;" %)**2**|=(% style="width: 70px;" %)**1**
	361	+)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1**
317	317	|(% 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"]]
318	318
319	319	(((
320		-If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
	365	+If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
321	321	)))
322	322
323	323
324	324	[[image:1657331036973-987.png]]
325	325
326		-(((
	371	+
	372	+
	373	+The payload is **ASCII** string, representative same HEX:
	374	+
	375	+(% style="background-color:yellow" %)**0x 724031556159 0064 0c6c 19 0292 00 **
	376	+
	377	+**where :**
	378	+
	379	+* (% style="color:#037691" %)**Device ID:**(%%) 0x724031556159 = 724031556159
	380	+
	381	+* (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
	382	+
	383	+* (% style="color:#037691" %)**BAT:** (%%) 0x0c6c = 3180 mV = 3.180V
	384	+
	385	+* (% style="color:#037691" %)**Signal:**(%%)  0x19 = 25
	386	+
	387	+* (% style="color:#037691" %)**Distance:**  (%%)0x0292= 658 mm
	388	+
	389	+* (% style="color:#037691" %)**Interrupt:**(%%) 0x00 = 0
	390	+
	391	+
	392	+=== 2.3.2  Since firmware v1.3.2 ===
	393	+
	394	+
	395	+In this mode, uplink payload includes 69 bytes in total by default.
	396	+
	397	+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.
	398	+
	399	+(% border="1" style="background-color:#ffffcc; color:green; width:490px" %)
	400	+|=(% 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**
	401	+|=(% 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.......
	402	+
	403	+If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
	404	+
	405	+[[image:image-20220908175246-1.png]]
	406	+
	407	+
327	327	The payload is ASCII string, representative same HEX:
328		-)))
329	329
330		-(((
331		-0x72403155615900640c6c19029200 where:
332		-)))
	410	+**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 (%%)**
333	333
334		-* (((
335		-Device ID: 0x724031556159 = 724031556159
336		-)))
337		-* (((
338		-Version: 0x0064=100=1.0.0
339		-)))
	412	+**where:**
340	340
341		-* (((
342		-BAT: 0x0c6c = 3180 mV = 3.180V
343		-)))
344		-* (((
345		-Signal: 0x19 = 25
346		-)))
347		-* (((
348		-Distance: 0x0292= 658 mm
349		-)))
350		-* (((
351		-Interrupt: 0x00 = 0
	414	+* (% style="color:#037691" %)**Device ID:**(%%) f867787050213317 = f867787050213317
352	352
	416	+* (% style="color:#037691" %)**Version:**(%%) 0x0084=132=1.3.2
353	353
	418	+* (% style="color:#037691" %)**BAT:**(%%)  0x0cf4 = 3316 mV = 3.316V
354	354
355		-
356		-)))
	420	+* (% style="color:#037691" %)**Singal:**(%%)  0x1e = 30
357	357
	422	+* (% style="color:#037691" %)**Mod:**(%%)**     **0x01 = 1
	423	+
	424	+* (% style="color:#037691" %)**Interrupt:**(%%) 0x00= 0
	425	+
	426	+* (% style="color:#037691" %)**Distance:**(%%) 0x0039= 57 = 57
	427	+
	428	+* (% style="color:#037691" %)**Time stamp:**(%%) 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
	429	+
	430	+* (% style="color:#037691" %)**Distance,Time stamp:**(%%) 00396319baf0
	431	+
	432	+* (% style="color:#037691" %)**8 sets of recorded data: Distance,Time stamp :**(%%) //**00396319ba3c**//,.......
	433	+
358	358	== 2.4  Payload Explanation and Sensor Interface ==
359	359
360	360
361	361	=== 2.4.1  Device ID ===
362	362
	439	+
363	363	(((
364	364	By default, the Device ID equal to the last 6 bytes of IMEI.
365	365	)))
...	...	@@ -366,10 +366,12 @@
366	366
367	367	(((
368	368	User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
	446	+
	447	+
369	369	)))
370	370
371	371	(((
372		-**Example:**
	451	+(% style="color:blue" %)**Example :**
373	373	)))
374	374
375	375	(((
...	...	@@ -377,13 +377,26 @@
377	377	)))
378	378
379	379	(((
380		-The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
	459	+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.
381	381	)))
382	382
383	383
	463	+(% style="color:red" %)**NOTE: When the firmware version is v1.3.2 and later firmware:**
384	384
	465	+(% style="color:red" %)**By default, the Device ID equal to the last 15 bits of IMEI.**
	466	+
	467	+User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
	468	+
	469	+
	470	+(% style="color:blue" %)**Example :**
	471	+
	472	+AT+DEUI=868411056754138
	473	+
	474	+
	475	+
385	385	=== 2.4.2  Version Info ===
386	386
	478	+
387	387	(((
388	388	Specify the software version: 0x64=100, means firmware version 1.00.
389	389	)))
...	...	@@ -396,6 +396,7 @@
396	396
397	397	=== 2.4.3  Battery Info ===
398	398
	491	+
399	399	(((
400	400	Ex1: 0x0B45 = 2885mV
401	401	)))
...	...	@@ -408,6 +408,7 @@
408	408
409	409	=== 2.4.4  Signal Strength ===
410	410
	504	+
411	411	(((
412	412	NB-IoT Network signal Strength.
413	413	)))
...	...	@@ -440,9 +440,12 @@
440	440
441	441	=== 2.4.5  Distance ===
442	442
	537	+
443	443	Get the distance. Flat object range 280mm - 7500mm.
444	444
	540	+(((
445	445	For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
	542	+)))
446	446
447	447	(((
448	448	(((
...	...	@@ -460,6 +460,7 @@
460	460
461	461	=== 2.4.6  Digital Interrupt ===
462	462
	560	+
463	463	(((
464	464	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.
465	465	)))
...	...	@@ -469,7 +469,7 @@
469	469	)))
470	470
471	471	(((
472		-(% 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]])**.**
	570	+(% 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]])**.**
473	473	)))
474	474
475	475
...	...	@@ -494,6 +494,7 @@
494	494
495	495	=== 2.4.7  ​+5V Output ===
496	496
	595	+
497	497	(((
498	498	NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling.
499	499	)))
...	...	@@ -501,10 +501,14 @@
501	501
502	502	(((
503	503	The 5V output time can be controlled by AT Command.
	603	+
	604	+
504	504	)))
505	505
506	506	(((
507	507	(% style="color:blue" %)**AT+5VT=1000**
	609	+
	610	+
508	508	)))
509	509
510	510	(((
...	...	@@ -515,6 +515,7 @@
515	515
516	516	== 2.5  Downlink Payload ==
517	517
	621	+
518	518	By default, NDDS75 prints the downlink payload to console port.
519	519
520	520	[[image:image-20220709100028-1.png]]
...	...	@@ -565,120 +565,96 @@
565	565
566	566
567	567
568		-== 2.6  ​LED Indicator ==
	672	+== 2.6  Distance alarm function(Since firmware v1.3.2) ==
569	569
570	570
571		-The NDDS75 has an internal LED which is to show the status of different state.
	675	+(% style="color:blue" %)** ➢ AT Command:**
572	572
	677	+(% style="color:#037691" %)** AT+ LDDSALARM=min,max**
573	573
574		-* When power on, NDDS75 will detect if sensor probe is connected, if probe detected, LED will blink four times. (no blinks in this step is no probe)
575		-* Then the LED will be on for 1 second means device is boot normally.
576		-* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
577		-* For each uplink probe, LED will be on for 500ms.
	679	+² When min=0, and max≠0, Alarm higher than max
578	578
579		-(((
580		-
581		-)))
	681	+² When min≠0, and max=0, Alarm lower than min
582	582
	683	+² When min≠0 and max≠0, Alarm higher than max or lower than min
583	583
584	584
585		-== 2.7  ​Firmware Change Log ==
	686	+(% style="color:blue" %)** Example:**
586	586
	688	+**AT+ LDDSALARM=260,2000**  ~/~/ Alarm when distance lower than 260.
587	587
588		-Download URL & Firmware Change log
589	589
590		-(((
591		-[[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/]]
592		-)))
593	593
	692	+== 2.7  Set the number of data to be uploaded and the recording time ==
594	594
595		-Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
596	596
	695	+(% style="color:blue" %)** ➢ AT Command:**
597	597
	697	+* (% 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)
	698	+* (% 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.
598	598
599		-== 2.8  ​Battery Analysis ==
	700	+ The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
600	600
601		-=== 2.8.1  ​Battery Type ===
	702	+[[image:image-20221009001114-1.png||height="687" width="955"]]
602	602
603	603
604		-(((
605		-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.
606		-)))
607	607
608		-(((
609		-The battery is designed to last for several years depends on the actually use environment and update interval.
610		-)))
	706	+== 2.8  Read or Clear cached data ==
611	611
612		-(((
613		-The battery related documents as below:
614		-)))
615	615
616		-* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
617		-* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
618		-* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
	709	+(% style="color:blue" %)** ➢ AT Command:**
619	619
620		-(((
621		-[[image:image-20220709101450-2.png]]
622		-)))
	711	+* (% style="color:#037691" %)** AT+CDP ** (%%) ~/~/  Read cached data
	712	+* (% style="color:#037691" %)** AT+CDP=0**  (%%) ~/~/  Clear cached data
623	623
	714	+[[image:image-20220908175333-2.png]]
624	624
625	625
626		-=== 2.8.2  Power consumption Analyze ===
627	627
628		-(((
629		-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.
630		-)))
	718	+== 2.9  ​LED Indicator ==
631	631
632	632
633		-(((
634		-Instruction to use as below:
635		-)))
	721	+The NDDS75 has an internal LED which is to show the status of different state.
636	636
637		-(((
638		-(% style="color:blue" %)**Step 1:  **(%%)Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/]]
639		-)))
640	640
	724	+* When power on, NDDS75 will detect if sensor probe is connected, if probe detected, LED will blink four times. (no blinks in this step is no probe)
	725	+* Then the LED will be on for 1 second means device is boot normally.
	726	+* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
	727	+* For each uplink probe, LED will be on for 500ms.
641	641
642	642	(((
643		-(% style="color:blue" %)**Step 2: **(%%) Open it and choose
	730	+
644	644	)))
645	645
646		-* (((
647		-Product Model
648		-)))
649		-* (((
650		-Uplink Interval
651		-)))
652		-* (((
653		-Working Mode
654		-)))
655	655
656		-(((
657		-And the Life expectation in difference case will be shown on the right.
658		-)))
659	659
660		-[[image:image-20220709110451-3.png]]
	735	+== 2.10  ​Firmware Change Log ==
661	661
662	662
	738	+(((
	739	+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]]
	740	+)))
663	663
664		-=== 2.8.3  ​Battery Note ===
	742	+(((
	743	+
	744	+)))
665	665
666	666	(((
667		-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.
	747	+Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
668	668	)))
669	669
670	670
671	671
672		-=== 2.8.4  Replace the battery ===
	752	+== 2.11 Battery & Power Consumption ==
673	673
674		-(((
675		-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).
676		-)))
677	677
	755	+PS-LB-NA uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace.
678	678
	757	+[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] .
679	679
680	680	= 3. ​ Access NB-IoT Module =
681	681
	761	+
682	682	(((
683	683	Users can directly access the AT command set of the NB-IoT module.
684	684	)))
...	...	@@ -685,6 +685,8 @@
685	685
686	686	(((
687	687	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/]]
	768	+
	769	+
688	688	)))
689	689
690	690	[[image:1657333200519-600.png]]
...	...	@@ -693,84 +693,103 @@
693	693
694	694	= 4.  Using the AT Commands =
695	695
	778	+
696	696	== 4.1  Access AT Commands ==
697	697
698		-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/]]
699	699
	782	+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]]
700	700
701		-AT+<CMD>?  : Help on <CMD>
702	702
703		-AT+<CMD>         : Run <CMD>
	785	+AT+<CMD>?  :  Help on <CMD>
704	704
705		-AT+<CMD>=<value> : Set the value
	787	+AT+<CMD>         :  Run <CMD>
706	706
707		-AT+<CMD>=?  : Get the value
	789	+AT+<CMD>=<value> :  Set the value
708	708
	791	+AT+<CMD>=?  :  Get the value
709	709
	793	+
710	710	(% style="color:#037691" %)**General Commands**(%%)
711	711
712		-AT  : Attention
	796	+AT  :  Attention
713	713
714		-AT?  : Short Help
	798	+AT?  :  Short Help
715	715
716		-ATZ  : MCU Reset
	800	+ATZ  :  MCU Reset
717	717
718		-AT+TDC  : Application Data Transmission Interval
	802	+AT+TDC  :  Application Data Transmission Interval
719	719
720		-AT+CFG  : Print all configurations
	804	+AT+CFG  :  Print all configurations
721	721
722		-AT+CFGMOD           : Working mode selection
	806	+AT+CFGMOD           :  Working mode selection
723	723
724		-AT+INTMOD            : Set the trigger interrupt mode
	808	+AT+INTMOD            :  Set the trigger interrupt mode
725	725
726		-AT+5VT  : Set extend the time of 5V power
	810	+AT+5VT  :  Set extend the time of 5V power
727	727
728		-AT+PRO  : Choose agreement
	812	+AT+PRO  :  Choose agreement
729	729
730		-AT+WEIGRE  : Get weight or set weight to 0
	814	+AT+WEIGRE  :  Get weight or set weight to 0
731	731
732		-AT+WEIGAP  : Get or Set the GapValue of weight
	816	+AT+WEIGAP  :  Get or Set the GapValue of weight
733	733
734		-AT+RXDL  : Extend the sending and receiving time
	818	+AT+RXDL  :  Extend the sending and receiving time
735	735
736		-AT+CNTFAC  : Get or set counting parameters
	820	+AT+CNTFAC  :  Get or set counting parameters
737	737
738		-AT+SERVADDR  : Server Address
	822	+AT+SERVADDR  :  Server Address
739	739
	824	+AT+TR  :  Get or Set record time"
740	740
	826	+AT+APN     :  Get or set the APN
	827	+
	828	+AT+FBAND  :  Get or Set whether to automatically modify the frequency band
	829	+
	830	+AT+DNSCFG  : Get or Set DNS Server
	831	+
	832	+AT+GETSENSORVALUE   :  Returns the current sensor measurement
	833	+
	834	+AT+NOUD  :  Get or Set the number of data to be uploaded
	835	+
	836	+AT+CDP     :  Read or Clear cached data
	837	+
	838	+AT+LDDSALARM :  Get or Set alarm of distance
	839	+
	840	+
741	741	(% style="color:#037691" %)**COAP Management**
742	742
743		-AT+URI            : Resource parameters
	843	+AT+URI            :  Resource parameters
744	744
745	745
746	746	(% style="color:#037691" %)**UDP Management**
747	747
748		-AT+CFM          : Upload confirmation mode (only valid for UDP)
	848	+AT+CFM          :  Upload confirmation mode (only valid for UDP)
749	749
750	750
751	751	(% style="color:#037691" %)**MQTT Management**
752	752
753		-AT+CLIENT               : Get or Set MQTT client
	853	+AT+CLIENT  :  Get or Set MQTT client
754	754
755		-AT+UNAME  : Get or Set MQTT Username
	855	+AT+UNAME  :  Get or Set MQTT Username
756	756
757		-AT+PWD                  : Get or Set MQTT password
	857	+AT+PWD  :  Get or Set MQTT password
758	758
759		-AT+PUBTOPIC  : Get or Set MQTT publish topic
	859	+AT+PUBTOPIC  :  Get or Set MQTT publish topic
760	760
761		-AT+SUBTOPIC  : Get or Set MQTT subscription topic
	861	+AT+SUBTOPIC  :  Get or Set MQTT subscription topic
762	762
763	763
764	764	(% style="color:#037691" %)**Information**
765	765
766		-AT+FDR  : Factory Data Reset
	866	+AT+FDR  :  Factory Data Reset
767	767
768		-AT+PWORD  : Serial Access Password
	868	+AT+PWORD  :  Serial Access Password
769	769
770	770
771	771
772	772	= ​5.  FAQ =
773	773
	874	+
774	774	== 5.1 ​ How to Upgrade Firmware ==
775	775
776	776
...	...	@@ -783,7 +783,7 @@
783	783	)))
784	784
785	785	(((
786		-(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.
	887	+(% style="color:red" %)**Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.**
787	787	)))
788	788
789	789
...	...	@@ -790,6 +790,7 @@
790	790
791	791	= 6.  Trouble Shooting =
792	792
	894	+
793	793	== 6.1  ​Connection problem when uploading firmware ==
794	794
795	795
...	...	@@ -805,6 +805,7 @@
805	805
806	806	== 6.2  AT Command input doesn't work ==
807	807
	910	+
808	808	(((
809	809	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.
810	810
...	...	@@ -830,7 +830,7 @@
830	830
831	831	(% style="color:#037691" %)**Package Includes**:
832	832
833		-* NSE01 NB-IoT Distance Detect Sensor Node x 1
	936	+* NDDS75 NB-IoT Distance Detect Sensor Node x 1
834	834	* External antenna x 1
835	835	)))
836	836
...	...	@@ -837,9 +837,9 @@
837	837	(((
838	838
839	839
	943	+
840	840	(% style="color:#037691" %)**Dimension and weight**:
841	841
842		-
843	843	* Device Size: 13.0 x 5 x 4.5 cm
844	844	* Device Weight: 150g
845	845	* Package Size / pcs : 15 x 12x 5.5 cm
...	...	@@ -855,5 +855,6 @@
855	855
856	856	= 9.  Support =
857	857
	961	+
858	858	* 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.
859	859	* 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