Summary

• Page properties (2 modified, 0 added, 0 removed)
• Attachments (0 modified, 0 added, 1 removed)
  • image-20221009001114-1.png

Details

Page properties

Author

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

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
...	...	@@ -70,7 +70,6 @@
70	70	* 8500mAh Battery for long term use
71	71
72	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
	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
90	90
91	91	(% style="color:#037691" %)**Battery:**
92	92
...	...	@@ -102,7 +102,6 @@
102	102	* Max transmit power: 350mA@3.3v
103	103
104	104
105		-
106	106	== ​1.4  Applications ==
107	107
108	108
...	...	@@ -117,6 +117,8 @@
117	117	​
118	118
119	119
	120	+
	121	+
120	120	== 1.5  Pin Definitions ==
121	121
122	122
...	...	@@ -123,8 +123,10 @@
123	123	[[image:1657328609906-564.png]]
124	124
125	125
	128	+
126	126	= 2.  Use NDDS75 to communicate with IoT Server =
127	127
	131	+
128	128	== 2.1  How it works ==
129	129
130	130
...	...	@@ -147,8 +147,10 @@
147	147
148	148	)))
149	149
	154	+
150	150	== 2.2 ​ Configure the NDDS75 ==
151	151
	157	+
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
	177	+
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
	193	+
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:**
	206	+**Connection:**
