Wiki source code of NDDS75 -- NB-IoT Distance Detect Sensor User Manual

Version 108.27 by Xiaoling on 2024/01/19 17:55

version	line-number	content
108.27	1
	2
74.2	3	(% style="text-align:center" %)
	4	[[image:image-20220709085040-1.png\|\|height="542" width="524"]]
1.1	5
	6
	7
35.25	8
	9
35.4	10	Table of Contents:
1.1	11
95.4	12	{{toc/}}
1.1	13
	14
	15
	16
31.17	17
65.3	18
44.2	19	= 1. Introduction =
1.1	20
67.2	21	== 1.1 What is NDDS75 Distance Detection Sensor ==
1.1	22
12.2	23	(((
35.4	24
	25
65.9	26	(((
97.14	27	(((
68.2	28	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.
97.14	29	)))
97.13	30
97.14	31	(((
97.13	32	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.
97.14	33	)))
97.13	34
97.14	35	(((
97.13	36	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.
97.14	37	)))
97.13	38
97.14	39	(((
97.13	40	NDDS75 supports different uplink methods include (% style="color:blue" %)TCP, MQTT, UDP and CoAP (%%)for different application requirement.
97.14	41	)))
97.13	42
97.14	43	(((
97.13	44	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)
97.14	45	)))
97.13	46
97.14	47	(((
97.13	48	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.
65.9	49	)))
97.14	50	)))
4.2	51
42.2	52
12.2	53	)))
4.2	54
75.2	55	[[image:1657327959271-447.png]]
4.2	56
	57
65.3	58	== 1.2 Features ==
13.3	59
100.2	60
44.2	61	* NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
75.3	62	* Ultra low power consumption
	63	* Distance Detection by Ultrasonic technology
	64	* Flat object range 280mm - 7500mm
	65	* Accuracy: ±(1cm+S*0.3%) (S: Distance)
	66	* Cable Length: 25cm
4.2	67	* AT Commands to change parameters
	68	* Uplink on periodically
	69	* Downlink to change configure
	70	* IP66 Waterproof Enclosure
44.2	71	* Micro SIM card slot for NB-IoT SIM
	72	* 8500mAh Battery for long term use
4.2	73
44.2	74	== 1.3 Specification ==
	75
100.2	76
44.2	77	(% style="color:#037691" %)Common DC Characteristics:
	78
	79	* Supply Voltage: 2.1v ~~ 3.6v
	80	* Operating Temperature: -40 ~~ 85°C
	81
	82	(% style="color:#037691" %)NB-IoT Spec:
	83
108.8	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
44.2	90
75.3	91	(% style="color:#037691" %)Battery:
4.2	92
75.3	93	* Li/SOCI2 un-chargeable battery
	94	* Capacity: 8500mAh
	95	* Self Discharge: <1% / Year @ 25°C
	96	* Max continuously current: 130mA
	97	* Max boost current: 2A, 1 second
14.2	98
75.3	99	(% style="color:#037691" %)Power Consumption
4.2	100
75.3	101	* STOP Mode: 10uA @ 3.3v
108.13	102	* Max transmit power: 350mA@3.3v
75.3	103
44.2	104	== 1.4 Applications ==
4.2	105
100.2	106
75.4	107	* Smart Buildings & Home Automation
	108	* Logistics and Supply Chain Management
	109	* Smart Metering
4.2	110	* Smart Agriculture
75.4	111	* Smart Cities
	112	* Smart Factory
4.2	113
15.6	114	(% class="wikigeneratedid" id="H200B1.5FirmwareChangelog" %)
	115
4.2	116
75.4	117
44.2	118	== 1.5 Pin Definitions ==
15.6	119
	120
76.2	121	[[image:1657328609906-564.png]]
4.2	122
14.3	123
81.2	124	= 2. Use NDDS75 to communicate with IoT Server =
14.3	125
45.2	126	== 2.1 How it works ==
14.3	127
100.2	128
15.3	129	(((
77.2	130	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.
15.3	131	)))
4.2	132
45.2	133
15.3	134	(((
77.2	135	The diagram below shows the working flow in default firmware of NDDS75:
15.3	136	)))
4.2	137
77.2	138	(((
	139
	140	)))
