Wiki source code of DS03A-NB_NB-IoT_Door_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 | * Upload water flow volume | ||
48 | * Monitor water waste | ||
49 | * Multiply Sampling and one uplink | ||
50 | * Support Bluetooth v5.1 remote configure and update firmware | ||
51 | * Uplink on periodically | ||
52 | * Downlink to change configure | ||
53 | * 8500mAh Battery for long term use | ||
54 | * Nano SIM card slot for NB-IoT SIM | ||
55 | |||
56 | |||
57 | |||
58 | == 1.3 Specification == | ||
59 | |||
60 | |||
61 | (% style="color:blue" %)**Common DC Characteristics:** | ||
62 | |||
63 | * Supply Voltage: 2.5v ~~ 3.6v | ||
64 | * Operating Temperature: -40 ~~ 85°C | ||
65 | |||
66 | (% style="color:blue" %)**NB-IoT Spec:** | ||
67 | |||
68 | (% style="color:#037691" %)**NB-IoT Module: BC660K-GL** | ||
69 | |||
70 | (% style="color:#037691" %)**Support Bands:** | ||
71 | |||
72 | * B1 @H-FDD: 2100MHz | ||
73 | * B2 @H-FDD: 1900MHz | ||
74 | * B3 @H-FDD: 1800MHz | ||
75 | * B4 @H-FDD: 2100MHz | ||
76 | * B5 @H-FDD: 860MHz | ||
77 | * B8 @H-FDD: 900MHz | ||
78 | * B12 @H-FDD: 720MHz | ||
79 | * B13 @H-FDD: 740MHz | ||
80 | * B17 @H-FDD: 730MHz | ||
81 | * B18 @H-FDD: 870MHz | ||
82 | * B19 @H-FDD: 870MHz | ||
83 | * B20 @H-FDD: 790MHz | ||
84 | * B25 @H-FDD: 1900MHz | ||
85 | * B28 @H-FDD: 750MHz | ||
86 | * B66 @H-FDD: 2000MHz | ||
87 | * B70 @H-FDD: 2000MHz | ||
88 | * B85 @H-FDD: 700MHz | ||
89 | |||
90 | (% style="color:blue" %)**Battery:** | ||
91 | |||
92 | * Li/SOCI2 un-chargeable battery | ||
93 | * Capacity: 8500mAh | ||
94 | * Self Discharge: <1% / Year @ 25°C | ||
95 | * Max continuously current: 130mA | ||
96 | * Max boost current: 2A, 1 second | ||
97 | |||
98 | (% style="color:blue" %)**Power Consumption** | ||
99 | |||
100 | * STOP Mode: 10uA @ 3.3v | ||
101 | * Max transmit power: 350mA@3.3v | ||
102 | |||
103 | (% class="wikigeneratedid" id="H1.4Ratedenvironmentalconditions" %) | ||
104 | (% style="display:none" %) (%%) | ||
105 | |||
106 | |||
107 | == 1.4 Flow Sensor Spec == | ||
108 | |||
109 | |||
110 | ((( | ||
111 | (% border="1" cellspacing="5" style="background-color:#f2f2f2; width:510px" %) | ||
112 | |=(% style="width: 80px;background-color:#4F81BD;color:white" %)**Model**|=(% style="width: 80px;background-color:#4F81BD;color:white" %)**Probe**|=(% style="width: 80px;background-color:#4F81BD;color:white" %)**Diameter**|=(% style="width: 80px;background-color:#4F81BD;color:white" %)**Range**|=(% style="width: 80px;background-color:#4F81BD;color:white" %)**Max Pressure**|=(% style="width: 110px;background-color:#4F81BD;color:white" %)**Measure** | ||
113 | |(% style="width:88px" %)SW3L-004|(% style="width:75px" %)DW-004|(% style="width:107px" %)G1/2" /DN15|(% style="width:101px" %)1~~30L/min|(% style="width:116px" %)≤ 2.0Mpa|(% style="width:124px" %)450 pulse = 1 L | ||
114 | |(% style="width:88px" %)SW3L-006|(% style="width:75px" %)DW-006|(% style="width:107px" %)G3/4" /DN20|(% style="width:101px" %)1~~60L/min|(% style="width:116px" %)≤ 1.2Mpa|(% style="width:124px" %)390 pulse = 1 L | ||
115 | |(% style="width:88px" %)SW3L-010|(% style="width:75px" %)DW-010|(% style="width:107px" %)G 1" /DN25|(% style="width:101px" %)2~~100L/min|(% style="width:116px" %)≤ 2.0Mpa|(% style="width:124px" %)64 pulse = 1 L | ||
116 | ))) | ||
117 | |||
118 | |||
119 | |||
120 | == 1.5 Applications == | ||
121 | |||
122 | |||
123 | * Flow Sensor application | ||
124 | * Water Control | ||
125 | * Toilet Flow Sensor | ||
126 | * Monitor Waste water | ||
127 | |||
128 | |||
129 | |||
130 | == 1.6 Sleep mode and working mode == | ||
131 | |||
132 | |||
133 | (% 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. | ||
134 | |||
135 | (% 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. | ||
136 | |||
137 | |||
138 | == 1.7 Button & LEDs == | ||
139 | |||
140 | |||
141 | [[image:Main.User Manual for LoRaWAN End Nodes.D20-LBD22-LBD23-LB_LoRaWAN_Temperature_Sensor_User_Manual.WebHome@1675071855856-879.png]] | ||
142 | |||
143 | |||
144 | (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) | ||
145 | |=(% 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** | ||
146 | |(% style="width:167px" %)Pressing ACT between 1s < time < 3s|(% style="width:117px" %)Send an uplink|(% style="width:225px" %)((( | ||
147 | If sensor has already attached to NB-IoT network, sensor will send an uplink packet, (% style="color:blue" %)**blue led** (%%)will blink once. | ||
148 | Meanwhile, BLE module will be active and user can connect via BLE to configure device. | ||
149 | ))) | ||
150 | |(% style="width:167px" %)Pressing ACT for more than 3s|(% style="width:117px" %)Active Device|(% style="width:225px" %)((( | ||
151 | (% 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. | ||
152 | (% style="color:green" %)**Green led**(%%) will solidly turn on for 5 seconds after joined in network. | ||
153 | 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. | ||
154 | ))) | ||
155 | |(% 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. | ||
156 | |||
157 | |||
158 | |||
159 | == 1.8 BLE connection == | ||
160 | |||
161 | |||
162 | SW3L-NB support BLE remote configure and firmware update. | ||
163 | |||
164 | |||
165 | 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: | ||
166 | |||
167 | * Press button to send an uplink | ||
168 | * Press button to active device. | ||
169 | * Device Power on or reset. | ||
170 | |||
171 | If there is no activity connection on BLE in 60 seconds, sensor will shut down BLE module to enter low power mode. | ||
172 | |||
173 | |||
174 | == 1.9 Pin Definitions & Switch == | ||
175 | |||
176 | |||
177 | [[image:image-20230819104805-5.png]] | ||
178 | |||
179 | |||
180 | === 1.9.1 Jumper JP2 === | ||
181 | |||
182 | |||
183 | Power on Device when put this jumper. | ||
184 | |||
185 | |||
186 | === 1.9.2 BOOT MODE / SW1 === | ||
187 | |||
188 | |||
189 | **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. | ||
190 | |||
191 | **2)** (% style="color:blue" %)**Flash**(%%): work mode, device starts to work and send out console output for further debug | ||
192 | |||
193 | |||
194 | === 1.9.3 Reset Button === | ||
195 | |||
196 | |||
197 | Press to reboot the device. | ||
198 | |||
199 | (% style="display:none" %) | ||
200 | |||
201 | |||
202 | == 1.10 Mechanical == | ||
203 | |||
204 | [[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"]] | ||
205 | |||
206 | [[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"]] | ||
207 | |||
208 | [[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"]] | ||
209 | |||
210 | |||
211 | |||
212 | **Probe Mechanical:** | ||
213 | |||
214 | |||
215 | (% style="color:blue" %)**DW-004 Flow Sensor: diameter: G1/2” / DN15. 450 pulse = 1 L** | ||
216 | |||
217 | [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/SW3L%20LoRaWAN%20Outdoor%20Flow%20Sensor/WebHome/image-20220519091350-1.png?width=722&height=385&rev=1.1||alt="image-20220519091350-1.png"]] | ||
218 | |||
219 | |||
220 | (% style="color:blue" %)**006: DW-006 Flow Sensor: diameter: G3/4” / DN20. 390 pulse = 1 L** | ||
221 | |||
222 | [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/SW3L%20LoRaWAN%20Outdoor%20Flow%20Sensor/WebHome/image-20220519091423-2.png?width=723&height=258&rev=1.1||alt="image-20220519091423-2.png"]] | ||
223 | |||
224 | |||
225 | (% style="color:blue" %)**010: DW-010 Flow Sensor: diameter: G 1” / DN25. 64 pulse = 1 L** | ||
226 | |||
227 | [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/SW3L%20LoRaWAN%20Outdoor%20Flow%20Sensor/WebHome/image-20220519091423-3.png?width=724&height=448&rev=1.1||alt="image-20220519091423-3.png"]] | ||
228 | |||
229 | |||
230 | = 2. Use SW3L-NB to communicate with IoT Server = | ||
231 | |||
232 | == 2.1 Send data to IoT server via NB-IoT network == | ||
233 | |||
234 | |||
235 | The SW3L-NB is equipped with a NB-IoT module, the pre-loaded firmware in SW3L-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 SW3L-NB. | ||
236 | |||
237 | |||
238 | Below shows the network structure: | ||
239 | |||
240 | [[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"]] | ||
241 | |||
242 | |||
243 | There are two version: (% style="color:blue" %)**-GE**(%%) and (% style="color:blue" %)**-1D**(%%) version of SW3L-NB. | ||
244 | |||
245 | |||
246 | (% 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 SW3L-NB send data to IoT server. | ||
247 | |||
248 | * 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]]. | ||
249 | |||
250 | * 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]]. | ||
251 | |||
252 | Below shows result of different server as a glance. | ||
253 | |||
254 | (% border="1" cellspacing="4" style="width:515px" %) | ||
255 | |(% 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** | ||
256 | |(% 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" %)((( | ||
257 | (% style="text-align:center" %) | ||
258 | [[image:image-20230819113244-8.png||height="183" width="367"]] | ||
259 | )))|(% style="width:170px" %) | ||
260 | |(% 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" %)((( | ||
261 | (% style="text-align:center" %) | ||
262 | [[image:image-20230819113244-9.png||height="119" width="367"]] | ||
263 | )))|(% style="width:170px" %) | ||
264 | |(% 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" %) | ||
265 | |(% 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" %) | ||
266 | |(% 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" %) | ||
267 | |(% 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" %)((( | ||
268 | (% style="text-align:center" %) | ||
269 | [[image:image-20230819113244-10.png||height="104" width="367"]] | ||
270 | )))|(% style="width:170px" %) | ||
271 | |(% 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" %)((( | ||
272 | (% style="text-align:center" %) | ||
273 | [[image:image-20230819113244-11.png||height="141" width="367"]] | ||
274 | )))|(% style="width:170px" %) | ||
275 | |||
276 | (% 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 SW3L-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]]. | ||
277 | |||
278 | |||
279 | == 2.2 Payload Types == | ||
280 | |||
281 | |||
282 | To meet different server requirement, SW3L-NB supports different payload type. | ||
283 | |||
284 | **Includes:** | ||
285 | |||
286 | * [[General JSON format payload>>||anchor="H2.2.1GeneralJsonFormat28Type3D529"]]. (Type=5) | ||
287 | |||
288 | * [[HEX format Payload>>||anchor="H2.2.2HEXformatPayload28Type3D029"]]. (Type=0) | ||
289 | |||
290 | * [[ThingSpeak Format>>||anchor="H2.2.4ThingSpeakPayload28Type3D129"]]. (Type=1) | ||
291 | |||
292 | * [[ThingsBoard Format>>||anchor="H2.2.3ThingsBoardPayload28Type3D329"]]. (Type=3) | ||
293 | |||
294 | User can specify the payload type when choose the connection protocol. Example: | ||
295 | |||
296 | (% style="color:#037691" %)**AT+PRO=2,0** (%%) ~/~/ Use UDP Connection & hex Payload | ||
297 | |||
298 | (% style="color:#037691" %)**AT+PRO=2,5** (%%) ~/~/ Use UDP Connection & Json Payload | ||
299 | |||
300 | (% style="color:#037691" %)**AT+PRO=3,5 ** (%%) ~/~/ Use MQTT Connection & Json Payload | ||
301 | |||
302 | |||
303 | === 2.2.1 General Json Format(Type~=5) === | ||
304 | |||
305 | |||
306 | This is the General Json Format. As below: | ||
307 | |||
308 | (% style="color:#4472c4" %)**{"IMEI":"866207058378443","Model":"SW3L-NB","flow":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}}** | ||
309 | |||
310 | |||
311 | [[image:image-20230920175015-3.png||height="613" width="890"]] | ||
312 | |||
313 | |||
314 | (% style="color:red" %)**Notice, from above payload:** | ||
315 | |||
316 | * Distance , Battery & Signal are the value at uplink time. | ||
317 | |||
318 | * 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): Water Flow, Sampling time. | ||
319 | |||
320 | |||
321 | |||
322 | === 2.2.2 HEX format Payload(Type~=0) === | ||
323 | |||
324 | |||
325 | This is the HEX Format. As below: | ||
326 | |||
327 | (% style="color:#4472c4" %)**f8662070583784430b640dda15010003a4650abc400000650ab8180000650ab4940000650ab10f0000650aad8b0000650aaa070000650aa6840000650aa3000000650a9308** | ||
328 | |||
329 | [[image:image-20230920172200-1.png||height="191" width="1047"]] | ||
330 | |||
331 | |||
332 | If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. | ||
333 | |||
334 | [[image:image-20230920173352-2.png||height="636" width="919"]] | ||
335 | |||
336 | |||
337 | (% style="color:blue" %)**Version:** | ||
338 | |||
339 | These bytes include the hardware and software version. | ||
340 | |||
341 | (% style="color:#037691" %)**Higher byte:**(%%) Specify Sensor Model: 0x11 for SW3L-NB | ||
342 | |||
343 | (% style="color:#037691" %)**Lower byte:**(%%) Specify the software version: 0x64=100, means firmware version 1.0.0 | ||
344 | |||
345 | |||
346 | (% style="color:blue" %)**BAT (Battery Info):** | ||
347 | |||
348 | Ex1: 0x0dda = 3546mV | ||
349 | |||
350 | |||
351 | (% style="color:blue" %)**Signal Strength:** | ||
352 | |||
353 | NB-IoT Network signal Strength. | ||
354 | |||
355 | **Ex1: 0x15 = 21** | ||
356 | |||
357 | **0** -113dBm or less | ||
358 | |||
359 | **1** -111dBm | ||
360 | |||
361 | **2...30** -109dBm... -53dBm | ||
362 | |||
363 | **31** -51dBm or greater | ||
364 | |||
365 | **99** Not known or not detectable | ||
366 | |||
367 | |||
368 | (% style="color:blue" %)**Timestamp: ** | ||
369 | |||
370 | Unit Timestamp Example: 650abc40(H) = 1695202368(D) | ||
371 | |||
372 | Put the decimal value into this link([[https:~~/~~/www.epochconverter.com)>>https://www.epochconverter.com]]) to get the time. | ||
373 | |||
374 | |||
375 | === 2.2.3 ThingsBoard Payload(Type~=3) === | ||
376 | |||
377 | |||
378 | Type3 payload special design for ThingsBoard, it will also configure other default server to ThingsBoard. | ||
379 | |||
380 | (% style="color:#4472c4" %)** {"IMEI": "866207058378443","Model": "SW3L","flow": 502,"battery": 3.57,"signal": 23}** | ||
381 | |||
382 | [[image:image-20230922094043-2.png||height="558" width="851"]] | ||
383 | |||
384 | |||
385 | |||
386 | === 2.2.4 ThingSpeak Payload(Type~=1) === | ||
387 | |||
388 | |||
389 | This payload meets ThingSpeak platform requirement. It includes only four fields. Form 1~~3 are: | ||
390 | |||
391 | Distance, Battery & Signal. This payload type only valid for ThingsSpeak Platform | ||
392 | |||
393 | As below: | ||
394 | |||
395 | (% style="color:#4472c4" %)**field1=Flow value&field2=Battery value&field3=Singal value** | ||
396 | |||
397 | [[image:image-20230921104741-1.png||height="565" width="826"]] | ||
398 | |||
399 | |||
400 | == 2.3 Uplink Payload == | ||
401 | |||
402 | === 2.3.1 Sensor Configuration, FPORT~=4 === | ||
403 | |||
404 | |||
405 | SW3L-NB will only send this command after getting the downlink command **(0x26 02)** from the server. | ||
406 | |||
407 | (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) | ||
408 | |(% style="background-color:#4f81bd; color:white; width:70px" %) **Size(bytes)**|(% style="background-color:#4f81bd; color:white; width:105px" %)**3**|(% style="background-color:#4f81bd; color:white; width:60px" %)**1**|(% style="background-color:#4f81bd; color:white; width:96px" %)**1**|(% style="background-color:#4f81bd; color:white; width:105px" %)**2**|(% style="background-color:#4f81bd; color:white; width:74px" %)**1** | ||
409 | |**Value**|(% style="width:104px" %)TDC(unit:sec)|(% style="width:43px" %)N/A|(% style="width:91px" %)Stop Timer|(% style="width:100px" %)Alarm Timer|(% style="width:69px" %)Reserve | ||
410 | |||
411 | Example parse in TTNv3 | ||
412 | |||
413 | [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/SW3L-LB_LoRaWAN_Flow_Sensor_User_Manual/WebHome/image-20230614172555-4.png?width=853&height=151&rev=1.1||alt="image-20230614172555-4.png"]] | ||
414 | |||
415 | |||
416 | * (% style="color:blue" %)**TDC: (default: 0x0004B0)** | ||
417 | |||
418 | Uplink interval for the total pulse count, default value is 0x0004B0 which is 1200 seconds = 20 minutes. | ||
419 | |||
420 | |||
421 | * (% style="color:blue" %)**STOP Duration & Alarm Timer** | ||
422 | |||
423 | Shows the configure value of [[Alarm for continuously water flow>>||anchor="H2.7Alarmforcontinuouslywaterflow"]] | ||
424 | |||
425 | |||
426 | === 2.3.2 Water Flow Value, Uplink FPORT~=2 === | ||
427 | |||
428 | |||
429 | ((( | ||
430 | SW3L-NB will send this uplink **after** Device Status once join the NB-IoT network successfully. And SW3L-NB will: | ||
431 | ))) | ||
432 | |||
433 | ((( | ||
434 | periodically send this uplink every 20 minutes, this interval [[can be changed>>||anchor="H2.10SetTransmitIntervalTime"]]. | ||
435 | ))) | ||
436 | |||
437 | ((( | ||
438 | Uplink Payload totals 11 bytes. | ||
439 | ))) | ||
440 | |||
441 | (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %) | ||
442 | |=(% colspan="6" style="width: 515px; background-color:#4F81BD;color:white" %)**Water Flow Value, FPORT=2** | ||
443 | |(% style="width:50px" %)**Size(bytes)**|(% style="width:110px" %)**1**|(% style="width:120px" %)**4**|(% style="width:110px" %)**1**|(% style="width:55px" %)**1**|(% style="width:70px" %)**4** | ||
444 | |(% style="width:110px" %)**Value**|(% style="width:81px" %)Calculate Flag & [[Alarm>>||anchor="H2.7Alarmforcontinuouslywaterflow"]]|(% style="width:95px" %)((( | ||
445 | Total pulse Or Last Pulse | ||
446 | )))|(% style="width:78px" %)((( | ||
447 | MOD & PA4_status & PB15_status | ||
448 | )))|(% style="width:92px" %)Reserve(0x01)|(% style="width:134px" %)Unix TimeStamp | ||
449 | |||
450 | **Calculate Flag & Alarm:** | ||
451 | |||
452 | (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:500px" %) | ||
453 | |(% style="background-color:#4f81bd; color:white; width:70px" %)**Size(bit)**|(% style="background-color:#4f81bd; color:white; width:70px" %)**[bit7:bit6]**|(% style="background-color:#4f81bd; color:white; width:90px" %)**[bit5:bit2]**|(% style="background-color:#4f81bd; color:white; width:140px" %)**bit1**|(% style="background-color:#4f81bd; color:white; width:130px" %)**bit0** | ||
454 | |(% style="width:88px" %)**Value**|(% style="width:117px" %)Reserve|(% style="width:117px" %)Calculate Flag|(% style="width:169px" %)Alarm: 0: No Alarm; 1: Alarm|(% style="width:150px" %)TDC flag 0:No;1:Yes | ||
455 | |||
456 | **MOD & PA4_status & PB15_status:** | ||
457 | |||
458 | (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:230px" %) | ||
459 | |(% style="background-color:#4f81bd; color:white; width:50px" %)**Size(bit)**|(% style="background-color:#4f81bd; color:white; width:60px" %)**bit7**|(% style="background-color:#4f81bd; color:white; width:60px" %)**bit6**|(% style="background-color:#4f81bd; color:white; width:60px" %)**[bit5:bit0]** | ||
460 | |(% style="width:88px" %)**Value**|(% style="width:117px" %)PA4_status|(% style="width:117px" %)PB15_status|(% style="width:118px" %)MOD | ||
461 | |||
462 | (% style="color:#037691" %)** **[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/SW3L-LB_LoRaWAN_Flow_Sensor_User_Manual/WebHome/image-20230626093242-1.png?width=892&height=276&rev=1.1||alt="image-20230626093242-1.png"]] | ||
463 | |||
464 | |||
465 | * ((( | ||
466 | (% style="color:blue" %)**Calculate Flag** | ||
467 | ))) | ||
468 | |||
469 | ((( | ||
470 | The calculate flag is a user defined field, IoT server can use this flag to handle different meters with different pulse factors. For example, if there are 100 Flow Sensors, meters 1 ~~50 are 1 liter/pulse and meters 51 ~~ 100 has 1.5 liter/pulse. | ||
471 | ))) | ||
472 | |||
473 | ((( | ||
474 | **Example: in the default payload:** | ||
475 | ))) | ||
476 | |||
477 | * ((( | ||
478 | calculate flag=0: for SW3L-004 Flow Sensor: 450 pulse = 1 L | ||
479 | ))) | ||
480 | * ((( | ||
481 | calculate flag=1: for SW3L-006 Flow Sensor: 390 pulse = 1 L | ||
482 | ))) | ||
483 | * ((( | ||
484 | calculate flag=2: for SW3L-010 Flow Sensor: 64 pulse = 1 L | ||
485 | ))) | ||
486 | |||
487 | ((( | ||
488 | Default value: 0. | ||
489 | ))) | ||
490 | |||
491 | ((( | ||
492 | Range (4 bits): (b)0000 ~~ (b) 1111 | ||
493 | |||
494 | If user use with a meter for example is 0.02L/pulse. To proper decode the correct value in server, | ||
495 | |||
496 | 1) User can set the Calculate Flag of this sensor to 3. | ||
497 | |||
498 | 2) In server side, when a sensor data arrive, the decoder will check the value of Calculate Flag, It the value is 3, the total volume = 0.02 x Pulse Count. | ||
499 | ))) | ||
500 | |||
501 | ((( | ||
502 | (% style="color:red" %)**NOTE: User need to set Calculate Flag to proper value before use Flow Sensor. Downlink or AT Command see: **(%%)Refer: [[Set Calculate Flag>>||anchor="H2.8Setthecalculateflag"]] | ||
503 | |||
504 | ((( | ||
505 | |||
506 | ))) | ||
507 | ))) | ||
508 | |||
509 | |||
510 | * ((( | ||
511 | (% style="color:blue" %)**Alarm** | ||
512 | ))) | ||
513 | |||
514 | ((( | ||
515 | See [[Alarm for continuously water flow>>||anchor="H2.7Alarmforcontinuouslywaterflow"]] | ||
516 | ))) | ||
517 | |||
518 | [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/SW3L%20LoRaWAN%20Outdoor%20Flow%20Sensor/WebHome/image-20220519095946-4.png?width=724&height=65&rev=1.1||alt="image-20220519095946-4.png"]] | ||
519 | |||
520 | |||
521 | ((( | ||
522 | * (% style="color:blue" %)**TDC flag** | ||
523 | |||
524 | When the flag is 1, it means sending packets at normal time intervals. | ||
525 | |||
526 | Otherwise, it is a packet sent at non-TDC time. | ||
527 | ))) | ||
528 | |||
529 | * ((( | ||
530 | (% style="color:blue" %)**Total pulse** | ||
531 | ))) | ||
532 | |||
533 | ((( | ||
534 | Total pulse/counting since factory | ||
535 | ))) | ||
536 | |||
537 | ((( | ||
538 | Range (4 Bytes) : 0x00000000~~ 0xFFFFFFFF . | ||
539 | |||
540 | |||
541 | ))) | ||
542 | |||
543 | * ((( | ||
544 | (% style="color:blue" %)**Last Pulse** | ||
545 | ))) | ||
546 | |||
547 | ((( | ||
548 | Total pulse since last FPORT=2 uplink. (Default 20 minutes) | ||
549 | ))) | ||
550 | |||
551 | ((( | ||
552 | Range (4 Bytes) : 0x00000000~~ 0xFFFFFFFF . | ||
553 | |||
554 | |||
555 | * ((( | ||
556 | (% style="color:blue" %)**PA4_status: Support digital level input below 3.3V** | ||
557 | ))) | ||
558 | |||
559 | ((( | ||
560 | 0 ~-~-> PA4 is at low level. | ||
561 | ))) | ||
562 | |||
563 | ((( | ||
564 | 1 ~-~-> PA4 is at high level. | ||
565 | |||
566 | |||
567 | * ((( | ||
568 | (% style="color:blue" %)**PB15_status: Support digital level input below 3.3V** | ||
569 | ))) | ||
570 | |||
571 | ((( | ||
572 | 0 ~-~-> PB15 is at low level. | ||
573 | ))) | ||
574 | |||
575 | ((( | ||
576 | 1 ~-~-> PB15 is at high level.. | ||
577 | ))) | ||
578 | ))) | ||
579 | ))) | ||
580 | |||
581 | * ((( | ||
582 | (% style="color:blue" %)**MOD: Default =0** | ||
583 | ))) | ||
584 | |||
585 | ((( | ||
586 | MOD=0 ~-~-> Uplink Total Pulse since factory | ||
587 | ))) | ||
588 | |||
589 | ((( | ||
590 | MOD=1 ~-~-> Uplink total pulse since last FPORT=2 uplink. | ||
591 | |||
592 | |||
593 | ))) | ||
594 | |||
595 | * ((( | ||
596 | (% style="color:blue" %)**Water Flow Value** | ||
597 | ))) | ||
598 | |||
599 | ((( | ||
600 | **Total Water Flow Volume = (Calculate Flag) x (Total Pulse)=9597/450=21.3L** | ||
601 | ))) | ||
602 | |||
603 | [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/SW3L%20LoRaWAN%20Outdoor%20Flow%20Sensor/WebHome/image-20220519095946-5.png?width=727&height=50&rev=1.1||alt="image-20220519095946-5.png"]] | ||
604 | |||
605 | |||
606 | ((( | ||
607 | **Total Water Flow for TDC timer = (Calculate Flag) x (Last Pulse)=79/450=0.2L** | ||
608 | ))) | ||
609 | |||
610 | [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/SW3L%20LoRaWAN%20Outdoor%20Flow%20Sensor/WebHome/image-20220519095946-6.png?width=733&height=43&rev=1.1||alt="image-20220519095946-6.png"]] ** ** | ||
611 | |||
612 | |||
613 | === 2.3.3 Historical Water Flow Status, FPORT~=3 === | ||
614 | |||
615 | |||
616 | ((( | ||
617 | SW3L-NB stores sensor values and users can retrieve these history values via the downlink command. | ||
618 | ))) | ||
619 | |||
620 | ((( | ||
621 | The historical payload includes one or multiplies entries and every entry has the same payload as Real-Time water flow status. | ||
622 | |||
623 | (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %) | ||
624 | |=(% colspan="6" style="width: 515px; background-color:#4F81BD;color:white" %)**Water Flow Value, FPORT=3** | ||
625 | |(% style="width:50px" %)**Size(bytes)**|(% style="width:110px" %)**1**|(% style="width:120px" %)**4**|(% style="width:110px" %)**1**|(% style="width:55px" %)**1**|(% style="width:70px" %)**4** | ||
626 | |(% style="width:110px" %)**Value**|(% style="width:81px" %)Calculate Flag & [[Alarm>>||anchor="H2.7Alarmforcontinuouslywaterflow"]]|(% style="width:95px" %)((( | ||
627 | Total pulse Or Last Pulse | ||
628 | )))|(% style="width:78px" %)((( | ||
629 | MOD & PA4_status & PB15_status | ||
630 | )))|(% style="width:92px" %)Reserve(0x01)|(% style="width:134px" %)Unix TimeStamp | ||
631 | |||
632 | **Calculate Flag & Alarm:** | ||
633 | |||
634 | (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %) | ||
635 | |(% style="background-color:#4f81bd; color:white; width:50px" %)**Size(bit)**|(% style="background-color:#4f81bd; color:white; width:89px" %)**bit7**|(% style="background-color:#4f81bd; color:white; width:89px" %)**bit6**|(% style="background-color:#4f81bd; color:white; width:69px" %)**[bit5:bit2]**|(% style="background-color:#4f81bd; color:white; width:129px" %)**bit1**|(% style="background-color:#4f81bd; color:white; width:89px" %)**bit0** | ||
636 | |(% style="width:88px" %)**Value**|(% style="width:96px" %)((( | ||
637 | No ACK message | ||
638 | )))|(% style="width:94px" %)Poll Message Flag|(% style="width:115px" %)Calculate Flag|(% style="width:136px" %)Alarm: 0: No Alarm; 1: Alarm|(% style="width:120px" %)TDC flag 0:No;1:Yes | ||
639 | |||
640 | **MOD & PA4_status & PB15_status:** | ||
641 | |||
642 | (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:240px" %) | ||
643 | |(% style="background-color:#4f81bd; color:white; width:60px" %)**Size(bit)**|(% style="background-color:#4f81bd; color:white; width:60px" %)**bit7**|(% style="background-color:#4f81bd; color:white; width:60px" %)**bit6**|(% style="background-color:#4f81bd; color:white; width:60px" %)**[bit5:bit0]** | ||
644 | |(% style="width:88px" %)**Value**|(% style="width:117px" %)PA4_status|(% style="width:117px" %)PB15_status|(% style="width:118px" %)MOD | ||
645 | ))) | ||
646 | |||
647 | * ((( | ||
648 | Each data entry is 11 bytes and has the same structure as [[real time water flow status>>||anchor="H2.3.2A0WaterFlowValue2CUplinkFPORT3D2"]], to save airtime and battery, SW3L will send max bytes according to the current DR and Frequency bands. | ||
649 | ))) | ||
650 | |||
651 | ((( | ||
652 | For example, in the US915 band, the max payload for different DR is: | ||
653 | ))) | ||
654 | |||
655 | ((( | ||
656 | (% style="color:blue" %)**a) DR0:**(%%) max is 11 bytes so one entry of data | ||
657 | ))) | ||
658 | |||
659 | ((( | ||
660 | (% style="color:blue" %)**b) DR1:**(%%) max is 53 bytes so devices will upload 4 entries of data (total 44 bytes) | ||
661 | ))) | ||
662 | |||
663 | ((( | ||
664 | (% style="color:blue" %)**c) DR2:**(%%) total payload includes 11 entries of data | ||
665 | ))) | ||
666 | |||
667 | ((( | ||
668 | (% style="color:blue" %)**d) DR3:**(%%) total payload includes 22 entries of data. | ||
669 | ))) | ||
670 | |||
671 | ((( | ||
672 | If SW3L-NB doesn't have any data in the polling time. It will uplink 11 bytes of 0 | ||
673 | |||
674 | |||
675 | ))) | ||
676 | |||
677 | ((( | ||
678 | (% style="color:#037691" %)**Downlink:** | ||
679 | ))) | ||
680 | |||
681 | ((( | ||
682 | 0x31 64 92 C5 AC 64 92 C7 8C 05 | ||
683 | ))) | ||
684 | |||
685 | [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/SW3L-LB_LoRaWAN_Flow_Sensor_User_Manual/WebHome/image-20230626093440-2.png?width=890&height=160&rev=1.1||alt="image-20230626093440-2.png"]] | ||
686 | |||
687 | |||
688 | ((( | ||
689 | (% style="color:#037691" %)**Uplink:** | ||
690 | ))) | ||
691 | |||
692 | ((( | ||
693 | 41 00 01 00 00 00 08 64 92 C5 E4 40 00 01 00 00 00 08 64 92 C6 06 49 41 01 00 00 00 00 64 92 C6 8B 49 81 01 00 00 00 00 64 92 C7 34 4A 01 01 00 00 00 2D 64 92 C7 7C | ||
694 | |||
695 | |||
696 | ))) | ||
697 | |||
698 | ((( | ||
699 | (% style="color:#037691" %)**Parsed Value:** | ||
700 | ))) | ||
701 | |||
702 | ((( | ||
703 | [TDC_flag, Alarm, Calculate Flag, PA4_status, PB15_status, MOD, Total pulse or Last Pulse,** **Water Flow Value, TIME] | ||
704 | ))) | ||
705 | |||
706 | |||
707 | ((( | ||
708 | [YES,FALSE,0,L,L, 0,8, 0.0,2023-06-21 09:41:56], | ||
709 | |||
710 | [NO,FALSE,0,L,L, 0,8, 0.0,2023-06-21 09:42:30], | ||
711 | |||
712 | [YES,FALSE,2,L,H,1,0, 0.0,2023-06-21 09:44:43], | ||
713 | |||
714 | [YES,FALSE,2,H,L,1,0, 0.0,2023-06-21 09:47:32], | ||
715 | |||
716 | [NO,TRUE ,2, L,L,1,45,0.7,2023-06-21 09:48:44], | ||
717 | ))) | ||
718 | |||
719 | [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/SW3L-LB_LoRaWAN_Flow_Sensor_User_Manual/WebHome/image-20230626093703-3.png?width=894&height=156&rev=1.1||alt="image-20230626093703-3.png"]] | ||
720 | |||
721 | |||
722 | == 2.4 Test Uplink and Change Update Interval == | ||
723 | |||
724 | |||
725 | By default, Sensor will send uplinks (% style="color:blue" %)**every 2 hours**(%%) & AT+NOUD=8 | ||
726 | |||
727 | User can use below commands to change the (% style="color:blue" %)**uplink interval**. | ||
728 | |||
729 | (% style="color:#037691" %)**AT+TDC=600 ** (%%) ~/~/ Set Update Interval to 600s | ||
730 | |||
731 | User can also push the button for more than 1 seconds to activate an uplink. | ||
732 | |||
733 | |||
734 | == 2.5 Multi-Samplings and One uplink == | ||
735 | |||
736 | |||
737 | To save battery life, SW3L-NB will sample Water Flow 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: | ||
738 | |||
739 | * (% 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) | ||
740 | |||
741 | * (% 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. | ||
742 | |||
743 | The diagram below explains the relationship between TR, NOUD, and TDC more clearly: | ||
744 | |||
745 | [[image:1692424376354-959.png]] | ||
746 | |||
747 | |||
748 | == 2.6 Trggier an uplink by external interrupt == | ||
749 | |||
750 | |||
751 | SW3L-NB has an external trigger interrupt function. Users can use the PB15 pin to trigger the upload of data packets. | ||
752 | |||
753 | (% style="color:blue" %)**AT command:** | ||
754 | |||
755 | * (% style="color:#037691" %)**AT+INTMOD **(%%) ~/~/ Set the trigger interrupt mode | ||
756 | |||
757 | * (% style="color:#037691" %)**AT+INTMOD=0 **(%%) ~/~/ Disable Interrupt | ||
758 | |||
759 | * (% style="color:#037691" %)**AT+INTMOD=1 **(%%) ~/~/ Trigger by rising and falling edge | ||
760 | |||
761 | * (% style="color:#037691" %)**AT+INTMOD=2 **(%%) ~/~/ Trigger by falling edge | ||
762 | |||
763 | * (% style="color:#037691" %)**AT+INTMOD=3 **(%%) ~/~/ Trigger by rising edge | ||
764 | |||
765 | |||
766 | |||
767 | == 2.7 Alarm for continuously water flow == | ||
768 | |||
769 | |||
770 | ((( | ||
771 | This feature is to monitor and send Alarm for continuously water flow. | ||
772 | ))) | ||
773 | |||
774 | ((( | ||
775 | Example case is for Toilet water monitoring, if some one push toilet button, the toilet will have water flow. If the toilet button has broken and can't returned to original state, the water flow will keep for hours or days which cause huge waste for water. | ||
776 | ))) | ||
777 | |||
778 | ((( | ||
779 | To monitor this faulty and send alarm, there are two settings: | ||
780 | ))) | ||
781 | |||
782 | * ((( | ||
783 | (% style="color:blue" %)**Stop Duration: Unit: Second** | ||
784 | ))) | ||
785 | |||
786 | ((( | ||
787 | Default: 15s, If SW3L-NB didn't see any water flow in 15s, SW3L-NB will consider stop of water flow event. | ||
788 | ))) | ||
789 | |||
790 | * ((( | ||
791 | (% style="color:blue" %)**Alarm Timer: Units: Minute; Default 0 minutes (means Alarm disable)** | ||
792 | ))) | ||
793 | |||
794 | ((( | ||
795 | **Example:** 3 minutes, if SW3L-NB detect a start of water flow event and didn't detect a stop event within Alarm timer, SW3L-NB will send an Alarm to indicate a water flow abnormal alarm. | ||
796 | ))) | ||
797 | |||
798 | ((( | ||
799 | So for example, If we set stop duration=15s and Alarm Timer=3minutes. If the toilet water flow continuously for more than 3 minutes, Sensor will send an alarm (in Confirmed MODE) to platform. | ||
800 | ))) | ||
801 | |||
802 | ((( | ||
803 | (% style="color:red" %)**Note:** **After this alarm is send, sensor will consider a stop of water flow and count for another new event. So if water flow waste last for 1 hour, Sensor will keep sending alarm every 3 minutes.** | ||
804 | ))) | ||
805 | |||
806 | ((( | ||
807 | (% style="color:blue" %)**AT Command to configure:** | ||
808 | ))) | ||
809 | |||
810 | * ((( | ||
811 | AT+PTRIG=15,3 ~-~-> Set Stop duration: 15s, Alarm Timer: 3 minutes. | ||
812 | ))) | ||
813 | |||
814 | * ((( | ||
815 | AT+ PTRIG=15,0 ~-~-> Default Value, disable water waste Alarm. | ||
816 | ))) | ||
817 | |||
818 | ((( | ||
819 | (% style="color:blue" %)**Downlink Command to configure:** | ||
820 | ))) | ||
821 | |||
822 | ((( | ||
823 | Command: **0xAA aa bb cc** | ||
824 | ))) | ||
825 | |||
826 | ((( | ||
827 | AA: Command Type Code | ||
828 | ))) | ||
829 | |||
830 | ((( | ||
831 | aa: Stop duration | ||
832 | ))) | ||
833 | |||
834 | ((( | ||
835 | bb cc: Alarm Timer | ||
836 | ))) | ||
837 | |||
838 | ((( | ||
839 | If user send 0xAA 0F 00 03: equal to AT+PTRIG=15,3 | ||
840 | ))) | ||
841 | |||
842 | |||
843 | == 2.8 Set the calculate flag == | ||
844 | |||
845 | |||
846 | Feature: Set the calculate flag | ||
847 | |||
848 | (% style="color:blue" %)**AT Command: AT+CALCFLAG** | ||
849 | |||
850 | (% border="1" cellspacing="5" style="background-color:#f2f2f2; width:461px" %) | ||
851 | |=(% style="width: 158px;background-color:#4F81BD;color:white" %)**Command Example**|=(% style="width: 193px;background-color:#4F81BD;color:white" %)**Function**|=(% style="width: 110px;background-color:#4F81BD;color:white" %)**Response** | ||
852 | |(% style="width:158px" %)AT+CALCFLAG =1|(% style="width:192px" %)Set the calculate flag to 1.|(% style="width:109px" %)OK | ||
853 | |(% style="width:158px" %)AT+CALCFLAG =2|(% style="width:192px" %)Set the calculate flag to 2.|(% style="width:109px" %)OK | ||
854 | |||
855 | (% style="color:blue" %)**Downlink Command:** | ||
856 | |||
857 | * **Example**: 0XA501 ~/~/ Same as AT+CALCFLAG =1 | ||
858 | |||
859 | |||
860 | |||
861 | == 2.9 Set count number == | ||
862 | |||
863 | |||
864 | Feature: Manually set the count number | ||
865 | |||
866 | (% style="color:blue" %)**AT Command: AT+SETCNT** | ||
867 | |||
868 | (% border="1" cellspacing="5" style="background-color:#f2f2f2; width:479px" %) | ||
869 | |=(% style="width: 160px;background-color:#4F81BD;color:white" %)**Command Example**|=(% style="width: 223px;background-color:#4F81BD;color:white" %)**Function**|=(% style="width: 96px;background-color:#4F81BD;color:white" %)**Response** | ||
870 | |(% style="width:160px" %)AT+ SETCNT =0|(% style="width:221px" %)Set the count number to 0.|(% style="width:95px" %)OK | ||
871 | |(% style="width:160px" %)AT+ SETCNT =100|(% style="width:221px" %)Set the count number to 100.|(% style="width:95px" %)OK | ||
872 | |||
873 | (% style="color:blue" %)**Downlink Command:** | ||
874 | |||
875 | * **Example**: 0xA6000001 ~/~/ Same as AT+ SETCNT =1 | ||
876 | |||
877 | * **Example**: 0xA6000064 ~/~/ Same as AT+ SETCNT =100 | ||
878 | |||
879 | |||
880 | |||
881 | == 2.10 Set Transmit Interval Time == | ||
882 | |||
883 | |||
884 | ((( | ||
885 | Feature: Change NB-IoT End Node Transmit Interval. | ||
886 | ))) | ||
887 | |||
888 | ((( | ||
889 | (% style="color:blue" %)**AT Command: AT+TDC** | ||
890 | ))) | ||
891 | |||
892 | (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) | ||
893 | |=(% style="width: 156px;background-color:#4F81BD;color:white" %)**Command Example**|=(% style="width: 137px;background-color:#4F81BD;color:white" %)**Function**|=(% style="background-color:#4F81BD;color:white" %)**Response** | ||
894 | |(% style="width:156px" %)AT+TDC=?|(% style="width:137px" %)Show current transmit Interval|((( | ||
895 | 30000 | ||
896 | OK | ||
897 | the interval is 30000ms = 30s | ||
898 | ))) | ||
899 | |(% style="width:156px" %)AT+TDC=60000|(% style="width:137px" %)Set Transmit Interval|((( | ||
900 | OK | ||
901 | Set transmit interval to 60000ms = 60 seconds | ||
902 | ))) | ||
903 | |||
904 | ((( | ||
905 | (% style="color:blue" %)**Downlink Command: 0x01** | ||
906 | ))) | ||
907 | |||
908 | ((( | ||
909 | Format: Command Code (0x01) followed by 3 bytes time value. | ||
910 | ))) | ||
911 | |||
912 | ((( | ||
913 | If the downlink payload=0100003C, it means set the END Node's Transmit Interval to 0x00003C=60(S), while type code is 01. | ||
914 | ))) | ||
915 | |||
916 | * ((( | ||
917 | Example 1: Downlink Payload: 0100001E ~/~/ Set Transmit Interval (TDC) = 30 seconds | ||
918 | ))) | ||
919 | * ((( | ||
920 | Example 2: Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds | ||
921 | |||
922 | |||
923 | |||
924 | ))) | ||
925 | |||
926 | = 3. Configure SW3L-NB = | ||
927 | |||
928 | == 3.1 Configure Methods == | ||
929 | |||
930 | |||
931 | SW3L-NB supports below configure method: | ||
932 | |||
933 | * AT Command via Bluetooth Connection (**Recommended**): [[BLE Configure Instruction>>http://wiki.dragino.com/xwiki/bin/view/Main/BLE%20Bluetooth%20Remote%20Configure/]]. | ||
934 | |||
935 | * 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]]. | ||
936 | |||
937 | |||
938 | |||
939 | == 3.2 AT Commands Set == | ||
940 | |||
941 | |||
942 | AT+<CMD>? : Help on <CMD> | ||
943 | |||
944 | AT+<CMD> : Run <CMD> | ||
945 | |||
946 | AT+<CMD>=<value> : Set the value | ||
947 | |||
948 | AT+<CMD>=? : Get the value | ||
949 | |||
950 | |||
951 | (% style="color:blue" %)**General Commands** | ||
952 | |||
953 | AT : Attention | ||
954 | |||
955 | AT? : Short Help | ||
956 | |||
957 | ATZ : MCU Reset | ||
958 | |||
959 | AT+TDC : Application Data Transmission Interval | ||
960 | |||
961 | AT+CFG : Print all configurations | ||
962 | |||
963 | AT+CFGMOD : Working mode selection | ||
964 | |||
965 | AT+DEUI : Get or set the Device ID | ||
966 | |||
967 | AT+INTMOD : Set the trigger interrupt mode | ||
968 | |||
969 | AT+5VT : Set extend the time of 5V power | ||
970 | |||
971 | AT+PRO : Choose agreement | ||
972 | |||
973 | AT+RXDL : Extend the sending and receiving time | ||
974 | |||
975 | AT+DNSCFG : Get or Set DNS Server | ||
976 | |||
977 | AT+GETSENSORVALUE : Returns the current sensor measurement | ||
978 | |||
979 | AT+NOUD : Get or Set the number of data to be uploaded | ||
980 | |||
981 | AT+CDP : Read or Clear cached data | ||
982 | |||
983 | AT+SHTEMP: Get or Set alarm of temp | ||
984 | |||
985 | AT+SHHUM: Get or Set alarm of moisture | ||
986 | |||
987 | AT+SERVADDR : Server Address | ||
988 | |||
989 | |||
990 | (% style="color:blue" %)**UDP Management** | ||
991 | |||
992 | AT+CFM : Upload confirmation mode (only valid for UDP) | ||
993 | |||
994 | |||
995 | (% style="color:blue" %)**MQTT Management** | ||
996 | |||
997 | AT+CLIENT : Get or Set MQTT client | ||
998 | |||
999 | AT+UNAME : Get or Set MQTT Username | ||
1000 | |||
1001 | AT+PWD : Get or Set MQTT password | ||
1002 | |||
1003 | AT+PUBTOPIC : Get or Set MQTT publish topic | ||
1004 | |||
1005 | AT+SUBTOPIC : Get or Set MQTT subscription topic | ||
1006 | |||
1007 | |||
1008 | (% style="color:blue" %)**Information** | ||
1009 | |||
1010 | AT+FDR : Factory Data Reset | ||
1011 | |||
1012 | AT+PWORD : Serial Access Password | ||
1013 | |||
1014 | AT+LDATA : Get the last upload data | ||
1015 | |||
1016 | AT+CDP : Read or Clear cached data | ||
1017 | |||
1018 | |||
1019 | = 4. Battery & Power Consumption = | ||
1020 | |||
1021 | |||
1022 | SW3L-NB use ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace. | ||
1023 | |||
1024 | [[**Battery Info & Power Consumption Analyze**>>http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] . | ||
1025 | |||
1026 | |||
1027 | = 5. Firmware update = | ||
1028 | |||
1029 | |||
1030 | User can change device firmware to:: | ||
1031 | |||
1032 | * Update with new features. | ||
1033 | |||
1034 | * Fix bugs. | ||
1035 | |||
1036 | Firmware and changelog can be downloaded from : **[[Firmware download link>>https://www.dropbox.com/sh/l0bszumyrmil3yv/AAAg8LYGeAgDsD_ycCnweD72a?dl=0]]** | ||
1037 | |||
1038 | Methods to Update Firmware: | ||
1039 | |||
1040 | * (Recommended way) OTA firmware update via BLE: [[**Instruction**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/BLE_Firmware_Update_NB_Sensors_BC660K-GL/]]. | ||
1041 | |||
1042 | * 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]]**. | ||
1043 | |||
1044 | |||
1045 | |||
1046 | = 6. FAQ = | ||
1047 | |||
1048 | == 6.1 How can I access t BC660K-GL AT Commands? == | ||
1049 | |||
1050 | |||
1051 | User can access to BC660K-GL directly and send AT Commands. | ||
1052 | |||
1053 | [[See BC660K-GL AT Command set>>url:https://www.dropbox.com/sh/5f6ssda5fum8rvs/AABT68l8ZzWOvZ5eg2qwOoFda?dl=0]] | ||
1054 | |||
1055 | |||
1056 | = 7. Order Info = | ||
1057 | |||
1058 | |||
1059 | Part Number: (% style="color:blue" %)**SW3L-NB-XX-YY** | ||
1060 | |||
1061 | (% style="color:red" %)**XX**(%%): | ||
1062 | |||
1063 | * (% style="color:#037691" %)**GE**(%%): General version ( Exclude SIM card) | ||
1064 | |||
1065 | * (% style="color:#037691" %)**1D**(%%): with 1NCE* 10 years 500MB SIM card and Pre-configure to DataCake server | ||
1066 | |||
1067 | (% 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 | ||
1068 | |||
1069 | ((( | ||
1070 | (% style="color:blue" %)**YY**(%%): Flow Sensor Model: | ||
1071 | ))) | ||
1072 | |||
1073 | ((( | ||
1074 | **004:** DW-004 Flow Sensor: diameter: G1/2” / DN15. 450 pulse = 1 L | ||
1075 | ))) | ||
1076 | |||
1077 | ((( | ||
1078 | **006:** DW-006 Flow Sensor: diameter: G3/4” / DN20. 390 pulse = 1 L | ||
1079 | ))) | ||
1080 | |||
1081 | ((( | ||
1082 | **010:** DW-010 Flow Sensor: diameter: G 1” / DN25. 64 pulse = 1 L | ||
1083 | ))) | ||
1084 | |||
1085 | * ((( | ||
1086 | calculate flag=0: for SW3L-004 Flow Sensor: 450 pulse = 1 L | ||
1087 | ))) | ||
1088 | |||
1089 | * ((( | ||
1090 | calculate flag=1: for SW3L-006 Flow Sensor: 390 pulse = 1 L | ||
1091 | ))) | ||
1092 | |||
1093 | * ((( | ||
1094 | calculate flag=2: for SW3L-010 Flow Sensor: 64 pulse = 1 L | ||
1095 | |||
1096 | |||
1097 | |||
1098 | ))) | ||
1099 | |||
1100 | = 8. Packing Info = | ||
1101 | |||
1102 | |||
1103 | (% style="color:#037691" %)**Package Includes**: | ||
1104 | |||
1105 | * SW3L-NB NB-IoT Distance Detection sensor x 1 | ||
1106 | |||
1107 | * External antenna x 1 | ||
1108 | |||
1109 | (% style="color:#037691" %)**Dimension and weight**: | ||
1110 | |||
1111 | * Device Size: 13.0 x 5 x 4.5 cm | ||
1112 | |||
1113 | * Device Weight: 150g | ||
1114 | |||
1115 | * Package Size / pcs : 14.0 x 8x 5 cm | ||
1116 | |||
1117 | * Weight / pcs : 180g | ||
1118 | |||
1119 | |||
1120 | |||
1121 | = 9. Support = | ||
1122 | |||
1123 | |||
1124 | * 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. | ||
1125 | |||
1126 | * 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]]. | ||
1127 | |||
1128 | (% style="display:none" %) (%%) |