Summary

• Page properties (1 modified, 0 added, 0 removed)
• Attachments (0 modified, 0 added, 1 removed)
  • 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	(((
...	...	@@ -53,6 +53,7 @@
53	53	[[image:1657327959271-447.png]]
54	54
55	55
	57	+
56	56	== 1.2 ​ Features ==
57	57
58	58
...	...	@@ -69,8 +69,6 @@
69	69	* Micro SIM card slot for NB-IoT SIM
70	70	* 8500mAh Battery for long term use
71	71
72		-
73		-
74	74	== 1.3  Specification ==
75	75
76	76
...	...	@@ -81,12 +81,12 @@
81	81
82	82	(% style="color:#037691" %)**NB-IoT Spec:**
83	83
84		-* B1 @H-FDD: 2100MHz
85		-* B3 @H-FDD: 1800MHz
86		-* B8 @H-FDD: 900MHz
87		-* B5 @H-FDD: 850MHz
88		-* B20 @H-FDD: 800MHz
89		-* B28 @H-FDD: 700MHz
	84	+* - B1 @H-FDD: 2100MHz
	85	+* - B3 @H-FDD: 1800MHz
	86	+* - B8 @H-FDD: 900MHz
	87	+* - B5 @H-FDD: 850MHz
	88	+* - B20 @H-FDD: 800MHz
	89	+* - B28 @H-FDD: 700MHz
90	90
91	91	(% style="color:#037691" %)**Battery:**
92	92
...	...	@@ -101,8 +101,6 @@
101	101	* STOP Mode: 10uA @ 3.3v
102	102	* Max transmit power: 350mA@3.3v
103	103
104		-
105		-
106	106	== ​1.4  Applications ==
107	107
108	108
...	...	@@ -117,6 +117,8 @@
117	117	​
118	118
119	119
	118	+
	119	+
120	120	== 1.5  Pin Definitions ==
121	121
122	122
...	...	@@ -123,8 +123,10 @@
123	123	[[image:1657328609906-564.png]]
124	124
125	125
	126	+
126	126	= 2.  Use NDDS75 to communicate with IoT Server =
127	127
	129	+
128	128	== 2.1  How it works ==
129	129
130	130
...	...	@@ -147,8 +147,10 @@
147	147
148	148	)))
149	149
	152	+
150	150	== 2.2 ​ Configure the NDDS75 ==
151	151
	155	+
152	152	=== 2.2.1 Test Requirement ===
153	153
154	154
...	...	@@ -168,6 +168,7 @@
168	168	[[image:1657328756309-230.png]]
169	169
170	170
	175	+
171	171	=== 2.2.2 Insert SIM card ===
172	172
173	173
...	...	@@ -183,6 +183,7 @@
183	183	[[image:1657328884227-504.png]]
184	184
185	185
	191	+
186	186	=== 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
187	187
188	188
...	...	@@ -195,13 +195,13 @@
195	195	[[image:image-20220709092052-2.png]]
196	196
197	197
198		-(% style="color:blue" %)**Connection:**
	204	+**Connection:**
199	199
200		- (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND**
	206	+ (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
201	201
202		-**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)**
	208	+ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
203	203
204		-**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)**
	210	+ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
205	205
206	206
207	207	In the PC, use below serial tool settings:
...	...	@@ -224,6 +224,7 @@
224	224	)))
225	225
226	226
	233	+