199	199
200		- (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND**
	208	+ (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
201	201
202		-**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)**
	210	+ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
203	203
204		-**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)**
	212	+ (% 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
	235	+
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
	250	+(% 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
	253	+(% 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
...	...	@@ -249,8 +249,6 @@
249	249
250	250	(((
251	251	For parameter description, please refer to AT command set
252		-
253		-
254	254	)))
255	255
256	256	[[image:1657330452568-615.png]]
...	...	@@ -259,19 +259,18 @@
259	259
260	260	(((
261	261	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.
262		-
263		-
264	264	)))
265	265
266	266	[[image:1657330472797-498.png]]
267	267
268	268
	274	+
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
	278	+* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
	279	+* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
	280	+* (% 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
	288	+
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
	292	+* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
	293	+* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
	294	+* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
	295	+* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
	296	+* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
	297	+* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/Set the sending topic of MQTT
	298	+* (% 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
	311	+
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
	315	+* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
	316	+* (% 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,34 +313,31 @@
313	313	[[image:image-20220709093918-2.png]]
314	314
315	315
	324	+
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
	330	+* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
322	322
323	323	(((
324		-
	333	+(% style="color:red" %)**NOTE: 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:**
	335	+
332	332	)))
333	333
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).**
	338	+**NOTE:When the firmware version is v1.3.2 and later firmware:**
335	335
	340	+**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).**
336	336
	342	+
337	337	== 2.3  Uplink Payload ==
338	338
339		-=== 2.3.1  Before Firmware v1.3.2 ===
340	340
341		-
342	342	In this mode, uplink payload includes in total 14 bytes
343	343
	348	+
344	344	(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
345	345	|=(% style="width: 60px;" %)(((
346	346	**Size(bytes)**
...	...	@@ -348,7 +348,7 @@
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.
	356	+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,68 +355,67 @@
355	355	[[image:1657331036973-987.png]]
356	356
357	357
358		-The payload is **ASCII** string, representative same HEX:
	363	+(((
	364	+The payload is ASCII string, representative same HEX:
	365	+)))
359	359
360		-(% style="background-color:yellow" %)**0x 724031556159 0064 0c6c 19 0292 00 **
	367	+(((
	368	+0x72403155615900640c6c19029200 where:
	369	+)))
361	361
362		-**where :**
	371	+* (((
	372	+Device ID: 0x724031556159 = 724031556159
	373	+)))
	374	+* (((
	375	+Version: 0x0064=100=1.0.0
	376	+)))
363	363
364		-* (% style="color:#037691" %)**Device ID:**(%%) 0x724031556159 = 724031556159
	378	+* (((
	379	+BAT: 0x0c6c = 3180 mV = 3.180V
	380	+)))
	381	+* (((
	382	+Signal: 0x19 = 25
	383	+)))
	384	+* (((
	385	+Distance: 0x0292= 658 mm
	386	+)))
	387	+* (((
	388	+Interrupt: 0x00 = 0
365	365
366		-* (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
	390	+
	391	+)))
367	367
368		-* (% style="color:#037691" %)**BAT:** (%%) 0x0c6c = 3180 mV = 3.180V
	393	+**NOTE:When the firmware version is v1.3.2 and later firmware:**
369	369
370		-* (% style="color:#037691" %)**Signal:**(%%)  0x19 = 25
371		-
372		-* (% style="color:#037691" %)**Distance:**  (%%)0x0292= 658 mm
373		-
374		-* (% style="color:#037691" %)**Interrupt:**(%%) 0x00 = 0
375		-
376		-=== 2.3.2  Since firmware v1.3.2 ===
377		-
378		-
379	379	In this mode, uplink payload includes 69 bytes in total by default.
380	380
381	381	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.
382	382
383		-(% border="1" style="background-color:#ffffcc; color:green; width:490px" %)
384		-|=(% 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**
385		-|=(% 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.......
	399	+|**Size(bytes)**|**8**|2|2|1|1|1|2|4|2|4
	400	+|**Value**|Device ID|Ver|BAT|Signal Strength|MOD|Interrupt|Distance|Timestamp|Distance|Timestamp.......
386	386
387	387	If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
388	388
389	389	[[image:image-20220908175246-1.png]]
390	390
391		-
392	392	The payload is ASCII string, representative same HEX:
393	393
394		-**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 (%%)**
	408	+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:
395	395
396		-**where:**
	410	+* (% style="color:green" %)Device ID: f867787050213317 = f867787050213317
	411	+* (% style="color:red" %)Version: 0x0084=132=1.3.2
	412	+* (% style="color:green" %)BAT: 0x0cf4 = 3316 mV = 3.316V
	413	+* (% style="color:blue" %)Singal: 0x1e = 30
	414	+* (% style="color:red" %)Mod: 0x01 = 1
	415	+* Interrupt: 0x00= 0
	416	+* Distance: 0x0039= 57 = 57
	417	+* Time stamp : 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
	418	+* Distance,Time stamp : 00396319baf0
	419	+* (% style="color:red" %) 8 sets of recorded data: Distance,Time stamp : //**00396319ba3c**//,.......
397	397
398		-* (% style="color:#037691" %)**Device ID:**(%%) f867787050213317 = f867787050213317
399		-
400		-* (% style="color:#037691" %)**Version:**(%%) 0x0084=132=1.3.2
401		-
402		-* (% style="color:#037691" %)**BAT:**(%%)  0x0cf4 = 3316 mV = 3.316V
403		-
404		-* (% style="color:#037691" %)**Singal:**(%%)  0x1e = 30
405		-
406		-* (% style="color:#037691" %)**Mod:**(%%)**     **0x01 = 1
407		-
408		-* (% style="color:#037691" %)**Interrupt:**(%%) 0x00= 0
409		-
410		-* (% style="color:#037691" %)**Distance:**(%%) 0x0039= 57 = 57
411		-
412		-* (% style="color:#037691" %)**Time stamp:**(%%) 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
413		-
414		-* (% style="color:#037691" %)**Distance,Time stamp:**(%%) 00396319baf0
415		-
416		-* (% style="color:#037691" %)**8 sets of recorded data: Distance,Time stamp :**(%%) //**00396319ba3c**//,.......
417		-
418	418	== 2.4  Payload Explanation and Sensor Interface ==
419	419
	423	+
420	420	=== 2.4.1  Device ID ===
421	421
422	422
...	...	@@ -431,7 +431,7 @@
431	431	)))
432	432
433	433	(((
434		-(% style="color:blue" %)**Example :**
	438	+**Example:**
435	435	)))
436	436
437	437	(((
...	...	@@ -439,22 +439,20 @@
439	439	)))
440	440
441	441	(((
442		-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.
	446	+The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
443	443	)))
444	444
445	445
446		-(% style="color:red" %)**NOTE: When the firmware version is v1.3.2 and later firmware:**
	450	+**NOTE:When the firmware version is v1.3.2 and later firmware:**
447	447
448		-(% style="color:red" %)**By default, the Device ID equal to the last 15 bits of IMEI.**
	452	+By default, the Device ID equal to the last 15 bits of IMEI.
449	449
450		-User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
	454	+User can use **AT+DEUI** to set Device ID
451	451
	456	+**Example:**
452	452
453		-(% style="color:blue" %)**Example :**
454		-
455	455	AT+DEUI=868411056754138
456	456
457		-
458	458	=== 2.4.2  Version Info ===
459	459
460	460
...	...	@@ -467,6 +467,7 @@
467	467	)))
468	468
469	469
	472	+
470	470	=== 2.4.3  Battery Info ===
471	471
472	472
...	...	@@ -479,6 +479,7 @@
479	479	)))
480	480
481	481
	485	+
482	482	=== 2.4.4  Signal Strength ===
483	483
484	484
...	...	@@ -511,6 +511,7 @@
511	511	)))
512	512
513	513
	518	+