4.2	141
77.2	142	[[image:1657328659945-416.png]]
	143
45.2	144	(((
	145
	146	)))
4.2	147
81.2	148	== 2.2 Configure the NDDS75 ==
4.2	149
45.4	150	=== 2.2.1 Test Requirement ===
4.2	151
100.2	152
65.10	153	(((
81.2	154	To use NDDS75 in your city, make sure meet below requirements:
65.10	155	)))
4.2	156
45.4	157	* Your local operator has already distributed a NB-IoT Network there.
97.22	158	* The local NB-IoT network used the band that NDDS75 supports.
45.4	159	* Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
4.2	160
48.2	161	(((
100.2	162	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.
48.2	163	)))
4.2	164
	165
81.2	166	[[image:1657328756309-230.png]]
4.2	167
	168
45.5	169	=== 2.2.2 Insert SIM card ===
4.2	170
100.2	171
65.11	172	(((
45.4	173	Insert the NB-IoT Card get from your provider.
65.11	174	)))
4.2	175
65.11	176	(((
45.4	177	User need to take out the NB-IoT module and insert the SIM card like below:
65.11	178	)))
4.2	179
81.2	180	[[image:1657328884227-504.png]]
4.2	181
	182
81.2	183	=== 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
4.2	184
100.2	185
48.2	186	(((
	187	(((
81.2	188	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.
48.2	189	)))
	190	)))
19.2	191
81.2	192	[[image:image-20220709092052-2.png]]
4.2	193
100.4	194
104.7	195	(% style="color:blue" %)Connection:
4.2	196
104.7	197	(% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
4.2	198
104.7	199	~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)
4.2	200
104.7	201	~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)
4.2	202
	203
45.4	204	In the PC, use below serial tool settings:
	205
57.4	206	* Baud: (% style="color:green" %)9600
48.2	207	* Data bits: (% style="color:green" %)8(%%)
	208	* Stop bits: (% style="color:green" %)1
57.4	209	* Parity: (% style="color:green" %)None
48.2	210	* Flow Control: (% style="color:green" %)None
45.4	211
48.2	212	(((
81.2	213	Make sure the switch is in FLASH position, then power on device by connecting the jumper on NDDS75. NDDS75 will output system info once power on as below, we can enter the (% style="color:green" %)password: 12345678(%%) to access AT Command input.
48.2	214	)))
45.4	215
81.2	216	[[image:1657329814315-101.png]]
45.4	217
100.4	218
65.12	219	(((
100.4	220	(% 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]]
65.12	221	)))
45.4	222
	223
48.2	224	=== 2.2.4 Use CoAP protocol to uplink data ===
45.4	225
	226
100.2	227	(% 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/]]
45.4	228
100.2	229
97.9	230	(((
50.2	231	Use below commands:
97.9	232	)))
45.4	233
97.9	234	* (((
	235	(% style="color:blue" %)AT+PRO=1 (%%) ~/~/ Set to use CoAP protocol to uplink
	236	)))
	237	* (((
104.7	238	(% style="color:blue" %)AT+SERVADDR=120.24.4.116,5683 (%%)~/~/ to set CoAP server address and port
97.9	239	)))
	240	* (((
104.7	241	(% style="color:blue" %)AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" (%%) ~/~/ Set COAP resource path
100.6	242
	243
97.9	244	)))
45.4	245
97.9	246	(((
45.4	247	For parameter description, please refer to AT command set
104.2	248
	249
97.9	250	)))
45.4	251
86.2	252	[[image:1657330452568-615.png]]
45.4	253
	254
97.10	255	(((
86.2	256	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.
97.10	257	)))
45.4	258
86.2	259	[[image:1657330472797-498.png]]
45.4	260
	261
45.6	262	=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
45.4	263
	264
