Summary

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

Details

Page properties

Content

...	...	@@ -16,6 +16,7 @@
16	16
17	17	= 1.  Introduction =
18	18
	19	+
19	19	== 1.1 ​ What is NDDS75 Distance Detection Sensor ==
20	20
21	21	(((
...	...	@@ -22,14 +22,31 @@
22	22
23	23
24	24	(((
	26	+(((
25	25	The Dragino NDDS75 is a (% style="color:blue" %)**NB-IoT Distance Detection Sensor**(%%) for Internet of Things solution. It is designed to measure the distance between the sensor and a flat object. The distance detection sensor is a module that uses ultrasonic sensing technology for distance measurement, and temperature compensation is performed internally to improve the reliability of data.
26		-\\The NDDS75 can be applied to scenarios such as horizontal distance measurement, liquid level measurement, parking management system, object proximity and presence detection, intelligent trash can management system, robot obstacle avoidance, automatic control, sewer, bottom water level monitoring, etc. It detects the distance between the measured object and the sensor, and uploads the value via wireless to IoT Server via NB-IoT Network.
27		-\\NarrowBand-Internet of Things (NB-IoT) is a standards-based low power wide area (LPWA) technology developed to enable a wide range of new IoT devices and services. NB-IoT significantly improves the power consumption of user devices, system capacity and spectrum efficiency, especially in deep coverage.
28		-\\NDDS75 supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP** (%%)for different application requirement.
29		-\\NDDS75 is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long term use up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method)
30		-\\To use NDDS75, user needs to check if there is NB-IoT coverage in local area and with the bands NDDS75 supports. If the local operate support it, user needs to get a NB-IoT SIM card from local operator and install NDDS75 to get NB-IoT network connection.
31	31	)))
32	32
	30	+(((
	31	+The NDDS75 can be applied to scenarios such as horizontal distance measurement, liquid level measurement, parking management system, object proximity and presence detection, intelligent trash can management system, robot obstacle avoidance, automatic control, sewer, bottom water level monitoring, etc. It detects the distance between the measured object and the sensor, and uploads the value via wireless to IoT Server via NB-IoT Network.
	32	+)))
	33	+
	34	+(((
	35	+NarrowBand-Internet of Things (NB-IoT) is a standards-based low power wide area (LPWA) technology developed to enable a wide range of new IoT devices and services. NB-IoT significantly improves the power consumption of user devices, system capacity and spectrum efficiency, especially in deep coverage.
	36	+)))
	37	+
	38	+(((
	39	+NDDS75 supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP** (%%)for different application requirement.
	40	+)))
	41	+
	42	+(((
	43	+NDDS75 is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long term use up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method)
	44	+)))
	45	+
	46	+(((
	47	+To use NDDS75, user needs to check if there is NB-IoT coverage in local area and with the bands NDDS75 supports. If the local operate support it, user needs to get a NB-IoT SIM card from local operator and install NDDS75 to get NB-IoT network connection.
	48	+)))
	49	+)))
	50	+
33	33
34	34	)))
35	35
...	...	@@ -55,6 +55,8 @@
55	55
56	56
57	57
	76	+
	77	+
58	58	== 1.3  Specification ==
59	59
60	60
...	...	@@ -87,8 +87,11 @@
87	87
88	88
89	89
	110	+
	111	+
90	90	== ​1.4  Applications ==
91	91
	114	+
92	92	* Smart Buildings & Home Automation
93	93	* Logistics and Supply Chain Management
94	94	* Smart Metering
...	...	@@ -100,6 +100,8 @@
100	100	​
101	101
102	102
	126	+
	127	+
103	103	== 1.5  Pin Definitions ==
104	104
105	105
...	...	@@ -109,8 +109,10 @@
109	109
110	110	= 2.  Use NDDS75 to communicate with IoT Server =
111	111
	137	+
112	112	== 2.1  How it works ==
113	113
	140	+
114	114	(((
115	115	The NDDS75 is equipped with a NB-IoT module, the pre-loaded firmware in NDDS75 will get environment data from sensors and send the value to local NB-IoT network via the NB-IoT module.  The NB-IoT network will forward this value to IoT server via the protocol defined by NDDS75.
116	116	)))
...	...	@@ -136,16 +136,17 @@
136	136
137	137	=== 2.2.1 Test Requirement ===
138	138
	166	+