514	514	=== 2.4.5  Distance ===
515	515
516	516
...	...	@@ -530,6 +530,10 @@
530	530
531	531	)))
532	532
	538	+(((
	539	+
	540	+)))
	541	+
533	533	=== 2.4.6  Digital Interrupt ===
534	534
535	535
...	...	@@ -542,7 +542,7 @@
542	542	)))
543	543
544	544	(((
545		-(% 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]])**.**
	554	+(% 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]])**.**
546	546	)))
547	547
548	548
...	...	@@ -564,6 +564,7 @@
564	564	)))
565	565
566	566
	576	+
567	567	=== 2.4.7  ​+5V Output ===
568	568
569	569
...	...	@@ -589,6 +589,7 @@
589	589	)))
590	590
591	591
	602	+
592	592	== 2.5  Downlink Payload ==
593	593
594	594
...	...	@@ -641,13 +641,12 @@
641	641	)))
642	642
643	643
644		-== 2.6  Distance alarm function(Since firmware v1.3.2) ==
	655	+== 2.6 Distance alarm function ==
645	645
	657	+➢ AT Command:
646	646
647		-(% style="color:blue" %)** ➢ AT Command:**
	659	+AT+ LDDSALARM=min,max
648	648
649		-(% style="color:#037691" %)** AT+ LDDSALARM=min,max**
650		-
651	651	² When min=0, and max≠0, Alarm higher than max
652	652
653	653	² When min≠0, and max=0, Alarm lower than min
...	...	@@ -654,35 +654,28 @@
654	654
655	655	² When min≠0 and max≠0, Alarm higher than max or lower than min
656	656
	667	+Example:
657	657
658		-(% style="color:blue" %)** Example:**
	669	+AT+ LDDSALARM=260,2000 ~/~/ Alarm when distance lower than 260.
659	659
660		-**AT+ LDDSALARM=260,2000**  ~/~/ Alarm when distance lower than 260.
661	661
	672	+== 2.7 Set the number of data to be uploaded and the recording time ==
662	662
663		-== 2.7  Set the number of data to be uploaded and the recording time ==
	674	+➢ AT Command:
664	664
	676	+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)
665	665
666		-(% style="color:blue" %)** ➢ AT Command:**
	678	+AT+NOUD=8  ~/~/The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
667	667
668		-* (% 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)
669		-* (% 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	+== 2.8 Read or Clear cached data ==
670	670
671		- The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
	682	+➢ AT Command:
672	672
673		-[[image:image-20221009001114-1.png||height="687" width="955"]]
	684	+AT+CDP ~/~/ Read cached data
674	674
675		-
676		-== 2.8  Read or Clear cached data ==
677		-
678		-
679		-(% style="color:blue" %)** ➢ AT Command:**
680		-
681		-* (% style="color:#037691" %)** AT+CDP ** (%%) ~/~/  Read cached data
682		-* (% style="color:#037691" %)** AT+CDP=0**  (%%) ~/~/  Clear cached data
683		-
684	684	[[image:image-20220908175333-2.png]]
685	685
	688	+AT+CDP=0 ~/~/ Clear cached data
686	686
687	687	== 2.9  ​LED Indicator ==
688	688
...	...	@@ -700,6 +700,7 @@
700	700	)))
701	701
702	702
	706	+
703	703	== 2.10  ​Firmware Change Log ==
704	704
705	705
...	...	@@ -708,18 +708,100 @@
708	708	)))
709	709
710	710	(((
	715	+
	716	+)))
	717	+
	718	+(((
711	711	Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
712	712	)))
713	713
714	714
715		-== 2.11 Battery & Power Consumption ==
716	716
	724	+== 2.11  ​Battery Analysis ==
717	717
718		-NDDS75 uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace.
719	719
720		-[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] .
	727	+=== 2.11.1  ​Battery Type ===