227	227	=== 2.2.4 Use CoAP protocol to uplink data ===
228	228
229	229
...	...	@@ -238,10 +238,10 @@
238	238	(% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
239	239	)))
240	240	* (((
241		-(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/  to set CoAP server address and port
	248	+(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
242	242	)))
243	243	* (((
244		-(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/  Set COAP resource path
	251	+(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
245	245
246	246
247	247
...	...	@@ -266,12 +266,13 @@
266	266	[[image:1657330472797-498.png]]
267	267
268	268
	276	+
269	269	=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
270	270
271	271
272		-* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
273		-* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/  to set UDP server address and port
274		-* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessary
	280	+* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
	281	+* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
	282	+* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
275	275
276	276	[[image:1657330501006-241.png]]
277	277
...	...	@@ -279,16 +279,17 @@
279	279	[[image:1657330533775-472.png]]
280	280
281	281
	290	+
282	282	=== 2.2.6 Use MQTT protocol to uplink data ===
283	283
284	284
285		-* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
286		-* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/  Set MQTT server address and port
287		-* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/  Set up the CLIENT of MQTT
288		-* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/  Set the username of MQTT
289		-* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/  Set the password of MQTT
290		-* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/  Set the sending topic of MQTT
291		-* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/  Set the subscription topic of MQTT
	294	+* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
	295	+* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
	296	+* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
	297	+* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
	298	+* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
	299	+* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/Set the sending topic of MQTT
	300	+* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/Set the subscription topic of MQTT
292	292
293	293	[[image:1657249978444-674.png]]
294	294
...	...	@@ -301,11 +301,12 @@
301	301	)))
302	302
303	303
	313	+
304	304	=== 2.2.7 Use TCP protocol to uplink data ===
305	305
306	306
307		-* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
308		-* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/  to set TCP server address and port
	317	+* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
	318	+* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
309	309
310	310	[[image:image-20220709093918-1.png]]
311	311
...	...	@@ -313,42 +313,42 @@
313	313	[[image:image-20220709093918-2.png]]
314	314
315	315
	326	+
316	316	=== 2.2.8 Change Update Interval ===
317	317
318	318
319	319	User can use below command to change the (% style="color:green" %)**uplink interval**.
320	320
321		-* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/  Set Update Interval to 600s
	332	+* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
322	322
323	323	(((
324		-
	335	+(% style="color:red" %)**NOTE 1: By default, the device will send an uplink message every 1 hour.**
325	325
326		-
327		-(% style="color:red" %)**NOTE:**
328		-
329		-(% style="color:red" %)**1. By default, the device will send an uplink message every 1 hour.**
330		-
331		-(% style="color:red" %)**2. When the firmware version is v1.3.2 and later firmware:**
	337	+
332	332	)))
333	333
	340	+(% style="color:red" %)**NOTE 2: When the firmware version is v1.3.2 and later firmware:**
	341	+
334	334	(% 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).**
335	335
336	336
	345	+
337	337	== 2.3  Uplink Payload ==
338	338
339		-=== 2.3.1  Before Firmware v1.3.2 ===
340	340
	349	+=== 2.3.1  Before Firmware 1.3.2 ===
341	341
	351	+
342	342	In this mode, uplink payload includes in total 14 bytes
343	343
344		-(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:440px" %)
345		-|=(% style="width: 60px;background-color:#D9E2F3;color:#0070C0" %)(((
	354	+(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
	355	+|=(% style="width: 60px;" %)(((
346	346	**Size(bytes)**
347		-)))|=(% style="width: 60px;background-color:#D9E2F3;color:#0070C0" %)**6**|=(% style="width: 35px;background-color:#D9E2F3;color:#0070C0" %)2|=(% style="width: 35px;background-color:#D9E2F3;color:#0070C0" %)**2**|=(% style="width: 80px;background-color:#D9E2F3;color:#0070C0" %)**1**|=(% style="width: 100px;background-color:#D9E2F3;color:#0070C0" %)**2**|=(% style="width: 60px;background-color:#D9E2F3;color:#0070C0" %)**1**
	357	+)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1**
348	348	|(% 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"]]
349	349
350	350	(((
351		-If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
	361	+If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
352	352	)))
353	353
354	354
...	...	@@ -355,36 +355,49 @@
355	355	[[image:1657331036973-987.png]]
356	356
357	357
	368	+(((
358	358	The payload is **ASCII** string, representative same HEX:
	370	+)))
359	359
360		-(% style="background-color:yellow" %)**0x 724031556159 0064 0c6c 19 0292 00 **
	372	+(((
	373	+0x72403155615900640c6c19029200 where:
	374	+)))
361	361
362		-**where :**
	376	+* (((
	377	+Device ID: 0x724031556159 = 724031556159
	378	+)))
	379	+* (((
	380	+Version:  0x0064=100=1.0.0
	381	+)))
363	363
364		-* (% style="color:#037691" %)**Device ID:**(%%) 0x724031556159 = 724031556159
	383	+* (((
	384	+BAT:  0x0c6c = 3180 mV = 3.180V
	385	+)))
	386	+* (((
	387	+Signal: 0x19 = 25
	388	+)))
	389	+* (((
	390	+Distance: 0x0292= 658 mm
	391	+)))
	392	+* (((
	393	+Interrupt: 0x00 = 0
365	365
366		-* (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
367	367
368		-* (% style="color:#037691" %)**BAT:** (%%) 0x0c6c = 3180 mV = 3.180V
369	369
370		-* (% style="color:#037691" %)**Signal:**(%%)  0x19 = 25
371	371
372		-* (% style="color:#037691" %)**Distance:**  (%%)0x0292= 658 mm
	398	+
	399	+)))
373	373
374		-* (% style="color:#037691" %)**Interrupt:**(%%) 0x00 = 0
	401	+=== **2.3.2  Since firmware v1.3.2** ===
375	375
376	376
377		-
378		-=== 2.3.2  Since firmware v1.3.2 ===
379		-
380		-
381	381	In this mode, uplink payload includes 69 bytes in total by default.
382	382
383	383	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.
384	384
385		-(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:490px" %)
386		-|=(% style="width: 60px;background-color:#D9E2F3;color:#0070C0" %)**Size(bytes)**|(% style="background-color:#d9e2f3; color:#0070c0; width:40px" %)**8**|(% style="background-color:#d9e2f3; color:#0070c0; width:25px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:25px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:60px" %)**1**|(% style="background-color:#d9e2f3; color:#0070c0; width:25px" %)**1**|(% style="background-color:#d9e2f3; color:#0070c0; width:40px" %)**1**|(% style="background-color:#d9e2f3; color:#0070c0; width:40px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:70px" %)**4**|(% style="background-color:#d9e2f3; color:#0070c0; width:40px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:60px" %)**4**
387		-|=(% 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.......
	408	+(% border="2" style="background-color:#ffffcc; color:green; width:896px" %)
	409	+|(% style="width:95px" %)**Size(bytes)**|(% style="width:84px" %)**8**|(% style="width:44px" %)2|(% style="width:48px" %)2|(% style="width:123px" %)1|(% style="width:55px" %)1|(% style="width:80px" %)1|(% style="width:77px" %)2|(% style="width:94px" %)4|(% style="width:77px" %)2|(% style="width:116px" %)4
	410	+|(% 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.......
388	388
389	389	If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
390	390
...	...	@@ -393,34 +393,26 @@
393	393
394	394	The payload is ASCII string, representative same HEX:
395	395
396		-**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 (%%)**
	419	+0x(% style="color:red" %)f867787050213317(% style="color:blue" %)0084(% style="color:green" %)0cf4(% style="color:red" %)1e(% style="color:blue" %)01(% style="color:green" %)00(% style="color:red" %)**//00396319bb32//**00396319baf0//**00396319ba3c**//00396319b988//**00396319b8d4**//00396319b820//**00396319b76c**//00396319b6b8//**00396319b604**//(%%) where:
397	397
398		-**where:**
	421	+* (% style="color:green" %)Device ID: f867787050213317 = f867787050213317
	422	+* (% style="color:red" %)Version: 0x0084=132=1.3.2
	423	+* (% style="color:green" %)BAT: 0x0cf4 = 3316 mV = 3.316V
	424	+* (% style="color:blue" %)Singal: 0x1e = 30
	425	+* (% style="color:red" %)Mod: 0x01 = 1
	426	+* Interrupt: 0x00= 0
	427	+* Distance: 0x0039= 57 = 57
	428	+* Time stamp : 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
	429	+* Distance,Time stamp : 00396319baf0
	430	+* (% style="color:red" %) 8 sets of recorded data: Distance,Time stamp : //**00396319ba3c**//,.......
399	399
400		-* (% style="color:#037691" %)**Device ID:**(%%) f867787050213317 = f867787050213317
401	401
402		-* (% style="color:#037691" %)**Version:**(%%) 0x0084=132=1.3.2
403	403
404		-* (% style="color:#037691" %)**BAT:**(%%)  0x0cf4 = 3316 mV = 3.316V
405	405
406		-* (% style="color:#037691" %)**Singal:**(%%)  0x1e = 30
407	407
408		-* (% style="color:#037691" %)**Mod:**(%%)**     **0x01 = 1
409		-
410		-* (% style="color:#037691" %)**Interrupt:**(%%) 0x00= 0
411		-
412		-* (% style="color:#037691" %)**Distance:**(%%) 0x0039= 57 = 57
413		-
414		-* (% style="color:#037691" %)**Time stamp:**(%%) 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
415		-
416		-* (% style="color:#037691" %)**Distance,Time stamp:**(%%) 00396319baf0
417		-
418		-* (% style="color:#037691" %)**8 sets of recorded data: Distance,Time stamp :**(%%) //**00396319ba3c**//,.......
419		-
420		-
421		-
422	422	== 2.4  Payload Explanation and Sensor Interface ==
423	423
	438	+
424	424	=== 2.4.1  Device ID ===
425	425
426	426
...	...	@@ -459,6 +459,7 @@
459	459	AT+DEUI=868411056754138
460	460
461	461
	477	+
462	462	=== 2.4.2  Version Info ===
463	463
464	464
...	...	@@ -471,6 +471,7 @@
471	471	)))
472	472
473	473
	490	+
474	474	=== 2.4.3  Battery Info ===
475	475
476	476
...	...	@@ -483,6 +483,7 @@
483	483	)))
484	484
485	485
	503	+
486	486	=== 2.4.4  Signal Strength ===
487	487
488	488
...	...	@@ -515,6 +515,7 @@
515	515	)))
516	516
517	517
	536	+
518	518	=== 2.4.5  Distance ===
519	519
520	520
...	...	@@ -534,6 +534,10 @@
534	534
535	535	)))
536	536
	556	+(((
	557	+
	558	+)))
	559	+
537	537	=== 2.4.6  Digital Interrupt ===
538	538
539	539
...	...	@@ -546,7 +546,7 @@
546	546	)))
547	547
548	548	(((
549		-(% 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]])**.**
	572	+(% 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]])**.**