139	139	(((
140	140	To use NDDS75 in your city, make sure meet below requirements:
141	141	)))
142	142
143	143	* Your local operator has already distributed a NB-IoT Network there.
144		-* The local NB-IoT network used the band that NSE01 supports.
	172	+* The local NB-IoT network used the band that NDDS75 supports.
145	145	* Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
146	146
147	147	(((
148		-Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.  The NDDS75 will use CoAP((% style="color:red" %)120.24.4.116:5683)(%%) or raw UDP((% style="color:red" %)120.24.4.116:5601)(%%) or MQTT((% style="color:red" %)120.24.4.116:1883)(%%)or TCP((% style="color:red" %)120.24.4.116:5600)(%%)protocol to send data to the test server
	176	+Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.  The NDDS75 will use CoAP((% style="color:red" %)120.24.4.116:5683)(%%) or raw UDP((% style="color:red" %)120.24.4.116:5601)(%%) or MQTT((% style="color:red" %)120.24.4.116:1883)(%%)or TCP((% style="color:red" %)120.24.4.116:5600)(%%)protocol to send data to the test server.
149	149	)))
150	150
151	151
...	...	@@ -155,6 +155,7 @@
155	155
156	156	=== 2.2.2 Insert SIM card ===
157	157
	186	+
158	158	(((
159	159	Insert the NB-IoT Card get from your provider.
160	160	)))
...	...	@@ -170,6 +170,7 @@
170	170
171	171	=== 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
172	172
	202	+