104.7	265	* (% style="color:blue" %)AT+PRO=2 (%%) ~/~/ Set to use UDP protocol to uplink
	266	* (% style="color:blue" %)AT+SERVADDR=120.24.4.116,5601 (%%) ~/~/ to set UDP server address and port
	267	* (% style="color:blue" %)AT+CFM=1 (%%) ~/~/ If the server does not respond, this command is unnecessary
45.4	268
86.2	269	[[image:1657330501006-241.png]]
45.4	270
	271
86.2	272	[[image:1657330533775-472.png]]
45.4	273
52.3	274
45.7	275	=== 2.2.6 Use MQTT protocol to uplink data ===
45.4	276
	277
104.7	278	* (% style="color:blue" %)AT+PRO=3 (%%) ~/~/ Set to use MQTT protocol to uplink
	279	* (% style="color:blue" %)AT+SERVADDR=120.24.4.116,1883 (%%) ~/~/ Set MQTT server address and port
	280	* (% style="color:blue" %)AT+CLIENT=CLIENT (%%)~/~/ Set up the CLIENT of MQTT
	281	* (% style="color:blue" %)AT+UNAME=UNAME (%%)~/~/ Set the username of MQTT
	282	* (% style="color:blue" %)AT+PWD=PWD (%%)~/~/ Set the password of MQTT
	283	* (% style="color:blue" %)AT+PUBTOPIC=NDDS75_PUB (%%)~/~/ Set the sending topic of MQTT
	284	* (% style="color:blue" %)AT+SUBTOPIC=NDDS75_SUB (%%) ~/~/ Set the subscription topic of MQTT
45.4	285
54.2	286	[[image:1657249978444-674.png]]
45.4	287
54.2	288
89.2	289	[[image:1657330723006-866.png]]
54.2	290
45.4	291
54.3	292	(((
45.4	293	MQTT protocol has a much higher power consumption compare vs UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval.
54.3	294	)))
45.4	295
	296
45.7	297	=== 2.2.7 Use TCP protocol to uplink data ===
45.4	298
	299
104.7	300	* (% style="color:blue" %)AT+PRO=4 (%%) ~/~/ Set to use TCP protocol to uplink
	301	* (% style="color:blue" %)AT+SERVADDR=120.24.4.116,5600 (%%) ~/~/ to set TCP server address and port
45.4	302
89.2	303	[[image:image-20220709093918-1.png]]
45.4	304
	305
