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
...	...	@@ -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
	86	+* - B1 @H-FDD: 2100MHz
	87	+* - B3 @H-FDD: 1800MHz
	88	+* - B8 @H-FDD: 900MHz
	89	+* - B5 @H-FDD: 850MHz
	90	+* - B20 @H-FDD: 800MHz
	91	+* - B28 @H-FDD: 700MHz
90	90
91	91	(% style="color:#037691" %)**Battery:**
92	92
...	...	@@ -99,7 +99,7 @@
99	99	(% style="color:#037691" %)**Power Consumption**
100	100
101	101	* STOP Mode: 10uA @ 3.3v
102		-* Max transmit power: [[350mA@3.3v>>mailto:350mA@3.3v]]
	104	+* Max transmit power: 350mA@3.3v
103	103
104	104
105	105
...	...	@@ -117,6 +117,8 @@
117	117	​
118	118
119	119
	122	+
	123	+
120	120	== 1.5  Pin Definitions ==
121	121
122	122
...	...	@@ -123,8 +123,10 @@
123	123	[[image:1657328609906-564.png]]
124	124
125	125
	130	+
126	126	= 2.  Use NDDS75 to communicate with IoT Server =
127	127
	133	+
128	128	== 2.1  How it works ==
129	129
130	130
...	...	@@ -147,8 +147,10 @@
147	147
148	148	)))
149	149
	156	+
150	150	== 2.2 ​ Configure the NDDS75 ==
151	151
	159	+
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
	179	+
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
	195	+
186	186	=== 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
187	187
188	188
...	...	@@ -224,6 +224,7 @@
224	224	)))
225	225
226	226
	237	+
227	227	=== 2.2.4 Use CoAP protocol to uplink data ===
228	228
229	229
...	...	@@ -266,6 +266,7 @@
266	266	[[image:1657330472797-498.png]]
267	267
268	268
	280	+
269	269	=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
270	270
271	271
...	...	@@ -273,6 +273,8 @@
273	273	* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/  to set UDP server address and port
274	274	* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessary
275	275
	288	+
	289	+
276	276	[[image:1657330501006-241.png]]
277	277
278	278
...	...	@@ -279,6 +279,7 @@
279	279	[[image:1657330533775-472.png]]
280	280
281	281
	296	+
282	282	=== 2.2.6 Use MQTT protocol to uplink data ===
283	283
284	284
...	...	@@ -301,6 +301,7 @@
301	301	)))
302	302
303	303
	319	+
304	304	=== 2.2.7 Use TCP protocol to uplink data ===
305	305
306	306
...	...	@@ -313,6 +313,7 @@
313	313	[[image:image-20220709093918-2.png]]
314	314
315	315
	332	+
316	316	=== 2.2.8 Change Update Interval ===
317	317
318	318
...	...	@@ -334,8 +334,10 @@
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
	354	+
337	337	== 2.3  Uplink Payload ==
338	338
	357	+
339	339	=== 2.3.1  Before Firmware v1.3.2 ===
340	340
341	341
...	...	@@ -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.
	370	+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
	377	+(((
358	358	The payload is **ASCII** string, representative same HEX:
	379	+)))
359	359
360		-(% style="background-color:yellow" %)**0x 724031556159 0064 0c6c 19 0292 00 **
	381	+(((
	382	+0x72403155615900640c6c19029200 where:
	383	+)))
361	361
362		-**where :**
	385	+* (((
	386	+Device ID: 0x724031556159 = 724031556159
	387	+)))
	388	+* (((
	389	+Version:  0x0064=100=1.0.0
	390	+)))
363	363
364		-* (% style="color:#037691" %)**Device ID:**(%%) 0x724031556159 = 724031556159
	392	+* (((
	393	+BAT:  0x0c6c = 3180 mV = 3.180V
	394	+)))
	395	+* (((
	396	+Signal: 0x19 = 25
	397	+)))
	398	+* (((
	399	+Distance: 0x0292= 658 mm
	400	+)))
	401	+* (((
	402	+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
	407	+
	408	+)))