721	721
722	722
	730	+(((
	731	+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.
	732	+)))
	733	+
	734	+(((
	735	+The battery is designed to last for several years depends on the actually use environment and update interval.
	736	+)))
	737	+
	738	+(((
	739	+The battery related documents as below:
	740	+)))
	741	+
	742	+* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
	743	+* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
	744	+* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
	745	+
	746	+(((
	747	+[[image:image-20220709101450-2.png]]
	748	+)))
	749	+
	750	+
	751	+
	752	+=== 2.11.2  Power consumption Analyze ===
	753	+
	754	+
	755	+(((
	756	+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.
	757	+)))
	758	+
	759	+
	760	+(((
	761	+Instruction to use as below:
	762	+)))
	763	+
	764	+(((
	765	+(% 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/]]
	766	+)))
	767	+
	768	+
	769	+(((
	770	+(% style="color:blue" %)**Step 2: **(%%) Open it and choose
	771	+)))
	772	+
	773	+* (((
	774	+Product Model
	775	+)))
	776	+* (((
	777	+Uplink Interval
	778	+)))
	779	+* (((
	780	+Working Mode
	781	+)))
	782	+
	783	+(((
	784	+And the Life expectation in difference case will be shown on the right.
	785	+)))
	786	+
	787	+[[image:image-20220709110451-3.png]]
	788	+
	789	+
	790	+
	791	+=== 2.11.3  ​Battery Note ===
	792	+
	793	+
	794	+(((
	795	+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.
	796	+)))
	797	+
	798	+
	799	+
	800	+=== 2.11.4  Replace the battery ===
	801	+
	802	+
	803	+(((
	804	+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).
	805	+)))
	806	+
	807	+
	808	+
723	723	= 3. ​ Access NB-IoT Module =
724	724
725	725
...	...	@@ -736,8 +736,10 @@
736	736	[[image:1657333200519-600.png]]
737	737
738	738
	825	+
739	739	= 4.  Using the AT Commands =
740	740
	828	+
741	741	== 4.1  Access AT Commands ==
742	742
743	743
...	...	@@ -744,94 +744,96 @@
744	744	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]]
745	745
746	746
747		-AT+<CMD>?  :  Help on <CMD>
	835	+AT+<CMD>?  : Help on <CMD>
748	748
749		-AT+<CMD>         :  Run <CMD>
	837	+AT+<CMD>         : Run <CMD>
750	750
751		-AT+<CMD>=<value> :  Set the value
	839	+AT+<CMD>=<value> : Set the value
752	752
753		-AT+<CMD>=?  :  Get the value
	841	+AT+<CMD>=?  : Get the value
754	754
755	755
756	756	(% style="color:#037691" %)**General Commands**(%%)
757	757
758		-AT  :  Attention
	846	+AT  : Attention
759	759
760		-AT?  :  Short Help
	848	+AT?  : Short Help
761	761
762		-ATZ  :  MCU Reset
	850	+ATZ  : MCU Reset
763	763
764		-AT+TDC  :  Application Data Transmission Interval
	852	+AT+TDC  : Application Data Transmission Interval
765	765
766		-AT+CFG  :  Print all configurations
	854	+AT+CFG  : Print all configurations
767	767
768		-AT+CFGMOD           :  Working mode selection
	856	+AT+CFGMOD           : Working mode selection
769	769
770		-AT+INTMOD            :  Set the trigger interrupt mode
	858	+AT+INTMOD            : Set the trigger interrupt mode
771	771
772		-AT+5VT  :  Set extend the time of 5V power
	860	+AT+5VT  : Set extend the time of 5V power
773	773
774		-AT+PRO  :  Choose agreement
	862	+AT+PRO  : Choose agreement
775	775
776		-AT+WEIGRE  :  Get weight or set weight to 0
	864	+AT+WEIGRE  : Get weight or set weight to 0
777	777
778		-AT+WEIGAP  :  Get or Set the GapValue of weight
	866	+AT+WEIGAP  : Get or Set the GapValue of weight
779	779
780		-AT+RXDL  :  Extend the sending and receiving time
	868	+AT+RXDL  : Extend the sending and receiving time
781	781
782		-AT+CNTFAC  :  Get or set counting parameters
	870	+AT+CNTFAC  : Get or set counting parameters
783	783
784		-AT+SERVADDR  :  Server Address
	872	+AT+SERVADDR  : Server Address