89.2	306	[[image:image-20220709093918-2.png]]
45.4	307
57.6	308
45.7	309	=== 2.2.8 Change Update Interval ===
45.4	310
100.2	311
48.2	312	User can use below command to change the (% style="color:green" %)uplink interval.
45.4	313
104.7	314	* (% style="color:blue" %)AT+TDC=600 (%%)~/~/ Set Update Interval to 600s
45.4	315
56.3	316	(((
104.4	317
103.1	318
104.4	319	(% style="color:red" %)NOTE:
	320
104.5	321	(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
104.4	322
104.5	323	(% style="color:red" %)2. When the firmware version is v1.3.2 and later firmware:
56.3	324	)))
45.4	325
104.2	326	(% 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).
45.4	327
103.1	328
57.2	329	== 2.3 Uplink Payload ==
4.2	330
104.7	331	=== 2.3.1 Before Firmware v1.3.2 ===
104.1	332
104.2	333
90.2	334	In this mode, uplink payload includes in total 14 bytes
32.9	335
108.23	336	(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:440px" %)
	337	\|=(% style="width: 61px;background-color:#4F81BD;color:white" %)(((
57.2	338	Size(bytes)
108.23	339	)))\|=(% style="width: 61px;background-color:#4F81BD;color:white" %)6\|=(% style="width: 37px;background-color:#4F81BD;color:white" %)2\|=(% style="width: 37px;background-color:#4F81BD;color:white" %)2\|=(% style="width: 82px;background-color:#4F81BD;color:white" %)1\|=(% style="width: 102px;background-color:#4F81BD;color:white" %)2\|=(% style="width: 60px;background-color:#4F81BD;color:white" %)1
	340	\|(% 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"]]
57.2	341
65.13	342	(((
108.8	343	If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
65.13	344	)))
57.2	345
	346
90.2	347	[[image:1657331036973-987.png]]
57.2	348
100.4	349
104.2	350	The payload is ASCII string, representative same HEX:
57.2	351
108.3	352	(% style="background-color:yellow" %)0x 724031556159 0064 0c6c 19 0292 00
57.2	353
108.2	354	where :
57.2	355
108.2	356	* (% style="color:#037691" %)Device ID:(%%) 0x724031556159 = 724031556159
95.5	357
108.2	358	* (% style="color:#037691" %)Version:(%%) 0x0064=100=1.0.0
104.2	359
108.2	360	* (% style="color:#037691" %)BAT: (%%) 0x0c6c = 3180 mV = 3.180V
104.2	361
108.2	362	* (% style="color:#037691" %)Signal:(%%) 0x19 = 25
104.2	363
108.2	364	* (% style="color:#037691" %)Distance: (%%)0x0292= 658 mm
57.2	365
108.2	366	* (% style="color:#037691" %)Interrupt:(%%) 0x00 = 0
	367
108.7	368	=== 2.3.2 Since firmware v1.3.2 ===
104.2	369
108.7	370
103.1	371	In this mode, uplink payload includes 69 bytes in total by default.
	372
	373	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.
	374
108.23	375	(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:490px" %)
108.27	376	\|(% style="background-color:#4f81bd; color:white; width:60px" %)Size(bytes)\|(% style="background-color:#4f81bd; color:white; width:40px" %)8\|(% style="background-color:#4f81bd; color:white; width:25px" %)2\|(% style="background-color:#4f81bd; color:white; width:25px" %)2\|(% style="background-color:#4f81bd; color:white; width:60px" %)1\|(% style="background-color:#4f81bd; color:white; width:25px" %)1\|(% style="background-color:#4f81bd; color:white; width:40px" %)1\|(% style="background-color:#4f81bd; color:white; width:40px" %)2\|(% style="background-color:#4f81bd; color:white; width:70px" %)4\|(% style="background-color:#4f81bd; color:white; width:40px" %)2\|(% style="background-color:#4f81bd; color:white; width:65px" %)4
108.23	377	\|(% 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.......
103.1	378
	379	If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
	380
	381	[[image:image-20220908175246-1.png]]
	382
104.2	383
103.1	384	The payload is ASCII string, representative same HEX:
	385
108.2	386	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 (%%)
103.1	387
108.2	388	where:
103.1	389
108.2	390	* (% style="color:#037691" %)Device ID:(%%) f867787050213317 = f867787050213317
	391
	392	* (% style="color:#037691" %)Version:(%%) 0x0084=132=1.3.2
	393
	394	* (% style="color:#037691" %)BAT:(%%) 0x0cf4 = 3316 mV = 3.316V
	395
	396	* (% style="color:#037691" %)Singal:(%%) 0x1e = 30
	397
108.8	398	* (% style="color:#037691" %)Mod:(%%) 0x01 = 1
108.2	399
	400	* (% style="color:#037691" %)Interrupt:(%%) 0x00= 0
	401
	402	* (% style="color:#037691" %)Distance:(%%) 0x0039= 57 = 57
	403
	404	* (% style="color:#037691" %)Time stamp:(%%) 0x6315537b =1662342011 ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
	405
	406	* (% style="color:#037691" %)Distance,Time stamp:(%%) 00396319baf0
	407
108.3	408	* (% style="color:#037691" %)8 sets of recorded data: Distance,Time stamp :(%%) //00396319ba3c//,.......
108.2	409
57.3	410	== 2.4 Payload Explanation and Sensor Interface ==
4.2	411
57.5	412	=== 2.4.1 Device ID ===
4.2	413
100.2	414
65.13	415	(((
57.3	416	By default, the Device ID equal to the last 6 bytes of IMEI.
65.13	417	)))
4.2	418
65.13	419	(((
57.4	420	User can use (% style="color:blue" %)AT+DEUI(%%) to set Device ID
100.4	421
	422
65.13	423	)))
4.2	424
65.13	425	(((
104.2	426	(% style="color:blue" %)Example :
65.13	427	)))
4.2	428
65.13	429	(((
57.3	430	AT+DEUI=A84041F15612
65.13	431	)))
4.2	432
65.13	433	(((
104.2	434	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.
65.13	435	)))
22.2	436
4.2	437
104.2	438	(% style="color:red" %)NOTE: When the firmware version is v1.3.2 and later firmware:
4.2	439
104.2	440	(% style="color:red" %)By default, the Device ID equal to the last 15 bits of IMEI.
103.1	441
104.2	442	User can use (% style="color:blue" %)AT+DEUI(%%) to set Device ID
103.1	443
	444
104.2	445	(% style="color:blue" %)Example :
	446
103.1	447	AT+DEUI=868411056754138
	448
104.2	449
57.5	450	=== 2.4.2 Version Info ===
	451
100.2	452
65.13	453	(((
57.3	454	Specify the software version: 0x64=100, means firmware version 1.00.
65.13	455	)))
4.2	456
65.13	457	(((
91.1	458	For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0.
65.13	459	)))
4.2	460
	461
57.5	462	=== 2.4.3 Battery Info ===
22.2	463
100.2	464
32.10	465	(((
4.2	466	Ex1: 0x0B45 = 2885mV
32.10	467	)))
4.2	468
32.10	469	(((
4.2	470	Ex2: 0x0B49 = 2889mV
32.10	471	)))
4.2	472
	473
57.6	474	=== 2.4.4 Signal Strength ===
4.2	475
100.2	476
65.13	477	(((
57.6	478	NB-IoT Network signal Strength.
65.13	479	)))
57.6	480
65.13	481	(((
57.6	482	Ex1: 0x1d = 29
65.13	483	)))
57.6	484
65.13	485	(((
57.6	486	(% style="color:blue" %)0(%%) -113dBm or less
65.13	487	)))
57.6	488
65.13	489	(((
57.6	490	(% style="color:blue" %)1(%%) -111dBm
65.13	491	)))
57.6	492
65.13	493	(((
57.6	494	(% style="color:blue" %)2...30(%%) -109dBm... -53dBm
65.13	495	)))
57.6	496
65.13	497	(((
57.6	498	(% style="color:blue" %)31 (%%) -51dBm or greater
65.13	499	)))
57.6	500
65.13	501	(((
57.6	502	(% style="color:blue" %)99 (%%) Not known or not detectable
65.13	503	)))
57.6	504
	505
95.4	506	=== 2.4.5 Distance ===
57.6	507
100.2	508
91.1	509	Get the distance. Flat object range 280mm - 7500mm.
4.2	510
97.17	511	(((
108.21	512	For example, if the data you get from the register is __0x0B 0x05__, the distance between the sensor and the measured object is(% style="color:blue" %) 0B05(H) = 2821(D) = 2821mm.
97.17	513	)))
4.2	514
32.10	515	(((
23.2	516
	517	)))
4.2	518
91.1	519	=== 2.4.6 Digital Interrupt ===
23.2	520
100.2	521
65.15	522	(((
91.1	523	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.
65.15	524	)))
4.2	525
65.15	526	(((
57.6	527	The command is:
65.15	528	)))
4.2	529
65.15	530	(((
104.7	531	(% 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]]).
65.15	532	)))
4.2	533
	534
65.15	535	(((
65.6	536	The lower four bits of this data field shows if this packet is generated by interrupt or not. Click here for the hardware and software set up.
65.15	537	)))
4.2	538
65.15	539	(((
108.21	540	Example:
65.15	541	)))
4.2	542
65.15	543	(((
57.6	544	0x(00): Normal uplink packet.
65.15	545	)))
4.2	546
65.15	547	(((
57.6	548	0x(01): Interrupt Uplink Packet.
65.15	549	)))
23.2	550
4.2	551
91.1	552	=== 2.4.7 +5V Output ===
4.2	553
100.2	554
65.16	555	(((
91.1	556	NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling.
65.16	557	)))
4.2	558
65.16	559	(((
57.6	560	The 5V output time can be controlled by AT Command.
65.16	561	)))
57.6	562
65.16	563	(((
57.7	564	(% style="color:blue" %)AT+5VT=1000
65.16	565	)))
57.6	566
65.16	567	(((
57.6	568	Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.
65.16	569	)))
57.6	570
	571
58.2	572	== 2.5 Downlink Payload ==
4.2	573
100.2	574
92.2	575	By default, NDDS75 prints the downlink payload to console port.
4.2	576
108.25	577	(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:515px" %)
108.27	578	\|(% style="background-color:#4f81bd; color:white; width:208px" %)Downlink Control Type\|(% style="background-color:#4f81bd; color:white; width:56px" %)FPort\|(% style="background-color:#4f81bd; color:white; width:100px" %)Type Code\|(% style="background-color:#4f81bd; color:white; width:151px" %)Downlink payload size(bytes)
108.17	579	\|(% style="width:208px" %)TDC (Transmit Time Interval)\|(% style="width:56px" %)Any\|(% style="width:100px" %)01\|(% style="width:154px" %)4
	580	\|(% style="width:208px" %)RESET\|(% style="width:56px" %)Any\|(% style="width:100px" %)04\|(% style="width:154px" %)2
	581	\|(% style="width:208px" %)INTMOD\|(% style="width:56px" %)Any\|(% style="width:100px" %)06\|(% style="width:154px" %)4
4.2	582
32.14	583	(((
40.4	584	(% style="color:blue" %)Examples:
32.14	585	)))
4.2	586
32.14	587	(((
	588
	589	)))
4.2	590
32.14	591	* (((
40.4	592	(% style="color:blue" %)Set TDC
32.14	593	)))
4.2	594
32.14	595	(((
60.2	596	If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01.
32.14	597	)))
4.2	598
32.14	599	(((
4.2	600	Payload: 01 00 00 1E TDC=30S
32.14	601	)))
4.2	602
32.14	603	(((
4.2	604	Payload: 01 00 00 3C TDC=60S
32.14	605	)))
4.2	606
32.14	607	(((
	608
	609	)))
4.2	610
32.14	611	* (((
40.4	612	(% style="color:blue" %)Reset
32.14	613	)))
4.2	614
32.14	615	(((
92.2	616	If payload = 0x04FF, it will reset the NDDS75
32.14	617	)))
4.2	618
	619
60.2	620	* (% style="color:blue" %)INTMOD
4.2	621
65.17	622	(((
60.2	623	Downlink Payload: 06000003, Set AT+INTMOD=3
65.17	624	)))
4.2	625
	626
104.2	627	== 2.6 Distance alarm function(Since firmware v1.3.2) ==
26.2	628
4.2	629
104.2	630	(% style="color:blue" %) ➢ AT Command:
	631
	632	(% style="color:#037691" %) AT+ LDDSALARM=min,max
	633
103.1	634	² When min=0, and max≠0, Alarm higher than max
	635
	636	² When min≠0, and max=0, Alarm lower than min
	637
	638	² When min≠0 and max≠0, Alarm higher than max or lower than min
	639
	640
104.2	641	(% style="color:blue" %) Example:
103.1	642
104.2	643	AT+ LDDSALARM=260,2000 ~/~/ Alarm when distance lower than 260.
103.1	644
	645
104.2	646	== 2.7 Set the number of data to be uploaded and the recording time ==
103.1	647
	648
104.2	649	(% style="color:blue" %) ➢ AT Command:
103.1	650
104.7	651	* (% 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)
105.1	652	* (% 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.
103.1	653
106.1	654	The diagram below explains the relationship between TR, NOUD, and TDC more clearly:
103.1	655
108.1	656	[[image:image-20221009001114-1.png\|\|height="687" width="955"]]
106.1	657
	658
104.2	659	== 2.8 Read or Clear cached data ==
	660
	661
	662	(% style="color:blue" %) ➢ AT Command:
	663
104.7	664	* (% style="color:#037691" %) AT+CDP (%%) ~/~/ Read cached data
	665	* (% style="color:#037691" %) AT+CDP=0 (%%) ~/~/ Clear cached data
104.2	666
103.1	667	[[image:image-20220908175333-2.png]]
	668
	669
	670	== 2.9 LED Indicator ==
	671
	672
92.2	673	The NDDS75 has an internal LED which is to show the status of different state.
4.2	674
92.2	675
	676	* 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)
60.2	677	* Then the LED will be on for 1 second means device is boot normally.
92.2	678	* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
60.2	679	* For each uplink probe, LED will be on for 500ms.
92.2	680
	681	(((
	682
32.15	683	)))
4.2	684
	685
103.1	686	== 2.10 Firmware Change Log ==
4.2	687
	688
97.18	689	(((
100.4	690	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]]
97.18	691	)))
4.2	692
60.2	693	(((
100.4	694	Upgrade Instruction: [[Upgrade Firmware>>\|\|anchor="H5.1200BHowtoUpgradeFirmware"]]
97.18	695	)))
28.5	696
4.2	697
108.9	698	== 2.11 Battery & Power Consumption ==
4.2	699
100.4	700
108.11	701	NDDS75 uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace.
4.2	702
108.9	703	[[Battery Info & Power Consumption Analyze>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] .
4.2	704
108.11	705
63.2	706	= 3. Access NB-IoT Module =
4.2	707
100.2	708
63.2	709	(((
	710	Users can directly access the AT command set of the NB-IoT module.
	711	)))
	712
	713	(((
64.2	714	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/]]
100.4	715
	716
63.2	717	)))
	718
95.2	719	[[image:1657333200519-600.png]]
63.2	720
	721
64.2	722	= 4. Using the AT Commands =
63.2	723
64.2	724	== 4.1 Access AT Commands ==
9.2	725
100.2	726
100.4	727	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]]
11.4	728
4.2	729
104.7	730	AT+<CMD>? : Help on <CMD>
4.2	731
104.7	732	AT+<CMD> : Run <CMD>
4.2	733
104.7	734	AT+<CMD>=<value> : Set the value
4.2	735
104.7	736	AT+<CMD>=? : Get the value
4.2	737
	738
