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

Version 108.23 by Xiaoling on 2024/01/19 17:49

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
81.2	178	[[image:1657328884227-504.png]]
4.2	179
	180
81.2	181	=== 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
4.2	182
100.2	183
48.2	184	(((
	185	(((
81.2	186	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	187	)))
	188	)))
19.2	189
81.2	190	[[image:image-20220709092052-2.png]]
4.2	191
100.4	192
104.7	193	(% style="color:blue" %)Connection:
4.2	194
104.7	195	(% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
4.2	196
104.7	197	~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)
4.2	198
104.7	199	~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)
4.2	200
	201
45.4	202	In the PC, use below serial tool settings:
	203
57.4	204	* Baud: (% style="color:green" %)9600
48.2	205	* Data bits: (% style="color:green" %)8(%%)
	206	* Stop bits: (% style="color:green" %)1
57.4	207	* Parity: (% style="color:green" %)None
48.2	208	* Flow Control: (% style="color:green" %)None
45.4	209
48.2	210	(((
81.2	211	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	212	)))
45.4	213
81.2	214	[[image:1657329814315-101.png]]
45.4	215
100.4	216
65.12	217	(((
100.4	218	(% 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	219	)))
45.4	220
	221
48.2	222	=== 2.2.4 Use CoAP protocol to uplink data ===
45.4	223
	224
100.2	225	(% 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	226
100.2	227
97.9	228	(((
50.2	229	Use below commands:
97.9	230	)))
45.4	231
97.9	232	* (((
	233	(% style="color:blue" %)AT+PRO=1 (%%) ~/~/ Set to use CoAP protocol to uplink
	234	)))
	235	* (((
104.7	236	(% style="color:blue" %)AT+SERVADDR=120.24.4.116,5683 (%%)~/~/ to set CoAP server address and port
97.9	237	)))
	238	* (((
104.7	239	(% style="color:blue" %)AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" (%%) ~/~/ Set COAP resource path
100.6	240
	241
97.9	242	)))
45.4	243
97.9	244	(((
45.4	245	For parameter description, please refer to AT command set
104.2	246
	247
97.9	248	)))
45.4	249
86.2	250	[[image:1657330452568-615.png]]
45.4	251
	252
97.10	253	(((
86.2	254	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	255	)))
45.4	256
86.2	257	[[image:1657330472797-498.png]]
45.4	258
	259
45.6	260	=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
45.4	261
	262
104.7	263	* (% style="color:blue" %)AT+PRO=2 (%%) ~/~/ Set to use UDP protocol to uplink
	264	* (% style="color:blue" %)AT+SERVADDR=120.24.4.116,5601 (%%) ~/~/ to set UDP server address and port
	265	* (% style="color:blue" %)AT+CFM=1 (%%) ~/~/ If the server does not respond, this command is unnecessary
45.4	266
86.2	267	[[image:1657330501006-241.png]]
45.4	268
	269
86.2	270	[[image:1657330533775-472.png]]
45.4	271
52.3	272
45.7	273	=== 2.2.6 Use MQTT protocol to uplink data ===
45.4	274
	275
104.7	276	* (% style="color:blue" %)AT+PRO=3 (%%) ~/~/ Set to use MQTT protocol to uplink
	277	* (% style="color:blue" %)AT+SERVADDR=120.24.4.116,1883 (%%) ~/~/ Set MQTT server address and port
	278	* (% style="color:blue" %)AT+CLIENT=CLIENT (%%)~/~/ Set up the CLIENT of MQTT
	279	* (% style="color:blue" %)AT+UNAME=UNAME (%%)~/~/ Set the username of MQTT
	280	* (% style="color:blue" %)AT+PWD=PWD (%%)~/~/ Set the password of MQTT
	281	* (% style="color:blue" %)AT+PUBTOPIC=NDDS75_PUB (%%)~/~/ Set the sending topic of MQTT
	282	* (% style="color:blue" %)AT+SUBTOPIC=NDDS75_SUB (%%) ~/~/ Set the subscription topic of MQTT
45.4	283
54.2	284	[[image:1657249978444-674.png]]
45.4	285
54.2	286
89.2	287	[[image:1657330723006-866.png]]
54.2	288
45.4	289
54.3	290	(((
45.4	291	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	292	)))
45.4	293
	294
45.7	295	=== 2.2.7 Use TCP protocol to uplink data ===
45.4	296
	297
104.7	298	* (% style="color:blue" %)AT+PRO=4 (%%) ~/~/ Set to use TCP protocol to uplink
	299	* (% style="color:blue" %)AT+SERVADDR=120.24.4.116,5600 (%%) ~/~/ to set TCP server address and port
45.4	300
89.2	301	[[image:image-20220709093918-1.png]]
45.4	302
	303
89.2	304	[[image:image-20220709093918-2.png]]
45.4	305
57.6	306
45.7	307	=== 2.2.8 Change Update Interval ===
45.4	308
100.2	309
48.2	310	User can use below command to change the (% style="color:green" %)uplink interval.
45.4	311
104.7	312	* (% style="color:blue" %)AT+TDC=600 (%%)~/~/ Set Update Interval to 600s
45.4	313
56.3	314	(((
104.4	315
103.1	316
104.4	317	(% style="color:red" %)NOTE:
	318
104.5	319	(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
104.4	320
104.5	321	(% style="color:red" %)2. When the firmware version is v1.3.2 and later firmware:
56.3	322	)))
45.4	323
104.2	324	(% 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	325
103.1	326
57.2	327	== 2.3 Uplink Payload ==
4.2	328
104.7	329	=== 2.3.1 Before Firmware v1.3.2 ===
104.1	330
104.2	331
90.2	332	In this mode, uplink payload includes in total 14 bytes
32.9	333
108.23	334	(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:440px" %)
	335	\|=(% style="width: 61px;background-color:#4F81BD;color:white" %)(((
57.2	336	Size(bytes)
108.23	337	)))\|=(% 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
	338	\|(% 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	339
65.13	340	(((
108.8	341	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	342	)))
57.2	343
	344
90.2	345	[[image:1657331036973-987.png]]
57.2	346
100.4	347
104.2	348	The payload is ASCII string, representative same HEX:
57.2	349
108.3	350	(% style="background-color:yellow" %)0x 724031556159 0064 0c6c 19 0292 00
57.2	351
108.2	352	where :
57.2	353
108.2	354	* (% style="color:#037691" %)Device ID:(%%) 0x724031556159 = 724031556159
95.5	355
108.2	356	* (% style="color:#037691" %)Version:(%%) 0x0064=100=1.0.0
104.2	357
108.2	358	* (% style="color:#037691" %)BAT: (%%) 0x0c6c = 3180 mV = 3.180V
104.2	359
108.2	360	* (% style="color:#037691" %)Signal:(%%) 0x19 = 25
104.2	361
108.2	362	* (% style="color:#037691" %)Distance: (%%)0x0292= 658 mm
57.2	363
108.2	364	* (% style="color:#037691" %)Interrupt:(%%) 0x00 = 0
	365
108.7	366	=== 2.3.2 Since firmware v1.3.2 ===
104.2	367
108.7	368
103.1	369	In this mode, uplink payload includes 69 bytes in total by default.
	370
	371	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.
	372
108.23	373	(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:490px" %)
	374	\|(% 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:60px" %)4
	375	\|(% 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	376
	377	If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
	378
	379	[[image:image-20220908175246-1.png]]
	380
104.2	381
103.1	382	The payload is ASCII string, representative same HEX:
	383
108.2	384	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	385
108.2	386	where:
103.1	387
108.2	388	* (% style="color:#037691" %)Device ID:(%%) f867787050213317 = f867787050213317
	389
	390	* (% style="color:#037691" %)Version:(%%) 0x0084=132=1.3.2
	391
	392	* (% style="color:#037691" %)BAT:(%%) 0x0cf4 = 3316 mV = 3.316V
	393
	394	* (% style="color:#037691" %)Singal:(%%) 0x1e = 30
	395
108.8	396	* (% style="color:#037691" %)Mod:(%%) 0x01 = 1
108.2	397
	398	* (% style="color:#037691" %)Interrupt:(%%) 0x00= 0
	399
	400	* (% style="color:#037691" %)Distance:(%%) 0x0039= 57 = 57
	401
	402	* (% style="color:#037691" %)Time stamp:(%%) 0x6315537b =1662342011 ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
	403
	404	* (% style="color:#037691" %)Distance,Time stamp:(%%) 00396319baf0
	405
108.3	406	* (% style="color:#037691" %)8 sets of recorded data: Distance,Time stamp :(%%) //00396319ba3c//,.......
108.2	407
57.3	408	== 2.4 Payload Explanation and Sensor Interface ==
4.2	409
57.5	410	=== 2.4.1 Device ID ===
4.2	411
100.2	412
65.13	413	(((
57.3	414	By default, the Device ID equal to the last 6 bytes of IMEI.
65.13	415	)))
4.2	416
65.13	417	(((
57.4	418	User can use (% style="color:blue" %)AT+DEUI(%%) to set Device ID
100.4	419
	420
65.13	421	)))
4.2	422
65.13	423	(((
104.2	424	(% style="color:blue" %)Example :
65.13	425	)))
4.2	426
65.13	427	(((
57.3	428	AT+DEUI=A84041F15612
65.13	429	)))
4.2	430
65.13	431	(((
104.2	432	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	433	)))
22.2	434
4.2	435
104.2	436	(% style="color:red" %)NOTE: When the firmware version is v1.3.2 and later firmware:
4.2	437
104.2	438	(% style="color:red" %)By default, the Device ID equal to the last 15 bits of IMEI.
103.1	439
104.2	440	User can use (% style="color:blue" %)AT+DEUI(%%) to set Device ID
103.1	441
	442
104.2	443	(% style="color:blue" %)Example :
	444
103.1	445	AT+DEUI=868411056754138
	446
104.2	447
57.5	448	=== 2.4.2 Version Info ===
	449
100.2	450
65.13	451	(((
57.3	452	Specify the software version: 0x64=100, means firmware version 1.00.
65.13	453	)))
4.2	454
65.13	455	(((
91.1	456	For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0.
65.13	457	)))
4.2	458
	459
57.5	460	=== 2.4.3 Battery Info ===
22.2	461
100.2	462
32.10	463	(((
4.2	464	Ex1: 0x0B45 = 2885mV
32.10	465	)))
4.2	466
32.10	467	(((
4.2	468	Ex2: 0x0B49 = 2889mV
32.10	469	)))
4.2	470
	471
57.6	472	=== 2.4.4 Signal Strength ===
4.2	473
100.2	474
65.13	475	(((
57.6	476	NB-IoT Network signal Strength.
65.13	477	)))
57.6	478
65.13	479	(((
57.6	480	Ex1: 0x1d = 29
65.13	481	)))
57.6	482
65.13	483	(((
57.6	484	(% style="color:blue" %)0(%%) -113dBm or less
65.13	485	)))
57.6	486
65.13	487	(((
57.6	488	(% style="color:blue" %)1(%%) -111dBm
65.13	489	)))
57.6	490
65.13	491	(((
57.6	492	(% style="color:blue" %)2...30(%%) -109dBm... -53dBm
65.13	493	)))
57.6	494
65.13	495	(((
57.6	496	(% style="color:blue" %)31 (%%) -51dBm or greater
65.13	497	)))
57.6	498
65.13	499	(((
57.6	500	(% style="color:blue" %)99 (%%) Not known or not detectable
65.13	501	)))
57.6	502
	503
95.4	504	=== 2.4.5 Distance ===
57.6	505
100.2	506
91.1	507	Get the distance. Flat object range 280mm - 7500mm.
4.2	508
97.17	509	(((
108.21	510	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	511	)))
4.2	512
32.10	513	(((
23.2	514
	515	)))
4.2	516
91.1	517	=== 2.4.6 Digital Interrupt ===
23.2	518
100.2	519
65.15	520	(((
91.1	521	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	522	)))
4.2	523
65.15	524	(((
57.6	525	The command is:
65.15	526	)))
4.2	527
65.15	528	(((
104.7	529	(% 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	530	)))
4.2	531
	532
65.15	533	(((
65.6	534	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	535	)))
4.2	536
65.15	537	(((
108.21	538	Example:
65.15	539	)))
4.2	540
65.15	541	(((
57.6	542	0x(00): Normal uplink packet.
65.15	543	)))
4.2	544
65.15	545	(((
57.6	546	0x(01): Interrupt Uplink Packet.
65.15	547	)))
23.2	548
4.2	549
91.1	550	=== 2.4.7 +5V Output ===
4.2	551
100.2	552
65.16	553	(((
91.1	554	NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling.
65.16	555	)))
4.2	556
65.16	557	(((
57.6	558	The 5V output time can be controlled by AT Command.
65.16	559	)))
57.6	560
65.16	561	(((
57.7	562	(% style="color:blue" %)AT+5VT=1000
65.16	563	)))
57.6	564
65.16	565	(((
57.6	566	Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.
65.16	567	)))
57.6	568
	569
58.2	570	== 2.5 Downlink Payload ==
4.2	571
100.2	572
92.2	573	By default, NDDS75 prints the downlink payload to console port.
4.2	574
108.23	575	(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:520px" %)
	576	\|(% 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:154px" %)Downlink payload size(bytes)
108.17	577	\|(% style="width:208px" %)TDC (Transmit Time Interval)\|(% style="width:56px" %)Any\|(% style="width:100px" %)01\|(% style="width:154px" %)4
	578	\|(% style="width:208px" %)RESET\|(% style="width:56px" %)Any\|(% style="width:100px" %)04\|(% style="width:154px" %)2
	579	\|(% style="width:208px" %)INTMOD\|(% style="width:56px" %)Any\|(% style="width:100px" %)06\|(% style="width:154px" %)4
4.2	580
32.14	581	(((
40.4	582	(% style="color:blue" %)Examples:
32.14	583	)))
4.2	584
32.14	585	(((
	586
	587	)))
4.2	588
32.14	589	* (((
40.4	590	(% style="color:blue" %)Set TDC
32.14	591	)))
4.2	592
32.14	593	(((
60.2	594	If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01.
32.14	595	)))
4.2	596
32.14	597	(((
4.2	598	Payload: 01 00 00 1E TDC=30S
32.14	599	)))
4.2	600
32.14	601	(((
4.2	602	Payload: 01 00 00 3C TDC=60S
32.14	603	)))
4.2	604
32.14	605	(((
	606
	607	)))
4.2	608
32.14	609	* (((
40.4	610	(% style="color:blue" %)Reset
32.14	611	)))
4.2	612
32.14	613	(((
92.2	614	If payload = 0x04FF, it will reset the NDDS75
32.14	615	)))
4.2	616
	617
60.2	618	* (% style="color:blue" %)INTMOD
4.2	619
65.17	620	(((
60.2	621	Downlink Payload: 06000003, Set AT+INTMOD=3
65.17	622	)))
4.2	623
	624
104.2	625	== 2.6 Distance alarm function(Since firmware v1.3.2) ==
26.2	626
4.2	627
104.2	628	(% style="color:blue" %) ➢ AT Command:
	629
	630	(% style="color:#037691" %) AT+ LDDSALARM=min,max
	631
103.1	632	² When min=0, and max≠0, Alarm higher than max
	633
	634	² When min≠0, and max=0, Alarm lower than min
	635
	636	² When min≠0 and max≠0, Alarm higher than max or lower than min
	637
	638
104.2	639	(% style="color:blue" %) Example:
103.1	640
104.2	641	AT+ LDDSALARM=260,2000 ~/~/ Alarm when distance lower than 260.
103.1	642
	643
104.2	644	== 2.7 Set the number of data to be uploaded and the recording time ==
103.1	645
	646
104.2	647	(% style="color:blue" %) ➢ AT Command:
103.1	648
104.7	649	* (% 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	650	* (% 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	651
106.1	652	The diagram below explains the relationship between TR, NOUD, and TDC more clearly:
103.1	653
108.1	654	[[image:image-20221009001114-1.png\|\|height="687" width="955"]]
106.1	655
	656
104.2	657	== 2.8 Read or Clear cached data ==
	658
	659
	660	(% style="color:blue" %) ➢ AT Command:
	661
104.7	662	* (% style="color:#037691" %) AT+CDP (%%) ~/~/ Read cached data
	663	* (% style="color:#037691" %) AT+CDP=0 (%%) ~/~/ Clear cached data
104.2	664
103.1	665	[[image:image-20220908175333-2.png]]
	666
	667
	668	== 2.9 LED Indicator ==
	669
	670
92.2	671	The NDDS75 has an internal LED which is to show the status of different state.
4.2	672
92.2	673
	674	* 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	675	* Then the LED will be on for 1 second means device is boot normally.
92.2	676	* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
60.2	677	* For each uplink probe, LED will be on for 500ms.
92.2	678
	679	(((
	680
32.15	681	)))
4.2	682
	683
103.1	684	== 2.10 Firmware Change Log ==
4.2	685
	686
97.18	687	(((
100.4	688	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	689	)))
4.2	690
60.2	691	(((
100.4	692	Upgrade Instruction: [[Upgrade Firmware>>\|\|anchor="H5.1200BHowtoUpgradeFirmware"]]
97.18	693	)))
28.5	694
4.2	695
108.9	696	== 2.11 Battery & Power Consumption ==
4.2	697
100.4	698
108.11	699	NDDS75 uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace.
4.2	700
108.9	701	[[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	702
108.11	703
63.2	704	= 3. Access NB-IoT Module =
4.2	705
100.2	706
63.2	707	(((
	708	Users can directly access the AT command set of the NB-IoT module.
	709	)))
	710
	711	(((
64.2	712	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	713
	714
63.2	715	)))
	716
95.2	717	[[image:1657333200519-600.png]]
63.2	718
	719
64.2	720	= 4. Using the AT Commands =
63.2	721
64.2	722	== 4.1 Access AT Commands ==
9.2	723
100.2	724
100.4	725	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	726
4.2	727
104.7	728	AT+<CMD>? : Help on <CMD>
4.2	729
104.7	730	AT+<CMD> : Run <CMD>
4.2	731
104.7	732	AT+<CMD>=<value> : Set the value
4.2	733
104.7	734	AT+<CMD>=? : Get the value
4.2	735
	736
11.6	737	(% style="color:#037691" %)General Commands(%%)
4.2	738
104.7	739	AT : Attention
4.2	740
104.7	741	AT? : Short Help
4.2	742
104.7	743	ATZ : MCU Reset
4.2	744
104.7	745	AT+TDC : Application Data Transmission Interval
4.2	746
104.7	747	AT+CFG : Print all configurations
4.2	748
104.7	749	AT+CFGMOD : Working mode selection
4.2	750
104.7	751	AT+INTMOD : Set the trigger interrupt mode
4.2	752
104.7	753	AT+5VT : Set extend the time of 5V power
4.2	754
104.7	755	AT+PRO : Choose agreement
4.2	756
104.7	757	AT+WEIGRE : Get weight or set weight to 0
4.2	758
104.7	759	AT+WEIGAP : Get or Set the GapValue of weight
4.2	760
104.7	761	AT+RXDL : Extend the sending and receiving time
4.2	762
104.7	763	AT+CNTFAC : Get or set counting parameters
4.2	764
104.7	765	AT+SERVADDR : Server Address
4.2	766
104.7	767	AT+TR : Get or Set record time"
4.2	768
104.7	769	AT+APN : Get or set the APN
103.1	770
104.7	771	AT+FBAND : Get or Set whether to automatically modify the frequency band
103.1	772
104.7	773	AT+DNSCFG : Get or Set DNS Server
103.1	774
104.7	775	AT+GETSENSORVALUE : Returns the current sensor measurement
103.1	776
104.7	777	AT+NOUD : Get or Set the number of data to be uploaded
103.1	778
104.7	779	AT+CDP : Read or Clear cached data
103.1	780
104.7	781	AT+LDDSALARM : Get or Set alarm of distance
103.1	782
	783
64.2	784	(% style="color:#037691" %)COAP Management
4.2	785
104.7	786	AT+URI : Resource parameters
4.2	787
	788
64.2	789	(% style="color:#037691" %)UDP Management
4.2	790
104.7	791	AT+CFM : Upload confirmation mode (only valid for UDP)
4.2	792
	793
64.2	794	(% style="color:#037691" %)MQTT Management
4.2	795
104.7	796	AT+CLIENT : Get or Set MQTT client
4.2	797
104.7	798	AT+UNAME : Get or Set MQTT Username
4.2	799
104.7	800	AT+PWD : Get or Set MQTT password
4.2	801
104.7	802	AT+PUBTOPIC : Get or Set MQTT publish topic
4.2	803
104.7	804	AT+SUBTOPIC : Get or Set MQTT subscription topic
4.2	805
	806
64.2	807	(% style="color:#037691" %)Information
4.2	808
104.7	809	AT+FDR : Factory Data Reset
4.2	810
104.7	811	AT+PWORD : Serial Access Password
4.2	812
	813
64.4	814	= 5. FAQ =
4.2	815
64.4	816	== 5.1 How to Upgrade Firmware ==
6.3	817
4.2	818
31.35	819	(((
64.4	820	User can upgrade the firmware for 1) bug fix, 2) new feature release.
31.35	821	)))
4.2	822
31.35	823	(((
64.4	824	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	825	)))
4.2	826
31.35	827	(((
100.2	828	(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.
31.35	829	)))
4.2	830
	831
64.5	832	= 6. Trouble Shooting =
4.2	833
64.5	834	== 6.1 Connection problem when uploading firmware ==
4.9	835
4.2	836
65.20	837	(((
	838	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]]
	839	)))
	840
64.5	841	(% class="wikigeneratedid" %)
31.29	842	(((
65.20	843
31.29	844	)))
4.2	845
64.5	846	== 6.2 AT Command input doesn't work ==
4.2	847
100.2	848
31.30	849	(((
64.5	850	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	851	)))
4.2	852
	853
108.13	854	== 6.3 Not able to connect to NB-IoT network and keep showing "Signal Strength:99". ==
	855
	856
	857	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]]//.
	858
	859
64.5	860	= 7. Order Info =
4.2	861
	862
95.3	863	Part Number: (% style="color:#4f81bd" %)NSDDS75
4.7	864
4.2	865
65.2	866	= 8. Packing Info =
4.2	867
4.3	868	(((
31.39	869
	870
31.40	871	(% style="color:#037691" %)Package Includes:
64.5	872
97.20	873	* NDDS75 NB-IoT Distance Detect Sensor Node x 1
64.5	874	* External antenna x 1
4.3	875	)))
4.2	876
4.3	877	(((
31.40	878
	879
	880	(% style="color:#037691" %)Dimension and weight:
4.2	881
95.3	882	* Device Size: 13.0 x 5 x 4.5 cm
	883	* Device Weight: 150g
	884	* Package Size / pcs : 15 x 12x 5.5 cm
	885	* Weight / pcs : 220g
4.3	886	)))
31.11	887
64.5	888	(((
31.11	889
64.5	890
	891
4.3	892	)))
4.2	893
64.5	894	= 9. Support =
4.2	895
100.2	896
4.2	897	* 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	898
4.2	899	* 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