785	785
786		-AT+TR  :  Get or Set record time"
	874	+AT+TR      : Get or Set record time"
787	787
788		-AT+APN     :  Get or set the APN
	876	+AT+APN     : Get or set the APN
789	789
790		-AT+FBAND  :  Get or Set whether to automatically modify the frequency band
	878	+AT+FBAND   : Get or Set whether to automatically modify the frequency band
791	791
792		-AT+DNSCFG  : Get or Set DNS Server
	880	+AT+DNSCFG  : Get or Set DNS Server
793	793
794		-AT+GETSENSORVALUE   :  Returns the current sensor measurement
	882	+AT+GETSENSORVALUE   : Returns the current sensor measurement
795	795
796		-AT+NOUD  :  Get or Set the number of data to be uploaded
	884	+AT+NOUD      : Get or Set the number of data to be uploaded
797	797
798		-AT+CDP     :  Read or Clear cached data
	886	+AT+CDP     : Read or Clear cached data
799	799
800		-AT+LDDSALARM :  Get or Set alarm of distance
	888	+AT+LDDSALARM : Get or Set alarm of distance
801	801
802	802
803	803	(% style="color:#037691" %)**COAP Management**
804	804
805		-AT+URI            :  Resource parameters
	893	+AT+URI            : Resource parameters
806	806
807	807
808	808	(% style="color:#037691" %)**UDP Management**
809	809
810		-AT+CFM          :  Upload confirmation mode (only valid for UDP)
	898	+AT+CFM          : Upload confirmation mode (only valid for UDP)
811	811
812	812
813	813	(% style="color:#037691" %)**MQTT Management**
814	814
815		-AT+CLIENT  :  Get or Set MQTT client
	903	+AT+CLIENT               : Get or Set MQTT client
816	816
817		-AT+UNAME  :  Get or Set MQTT Username
	905	+AT+UNAME  : Get or Set MQTT Username
818	818
819		-AT+PWD  :  Get or Set MQTT password
	907	+AT+PWD                  : Get or Set MQTT password
820	820
821		-AT+PUBTOPIC  :  Get or Set MQTT publish topic
	909	+AT+PUBTOPIC  : Get or Set MQTT publish topic
822	822
823		-AT+SUBTOPIC  :  Get or Set MQTT subscription topic
	911	+AT+SUBTOPIC  : Get or Set MQTT subscription topic
824	824
825	825
826	826	(% style="color:#037691" %)**Information**
827	827
828		-AT+FDR  :  Factory Data Reset
	916	+AT+FDR  : Factory Data Reset
829	829
830		-AT+PWORD  :  Serial Access Password
	918	+AT+PWORD  : Serial Access Password
831	831
832	832
	921	+
833	833	= ​5.  FAQ =
834	834
	924	+
835	835	== 5.1 ​ How to Upgrade Firmware ==
836	836
837	837
...	...	@@ -848,8 +848,10 @@
848	848	)))
849	849
850	850
	941	+
851	851	= 6.  Trouble Shooting =
852	852
	944	+
853	853	== 6.1  ​Connection problem when uploading firmware ==
854	854
855	855
...	...	@@ -862,20 +862,17 @@
862	862
863	863	)))
864	864
	957	+
865	865	== 6.2  AT Command input doesn't work ==
866	866
867	867
868	868	(((
869	869	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.
	963	+
	964	+
870	870	)))
871	871
872	872
873		-== 6.3 Not able to connect to NB-IoT network and keep showing "Signal Strength:99". ==
874		-
875		-
876		-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]]//**.
877		-
878		-
879	879	= 7. ​ Order Info =
880	880
881	881
...	...	@@ -882,6 +882,11 @@
882	882	Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
883	883
884	884
	974	+(% class="wikigeneratedid" %)
	975	+(((
	976	+
	977	+)))
	978	+
885	885	= 8.  Packing Info =
886	886
887	887	(((
...	...	@@ -896,6 +896,7 @@
896	896	(((
897	897
898	898
	993	+
899	899	(% style="color:#037691" %)**Dimension and weight**:
900	900
901	901	* Device Size: 13.0 x 5 x 4.5 cm
...	...	@@ -907,6 +907,7 @@
907	907	(((
908	908
909	909
	1005	+
910	910
911	911	)))
912	912
...	...	@@ -914,5 +914,4 @@
914	914
915	915
916	916	* 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.
917		-
918	918	* 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