550	550	)))
551	551
552	552
...	...	@@ -568,6 +568,7 @@
568	568	)))
569	569
570	570
	594	+
571	571	=== 2.4.7  ​+5V Output ===
572	572
573	573
...	...	@@ -593,16 +593,13 @@
593	593	)))
594	594
595	595
	620	+
596	596	== 2.5  Downlink Payload ==
597	597
598	598
599	599	By default, NDDS75 prints the downlink payload to console port.
600	600
601		-(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:520px" %)
602		-|(% style="background-color:#d9e2f3; color:#0070c0; width:208px" %)**Downlink Control Type**|(% style="background-color:#d9e2f3; color:#0070c0; width:56px" %)**FPort**|(% style="background-color:#d9e2f3; color:#0070c0; width:100px" %)**Type Code**|(% style="background-color:#d9e2f3; color:#0070c0; width:154px" %)**Downlink payload size(bytes)**
603		-|(% style="width:208px" %)TDC (Transmit Time Interval)|(% style="width:56px" %)Any|(% style="width:100px" %)01|(% style="width:154px" %)4
604		-|(% style="width:208px" %)RESET|(% style="width:56px" %)Any|(% style="width:100px" %)04|(% style="width:154px" %)2
605		-|(% style="width:208px" %)INTMOD|(% style="width:56px" %)Any|(% style="width:100px" %)06|(% style="width:154px" %)4
	626	+[[image:image-20220709100028-1.png]]
606	606
607	607
608	608	(((
...	...	@@ -649,6 +649,7 @@
649	649	)))
650	650
651	651
	673	+
652	652	== 2.6  Distance alarm function(Since firmware v1.3.2) ==
653	653
654	654
...	...	@@ -668,17 +668,16 @@
668	668	**AT+ LDDSALARM=260,2000**  ~/~/ Alarm when distance lower than 260.
669	669
670	670
	693	+
671	671	== 2.7  Set the number of data to be uploaded and the recording time ==
672	672
673	673
674	674	(% style="color:blue" %)** ➢ AT Command:**
675	675
676		-* (% 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)
677		-* (% 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.
	699	+(% 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)
678	678
679		- The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
	701	+(% 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.
680	680
681		-[[image:image-20221009001114-1.png||height="687" width="955"]]
682	682
683	683
684	684	== 2.8  Read or Clear cached data ==
...	...	@@ -686,12 +686,16 @@
686	686
687	687	(% style="color:blue" %)** ➢ AT Command:**
688	688
689		-* (% style="color:#037691" %)** AT+CDP ** (%%) ~/~/  Read cached data
690		-* (% style="color:#037691" %)** AT+CDP=0**  (%%) ~/~/  Clear cached data
	710	+(% style="color:#037691" %)** AT+CDP ** (%%) ~/~/ Read cached data
691	691
	712	+
692	692	[[image:image-20220908175333-2.png]]
693	693
694	694
	716	+(% style="color:#037691" %)** AT+CDP=0**  (%%) ~/~/ Clear cached data
	717	+
	718	+
	719	+
695	695	== 2.9  ​LED Indicator ==
696	696
697	697
...	...	@@ -708,6 +708,7 @@
708	708	)))
709	709
710	710
	736	+
