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