Wiki source code of PS-NB -- NB-IoT Air/Water Pressure Sensor User Manual
Last modified by Mengting Qiu on 2024/05/09 10:19
Show last authors
author | version | line-number | content |
---|---|---|---|
1 | [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/PS-LB%20--%20LoRaWAN%20Pressure%20Sensor/WebHome/image-20231120111226-4.png?rev=1.1||alt="image-20231120111226-4.png"]] | ||
2 | |||
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 NB-IoT Pressure Sensor == | ||
19 | |||
20 | |||
21 | The Dragino PS-NB series sensors are (% style="color:blue" %)**NB-IoT Pressure Sensor**(%%) for Internet of Things solution. PS-NB can (% style="color:blue" %)**measure Air, Water pressure and liquid level**(%%) and upload the sensor data send to IoT platform via NB-IoT network. | ||
22 | |||
23 | The PS-NB series sensors include (% style="color:blue" %)**Thread Installation Type and Immersion Type**(%%), it supports (% style="color:blue" %)**different pressure range**(%%) which can be used for different measurement requirement. | ||
24 | |||
25 | PS-NB supports different uplink methods including (% style="color:blue" %)**MQTT, MQTTs, UDP & TCP**(%%) for different application requirement, and support uplinks to various IoT Servers. | ||
26 | |||
27 | PS-NB (% style="color:blue" %)**supports BLE configure **(%%)and(% style="color:blue" %)** OTA update**(%%) which make user easy to use. | ||
28 | |||
29 | PS-NB is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), it is designed for long-term use up to several years. | ||
30 | |||
31 | PS-NB has optional built-in SIM card and default IoT server connection version. Which makes it works with simple configuration. | ||
32 | |||
33 | [[image:image-20230911092301-6.png||height="296" width="921"]] | ||
34 | |||
35 | |||
36 | == 1.2 Features == | ||
37 | |||
38 | |||
39 | * NB-IoT Bands: B1/B2/B3/B4/B5/B8/B12/B13/B17/B18/B19/B20/B25/B28/B66/B70/B85 @H-FDD | ||
40 | * Ultra-low power consumption | ||
41 | * Measure air / gas or water pressure | ||
42 | * Different pressure range available | ||
43 | * Thread Installation Type or Immersion Type | ||
44 | * Multiply Sampling and one uplink | ||
45 | * Support Bluetooth v5.1 remote configure and update firmware | ||
46 | * Uplink on periodically | ||
47 | * Downlink to change configure | ||
48 | * 8500mAh Battery for long term use | ||
49 | * IP66 Waterproof Enclosure | ||
50 | * Uplink via MQTT, MQTTs, TCP, or UDP | ||
51 | * Nano SIM card slot for NB-IoT SIM | ||
52 | |||
53 | == 1.3 Specification == | ||
54 | |||
55 | |||
56 | (% style="color:blue" %)**Common DC Characteristics:** | ||
57 | |||
58 | * Supply Voltage: 2.5v ~~ 3.6v | ||
59 | * Operating Temperature: -40 ~~ 85°C | ||
60 | |||
61 | (% style="color:blue" %)**Current Input (DC) Measuring :** | ||
62 | |||
63 | * Range: 0 ~~ 20mA | ||
64 | * Accuracy: 0.02mA | ||
65 | * Resolution: 0.001mA | ||
66 | |||
67 | (% style="color:blue" %)**Voltage Input Measuring:** | ||
68 | |||
69 | * Range: 0 ~~ 30v | ||
70 | * Accuracy: 0.02v | ||
71 | * Resolution: 0.001v | ||
72 | |||
73 | (% style="color:blue" %)**NB-IoT Spec:** | ||
74 | |||
75 | (% style="color:#037691" %)**NB-IoT Module: BC660K-GL** | ||
76 | |||
77 | (% style="color:#037691" %)**Support Bands:** | ||
78 | |||
79 | * B1 @H-FDD: 2100MHz | ||
80 | * B2 @H-FDD: 1900MHz | ||
81 | * B3 @H-FDD: 1800MHz | ||
82 | * B4 @H-FDD: 2100MHz | ||
83 | * B5 @H-FDD: 860MHz | ||
84 | * B8 @H-FDD: 900MHz | ||
85 | * B12 @H-FDD: 720MHz | ||
86 | * B13 @H-FDD: 740MHz | ||
87 | * B17 @H-FDD: 730MHz | ||
88 | * B18 @H-FDD: 870MHz | ||
89 | * B19 @H-FDD: 870MHz | ||
90 | * B20 @H-FDD: 790MHz | ||
91 | * B25 @H-FDD: 1900MHz | ||
92 | * B28 @H-FDD: 750MHz | ||
93 | * B66 @H-FDD: 2000MHz | ||
94 | * B70 @H-FDD: 2000MHz | ||
95 | * B85 @H-FDD: 700MHz | ||
96 | |||
97 | (% style="color:blue" %)**Battery:** | ||
98 | |||
99 | * Li/SOCI2 un-chargeable battery | ||
100 | * Capacity: 8500mAh | ||
101 | * Self Discharge: <1% / Year @ 25°C | ||
102 | * Max continuously current: 130mA | ||
103 | * Max boost current: 2A, 1 second | ||
104 | |||
105 | (% style="color:blue" %)**Power Consumption** | ||
106 | |||
107 | * STOP Mode: 10uA @ 3.3v | ||
108 | * Max transmit power: 350mA@3.3v | ||
109 | |||
110 | == 1.4 Probe Types(% style="display:none" %) (%%) == | ||
111 | |||
112 | === 1.4.1 Thread Installation Type === | ||
113 | |||
114 | |||
115 | [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/PS-LB%20--%20LoRaWAN%20Pressure%20Sensor/WebHome/1675071448299-229.png?rev=1.1||alt="1675071448299-229.png"]] | ||
116 | |||
117 | * Hersman Pressure Transmitter | ||
118 | * Measuring Range: -0.1 ~~ 0 ~~ 60MPa, see order info. | ||
119 | * Accuracy: 0.2% F.S | ||
120 | * Long-Term Stability: 0.2% F.S ±0.05% | ||
121 | * Overload 200% F.S | ||
122 | * Zero Temperature Drift: 0.03% FS/℃(≤100Kpa), 0.02%FS/℃(>100Kpa) | ||
123 | * FS Temperature Drift: 0.003% FS/℃(≤100Kpa), 0.002%FS/℃(>100Kpa) | ||
124 | * Storage temperature: -30℃~~80℃ | ||
125 | * Operating temperature: -20℃~~60℃ | ||
126 | * Connector Type: Various Types, see order info | ||
127 | |||
128 | === 1.4.2 Immersion Type === | ||
129 | |||
130 | |||
131 | [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/PS-LB%20--%20LoRaWAN%20Pressure%20Sensor/WebHome/1675071521308-426.png?rev=1.1||alt="1675071521308-426.png" height="206" width="188"]] | ||
132 | |||
133 | * Immersion Type, Probe IP Level: IP68 | ||
134 | * Measuring Range: Measure range can be customized, up to 100m. | ||
135 | * Accuracy: 0.2% F.S | ||
136 | * Long-Term Stability: ±0.2% F.S / Year | ||
137 | * Storage temperature: -30℃~~80℃ | ||
138 | * Operating temperature: 0℃~~50℃ | ||
139 | * Material: 316 stainless steels | ||
140 | |||
141 | (% style="display:none" %) (%%) | ||
142 | |||
143 | |||
144 | == 1.5 Application and Installation == | ||
145 | |||
146 | === 1.5.1 Thread Installation Type === | ||
147 | |||
148 | |||
149 | (% style="color:blue" %)**Application:** | ||
150 | |||
151 | * Hydraulic Pressure | ||
152 | * Petrochemical Industry | ||
153 | * Health and Medical | ||
154 | * Food & Beverage Processing | ||
155 | * Auto-controlling house | ||
156 | * Constant Pressure Water Supply | ||
157 | * Liquid Pressure measuring | ||
158 | |||
159 | Order the suitable thread size and install to measure the air / liquid pressure | ||
160 | |||
161 | [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/PS-LB%20--%20LoRaWAN%20Pressure%20Sensor/WebHome/1675071670469-145.png?rev=1.1||alt="1675071670469-145.png"]] | ||
162 | |||
163 | |||
164 | === 1.5.2 Immersion Type === | ||
165 | |||
166 | |||
167 | (% style="color:blue" %)**Application:** | ||
168 | |||
169 | Liquid & Water Pressure / Level detect. | ||
170 | |||
171 | [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/PS-LB%20--%20LoRaWAN%20Pressure%20Sensor/WebHome/1675071725288-579.png?rev=1.1||alt="1675071725288-579.png"]] | ||
172 | |||
173 | |||
174 | The Immersion Type pressure sensor is shipped with the probe and device separately. When user got the device, below is the wiring to for connect the probe to the device. | ||
175 | |||
176 | [[image:image-20230913150619-1.png]] | ||
177 | |||
178 | |||
179 | [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/PS-LB%20--%20LoRaWAN%20Pressure%20Sensor/WebHome/1675071776102-240.png?rev=1.1||alt="1675071776102-240.png"]](% style="display:none" %) | ||
180 | |||
181 | |||
182 | == 1.6 Sleep mode and working mode == | ||
183 | |||
184 | |||
185 | (% 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. | ||
186 | |||
187 | (% 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. | ||
188 | |||
189 | |||
190 | == 1.7 Button & LEDs == | ||
191 | |||
192 | |||
193 | [[image:Main.User Manual for LoRaWAN End Nodes.D20-LBD22-LBD23-LB_LoRaWAN_Temperature_Sensor_User_Manual.WebHome@1675071855856-879.png]] | ||
194 | |||
195 | |||
196 | (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) | ||
197 | |=(% 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** | ||
198 | |(% style="width:167px" %)Pressing ACT between 1s < time < 3s|(% style="width:117px" %)Send an uplink|(% style="width:225px" %)((( | ||
199 | If sensor has already attached to NB-IoT network, sensor will send an uplink packet, (% style="color:blue" %)**blue led** (%%)will blink once. | ||
200 | Meanwhile, BLE module will be active and user can connect via BLE to configure device. | ||
201 | ))) | ||
202 | |(% style="width:167px" %)Pressing ACT for more than 3s|(% style="width:117px" %)Active Device|(% style="width:225px" %)((( | ||
203 | (% 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. | ||
204 | (% style="color:green" %)**Green led**(%%) will solidly turn on for 5 seconds after joined in network. | ||
205 | 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. | ||
206 | ))) | ||
207 | |(% 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. | ||
208 | |||
209 | (% 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.** | ||
210 | |||
211 | |||
212 | == 1.8 BLE connection == | ||
213 | |||
214 | |||
215 | PS-NB support BLE remote configure and firmware update. | ||
216 | |||
217 | |||
218 | 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: | ||
219 | |||
220 | * Press button to send an uplink | ||
221 | * Press button to active device. | ||
222 | * Device Power on or reset. | ||
223 | |||
224 | If there is no activity connection on BLE in 60 seconds, sensor will shut down BLE module to enter low power mode. | ||
225 | |||
226 | |||
227 | == 1.9 Pin Definitions , Switch & SIM Direction == | ||
228 | |||
229 | |||
230 | PS-NB use the mother board which as below. | ||
231 | |||
232 | [[image:http://8.211.40.43/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/PS-NB-NA_NB-IoT_Analog_Sensor_User_Manual/WebHome/image-20230913113836-1.png?width=545&height=330&rev=1.1||alt="image-20230913113836-1.png"]] | ||
233 | |||
234 | |||
235 | === 1.8.1 Jumper JP2 === | ||
236 | |||
237 | |||
238 | Power on Device when put this jumper. | ||
239 | |||
240 | |||
241 | === 1.8.2 BOOT MODE / SW1 === | ||
242 | |||
243 | |||
244 | **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. | ||
245 | |||
246 | **2)** (% style="color:blue" %)**Flash**(%%): work mode, device starts to work and send out console output for further debug | ||
247 | |||
248 | |||
249 | === 1.8.3 Reset Button === | ||
250 | |||
251 | |||
252 | Press to reboot the device. | ||
253 | |||
254 | (% style="display:none" %) (%%) | ||
255 | |||
256 | === 1.8.4 SIM Card Direction === | ||
257 | |||
258 | 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]]. | ||
259 | |||
260 | |||
261 | == 1.9 BLE connection == | ||
262 | |||
263 | |||
264 | PS-NB support BLE remote configure. | ||
265 | |||
266 | 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: | ||
267 | |||
268 | * Press button to send an uplink | ||
269 | * Press button to active device. | ||
270 | * Device Power on or reset. | ||
271 | |||
272 | If there is no activity connection on BLE in 60 seconds, sensor will shut down BLE module to enter low power mode.(% style="display:none" %) | ||
273 | |||
274 | |||
275 | == 1.10 Mechanical == | ||
276 | |||
277 | [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/PS-LB%20--%20LoRaWAN%20Pressure%20Sensor/WebHome/1675143884058-338.png?rev=1.1||alt="1675143884058-338.png"]] | ||
278 | |||
279 | [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/PS-LB%20--%20LoRaWAN%20Pressure%20Sensor/WebHome/1675143899218-599.png?rev=1.1||alt="1675143899218-599.png"]] | ||
280 | |||
281 | [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/PS-LB%20--%20LoRaWAN%20Pressure%20Sensor/WebHome/1675143909447-639.png?rev=1.1||alt="1675143909447-639.png"]](% style="display:none" %) | ||
282 | |||
283 | |||
284 | = 2. Use PS-NB to communicate with IoT Server = | ||
285 | |||
286 | == 2.1 Send data to IoT server via NB-IoT network == | ||
287 | |||
288 | |||
289 | The PS-NB is equipped with a NB-IoT module, the pre-loaded firmware in PS-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 PS-NB. | ||
290 | |||
291 | |||
292 | Below shows the network structure: | ||
293 | |||
294 | [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/PS-NB_NB-IoT_AirWater_Pressure_Sensor_User_Manual/WebHome/image-20230911092301-6.png?width=921&height=296&rev=1.1||alt="image-20230911092301-6.png"]] | ||
295 | |||
296 | |||
297 | There are two version: (% style="color:blue" %)**-GE**(%%) and (% style="color:blue" %)**-1D**(%%) version of PS-NB. | ||
298 | |||
299 | |||
300 | (% 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 PS-NB send data to IoT server. | ||
301 | |||
302 | * 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]]. | ||
303 | |||
304 | * 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]]. | ||
305 | |||
306 | Below shows result of different server as a glance. | ||
307 | |||
308 | (% border="1" cellspacing="4" style="width:515px" %) | ||
309 | |(% 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** | ||
310 | |(% 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" %)((( | ||
311 | (% style="text-align:center" %) | ||
312 | [[image:image-20230819113244-8.png||height="183" width="367"]] | ||
313 | )))|(% style="width:170px" %) | ||
314 | |(% 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" %)((( | ||
315 | (% style="text-align:center" %) | ||
316 | [[image:image-20230819113244-9.png||height="119" width="367"]] | ||
317 | )))|(% style="width:170px" %) | ||
318 | |(% 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" %) | ||
319 | |(% 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" %) | ||
320 | |(% 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" %) | ||
321 | |(% 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" %)((( | ||
322 | (% style="text-align:center" %) | ||
323 | [[image:image-20230819113244-10.png||height="104" width="367"]] | ||
324 | )))|(% style="width:170px" %) | ||
325 | |(% 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" %)((( | ||
326 | (% style="text-align:center" %) | ||
327 | [[image:image-20230819113244-11.png||height="141" width="367"]] | ||
328 | )))|(% style="width:170px" %) | ||
329 | |||
330 | (% 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 PS-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]]. | ||
331 | |||
332 | |||
333 | == 2.2 Payload Types == | ||
334 | |||
335 | |||
336 | To meet different server requirement, PS-NB supports different payload type. | ||
337 | |||
338 | **Includes:** | ||
339 | |||
340 | * [[General JSON format payload>>||anchor="H2.2.1GeneralJsonFormat28Type3D529"]]. (Type=5) | ||
341 | |||
342 | * [[HEX format Payload>>||anchor="H2.2.2HEXformatPayload28Type3D029"]]. (Type=0) | ||
343 | |||
344 | * [[ThingSpeak Format>>||anchor="H2.2.4ThingSpeakPayload28Type3D129"]]. (Type=1) | ||
345 | |||
346 | * [[ThingsBoard Format>>||anchor="H2.2.3ThingsBoardPayload28Type3D329"]]. (Type=3) | ||
347 | |||
348 | User can specify the payload type when choose the connection protocol. Example: | ||
349 | |||
350 | (% style="color:#037691" %)**AT+PRO=2,0** (%%) ~/~/ Use UDP Connection & hex Payload | ||
351 | |||
352 | (% style="color:#037691" %)**AT+PRO=2,5** (%%) ~/~/ Use UDP Connection & Json Payload | ||
353 | |||
354 | (% style="color:#037691" %)**AT+PRO=3,0** (%%) ~/~/ Use MQTT Connection & hex Payload | ||
355 | |||
356 | (% style="color:#037691" %)**AT+PRO=3,1 **(%%)~/~/ Use MQTT Connection & ThingSpeak | ||
357 | |||
358 | (% style="color:#037691" %)**AT+PRO=3,3 **(%%)~/~/ Use MQTT Connection & ThingsBoard | ||
359 | |||
360 | (% style="color:#037691" %)**AT+PRO=3,5 ** (%%) ~/~/ Use MQTT Connection & Json Payload | ||
361 | |||
362 | (% style="color:#037691" %)**AT+PRO=4,0** (%%) ~/~/ Use TCP Connection & hex Payload | ||
363 | |||
364 | (% style="color:#037691" %)**AT+PRO=4,5** (%%) ~/~/ Use TCP Connection & Json Payload | ||
365 | |||
366 | |||
367 | === 2.2.1 General Json Format(Type~=5) === | ||
368 | |||
369 | |||
370 | This is the General Json Format. As below: | ||
371 | \\(% style="color:#4472c4" %)**{"IMEI":"866207053462705","Model":"PS-NB","idc_intput":0.000,"vdc_intput":0.000,"battery":3.513,"signal":23,"1":{0.000,5.056,2023/09/13 02:14:41},"2":{0.000,3.574,2023/09/13 02:08:20},"3":{0.000,3.579,2023/09/13 02:04:41},"4":{0.000,3.584,2023/09/13 02:00:24},"5":{0.000,3.590,2023/09/13 01:53:37},"6":{0.000,3.590,2023/09/13 01:50:37},"7":{0.000,3.589,2023/09/13 01:47:37},"8":{0.000,3.589,2023/09/13 01:44:37}}** | ||
372 | |||
373 | |||
374 | (% style="color:red" %)**Notice, from above payload:** | ||
375 | |||
376 | * Idc_input , Vdc_input , Battery & Signal are the value at uplink time. | ||
377 | |||
378 | * 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): Idc_input , Vdc_input, Sampling time. | ||
379 | |||
380 | === 2.2.2 HEX format Payload(Type~=0) === | ||
381 | |||
382 | |||
383 | This is the HEX Format. As below: | ||
384 | |||
385 | (% style="color:#4472c4" %)**f866207053462705 0165 0dde 13 0000 00 00 00 00 0fae 0000 64e2d74f 10b2 0000 64e2d69b 0fae 0000 64e2d5e7 10b2 0000 64e2d47f 0fae 0000 64e2d3cb 0fae 0000 64e2d263 0fae 0000 64e2d1af 011a 01e8 64d494ed 0118 01e8 64d4943** | ||
386 | |||
387 | [[image:image-20230904115628-4.png||height="233" width="1290"]] | ||
388 | |||
389 | |||
390 | (% style="color:blue" %)**Version:** | ||
391 | |||
392 | These bytes include the hardware and software version. | ||
393 | |||
394 | (% style="color:#037691" %)**Higher byte:**(%%) Specify Sensor Model: 0x01 for PS-NB | ||
395 | |||
396 | (% style="color:#037691" %)**Lower byte:**(%%) Specify the software version: 0x65=101, means firmware version 1.0.1 | ||
397 | |||
398 | |||
399 | (% style="color:blue" %)**BAT (Battery Info):** | ||
400 | |||
401 | Check the battery voltage for PS-NB. | ||
402 | |||
403 | Ex1: 0x0dde = 3550mV | ||
404 | |||
405 | Ex2: 0x0B49 = 2889mV | ||
406 | |||
407 | |||
408 | (% style="color:blue" %)**Signal Strength:** | ||
409 | |||
410 | NB-IoT Network signal Strength. | ||
411 | |||
412 | **Ex1: 0x13 = 19** | ||
413 | |||
414 | **0** -113dBm or less | ||
415 | |||
416 | **1** -111dBm | ||
417 | |||
418 | **2...30** -109dBm... -53dBm | ||
419 | |||
420 | **31** -51dBm or greater | ||
421 | |||
422 | **99** Not known or not detectable | ||
423 | |||
424 | |||
425 | (% style="color:blue" %)**Probe Model:** | ||
426 | |||
427 | PS-NB might connect to different kind of probes, 4~~20mA represent the full scale of the measuring range. So a 12mA output means different meaning for different probe. | ||
428 | |||
429 | **For example.** | ||
430 | |||
431 | (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:500px" %) | ||
432 | |(% style="background-color:#4f81bd; color:white; width:150px" %)**Probe Type**|(% style="background-color:#4f81bd; color:white; width:150px" %)**4~~20mA scale for this probe**|(% style="background-color:#4f81bd; color:white; width:200px" %)**Example: 12mA actually meaning for this probe** | ||
433 | |(% style="background-color:#f2f2f2; width:206px" %)PH Combination Electrodes|(% style="background-color:#f2f2f2; width:222px" %)0 ~~ 14 pH|(% style="background-color:#f2f2f2; width:356px" %)PH Value: 7 | ||
434 | |(% style="background-color:#f2f2f2; width:206px" %)Water Pressure Sensor|(% style="background-color:#f2f2f2; width:222px" %)0~~5 meters|(% style="background-color:#f2f2f2; width:356px" %)2.5 meters pure water | ||
435 | |(% style="background-color:#f2f2f2; width:206px" %)Pressure transmitter probe|(% style="background-color:#f2f2f2; width:222px" %)0~~1MPa|(% style="background-color:#f2f2f2; width:356px" %)0.5MPa air / gas or water pressure | ||
436 | |||
437 | User can set different probe model for above probes. So IoT server is able to se identical how it should parse the 4~~20mA or 0~~30v sensor value and get the correct value. | ||
438 | |||
439 | |||
440 | (% style="color:blue" %)**IN1 & IN2: ** | ||
441 | |||
442 | IN1 and IN2 are used as Digital input pins. | ||
443 | |||
444 | (% style="color:#037691" %)**Example**: | ||
445 | |||
446 | 01 (H): IN1 or IN2 pin is high level. | ||
447 | |||
448 | 00 (L): IN1 or IN2 pin is low level.(% style="color:blue" %)** ** | ||
449 | |||
450 | |||
451 | (% style="color:blue" %)**GPIO_EXTI Level:** | ||
452 | |||
453 | GPIO_EXTI is used as Interrupt Pin. | ||
454 | |||
455 | (% style="color:#037691" %)**Example**: | ||
456 | |||
457 | 01 (H): GPIO_EXTI pin is high level. | ||
458 | |||
459 | 00 (L): GPIO_EXTI pin is low level. | ||
460 | |||
461 | |||
462 | (% style="color:blue" %)**GPIO_EXTI Flag:** | ||
463 | |||
464 | This data field shows if this packet is generated by (% style="color:blue" %)**Interrupt Pin** (%%)or not. | ||
465 | |||
466 | Note: The Interrupt Pin is a separate pin in the screw terminal. | ||
467 | |||
468 | (% style="color:#037691" %)**Example:** | ||
469 | |||
470 | 0x00: Normal uplink packet. | ||
471 | |||
472 | 0x01: Interrupt Uplink Packet. | ||
473 | |||
474 | |||
475 | (% style="color:blue" %)**0~~20mA:** | ||
476 | |||
477 | (% style="color:#037691" %)**Example**: | ||
478 | |||
479 | 27AE(H) = 10158 (D)/1000 = 10.158mA. | ||
480 | |||
481 | [[image:image-20230904112121-3.png||height="219" width="552"]] | ||
482 | |||
483 | **Connect to a 2 wire 4~~20mA sensor.** | ||
484 | |||
485 | [[image:image-20230913150648-2.png||height="304" width="559"]] | ||
486 | |||
487 | |||
488 | (% style="color:blue" %)**0~~30V:** | ||
489 | |||
490 | Measure the voltage value. The range is 0 to 30V. | ||
491 | |||
492 | (% style="color:#037691" %)**Example**: | ||
493 | |||
494 | 138E(H) = 5006(D)/1000= 5.006V | ||
495 | |||
496 | |||
497 | (% style="color:blue" %)**TimeStamp: ** | ||
498 | |||
499 | Unit TimeStamp Example: 64e2d74f(H) = 1692587855(D) | ||
500 | |||
501 | Put the decimal value into this link([[https:~~/~~/www.epochconverter.com)>>https://www.epochconverter.com]])to get the time. | ||
502 | |||
503 | |||
504 | === 2.2.3 ThingsBoard Payload(Type~=3) === | ||
505 | |||
506 | |||
507 | Type3 payload special design for ThingsBoard, it will also configure other default server to ThingsBoard. | ||
508 | |||
509 | (% style="color:blue" %)**{"IMEI": "866207053462705","Model": "PS-NB","idc_intput": 0.0,"vdc_intput": 3.577,"battery": 3.55,"signal": 22}** | ||
510 | |||
511 | [[image:http://8.211.40.43/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/PS-NB-NA_NB-IoT_Analog_Sensor_User_Manual/WebHome/image-20230913113900-2.png?width=688&height=401&rev=1.1||alt="image-20230913113900-2.png"]] | ||
512 | |||
513 | |||
514 | |||
515 | === 2.2.4 ThingSpeak Payload(Type~=1) === | ||
516 | |||
517 | |||
518 | This payload meets ThingSpeak platform requirement. It includes only four fields. Form 1~~4 are: | ||
519 | |||
520 | Idc_input , Vdc_input , Battery & Signal. This payload type only valid for ThingsSpeak Platform | ||
521 | |||
522 | As below: | ||
523 | |||
524 | (% style="color:blue" %)**field1=idc_intput value&field2=vdc_intput value&field3=battery value&field4=signal value** | ||
525 | |||
526 | [[image:http://8.211.40.43/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/PS-NB-NA_NB-IoT_Analog_Sensor_User_Manual/WebHome/image-20230913113919-3.png?width=622&height=453&rev=1.1||alt="image-20230913113919-3.png"]] | ||
527 | |||
528 | |||
529 | == 2.3 Test Uplink and Change Update Interval == | ||
530 | |||
531 | |||
532 | By default, Sensor will send uplinks (% style="color:blue" %)**every 2 hours**(%%) & AT+NOUD=8 | ||
533 | |||
534 | User can use below commands to change the (% style="color:blue" %)**uplink interval**. | ||
535 | |||
536 | (% style="color:#037691" %)**AT+TDC=600 ** (%%) ~/~/ Set Update Interval to 600s | ||
537 | |||
538 | User can also push the button for more than 1 seconds to activate an uplink. | ||
539 | |||
540 | |||
541 | == 2.4 Multi-Samplings and One uplink == | ||
542 | |||
543 | (% style="color:red" %)Notice: The AT+NOUD feature is upgraded to Clock Logging, please refer** **(%%)[[Clock Logging Feature>>||anchor="H2.8A0Clocklogging28Sincefirmwareversionv1.0.529"]]. | ||
544 | |||
545 | To save battery life, PS-NB will sample Idc_input & Vdc_input 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: | ||
546 | |||
547 | * (% 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) | ||
548 | |||
549 | * (% 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. | ||
550 | |||
551 | The diagram below explains the relationship between TR, NOUD, and TDC more clearly: | ||
552 | |||
553 | [[image:1692424376354-959.png]] | ||
554 | |||
555 | |||
556 | == 2.5 Trggier an uplink by external interrupt == | ||
557 | |||
558 | |||
559 | PS-NB has an external trigger interrupt function. Users can use the GPIO_EXTI pin to trigger the upload of data packets. | ||
560 | |||
561 | (% style="color:blue" %)**AT command:** | ||
562 | |||
563 | * (% style="color:#037691" %)**AT+INTMOD **(%%) ~/~/ Set the trigger interrupt mode | ||
564 | |||
565 | * (% style="color:#037691" %)**AT+INTMOD=0 **(%%) ~/~/ Disable Interrupt,as a digital input pin | ||
566 | |||
567 | * (% style="color:#037691" %)**AT+INTMOD=1 **(%%) ~/~/ Trigger by rising and falling edge | ||
568 | |||
569 | * (% style="color:#037691" %)**AT+INTMOD=2 **(%%) ~/~/ Trigger by falling edge | ||
570 | |||
571 | * (% style="color:#037691" %)**AT+INTMOD=3 **(%%) ~/~/ Trigger by rising edge | ||
572 | |||
573 | == 2.6 Set Power Output Duration == | ||
574 | |||
575 | |||
576 | Control the output duration 3V3 , 5V or 12V. Before each sampling, device will | ||
577 | |||
578 | ~1. first enable the power output to external sensor, | ||
579 | |||
580 | 2. keep it on as per duration, read sensor value and construct uplink payload | ||
581 | |||
582 | 3. final, close the power output. | ||
583 | |||
584 | |||
585 | (% style="color:blue" %)**AT Command: AT+3V3T** | ||
586 | |||
587 | (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:471px" %) | ||
588 | |=(% style="width: 154px;background-color:#4F81BD;color:white" %)**Command Example**|=(% style="width: 201px;background-color:#4F81BD;color:white" %)**Function**|=(% style="width: 116px;background-color:#4F81BD;color:white" %)**Response** | ||
589 | |(% style="background-color:#f2f2f2; width:154px" %)AT+3V3T=?|(% style="background-color:#f2f2f2; width:201px" %)Show 3V3 open time.|(% style="background-color:#f2f2f2; width:116px" %)((( | ||
590 | 0 | ||
591 | OK | ||
592 | ))) | ||
593 | |(% style="background-color:#f2f2f2; width:154px" %)AT+3V3T=0|(% style="background-color:#f2f2f2; width:201px" %)Normally open 3V3 power supply.|(% style="background-color:#f2f2f2; width:116px" %)((( | ||
594 | OK | ||
595 | default setting | ||
596 | ))) | ||
597 | |(% style="background-color:#f2f2f2; width:154px" %)AT+3V3T=1000|(% style="background-color:#f2f2f2; width:201px" %)Close after a delay of 1000 milliseconds.|(% style="background-color:#f2f2f2; width:116px" %)((( | ||
598 | OK | ||
599 | ))) | ||
600 | |(% style="background-color:#f2f2f2; width:154px" %)AT+3V3T=65535|(% style="background-color:#f2f2f2; width:201px" %)Normally closed 3V3 power supply.|(% style="background-color:#f2f2f2; width:116px" %)((( | ||
601 | OK | ||
602 | ))) | ||
603 | |||
604 | (% style="color:blue" %)**AT Command: AT+5VT** | ||
605 | |||
606 | (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:465px" %) | ||
607 | |=(% style="width: 155px;background-color:#4F81BD;color:white" %)**Command Example**|=(% style="width: 196px;background-color:#4F81BD;color:white" %)**Function**|=(% style="width: 114px;background-color:#4F81BD;color:white" %)**Response** | ||
608 | |(% style="background-color:#f2f2f2; width:155px" %)AT+5VT=?|(% style="background-color:#f2f2f2; width:196px" %)Show 5V open time.|(% style="background-color:#f2f2f2; width:114px" %)((( | ||
609 | 0 | ||
610 | OK | ||
611 | ))) | ||
612 | |(% style="background-color:#f2f2f2; width:155px" %)AT+5VT=0|(% style="background-color:#f2f2f2; width:196px" %)Normally closed 5V power supply.|(% style="background-color:#f2f2f2; width:114px" %)((( | ||
613 | OK | ||
614 | default setting | ||
615 | ))) | ||
616 | |(% style="background-color:#f2f2f2; width:155px" %)AT+5VT=1000|(% style="background-color:#f2f2f2; width:196px" %)Close after a delay of 1000 milliseconds.|(% style="background-color:#f2f2f2; width:114px" %)((( | ||
617 | OK | ||
618 | ))) | ||
619 | |(% style="background-color:#f2f2f2; width:155px" %)AT+5VT=65535|(% style="background-color:#f2f2f2; width:196px" %)Normally open 5V power supply.|(% style="background-color:#f2f2f2; width:114px" %)((( | ||
620 | OK | ||
621 | ))) | ||
622 | |||
623 | (% style="color:blue" %)**AT Command: AT+12VT** | ||
624 | |||
625 | (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:438px" %) | ||
626 | |=(% style="width: 156px;background-color:#4F81BD;color:white" %)**Command Example**|=(% style="width: 199px;background-color:#4F81BD;color:white" %)**Function**|=(% style="width: 83px;background-color:#4F81BD;color:white" %)**Response** | ||
627 | |(% style="background-color:#f2f2f2; width:156px" %)AT+12VT=?|(% style="background-color:#f2f2f2; width:199px" %)Show 12V open time.|(% style="background-color:#f2f2f2; width:83px" %)((( | ||
628 | 0 | ||
629 | OK | ||
630 | ))) | ||
631 | |(% style="background-color:#f2f2f2; width:156px" %)AT+12VT=0|(% style="background-color:#f2f2f2; width:199px" %)Normally closed 12V power supply.|(% style="background-color:#f2f2f2; width:83px" %)OK | ||
632 | |(% style="background-color:#f2f2f2; width:156px" %)AT+12VT=500|(% style="background-color:#f2f2f2; width:199px" %)Close after a delay of 500 milliseconds.|(% style="background-color:#f2f2f2; width:83px" %)((( | ||
633 | OK | ||
634 | ))) | ||
635 | |||
636 | == 2.7 Set the Probe Model == | ||
637 | |||
638 | |||
639 | Users need to configure this parameter according to the type of external probe. In this way, the server can decode according to this value, and convert the current value output by the sensor into water depth or pressure value. | ||
640 | |||
641 | (% style="color:blue" %)**AT Command: AT** **+PROBE** | ||
642 | |||
643 | AT+PROBE=aabb | ||
644 | |||
645 | When aa=00, it is the water depth mode, and the current is converted into the water depth value; bb is the probe at a depth of several meters. | ||
646 | |||
647 | When aa=01, it is the pressure mode, which converts the current into a pressure value; | ||
648 | |||
649 | bb represents which type of pressure sensor it is. | ||
650 | |||
651 | (A->01,B->02,C->03,D->04,E->05,F->06,G->07,H->08,I->09,J->0A,K->0B,L->0C) | ||
652 | |||
653 | (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) | ||
654 | |(% style="background-color:#4f81bd; color:white; width:154px" %)**Command Example**|(% style="background-color:#4f81bd; color:white; width:269px" %)**Function**|(% style="background-color:#4f81bd; color:white" %)**Response** | ||
655 | |(% style="background-color:#f2f2f2; width:154px" %)AT +PROBE =?|(% style="background-color:#f2f2f2; width:269px" %)Get or Set the probe model.|(% style="background-color:#f2f2f2" %)0 | ||
656 | OK | ||
657 | |(% style="background-color:#f2f2f2; width:154px" %)AT +PROBE =0003|(% style="background-color:#f2f2f2; width:269px" %)Set water depth sensor mode, 3m type.|(% style="background-color:#f2f2f2" %)OK | ||
658 | |(% style="background-color:#f2f2f2; width:154px" %)((( | ||
659 | AT +PROBE =000A | ||
660 | |||
661 | |||
662 | )))|(% style="background-color:#f2f2f2; width:269px" %)Set water depth sensor mode, 10m type.|(% style="background-color:#f2f2f2" %)OK | ||
663 | |(% style="background-color:#f2f2f2; width:154px" %)AT +PROBE =0101|(% style="background-color:#f2f2f2; width:269px" %)Set pressure transmitters mode, first type(A).|(% style="background-color:#f2f2f2" %)OK | ||
664 | |(% style="background-color:#f2f2f2; width:154px" %)AT +PROBE =0000|(% style="background-color:#f2f2f2; width:269px" %)Initial state, no settings.|(% style="background-color:#f2f2f2" %)OK | ||
665 | |||
666 | == 2.8 Clock logging (Since firmware version v1.0.5) == | ||
667 | |||
668 | 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. | ||
669 | |||
670 | 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. | ||
671 | |||
672 | (% style="color:blue" %)**AT Command: AT+CLOCKLOG=a,b,c,d** | ||
673 | |||
674 | **a: 0:** Disable Clock logging. ** 1: **Enable Clock Logging | ||
675 | |||
676 | **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. | ||
677 | |||
678 | **c: **Specify the sampling interval: range **(0 ~~ 255 minutes)** | ||
679 | |||
680 | **d: **How many entries should be uplink on every TDC **(max 32)** | ||
681 | |||
682 | [[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-20240408084118-1.png?rev=1.1||alt="image-20240408084118-1.png"]] | ||
683 | |||
684 | **Example:** | ||
685 | |||
686 | **AT+CLOCKLOG=1,65535,1,3** | ||
687 | |||
688 | 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 3 memory records (payload + timestamp). | ||
689 | |||
690 | [[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-20240407191613-1.png?width=1128&height=538&rev=1.1||alt="image-20240407191613-1.png"]] | ||
691 | |||
692 | (% 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.** | ||
693 | |||
694 | |||
695 | |||
696 | == 2.9 Example Query saved historical records == | ||
697 | |||
698 | |||
699 | (% style="color:blue" %)**AT Command: AT +CDP**(%%) | ||
700 | 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. | ||
701 | |||
702 | [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/TS01-NB_NB-IoT_Tilting_Sensor_User_Manual/WebHome/image-20240316163550-2.png?width=829&height=638&rev=1.1||alt="image-20240316163550-2.png"]] | ||
703 | |||
704 | == 2.10 Uplink log query == | ||
705 | |||
706 | |||
707 | (% style="color:blue" %)**AT Command: AT** **+GETLOG** | ||
708 | |||
709 | This command can be used to query upstream logs of data packets. | ||
710 | |||
711 | [[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"]] | ||
712 | |||
713 | |||
714 | |||
715 | |||
716 | = 3. Configure PS-NB = | ||
717 | |||
718 | == 3.1 Configure Methods == | ||
719 | |||
720 | |||
721 | PS-NB supports below configure method: | ||
722 | |||
723 | * AT Command via Bluetooth Connection (**Recommended**): [[BLE Configure Instruction>>http://wiki.dragino.com/xwiki/bin/view/Main/BLE%20Bluetooth%20Remote%20Configure/]]. | ||
724 | |||
725 | * 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]]. | ||
726 | |||
727 | == 3.2 AT Commands Set == | ||
728 | |||
729 | |||
730 | AT+<CMD>? : Help on <CMD> | ||
731 | |||
732 | AT+<CMD> : Run <CMD> | ||
733 | |||
734 | AT+<CMD>=<value> : Set the value | ||
735 | |||
736 | AT+<CMD>=? : Get the value | ||
737 | |||
738 | |||
739 | (% style="color:blue" %)**General Commands** | ||
740 | |||
741 | AT : Attention | ||
742 | |||
743 | AT? : Short Help | ||
744 | |||
745 | ATZ : MCU Reset | ||
746 | |||
747 | AT+TDC : Application Data Transmission Interval | ||
748 | |||
749 | AT+CFG : Print all configurations | ||
750 | |||
751 | AT+MODEL :Get module information | ||
752 | |||
753 | AT+SLEEP :Get or set the sleep status | ||
754 | |||
755 | AT+DEUI : Get or set the Device ID | ||
756 | |||
757 | AT+INTMOD : Set the trigger interrupt mode | ||
758 | |||
759 | AT+APN : Get or set the APN | ||
760 | |||
761 | AT+3V3T : Set extend the time of 3V3 power | ||
762 | |||
763 | AT+5VT : Set extend the time of 5V power | ||
764 | |||
765 | AT+12VT : Set extend the time of 12V power | ||
766 | |||
767 | AT+PROBE : Get or Set the probe model | ||
768 | |||
769 | AT+PRO : Choose agreement | ||
770 | |||
771 | AT+RXDL : Extend the sending and receiving time | ||
772 | |||
773 | AT+TR : Get or set data record time | ||
774 | |||
775 | AT+CDP : Read or Clear cached data | ||
776 | |||
777 | AT+NOUD : Get or Set the number of data to be uploaded | ||
778 | |||
779 | AT+DNSCFG : Get or Set DNS Server | ||
780 | |||
781 | AT+CSQTIME : Get or Set the time to join the network | ||
782 | |||
783 | AT+DNSTIMER : Get or Set the NDS timer | ||
784 | |||
785 | AT+TLSMOD : Get or Set the TLS mode | ||
786 | |||
787 | AT+GETSENSORVALUE : Returns the current sensor measurement | ||
788 | |||
789 | AT+SERVADDR : Server Address | ||
790 | |||
791 | |||
792 | (% style="color:blue" %)**MQTT Management** | ||
793 | |||
794 | AT+CLIENT : Get or Set MQTT client | ||
795 | |||
796 | AT+UNAME : Get or Set MQTT Username | ||
797 | |||
798 | AT+PWD : Get or Set MQTT password | ||
799 | |||
800 | AT+PUBTOPIC : Get or Set MQTT publish topic | ||
801 | |||
802 | AT+SUBTOPIC : Get or Set MQTT subscription topic | ||
803 | |||
804 | |||
805 | (% style="color:blue" %)**Information** | ||
806 | |||
807 | AT+FDR : Factory Data Reset | ||
808 | |||
809 | AT+PWORD : Serial Access Password | ||
810 | |||
811 | AT+LDATA : Get the last upload data | ||
812 | |||
813 | AT+CDP : Read or Clear cached data | ||
814 | |||
815 | |||
816 | = 4. Battery & Power Consumption = | ||
817 | |||
818 | |||
819 | PS-NB use ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace. | ||
820 | |||
821 | [[**Battery Info & Power Consumption Analyze**>>http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] . | ||
822 | |||
823 | |||
824 | = 5. Firmware update = | ||
825 | |||
826 | |||
827 | User can change device firmware to:: | ||
828 | |||
829 | * Update with new features. | ||
830 | |||
831 | * Fix bugs. | ||
832 | |||
833 | Firmware and changelog can be downloaded from : **[[Firmware download link>>https://www.dropbox.com/sh/91v917ybgrdf6ml/AAD-65iMMIxpCkhaBvHN44e-a?dl=0]]** | ||
834 | |||
835 | Methods to Update Firmware: | ||
836 | |||
837 | * (Recommended way) OTA firmware update via BLE: [[**Instruction**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/BLE_Firmware_Update_NB_Sensors_BC660K-GL/]]. | ||
838 | |||
839 | * Update through UART TTL interface : **[[Instruction>>http://wiki.dragino.com/xwiki/bin/view/Main/UART_Access_for_NB_ST_BC660K-GL/#H4.2UpdateFirmware28Assumethedevicealreadyhaveabootloader29]]**. | ||
840 | |||
841 | = 6. FAQ = | ||
842 | |||
843 | == 6.1 How can I access t BC660K-GL AT Commands? == | ||
844 | |||
845 | |||
846 | User can access to BC660K-GL directly and send AT Commands. | ||
847 | |||
848 | [[See BC660K-GL AT Command set>>url:https://www.dropbox.com/sh/5f6ssda5fum8rvs/AABT68l8ZzWOvZ5eg2qwOoFda?dl=0]] | ||
849 | |||
850 | |||
851 | == 6.2 How to configure the device through the MQTT subscription function?(Since version v1.0.3) == | ||
852 | |||
853 | |||
854 | Subscription content: {AT COMMAND} | ||
855 | |||
856 | (% style="color:#037691" %)**Example:** | ||
857 | |||
858 | Setting **AT+5VT=500** through Node-RED requires MQTT to send the content {AT+5VT=500}. | ||
859 | |||
860 | [[image:http://8.211.40.43/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/PS-NB-NA_NB-IoT_Analog_Sensor_User_Manual/WebHome/image-20231025162946-2.png?rev=1.1||alt="image-20231025162946-2.png"]] | ||
861 | |||
862 | The serial port displays: | ||
863 | |||
864 | [[image:http://8.211.40.43/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/PS-NB-NA_NB-IoT_Analog_Sensor_User_Manual/WebHome/image-20231025162958-3.png?rev=1.1||alt="image-20231025162958-3.png"]] | ||
865 | |||
866 | |||
867 | = 7. Troubleshooting = | ||
868 | |||
869 | == 7.1 Water Depth Always shows 0 in payload == | ||
870 | |||
871 | |||
872 | If your device's IDC_intput_mA is normal, but your reading always shows 0, please refer to the following points: | ||
873 | |||
874 | ~1. Please set it to mod1 | ||
875 | |||
876 | 2. Please set the command [[AT+PROBE>>||anchor="H2.7SettheProbeModel"]] according to the model of your sensor | ||
877 | |||
878 | 3. Check the connection status of the sensor | ||
879 | |||
880 | |||
881 | = 8. Order Info = | ||
882 | |||
883 | |||
884 | Part Number: (% style="color:blue" %)**PS-NB-Txx-YY or PS-NB-Ixx-YY** | ||
885 | |||
886 | (% style="color:red" %)**XX: Pressure Range and Thread Type ** | ||
887 | |||
888 | (% style="color:blue" %)**YY: ** | ||
889 | |||
890 | * (% style="color:red" %)**GE**(%%): General version ( Exclude SIM card) | ||
891 | |||
892 | * (% style="color:red" %)**1D**(%%): with 1NCE* 10 years 500MB SIM card and Pre-configure to DataCake server. | ||
893 | |||
894 | [[image:image-20231009155543-1.png]] | ||
895 | |||
896 | |||
897 | = 9. Packing Info = | ||
898 | |||
899 | |||
900 | (% style="color:#037691" %)**Package Includes**: | ||
901 | |||
902 | * PS-NB NB-IoT Air/Water Pressure Sensor x 1 | ||
903 | |||
904 | * External antenna x 1 | ||
905 | |||
906 | (% style="color:#037691" %)**Dimension and weight**: | ||
907 | |||
908 | * Device Size: cm | ||
909 | |||
910 | * Device Weight: g | ||
911 | |||
912 | * Package Size / pcs : cm | ||
913 | |||
914 | * Weight / pcs : g | ||
915 | |||
916 | = 10. Support = | ||
917 | |||
918 | |||
919 | * 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. | ||
920 | |||
921 | * 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]]. | ||
922 | |||
923 | (% style="display:none" %) (%%) |