711	711	== 2.10  ​Firmware Change Log ==
712	712
713	713
...	...	@@ -716,18 +716,100 @@
716	716	)))
717	717
718	718	(((
	745	+
	746	+)))
	747	+
	748	+(((
719	719	Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
720	720	)))
721	721
722	722
723		-== 2.11 Battery & Power Consumption ==
724	724
	754	+== 2.11  ​Battery Analysis ==
725	725
726		-NDDS75 uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace.
727	727
728		-[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] .
	757	+=== 2.11.1  ​Battery Type ===
729	729
730	730
	760	+(((
	761	+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.
	762	+)))
	763	+
	764	+(((
	765	+The battery is designed to last for several years depends on the actually use environment and update interval.
	766	+)))
	767	+
	768	+(((
	769	+The battery related documents as below:
	770	+)))
	771	+
	772	+* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
	773	+* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
	774	+* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
	775	+
	776	+(((
	777	+[[image:image-20220709101450-2.png]]
	778	+)))
	779	+
	780	+
	781	+
	782	+=== 2.11.2  Power consumption Analyze ===
	783	+
	784	+
	785	+(((
	786	+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.
	787	+)))
	788	+
	789	+
	790	+(((
	791	+Instruction to use as below:
	792	+)))
	793	+
	794	+(((
	795	+(% 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/]]
	796	+)))
	797	+
	798	+
	799	+(((
	800	+(% style="color:blue" %)**Step 2: **(%%) Open it and choose
	801	+)))
	802	+
	803	+* (((
	804	+Product Model
	805	+)))
	806	+* (((
	807	+Uplink Interval
	808	+)))
	809	+* (((
	810	+Working Mode
	811	+)))
	812	+
	813	+(((
	814	+And the Life expectation in difference case will be shown on the right.
	815	+)))
	816	+
	817	+[[image:image-20220709110451-3.png]]
	818	+
	819	+
	820	+
	821	+=== 2.11.3  ​Battery Note ===
	822	+
	823	+
	824	+(((
	825	+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.
	826	+)))
	827	+
	828	+
	829	+
	830	+=== 2.11.4  Replace the battery ===
	831	+
	832	+
	833	+(((
	834	+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).
	835	+)))
	836	+
	837	+
	838	+