173	173	(((
174	174	(((
175	175	User need to configure NDDS75 via serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. NDDS75 support AT Commands, user can use a USB to TTL adapter to connect to NDDS75 and use AT Commands to configure it, as below.
...	...	@@ -178,6 +178,7 @@
178	178
179	179	[[image:image-20220709092052-2.png]]
180	180
	211	+
181	181	**Connection:**
182	182
183	183	(% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
...	...	@@ -201,8 +201,9 @@
201	201
202	202	[[image:1657329814315-101.png]]
203	203
	235	+
204	204	(((
205		-(% style="color:red" %)Note: the valid AT Commands can be found at: (%%)[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/]]
	237	+(% style="color:red" %)**Note: the valid AT Commands can be found at: **(%%)**[[https:~~/~~/www.dropbox.com/sh/aaq2xcl0bzfu0yd/AAAEAHRa7Io_465ds4Y7-F3aa?dl=0>>https://www.dropbox.com/sh/aaq2xcl0bzfu0yd/AAAEAHRa7Io_465ds4Y7-F3aa?dl=0]]**
206	206	)))
207	207
208	208
...	...	@@ -209,22 +209,43 @@
209	209
210	210	=== 2.2.4 Use CoAP protocol to uplink data ===
211	211
212		-(% style="color:red" %)Note: if you don't have CoAP server, you can refer this link to set up one: (%%)[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/>>http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]]
213	213
	245	+(% 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
	247	+
	248	+(((
215	215	**Use below commands:**
	250	+)))
216	216
217		-* (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
218		-* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
219		-* (% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
	252	+* (((
	253	+(% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
	254	+)))
	255	+* (((
	256	+(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
	257	+)))
	258	+* (((
	259	+(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
220	220
	261	+
	262	+
	263	+)))
	264	+
	265	+(((
221	221	For parameter description, please refer to AT command set
222	222
	268	+
	269	+)))
	270	+
223	223	[[image:1657330452568-615.png]]
224	224
225	225
	274	+
	275	+(((
226	226	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.
227	227
	278	+
	279	+)))
	280	+
228	228	[[image:1657330472797-498.png]]
229	229
230	230
...	...	@@ -246,11 +246,11 @@
246	246	=== 2.2.6 Use MQTT protocol to uplink data ===
247	247
248	248
249		-* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
250		-* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
251		-* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
252		-* (% style="color:blue" %)**AT+UNAME=UNAME                               **(%%)~/~/Set the username of MQTT
253		-* (% style="color:blue" %)**AT+PWD=PWD                                        **(%%)~/~/Set the password of MQTT
	302	+* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
	303	+* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
	304	+* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
	305	+* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
	306	+* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
254	254	* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/Set the sending topic of MQTT
255	255	* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/Set the subscription topic of MQTT
256	256
...	...	@@ -281,29 +281,38 @@
281	281
282	282	=== 2.2.8 Change Update Interval ===
283	283
	337	+
284	284	User can use below command to change the (% style="color:green" %)**uplink interval**.
285	285
286	286	* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
287	287
288	288	(((
	343	+
	344	+
	345	+
289	289	(% style="color:red" %)**NOTE:**
290		-)))
291	291
292		-(((
293		-(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
	348	+(% style="color:red" %)**1. By default, the device will send an uplink message every 1 hour.**
	349	+
	350	+(% style="color:red" %)**2. When the firmware version is v1.3.2 and later firmware:**
294	294	)))
295	295
	353	+(% 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).**
296	296
297	297
	356	+
298	298	== 2.3  Uplink Payload ==
299	299
300		-In this mode, uplink payload includes in total 14 bytes
301	301
	360	+=== 2.3.1  Before Firmware 1.3.2 ===
302	302
303		-(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
304		-|=(% style="width: 80px;" %)(((
	362	+
	363	+In this mode, uplink payload includes in total 14 bytes
	364	+
	365	+(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
	366	+|=(% style="width: 60px;" %)(((
305	305	**Size(bytes)**
306		-)))|=(% style="width: 80px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 110px;" %)**1**|=(% style="width: 110px;" %)**2**|=(% style="width: 70px;" %)**1**
	368	+)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1**
307	307	|(% 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"]]
308	308
309	309	(((
...	...	@@ -313,8 +313,9 @@
313	313
314	314	[[image:1657331036973-987.png]]
315	315
	378	+
316	316	(((
317		-The payload is ASCII string, representative same HEX:
	380	+The payload is **ASCII** string, representative same HEX:
318	318	)))
319	319
320	320	(((
...	...	@@ -325,11 +325,11 @@
325	325	Device ID: 0x724031556159 = 724031556159
326	326	)))
327	327	* (((
328		-Version: 0x0064=100=1.0.0
	391	+Version:  0x0064=100=1.0.0
329	329	)))
330	330
331	331	* (((
332		-BAT: 0x0c6c = 3180 mV = 3.180V
	395	+BAT:  0x0c6c = 3180 mV = 3.180V
333	333	)))
334	334	* (((
335	335	Signal: 0x19 = 25
...	...	@@ -342,14 +342,51 @@
342	342
343	343
344	344
	408	+
345	345
346	346	)))
347	347
	412	+=== **2.3.2  Since firmware v1.3.2** ===
	413	+
	414	+
	415	+In this mode, uplink payload includes 69 bytes in total by default.
	416	+
	417	+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.
	418	+
	419	+(% border="2" style="background-color:#ffffcc; color:green; width:896px" %)
	420	+|(% 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
	421	+|(% 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.......
	422	+
	423	+If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
	424	+
	425	+[[image:image-20220908175246-1.png]]
	426	+
	427	+
	428	+The payload is ASCII string, representative same HEX:
	429	+
	430	+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:
	431	+
	432	+* (% style="color:green" %)Device ID: f867787050213317 = f867787050213317
	433	+* (% style="color:red" %)Version: 0x0084=132=1.3.2
	434	+* (% style="color:green" %)BAT: 0x0cf4 = 3316 mV = 3.316V
	435	+* (% style="color:blue" %)Singal: 0x1e = 30
	436	+* (% style="color:red" %)Mod: 0x01 = 1
	437	+* Interrupt: 0x00= 0
	438	+* Distance: 0x0039= 57 = 57
	439	+* Time stamp : 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
	440	+* Distance,Time stamp : 00396319baf0
	441	+* (% style="color:red" %) 8 sets of recorded data: Distance,Time stamp : //**00396319ba3c**//,.......
	442	+
	443	+
	444	+
	445	+
	446	+
348	348	== 2.4  Payload Explanation and Sensor Interface ==
349	349
350	350
351	351	=== 2.4.1  Device ID ===
352	352
	452	+
353	353	(((
354	354	By default, the Device ID equal to the last 6 bytes of IMEI.
355	355	)))
...	...	@@ -356,10 +356,12 @@
356	356
357	357	(((
358	358	User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
	459	+
	460	+
359	359	)))
360	360
361	361	(((
362		-**Example:**
	464	+(% style="color:blue" %)**Example :**
363	363	)))
364	364
365	365	(((
...	...	@@ -367,13 +367,26 @@
367	367	)))
368	368
369	369	(((
370		-The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
	472	+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.
371	371	)))
372	372
373	373
	476	+(% style="color:red" %)**NOTE: When the firmware version is v1.3.2 and later firmware:**
374	374
	478	+(% style="color:red" %)**By default, the Device ID equal to the last 15 bits of IMEI.**
	479	+
	480	+User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
	481	+
	482	+
	483	+(% style="color:blue" %)**Example :**
	484	+
	485	+AT+DEUI=868411056754138
	486	+
	487	+
	488	+
375	375	=== 2.4.2  Version Info ===
376	376
	491	+
377	377	(((
378	378	Specify the software version: 0x64=100, means firmware version 1.00.
379	379	)))
...	...	@@ -386,6 +386,7 @@
386	386
387	387	=== 2.4.3  Battery Info ===
388	388
	504	+
389	389	(((
390	390	Ex1: 0x0B45 = 2885mV
391	391	)))
...	...	@@ -398,6 +398,7 @@
398	398
399	399	=== 2.4.4  Signal Strength ===
400	400
	517	+
401	401	(((
402	402	NB-IoT Network signal Strength.
403	403	)))
...	...	@@ -430,9 +430,12 @@
430	430
431	431	=== 2.4.5  Distance ===
432	432
	550	+
433	433	Get the distance. Flat object range 280mm - 7500mm.
434	434
	553	+(((
435	435	For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
	555	+)))
436	436
437	437	(((
438	438	(((
...	...	@@ -450,6 +450,7 @@
450	450
451	451	=== 2.4.6  Digital Interrupt ===
452	452
	573	+
453	453	(((
454	454	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.
455	455	)))
...	...	@@ -484,6 +484,7 @@
484	484
485	485	=== 2.4.7  ​+5V Output ===
486	486
	608	+
487	487	(((
488	488	NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling.
489	489	)))
...	...	@@ -491,10 +491,14 @@
491	491
492	492	(((
493	493	The 5V output time can be controlled by AT Command.
	616	+
	617	+
494	494	)))
495	495
496	496	(((
497	497	(% style="color:blue" %)**AT+5VT=1000**
	622	+
	623	+
498	498	)))
499	499
500	500	(((
...	...	@@ -505,6 +505,7 @@
505	505
506	506	== 2.5  Downlink Payload ==
507	507
	634	+
508	508	By default, NDDS75 prints the downlink payload to console port.
509	509
510	510	[[image:image-20220709100028-1.png]]
...	...	@@ -555,9 +555,54 @@
555	555
556	556
557	557
558		-== 2.6  ​LED Indicator ==
	685	+== 2.6  Distance alarm function(Since firmware v1.3.2) ==
559	559
560	560
	688	+(% style="color:blue" %)** ➢ AT Command:**
	689	+
	690	+(% style="color:#037691" %)** AT+ LDDSALARM=min,max**
	691	+
	692	+² When min=0, and max≠0, Alarm higher than max
	693	+
	694	+² When min≠0, and max=0, Alarm lower than min
	695	+
	696	+² When min≠0 and max≠0, Alarm higher than max or lower than min
	697	+
	698	+
	699	+(% style="color:blue" %)** Example:**
	700	+
	701	+**AT+ LDDSALARM=260,2000**  ~/~/ Alarm when distance lower than 260.
	702	+
	703	+
	704	+
	705	+== 2.7  Set the number of data to be uploaded and the recording time ==
	706	+
	707	+
	708	+(% style="color:blue" %)** ➢ AT Command:**
	709	+
	710	+* (% 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)
	711	+* (% 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.
	712	+
	713	+
	714	+
	715	+
	716	+== 2.8  Read or Clear cached data ==
	717	+
	718	+
	719	+(% style="color:blue" %)** ➢ AT Command:**
	720	+
	721	+* (% style="color:#037691" %)** AT+CDP ** (%%) ~/~/ Read cached data
	722	+* (% style="color:#037691" %)** AT+CDP=0**  (%%) ~/~/  Clear cached data
	723	+
	724	+
	725	+
	726	+[[image:image-20220908175333-2.png]]
	727	+
	728	+
	729	+
	730	+== 2.9  ​LED Indicator ==
	731	+
	732	+
561	561	The NDDS75 has an internal LED which is to show the status of different state.
562	562
563	563
...	...	@@ -572,23 +572,27 @@
572	572
573	573
574	574
575		-== 2.7  ​Firmware Change Log ==
	747	+== 2.10  ​Firmware Change Log ==
576	576
577	577
578		-Download URL & Firmware Change log
	750	+(((
	751	+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]]
	752	+)))
579	579
580	580	(((
581		-[[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/]]
	755	+
582	582	)))
583	583
	758	+(((
	759	+Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
	760	+)))
584	584
585		-Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
586	586
587	587
	764	+== 2.11  ​Battery Analysis ==
588	588
589		-== 2.8  ​Battery Analysis ==
590	590
591		-=== 2.8.1  ​Battery Type ===
	767	+=== 2.11.1  ​Battery Type ===
592	592
593	593
594	594	(((
...	...	@@ -613,8 +613,9 @@
613	613
614	614
615	615
616		-=== 2.8.2  Power consumption Analyze ===
	792	+=== 2.11.2  Power consumption Analyze ===
617	617
	794	+
618	618	(((
619	619	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.
620	620	)))
...	...	@@ -651,8 +651,9 @@
651	651
652	652
653	653
654		-=== 2.8.3  ​Battery Note ===
	831	+=== 2.11.3  ​Battery Note ===
655	655
	833	+
656	656	(((
657	657	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.
658	658	)))
...	...	@@ -659,8 +659,9 @@
659	659
660	660
661	661
662		-=== 2.8.4  Replace the battery ===
	840	+=== 2.11.4  Replace the battery ===
663	663
	842	+
664	664	(((
665	665	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).
666	666	)))
...	...	@@ -669,6 +669,7 @@
669	669
670	670	= 3. ​ Access NB-IoT Module =
671	671
	851	+
672	672	(((
673	673	Users can directly access the AT command set of the NB-IoT module.
674	674	)))
...	...	@@ -675,6 +675,8 @@
675	675
676	676	(((
677	677	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/]]
	858	+
	859	+
678	678	)))
679	679
680	680	[[image:1657333200519-600.png]]
...	...	@@ -683,11 +683,13 @@
683	683
684	684	= 4.  Using the AT Commands =
685	685
	868	+
686	686	== 4.1  Access AT Commands ==
687	687
688		-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/]]
689	689
	872	+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]]
690	690
	874	+
691	691	AT+<CMD>?  : Help on <CMD>
692	692
693	693	AT+<CMD>         : Run <CMD>
...	...	@@ -727,7 +727,23 @@
727	727
728	728	AT+SERVADDR  : Server Address
729	729
	914	+AT+TR      : Get or Set record time"
730	730
	916	+AT+APN     : Get or set the APN
	917	+
	918	+AT+FBAND   : Get or Set whether to automatically modify the frequency band
	919	+
	920	+AT+DNSCFG  : Get or Set DNS Server
	921	+
	922	+AT+GETSENSORVALUE   : Returns the current sensor measurement
	923	+
	924	+AT+NOUD      : Get or Set the number of data to be uploaded
	925	+
	926	+AT+CDP     : Read or Clear cached data
	927	+
	928	+AT+LDDSALARM : Get or Set alarm of distance
	929	+
	930	+
731	731	(% style="color:#037691" %)**COAP Management**
732	732
733	733	AT+URI            : Resource parameters
...	...	@@ -761,6 +761,7 @@
761	761
762	762	= ​5.  FAQ =
763	763
	964	+
764	764	== 5.1 ​ How to Upgrade Firmware ==
765	765
766	766
...	...	@@ -773,7 +773,7 @@
773	773	)))
774	774
775	775	(((
776		-(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.
	977	+(% style="color:red" %)**Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.**
777	777	)))
778	778
779	779
...	...	@@ -780,6 +780,7 @@
780	780
781	781	= 6.  Trouble Shooting =
782	782
	984	+
783	783	== 6.1  ​Connection problem when uploading firmware ==
784	784
785	785
...	...	@@ -795,6 +795,7 @@
795	795
796	796	== 6.2  AT Command input doesn't work ==
797	797
	1000	+
798	798	(((
799	799	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.
800	800
...	...	@@ -820,7 +820,7 @@
820	820
821	821	(% style="color:#037691" %)**Package Includes**:
822	822
823		-* NSE01 NB-IoT Distance Detect Sensor Node x 1
	1026	+* NDDS75 NB-IoT Distance Detect Sensor Node x 1
824	824	* External antenna x 1
825	825	)))
826	826
...	...	@@ -827,9 +827,9 @@
827	827	(((
828	828
829	829
	1033	+
830	830	(% style="color:#037691" %)**Dimension and weight**:
831	831
832		-
833	833	* Device Size: 13.0 x 5 x 4.5 cm
834	834	* Device Weight: 150g
835	835	* Package Size / pcs : 15 x 12x 5.5 cm
...	...	@@ -845,5 +845,6 @@
845	845
846	846	= 9.  Support =
847	847
	1051	+
848	848	* 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.
849	849	* 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