11.6	739	(% style="color:#037691" %)General Commands(%%)
4.2	740
104.7	741	AT : Attention
4.2	742
104.7	743	AT? : Short Help
4.2	744
104.7	745	ATZ : MCU Reset
4.2	746
104.7	747	AT+TDC : Application Data Transmission Interval
4.2	748
104.7	749	AT+CFG : Print all configurations
4.2	750
104.7	751	AT+CFGMOD : Working mode selection
4.2	752
104.7	753	AT+INTMOD : Set the trigger interrupt mode
4.2	754
104.7	755	AT+5VT : Set extend the time of 5V power
4.2	756
104.7	757	AT+PRO : Choose agreement
4.2	758
104.7	759	AT+WEIGRE : Get weight or set weight to 0
4.2	760
104.7	761	AT+WEIGAP : Get or Set the GapValue of weight
4.2	762
104.7	763	AT+RXDL : Extend the sending and receiving time
4.2	764
104.7	765	AT+CNTFAC : Get or set counting parameters
4.2	766
104.7	767	AT+SERVADDR : Server Address
4.2	768
104.7	769	AT+TR : Get or Set record time"
4.2	770
104.7	771	AT+APN : Get or set the APN
103.1	772
104.7	773	AT+FBAND : Get or Set whether to automatically modify the frequency band
103.1	774
104.7	775	AT+DNSCFG : Get or Set DNS Server
103.1	776
104.7	777	AT+GETSENSORVALUE : Returns the current sensor measurement
103.1	778
104.7	779	AT+NOUD : Get or Set the number of data to be uploaded
103.1	780
104.7	781	AT+CDP : Read or Clear cached data
103.1	782
104.7	783	AT+LDDSALARM : Get or Set alarm of distance
103.1	784
	785
