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

Version 96.2 by Xiaoling on 2022/07/09 11:05

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