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

Version 106.1 by Edwin Chen on 2022/10/09 00:06

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
100.5	19
67.2	20	== 1.1 What is NDDS75 Distance Detection Sensor ==
1.1	21
12.2	22	(((
35.4	23
	24
65.9	25	(((
97.14	26	(((
68.2	27	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	28	)))
97.13	29
97.14	30	(((
97.13	31	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	32	)))
97.13	33
97.14	34	(((
97.13	35	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	36	)))
97.13	37
97.14	38	(((
97.13	39	NDDS75 supports different uplink methods include (% style="color:blue" %)TCP, MQTT, UDP and CoAP (%%)for different application requirement.
97.14	40	)))
97.13	41
97.14	42	(((
97.13	43	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	44	)))
97.13	45
97.14	46	(((
97.13	47	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	48	)))
97.14	49	)))
4.2	50
42.2	51
12.2	52	)))
4.2	53
75.2	54	[[image:1657327959271-447.png]]
4.2	55
	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
	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
	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
99.1	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
100.4	118
	119
44.2	120	== 1.5 Pin Definitions ==
15.6	121
	122
76.2	123	[[image:1657328609906-564.png]]
4.2	124
14.3	125
	126
81.2	127	= 2. Use NDDS75 to communicate with IoT Server =
14.3	128
100.4	129
45.2	130	== 2.1 How it works ==
14.3	131
100.2	132
15.3	133	(((
77.2	134	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	135	)))
4.2	136
45.2	137
15.3	138	(((
77.2	139	The diagram below shows the working flow in default firmware of NDDS75:
15.3	140	)))
4.2	141
77.2	142	(((
	143
	144	)))
4.2	145
77.2	146	[[image:1657328659945-416.png]]
	147
45.2	148	(((
	149
	150	)))
4.2	151
45.2	152
81.2	153	== 2.2 Configure the NDDS75 ==
4.2	154
48.2	155
45.4	156	=== 2.2.1 Test Requirement ===
4.2	157
100.2	158
65.10	159	(((
81.2	160	To use NDDS75 in your city, make sure meet below requirements:
65.10	161	)))
4.2	162
45.4	163	* Your local operator has already distributed a NB-IoT Network there.
97.22	164	* The local NB-IoT network used the band that NDDS75 supports.
45.4	165	* Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
4.2	166
48.2	167	(((
100.2	168	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	169	)))
4.2	170
	171
81.2	172	[[image:1657328756309-230.png]]
4.2	173
	174
	175
45.5	176	=== 2.2.2 Insert SIM card ===
4.2	177
100.2	178
65.11	179	(((
45.4	180	Insert the NB-IoT Card get from your provider.
65.11	181	)))
4.2	182
65.11	183	(((
45.4	184	User need to take out the NB-IoT module and insert the SIM card like below:
65.11	185	)))
4.2	186
	187
81.2	188	[[image:1657328884227-504.png]]
4.2	189
	190
48.2	191
81.2	192	=== 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
4.2	193
100.2	194
48.2	195	(((
	196	(((
81.2	197	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	198	)))
	199	)))
19.2	200
81.2	201	[[image:image-20220709092052-2.png]]
4.2	202
100.4	203
104.7	204	(% style="color:blue" %)Connection:
4.2	205
104.7	206	(% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
4.2	207
104.7	208	~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)
4.2	209
104.7	210	~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)
4.2	211
	212
45.4	213	In the PC, use below serial tool settings:
	214
57.4	215	* Baud: (% style="color:green" %)9600
48.2	216	* Data bits: (% style="color:green" %)8(%%)
	217	* Stop bits: (% style="color:green" %)1