64.2	786	(% style="color:#037691" %)COAP Management
4.2	787
104.7	788	AT+URI : Resource parameters
4.2	789
	790
64.2	791	(% style="color:#037691" %)UDP Management
4.2	792
104.7	793	AT+CFM : Upload confirmation mode (only valid for UDP)
4.2	794
	795
64.2	796	(% style="color:#037691" %)MQTT Management
4.2	797
104.7	798	AT+CLIENT : Get or Set MQTT client
4.2	799
104.7	800	AT+UNAME : Get or Set MQTT Username
4.2	801
104.7	802	AT+PWD : Get or Set MQTT password
4.2	803
104.7	804	AT+PUBTOPIC : Get or Set MQTT publish topic
4.2	805
104.7	806	AT+SUBTOPIC : Get or Set MQTT subscription topic
4.2	807
	808
64.2	809	(% style="color:#037691" %)Information
4.2	810
104.7	811	AT+FDR : Factory Data Reset
4.2	812
104.7	813	AT+PWORD : Serial Access Password
4.2	814
	815
64.4	816	= 5. FAQ =
4.2	817
64.4	818	== 5.1 How to Upgrade Firmware ==
6.3	819
4.2	820
31.35	821	(((
64.4	822	User can upgrade the firmware for 1) bug fix, 2) new feature release.
31.35	823	)))
4.2	824
31.35	825	(((
64.4	826	Please see this link for how to upgrade: [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H2.HardwareUpgradeMethodSupportList>>http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H2.HardwareUpgradeMethodSupportList]]
31.35	827	)))
4.2	828
31.35	829	(((
100.2	830	(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.
31.35	831	)))
4.2	832
	833
64.5	834	= 6. Trouble Shooting =
4.2	835
64.5	836	== 6.1 Connection problem when uploading firmware ==
4.9	837
4.2	838
65.20	839	(((
	840	Please see: [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H3.3Troubleshooting>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H3.3Troubleshooting]]
	841	)))
	842