731	731	= 3. ​ Access NB-IoT Module =
732	732
733	733
...	...	@@ -744,8 +744,10 @@
744	744	[[image:1657333200519-600.png]]
745	745
746	746
	855	+
747	747	= 4.  Using the AT Commands =
748	748
	858	+
749	749	== 4.1  Access AT Commands ==
750	750
751	751
...	...	@@ -752,94 +752,96 @@
752	752	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]]
753	753
754	754
755		-AT+<CMD>?  :  Help on <CMD>
	865	+AT+<CMD>?  : Help on <CMD>
756	756
757		-AT+<CMD>         :  Run <CMD>
	867	+AT+<CMD>         : Run <CMD>
758	758
759		-AT+<CMD>=<value> :  Set the value
	869	+AT+<CMD>=<value> : Set the value
760	760
761		-AT+<CMD>=?  :  Get the value
	871	+AT+<CMD>=?  : Get the value
762	762
763	763
764	764	(% style="color:#037691" %)**General Commands**(%%)
765	765
766		-AT  :  Attention
	876	+AT  : Attention
767	767
768		-AT?  :  Short Help
	878	+AT?  : Short Help
769	769
770		-ATZ  :  MCU Reset
	880	+ATZ  : MCU Reset
771	771
772		-AT+TDC  :  Application Data Transmission Interval
	882	+AT+TDC  : Application Data Transmission Interval
