Skip to Content
Version 100.1 by Mengting Qiu on 2024/05/31 15:54
Show last authors
1
2
3 (% style="text-align:center" %)
4 [[image:image-20230819102136-3.png||height="425" width="646"]]
5
6
7
8
9
10
11 **Table of Contents:**
12
13 {{toc/}}
14
15
16
17
18
19
20 = 1. Introduction =
21
22 == 1.1 What is S31x-NB NB-IoT Temperature & Humidity Sensor ==
23
24
25 The Dragino S31-NB and S31B-NB are (% style="color:blue" %)**NB-IoT Temperature and Humidity Sensor**(%%) for Internet of Things solution. It is used to measure the surrounding (% style="color:blue" %)**environment temperature and relative air humidity precisely**(%%), and then upload to IoT server via NB-IoT network*.
26
27 The temperature & humidity sensor used in S31-NB is SHT31, which is fully calibrated, linearized, and temperature compensated digital output from Sensirion, it provides a strong reliability and long-term stability. The SHT31 is fixed in a (% style="color:blue" %)**waterproof anti-condensation casing**(%%) for long term use.
28
29 S31-NB supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP**(%%) for different application requirement. and Support Uplinks to various IoT Servers.
30
31 S31-NB is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long term use up to several years. (Real-world battery life depends on the use environment, update period and uplink method. Please check related Power Analyze report).
32
33 *make sure you have NB-IoT coverage locally.
34
35
36 [[image:1692411831805-116.png]]
37
38
39 == 1.2 ​Features ==
40
41
42 * NB-IoT Bands: B1/B2/B3/B4/B5/B8/B12/B13/B17/B18/B19/B20/B25/B28/B66/B70/B85 @H-FDD
43 * Ultra-low power consumption
44 * External 3 meters SHT31 probe (For S31-NB)
45 * Measure range -40°C ~~ 80°C
46 * Temperature & Humidity alarm
47 * Multiply Sampling and one uplink
48 * Support Bluetooth v5.1 remote configure and update firmware
49 * Uplink on periodically
50 * Downlink to change configure
51 * 8500mAh Battery for long term use
52 * Nano SIM card slot for NB-IoT SIM
53
54 == 1.3 Specification ==
55
56
57 (% style="color:blue" %)**Common DC Characteristics:**
58
59 * Supply Voltage: 2.1v ~~ 3.6v
60 * Operating Temperature: -40 ~~ 85°C
61
62 (% style="color:blue" %)**Temperature Sensor:**
63
64 * Range: -40 to + 80°C
65 * Accuracy: ±0.2 @ 0-90 °C
66 * Resolution: 0.1°C
67 * Long Term Shift: <0.03 °C/yr
68
69 (% style="color:blue" %)**Humidity Sensor: **
70
71 * Range: 0 ~~ 99.9% RH
72 * Accuracy: ± 2%RH ( 0 ~~ 100%RH)
73 * Resolution: 0.01% RH
74 * Long Term Shift: <0.25 %RH/yr
75
76 (% style="color:blue" %)**NB-IoT Spec:**
77
78 (% style="color:#037691" %)**NB-IoT Module: BC660K-GL**
79
80 (% style="color:#037691" %)**Support Bands:**
81
82 * B1 @H-FDD: 2100MHz
83 * B2 @H-FDD: 1900MHz
84 * B3 @H-FDD: 1800MHz
85 * B4 @H-FDD: 2100MHz
86 * B5 @H-FDD: 860MHz
87 * B8 @H-FDD: 900MHz
88 * B12 @H-FDD: 720MHz
89 * B13 @H-FDD: 740MHz
90 * B17 @H-FDD: 730MHz
91 * B18 @H-FDD: 870MHz
92 * B19 @H-FDD: 870MHz
93 * B20 @H-FDD: 790MHz
94 * B25 @H-FDD: 1900MHz
95 * B28 @H-FDD: 750MHz
96 * B66 @H-FDD: 2000MHz
97 * B70 @H-FDD: 2000MHz
98 * B85 @H-FDD: 700MHz
99
100 (% style="color:blue" %)**Battery:**
101
102 * Li/SOCI2 un-chargeable battery
103 * Capacity: 8500mAh
104 * Self Discharge: <1% / Year @ 25°C
105 * Max continuously current: 130mA
106 * Max boost current: 2A, 1 second
107
108 (% style="color:blue" %)**Power Consumption**
109
110 * STOP Mode: 10uA @ 3.3v
111 * Max transmit power: 350mA@3.3v
112
113 == 1.4 Applications ==
114
115
116 * Smart Buildings & Home Automation
117 * Logistics and Supply Chain Management
118 * Smart Metering
119 * Smart Agriculture
120 * Smart Cities
121 * Smart Factory
122
123 == 1.5 Sleep mode and working mode ==
124
125
126 (% 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.
127
128 (% 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.
129
130
131 == 1.6 Button & LEDs ==
132
133
134 [[image:Main.User Manual for LoRaWAN End Nodes.D20-LBD22-LBD23-LB_LoRaWAN_Temperature_Sensor_User_Manual.WebHome@1675071855856-879.png]]
135
136 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %)
137 |=(% style="width: 167px;background-color:#4F81BD;color:white" %)**Behavior on ACT**|=(% style="width: 117px;background-color:#4F81BD;color:white" %)**Function**|=(% style="width:226px;background-color:#4F81BD;color:white" %)**Action**
138 |(% style="width:167px" %)Pressing ACT between 1s < time < 3s|(% style="width:117px" %)Send an uplink|(% style="width:225px" %)(((
139 If sensor has already attached to NB-IoT network, sensor will send an uplink packet, (% style="color:blue" %)**blue led** (%%)will blink once.
140 Meanwhile, BLE module will be active and user can connect via BLE to configure device.
141 )))
142 |(% style="width:167px" %)Pressing ACT for more than 3s|(% style="width:117px" %)Active Device|(% style="width:225px" %)(((
143 (% 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.
144 (% style="color:green" %)**Green led**(%%) will solidly turn on for 5 seconds after joined in network.
145 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.
146 )))
147 |(% 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.
148
149 (% 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.**
150
151
152 == 1.7 BLE connection ==
153
154
155 S31x-NB support BLE remote configure and firmware update.
156
157 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:
158
159 * Press button to send an uplink
160 * Press button to active device.
161 * Device Power on or reset.
162
163 If there is no activity connection on BLE in 60 seconds, sensor will shut down BLE module to enter low power mode.
164
165
166 == 1.8 Pin Definitions , Switch & SIM Direction ==
167
168
169 S31x-NB use the mother board from S31-NB which as below.
170
171 [[image:image-20230819104805-5.png]]
172
173
174 === 1.8.1 Jumper JP2 ===
175
176
177 Power on Device when put this jumper.
178
179 Power off device when take out this jumper
180
181
182 === 1.8.2 BOOT MODE / SW1 ===
183
184
185 **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.
186
187 **2)** (% style="color:blue" %)**Flash**(%%): work mode, device starts to work and send out console output for further debug
188
189
190 === 1.8.3 Reset Button ===
191
192
193 Press to reboot the device.
194
195
196 === 1.8.4 SIM Card Direction ===
197
198 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]].
199
200
201 == 1.9 Hardware Variant ==
202
203
204 (% border="1" cellspacing="3" style="width:410px" %)
205 |=(% style="width: 103px;background-color:#4F81BD;color:white" %)Model|=(% style="width: 127px; background-color:#4F81BD;color:white" %)Photo|=(% style="width: 180px;background-color:#4F81BD;color:white" %)Probe Info
206 |(% style="width:102px" %)(((
207 S31-NB
208 )))|(% style="width:126px" %)(((
209 (% style="text-align:center" %)
210 [[image:image-20230819110632-6.png||height="130" width="104"]]
211 )))|(% style="width:179px" %)(((
212 1 x SHT31 Probe
213
214 Cable Length : 3 meters
215
216
217 )))
218 |(% style="width:102px" %)(((
219 S31B-NB
220 )))|(% style="width:126px" %)(((
221 (% style="text-align:center" %)
222 [[image:image-20230819110702-7.png||height="164" width="90"]]
223 )))|(% style="width:179px" %)(((
224 1 x SHT31 Probe
225
226 Installed in device.
227 )))
228
229 (% style="display:none" %)
230
231
232
233 = 2. Use S31-NB to communicate with IoT Server =
234
235 == 2.1 Send data to IoT server via NB-IoT network ==
236
237
238 The S31-NB is equipped with a NB-IoT module, the pre-loaded firmware in S31-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 S31-NB.
239
240
241 Below shows the network structure:
242
243 [[image:1692415924540-357.png]]
244
245
246 There are two version: (% style="color:blue" %)**-GE**(%%) and (% style="color:blue" %)**-1D**(%%) version of S31-NB.
247
248
249 (% 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 S31-NB send data to IoT server.
250
251 * 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]].
252
253 * 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]]. 
254
255 Below shows result of different server as a glance.
256
257 (% border="1" cellspacing="3" style="width:515px" %)
258 |(% 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**
259 |(% 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" %)(((
260 (% style="text-align:center" %)
261 [[image:image-20230819113244-8.png||height="183" width="367"]]
262 )))|(% style="width:170px" %)
263 |(% 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" %)(((
264 (% style="text-align:center" %)
265 [[image:image-20230819113244-9.png||height="119" width="367"]]
266 )))|(% style="width:170px" %)
267 |(% 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" %)
268 |(% 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" %)
269 |(% 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" %)
270 |(% 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" %)(((
271 (% style="text-align:center" %)
272 [[image:image-20230819113244-10.png||height="104" width="367"]]
273 )))|(% style="width:170px" %)
274 |(% 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" %)(((
275 (% style="text-align:center" %)
276 [[image:image-20230819113244-11.png||height="141" width="367"]]
277 )))|(% style="width:170px" %)
278
279 (% 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 S31-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]].
280
281
282 == 2.2 ​Payload Types ==
283
284
285 To meet different server requirement, S31-NB supports different payload type.
286
287 **Includes:**
288
289 * [[General JSON format payload>>||anchor="H2.2.1GeneralJsonFormat28Type3D529"]]. (Type=5)
290
291 * [[HEX format Payload>>||anchor="H2.2.2HEXformatPayload28Type3D029"]]. (Type=0)
292
293 * [[ThingSpeak Format>>||anchor="H2.2.4ThingSpeakPayload28Type3D129"]]. (Type=1)
294
295 * [[ThingsBoard Format>>||anchor="H2.2.3ThingsBoardPayload28Type3D329"]]. (Type=3)
296
297 User can specify the payload type when choose the connection protocol. Example:
298
299 (% style="color:#037691" %)**AT+PRO=2,0**  (%%) ~/~/ Use UDP Connection & hex Payload
300
301 (% style="color:#037691" %)**AT+PRO=2,5**   (%%) ~/~/ Use UDP Connection & Json Payload
302
303 (% style="color:#037691" %)**AT+PRO=3,5 ** (%%) ~/~/ Use MQTT Connection & Json Payload
304
305
306 === 2.2.1 General Json Format(Type~=5) ===
307
308
309 This is the General Json Format. As below:
310
311 (% style="color:#4472c4" %)**{"IMEI":866207053462762,"temperature":29.2,"humidity":54.2,"battery":3.27,"signal":24,"Model":S31x-NB, "1":{28.2,48.3,2023/08/10 08:00:37},"2":{28.1,49.1,2023/08/10 07:57:37},"3":{28.1,48.5,2023/08/10 07:54:37},"4":{28.2,48.6,2023/08/10 07:51:37},"5":{28.1,48.9,2023/08/10 07:48:37},"6":{28.2,48.8,2023/08/10 07:45:37},"7":{28.2,48.8,2023/08/10 07:42:37},"8":{28.0,48.8,2023/08/10 07:39:37}}**
312
313
314 (% style="color:red" %)**Notice, from above payload:**
315
316 * Temperature , Humidity , Battery & Signal are the value at uplink time.
317
318 * Json entry 1 ~~ 8 are the last 1 ~~ 8 sampling data as specify by (% style="color:#037691" %)**AT+NOUD=8 ** (%%)Command. Each entry includes (from left to right): Temperature, Humidity, Sampling time.
319
320 Example in ThingsBoard:
321
322 [[image:image-20240522172252-1.png||height="531" width="1119"]]
323
324
325 === 2.2.2 HEX format Payload(Type~=0) ===
326
327
328 This is the HEX Format. As below:
329
330 (% style="color:#4472c4" %)**f86620705346276200640cba16010000000011011801e864d49c2d011a01e364d49925011901eb64d49871011901e564d497bd011a01e664d49709011901e964d49655011a01e864d495a1011a01e864d494ed011801e864d49439**
331
332 [[image:1692424009971-458.png]]
333
334
335 (% style="color:blue" %)**Version:**
336
337 These bytes include the hardware and software version.
338
339 (% style="color:#037691" %)**Higher byte:**(%%) Specify Sensor Model: 0x00 for S31B-NB & S31-NB
340
341 (% style="color:#037691" %)**Lower byte:**(%%) Specify the software version: 0x64=100, means firmware version 100
342
343
344 (% style="color:blue" %)**BAT (Battery Info):**
345
346 Ex1: 0x0CBA = 3258mV
347
348
349 (% style="color:blue" %)**Signal Strength:**
350
351 NB-IoT Network signal Strength.
352
353 **Ex1: 0x16 = 22**
354
355 **0**  -113dBm or less
356
357 **1**  -111dBm
358
359 **2...30** -109dBm... -53dBm
360
361 **31**   -51dBm or greater
362
363 **99**    Not known or not detectable
364
365
366 (% style="color:blue" %)**Temperature: **
367
368 If payload is: 0105H:  (0105 & 8000 == 0), temp = 0105H /10 = 26.1 degree
369
370 If payload is: FF3FH :  (FF3F & 8000 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees.
371
372 (FF3F & 8000: Judge whether the highest bit is 1, when the highest bit is 1, it is negative)
373
374
375 (% style="color:blue" %)**Humidity:   **
376
377 Read:0295(H)=661(D)    Value:  661 / 10=66.1, So 66.1%
378
379
380 (% style="color:blue" %)**TimeStamp:   **
381
382 Unit TimeStamp Example: 64d49439(H) = 1691653177(D)
383
384 Put the decimal value into this link(https:~/~/www.epochconverter.com/) to get the time.
385
386
387 === 2.2.3 ThingsBoard Payload(Type~=3) ===
388
389
390 Type3 payload special design for ThingsBoard, it will also configure other default server to ThingsBoard.
391
392 (% style="color:#4472c4" %)**{"IMEI":866207053462762,"temperature":29.2,"humidity":54.2,"battery":3.27,"signal":24}**
393
394
395 === 2.2.4 ThingSpeak Payload(Type~=1) ===
396
397
398 This payload meets ThingSpeak platform requirement. It includes only four fields. Form 1~~4 are:
399
400 Temperature, Humidity, Battery & Signal. This payload type only valid for ThingsSpeak Platform
401
402 As below:
403
404 (% style="color:#4472c4" %)**field1=27.9&field2=49.9&field3=3.23&field4=28**
405
406
407 == 2.3 Test Uplink and Change Update Interval ==
408
409
410 By default, Sensor will send uplinks (% style="color:blue" %)**every 2 hours**(%%) & AT+NOUD=8
411
412 User can use below commands to change the (% style="color:blue" %)**uplink interval**.
413
414 (% style="color:#037691" %)**AT+TDC=600 ** (%%) ~/~/ Set Update Interval to 600s
415
416 User can also push the button for more than 1 seconds to activate an uplink.
417
418
419 == 2.4 Multi-Samplings and One uplink ==
420
421 (% style="color:red" %)Notice: The AT+NOUD feature is upgraded to Clock Logging, please refer [[Clock Logging Feature>>||anchor="H2.7Clocklogging28Sincefirmwareversionv1.2.129"]]
422
423 To save battery life, S31-NB will sample temperature & humidity 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:
424
425 * (% 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)
426
427 * (% 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.
428
429 The diagram below explains the relationship between TR, NOUD, and TDC more clearly:
430
431 [[image:1692424376354-959.png]]
432
433
434 == 2.5 Humidity and Temperature alarm function ==
435
436
437 On each sampling define by AT+TR ( default 900s or 15 minutes), when the value exceed the range, it will trigger an Alarm and immediately sends a uplink.
438
439
440 (% style="color:blue" %)**AT Commands:**
441
442 (% style="color:#037691" %)**AT+ SHHUM=min,max**
443
444 Example: AT+ SHHUM=50,80  ~/~/ Alarm when humidity lower than 50 or higher than 80.
445
446
447 (% style="color:#037691" %)**AT+ SHTEMP=min,max**
448
449 Example: AT+ SHTEMP=20,30  ~/~/ Alarm when temperature lower than 20 or higher than 30
450
451
452 (% style="color:red" %)**Notice:**
453
454 * To disable Alarm, user can set min and max to same value , such as (% style="color:#037691" %)**AT+SHTEMP=0,0.**
455
456 * If user only want to send only min or max, user can set the alarm to a value that device won’t reach. For example: (% style="color:#037691" %)**AT+SHTEMP=-80,0.**
457
458 == 2.6 Trggier an uplink by external interrupt ==
459
460
461 S31-NB has an external trigger interrupt function. Users can use the PB15 pin to trigger the upload of data packets.
462
463 (% style="color:blue" %)**AT command:**
464
465 * (% style="color:#037691" %)**AT+INTMOD **(%%) ~/~/ Set the trigger interrupt mode
466
467 * (% style="color:#037691" %)**AT+INTMOD=0 **(%%) ~/~/ Disable Interrupt
468
469 * (% style="color:#037691" %)**AT+INTMOD=1 **(%%) ~/~/ Trigger by rising and falling edge
470
471 * (% style="color:#037691" %)**AT+INTMOD=2 **(%%) ~/~/ Trigger by falling edge
472
473 * (% style="color:#037691" %)**AT+INTMOD=3  **(%%) ~/~/ Trigger by rising edge
474
475 == 2.7 Clock logging (Since firmware version v1.2.1) ==
476
477
478 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.
479
480 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.
481
482 * (% style="color:blue" %)**AT command:**(%%)** (% style="color:#037691" %)AT+CLOCKLOG=a,b,c,d(%%)**
483
484 (% style="color:#037691" %)**a: **(%%)**0:** Disable Clock logging.  ** 1: **Enable Clock Logging
485
486 (% style="color:#037691" %)**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.
487
488 (% style="color:#037691" %)**c: **(%%)Specify the sampling interval: range **(0 ~~ 255 minutes)**
489
490 (% style="color:#037691" %)**d:**(%%)** **How many entries should be uplink on every TDC **(max 32)**
491
492 [[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"]]
493
494 **Example:**
495
496 **AT+CLOCKLOG=1,65535,1,5**
497
498 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).
499
500 (% class="wikigeneratedid" %)
501 [[image:image-20240316172630-1.png||height="452" width="1127"]]
502
503 (% class="wikigeneratedid" %)
504 (% 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.**
505
506
507 == 2.8 Example Query saved historical records ==
508
509
510 * (% style="color:blue" %)**AT command:**(%%)** (% style="color:#037691" %)AT+CDP(%%)**
511
512 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.
513
514 (% class="wikigeneratedid" %)
515 [[image:image-20240316172700-2.png||height="632" width="819"]]
516
517
518 == 2.9 Uplink log query ==
519
520
521 * (% style="color:blue" %)**AT command:**(%%)** (% style="color:#037691" %)AT+GETLOG(%%)**
522
523 This command can be used to query upstream logs of data packets.
524
525 [[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"]]
526
527
528 == 2.10 Scheduled domain name resolution ==
529
530
531 This command is used to set up scheduled domain name resolution
532
533 (% style="color:blue" %)**AT command:**
534
535 * (% style="color:#037691" %)**AT+DNSTIMER=XX**(%%)**  **~/~/ Unit: hour
536
537 After setting this command, domain name resolution will be performed regularly.
538
539
540 = 3. Configure S31x-NB =
541
542 == 3.1 Configure Methods ==
543
544
545 S31x-NB supports below configure method:
546
547 * AT Command via Bluetooth Connection (**Recommended**): [[BLE Configure Instruction>>http://wiki.dragino.com/xwiki/bin/view/Main/BLE%20Bluetooth%20Remote%20Configure/]].
548
549 * 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]].
550
551 == 3.2 AT Commands Set ==
552
553
554 AT+<CMD>?        : Help on <CMD>
555
556 AT+<CMD>         : Run <CMD>
557
558 AT+<CMD>=<value> : Set the value
559
560 AT+<CMD>=?       : Get the value
561
562
563 (% style="color:blue" %)**General Commands**      
564
565 AT                    : Attention       
566
567 AT?  : Short Help     
568
569 ATZ  : MCU Reset    
570
571 AT+TDC  : Application Data Transmission Interval
572
573 AT+CFG  : Print all configurations
574
575 AT+CFGMOD           : Working mode selection
576
577 AT+DEUI  : Get or set the Device ID
578
579 AT+INTMOD            : Set the trigger interrupt mode
580
581 AT+5VT           : Set extend the time of 5V power  
582
583 AT+PRO          : Choose agreement
584
585 AT+RXDL  : Extend the sending and receiving time
586
587 AT+DNSCFG  : Get or Set DNS Server
588
589 AT+GETSENSORVALUE   : Returns the current sensor measurement
590
591 AT+NOUD  : Get or Set the number of data to be uploaded
592
593 AT+CDP     : AT+CDP Read cached data/AT+CDP=0  Clear cached data
594
595 AT+SHTEMP:  Get or Set alarm of temp
596
597 AT+SHHUM:  Get or Set alarm of moisture
598
599 AT+SERVADDR :  Server Address
600
601
602 (% style="color:blue" %)**MQTT Management**
603
604 AT+CLIENT               : Get or Set MQTT client
605
606 AT+UNAME              : Get or Set MQTT Username
607
608 AT+PWD                  : Get or Set MQTT password
609
610 AT+PUBTOPIC  : Get or Set MQTT publish topic
611
612 AT+SUBTOPIC  : Get or Set MQTT subscription topic
613
614
615 (% style="color:blue" %)**Information**          
616
617 AT+FDR  : Factory Data Reset
618
619 AT+PWORD  : Serial Access Password
620
621 AT+LDATA  : Get the last upload data
622
623 AT+CDP  : AT+CDP Read cached data/AT+CDP=0  Clear cached data
624
625
626 = 4. Battery & Power Consumption =
627
628
629 S31x-NB use ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace.
630
631 [[**Battery Info & Power Consumption Analyze**>>http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] .
632
633
634 = 5. Firmware update =
635
636
637 User can change device firmware to::
638
639 * Update with new features.
640
641 * Fix bugs.
642
643 Firmware and changelog can be downloaded from : **[[Firmware download link>>https://www.dropbox.com/sh/fhb3uyl4gt6clru/AAAiZVTFcxrfE1JOOyfcgO9ha?dl=0]]**
644
645 Methods to Update Firmware:
646
647 * (Recommended way) OTA firmware update via BLE: [[**Instruction**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/BLE_Firmware_Update_NB_Sensors_BC660K-GL/]].
648
649 * Update through UART TTL interface : **[[Instruction>>http://wiki.dragino.com/xwiki/bin/view/Main/UART_Access_for_NB_ST_BC660K-GL/#H4.2UpdateFirmware28Assumethedevicealreadyhaveabootloader29]]**.
650
651 = 6. FAQ =
652
653 == 6.1 How can I access t BC660K-GL AT Commands? ==
654
655
656 User can access to BC660K-GL directly and send AT Commands.
657
658 [[See BC660K-GL AT Command set>>url:https://www.dropbox.com/sh/5f6ssda5fum8rvs/AABT68l8ZzWOvZ5eg2qwOoFda?dl=0]]
659
660
661 = 7. Order Info =
662
663
664 Part Number: (% style="color:blue" %)**S31-NB-XX  / S31B-NB-XX**
665
666 (% style="color:red" %)**XX**(%%):
667
668 * (% style="color:#037691" %)**GE**(%%): General version ( Exclude SIM card)
669
670 * (% style="color:#037691" %)**1D**(%%): with 1NCE* 10 years 500MB SIM card and Pre-configure to DataCake server
671
672 (% 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
673
674
675 = 8. ​Packing Info =
676
677
678 (% style="color:#037691" %)**Package Includes**:
679
680 * S31-NB or S31-NB NB-IoT Sensor Node x 1
681
682 * External antenna x 1
683
684 (% style="color:#037691" %)**Dimension and weight**:
685
686 * Device Size: 13.0 x 5 x 4.5 cm
687
688 * Device Weight: 150g
689
690 * Package Size / pcs : 14.0 x 8x 5 cm
691
692 * Weight / pcs : 180g
693
694 = 9. Support =
695
696
697 * 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.
698
699 * 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]].
700
701 (% style="display:none" %) (%%)