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

Last modified by Bei Jinggeng on 2024/05/31 09:53

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

Navigation