773	773
774		-AT+CFG  :  Print all configurations
	884	+AT+CFG  : Print all configurations
775	775
776		-AT+CFGMOD           :  Working mode selection
	886	+AT+CFGMOD           : Working mode selection
777	777
778		-AT+INTMOD            :  Set the trigger interrupt mode
	888	+AT+INTMOD            : Set the trigger interrupt mode
779	779
780		-AT+5VT  :  Set extend the time of 5V power
	890	+AT+5VT  : Set extend the time of 5V power
781	781
782		-AT+PRO  :  Choose agreement
	892	+AT+PRO  : Choose agreement
783	783
784		-AT+WEIGRE  :  Get weight or set weight to 0
	894	+AT+WEIGRE  : Get weight or set weight to 0
785	785
786		-AT+WEIGAP  :  Get or Set the GapValue of weight
	896	+AT+WEIGAP  : Get or Set the GapValue of weight
787	787
788		-AT+RXDL  :  Extend the sending and receiving time
	898	+AT+RXDL  : Extend the sending and receiving time
789	789
790		-AT+CNTFAC  :  Get or set counting parameters
	900	+AT+CNTFAC  : Get or set counting parameters
791	791
792		-AT+SERVADDR  :  Server Address
	902	+AT+SERVADDR  : Server Address
793	793
794		-AT+TR  :  Get or Set record time"
	904	+AT+TR      : Get or Set record time"
795	795
796		-AT+APN     :  Get or set the APN
	906	+AT+APN     : Get or set the APN
797	797
798		-AT+FBAND  :  Get or Set whether to automatically modify the frequency band
	908	+AT+FBAND   : Get or Set whether to automatically modify the frequency band
799	799
800		-AT+DNSCFG  : Get or Set DNS Server
	910	+AT+DNSCFG  : Get or Set DNS Server
801	801
802		-AT+GETSENSORVALUE   :  Returns the current sensor measurement
	912	+AT+GETSENSORVALUE   : Returns the current sensor measurement