64.5	843	(% class="wikigeneratedid" %)
31.29	844	(((
65.20	845
31.29	846	)))
4.2	847
64.5	848	== 6.2 AT Command input doesn't work ==
4.2	849
100.2	850
31.30	851	(((
64.5	852	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.
31.30	853	)))
4.2	854
	855
108.13	856	== 6.3 Not able to connect to NB-IoT network and keep showing "Signal Strength:99". ==
	857
	858
	859	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]]//.
	860
	861
64.5	862	= 7. Order Info =
4.2	863
	864
95.3	865	Part Number: (% style="color:#4f81bd" %)NSDDS75
4.7	866
4.2	867
65.2	868	= 8. Packing Info =
4.2	869
4.3	870	(((
31.39	871
	872
31.40	873	(% style="color:#037691" %)Package Includes:
64.5	874
97.20	875	* NDDS75 NB-IoT Distance Detect Sensor Node x 1
64.5	876	* External antenna x 1
4.3	877	)))
4.2	878
4.3	879	(((
31.40	880
	881
	882	(% style="color:#037691" %)Dimension and weight:
4.2	883
95.3	884	* Device Size: 13.0 x 5 x 4.5 cm
	885	* Device Weight: 150g
	886	* Package Size / pcs : 15 x 12x 5.5 cm
	887	* Weight / pcs : 220g
4.3	888	)))
31.11	889
64.5	890	(((
31.11	891
64.5	892
	893
4.3	894	)))
4.2	895
64.5	896	= 9. Support =
4.2	897
100.2	898
4.2	899	* 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.
108.13	900
4.2	901	* 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]]

Wiki source code of NDDS75 -- NB-IoT Distance Detect Sensor User Manual

Applications