Summary

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

Details

Page properties

Content

...	...	@@ -16,6 +16,7 @@
16	16
17	17	= 1.  Introduction =
18	18
	19	+
19	19	== 1.1 ​ What is NDDS75 Distance Detection Sensor ==
20	20
21	21	(((
...	...	@@ -56,6 +56,7 @@
56	56
57	57	== 1.2 ​ Features ==
58	58
	60	+
59	59	* NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
60	60	* Ultra low power consumption
61	61	* Distance Detection by Ultrasonic technology
...	...	@@ -79,12 +79,12 @@
79	79
80	80	(% style="color:#037691" %)**NB-IoT Spec:**
81	81
82		-* - B1 @H-FDD: 2100MHz
83		-* - B3 @H-FDD: 1800MHz
84		-* - B8 @H-FDD: 900MHz
85		-* - B5 @H-FDD: 850MHz
86		-* - B20 @H-FDD: 800MHz
87		-* - 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
88	88
89	89	(% style="color:#037691" %)**Battery:**
90	90
...	...	@@ -101,6 +101,7 @@
101	101
102	102	== ​1.4  Applications ==
103	103
	106	+
104	104	* Smart Buildings & Home Automation
105	105	* Logistics and Supply Chain Management
106	106	* Smart Metering
...	...	@@ -112,6 +112,7 @@
112	112	​
113	113
114	114
	118	+
115	115	== 1.5  Pin Definitions ==
116	116
117	117
...	...	@@ -121,8 +121,10 @@
121	121
122	122	= 2.  Use NDDS75 to communicate with IoT Server =
123	123
	128	+
124	124	== 2.1  How it works ==
125	125
	131	+
126	126	(((
127	127	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.
128	128	)))
...	...	@@ -148,6 +148,7 @@
148	148
149	149	=== 2.2.1 Test Requirement ===
150	150
	157	+
151	151	(((
152	152	To use NDDS75 in your city, make sure meet below requirements:
153	153	)))
...	...	@@ -157,7 +157,7 @@
157	157	* Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
158	158
159	159	(((
160		-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
	167	+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.
161	161	)))
162	162
163	163
...	...	@@ -167,6 +167,7 @@
167	167
168	168	=== 2.2.2 Insert SIM card ===
169	169
	177	+
170	170	(((
171	171	Insert the NB-IoT Card get from your provider.
172	172	)))
...	...	@@ -182,6 +182,7 @@
182	182
183	183	=== 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
184	184
	193	+
185	185	(((
186	186	(((
187	187	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.
...	...	@@ -190,15 +190,16 @@
190	190
191	191	[[image:image-20220709092052-2.png]]
192	192
193		-**Connection:**
194	194
195		- (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
	203	+(% style="color:blue" %)**Connection:**
196	196
197		- (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
	205	+ (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND**
198	198
199		- (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
	207	+**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)**
200	200
	209	+**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)**
201	201
	211	+
202	202	In the PC, use below serial tool settings:
203	203
204	204	* Baud:  (% style="color:green" %)**9600**
...	...	@@ -213,8 +213,9 @@
213	213
214	214	[[image:1657329814315-101.png]]
215	215
	226	+
216	216	(((
217		-(% 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/]]
	228	+(% 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]]**
218	218	)))
219	219
220	220
...	...	@@ -221,9 +221,10 @@
221	221
222	222	=== 2.2.4 Use CoAP protocol to uplink data ===
223	223
224		-(% 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/]]
225	225
	236	+(% 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/]]**
226	226
	238	+
227	227	(((
228	228	**Use below commands:**
229	229	)))
...	...	@@ -232,21 +232,29 @@
232	232	(% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
233	233	)))
234	234	* (((
235		-(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
	247	+(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/  to set CoAP server address and port
236	236	)))
237	237	* (((
238		-(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
	250	+(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/  Set COAP resource path
	251	+
	252	+
	253	+
239	239	)))
240	240
241	241	(((
242	242	For parameter description, please refer to AT command set
	258	+
	259	+
243	243	)))
244	244
245	245	[[image:1657330452568-615.png]]
246	246
247	247
	265	+
248	248	(((
249	249	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.
	268	+
	269	+
250	250	)))
251	251
252	252	[[image:1657330472797-498.png]]
...	...	@@ -256,9 +256,9 @@
256	256	=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
257	257
258	258
259		-* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
260		-* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
261		-* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
	279	+* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
	280	+* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/  to set UDP server address and port
	281	+* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessary
262	262
263	263	[[image:1657330501006-241.png]]
264	264
...	...	@@ -270,13 +270,13 @@
270	270	=== 2.2.6 Use MQTT protocol to uplink data ===
271	271
272	272
273		-* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
274		-* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
275		-* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
276		-* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
277		-* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
278		-* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/Set the sending topic of MQTT
279		-* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/Set the subscription topic of MQTT
	293	+* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
	294	+* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/  Set MQTT server address and port
	295	+* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/  Set up the CLIENT of MQTT
	296	+* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/  Set the username of MQTT
	297	+* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/  Set the password of MQTT
	298	+* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/  Set the sending topic of MQTT
	299	+* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/  Set the subscription topic of MQTT
280	280
281	281	[[image:1657249978444-674.png]]
282	282
...	...	@@ -293,8 +293,8 @@
293	293	=== 2.2.7 Use TCP protocol to uplink data ===
294	294
295	295
296		-* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
297		-* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
	316	+* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
	317	+* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/  to set TCP server address and port
298	298
299	299	[[image:image-20220709093918-1.png]]
300	300
...	...	@@ -305,25 +305,34 @@
305	305
306	306	=== 2.2.8 Change Update Interval ===
307	307
	328	+
308	308	User can use below command to change the (% style="color:green" %)**uplink interval**.
309	309
310		-* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
	331	+* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/  Set Update Interval to 600s
311	311
312	312	(((
	334	+
	335	+
	336	+
313	313	(% style="color:red" %)**NOTE:**
314		-)))
315	315
316		-(((
317		-(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
	339	+(% style="color:red" %)**1. By default, the device will send an uplink message every 1 hour.**
	340	+
	341	+(% style="color:red" %)**2. When the firmware version is v1.3.2 and later firmware:**
318	318	)))
319	319
	344	+(% 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).**
320	320
321	321
	347	+
322	322	== 2.3  Uplink Payload ==
323	323
324		-In this mode, uplink payload includes in total 14 bytes
325	325
	351	+=== 2.3.1  Before Firmware v1.3.2 ===
326	326
	353	+
	354	+In this mode, uplink payload includes in total 14 bytes
	355	+
327	327	(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
328	328	|=(% style="width: 60px;" %)(((
329	329	**Size(bytes)**
...	...	@@ -331,49 +331,80 @@
331	331	|(% 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"]]
332	332
333	333	(((
334		-If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
	363	+If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
335	335	)))
336	336
337	337
338	338	[[image:1657331036973-987.png]]
339	339
340		-(((
	369	+
	370	+
	371	+The payload is **ASCII** string, representative same HEX:
	372	+
	373	+(% style="background-color:yellow" %)**0x 724031556159 0064 0c6c 19 0292 00 **
	374	+
	375	+**where :**
	376	+
	377	+* (% style="color:#037691" %)**Device ID:**(%%) 0x724031556159 = 724031556159
	378	+
	379	+* (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
	380	+
	381	+* (% style="color:#037691" %)**BAT:** (%%) 0x0c6c = 3180 mV = 3.180V
	382	+
	383	+* (% style="color:#037691" %)**Signal:**(%%)  0x19 = 25
	384	+
	385	+* (% style="color:#037691" %)**Distance:**  (%%)0x0292= 658 mm
	386	+
	387	+* (% style="color:#037691" %)**Interrupt:**(%%) 0x00 = 0
	388	+
	389	+=== 2.3.2  Since firmware v1.3.2 ===
	390	+
	391	+
	392	+In this mode, uplink payload includes 69 bytes in total by default.
	393	+
	394	+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.
	395	+
	396	+(% border="1" style="background-color:#ffffcc; color:green; width:490px" %)
	397	+|=(% 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**
	398	+|=(% 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	+
	400	+If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
	401	+
	402	+[[image:image-20220908175246-1.png]]
	403	+
	404	+
341	341	The payload is ASCII string, representative same HEX:
342		-)))
343	343
344		-(((
345		-0x72403155615900640c6c19029200 where:
346		-)))
	407	+**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 (%%)**
347	347
348		-* (((
349		-Device ID: 0x724031556159 = 724031556159
350		-)))
351		-* (((
352		-Version: 0x0064=100=1.0.0
353		-)))
	409	+**where:**
354	354
355		-* (((
356		-BAT: 0x0c6c = 3180 mV = 3.180V
357		-)))
358		-* (((
359		-Signal: 0x19 = 25
360		-)))
361		-* (((
362		-Distance: 0x0292= 658 mm
363		-)))
364		-* (((
365		-Interrupt: 0x00 = 0
	411	+* (% style="color:#037691" %)**Device ID:**(%%) f867787050213317 = f867787050213317
366	366
	413	+* (% style="color:#037691" %)**Version:**(%%) 0x0084=132=1.3.2
367	367
	415	+* (% style="color:#037691" %)**BAT:**(%%)  0x0cf4 = 3316 mV = 3.316V
368	368
369		-
370		-)))
	417	+* (% style="color:#037691" %)**Singal:**(%%)  0x1e = 30
371	371
	419	+* (% style="color:#037691" %)**Mod:**(%%)**     **0x01 = 1
	420	+
	421	+* (% style="color:#037691" %)**Interrupt:**(%%) 0x00= 0
	422	+
	423	+* (% style="color:#037691" %)**Distance:**(%%) 0x0039= 57 = 57
	424	+
	425	+* (% style="color:#037691" %)**Time stamp:**(%%) 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
	426	+
	427	+* (% style="color:#037691" %)**Distance,Time stamp:**(%%) 00396319baf0
	428	+
	429	+* (% style="color:#037691" %)**8 sets of recorded data: Distance,Time stamp :**(%%) //**00396319ba3c**//,.......
	430	+
372	372	== 2.4  Payload Explanation and Sensor Interface ==
373	373
374	374
375	375	=== 2.4.1  Device ID ===
376	376
	436	+
377	377	(((
378	378	By default, the Device ID equal to the last 6 bytes of IMEI.
379	379	)))
...	...	@@ -380,10 +380,12 @@
380	380
381	381	(((
382	382	User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
	443	+
	444	+
383	383	)))
384	384
385	385	(((
386		-**Example:**
	448	+(% style="color:blue" %)**Example :**
387	387	)))
388	388
389	389	(((
...	...	@@ -391,13 +391,26 @@
391	391	)))
392	392
393	393	(((
394		-The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
	456	+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.
395	395	)))
396	396
397	397
	460	+(% style="color:red" %)**NOTE: When the firmware version is v1.3.2 and later firmware:**
398	398
	462	+(% style="color:red" %)**By default, the Device ID equal to the last 15 bits of IMEI.**
	463	+
	464	+User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
	465	+
	466	+
	467	+(% style="color:blue" %)**Example :**
	468	+
	469	+AT+DEUI=868411056754138
	470	+
	471	+
	472	+
399	399	=== 2.4.2  Version Info ===
400	400
	475	+
401	401	(((
402	402	Specify the software version: 0x64=100, means firmware version 1.00.
403	403	)))
...	...	@@ -410,6 +410,7 @@
410	410
411	411	=== 2.4.3  Battery Info ===
412	412
	488	+
413	413	(((
414	414	Ex1: 0x0B45 = 2885mV
415	415	)))
...	...	@@ -422,6 +422,7 @@
422	422
423	423	=== 2.4.4  Signal Strength ===
424	424
	501	+
425	425	(((
426	426	NB-IoT Network signal Strength.
427	427	)))
...	...	@@ -454,6 +454,7 @@
454	454
455	455	=== 2.4.5  Distance ===
456	456
	534	+
457	457	Get the distance. Flat object range 280mm - 7500mm.
458	458
459	459	(((
...	...	@@ -476,6 +476,7 @@
476	476
477	477	=== 2.4.6  Digital Interrupt ===
478	478
	557	+
479	479	(((
480	480	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.
481	481	)))
...	...	@@ -485,7 +485,7 @@
485	485	)))
486	486
487	487	(((
488		-(% 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]])**.**
	567	+(% 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]])**.**
489	489	)))
490	490
491	491
...	...	@@ -510,6 +510,7 @@
510	510
511	511	=== 2.4.7  ​+5V Output ===
512	512
	592	+
513	513	(((
514	514	NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling.
515	515	)))
...	...	@@ -517,10 +517,14 @@
517	517
518	518	(((
519	519	The 5V output time can be controlled by AT Command.
	600	+
	601	+
520	520	)))
521	521
522	522	(((
523	523	(% style="color:blue" %)**AT+5VT=1000**
	606	+
	607	+
524	524	)))
525	525
526	526	(((
...	...	@@ -531,6 +531,7 @@
531	531
532	532	== 2.5  Downlink Payload ==
533	533
	618	+
534	534	By default, NDDS75 prints the downlink payload to console port.
535	535
536	536	[[image:image-20220709100028-1.png]]
...	...	@@ -581,124 +581,96 @@
581	581
582	582
583	583
584		-== 2.6  ​LED Indicator ==
	669	+== 2.6  Distance alarm function(Since firmware v1.3.2) ==
585	585
586	586
587		-The NDDS75 has an internal LED which is to show the status of different state.
	672	+(% style="color:blue" %)** ➢ AT Command:**
588	588
	674	+(% style="color:#037691" %)** AT+ LDDSALARM=min,max**
589	589
590		-* When power on, NDDS75 will detect if sensor probe is connected, if probe detected, LED will blink four times. (no blinks in this step is no probe)
591		-* Then the LED will be on for 1 second means device is boot normally.
592		-* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
593		-* For each uplink probe, LED will be on for 500ms.
	676	+² When min=0, and max≠0, Alarm higher than max
594	594
595		-(((
596		-
597		-)))
	678	+² When min≠0, and max=0, Alarm lower than min
598	598
	680	+² When min≠0 and max≠0, Alarm higher than max or lower than min
599	599
600	600
601		-== 2.7  ​Firmware Change Log ==
	683	+(% style="color:blue" %)** Example:**
602	602
	685	+**AT+ LDDSALARM=260,2000**  ~/~/ Alarm when distance lower than 260.
603	603
604		-(((
605		-Download URL & Firmware Change log
606		-)))
607	607
608		-(((
609		-[[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/]]
610		-)))
611	611
	689	+== 2.7  Set the number of data to be uploaded and the recording time ==
612	612
613		-(((
614		-Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
615		-)))
616	616
	692	+(% style="color:blue" %)** ➢ AT Command:**
617	617
	694	+* (% 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)
	695	+* (% 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.
618	618
619		-== 2.8  ​Battery Analysis ==
	697	+ The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
620	620
621		-=== 2.8.1  ​Battery Type ===
	699	+[[image:image-20221009001114-1.png||height="687" width="955"]]
622	622
623	623
624		-(((
625		-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.
626		-)))
627	627
628		-(((
629		-The battery is designed to last for several years depends on the actually use environment and update interval.
630		-)))
	703	+== 2.8  Read or Clear cached data ==
631	631
632		-(((
633		-The battery related documents as below:
634		-)))
635	635
636		-* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
637		-* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
638		-* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
	706	+(% style="color:blue" %)** ➢ AT Command:**
639	639
640		-(((
641		-[[image:image-20220709101450-2.png]]
642		-)))
	708	+* (% style="color:#037691" %)** AT+CDP ** (%%) ~/~/  Read cached data
	709	+* (% style="color:#037691" %)** AT+CDP=0**  (%%) ~/~/  Clear cached data
643	643
	711	+[[image:image-20220908175333-2.png]]
644	644
645	645
646		-=== 2.8.2  Power consumption Analyze ===
647	647
648		-(((
649		-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.
650		-)))
	715	+== 2.9  ​LED Indicator ==
651	651
652	652
653		-(((
654		-Instruction to use as below:
655		-)))
	718	+The NDDS75 has an internal LED which is to show the status of different state.
656	656
657		-(((
658		-(% 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/]]
659		-)))
660	660
	721	+* When power on, NDDS75 will detect if sensor probe is connected, if probe detected, LED will blink four times. (no blinks in this step is no probe)
	722	+* Then the LED will be on for 1 second means device is boot normally.
	723	+* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
	724	+* For each uplink probe, LED will be on for 500ms.
661	661
662	662	(((
663		-(% style="color:blue" %)**Step 2: **(%%) Open it and choose
	727	+
664	664	)))
665	665
666		-* (((
667		-Product Model
668		-)))
669		-* (((
670		-Uplink Interval
671		-)))
672		-* (((
673		-Working Mode
674		-)))
675	675
676		-(((
677		-And the Life expectation in difference case will be shown on the right.
678		-)))
679	679
680		-[[image:image-20220709110451-3.png]]
	732	+== 2.10  ​Firmware Change Log ==
681	681
682	682
	735	+(((
	736	+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]]
	737	+)))
683	683
684		-=== 2.8.3  ​Battery Note ===
	739	+(((
	740	+
	741	+)))
685	685
686	686	(((
687		-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.
	744	+Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
688	688	)))
689	689
690	690
691	691
692		-=== 2.8.4  Replace the battery ===
	749	+== 2.11 Battery & Power Consumption ==
693	693
694		-(((
695		-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).
696		-)))
697	697
	752	+PS-LB-NA uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace.
698	698
	754	+[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] .
699	699
700	700	= 3. ​ Access NB-IoT Module =
701	701
	758	+
702	702	(((
703	703	Users can directly access the AT command set of the NB-IoT module.
704	704	)))
...	...	@@ -705,6 +705,8 @@
705	705
706	706	(((
707	707	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/]]
	765	+
	766	+
708	708	)))
709	709
710	710	[[image:1657333200519-600.png]]
...	...	@@ -713,84 +713,103 @@
713	713
714	714	= 4.  Using the AT Commands =
715	715
	775	+
716	716	== 4.1  Access AT Commands ==
717	717
718		-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/]]
719	719
	779	+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]]
720	720
721		-AT+<CMD>?  : Help on <CMD>
722	722
723		-AT+<CMD>         : Run <CMD>
	782	+AT+<CMD>?  :  Help on <CMD>
724	724
725		-AT+<CMD>=<value> : Set the value
	784	+AT+<CMD>         :  Run <CMD>
726	726
727		-AT+<CMD>=?  : Get the value
	786	+AT+<CMD>=<value> :  Set the value
728	728
	788	+AT+<CMD>=?  :  Get the value
729	729
	790	+
730	730	(% style="color:#037691" %)**General Commands**(%%)
731	731
732		-AT  : Attention
	793	+AT  :  Attention
733	733
734		-AT?  : Short Help
	795	+AT?  :  Short Help
735	735
736		-ATZ  : MCU Reset
	797	+ATZ  :  MCU Reset
737	737
738		-AT+TDC  : Application Data Transmission Interval
	799	+AT+TDC  :  Application Data Transmission Interval
739	739
740		-AT+CFG  : Print all configurations
	801	+AT+CFG  :  Print all configurations
741	741
742		-AT+CFGMOD           : Working mode selection
	803	+AT+CFGMOD           :  Working mode selection
743	743
744		-AT+INTMOD            : Set the trigger interrupt mode
	805	+AT+INTMOD            :  Set the trigger interrupt mode
745	745
746		-AT+5VT  : Set extend the time of 5V power
	807	+AT+5VT  :  Set extend the time of 5V power
747	747
748		-AT+PRO  : Choose agreement
	809	+AT+PRO  :  Choose agreement
749	749
750		-AT+WEIGRE  : Get weight or set weight to 0
	811	+AT+WEIGRE  :  Get weight or set weight to 0
751	751
752		-AT+WEIGAP  : Get or Set the GapValue of weight
	813	+AT+WEIGAP  :  Get or Set the GapValue of weight
753	753
754		-AT+RXDL  : Extend the sending and receiving time
	815	+AT+RXDL  :  Extend the sending and receiving time
755	755
756		-AT+CNTFAC  : Get or set counting parameters
	817	+AT+CNTFAC  :  Get or set counting parameters
757	757
758		-AT+SERVADDR  : Server Address
	819	+AT+SERVADDR  :  Server Address
759	759
	821	+AT+TR  :  Get or Set record time"
760	760
	823	+AT+APN     :  Get or set the APN
	824	+
	825	+AT+FBAND  :  Get or Set whether to automatically modify the frequency band
	826	+
	827	+AT+DNSCFG  : Get or Set DNS Server
	828	+
	829	+AT+GETSENSORVALUE   :  Returns the current sensor measurement
	830	+
	831	+AT+NOUD  :  Get or Set the number of data to be uploaded
	832	+
	833	+AT+CDP     :  Read or Clear cached data
	834	+
	835	+AT+LDDSALARM :  Get or Set alarm of distance
	836	+
	837	+
761	761	(% style="color:#037691" %)**COAP Management**
762	762
763		-AT+URI            : Resource parameters
	840	+AT+URI            :  Resource parameters
764	764
765	765
766	766	(% style="color:#037691" %)**UDP Management**
767	767
768		-AT+CFM          : Upload confirmation mode (only valid for UDP)
	845	+AT+CFM          :  Upload confirmation mode (only valid for UDP)
769	769
770	770
771	771	(% style="color:#037691" %)**MQTT Management**
772	772
773		-AT+CLIENT               : Get or Set MQTT client
	850	+AT+CLIENT  :  Get or Set MQTT client
774	774
775		-AT+UNAME  : Get or Set MQTT Username
	852	+AT+UNAME  :  Get or Set MQTT Username
776	776
777		-AT+PWD                  : Get or Set MQTT password
	854	+AT+PWD  :  Get or Set MQTT password
778	778
779		-AT+PUBTOPIC  : Get or Set MQTT publish topic
	856	+AT+PUBTOPIC  :  Get or Set MQTT publish topic
780	780
781		-AT+SUBTOPIC  : Get or Set MQTT subscription topic
	858	+AT+SUBTOPIC  :  Get or Set MQTT subscription topic
782	782
783	783
784	784	(% style="color:#037691" %)**Information**
785	785
786		-AT+FDR  : Factory Data Reset
	863	+AT+FDR  :  Factory Data Reset
787	787
788		-AT+PWORD  : Serial Access Password
	865	+AT+PWORD  :  Serial Access Password
789	789
790	790
791	791
792	792	= ​5.  FAQ =
793	793
	871	+
794	794	== 5.1 ​ How to Upgrade Firmware ==
795	795
796	796
...	...	@@ -803,7 +803,7 @@
803	803	)))
804	804
805	805	(((
806		-(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.
	884	+(% style="color:red" %)**Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.**
807	807	)))
808	808
809	809
...	...	@@ -810,6 +810,7 @@
810	810
811	811	= 6.  Trouble Shooting =
812	812
	891	+
813	813	== 6.1  ​Connection problem when uploading firmware ==
814	814
815	815
...	...	@@ -825,6 +825,7 @@
825	825
826	826	== 6.2  AT Command input doesn't work ==
827	827
	907	+
828	828	(((
829	829	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.
830	830
...	...	@@ -857,6 +857,7 @@
857	857	(((
858	858
859	859
	940	+
860	860	(% style="color:#037691" %)**Dimension and weight**:
861	861
862	862	* Device Size: 13.0 x 5 x 4.5 cm
...	...	@@ -874,5 +874,6 @@
874	874
875	875	= 9.  Support =
876	876
	958	+
877	877	* 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.
878	878	* Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[support@dragino.com>>url:http://../../../../../../D:%5C%E5%B8%82%E5%9C%BA%E8%B5%84%E6%96%99%5C%E8%AF%B4%E6%98%8E%E4%B9%A6%5CLoRa%5CLT%E7%B3%BB%E5%88%97%5Csupport@dragino.com]]

image-20220908175246-1.png

Author

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

Size

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

Content

image-20220908175333-2.png

Author

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

Size

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

Content

image-20221009001114-1.png

Author

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

Size

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

Content