803	803
804		-AT+NOUD  :  Get or Set the number of data to be uploaded
	914	+AT+NOUD      : Get or Set the number of data to be uploaded
805	805
806		-AT+CDP     :  Read or Clear cached data
	916	+AT+CDP     : Read or Clear cached data
807	807
808		-AT+LDDSALARM :  Get or Set alarm of distance
	918	+AT+LDDSALARM : Get or Set alarm of distance
809	809
810	810
811	811	(% style="color:#037691" %)**COAP Management**
812	812
813		-AT+URI            :  Resource parameters
	923	+AT+URI            : Resource parameters
814	814
815	815
816	816	(% style="color:#037691" %)**UDP Management**
817	817
818		-AT+CFM          :  Upload confirmation mode (only valid for UDP)
	928	+AT+CFM          : Upload confirmation mode (only valid for UDP)
819	819
820	820
821	821	(% style="color:#037691" %)**MQTT Management**
822	822
823		-AT+CLIENT  :  Get or Set MQTT client
	933	+AT+CLIENT               : Get or Set MQTT client
824	824
825		-AT+UNAME  :  Get or Set MQTT Username
	935	+AT+UNAME  : Get or Set MQTT Username
826	826
827		-AT+PWD  :  Get or Set MQTT password
	937	+AT+PWD                  : Get or Set MQTT password
828	828
829		-AT+PUBTOPIC  :  Get or Set MQTT publish topic
	939	+AT+PUBTOPIC  : Get or Set MQTT publish topic
830	830
831		-AT+SUBTOPIC  :  Get or Set MQTT subscription topic
	941	+AT+SUBTOPIC  : Get or Set MQTT subscription topic
832	832
833	833
834	834	(% style="color:#037691" %)**Information**
835	835
836		-AT+FDR  :  Factory Data Reset
	946	+AT+FDR  : Factory Data Reset
837	837
838		-AT+PWORD  :  Serial Access Password
	948	+AT+PWORD  : Serial Access Password
839	839
840	840
	951	+
841	841	= ​5.  FAQ =
842	842
	954	+
843	843	== 5.1 ​ How to Upgrade Firmware ==
844	844
845	845
...	...	@@ -856,8 +856,10 @@
856	856	)))
857	857
858	858
	971	+
859	859	= 6.  Trouble Shooting =
860	860
	974	+
861	861	== 6.1  ​Connection problem when uploading firmware ==
862	862
863	863
...	...	@@ -870,20 +870,17 @@
870	870
871	871	)))
872	872
	987	+
873	873	== 6.2  AT Command input doesn't work ==
874	874
875	875
876	876	(((
877	877	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.
	993	+
	994	+
878	878	)))
879	879
880	880
881		-== 6.3 Not able to connect to NB-IoT network and keep showing "Signal Strength:99". ==
882		-
883		-
884		-This means sensor is trying to join the NB-IoT network but fail. Please see this link for **//[[trouble shooting for signal strenght:99>>doc:Main.CSQ\:99,99.WebHome]]//**.
885		-
886		-
887	887	= 7. ​ Order Info =
888	888
889	889
...	...	@@ -890,6 +890,11 @@
890	890	Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
891	891
892	892
	1004	+(% class="wikigeneratedid" %)
	1005	+(((
	1006	+
	1007	+)))
	1008	+
893	893	= 8.  Packing Info =
894	894
895	895	(((
...	...	@@ -904,6 +904,7 @@
904	904	(((
905	905
906	906
	1023	+
907	907	(% style="color:#037691" %)**Dimension and weight**:
908	908
909	909	* Device Size: 13.0 x 5 x 4.5 cm
...	...	@@ -915,6 +915,7 @@
915	915	(((
916	916
917	917
	1035	+
918	918
919	919	)))
920	920
...	...	@@ -922,5 +922,4 @@
922	922
923	923
924	924	* 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.
925		-
926	926	* 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-20221009001114-1.png

Author

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

Size

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

Content