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

Version 108.17 by Xiaoling on 2023/05/17 18:20

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