Wiki source code of SW3L-NB -- NB-IoT Flow Sensor User Manual
Show last authors
author | version | line-number | content |
---|---|---|---|
1 | (% style="text-align:center" %) | ||
2 | [[image:image-20231010090810-1.png||height="518" width="839"]] | ||
3 | |||
4 | |||
5 | |||
6 | |||
7 | |||
8 | |||
9 | |||
10 | |||
11 | **Table of Contents:** | ||
12 | |||
13 | {{toc/}} | ||
14 | |||
15 | |||
16 | |||
17 | |||
18 | |||
19 | |||
20 | = 1. Introduction = | ||
21 | |||
22 | == 1.1 What is SW3L-NB NB-IoT Flow Sensor == | ||
23 | |||
24 | |||
25 | The Dragino SW3L-NB is a (% style="color:blue" %)**NB-IoT Flow Sensor**(%%). It detects water flow volume and uplink to IoT server via NB-IoT network. User can use this to (% style="color:blue" %)**monitor the water usage for buildings**. | ||
26 | |||
27 | The SW3L-NB will send water flow volume every 20 minutes. It can also detect the (% style="color:blue" %)**water flow status and send Alarm**(%%), to avoid the waste for water usage such as broken toilet case. | ||
28 | |||
29 | SW3L-NB is designed for both indoor and outdoor use. It has a weatherproof enclosure and industrial level battery to (% style="color:blue" %)**work in low to high temperatures**. | ||
30 | |||
31 | SW3L-NB supports different uplink methods including (% style="color:blue" %)**MQTT, MQTTs, UDP & TCP**(%%) for different application requirement, and support uplinks to various IoT Servers. | ||
32 | |||
33 | SW3L-NB (% style="color:blue" %)**supports BLE configure **(%%)and(% style="color:blue" %)** OTA update**(%%) which make user easy to use. | ||
34 | |||
35 | SW3L-NB is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), it is designed for long-term use up to several years. | ||
36 | |||
37 | SW3L-NB has optional built-in SIM card and default IoT server connection version. Which makes it works with simple configuration. | ||
38 | |||
39 | [[image:image-20231010091546-2.png||height="348" width="909"]] | ||
40 | |||
41 | |||
42 | == 1.2 Features == | ||
43 | |||
44 | |||
45 | * NB-IoT Bands: B1/B2/B3/B4/B5/B8/B12/B13/B17/B18/B19/B20/B25/B28/B66/B70/B85 @H-FDD | ||
46 | * Ultra-low power consumption | ||
47 | * Distance Detection by Ultrasonic technology | ||
48 | * Flat object range 30mm - 4500mm | ||
49 | * Accuracy: ±(1cm+S*0.3%) (S: Distance) | ||
50 | * Measure Angle: 60° | ||
51 | * Multiply Sampling and one uplink | ||
52 | * Support Bluetooth v5.1 remote configure and update firmware | ||
53 | * Uplink on periodically | ||
54 | * Downlink to change configure | ||
55 | * IP66 Waterproof Enclosure | ||
56 | * 8500mAh Battery for long term use | ||
57 | * Nano SIM card slot for NB-IoT SIM | ||
58 | |||
59 | == 1.3 Specification == | ||
60 | |||
61 | |||
62 | (% style="color:blue" %)**Common DC Characteristics:** | ||
63 | |||
64 | * Supply Voltage: 2.5v ~~ 3.6v | ||
65 | * Operating Temperature: -40 ~~ 85°C | ||
66 | |||
67 | (% style="color:blue" %)**NB-IoT Spec:** | ||
68 | |||
69 | (% style="color:#037691" %)**NB-IoT Module: BC660K-GL** | ||
70 | |||
71 | (% style="color:#037691" %)**Support Bands:** | ||
72 | |||
73 | * B1 @H-FDD: 2100MHz | ||
74 | * B2 @H-FDD: 1900MHz | ||
75 | * B3 @H-FDD: 1800MHz | ||
76 | * B4 @H-FDD: 2100MHz | ||
77 | * B5 @H-FDD: 860MHz | ||
78 | * B8 @H-FDD: 900MHz | ||
79 | * B12 @H-FDD: 720MHz | ||
80 | * B13 @H-FDD: 740MHz | ||
81 | * B17 @H-FDD: 730MHz | ||
82 | * B18 @H-FDD: 870MHz | ||
83 | * B19 @H-FDD: 870MHz | ||
84 | * B20 @H-FDD: 790MHz | ||
85 | * B25 @H-FDD: 1900MHz | ||
86 | * B28 @H-FDD: 750MHz | ||
87 | * B66 @H-FDD: 2000MHz | ||
88 | * B70 @H-FDD: 2000MHz | ||
89 | * B85 @H-FDD: 700MHz | ||
90 | |||
91 | (% style="color:blue" %)**Battery:** | ||
92 | |||
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 | ||
98 | |||
99 | (% style="color:blue" %)**Power Consumption** | ||
100 | |||
101 | * STOP Mode: 10uA @ 3.3v | ||
102 | * Max transmit power: 350mA@3.3v | ||
103 | |||
104 | (% class="wikigeneratedid" id="H1.4Ratedenvironmentalconditions" %) | ||
105 | (% style="display:none" %) (%%) | ||
106 | |||
107 | == 1.6 Applications == | ||
108 | |||
109 | |||
110 | * Horizontal distance measurement | ||
111 | * Liquid level measurement | ||
112 | * Parking management system | ||
113 | * Object proximity and presence detection | ||
114 | * Intelligent trash can management system | ||
115 | * Robot obstacle avoidance | ||
116 | * Automatic control | ||
117 | * Sewer | ||
118 | * Bottom water level monitoring | ||
119 | |||
120 | == 1.7 Sleep mode and working mode == | ||
121 | |||
122 | |||
123 | (% style="color:blue" %)**Deep Sleep Mode: **(%%)Sensor doesn't have any NB-IoT activate. This mode is used for storage and shipping to save battery life. | ||
124 | |||
125 | (% style="color:blue" %)**Working Mode:** (%%)In this mode, Sensor will work as NB-IoT Sensor to Join NB-IoT network and send out sensor data to server. Between each sampling/tx/rx periodically, sensor will be in IDLE mode), in IDLE mode, sensor has the same power consumption as Deep Sleep mode. | ||
126 | |||
127 | |||
128 | == 1.8 Button & LEDs == | ||
129 | |||
130 | |||
131 | [[image:Main.User Manual for LoRaWAN End Nodes.D20-LBD22-LBD23-LB_LoRaWAN_Temperature_Sensor_User_Manual.WebHome@1675071855856-879.png]] | ||
132 | |||
133 | |||
134 | (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) | ||
135 | |=(% style="width: 167px;background-color:#4F81BD;color:white" %)**Behavior on ACT**|=(% style="width: 117px;background-color:#4F81BD;color:white" %)**Function**|=(% style="width:225px;background-color:#4F81BD;color:white" %)**Action** | ||
136 | |(% style="width:167px" %)Pressing ACT between 1s < time < 3s|(% style="width:117px" %)Send an uplink|(% style="width:225px" %)((( | ||
137 | If sensor has already attached to NB-IoT network, sensor will send an uplink packet, (% style="color:blue" %)**blue led** (%%)will blink once. | ||
138 | Meanwhile, BLE module will be active and user can connect via BLE to configure device. | ||
139 | ))) | ||
140 | |(% style="width:167px" %)Pressing ACT for more than 3s|(% style="width:117px" %)Active Device|(% style="width:225px" %)((( | ||
141 | (% style="color:green" %)**Green led**(%%) will fast blink 5 times, device will enter (% style="color:#037691" %)**OTA mode**(%%) for 3 seconds. And then start to attach NB-IoT network. | ||
142 | (% style="color:green" %)**Green led**(%%) will solidly turn on for 5 seconds after joined in network. | ||
143 | Once sensor is active, BLE module will be active and user can connect via BLE to configure device, no matter if device attach NB-IoT network or not. | ||
144 | ))) | ||
145 | |(% style="width:167px" %)Fast press ACT 5 times.|(% style="width:117px" %)Deactivate Device|(% style="width:225px" %)(% style="color:red" %)**Red led**(%%) will solid on for 5 seconds. Means device is in Deep Sleep Mode. | ||
146 | |||
147 | == 1.9 BLE connection == | ||
148 | |||
149 | |||
150 | DDS45-NB support BLE remote configure and firmware update. | ||
151 | |||
152 | |||
153 | BLE can be used to configure the parameter of sensor or see the console output from sensor. BLE will be only activate on below case: | ||
154 | |||
155 | * Press button to send an uplink | ||
156 | * Press button to active device. | ||
157 | * Device Power on or reset. | ||
158 | |||
159 | If there is no activity connection on BLE in 60 seconds, sensor will shut down BLE module to enter low power mode. | ||
160 | |||
161 | |||
162 | == 1.10 Pin Definitions & Switch == | ||
163 | |||
164 | |||
165 | [[image:image-20230819104805-5.png]] | ||
166 | |||
167 | |||
168 | === 1.10.1 Jumper JP2 === | ||
169 | |||
170 | |||
171 | Power on Device when put this jumper. | ||
172 | |||
173 | |||
174 | === 1.10.2 BOOT MODE / SW1 === | ||
175 | |||
176 | |||
177 | **1)** (% style="color:blue" %)**ISP**(%%): upgrade mode, device won't have any signal in this mode. but ready for upgrade firmware. LED won't work. Firmware won't run. | ||
178 | |||
179 | **2)** (% style="color:blue" %)**Flash**(%%): work mode, device starts to work and send out console output for further debug | ||
180 | |||
181 | |||
182 | === 1.10.3 Reset Button === | ||
183 | |||
184 | |||
185 | Press to reboot the device. | ||
186 | |||
187 | (% style="display:none" %) | ||
188 | |||
189 | |||
190 | == 1.11 Mechanical == | ||
191 | |||
192 | [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/D20-LBD22-LBD23-LB_LoRaWAN_Temperature_Sensor_User_Manual/WebHome/1675143884058-338.png?rev=1.1||alt="1675143884058-338.png"]] | ||
193 | |||
194 | [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/D20-LBD22-LBD23-LB_LoRaWAN_Temperature_Sensor_User_Manual/WebHome/1675143899218-599.png?rev=1.1||alt="1675143899218-599.png"]] | ||
195 | |||
196 | [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/D20-LBD22-LBD23-LB_LoRaWAN_Temperature_Sensor_User_Manual/WebHome/1675143909447-639.png?rev=1.1||alt="1675143909447-639.png"]] | ||
197 | |||
198 | |||
199 | (% style="color:blue" %)**Probe Mechanical:** | ||
200 | |||
201 | [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDDS45%20-%20LoRaWAN%20Distance%20Detection%20Sensor%20User%20Manual/WebHome/1654915562090-396.png?rev=1.1||alt="1654915562090-396.png"]] | ||
202 | |||
203 | |||
204 | |||
205 | = 2. Use DDS45-NB to communicate with IoT Server = | ||
206 | |||
207 | == 2.1 Send data to IoT server via NB-IoT network == | ||
208 | |||
209 | |||
210 | The DDS45-NB is equipped with a NB-IoT module, the pre-loaded firmware in DDS45-NB 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 DDS45-NB. | ||
211 | |||
212 | |||
213 | Below shows the network structure: | ||
214 | |||
215 | [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/SW3L-NB_NB-IoT_Flow_Sensor_User_Manual/WebHome/image-20231010091546-2.png?width=909&height=348&rev=1.1||alt="image-20231010091546-2.png"]] | ||
216 | |||
217 | |||
218 | There are two version: (% style="color:blue" %)**-GE**(%%) and (% style="color:blue" %)**-1D**(%%) version of DDS45-NB. | ||
219 | |||
220 | |||
221 | (% style="color:blue" %)**GE Version**(%%): This version doesn't include SIM card or point to any IoT server. User needs to use AT Commands to configure below two steps to set DDS45-NB send data to IoT server. | ||
222 | |||
223 | * Install NB-IoT SIM card and configure APN. See instruction of [[Attach Network>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H2.AttachNetwork]]. | ||
224 | |||
225 | * Set up sensor to point to IoT Server. See instruction of [[Configure to Connect Different Servers>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H3.Configuretoconnecttodifferentservers]]. | ||
226 | |||
227 | Below shows result of different server as a glance. | ||
228 | |||
229 | (% border="1" cellspacing="4" style="width:515px" %) | ||
230 | |(% style="background-color:#4f81bd; color:white; width:100px" %)**Servers**|(% style="background-color:#4f81bd; color:white; width:300px" %)**Dash Board**|(% style="background-color:#4f81bd; color:white; width:115px" %)**Comments** | ||
231 | |(% style="width:127px" %)[[Node-Red>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H3.5A0Node-RedA028viaA0MQTT29]]|(% style="width:385px" %)((( | ||
232 | (% style="text-align:center" %) | ||
233 | [[image:image-20230819113244-8.png||height="183" width="367"]] | ||
234 | )))|(% style="width:170px" %) | ||
235 | |(% style="width:127px" %)[[DataCake>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H3.4Datacake]]|(% style="width:385px" %)((( | ||
236 | (% style="text-align:center" %) | ||
237 | [[image:image-20230819113244-9.png||height="119" width="367"]] | ||
238 | )))|(% style="width:170px" %) | ||
239 | |(% style="width:127px" %)[[Tago.IO>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H3.7A0Tago.ioA028viaA0MQTT29]]|(% style="width:385px" %) |(% style="width:170px" %) | ||
240 | |(% style="width:127px" %)[[General UDP>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H3.1GeneralA0UDPA0Connection]]|(% style="width:385px" %)Raw Payload. Need Developer to design Dash Board|(% style="width:170px" %) | ||
241 | |(% style="width:127px" %)[[General MQTT>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H3.2GeneralA0MQTTA0Connection]]|(% style="width:385px" %)Raw Payload. Need Developer to design Dash Board|(% style="width:170px" %) | ||
242 | |(% style="width:127px" %)[[ThingSpeak>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H3.3A0ThingSpeakA028viaA0MQTT29]]|(% style="width:385px" %)((( | ||
243 | (% style="text-align:center" %) | ||
244 | [[image:image-20230819113244-10.png||height="104" width="367"]] | ||
245 | )))|(% style="width:170px" %) | ||
246 | |(% style="width:127px" %)[[ThingsBoard>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H3.6A0ThingsBoard.CloudA028viaA0MQTT29]]|(% style="width:385px" %)((( | ||
247 | (% style="text-align:center" %) | ||
248 | [[image:image-20230819113244-11.png||height="141" width="367"]] | ||
249 | )))|(% style="width:170px" %) | ||
250 | |||
251 | (% style="color:blue" %)**1D Version**(%%): This version has 1NCE SIM card pre-installed and configure to send value to DataCake. User Just need to select the sensor type in DataCake and Activate DDS45-NB and user will be able to see data in DataCake. See here for [[DataCake Config Instruction>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H3.4Datacake]]. | ||
252 | |||
253 | |||
254 | == 2.2 Payload Types == | ||
255 | |||
256 | |||
257 | To meet different server requirement, DDS45-NB supports different payload type. | ||
258 | |||
259 | **Includes:** | ||
260 | |||
261 | * [[General JSON format payload>>||anchor="H2.2.1GeneralJsonFormat28Type3D529"]]. (Type=5) | ||
262 | |||
263 | * [[HEX format Payload>>||anchor="H2.2.2HEXformatPayload28Type3D029"]]. (Type=0) | ||
264 | |||
265 | * [[ThingSpeak Format>>||anchor="H2.2.4ThingSpeakPayload28Type3D129"]]. (Type=1) | ||
266 | |||
267 | * [[ThingsBoard Format>>||anchor="H2.2.3ThingsBoardPayload28Type3D329"]]. (Type=3) | ||
268 | |||
269 | User can specify the payload type when choose the connection protocol. Example: | ||
270 | |||
271 | (% style="color:#037691" %)**AT+PRO=2,0** (%%) ~/~/ Use UDP Connection & hex Payload | ||
272 | |||
273 | (% style="color:#037691" %)**AT+PRO=2,5** (%%) ~/~/ Use UDP Connection & Json Payload | ||
274 | |||
275 | (% style="color:#037691" %)**AT+PRO=3,5 ** (%%) ~/~/ Use MQTT Connection & Json Payload | ||
276 | |||
277 | |||
278 | === 2.2.1 General Json Format(Type~=5) === | ||
279 | |||
280 | |||
281 | This is the General Json Format. As below: | ||
282 | |||
283 | (% style="color:#4472c4" %)**{"IMEI":"866207058378443","Model":"DDS45-NB","distance":217,"battery":3.54,"signal":24,"1":{221,2023/09/20 09:47:01},"2":{0,2023/09/20 09:15:04},"3":{0,2023/09/20 09:00:04},"4":{0,2023/09/20 08:45:03},"5":{0,2023/09/20 08:30:03},"6":{0,2023/09/20 08:15:03},"7":{0,2023/09/20 08:00:04},"8":{0,2023/09/20 07:45:04}}** | ||
284 | |||
285 | |||
286 | [[image:image-20230920175015-3.png||height="613" width="890"]] | ||
287 | |||
288 | |||
289 | (% style="color:red" %)**Notice, from above payload:** | ||
290 | |||
291 | * Distance , Battery & Signal are the value at uplink time. | ||
292 | |||
293 | * Json entry 1 ~~ 8 are the last 1 ~~ 8 sampling data as specify by (% style="color:#037691" %)**AT+NOUD=8 ** (%%)Command. Each entry includes (from left to right): Distance, Sampling time. | ||
294 | |||
295 | === 2.2.2 HEX format Payload(Type~=0) === | ||
296 | |||
297 | |||
298 | This is the HEX Format. As below: | ||
299 | |||
300 | (% style="color:#4472c4" %)**f8662070583784430b640dda15010003a4650abc400000650ab8180000650ab4940000650ab10f0000650aad8b0000650aaa070000650aa6840000650aa3000000650a9308** | ||
301 | |||
302 | [[image:image-20230920172200-1.png||height="191" width="1047"]] | ||
303 | |||
304 | |||
305 | If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. | ||
306 | |||
307 | [[image:image-20230920173352-2.png||height="636" width="919"]] | ||
308 | |||
309 | |||
310 | (% style="color:blue" %)**Version:** | ||
311 | |||
312 | These bytes include the hardware and software version. | ||
313 | |||
314 | (% style="color:#037691" %)**Higher byte:**(%%) Specify Sensor Model: 0x0b for DDS45-NB | ||
315 | |||
316 | (% style="color:#037691" %)**Lower byte:**(%%) Specify the software version: 0x64=100, means firmware version 1.0.0 | ||
317 | |||
318 | |||
319 | (% style="color:blue" %)**BAT (Battery Info):** | ||
320 | |||
321 | Ex1: 0x0dda = 3546mV | ||
322 | |||
323 | |||
324 | (% style="color:blue" %)**Signal Strength:** | ||
325 | |||
326 | NB-IoT Network signal Strength. | ||
327 | |||
328 | **Ex1: 0x15 = 21** | ||
329 | |||
330 | **0** -113dBm or less | ||
331 | |||
332 | **1** -111dBm | ||
333 | |||
334 | **2...30** -109dBm... -53dBm | ||
335 | |||
336 | **31** -51dBm or greater | ||
337 | |||
338 | **99** Not known or not detectable | ||
339 | |||
340 | |||
341 | (% style="color:blue" %)**Distance: ** | ||
342 | |||
343 | Ex1: 0x03a4 = 932 mm | ||
344 | |||
345 | |||
346 | (% style="color:blue" %)**Timestamp: ** | ||
347 | |||
348 | Unit Timestamp Example: 650abc40(H) = 1695202368(D) | ||
349 | |||
350 | Put the decimal value into this link([[https:~~/~~/www.epochconverter.com)>>https://www.epochconverter.com]]) to get the time. | ||
351 | |||
352 | |||
353 | === 2.2.3 ThingsBoard Payload(Type~=3) === | ||
354 | |||
355 | |||
356 | Type3 payload special design for ThingsBoard, it will also configure other default server to ThingsBoard. | ||
357 | |||
358 | (% style="color:#4472c4" %)** {"IMEI": "866207058378443","Model": "DDS45-NB","distance": 502,"battery": 3.57,"signal": 23}** | ||
359 | |||
360 | [[image:image-20230922094043-2.png||height="558" width="851"]] | ||
361 | |||
362 | |||
363 | === === | ||
364 | |||
365 | === 2.2.4 ThingSpeak Payload(Type~=1) === | ||
366 | |||
367 | |||
368 | This payload meets ThingSpeak platform requirement. It includes only four fields. Form 1~~3 are: | ||
369 | |||
370 | Distance, Battery & Signal. This payload type only valid for ThingsSpeak Platform | ||
371 | |||
372 | As below: | ||
373 | |||
374 | (% style="color:#4472c4" %)**field1=Distance value&field2=Battery value&field3=Singal value** | ||
375 | |||
376 | [[image:image-20230921104741-1.png||height="565" width="826"]] | ||
377 | |||
378 | |||
379 | == 2.3 Uplink Payload == | ||
380 | |||
381 | |||
382 | ((( | ||
383 | DDS45-NB will uplink payload via LoRaWAN with below payload format: | ||
384 | ))) | ||
385 | |||
386 | ((( | ||
387 | Uplink payload includes in total 21 bytes. | ||
388 | ))) | ||
389 | |||
390 | (% border="1" cellspacing="5" style="background-color:#f2f2f2; width:510px" %) | ||
391 | |=(% style="width: 95px; background-color:#4F81BD;color:white" %)Size(bytes)|=(% style="width: 61px; background-color:#4F81BD;color:white" %)8|=(% style="width: 61px; background-color:#4F81BD;color:white" %)2|=(% style="background-color:#4F81BD;color:white" %)2|=(% style="background-color:#4F81BD;color:white" %)1|=(% style="background-color: rgb(79, 129, 189); color: white; width: 49px;" %)1|=(% style="background-color: rgb(79, 129, 189); color: white; width: 79px;" %)1|=(% style="background-color:#4F81BD;color:white" %)2|=(% style="background-color:#4F81BD;color:white" %)4 | ||
392 | |(% style="width:95px" %)Value|(% style="width:61px" %)f+IMEI|(% style="width:61px" %)Ver|(% style="width:61px" %)[[BAT>>||anchor="H2.3.1A0BatteryInfo"]]|(% style="width:61px" %)((( | ||
393 | Singal | ||
394 | |||
395 | Strength | ||
396 | )))|(% style="width:49px" %)Mod|(% style="width:79px" %)[[Digital Interrupt >>||anchor="H2.3.2A0Interrupt"]]|(% style="width:61px" %)[[Distance>>||anchor="H2.3.3A0Distance"]](unit: mm)|(% style="width:61px" %)((( | ||
397 | Timestamp | ||
398 | |||
399 | |||
400 | ))) | ||
401 | |||
402 | If the cache upload mechanism is turned on, you will receive the payload shown in the figure below. | ||
403 | |||
404 | (% border="1" cellspacing="5" style="background-color:#f2f2f2; width:512px" %) | ||
405 | |(% style="width:115px" %)**Frame header**|(% style="width:118px" %)**Frame data(1)**|(% style="width:116px" %)**Frame data(2)**|(% style="width:39px" %)**F…**|(% style="width:117px" %)**Frame data(X)** | ||
406 | |||
407 | === === | ||
408 | |||
409 | === 2.3.1 Battery Info === | ||
410 | |||
411 | |||
412 | Check the battery voltage for DDS45-NB. | ||
413 | |||
414 | Ex1: 0x0B45 = 2885mV | ||
415 | |||
416 | Ex2: 0x0B49 = 2889mV | ||
417 | |||
418 | |||
419 | === 2.3.2 Interrupt === | ||
420 | |||
421 | |||
422 | This data field shows if this packet is generated by interrupt or not. | ||
423 | |||
424 | **Example:** | ||
425 | |||
426 | 0x00: Normal uplink packet. | ||
427 | |||
428 | 0x01: Interrupt Uplink Packet. | ||
429 | |||
430 | |||
431 | === 2.3.3 Distance === | ||
432 | |||
433 | |||
434 | ((( | ||
435 | Get the distance. Flat object range 30mm - 4500mm. | ||
436 | ))) | ||
437 | |||
438 | ((( | ||
439 | 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:#4472c4" %)** ** | ||
440 | |||
441 | (% style="color:blue" %)**0B05(H) = 2821 (D) = 2821 mm.** | ||
442 | ))) | ||
443 | |||
444 | * If the sensor value is 0x0000, it means system doesn't detect ultrasonic sensor. | ||
445 | |||
446 | * If the sensor value lower than 0x001E (30mm), the sensor value will be 0x00. | ||
447 | |||
448 | ((( | ||
449 | |||
450 | ))) | ||
451 | |||
452 | == 2.4 Test Uplink and Change Update Interval == | ||
453 | |||
454 | |||
455 | By default, Sensor will send uplinks (% style="color:blue" %)**every 2 hours**(%%) & AT+NOUD=8 | ||
456 | |||
457 | User can use below commands to change the (% style="color:blue" %)**uplink interval**. | ||
458 | |||
459 | (% style="color:#037691" %)**AT+TDC=600 ** (%%) ~/~/ Set Update Interval to 600s | ||
460 | |||
461 | User can also push the button for more than 1 seconds to activate an uplink. | ||
462 | |||
463 | |||
464 | == 2.5 Multi-Samplings and One uplink == | ||
465 | |||
466 | |||
467 | To save battery life, DDS45-NB will sample Distance data every 15 minutes and send one uplink every 2 hours. So each uplink it will include 8 stored data + 1 real-time data. They are defined by: | ||
468 | |||
469 | * (% style="color:#037691" %)**AT+TR=900** (%%) ~/~/ The unit is seconds, and the default is to record data once every 900 seconds (15 minutes, the minimum can be set to 180 seconds) | ||
470 | |||
471 | * (% 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. | ||
472 | |||
473 | The diagram below explains the relationship between TR, NOUD, and TDC more clearly: | ||
474 | |||
475 | [[image:1692424376354-959.png]] | ||
476 | |||
477 | |||
478 | == 2.6 Trggier an uplink by external interrupt == | ||
479 | |||
480 | |||
481 | DDS45-NB has an external trigger interrupt function. Users can use the PB15 pin to trigger the upload of data packets. | ||
482 | |||
483 | (% style="color:blue" %)**AT command:** | ||
484 | |||
485 | * (% style="color:#037691" %)**AT+INTMOD **(%%) ~/~/ Set the trigger interrupt mode | ||
486 | |||
487 | * (% style="color:#037691" %)**AT+INTMOD=0 **(%%) ~/~/ Disable Interrupt | ||
488 | |||
489 | * (% style="color:#037691" %)**AT+INTMOD=1 **(%%) ~/~/ Trigger by rising and falling edge | ||
490 | |||
491 | * (% style="color:#037691" %)**AT+INTMOD=2 **(%%) ~/~/ Trigger by falling edge | ||
492 | |||
493 | * (% style="color:#037691" %)**AT+INTMOD=3 **(%%) ~/~/ Trigger by rising edge | ||
494 | |||
495 | = 3. Configure DDS45-NB = | ||
496 | |||
497 | == 3.1 Configure Methods == | ||
498 | |||
499 | |||
500 | DDS45-NB supports below configure method: | ||
501 | |||
502 | * AT Command via Bluetooth Connection (**Recommended**): [[BLE Configure Instruction>>http://wiki.dragino.com/xwiki/bin/view/Main/BLE%20Bluetooth%20Remote%20Configure/]]. | ||
503 | |||
504 | * AT Command via UART Connection : See [[UART Connection>>http://wiki.dragino.com/xwiki/bin/view/Main/UART%20Access%20for%20LoRa%20ST%20v4%20base%20model/#H2.3UARTConnectionforSN50v3basemotherboard]]. | ||
505 | |||
506 | == 3.2 AT Commands Set == | ||
507 | |||
508 | |||
509 | AT+<CMD>? : Help on <CMD> | ||
510 | |||
511 | AT+<CMD> : Run <CMD> | ||
512 | |||
513 | AT+<CMD>=<value> : Set the value | ||
514 | |||
515 | AT+<CMD>=? : Get the value | ||
516 | |||
517 | |||
518 | (% style="color:blue" %)**General Commands** | ||
519 | |||
520 | AT : Attention | ||
521 | |||
522 | AT? : Short Help | ||
523 | |||
524 | ATZ : MCU Reset | ||
525 | |||
526 | AT+TDC : Application Data Transmission Interval | ||
527 | |||
528 | AT+CFG : Print all configurations | ||
529 | |||
530 | AT+CFGMOD : Working mode selection | ||
531 | |||
532 | AT+DEUI : Get or set the Device ID | ||
533 | |||
534 | AT+INTMOD : Set the trigger interrupt mode | ||
535 | |||
536 | AT+5VT : Set extend the time of 5V power | ||
537 | |||
538 | AT+PRO : Choose agreement | ||
539 | |||
540 | AT+RXDL : Extend the sending and receiving time | ||
541 | |||
542 | AT+DNSCFG : Get or Set DNS Server | ||
543 | |||
544 | AT+GETSENSORVALUE : Returns the current sensor measurement | ||
545 | |||
546 | AT+NOUD : Get or Set the number of data to be uploaded | ||
547 | |||
548 | AT+CDP : Read or Clear cached data | ||
549 | |||
550 | AT+SHTEMP: Get or Set alarm of temp | ||
551 | |||
552 | AT+SHHUM: Get or Set alarm of moisture | ||
553 | |||
554 | AT+SERVADDR : Server Address | ||
555 | |||
556 | |||
557 | (% style="color:blue" %)**UDP Management** | ||
558 | |||
559 | AT+CFM : Upload confirmation mode (only valid for UDP) | ||
560 | |||
561 | |||
562 | (% style="color:blue" %)**MQTT Management** | ||
563 | |||
564 | AT+CLIENT : Get or Set MQTT client | ||
565 | |||
566 | AT+UNAME : Get or Set MQTT Username | ||
567 | |||
568 | AT+PWD : Get or Set MQTT password | ||
569 | |||
570 | AT+PUBTOPIC : Get or Set MQTT publish topic | ||
571 | |||
572 | AT+SUBTOPIC : Get or Set MQTT subscription topic | ||
573 | |||
574 | |||
575 | (% style="color:blue" %)**Information** | ||
576 | |||
577 | AT+FDR : Factory Data Reset | ||
578 | |||
579 | AT+PWORD : Serial Access Password | ||
580 | |||
581 | AT+LDATA : Get the last upload data | ||
582 | |||
583 | AT+CDP : Read or Clear cached data | ||
584 | |||
585 | |||
586 | = 4. Battery & Power Consumption = | ||
587 | |||
588 | |||
589 | DDS45-NB use ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace. | ||
590 | |||
591 | [[**Battery Info & Power Consumption Analyze**>>http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] . | ||
592 | |||
593 | |||
594 | = 5. Firmware update = | ||
595 | |||
596 | |||
597 | User can change device firmware to:: | ||
598 | |||
599 | * Update with new features. | ||
600 | |||
601 | * Fix bugs. | ||
602 | |||
603 | Firmware and changelog can be downloaded from : **[[Firmware download link>>https://www.dropbox.com/sh/l0bszumyrmil3yv/AAAg8LYGeAgDsD_ycCnweD72a?dl=0]]** | ||
604 | |||
605 | Methods to Update Firmware: | ||
606 | |||
607 | * (Recommended way) OTA firmware update via BLE: [[**Instruction**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/BLE_Firmware_Update_NB_Sensors_BC660K-GL/]]. | ||
608 | |||
609 | * Update through UART TTL interface : **[[Instruction>>url:http://wiki.dragino.com/xwiki/bin/view/Main/UART%20Access%20for%20LoRa%20ST%20v4%20base%20model/#H1.LoRaSTv4baseHardware]]**. | ||
610 | |||
611 | = 6. FAQ = | ||
612 | |||
613 | == 6.1 How can I access t BC660K-GL AT Commands? == | ||
614 | |||
615 | |||
616 | User can access to BC660K-GL directly and send AT Commands. | ||
617 | |||
618 | [[See BC660K-GL AT Command set>>url:https://www.dropbox.com/sh/5f6ssda5fum8rvs/AABT68l8ZzWOvZ5eg2qwOoFda?dl=0]] | ||
619 | |||
620 | |||
621 | == 6.2 Can I use DDS45-NB in condensation environment? == | ||
622 | |||
623 | |||
624 | DDS45-NB is not suitable to be used in condensation environment. Condensation on the DDS45-NB probe will affect the reading and always got 0. | ||
625 | |||
626 | |||
627 | = 7. Trouble Shooting = | ||
628 | |||
629 | == 7.1 Why does the sensor reading show 0 or "No sensor" == | ||
630 | |||
631 | |||
632 | ~1. The measurement object is very close to the sensor, but in the blind spot of the sensor. | ||
633 | |||
634 | 2. Sensor wiring is disconnected | ||
635 | |||
636 | 3. Not using the correct decoder | ||
637 | |||
638 | |||
639 | == 7.2 Abnormal readings The gap between multiple readings is too large or the gap between the readings and the actual value is too large == | ||
640 | |||
641 | |||
642 | 1) Please check if there is something on the probe affecting its measurement (condensed water, volatile oil, etc.) | ||
643 | |||
644 | 2) Does it change with temperature, temperature will affect its measurement | ||
645 | |||
646 | 3) If abnormal data occurs, you can turn on DEBUG mode, Please use downlink or AT COMMAN to enter DEBUG mode. | ||
647 | |||
648 | downlink command: (% style="color:blue" %)**F1 01**(%%), AT command: (% style="color:blue" %)**AT+DDEBUG=1** | ||
649 | |||
650 | 4) After entering the debug mode, it will send 20 pieces of data at a time, and you can send its uplink to us for analysis | ||
651 | |||
652 | [[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-20230113135125-2.png?width=1057&height=136&rev=1.1||alt="image-20230113135125-2.png"]] | ||
653 | |||
654 | |||
655 | Its original payload will be longer than other data. Even though it is being parsed, it can be seen that it is abnormal data. | ||
656 | |||
657 | Please send the data to us for check. | ||
658 | |||
659 | |||
660 | = 8. Order Info = | ||
661 | |||
662 | |||
663 | Part Number: (% style="color:blue" %)**DDS45-NB-XX** | ||
664 | |||
665 | (% style="color:red" %)**XX**(%%): | ||
666 | |||
667 | * (% style="color:#037691" %)**GE**(%%): General version ( Exclude SIM card) | ||
668 | |||
669 | * (% style="color:#037691" %)**1D**(%%): with 1NCE* 10 years 500MB SIM card and Pre-configure to DataCake server | ||
670 | |||
671 | (% style="color:#037691" %)**1NCE SIM Card NB-IoT network coverage**(%%): Austria, Belgium, Bulgaria, Croatia, Czech Republic, Denmark, Finland, Germany, Great Britain, Greece, Hungary, Ireland, Italy, Latvia, Malta, Netherlands, Norway, Puerto Rico, Russia, Slovak , Republic, Slovenia, Spain, Sweden, Switzerland, Taiwan, USA, US Virgin Islands | ||
672 | |||
673 | |||
674 | = 9. Packing Info = | ||
675 | |||
676 | |||
677 | (% style="color:#037691" %)**Package Includes**: | ||
678 | |||
679 | * DDS45-NB NB-IoT Distance Detection sensor x 1 | ||
680 | |||
681 | * External antenna x 1 | ||
682 | |||
683 | (% style="color:#037691" %)**Dimension and weight**: | ||
684 | |||
685 | * Device Size: 13.0 x 5 x 4.5 cm | ||
686 | |||
687 | * Device Weight: 150g | ||
688 | |||
689 | * Package Size / pcs : 14.0 x 8x 5 cm | ||
690 | |||
691 | * Weight / pcs : 180g | ||
692 | |||
693 | = 10. Support = | ||
694 | |||
695 | |||
696 | * 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. | ||
697 | |||
698 | * 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.cc>>mailto:Support@dragino.cc]]. | ||
699 | |||
700 | (% style="display:none" %) (%%) |