373	373
374		-* (% style="color:#037691" %)**Interrupt:**(%%) 0x00 = 0
	410	+=== **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" style="background-color:#ffffcc; color:green; width:490px" %)
386		-|=(% 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**
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.......
	417	+(% border="2" style="background-color:#ffffcc; color:green; width:896px" %)
	418	+|(% 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
	419	+|(% 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,24 @@
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 (%%)**
	428	+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:**
	430	+* (% style="color:green" %)Device ID: f867787050213317 = f867787050213317
	431	+* (% style="color:red" %)Version: 0x0084=132=1.3.2
	432	+* (% style="color:green" %)BAT: 0x0cf4 = 3316 mV = 3.316V
	433	+* (% style="color:blue" %)Singal: 0x1e = 30
	434	+* (% style="color:red" %)Mod: 0x01 = 1
	435	+* Interrupt: 0x00= 0
	436	+* Distance: 0x0039= 57 = 57
	437	+* Time stamp : 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
	438	+* Distance,Time stamp : 00396319baf0
	439	+* (% 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		-
406		-* (% style="color:#037691" %)**Singal:**(%%)  0x1e = 30
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
	445	+
424	424	=== 2.4.1  Device ID ===
425	425
426	426
...	...	@@ -459,6 +459,7 @@
459	459	AT+DEUI=868411056754138
460	460
461	461
	484	+
462	462	=== 2.4.2  Version Info ===
463	463
464	464
...	...	@@ -471,6 +471,7 @@
471	471	)))
472	472
473	473
	497	+
474	474	=== 2.4.3  Battery Info ===
475	475
476	476
...	...	@@ -483,6 +483,7 @@
483	483	)))
484	484
485	485
	510	+
486	486	=== 2.4.4  Signal Strength ===
487	487
488	488
...	...	@@ -515,6 +515,7 @@
515	515	)))
516	516
517	517
	543	+
518	518	=== 2.4.5  Distance ===
519	519
520	520
...	...	@@ -534,6 +534,10 @@
534	534
535	535	)))
536	536
	563	+(((
	564	+
	565	+)))
	566	+
537	537	=== 2.4.6  Digital Interrupt ===
538	538
539	539
...	...	@@ -568,6 +568,7 @@
568	568	)))
569	569
570	570
	601	+
571	571	=== 2.4.7  ​+5V Output ===
572	572
573	573
...	...	@@ -593,6 +593,7 @@
593	593	)))
594	594
595	595
	627	+
596	596	== 2.5  Downlink Payload ==
597	597
598	598
...	...	@@ -645,6 +645,7 @@
645	645	)))
646	646
647	647
	680	+
648	648	== 2.6  Distance alarm function(Since firmware v1.3.2) ==
649	649
650	650
...	...	@@ -664,6 +664,7 @@
664	664	**AT+ LDDSALARM=260,2000**  ~/~/ Alarm when distance lower than 260.
665	665
666	666
	700	+
667	667	== 2.7  Set the number of data to be uploaded and the recording time ==
668	668
669	669
...	...	@@ -670,11 +670,9 @@
670	670	(% style="color:blue" %)** ➢ AT Command:**
671	671
672	672	* (% 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)
673		-* (% 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.
	707	+* (% 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.
674	674
675		- The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
676	676
677		-[[image:image-20221009001114-1.png||height="687" width="955"]]
678	678
679	679
680	680	== 2.8  Read or Clear cached data ==
...	...	@@ -688,6 +688,7 @@
688	688	[[image:image-20220908175333-2.png]]
689	689
690	690
	723	+
691	691	== 2.9  ​LED Indicator ==
692	692
693	693
...	...	@@ -704,6 +704,7 @@
704	704	)))
705	705
706	706
	740	+
