Wiki source code of DS03A-NB -- NB-IoT Door Sensor User Manual
Last modified by Mengting Qiu on 2024/05/09 11:47
Show last authors
author | version | line-number | content |
---|---|---|---|
1 | (% style="text-align:center" %) | ||
2 | [[image:image-20231011093014-5.png]] | ||
3 | |||
4 | |||
5 | |||
6 | |||
7 | **Table of Contents:** | ||
8 | |||
9 | {{toc/}} | ||
10 | |||
11 | |||
12 | |||
13 | |||
14 | |||
15 | |||
16 | = 1. Introduction = | ||
17 | |||
18 | == 1.1 What is DS03A-NB NB-IoT Door Sensor == | ||
19 | |||
20 | |||
21 | The Dragino DS03A-NB is a (% style="color:blue" %) **NB-IoT Door Sensor**(%%) for Internet of Things solution. It (% style="color:blue" %)**detects door open/close status**(%%) and uplinks to IoT server via NB-IoT network. user can see the door status, open duration, open counts in the IoT Server. | ||
22 | |||
23 | The DS03A-NB will send periodically data every 2 hours as well as for each door open/close action. It also counts the door open times and calculates the last door open duration. Users can also disable the uplink for each open/close event, instead, DS03A-NB can count each open event and uplink periodically. | ||
24 | |||
25 | DS03A-NB supports (% style="color:blue" %)**Datalog Feature,** (%%)it can save the data when there is no NB-IoT network and uplink when network recover. | ||
26 | |||
27 | DS03A-NB has the (% style="color:blue" %)**Open Alarm Feature**,(%%) user can set this feature so the device will send an alarm if the door has been open for a certain time. | ||
28 | |||
29 | DS03A-NB is designed for outdoor use. It has a weatherproof enclosure and industrial level battery to work in low to high temperatures | ||
30 | |||
31 | DS03A-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 | DS03A-NB (% style="color:blue" %)**supports BLE configure **(%%)and(% style="color:blue" %)** OTA update**(%%) which make user easy to use. | ||
34 | |||
35 | DS03A-NB is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), it is designed for long-term use up to several years. | ||
36 | |||
37 | DS03A-NB has optional built-in SIM card and default IoT server connection version. Which makes it works with simple configuration. | ||
38 | |||
39 | [[image:image-20231011093807-6.png||height="278" width="879"]] | ||
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 | * Door Open/Close detect | ||
48 | * Door open/close statistics | ||
49 | * Datalog Feature | ||
50 | * Open Alarm Feature | ||
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 | * 8500mAh Battery for long term use | ||
56 | * Nano SIM card slot for NB-IoT SIM | ||
57 | (% style="display:none" %) (%%) | ||
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 | (% style="display:none" %) (%%) | ||
104 | |||
105 | == 1.4 Applications == | ||
106 | |||
107 | |||
108 | [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDS03A%20-%20Outdoor%20LoRaWAN%20OpenClose%20Door%20Sensor%20Manual/WebHome/1654741400370-813.png?rev=1.1||alt="1654741400370-813.png"]] | ||
109 | |||
110 | |||
111 | == 1.5 Sleep mode and working mode == | ||
112 | |||
113 | |||
114 | (% 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. | ||
115 | |||
116 | (% 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. | ||
117 | |||
118 | |||
119 | == 1.6 Button & LEDs == | ||
120 | |||
121 | |||
122 | [[image:Main.User Manual for LoRaWAN End Nodes.D20-LBD22-LBD23-LB_LoRaWAN_Temperature_Sensor_User_Manual.WebHome@1675071855856-879.png]] | ||
123 | |||
124 | |||
125 | (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) | ||
126 | |=(% 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** | ||
127 | |(% style="width:167px" %)Pressing ACT between 1s < time < 3s|(% style="width:117px" %)Send an uplink|(% style="width:225px" %)((( | ||
128 | If sensor has already attached to NB-IoT network, sensor will send an uplink packet, (% style="color:blue" %)**blue led** (%%)will blink once. | ||
129 | Meanwhile, BLE module will be active and user can connect via BLE to configure device. | ||
130 | ))) | ||
131 | |(% style="width:167px" %)Pressing ACT for more than 3s|(% style="width:117px" %)Active Device|(% style="width:225px" %)((( | ||
132 | (% 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. | ||
133 | (% style="color:green" %)**Green led**(%%) will solidly turn on for 5 seconds after joined in network. | ||
134 | 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. | ||
135 | ))) | ||
136 | |(% 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. | ||
137 | |||
138 | (% style="color:red" %)**Note: When the device is executing a program, the buttons may become invalid. It is best to press the buttons after the device has completed the program execution.** | ||
139 | |||
140 | |||
141 | == 1.7 BLE connection == | ||
142 | |||
143 | |||
144 | DS03A-NB support BLE remote configure and firmware update. | ||
145 | |||
146 | |||
147 | 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: | ||
148 | |||
149 | * Press button to send an uplink | ||
150 | * Press button to active device. | ||
151 | * Device Power on or reset. | ||
152 | |||
153 | If there is no activity connection on BLE in 60 seconds, sensor will shut down BLE module to enter low power mode. | ||
154 | |||
155 | |||
156 | == 1.8 Pin Definitions , Switch & SIM Direction == | ||
157 | |||
158 | |||
159 | [[image:image-20230819104805-5.png]] | ||
160 | |||
161 | |||
162 | === 1.8.1 Jumper JP2 === | ||
163 | |||
164 | |||
165 | Power on Device when put this jumper. | ||
166 | |||
167 | |||
168 | === 1.8.2 BOOT MODE / SW1 === | ||
169 | |||
170 | |||
171 | **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. | ||
172 | |||
173 | **2)** (% style="color:blue" %)**Flash**(%%): work mode, device starts to work and send out console output for further debug | ||
174 | |||
175 | |||
176 | === 1.8.3 Reset Button === | ||
177 | |||
178 | |||
179 | Press to reboot the device. | ||
180 | |||
181 | (% style="display:none" %) | ||
182 | |||
183 | |||
184 | === 1.8.4 SIM Card Direction === | ||
185 | |||
186 | |||
187 | See this link. [[How to insert SIM Card>>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]]. | ||
188 | |||
189 | |||
190 | == 1.9 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 | |||
200 | **Probe Mechanical:** | ||
201 | |||
202 | |||
203 | [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDS03A%20-%20Outdoor%20LoRaWAN%20OpenClose%20Door%20Sensor%20Manual/WebHome/1654741444887-479.png?width=513&height=399&rev=1.1||alt="1654741444887-479.png"]] | ||
204 | |||
205 | |||
206 | |||
207 | == 1.10 Magnet Distance == | ||
208 | |||
209 | |||
210 | * Wood Door: 10mm ~~ 30mm | ||
211 | * Iron Door: 30 ~~ 45mm | ||
212 | (% style="display:none" %) (%%) | ||
213 | |||
214 | = 2. Use DS03A-NB to communicate with IoT Server = | ||
215 | |||
216 | == 2.1 Send data to IoT server via NB-IoT network == | ||
217 | |||
218 | |||
219 | The DS03A-NB is equipped with a NB-IoT module, the pre-loaded firmware in DS03A-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 DS03A-NB. | ||
220 | |||
221 | |||
222 | Below shows the network structure: | ||
223 | |||
224 | [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/DS03A-NB_NB-IoT_Door_Sensor_User_Manual/WebHome/image-20231011093807-6.png?width=879&height=278&rev=1.1||alt="image-20231011093807-6.png"]] | ||
225 | |||
226 | |||
227 | There are two version: (% style="color:blue" %)**-GE**(%%) and (% style="color:blue" %)**-1D**(%%) version of DS03A-NB. | ||
228 | |||
229 | |||
230 | (% 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 DS03A-NB send data to IoT server. | ||
231 | |||
232 | * 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]]. | ||
233 | |||
234 | * 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]]. | ||
235 | |||
236 | Below shows result of different server as a glance. | ||
237 | |||
238 | (% border="1" cellspacing="4" style="width:515px" %) | ||
239 | |(% 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** | ||
240 | |(% 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" %)((( | ||
241 | (% style="text-align:center" %) | ||
242 | [[image:image-20230819113244-8.png||height="183" width="367"]] | ||
243 | )))|(% style="width:170px" %) | ||
244 | |(% 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" %)((( | ||
245 | (% style="text-align:center" %) | ||
246 | [[image:image-20230819113244-9.png||height="119" width="367"]] | ||
247 | )))|(% style="width:170px" %) | ||
248 | |(% 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" %) | ||
249 | |(% 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" %) | ||
250 | |(% 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" %) | ||
251 | |(% 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" %)((( | ||
252 | (% style="text-align:center" %) | ||
253 | [[image:image-20230819113244-10.png||height="104" width="367"]] | ||
254 | )))|(% style="width:170px" %) | ||
255 | |(% 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" %)((( | ||
256 | (% style="text-align:center" %) | ||
257 | [[image:image-20230819113244-11.png||height="141" width="367"]] | ||
258 | )))|(% style="width:170px" %) | ||
259 | |||
260 | (% 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 DS03A-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]]. | ||
261 | |||
262 | |||
263 | == 2.2 Payload Types == | ||
264 | |||
265 | |||
266 | To meet different server requirement, DS03A-NB supports different payload type. | ||
267 | |||
268 | **Includes:** | ||
269 | |||
270 | * [[General JSON format payload>>||anchor="H2.2.1GeneralJsonFormat28Type3D529"]]. (Type=5) | ||
271 | |||
272 | * [[HEX format Payload>>||anchor="H2.2.2HEXformatPayload28Type3D029"]]. (Type=0) | ||
273 | |||
274 | * [[ThingSpeak Format>>||anchor="H2.2.4ThingSpeakPayload28Type3D129"]]. (Type=1) | ||
275 | |||
276 | * [[ThingsBoard Format>>||anchor="H2.2.3ThingsBoardPayload28Type3D329"]]. (Type=3) | ||
277 | |||
278 | User can specify the payload type when choose the connection protocol. Example: | ||
279 | |||
280 | (% style="color:#037691" %)**AT+PRO=2,0** (%%) ~/~/ Use UDP Connection & hex Payload | ||
281 | |||
282 | (% style="color:#037691" %)**AT+PRO=2,5** (%%) ~/~/ Use UDP Connection & Json Payload | ||
283 | |||
284 | (% style="color:#037691" %)**AT+PRO=3,5 ** (%%) ~/~/ Use MQTT Connection & Json Payload | ||
285 | |||
286 | |||
287 | === 2.2.1 General Json Format(Type~=5) === | ||
288 | |||
289 | |||
290 | (% style="color:red" %)**This is the General Json Format. Payloads in General Json format for single-channel mode and double-channel mode have different byte lengths.** | ||
291 | |||
292 | |||
293 | **The General Json format payload for the single-channel mode is as follows:** | ||
294 | |||
295 | (% style="color:#4472c4" %)**{"IMEI":"866207052559857","Model":"DS03A-NB","level status":1,"alarm status":0,"door open num":0,"last open time":0,"level status2":1,"alarm status2":0,"door open num2":0,"last open time2":0,"battery":3.48,"signal":24,"1":{1,0,0,2023/11/13 09:59:01},"2":{0,0,261,2023/11/13 03:20:00},"3":{237,9896971,263,2023/11/13 03:05:00},"4":{0,29,263,2023/11/13 02:20:12},"5":{215,9897015,268,2023/11/13 01:58:16},"6":{0,79,261,2023/11/13 01:43:16},"7":{227,9896991,5368540,2023/11/13 01:18:46},"8":{0,19,5367640,2023/11/11 08:53:57}}** | ||
296 | |||
297 | [[image:image-20231115162221-7.png]] | ||
298 | |||
299 | |||
300 | **The General Json format payload for the double-channel mode is as follows:** | ||
301 | |||
302 | (% style="color:#4472c4" %)**{"IMEI":"866207058378443","Model":"DS03A-NB","level status":1,"alarm status":0,"door open num":2,"last open time":0,"level status2":1,"alarm status2":0,"door open num2":3,"last open time2":0,"battery":3.39,"signal":25,"1":{1,4,0,1,3,0,2023/11/15 07:54:30},"2":{1,3,0,1,6,1,2023/11/15 07:10:04},"3":{0,0,0,1,1,0,2023/11/15 06:55:04},"4":{0,0,0,1,0,0,2023/11/15 06:40:04},"5":{0,0,0,1,0,0,2023/11/15 03:50:36},"6":{0,0,0,1,4,11,2023/11/15 03:28:16},"7":{0,0,0,1,4,11,2023/11/15 03:13:16},"8":{0,0,0,1,3,11,2023/11/15 02:58:25}}** | ||
303 | |||
304 | [[image:image-20231115161803-6.png]] | ||
305 | |||
306 | |||
307 | (% style="color:red" %)**Notice, from above payload:** | ||
308 | |||
309 | * level status, alarm status, door open num, last open time, level status2, alarm status2, door open sum2, last open time2, Battery & Signal are the value at uplink time. | ||
310 | |||
311 | * 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): | ||
312 | |||
313 | Single-channel mode: level status, door open num, last open time, Sampling time. | ||
314 | |||
315 | Double-channel mode: level status, door open num, last open time, level status2, door open sum2, last open time2, Sampling time. | ||
316 | |||
317 | |||
318 | |||
319 | === 2.2.2 HEX format Payload(Type~=0) === | ||
320 | |||
321 | |||
322 | (% style="color:red" %)**This is the HEX Format. Payloads in HEX format for single-channel mode and double-channel mode have different byte lengths.** | ||
323 | |||
324 | |||
325 | **The HEX format payload for the single-channel mode is as follows:** | ||
326 | |||
327 | (% style="color:#4472c4" %)**f86620705255985712640d9c180101000000000000006551f424010000000000006551f36500000000000105655195e0ed97040b0001076551925c0000001d000107655187dcd797043700010c655182b80000004f00010565517f34e397041f51eadc655179760000001351e758654f4125** | ||
328 | |||
329 | [[image:image-20231114091247-2.png||height="186" width="1363"]] | ||
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-20231114094432-3.png]] | ||
335 | |||
336 | |||
337 | |||
338 | **The HEX format payload for the double-channel mode is as follows:** | ||
339 | |||
340 | (% style="color:#4472c4" %)**f86620705255985712640db71701010000000000000001000000000000006552d13401000000000000000000000000006551f365000000000001050000005f00005f655195e0ed97040b0001070000005c00005c6551925c0000001d00010700000033000033655187dcd797043700010c00000033000033655182b80000004f0001050000003300003365517f34e397041f51eadc00000000000000655179760000001351e75800000000000000654f4125** | ||
341 | |||
342 | [[image:image-20231114091229-1.png||height="180" width="1584"]] | ||
343 | |||
344 | |||
345 | If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. | ||
346 | |||
347 | [[image:image-20231114094838-5.png]] | ||
348 | |||
349 | |||
350 | (% style="color:blue" %)**Version:** | ||
351 | |||
352 | These bytes include the hardware and software version. | ||
353 | |||
354 | (% style="color:#037691" %)**Higher byte:**(%%) Specify Sensor Model: 0x12 for DS03A-NB | ||
355 | |||
356 | (% style="color:#037691" %)**Lower byte:**(%%) Specify the software version: 0x64=100, means firmware version 1.0.0 | ||
357 | |||
358 | |||
359 | (% style="color:blue" %)**BAT (Battery Info):** | ||
360 | |||
361 | Ex1: 0x0dda = 3546mV | ||
362 | |||
363 | |||
364 | (% style="color:blue" %)**Signal Strength:** | ||
365 | |||
366 | NB-IoT Network signal Strength. | ||
367 | |||
368 | **Ex1: 0x15 = 21** | ||
369 | |||
370 | **0** -113dBm or less | ||
371 | |||
372 | **1** -111dBm | ||
373 | |||
374 | **2...30** -109dBm... -53dBm | ||
375 | |||
376 | **31** -51dBm or greater | ||
377 | |||
378 | **99** Not known or not detectable | ||
379 | |||
380 | |||
381 | (% style="color:blue" %)**Timestamp: ** | ||
382 | |||
383 | Unit Timestamp Example: 650abc40(H) = 1695202368(D) | ||
384 | |||
385 | Put the decimal value into this link([[https:~~/~~/www.epochconverter.com)>>https://www.epochconverter.com]]) to get the time. | ||
386 | |||
387 | |||
388 | === 2.2.3 ThingsBoard Payload(Type~=3) === | ||
389 | |||
390 | |||
391 | Type3 payload special design for ThingsBoard, it will also configure other default server to ThingsBoard. | ||
392 | |||
393 | (% style="color:#4472c4" %)**{ | ||
394 | "IMEI": "866207058378443", | ||
395 | "Model": "DS03A-NB", | ||
396 | "level status": 1, | ||
397 | "alarm status": 0, | ||
398 | "door open num": 6, | ||
399 | "last open time": 1, | ||
400 | "level status2": 1, | ||
401 | "alarm status2": 0, | ||
402 | "door open num2": 2, | ||
403 | "last open time2": 0, | ||
404 | "battery": 3.4, | ||
405 | "signal": 24 | ||
406 | }** | ||
407 | |||
408 | [[image:image-20231115150948-1.png||height="625" width="1188"]] | ||
409 | |||
410 | |||
411 | === 2.2.4 ThingSpeak Payload(Type~=1) === | ||
412 | |||
413 | |||
414 | This payload meets ThingSpeak platform requirement. It includes eight fields. Form 1~~8 are: | ||
415 | |||
416 | Distance, Battery & Signal. This payload type only valid for ThingsSpeak Platform | ||
417 | |||
418 | As below: | ||
419 | |||
420 | (% style="color:#4472c4" %)**field1=Flow value&field2=Battery value&field3=signal value** | ||
421 | |||
422 | [[image:image-20231115154757-2.png]] | ||
423 | |||
424 | [[image:image-20231115154821-3.png||height="695" width="1119"]] | ||
425 | |||
426 | |||
427 | |||
428 | == 2.3 Test Uplink and Change Update Interval == | ||
429 | |||
430 | |||
431 | By default, Sensor will send uplinks (% style="color:blue" %)**every 2 hours**(%%) & AT+NOUD=8 | ||
432 | |||
433 | User can use below commands to change the (% style="color:blue" %)**uplink interval**. | ||
434 | |||
435 | (% style="color:#037691" %)**AT+TDC=600 ** (%%) ~/~/ Set Update Interval to 600s | ||
436 | |||
437 | User can also push the button for more than 1 seconds to activate an uplink. | ||
438 | |||
439 | |||
440 | == 2.4 Multi-Samplings and One uplink == | ||
441 | |||
442 | (% style="color:red" %)Notice: The AT+NOUD feature is upgraded to Clock Logging, please refer [[Clock Logging Feature>>||anchor="H2.14Clocklogging28Sincefirmwareversionv1.2.129"]] | ||
443 | |||
444 | To save battery life, DS03A-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: | ||
445 | |||
446 | * (% 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) | ||
447 | |||
448 | * (% 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. | ||
449 | |||
450 | The diagram below explains the relationship between TR, NOUD, and TDC more clearly: | ||
451 | |||
452 | [[image:1692424376354-959.png]] | ||
453 | |||
454 | |||
455 | == 2.5 Trggier an uplink by external interrupt == | ||
456 | |||
457 | |||
458 | DS03A-NB has an external trigger interrupt function. Users can use the PB15 pin to trigger the upload of data packets. | ||
459 | |||
460 | (% style="color:blue" %)**AT command:** | ||
461 | |||
462 | * (% style="color:#037691" %)**AT+INTMOD **(%%) ~/~/ Set the trigger interrupt mode | ||
463 | |||
464 | * (% style="color:#037691" %)**AT+INTMOD=0 **(%%) ~/~/ Disable Interrupt | ||
465 | |||
466 | * (% style="color:#037691" %)**AT+INTMOD=1 **(%%) ~/~/ Trigger by rising and falling edge | ||
467 | |||
468 | * (% style="color:#037691" %)**AT+INTMOD=2 **(%%) ~/~/ Trigger by falling edge | ||
469 | |||
470 | * (% style="color:#037691" %)**AT+INTMOD=3 **(%%) ~/~/ Trigger by rising edge | ||
471 | (% style="display:none" %) (%%) | ||
472 | |||
473 | == 2.5 Set Transmit Interval Time == | ||
474 | |||
475 | |||
476 | ((( | ||
477 | Feature: Change NB-IoT End Node Transmit Interval. | ||
478 | ))) | ||
479 | |||
480 | ((( | ||
481 | (% style="color:blue" %)**AT Command: AT+TDC** | ||
482 | ))) | ||
483 | |||
484 | (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) | ||
485 | |=(% 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** | ||
486 | |(% style="width:156px" %)AT+TDC=?|(% style="width:137px" %)Show current transmit Interval|((( | ||
487 | 30000 | ||
488 | OK | ||
489 | the interval is 30000ms = 30s | ||
490 | ))) | ||
491 | |(% style="width:156px" %)AT+TDC=60000|(% style="width:137px" %)Set Transmit Interval|((( | ||
492 | OK | ||
493 | Set transmit interval to 60000ms = 60 seconds | ||
494 | ))) | ||
495 | |||
496 | ((( | ||
497 | (% style="color:blue" %)**Downlink Command: 0x01** | ||
498 | ))) | ||
499 | |||
500 | ((( | ||
501 | Format: Command Code (0x01) followed by 3 bytes time value. | ||
502 | ))) | ||
503 | |||
504 | ((( | ||
505 | If the downlink payload=0100003C, it means set the END Node's Transmit Interval to 0x00003C=60(S), while type code is 01. | ||
506 | ))) | ||
507 | |||
508 | * ((( | ||
509 | Example 1: Downlink Payload: 0100001E ~/~/ Set Transmit Interval (TDC) = 30 seconds | ||
510 | ))) | ||
511 | * ((( | ||
512 | Example 2: Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds | ||
513 | )))(% style="display:none" %) (%%) | ||
514 | |||
515 | == 2.7 Enable / Disable Alarm == | ||
516 | |||
517 | |||
518 | Feature: Enable/Disable Alarm for open/close event. Default value 0. | ||
519 | |||
520 | (% style="color:blue" %)**AT Command: ** | ||
521 | |||
522 | (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %) | ||
523 | |(% style="background-color:#4f81bd; color:white; width:153px" %)**Command Example**|(% style="background-color:#4f81bd; color:white; width:276px" %)**Function**|(% style="background-color:#4f81bd; color:white; width:86px" %)**Response** | ||
524 | |(% style="width:154px" %)AT+DISALARM=1|(% style="width:278px" %)End node will only send packets in TDC time.|OK | ||
525 | |(% style="width:154px" %)AT+DISALARM=0|(% style="width:278px" %)End node will send packets in TDC time or status change for door sensor|OK | ||
526 | |||
527 | (% style="color:blue" %)**Downlink Command: ** | ||
528 | |||
529 | 0xA7 01 ~/~/ Same As AT+DISALARM=1 | ||
530 | |||
531 | 0xA7 00 ~/~/ Same As AT+DISALARM=0 | ||
532 | |||
533 | |||
534 | == 2.8 Alarm Base on Timeout == | ||
535 | |||
536 | |||
537 | DS03A-NB can monitor the timeout for a status change, this feature can be used to monitor some events such as door opening too long etc. Related Parameters are: | ||
538 | |||
539 | * ((( | ||
540 | (% style="color:blue" %)**Keep Status: Status to be monitor** | ||
541 | ))) | ||
542 | |||
543 | (% style="color:#037691" %)**Keep Status = 1**(%%): Monitor Close to Open event | ||
544 | |||
545 | (% style="color:#037691" %)**Keep Status = 0**(%%): Monitor Open to Close event | ||
546 | |||
547 | |||
548 | * ((( | ||
549 | (% style="color:blue" %)**Keep Time: Timeout to send an Alarm** | ||
550 | ))) | ||
551 | |||
552 | Range 0 ~~ 65535(0xFFFF) seconds. | ||
553 | |||
554 | If (% style="color:#037691" %)**keep time = 0**(%%), Disable Alarm Base on Timeout feature. | ||
555 | |||
556 | If (% style="color:#037691" %)**keep time > 0**(%%), device will monitor the keep status event and send an alarm when status doesn't change after timeout. | ||
557 | |||
558 | |||
559 | * ((( | ||
560 | (% style="color:blue" %)**Downlink Command** | ||
561 | ))) | ||
562 | |||
563 | (% style="color:#037691" %)**Command: 0xA9 aa bb cc dd** | ||
564 | |||
565 | **A9:** Command Type Code | ||
566 | |||
567 | **aa: **01:TTRIG1; 02:TTRIG2 | ||
568 | |||
569 | **bb:** status to be monitored | ||
570 | |||
571 | **cc dd:** timeout. | ||
572 | |||
573 | |||
574 | **1) AT+TTRIG1 : (PA8 of pin)** | ||
575 | |||
576 | (% style="color:blue" %)**AT Command to configure:** | ||
577 | |||
578 | * ((( | ||
579 | (% style="color:#037691" %)**AT+TTRIG1=1,30** (%%) **~-~->** When the **Keep Status** change from close to open, and device remains in open status for more than 30 seconds. DS03A-NB will send an uplink packet, the Alarm1 bit(the second bit of 1^^st^^ byte of payload) on this uplink packet is set to 1. | ||
580 | |||
581 | (% style="color:#037691" %)**AT+TTRIG1=0,30** (%%) **~-~->** When the **Keep Status** change from open to close, and device remains in open status for more than 30 seconds. DS03A-NB will send an uplink packet, the Alarm1 bit (the second bit of 1^^st^^ byte of payload) on this uplink packet is set to 1. | ||
582 | ))) | ||
583 | |||
584 | * ((( | ||
585 | (% style="color:#037691" %)**AT+TTRIG1=0,0** (%%) **~-~-> ** Default Value, disable timeout Alarm. | ||
586 | |||
587 | |||
588 | ))) | ||
589 | |||
590 | (% style="color:blue" %)**Downlink Command to configure:** | ||
591 | |||
592 | If user send 0xA9 01 01 00 1E: equal to AT+TTRIG1=1,30 **or** 0xA9 01 00 00 00: Equal to AT+TTRIG1=0,0. | ||
593 | |||
594 | |||
595 | **2) AT+TTRIG2 : (PA4 of pin,need to use AT+TTRCHANNEL=2)** | ||
596 | |||
597 | (% style="color:blue" %)**AT Command to configure:** | ||
598 | |||
599 | * ((( | ||
600 | (% style="color:#037691" %)**AT+TTRIG2=1,30** (%%) **~-~->** When the **Keep Status** change from close to open, and device remains in open status for more than 30 seconds. DS03A-NB will send an uplink packet, the Alarm2 bit (the second bit of 12^^st^^ byte of payload) on this uplink packet is set to 1. | ||
601 | |||
602 | (% style="color:#037691" %)**AT+TTRIG2=0,30** (%%) **~-~->** When the **Keep Status** change from open to close, and device remains in open status for more than 30 seconds. DS03A-NB will send an uplink packet, the Alarm2 bit (the second bit of 12^^st^^ byte of payload) on this uplink packet is set to 1. | ||
603 | ))) | ||
604 | |||
605 | * ((( | ||
606 | (% style="color:#037691" %)**AT+TTRIG2=0,0** (%%) **~-~-> ** Default Value, disable timeout Alarm. | ||
607 | |||
608 | |||
609 | ))) | ||
610 | |||
611 | (% style="color:blue" %)**Downlink Command to configure:** | ||
612 | |||
613 | If user send 0xA9 02 00 00 1E: equal to AT+TTRIG2=0,30 **or** 0xA9 02 00 00 00: Equal to AT+TTRIG2=0,0. | ||
614 | |||
615 | |||
616 | == 2.9 TTRIG1 & TTRIG2 timeout status alarm == | ||
617 | |||
618 | |||
619 | It needs to be used with AT+TTRIG1 or AT+TTRIG2. When TTRIG1 or TTRIG2 times out and causes an alarm, and the status does not change subsequently, an alarm packet will be sent at the alarm interval. | ||
620 | |||
621 | (% style="color:blue" %)**AT Command:** | ||
622 | |||
623 | (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) | ||
624 | |=(% style="width: 155px;background-color:#4F81BD;color:white" %)**Command Example**|=(% style="width: 279px;background-color:#4F81BD;color:white" %)**Function**|=(% style="width: 76px;background-color:#4F81BD;color:white" %)**Response** | ||
625 | |(% style="width:155px" %)((( | ||
626 | AT+TTRALARM=0 | ||
627 | )))|(% style="width:279px" %)((( | ||
628 | disable continuous alarm | ||
629 | )))|(% style="width:84px" %)((( | ||
630 | OK | ||
631 | ))) | ||
632 | |(% style="width:155px" %)((( | ||
633 | AT+TTRALARM=60 | ||
634 | )))|(% style="width:279px" %)((( | ||
635 | The alarm interval is 60 minutes (unit: minutes) | ||
636 | )))|(% style="width:84px" %)((( | ||
637 | OK | ||
638 | ))) | ||
639 | |||
640 | (% style="color:blue" %)**Downlink Command:** | ||
641 | |||
642 | Example: 0C aa => AT+TTRALARM= aa | ||
643 | |||
644 | |||
645 | == 2.10 Count Mod == | ||
646 | |||
647 | |||
648 | Feature: Manually set the count mode. | ||
649 | |||
650 | (% style="color:blue" %)**AT Command:** | ||
651 | |||
652 | (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %) | ||
653 | |=(% style="width: 154px;background-color:#4F81BD;color:white" %)**Command Example**|=(% style="width: 275px;background-color:#4F81BD;color:white" %)**Function**|=(% style="width: 86px;background-color:#4F81BD;color:white" %)**Response** | ||
654 | |(% style="width:155px" %)((( | ||
655 | AT+COUNTMOD=0 | ||
656 | )))|(% style="width:277px" %)((( | ||
657 | the count value keeps accumulating mode | ||
658 | )))|(% style="width:86px" %)((( | ||
659 | OK | ||
660 | ))) | ||
661 | |(% style="width:155px" %)((( | ||
662 | AT+COUNTMOD=1 | ||
663 | )))|(% style="width:277px" %)((( | ||
664 | the count value will be reset after each TDC time(Last Close Duration Reset after each uplink) | ||
665 | )))|(% style="width:86px" %)((( | ||
666 | OK | ||
667 | ))) | ||
668 | |||
669 | (% style="color:blue" %)**Downlink Command:** | ||
670 | |||
671 | Example: 0B aa => AT+COUNTMOD = second byte | ||
672 | |||
673 | |||
674 | == 2.11 Number of channel of door sensors == | ||
675 | |||
676 | |||
677 | Feature: Set the number of door sensor channels. | ||
678 | |||
679 | (% style="color:blue" %)**AT Command:** | ||
680 | |||
681 | (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:500px" %) | ||
682 | |=(% style="width: 155px;background-color:#4F81BD;color:white" %)**Command Example**|=(% style="width: 288px; background-color:#4F81BD;color:white" %)**Function**|=(% style="width: 57px;background-color:#4F81BD;color:white" %)**Response** | ||
683 | |(% style="width:155px" %)((( | ||
684 | AT+TTRCHANNEL=1 | ||
685 | )))|(% style="width:259px" %)((( | ||
686 | Set as single channel, only use PA8 pin as interrupt pin. | ||
687 | )))|(% style="width:44px" %)((( | ||
688 | OK | ||
689 | ))) | ||
690 | |(% style="width:155px" %)((( | ||
691 | AT+TTRCHANNEL=2 | ||
692 | )))|(% style="width:259px" %)((( | ||
693 | Set as dual channel, use PA8 pin and PA4 pin as interrupt pin. | ||
694 | )))|(% style="width:44px" %)((( | ||
695 | OK | ||
696 | ))) | ||
697 | |||
698 | (% style="color:blue" %)**Downlink Command:** | ||
699 | |||
700 | Example: 0D aa => AT+TTRCHANNEL = second byte | ||
701 | |||
702 | |||
703 | == 2.12 Clear the open door times and the duration of the last open door == | ||
704 | |||
705 | |||
706 | (% style="color:blue" %)**AT Command:** | ||
707 | |||
708 | (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) | ||
709 | |=(% style="width: 163px;background-color:#4F81BD;color:white" %)**Command Example**|=(% style="width: 290px; background-color:#4F81BD;color:white" %)**Function**|=(% style="width: 57px;background-color:#4F81BD;color:white" %)**Response** | ||
710 | |(% style="width:155px" %)AT+CLRC|(% style="width:259px" %)clear the open door times and the duration of the last open door.|(% style="width:44px" %)((( | ||
711 | OK | ||
712 | ))) | ||
713 | |||
714 | (% style="color:blue" %)**Downlink Command:**(%%)0xA6 01 | ||
715 | |||
716 | The sensor will clear the open door times and the duration of the last open door. | ||
717 | |||
718 | |||
719 | == 2.13 Set the count value of the number of open door == | ||
720 | |||
721 | |||
722 | (% style="color:blue" %)**AT Command:** | ||
723 | |||
724 | (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:500px" %) | ||
725 | |=(% style="width: 155px;background-color:#4F81BD;color:white" %)**Command Example**|=(% style="width: 288px; background-color:#4F81BD;color:white" %)**Function**|=(% style="width: 57px;background-color:#4F81BD;color:white" %)**Response** | ||
726 | |(% style="width:155px" %)((( | ||
727 | AT+SETCNT=1,100 | ||
728 | )))|(% style="width:259px" %)((( | ||
729 | Set the open door times of PA8 pin to 100 times. | ||
730 | )))|(% style="width:44px" %)((( | ||
731 | OK | ||
732 | ))) | ||
733 | |(% style="width:155px" %)AT+SETCNT=1,0|(% style="width:259px" %)Clear the open door times of PA8 pin.|(% style="width:44px" %)OK | ||
734 | |(% style="width:155px" %)((( | ||
735 | AT+SETCNT=2,50 | ||
736 | )))|(% style="width:259px" %)((( | ||
737 | Set the open door times of PA4 pin to 100 times. | ||
738 | )))|(% style="width:44px" %)((( | ||
739 | OK | ||
740 | ))) | ||
741 | |||
742 | (% style="color:blue" %)**Downlink Command:** | ||
743 | |||
744 | 0xA6 01 00 00 64 ==> AT+SETCNT=1,100 | ||
745 | |||
746 | 0xA6 01 00 00 00 ==> AT+SETCNT=1,0 | ||
747 | |||
748 | 0xA6 02 00 00 32 ==> AT+SETCNT=2,50 | ||
749 | |||
750 | |||
751 | == 2.14 Clock logging (Since firmware version v1.2.1) == | ||
752 | |||
753 | |||
754 | Sometimes when we deploy lots of end nodes in field. We want all sensors sample data at the same time, and upload these data together for analyze. In such case, we can use clock loging feature. | ||
755 | |||
756 | We can use this command to set the start time of data recording and the time interval to meet the requirements of the specific collection time of data. | ||
757 | |||
758 | * (% style="color:blue" %)**AT Command: AT+CLOCKLOG=a,b,c,d** | ||
759 | |||
760 | (% style="color:blue" %)**a:**(%%)** 0:** Disable Clock logging. ** 1: **Enable Clock Logging | ||
761 | |||
762 | (% style="color:blue" %)**b:**(%%)** **Specify First sampling start second: range **(0 ~~ 3599, 65535) ** ~/~/ (% style="color:red" %)**Note:**(%%)** **If parameter b is set to 65535, the log period starts after the node accesses the network and sends packets. | ||
763 | |||
764 | (% style="color:blue" %)**c:**(%%)** **Specify the sampling interval: range **(0 ~~ 255 minutes)** | ||
765 | |||
766 | (% style="color:blue" %)**d:**(%%)** **How many entries should be uplink on every TDC **(max 32)** | ||
767 | |||
768 | [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/SPH01-NB_NB-IoT_Soil_pH_Sensor_User_Manual/WebHome/image-20240315141254-1.png?rev=1.1||alt="image-20240315141254-1.png"]] | ||
769 | |||
770 | **Example:** | ||
771 | |||
772 | **AT+CLOCKLOG=1,65535,1,5** | ||
773 | |||
774 | After the node sends the first packet, data is recorded to the memory at intervals of 1 minute. For each TDC uplink, the uplink load will include: battery information + the last 5 memory records (payload + timestamp). | ||
775 | |||
776 | (% class="wikigeneratedid" %) | ||
777 | [[image:image-20240316150911-1.png||height="493" width="1144"]] | ||
778 | |||
779 | (% class="wikigeneratedid" %) | ||
780 | (% style="color:red" %)**Note: Users need to synchronize the server time before configuring this command. If the server time is not synchronized before this command is configured, the command takes effect only after the node is reset.** | ||
781 | |||
782 | |||
783 | == 2.15 Example Query saved historical records == | ||
784 | |||
785 | |||
786 | * (% style="color:blue" %)**AT Command: AT+CDP** | ||
787 | |||
788 | This command can be used to search the saved history, recording up to 32 groups of data, each group of historical data contains a maximum of 100 bytes. | ||
789 | |||
790 | (% class="wikigeneratedid" %) | ||
791 | [[image:image-20240316151014-2.png||height="632" width="825"]] | ||
792 | |||
793 | |||
794 | == 2.16 Uplink log query == | ||
795 | |||
796 | |||
797 | * (% style="color:blue" %)**AT Command: AT+GETLOG** | ||
798 | |||
799 | This command can be used to query upstream logs of data packets. | ||
800 | |||
801 | [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/PS-NB-NA_NB-IoT_Analog_Sensor_User_Manual/WebHome/image-20240407191922-2.png?width=903&height=631&rev=1.1||alt="image-20240407191922-2.png"]] | ||
802 | |||
803 | |||
804 | |||
805 | |||
806 | = 3. Configure DS03A-NB = | ||
807 | |||
808 | == 3.1 Configure Methods == | ||
809 | |||
810 | |||
811 | DS03A-NB supports below configure method: | ||
812 | |||
813 | * AT Command via Bluetooth Connection (**Recommended**): [[BLE Configure Instruction>>http://wiki.dragino.com/xwiki/bin/view/Main/BLE%20Bluetooth%20Remote%20Configure/]]. | ||
814 | |||
815 | * 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]]. | ||
816 | (% style="display:none" %) (%%) | ||
817 | |||
818 | == 3.2 AT Commands Set == | ||
819 | |||
820 | |||
821 | AT+<CMD>? : Help on <CMD> | ||
822 | |||
823 | AT+<CMD> : Run <CMD> | ||
824 | |||
825 | AT+<CMD>=<value> : Set the value | ||
826 | |||
827 | AT+<CMD>=? : Get the value | ||
828 | |||
829 | |||
830 | (% style="color:blue" %)**General Commands** | ||
831 | |||
832 | AT : Attention | ||
833 | |||
834 | AT? : Short Help | ||
835 | |||
836 | ATZ : MCU Reset | ||
837 | |||
838 | AT+TDC : Application Data Transmission Interval | ||
839 | |||
840 | AT+CFG : Print all configurations | ||
841 | |||
842 | AT+CFGMOD : Working mode selection | ||
843 | |||
844 | AT+DEUI : Get or set the Device ID | ||
845 | |||
846 | AT+INTMOD : Set the trigger interrupt mode | ||
847 | |||
848 | AT+5VT : Set extend the time of 5V power | ||
849 | |||
850 | AT+PRO : Choose agreement | ||
851 | |||
852 | AT+RXDL : Extend the sending and receiving time | ||
853 | |||
854 | AT+DNSCFG : Get or Set DNS Server | ||
855 | |||
856 | AT+GETSENSORVALUE : Returns the current sensor measurement | ||
857 | |||
858 | AT+NOUD : Get or Set the number of data to be uploaded | ||
859 | |||
860 | AT+CDP : Read or Clear cached data | ||
861 | |||
862 | AT+SHTEMP: Get or Set alarm of temp | ||
863 | |||
864 | AT+SHHUM: Get or Set alarm of moisture | ||
865 | |||
866 | AT+SERVADDR : Server Address | ||
867 | |||
868 | |||
869 | (% style="color:blue" %)**MQTT Management** | ||
870 | |||
871 | AT+CLIENT : Get or Set MQTT client | ||
872 | |||
873 | AT+UNAME : Get or Set MQTT Username | ||
874 | |||
875 | AT+PWD : Get or Set MQTT password | ||
876 | |||
877 | AT+PUBTOPIC : Get or Set MQTT publish topic | ||
878 | |||
879 | AT+SUBTOPIC : Get or Set MQTT subscription topic | ||
880 | |||
881 | |||
882 | (% style="color:blue" %)**Information** | ||
883 | |||
884 | AT+FDR : Factory Data Reset | ||
885 | |||
886 | AT+PWORD : Serial Access Password | ||
887 | |||
888 | AT+LDATA : Get the last upload data | ||
889 | |||
890 | AT+CDP : Read or Clear cached data | ||
891 | |||
892 | |||
893 | = 4. Battery & Power Consumption = | ||
894 | |||
895 | |||
896 | DS03A-NB use ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace. | ||
897 | |||
898 | [[**Battery Info & Power Consumption Analyze**>>http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] . | ||
899 | |||
900 | |||
901 | = 5. Firmware update = | ||
902 | |||
903 | |||
904 | User can change device firmware to:: | ||
905 | |||
906 | * Update with new features. | ||
907 | |||
908 | * Fix bugs. | ||
909 | |||
910 | Firmware and changelog can be downloaded from : **[[Firmware download link>>https://www.dropbox.com/sh/zbsm9p4coksqwd5/AADy2ZJc39KsvfbhTMCUGmz1a?dl=0]]** | ||
911 | |||
912 | Methods to Update Firmware: | ||
913 | |||
914 | * (Recommended way) OTA firmware update via BLE: [[**Instruction**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/BLE_Firmware_Update_NB_Sensors_BC660K-GL/]]. | ||
915 | |||
916 | * Update through UART TTL interface : **[[Instruction>>http://wiki.dragino.com/xwiki/bin/view/Main/UART_Access_for_NB_ST_BC660K-GL/#H4.2UpdateFirmware28Assumethedevicealreadyhaveabootloader29]]**. | ||
917 | (% style="display:none" %) (%%) | ||
918 | |||
919 | = 6. FAQ = | ||
920 | |||
921 | == 6.1 How can I access t BC660K-GL AT Commands? == | ||
922 | |||
923 | |||
924 | User can access to BC660K-GL directly and send AT Commands. | ||
925 | |||
926 | [[See BC660K-GL AT Command set>>url:https://www.dropbox.com/sh/5f6ssda5fum8rvs/AABT68l8ZzWOvZ5eg2qwOoFda?dl=0]] | ||
927 | |||
928 | |||
929 | = 7. Order Info = | ||
930 | |||
931 | |||
932 | Part Number: (% style="color:blue" %)**DS03A-NB-XX** | ||
933 | |||
934 | (% style="color:red" %)**XX**(%%): | ||
935 | |||
936 | * (% style="color:#037691" %)**GE**(%%): General version ( Exclude SIM card) | ||
937 | |||
938 | * (% style="color:#037691" %)**1D**(%%): with 1NCE* 10 years 500MB SIM card and Pre-configure to DataCake server | ||
939 | |||
940 | (% 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 | ||
941 | |||
942 | |||
943 | = 8. Packing Info = | ||
944 | |||
945 | |||
946 | (% style="color:#037691" %)**Package Includes**: | ||
947 | |||
948 | * DS03A-NB NB-IoT Door sensor x 1 | ||
949 | |||
950 | * External antenna x 1 | ||
951 | |||
952 | (% style="color:#037691" %)**Dimension and weight**: | ||
953 | |||
954 | * Device Size: 13.0 x 5 x 4.5 cm | ||
955 | |||
956 | * Device Weight: 150g | ||
957 | |||
958 | * Package Size / pcs : 14.0 x 8x 5 cm | ||
959 | |||
960 | * Weight / pcs : 180g | ||
961 | (% style="display:none" %) (%%) | ||
962 | |||
963 | = 9. Support = | ||
964 | |||
965 | |||
966 | * 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. | ||
967 | |||
968 | * 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]]. | ||
969 | |||
970 | (% style="display:none" %) (%%) |