57.4	218	* Parity: (% style="color:green" %)None
48.2	219	* Flow Control: (% style="color:green" %)None
45.4	220
48.2	221	(((
81.2	222	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	223	)))
45.4	224
81.2	225	[[image:1657329814315-101.png]]
45.4	226
100.4	227
65.12	228	(((
100.4	229	(% 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	230	)))
45.4	231
	232
	233
48.2	234	=== 2.2.4 Use CoAP protocol to uplink data ===
45.4	235
	236
100.2	237	(% 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	238
100.2	239
97.9	240	(((
50.2	241	Use below commands:
97.9	242	)))
45.4	243
97.9	244	* (((
	245	(% style="color:blue" %)AT+PRO=1 (%%) ~/~/ Set to use CoAP protocol to uplink
	246	)))
	247	* (((
104.7	248	(% style="color:blue" %)AT+SERVADDR=120.24.4.116,5683 (%%)~/~/ to set CoAP server address and port
97.9	249	)))
	250	* (((
104.7	251	(% style="color:blue" %)AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" (%%) ~/~/ Set COAP resource path
100.6	252
	253
	254
97.9	255	)))
45.4	256
97.9	257	(((
45.4	258	For parameter description, please refer to AT command set
104.2	259
	260
97.9	261	)))
45.4	262
86.2	263	[[image:1657330452568-615.png]]
45.4	264
	265
100.4	266
97.10	267	(((
86.2	268	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	269
	270
97.10	271	)))
45.4	272
86.2	273	[[image:1657330472797-498.png]]
45.4	274
	275
50.2	276
45.6	277	=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
45.4	278
	279
104.7	280	* (% style="color:blue" %)AT+PRO=2 (%%) ~/~/ Set to use UDP protocol to uplink
	281	* (% style="color:blue" %)AT+SERVADDR=120.24.4.116,5601 (%%) ~/~/ to set UDP server address and port
	282	* (% style="color:blue" %)AT+CFM=1 (%%) ~/~/ If the server does not respond, this command is unnecessary
45.4	283
86.2	284	[[image:1657330501006-241.png]]
45.4	285
	286
86.2	287	[[image:1657330533775-472.png]]
45.4	288
52.3	289
86.2	290
45.7	291	=== 2.2.6 Use MQTT protocol to uplink data ===
45.4	292
	293
104.7	294	* (% style="color:blue" %)AT+PRO=3 (%%) ~/~/ Set to use MQTT protocol to uplink
	295	* (% style="color:blue" %)AT+SERVADDR=120.24.4.116,1883 (%%) ~/~/ Set MQTT server address and port
	296	* (% style="color:blue" %)AT+CLIENT=CLIENT (%%)~/~/ Set up the CLIENT of MQTT
	297	* (% style="color:blue" %)AT+UNAME=UNAME (%%)~/~/ Set the username of MQTT
	298	* (% style="color:blue" %)AT+PWD=PWD (%%)~/~/ Set the password of MQTT
	299	* (% style="color:blue" %)AT+PUBTOPIC=NDDS75_PUB (%%)~/~/ Set the sending topic of MQTT
	300	* (% style="color:blue" %)AT+SUBTOPIC=NDDS75_SUB (%%) ~/~/ Set the subscription topic of MQTT
45.4	301
54.2	302	[[image:1657249978444-674.png]]
45.4	303
54.2	304
89.2	305	[[image:1657330723006-866.png]]
54.2	306
45.4	307
54.3	308	(((
45.4	309	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	310	)))
45.4	311
	312
54.3	313
45.7	314	=== 2.2.7 Use TCP protocol to uplink data ===
45.4	315
	316
104.7	317	* (% style="color:blue" %)AT+PRO=4 (%%) ~/~/ Set to use TCP protocol to uplink
	318	* (% style="color:blue" %)AT+SERVADDR=120.24.4.116,5600 (%%) ~/~/ to set TCP server address and port
45.4	319
89.2	320	[[image:image-20220709093918-1.png]]
45.4	321
	322
89.2	323	[[image:image-20220709093918-2.png]]
45.4	324
57.6	325
89.2	326
45.7	327	=== 2.2.8 Change Update Interval ===
45.4	328
100.2	329
48.2	330	User can use below command to change the (% style="color:green" %)uplink interval.
45.4	331
104.7	332	* (% style="color:blue" %)AT+TDC=600 (%%)~/~/ Set Update Interval to 600s
45.4	333
56.3	334	(((
104.4	335
103.1	336
104.4	337
	338	(% style="color:red" %)NOTE:
	339
104.5	340	(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
104.4	341
104.5	342	(% style="color:red" %)2. When the firmware version is v1.3.2 and later firmware:
56.3	343	)))
45.4	344
104.2	345	(% 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	346
103.1	347
104.2	348
57.2	349	== 2.3 Uplink Payload ==
4.2	350
100.2	351
104.7	352	=== 2.3.1 Before Firmware v1.3.2 ===
104.1	353
104.2	354
90.2	355	In this mode, uplink payload includes in total 14 bytes
32.9	356
97.16	357	(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
97.12	358	\|=(% style="width: 60px;" %)(((
57.2	359	Size(bytes)
97.15	360	)))\|=(% style="width: 60px;" %)6\|=(% style="width: 35px;" %)2\|=(% style="width: 35px;" %)2\|=(% style="width: 80px;" %)1\|=(% style="width: 100px;" %)2\|=(% style="width: 60px;" %)1
97.2	361	\|(% 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	362
65.13	363	(((
90.2	364	If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
65.13	365	)))
57.2	366
	367
90.2	368	[[image:1657331036973-987.png]]
57.2	369
100.4	370
90.2	371	(((
104.2	372	The payload is ASCII string, representative same HEX:
90.2	373	)))
57.2	374
90.2	375	(((
	376	0x72403155615900640c6c19029200 where:
	377	)))
57.2	378
90.2	379	* (((
	380	Device ID: 0x724031556159 = 724031556159
	381	)))
	382	* (((
104.2	383	Version: 0x0064=100=1.0.0
90.2	384	)))
57.2	385
90.2	386	* (((
104.2	387	BAT: 0x0c6c = 3180 mV = 3.180V
90.2	388	)))
	389	* (((
	390	Signal: 0x19 = 25
	391	)))
	392	* (((
	393	Distance: 0x0292= 658 mm
	394	)))
	395	* (((
	396	Interrupt: 0x00 = 0
95.5	397
104.2	398
	399
	400
95.5	401
90.2	402	)))
57.2	403
104.2	404	=== 2.3.2 Since firmware v1.3.2 ===
103.1	405
104.2	406
103.1	407	In this mode, uplink payload includes 69 bytes in total by default.
	408
	409	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.
	410
104.2	411	(% border="2" style="background-color:#ffffcc; color:green; width:896px" %)
	412	\|(% style="width:95px" %)Size(bytes)\|(% style="width:84px" %)8\|(% style="width:44px" %)2\|(% style="width:48px" %)2\|(% style="width:123px" %)1\|(% style="width:55px" %)1\|(% style="width:80px" %)1\|(% style="width:77px" %)2\|(% style="width:94px" %)4\|(% style="width:77px" %)2\|(% style="width:116px" %)4
	413	\|(% 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	414
	415	If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
	416
	417	[[image:image-20220908175246-1.png]]
	418
104.2	419
103.1	420	The payload is ASCII string, representative same HEX:
	421
	422	0x(% style="color:red" %)f867787050213317(% style="color:blue" %)0084(% style="color:green" %)0cf4(% style="color:red" %)1e(% style="color:blue" %)01(% style="color:green" %)00(% style="color:red" %)//00396319bb32//00396319baf0//00396319ba3c//00396319b988//00396319b8d4//00396319b820//00396319b76c//00396319b6b8//00396319b604//(%%) where:
	423
	424	* (% style="color:green" %)Device ID: f867787050213317 = f867787050213317
	425	* (% style="color:red" %)Version: 0x0084=132=1.3.2
	426	* (% style="color:green" %)BAT: 0x0cf4 = 3316 mV = 3.316V
	427	* (% style="color:blue" %)Singal: 0x1e = 30
	428	* (% style="color:red" %)Mod: 0x01 = 1
	429	* Interrupt: 0x00= 0
	430	* Distance: 0x0039= 57 = 57
	431	* Time stamp : 0x6315537b =1662342011 ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
	432	* Distance,Time stamp : 00396319baf0
	433	* (% style="color:red" %) 8 sets of recorded data: Distance,Time stamp : //00396319ba3c//,.......
	434
57.3	435	== 2.4 Payload Explanation and Sensor Interface ==
4.2	436
57.7	437
57.5	438	=== 2.4.1 Device ID ===
4.2	439
100.2	440
65.13	441	(((
57.3	442	By default, the Device ID equal to the last 6 bytes of IMEI.
65.13	443	)))
4.2	444
65.13	445	(((
57.4	446	User can use (% style="color:blue" %)AT+DEUI(%%) to set Device ID
100.4	447
	448
65.13	449	)))
4.2	450
65.13	451	(((
104.2	452	(% style="color:blue" %)Example :
65.13	453	)))
4.2	454
65.13	455	(((
57.3	456	AT+DEUI=A84041F15612
65.13	457	)))
4.2	458
65.13	459	(((
104.2	460	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	461	)))
22.2	462
4.2	463
104.2	464	(% style="color:red" %)NOTE: When the firmware version is v1.3.2 and later firmware:
4.2	465
104.2	466	(% style="color:red" %)By default, the Device ID equal to the last 15 bits of IMEI.
103.1	467
104.2	468	User can use (% style="color:blue" %)AT+DEUI(%%) to set Device ID
103.1	469
	470
104.2	471	(% style="color:blue" %)Example :
	472
103.1	473	AT+DEUI=868411056754138
	474
104.2	475
	476
57.5	477	=== 2.4.2 Version Info ===
	478
100.2	479
65.13	480	(((
57.3	481	Specify the software version: 0x64=100, means firmware version 1.00.
65.13	482	)))
4.2	483
65.13	484	(((
91.1	485	For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0.
65.13	486	)))
4.2	487
	488
57.3	489
57.5	490	=== 2.4.3 Battery Info ===
22.2	491
100.2	492
32.10	493	(((
4.2	494	Ex1: 0x0B45 = 2885mV
32.10	495	)))
4.2	496
32.10	497	(((
4.2	498	Ex2: 0x0B49 = 2889mV
32.10	499	)))
4.2	500
	501
	502
57.6	503	=== 2.4.4 Signal Strength ===
4.2	504
100.2	505
65.13	506	(((
57.6	507	NB-IoT Network signal Strength.
65.13	508	)))
57.6	509
65.13	510	(((
57.6	511	Ex1: 0x1d = 29
65.13	512	)))
57.6	513
65.13	514	(((
57.6	515	(% style="color:blue" %)0(%%) -113dBm or less
65.13	516	)))
57.6	517
65.13	518	(((
57.6	519	(% style="color:blue" %)1(%%) -111dBm
65.13	520	)))
57.6	521
65.13	522	(((
57.6	523	(% style="color:blue" %)2...30(%%) -109dBm... -53dBm
65.13	524	)))
57.6	525
65.13	526	(((
57.6	527	(% style="color:blue" %)31 (%%) -51dBm or greater
65.13	528	)))
57.6	529
65.13	530	(((
57.6	531	(% style="color:blue" %)99 (%%) Not known or not detectable
65.13	532	)))
57.6	533
	534
	535
95.4	536	=== 2.4.5 Distance ===
57.6	537
100.2	538
91.1	539	Get the distance. Flat object range 280mm - 7500mm.
4.2	540
97.17	541	(((
91.1	542	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	543	)))
4.2	544
32.10	545	(((
	546	(((
91.4	547	(% style="color:blue" %) 0B05(H) = 2821(D) = 2821mm.
32.10	548	)))
32.11	549	)))
4.2	550
32.11	551	(((
23.2	552
	553	)))
4.2	554
23.2	555	(((
	556
	557	)))
	558
91.1	559	=== 2.4.6 Digital Interrupt ===
23.2	560
100.2	561
65.15	562	(((
91.1	563	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	564	)))
4.2	565
65.15	566	(((
57.6	567	The command is:
65.15	568	)))
4.2	569
65.15	570	(((
104.7	571	(% 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	572	)))
4.2	573
	574
65.15	575	(((
65.6	576	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	577	)))
4.2	578
	579
65.15	580	(((
57.6	581	Example:
65.15	582	)))
4.2	583
65.15	584	(((
57.6	585	0x(00): Normal uplink packet.
65.15	586	)))
4.2	587
65.15	588	(((
57.6	589	0x(01): Interrupt Uplink Packet.
65.15	590	)))
23.2	591
4.2	592
	593
91.1	594	=== 2.4.7 +5V Output ===
4.2	595
100.2	596
65.16	597	(((
91.1	598	NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling.
65.16	599	)))
4.2	600
57.6	601
65.16	602	(((
57.6	603	The 5V output time can be controlled by AT Command.
100.4	604
	605
65.16	606	)))
57.6	607
65.16	608	(((
57.7	609	(% style="color:blue" %)AT+5VT=1000
100.4	610
	611
65.16	612	)))
57.6	613
65.16	614	(((
57.6	615	Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.
65.16	616	)))
57.6	617
	618
	619
58.2	620	== 2.5 Downlink Payload ==
4.2	621
100.2	622
92.2	623	By default, NDDS75 prints the downlink payload to console port.
4.2	624
92.2	625	[[image:image-20220709100028-1.png]]
4.2	626
	627
32.14	628	(((
40.4	629	(% style="color:blue" %)Examples:
32.14	630	)))
4.2	631
32.14	632	(((
	633
	634	)))
4.2	635
32.14	636	* (((
40.4	637	(% style="color:blue" %)Set TDC
32.14	638	)))
4.2	639
32.14	640	(((
60.2	641	If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01.
32.14	642	)))
4.2	643
32.14	644	(((
4.2	645	Payload: 01 00 00 1E TDC=30S
32.14	646	)))
4.2	647
32.14	648	(((
4.2	649	Payload: 01 00 00 3C TDC=60S
32.14	650	)))
4.2	651
32.14	652	(((
	653
	654	)))
4.2	655
32.14	656	* (((
40.4	657	(% style="color:blue" %)Reset
32.14	658	)))
4.2	659
32.14	660	(((
92.2	661	If payload = 0x04FF, it will reset the NDDS75
32.14	662	)))
4.2	663
	664
60.2	665	* (% style="color:blue" %)INTMOD
4.2	666
65.17	667	(((
60.2	668	Downlink Payload: 06000003, Set AT+INTMOD=3
65.17	669	)))
4.2	670
	671
26.2	672
104.2	673	== 2.6 Distance alarm function(Since firmware v1.3.2) ==
26.2	674
4.2	675
104.2	676	(% style="color:blue" %) ➢ AT Command:
	677
	678	(% style="color:#037691" %) AT+ LDDSALARM=min,max
	679
103.1	680	² When min=0, and max≠0, Alarm higher than max
	681
	682	² When min≠0, and max=0, Alarm lower than min
	683
	684	² When min≠0 and max≠0, Alarm higher than max or lower than min
	685
	686
104.2	687	(% style="color:blue" %) Example:
103.1	688
104.2	689	AT+ LDDSALARM=260,2000 ~/~/ Alarm when distance lower than 260.
103.1	690
	691
	692
104.2	693	== 2.7 Set the number of data to be uploaded and the recording time ==
103.1	694
	695
104.2	696	(% style="color:blue" %) ➢ AT Command:
103.1	697
104.7	698	* (% 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	699	* (% 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	700
106.1	701	The diagram below explains the relationship between TR, NOUD, and TDC more clearly:
103.1	702
106.1	703	[[image:image-20221009000513-1.png\|\|height="732" width="1018"]]
	704
	705
	706
104.2	707	== 2.8 Read or Clear cached data ==
	708
	709
	710	(% style="color:blue" %) ➢ AT Command:
	711
104.7	712	* (% style="color:#037691" %) AT+CDP (%%) ~/~/ Read cached data
	713	* (% style="color:#037691" %) AT+CDP=0 (%%) ~/~/ Clear cached data
104.2	714
103.1	715	[[image:image-20220908175333-2.png]]
	716
	717
104.2	718
103.1	719	== 2.9 LED Indicator ==
	720
	721
92.2	722	The NDDS75 has an internal LED which is to show the status of different state.
4.2	723
92.2	724
	725	* 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	726	* Then the LED will be on for 1 second means device is boot normally.
92.2	727	* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
60.2	728	* For each uplink probe, LED will be on for 500ms.
92.2	729
	730	(((
	731
32.15	732	)))
4.2	733
	734
	735
103.1	736	== 2.10 Firmware Change Log ==
4.2	737
	738
97.18	739	(((
100.4	740	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	741	)))
4.2	742
60.2	743	(((
100.4	744
60.2	745	)))
4.2	746
97.18	747	(((
100.4	748	Upgrade Instruction: [[Upgrade Firmware>>\|\|anchor="H5.1200BHowtoUpgradeFirmware"]]
97.18	749	)))
28.5	750
4.2	751
	752
103.1	753	== 2.11 Battery Analysis ==
4.2	754
100.4	755
103.1	756	=== 2.11.1 Battery Type ===
4.2	757
	758
65.18	759	(((
95.2	760	The NDDS75 battery is a combination of an 8500mAh Li/SOCI2 Battery and a Super Capacitor. The battery is none-rechargeable battery type with a low discharge rate (<2% per year). This type of battery is commonly used in IoT devices such as water meter.
65.18	761	)))
4.2	762
65.18	763	(((
62.3	764	The battery is designed to last for several years depends on the actually use environment and update interval.
65.18	765	)))
4.2	766
65.18	767	(((
60.2	768	The battery related documents as below:
65.18	769	)))
4.2	770
60.2	771	* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
65.7	772	* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
60.2	773	* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
4.2	774
29.2	775	(((
95.2	776	[[image:image-20220709101450-2.png]]
29.2	777	)))
4.2	778
	779
35.18	780
103.1	781	=== 2.11.2 Power consumption Analyze ===
4.2	782
100.2	783
62.3	784	(((
60.2	785	Dragino battery powered product are all runs in Low Power mode. We have an update battery calculator which base on the measurement of the real device. User can use this calculator to check the battery life and calculate the battery life if want to use different transmit interval.
62.3	786	)))
4.2	787
	788
62.3	789	(((
60.2	790	Instruction to use as below:
62.3	791	)))
4.2	792
62.3	793	(((
	794	(% style="color:blue" %)Step 1: (%%)Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/]]
	795	)))
4.2	796
	797
62.3	798	(((
	799	(% style="color:blue" %)Step 2: (%%) Open it and choose
	800	)))
4.2	801
62.3	802	* (((
	803	Product Model
	804	)))
	805	* (((
	806	Uplink Interval
	807	)))
	808	* (((
	809	Working Mode
	810	)))
4.2	811
62.3	812	(((
60.2	813	And the Life expectation in difference case will be shown on the right.
62.3	814	)))
4.2	815
96.2	816	[[image:image-20220709110451-3.png]]
4.2	817
	818
62.2	819
103.1	820	=== 2.11.3 Battery Note ===
4.2	821
100.2	822
31.6	823	(((
4.2	824	The Li-SICO battery is designed for small current / long period application. It is not good to use a high current, short period transmit method. The recommended minimum period for use of this battery is 5 minutes. If you use a shorter period time to transmit LoRa, then the battery life may be decreased.
31.3	825	)))
4.2	826
	827
	828
103.1	829	=== 2.11.4 Replace the battery ===
31.2	830
100.2	831
62.2	832	(((
95.2	833	The default battery pack of NDDS75 includes a ER26500 plus super capacitor. If user can't find this pack locally, they can find ER26500 or equivalence without the SPC1520 capacitor, which will also work in most case. The SPC can enlarge the battery life for high frequency use (update period below 5 minutes).
62.2	834	)))
4.2	835
	836
	837
63.2	838	= 3. Access NB-IoT Module =
4.2	839
100.2	840
63.2	841	(((
	842	Users can directly access the AT command set of the NB-IoT module.
	843	)))
	844
	845	(((
64.2	846	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	847
	848
63.2	849	)))
	850
95.2	851	[[image:1657333200519-600.png]]
63.2	852
	853
	854
64.2	855	= 4. Using the AT Commands =
63.2	856
100.4	857
64.2	858	== 4.1 Access AT Commands ==
9.2	859
100.2	860
100.4	861	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	862
4.2	863
104.7	864	AT+<CMD>? : Help on <CMD>
4.2	865
104.7	866	AT+<CMD> : Run <CMD>
4.2	867
104.7	868	AT+<CMD>=<value> : Set the value
4.2	869
104.7	870	AT+<CMD>=? : Get the value
4.2	871
	872
11.6	873	(% style="color:#037691" %)General Commands(%%)
4.2	874
104.7	875	AT : Attention
4.2	876
104.7	877	AT? : Short Help
4.2	878
104.7	879	ATZ : MCU Reset
4.2	880
104.7	881	AT+TDC : Application Data Transmission Interval
4.2	882
104.7	883	AT+CFG : Print all configurations
4.2	884
104.7	885	AT+CFGMOD : Working mode selection
4.2	886
104.7	887	AT+INTMOD : Set the trigger interrupt mode
4.2	888
104.7	889	AT+5VT : Set extend the time of 5V power
4.2	890
104.7	891	AT+PRO : Choose agreement
4.2	892
104.7	893	AT+WEIGRE : Get weight or set weight to 0
4.2	894
104.7	895	AT+WEIGAP : Get or Set the GapValue of weight
4.2	896
104.7	897	AT+RXDL : Extend the sending and receiving time
4.2	898
104.7	899	AT+CNTFAC : Get or set counting parameters
4.2	900
104.7	901	AT+SERVADDR : Server Address
4.2	902
104.7	903	AT+TR : Get or Set record time"
4.2	904
104.7	905	AT+APN : Get or set the APN
103.1	906
104.7	907	AT+FBAND : Get or Set whether to automatically modify the frequency band
103.1	908
104.7	909	AT+DNSCFG : Get or Set DNS Server
103.1	910
104.7	911	AT+GETSENSORVALUE : Returns the current sensor measurement
103.1	912
104.7	913	AT+NOUD : Get or Set the number of data to be uploaded
103.1	914
104.7	915	AT+CDP : Read or Clear cached data
103.1	916
104.7	917	AT+LDDSALARM : Get or Set alarm of distance
103.1	918
	919
64.2	920	(% style="color:#037691" %)COAP Management
4.2	921
104.7	922	AT+URI : Resource parameters
4.2	923
	924
64.2	925	(% style="color:#037691" %)UDP Management
4.2	926
104.7	927	AT+CFM : Upload confirmation mode (only valid for UDP)
4.2	928
	929
64.2	930	(% style="color:#037691" %)MQTT Management
4.2	931
104.7	932	AT+CLIENT : Get or Set MQTT client
4.2	933
104.7	934	AT+UNAME : Get or Set MQTT Username
4.2	935
104.7	936	AT+PWD : Get or Set MQTT password
4.2	937
104.7	938	AT+PUBTOPIC : Get or Set MQTT publish topic
4.2	939
104.7	940	AT+SUBTOPIC : Get or Set MQTT subscription topic
4.2	941
	942
64.2	943	(% style="color:#037691" %)Information
4.2	944
104.7	945	AT+FDR : Factory Data Reset
4.2	946
104.7	947	AT+PWORD : Serial Access Password
4.2	948
	949
	950
64.4	951	= 5. FAQ =
4.2	952
100.4	953
64.4	954	== 5.1 How to Upgrade Firmware ==
6.3	955
4.2	956
31.35	957	(((
64.4	958	User can upgrade the firmware for 1) bug fix, 2) new feature release.
31.35	959	)))
4.2	960
31.35	961	(((
64.4	962	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	963	)))
4.2	964
31.35	965	(((
100.2	966	(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.
31.35	967	)))
4.2	968
	969
	970
64.5	971	= 6. Trouble Shooting =
4.2	972
100.4	973
64.5	974	== 6.1 Connection problem when uploading firmware ==
4.9	975
4.2	976
65.20	977	(((
	978	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]]
	979	)))
	980
64.5	981	(% class="wikigeneratedid" %)
31.29	982	(((
65.20	983
31.29	984	)))
4.2	985
	986
64.5	987	== 6.2 AT Command input doesn't work ==
4.2	988
100.2	989
31.30	990	(((
64.5	991	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.
65.22	992
65.23	993
31.30	994	)))
4.2	995
	996
64.5	997	= 7. Order Info =
4.2	998
	999
95.3	1000	Part Number: (% style="color:#4f81bd" %)NSDDS75
4.7	1001
4.2	1002
31.10	1003	(% class="wikigeneratedid" %)
	1004	(((
	1005
	1006	)))
	1007
65.2	1008	= 8. Packing Info =
4.2	1009
4.3	1010	(((
31.39	1011
	1012
31.40	1013	(% style="color:#037691" %)Package Includes:
64.5	1014
97.20	1015	* NDDS75 NB-IoT Distance Detect Sensor Node x 1
64.5	1016	* External antenna x 1
4.3	1017	)))
4.2	1018
4.3	1019	(((
31.40	1020
	1021
100.6	1022
31.40	1023	(% style="color:#037691" %)Dimension and weight:
4.2	1024
95.3	1025	* Device Size: 13.0 x 5 x 4.5 cm
	1026	* Device Weight: 150g
	1027	* Package Size / pcs : 15 x 12x 5.5 cm
	1028	* Weight / pcs : 220g
4.3	1029	)))
31.11	1030
64.5	1031	(((
31.11	1032
64.5	1033
	1034
	1035
4.3	1036	)))
4.2	1037
64.5	1038	= 9. Support =
4.2	1039
100.2	1040
4.2	1041	* 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.
	1042	* 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