707	707	== 2.10  ​Firmware Change Log ==
708	708
709	709
...	...	@@ -712,18 +712,100 @@
712	712	)))
713	713
714	714	(((
	749	+
	750	+)))
	751	+
	752	+(((
715	715	Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
716	716	)))
717	717
718	718
719		-== 2.11 Battery & Power Consumption ==
720	720
	758	+== 2.11  ​Battery Analysis ==
721	721
722		-NDDS75 uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace.
723	723
724		-[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] .
	761	+=== 2.11.1  ​Battery Type ===
725	725
726	726
	764	+(((
	765	+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.
	766	+)))
	767	+
	768	+(((
	769	+The battery is designed to last for several years depends on the actually use environment and update interval.
	770	+)))
	771	+
	772	+(((
	773	+The battery related documents as below:
	774	+)))
	775	+
	776	+* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
	777	+* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
	778	+* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
	779	+
	780	+(((
	781	+[[image:image-20220709101450-2.png]]
	782	+)))
	783	+
	784	+
	785	+
	786	+=== 2.11.2  Power consumption Analyze ===
	787	+
	788	+
	789	+(((
	790	+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.
	791	+)))
	792	+
	793	+
	794	+(((
	795	+Instruction to use as below:
	796	+)))
	797	+
	798	+(((
	799	+(% 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/]]
	800	+)))
	801	+
	802	+
	803	+(((
	804	+(% style="color:blue" %)**Step 2: **(%%) Open it and choose
	805	+)))
	806	+
	807	+* (((
	808	+Product Model
	809	+)))
	810	+* (((
	811	+Uplink Interval
	812	+)))
	813	+* (((
	814	+Working Mode
	815	+)))
	816	+
	817	+(((
	818	+And the Life expectation in difference case will be shown on the right.
	819	+)))
	820	+
	821	+[[image:image-20220709110451-3.png]]
	822	+
	823	+
	824	+
	825	+=== 2.11.3  ​Battery Note ===
	826	+
	827	+
	828	+(((
	829	+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.
	830	+)))
	831	+
	832	+
	833	+
	834	+=== 2.11.4  Replace the battery ===
	835	+
	836	+
	837	+(((
	838	+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).
	839	+)))
	840	+
	841	+
	842	+
727	727	= 3. ​ Access NB-IoT Module =
728	728
729	729
...	...	@@ -740,8 +740,10 @@
740	740	[[image:1657333200519-600.png]]
741	741
742	742
	859	+
743	743	= 4.  Using the AT Commands =
744	744
	862	+
745	745	== 4.1  Access AT Commands ==
746	746
747	747
...	...	@@ -834,8 +834,10 @@
834	834	AT+PWORD  :  Serial Access Password
835	835
836	836
	955	+
837	837	= ​5.  FAQ =
838	838
	958	+
839	839	== 5.1 ​ How to Upgrade Firmware ==
840	840
841	841
...	...	@@ -852,8 +852,10 @@
852	852	)))
853	853
854	854
	975	+
855	855	= 6.  Trouble Shooting =
856	856
	978	+
857	857	== 6.1  ​Connection problem when uploading firmware ==
858	858
859	859
...	...	@@ -866,11 +866,14 @@
866	866
867	867	)))
868	868
	991	+
869	869	== 6.2  AT Command input doesn't work ==
870	870
871	871
872	872	(((
873	873	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.
	997	+
	998	+
874	874	)))
875	875
876	876
...	...	@@ -880,6 +880,11 @@
880	880	Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
881	881
882	882
	1008	+(% class="wikigeneratedid" %)
	1009	+(((
	1010	+
	1011	+)))
	1012	+
883	883	= 8.  Packing Info =
884	884
885	885	(((
...	...	@@ -894,6 +894,7 @@
894	894	(((
895	895
896	896
	1027	+
897	897	(% style="color:#037691" %)**Dimension and weight**:
898	898
899	899	* Device Size: 13.0 x 5 x 4.5 cm
...	...	@@ -905,6 +905,7 @@
905	905	(((
906	906
907	907
	1039	+
908	908
909	909	)))
910	910

image-20221009001114-1.png

Author

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

Size

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

Content