Wiki source code of S31-CB/S31B-CB -- NB-IoT/LTE-M Temperature & Humidity Sensor User Manual
Last modified by kai on 2025/03/14 09:48
Show last authors
author | version | line-number | content |
---|---|---|---|
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 Temperature & Humidity Sensor == | ||
23 | |||
24 | |||
25 | The Dragino S31-CB and S31B-CB are (% style="color:blue" %)**NB-IoT/LTE-M 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 or CAT-M1 network. | ||
26 | |||
27 | The temperature & humidity sensor used in S31x-CB 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 | S31x-CB supports different uplink methods include (% style="color:blue" %)**MQTT, MQTTs, TCP, UDP or CoAP**(%%) for different application requirement. and Support Uplinks to various IoT Servers. | ||
30 | |||
31 | S31x-CB 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 or CAT-M1 coverage locally. | ||
34 | |||
35 | |||
36 | == 1.2 Features == | ||
37 | |||
38 | |||
39 | * For -NB Bands: B1/B2/B3/B4/B5/B8/B12/B13/B17/B18/B19/B20/B25/B28/B66/B70/B85 | ||
40 | * For -CB Bands: B1/B2/B3/B4/B5/B8/B12/B13~/~/B18/B19/B20/B25/B28/B66/B71/B85 | ||
41 | * CAT-M1 / LTE-M Bands: B1/B2/B3/B4/B5/B8/B12/B13/B18/B19/B20/B25/B26/B27/B28/B66/B85 | ||
42 | * Ultra-low power consumption | ||
43 | * External 3 meters SHT31 probe (For S31-CB) | ||
44 | * Measure range -40°C ~~ 80°C | ||
45 | * Temperature & Humidity alarm | ||
46 | * Multiply Sampling and one uplink | ||
47 | * Uplink via MQTT, MQTTs, TCP, UDP or CoAP | ||
48 | * GNSS for Location Report | ||
49 | * Support Bluetooth v5.1 remote configure and update firmware | ||
50 | * Uplink on periodically | ||
51 | * Downlink to change configure | ||
52 | * 8500mAh Li/SOCl2 Battery (S31x-CB) | ||
53 | * Solar panel + 3000mAh Li-ion battery (S31x-CS) | ||
54 | * Nano SIM card slot for NB-IoT SIM | ||
55 | |||
56 | == 1.3 Specification == | ||
57 | |||
58 | |||
59 | (% style="color:blue" %)**Common DC Characteristics:** | ||
60 | |||
61 | * Supply Voltage: 2.6v ~~ 3.6v | ||
62 | * Operating Temperature: -40 ~~ 85°C | ||
63 | |||
64 | (% style="color:blue" %)**Temperature Sensor:** | ||
65 | |||
66 | * Range: -40 to + 80°C | ||
67 | * Accuracy: ±0.2 @ 0-90 °C | ||
68 | * Resolution: 0.1°C | ||
69 | * Long Term Shift: <0.03 °C/yr | ||
70 | |||
71 | (% style="color:blue" %)**Humidity Sensor: ** | ||
72 | |||
73 | * Range: 0 ~~ 99.9% RH | ||
74 | * Accuracy: ± 2%RH ( 0 ~~ 100%RH) | ||
75 | * Resolution: 0.01% RH | ||
76 | * Long Term Shift: <0.25 %RH/yr | ||
77 | |||
78 | (% style="color:blue" %)**NB-IoT Spec:** | ||
79 | |||
80 | (% style="color:#037691" %)**NB-IoT Module: BG95-NGFF** | ||
81 | |||
82 | (% style="color:#037691" %)**Support Bands:** | ||
83 | |||
84 | * B1 @H-FDD: 2100MHz | ||
85 | * B2 @H-FDD: 1900MHz | ||
86 | * B3 @H-FDD: 1800MHz | ||
87 | * B4 @H-FDD: 2100MHz | ||
88 | * B5 @H-FDD: 860MHz | ||
89 | * B8 @H-FDD: 900MHz | ||
90 | * B12 @H-FDD: 720MHz | ||
91 | * B13 @H-FDD: 740MHz | ||
92 | * B17 @H-FDD: 730MHz | ||
93 | * B18 @H-FDD: 870MHz | ||
94 | * B19 @H-FDD: 870MHz | ||
95 | * B20 @H-FDD: 790MHz | ||
96 | * B25 @H-FDD: 1900MHz | ||
97 | * B28 @H-FDD: 750MHz | ||
98 | * B66 @H-FDD: 2000MHz | ||
99 | * B70 @H-FDD: 2000MHz | ||
100 | * B85 @H-FDD: 700MHz | ||
101 | |||
102 | (% style="color:blue" %)**Battery:** | ||
103 | |||
104 | * Li/SOCI2 un-chargeable battery | ||
105 | * Capacity: 8500mAh | ||
106 | * Self Discharge: <1% / Year @ 25°C | ||
107 | * Max continuously current: 130mA | ||
108 | * Max boost current: 2A, 1 second | ||
109 | |||
110 | (% style="color:blue" %)**Power Consumption:** | ||
111 | |||
112 | * STOP Mode: 14uA @ 3.3v | ||
113 | * Max transmit power: 350mA@3.3v | ||
114 | |||
115 | == 1.4 Applications == | ||
116 | |||
117 | |||
118 | * Smart Buildings & Home Automation | ||
119 | * Logistics and Supply Chain Management | ||
120 | * Smart Metering | ||
121 | * Smart Agriculture | ||
122 | * Smart Cities | ||
123 | * Smart Factory | ||
124 | |||
125 | == 1.5 Sleep mode and working mode == | ||
126 | |||
127 | |||
128 | (% style="color:blue" %)**Deep Sleep Mode: **(%%)Sensor doesn't have any NB-IoT/CAT-M1 activate. This mode is used for storage and shipping to save battery life. | ||
129 | |||
130 | (% 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. | ||
131 | |||
132 | |||
133 | == 1.6 Button & LEDs == | ||
134 | |||
135 | |||
136 | [[image:Main.User Manual for LoRaWAN End Nodes.D20-LBD22-LBD23-LB_LoRaWAN_Temperature_Sensor_User_Manual.WebHome@1675071855856-879.png]] | ||
137 | |||
138 | (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %) | ||
139 | |=(% 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** | ||
140 | |(% style="width:167px" %)Pressing ACT between 1s < time < 3s|(% style="width:117px" %)Send an uplink|(% style="width:225px" %)((( | ||
141 | If sensor has already attached to NB-IoT/CAT-M1 network, sensor will send an uplink packet, (% style="color:blue" %)**blue led** (%%)will blink once. | ||
142 | Meanwhile, BLE module will be active and user can connect via BLE to configure device. | ||
143 | ))) | ||
144 | |(% style="width:167px" %)Pressing ACT for more than 3s|(% style="width:117px" %)Active Device|(% style="width:225px" %)((( | ||
145 | (% 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/CAT-M1 network. | ||
146 | (% style="color:green" %)**Green led**(%%) will solidly turn on for 5 seconds after joined in network. | ||
147 | 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/CAT-M1 network or not. | ||
148 | ))) | ||
149 | |(% 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. | ||
150 | |||
151 | (% 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.** | ||
152 | |||
153 | |||
154 | == 1.7 BLE connection == | ||
155 | |||
156 | |||
157 | S31x-CB support BLE remote configure and firmware update. | ||
158 | |||
159 | 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: | ||
160 | |||
161 | * Press button to send an uplink | ||
162 | * Press button to active device. | ||
163 | * Device Power on or reset. | ||
164 | |||
165 | If there is no activity connection on BLE in 60 seconds, sensor will shut down BLE module to enter low power mode. | ||
166 | |||
167 | |||
168 | == 1.8 Pin Definitions , Switch & SIM Direction == | ||
169 | |||
170 | |||
171 | [[image:image-20240617104620-1.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 | |||
199 | See this link. [[How to insert SIM Card>>https://wiki.dragino.com/xwiki/bin/view/Main/General%20Manual%20for%20-CB%20%2C%20-CS%20models/#H2.AttachNetwork]]. | ||
200 | |||
201 | |||
202 | == 1.9 Hardware Variant == | ||
203 | |||
204 | |||
205 | (% border="1" cellspacing="3" style="width:410px" %) | ||
206 | |=(% 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 | ||
207 | |(% style="width:102px" %)((( | ||
208 | S31-CB | ||
209 | )))|(% style="width:126px" %)((( | ||
210 | (% style="text-align:center" %) | ||
211 | [[image:image-20230819110632-6.png||height="130" width="104"]] | ||
212 | )))|(% style="width:179px" %)((( | ||
213 | 1 x SHT31 Probe | ||
214 | |||
215 | Cable Length : 3 meters | ||
216 | |||
217 | |||
218 | ))) | ||
219 | |(% style="width:102px" %)((( | ||
220 | S31B-CB | ||
221 | )))|(% style="width:126px" %)((( | ||
222 | (% style="text-align:center" %) | ||
223 | [[image:image-20230819110702-7.png||height="164" width="90"]] | ||
224 | )))|(% style="width:179px" %)((( | ||
225 | 1 x SHT31 Probe | ||
226 | |||
227 | Installed in device. | ||
228 | ))) | ||
229 | |||
230 | (% style="display:none" %) | ||
231 | |||
232 | |||
233 | |||
234 | = 2. Use S31x-CB to communicate with IoT Server = | ||
235 | |||
236 | == 2.1 Send data to IoT server via NB-IoT/CAT-M1 network == | ||
237 | |||
238 | |||
239 | The S31x-CB is equipped with a NB-IoT module, the pre-loaded firmware in S31x-CB 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 S31x-CB. | ||
240 | |||
241 | |||
242 | Below shows the network structure: | ||
243 | |||
244 | [[image:image-20240611104604-2.png]] | ||
245 | |||
246 | |||
247 | There are two version: (% style="color:blue" %)**-GE**(%%) and (% style="color:blue" %)**-1T**(%%) version of S31x-CB. | ||
248 | |||
249 | |||
250 | (% 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 S31x-CB send data to IoT server. | ||
251 | |||
252 | * 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]]. | ||
253 | |||
254 | * 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]]. | ||
255 | |||
256 | Below shows result of different server as a glance. | ||
257 | |||
258 | (% border="1" cellspacing="3" style="width:515px" %) | ||
259 | |(% 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** | ||
260 | |(% 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" %)((( | ||
261 | (% style="text-align:center" %) | ||
262 | [[image:image-20230819113244-8.png||height="183" width="367"]] | ||
263 | )))|(% style="width:170px" %) | ||
264 | |(% 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" %)((( | ||
265 | (% style="text-align:center" %) | ||
266 | [[image:image-20230819113244-9.png||height="119" width="367"]] | ||
267 | )))|(% style="width:170px" %) | ||
268 | |(% 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" %) | ||
269 | |(% 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" %) | ||
270 | |(% 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" %) | ||
271 | |(% 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" %)((( | ||
272 | (% style="text-align:center" %) | ||
273 | [[image:image-20230819113244-10.png||height="104" width="367"]] | ||
274 | )))|(% style="width:170px" %) | ||
275 | |(% 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" %)((( | ||
276 | (% style="text-align:center" %) | ||
277 | [[image:image-20230819113244-11.png||height="141" width="367"]] | ||
278 | )))|(% style="width:170px" %) | ||
279 | |||
280 | (% style="color:blue" %)**1T Version**(%%): This version has 1NCE SIM card pre-installed and configure to send value to ThingsEye. User Just need to select the sensor type in ThingsEyeand Activate S31x-CB and user will be able to see data in ThingsEye. See here for [[ThingsEye Config Instruction>>url:https://wiki.thingseye.io/xwiki/bin/view/Main/]]. | ||
281 | |||
282 | |||
283 | == 2.2 Payload Types == | ||
284 | |||
285 | |||
286 | To meet different server requirement, S31x-CB supports different payload type. | ||
287 | |||
288 | **Includes:** | ||
289 | |||
290 | * [[General JSON format payload>>||anchor="H2.2.1GeneralJsonFormat28Type3D529"]]. (Type=5) | ||
291 | |||
292 | * [[HEX format Payload>>||anchor="H2.2.2HEXformatPayload28Type3D029"]]. (Type=0) | ||
293 | |||
294 | * [[ThingSpeak Format>>||anchor="H2.2.4ThingSpeakPayload28Type3D129"]]. (Type=1) | ||
295 | |||
296 | * [[ThingsBoard Format>>||anchor="H2.2.3ThingsBoardPayload28Type3D329"]]. (Type=3) | ||
297 | |||
298 | User can specify the payload type when choose the connection protocol. Example: | ||
299 | |||
300 | (% style="color:#037691" %)**AT+PRO=2,0** (%%) ~/~/ Use UDP Connection & hex Payload | ||
301 | |||
302 | (% style="color:#037691" %)**AT+PRO=2,5** (%%) ~/~/ Use UDP Connection & Json Payload | ||
303 | |||
304 | (% style="color:#037691" %)**AT+PRO=3,5 ** (%%) ~/~/ Use MQTT Connection & Json Payload | ||
305 | |||
306 | |||
307 | **Since firmware V1.0.4**, [[count mode>>||anchor="H3.27Workingmodeselection28SincefirmwareV1.0.429"]] has been added to S31x-CB, so paylaod adds count. | ||
308 | |||
309 | **Since firmware V1.1.0**, (% style="color:#4472c4" %)**IMSI**(%%) has been added to payload. | ||
310 | |||
311 | The following describes the latest payload. | ||
312 | |||
313 | (% style="color:red" %)**Note: The default is AT+GPS=0 ~/~/ The GPS function is not enabled. Therefore, the GPS collection time in the following example paylaod does not follow the system time, and the latitude and longitude are 0.** | ||
314 | |||
315 | |||
316 | === 2.2.1 General Json Format(Type~=5) === | ||
317 | |||
318 | |||
319 | This is the General Json Format. As below: | ||
320 | |||
321 | (% style="color:#4472c4" %)**{"IMEI":"868508065628110","IMSI":"460240210507481","Model":"S31x-CB","temperature":25.6,"humidity":52.5,"interrupt":0,"interrupt_level":0,"count":0,"battery":3.48,"signal":21,"time":"2024/12/03 03:24:54","latitude":0.000000,"longitude":0.000000,"gps_time":"1970-01-01T00:00:00Z","1":[24.2,52.5,"2024-12-02T05:34:19Z"],"2":[24.1,52.5,"2024-12-02T05:19:19Z"],"3":[24.1,52.6,"2024-12-02T05:04:19Z"],"4":[24.2,52.8,"2024-12-02T04:49:19Z"],"5":[24.3,52.0,"2024-12-02T04:34:19Z"],"6":[24.2,51.6,"2024-12-02T04:19:19Z"],"7":[24.5,50.2,"2024-12-02T03:39:02Z"],"8":[24.3,50.1,"2024-12-02T03:24:02Z"]}** | ||
322 | |||
323 | |||
324 | (% style="color:red" %)**Notice, from above payload:** | ||
325 | |||
326 | * Temperature, Humidity, Interrupt, Interrupt_level, Count, Battery, Signal, latitude, longitude & GPS time are the value at uplink time. | ||
327 | |||
328 | * Json entry 1 ~~ 8 are the last 1 ~~ 8 sampling data as specify by (% style="color:#037691" %)**AT+CLOCKLOG=1,65535,15,8 ** (%%)Command. Each entry includes (from left to right): Temperature, Humidity, Sampling time. | ||
329 | |||
330 | Example: | ||
331 | |||
332 | [[image:image-20241203113440-1.png||height="680" width="850"]] | ||
333 | |||
334 | |||
335 | === 2.2.2 HEX format Payload(Type~=0) === | ||
336 | |||
337 | |||
338 | This is the HEX Format. As below: | ||
339 | |||
340 | (% style="color:#4472c4" %)**f868508065628110f4602402105074814a6e0da01802Ffff0000000000000000000100020d674e7cb400000000000000000000000000f2020d674d46db00f1020d674d435700f1020e674d3fd300f20210674d3c4f00f30208674d38cb00f20204674d354700f501f6674d2bd600f301f5674d2852** | ||
341 | |||
342 | [[image:image-20241226084338-1.png||height="279" width="1762"]] | ||
343 | |||
344 | [[image:image-20240613142759-3.png]] | ||
345 | |||
346 | |||
347 | (% style="color:blue" %)**Device ID(f+IMEI): **(%%)f868508065628110 =868508065628110 | ||
348 | |||
349 | |||
350 | (% style="color:blue" %)**SIM Card ID(f+IMSI): **(%%)f460240210507481 =460240210507481 | ||
351 | |||
352 | |||
353 | (% style="color:blue" %)**Version:** | ||
354 | |||
355 | These bytes include the hardware and software version. | ||
356 | |||
357 | (% style="color:#037691" %)**Higher byte:**(%%) Specify Sensor Model: 0x4a for S31B-CB & S31-CB | ||
358 | |||
359 | (% style="color:#037691" %)**Lower byte:**(%%) Specify the software version: 0x6e=110, means firmware version 1.1.0 | ||
360 | |||
361 | |||
362 | (% style="color:blue" %)**BAT (Battery Info):** | ||
363 | |||
364 | Ex1: 0x0DC7 = 3527mV | ||
365 | |||
366 | |||
367 | (% style="color:blue" %)**Signal Strength:** | ||
368 | |||
369 | NB-IoT Network signal Strength. | ||
370 | |||
371 | **Ex1: 0x1f = 31** | ||
372 | |||
373 | **0** -113dBm or less | ||
374 | |||
375 | **1** -111dBm | ||
376 | |||
377 | **2...30** -109dBm... -53dBm | ||
378 | |||
379 | **31** -51dBm or greater | ||
380 | |||
381 | **99** Not known or not detectable | ||
382 | |||
383 | |||
384 | (% style="color:blue" %)**DS18B20_Temperature:** | ||
385 | |||
386 | **Example:** 0x00de(H)= 222(D) =22.2 ℃ | ||
387 | |||
388 | (% style="color:red" %)**Note:**(%%) If the DS18B20 sensor is not connected, the hex payload is **0xFFFF** and Serial port print: **-409.5 ℃.** | ||
389 | |||
390 | |||
391 | (% style="color:blue" %)**PA4_level:** | ||
392 | |||
393 | Level of PA4 pin. (0: Low level 1: High level) | ||
394 | |||
395 | |||
396 | (% style="color:blue" %)**Interrupt:** | ||
397 | |||
398 | This data field shows if this packet is generated by interrupt or not. | ||
399 | |||
400 | **Example:** | ||
401 | |||
402 | If byte[0]&0x01=0x00 : Normal uplink packet. | ||
403 | |||
404 | If byte[0]&0x01=0x01 : Interrupt Uplink Packet. | ||
405 | |||
406 | |||
407 | (% style="color:blue" %)**Interrupt_level:** | ||
408 | |||
409 | This byte shows whether the interrupt is triggered by a high or low level. | ||
410 | |||
411 | **Ex1:** 0x00 Interrupt triggered by falling edge (low level) | ||
412 | |||
413 | **Ex2: **0x01 Interrupt triggered by rising edge (high level) | ||
414 | |||
415 | |||
416 | (% style="color:blue" %)**Count:** | ||
417 | |||
418 | When using count mode, PB15 will accumulate counts each time it is triggered. | ||
419 | |||
420 | **Example: **0x00000064(H)= 100(D), So the count value is 100. | ||
421 | |||
422 | Use the **[[AT+CFGMOD>>||anchor="H3.27Workingmodeselection28SincefirmwareV1.0.429"]]** command to set the working mode to count mode. | ||
423 | |||
424 | Use **[[AT+EXT>>||anchor="H3.28SetCountvalue28SincefirmwareV1.0.429"]]** to set the count value. | ||
425 | |||
426 | |||
427 | (% style="color:blue" %)**Temperature: ** | ||
428 | |||
429 | If payload is: 0105H: (0105 & 8000 == 0), temp = 0105H /10 = 26.1 degree | ||
430 | |||
431 | If payload is: FF3FH : (FF3F & 8000 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees. | ||
432 | |||
433 | (FF3F & 8000: Judge whether the highest bit is 1, when the highest bit is 1, it is negative) | ||
434 | |||
435 | |||
436 | (% style="color:blue" %)**Humidity: ** | ||
437 | |||
438 | Read:0295(H)=661(D) Value: 661 / 10=66.1, So 66.1% | ||
439 | |||
440 | |||
441 | (% style="color:blue" %)**TimeStamp & GPS Timestamp** | ||
442 | |||
443 | Unit TimeStamp Example: 666A909F(H) = 1718259871(D) | ||
444 | |||
445 | Put the decimal value into this link(https:~/~/www.epochconverter.com/) to get the time. | ||
446 | |||
447 | |||
448 | (% style="color:blue" %)**Latitude:** | ||
449 | |||
450 | **Example: **0x015a7886(H)=22706310(D)=22.706150 | ||
451 | |||
452 | |||
453 | (% style="color:blue" %)**Longitude: ** | ||
454 | |||
455 | **Example: **0x06cf341e(H)=114242590(D)=114.242830 | ||
456 | |||
457 | |||
458 | === 2.2.3 ThingsBoard Payload(Type~=3) === | ||
459 | |||
460 | |||
461 | Type3 payload special design for ThingsBoard, it will also configure other default server to ThingsBoard. | ||
462 | |||
463 | (% style="color:#4472c4" %)**{ | ||
464 | "topic": "002_CB", | ||
465 | "payload": { | ||
466 | "IMEI": "868508065628110", | ||
467 | "IMSI": "460240210507481", | ||
468 | "Model": "S31x-CB", | ||
469 | "temperature": 23.7, | ||
470 | "humidity": 51.4, | ||
471 | "interrupt": 0, | ||
472 | "interrupt_level": 0, | ||
473 | "count": 0, | ||
474 | "battery": 3.15, | ||
475 | "signal": 25, | ||
476 | "time": "2024/12/09 03:35:07", | ||
477 | "latitude": 0.0, | ||
478 | "longitude": 0.0, | ||
479 | "gps_time": "1970-01-01T00:00:00Z", | ||
480 | "1": [130.0, 0.0, "2024-12-09T03:24:17Z"], | ||
481 | "2": [130.0, 0.0, "2024-12-09T03:02:32Z"], | ||
482 | "3": [130.0, 0.0, "2024-12-09T02:52:32Z"], | ||
483 | "4": [24.9, 53.3, "2024-12-04T09:10:54Z"], | ||
484 | "5": [25.1, 52.7, "2024-12-04T08:55:54Z"], | ||
485 | "6": [25.4, 52.0, "2024-12-04T08:40:54Z"], | ||
486 | "7": [25.8, 52.9, "2024-12-04T08:25:54Z"], | ||
487 | "8": [24.2, 52.5, "2024-12-04T08:10:54Z"] | ||
488 | } | ||
489 | }** | ||
490 | |||
491 | [[image:image-20241209113641-2.png]] | ||
492 | |||
493 | |||
494 | === 2.2.4 ThingSpeak Payload(Type~=1) === | ||
495 | |||
496 | |||
497 | This payload meets ThingSpeak platform requirement. It includes only four fields. Form 1~~6 are: | ||
498 | |||
499 | Temperature, Humidity, Battery, Signal, Latitude & Longitude. This payload type only valid for ThingsSpeak Platform. | ||
500 | |||
501 | As below: | ||
502 | |||
503 | (% style="color:#4472c4" %)**field1=Tem&field2=Hum&field3=BatV&field4=Singal&field5=latitude&field6=longitude** | ||
504 | |||
505 | [[image:image-20241025142930-2.png||height="809" width="841"]] | ||
506 | |||
507 | |||
508 | = 3. Configure S31x-CB = | ||
509 | |||
510 | == 3.1 Configure Methods == | ||
511 | |||
512 | |||
513 | S31x-CB supports below configure method: | ||
514 | |||
515 | * AT Command via Bluetooth Connection (**Recommended**): [[BLE Configure Instruction>>http://wiki.dragino.com/xwiki/bin/view/Main/BLE%20Bluetooth%20Remote%20Configure/]]. | ||
516 | |||
517 | * 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]]. | ||
518 | |||
519 | == 3.2 Serial Access Password == | ||
520 | |||
521 | |||
522 | After the Bluetooth or UART connection is successful, use the Serial Access Password to enter the AT command window. | ||
523 | |||
524 | The label on the box of the node will print the initial password: AT+PIN=**xxxxxx**, and directly use the six-digit password to access the AT instruction window. | ||
525 | |||
526 | [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/RS485-NB%2C-NS_RS485%2CUART_to_NB-IoT_Converter_User_Manual/WebHome/image-20250226165815-1.png?rev=1.1||alt="image-20250226165815-1.png"]] | ||
527 | |||
528 | |||
529 | If you need to change the password, use **AT+PWORD=**xxxxxx (6 characters), -CB nodes only support lowercase letters. | ||
530 | |||
531 | [[image:image-20240826183254-2.png]] | ||
532 | |||
533 | |||
534 | (% style="color:red" %)**Note: After entering the command, you need to add a line break, and you can also set automatic line breaks in the Bluetooth tool or UART connection tool.** | ||
535 | |||
536 | [[image:image-20240826183302-3.png]] | ||
537 | |||
538 | |||
539 | == 3.3 AT Commands Set == | ||
540 | |||
541 | |||
542 | AT+<CMD>? : Help on <CMD> | ||
543 | |||
544 | AT+<CMD> : Run <CMD> | ||
545 | |||
546 | AT+<CMD>=<value> : Set the value | ||
547 | |||
548 | AT+<CMD>=? : Get the value | ||
549 | |||
550 | |||
551 | (% style="color:blue" %)**General Commands** | ||
552 | |||
553 | AT+MODEL : Get module information | ||
554 | |||
555 | AT+CFGMOD : Working mode selection | ||
556 | |||
557 | AT+DEUI : Get or set the Device ID | ||
558 | |||
559 | AT+CFG : Print all settings | ||
560 | |||
561 | AT+SERVADDR: Get or Set the Server address | ||
562 | |||
563 | AT+TDC : Get or set the application data transmission interval in s | ||
564 | |||
565 | AT+INTMOD : Get or Set the trigger interrupt mode (0:input,1:falling or rising,2:falling,3:rising) | ||
566 | |||
567 | AT+APN : Get or set the APN | ||
568 | |||
569 | AT+5VT : Get or Set extend the time of 5V power | ||
570 | |||
571 | AT+PRO : Get or Set usage agreement (1:COAP,2:UDP,3:MQTT,4:TCP) | ||
572 | |||
573 | AT+RXDL : Get or Set the receiving time | ||
574 | |||
575 | AT+EXT : Get or Set Count value | ||
576 | |||
577 | AT+SHTEMP:Get or Set alarm of shtemp | ||
578 | |||
579 | AT+SHHUM:Get or Set alarm of shthum | ||
580 | |||
581 | AT+GETSENSORVALUE : Returns the current sensor measurement | ||
582 | |||
583 | AT+DNSCFG : Get or Set DNS Server | ||
584 | |||
585 | AT+CSQTIME : Get or Set the time to join the network | ||
586 | |||
587 | AT+GDNS : Get or Set the DNS | ||
588 | |||
589 | AT+SLEEP : Get or Set the sleep mode | ||
590 | |||
591 | AT+IPTYPE : Set the IPv4 or IPv6 | ||
592 | |||
593 | AT+QSW : Power on and power off BG95 module | ||
594 | |||
595 | AT+CLOCKLOG: Get or set SHT record time | ||
596 | |||
597 | AT+QBAND: Get or set Frequency Band | ||
598 | |||
599 | AT+IOTMOD: Configure Network Category to be Searched for under LTE RAT | ||
600 | |||
601 | AT+DOWNTE: Get or set the conversion between the standard version and 1T version downlinks | ||
602 | |||
603 | |||
604 | (% style="color:blue" %)**MQTT Management** | ||
605 | |||
606 | AT+CLIENT : Get or Set the MQTT clientID | ||
607 | |||
608 | AT+UNAME : Get or Set the MQTT Username | ||
609 | |||
610 | AT+PWD : Get or Set the MQTT password | ||
611 | |||
612 | AT+PUBTOPIC: Get or set MQTT publishing topic | ||
613 | |||
614 | AT+SUBTOPIC: Get or set MQTT subscription topic | ||
615 | |||
616 | AT+MQOS : Set the QoS level of MQTT | ||
617 | |||
618 | AT+TLSMOD : Get or Set the TLS mode | ||
619 | |||
620 | |||
621 | (% style="color:blue" %)**COAP Management** | ||
622 | |||
623 | AT+URI1: Get or set CoAP option 1 | ||
624 | |||
625 | AT+URI2: Get or set CoAP option 2 | ||
626 | |||
627 | AT+URI3: Get or set CoAP option 3 | ||
628 | |||
629 | AT+URI4: Get or set CoAP option 4 | ||
630 | |||
631 | AT+URI5: Get or set CoAP option 5 | ||
632 | |||
633 | AT+URI6: Get or set CoAP option 6 | ||
634 | |||
635 | AT+URI7: Get or set CoAP option 7 | ||
636 | |||
637 | AT+URI8: Get or set CoAP option 8 | ||
638 | |||
639 | |||
640 | (% style="color:blue" %)**GPS** | ||
641 | |||
642 | AT+GNSST : Extend the time to turn on GNSS | ||
643 | |||
644 | AT+GPS : Turn off and on GPS | ||
645 | |||
646 | AT+GTDC : Get or set GPS positioning interval in units of h | ||
647 | |||
648 | |||
649 | (% style="color:blue" %)**Information** | ||
650 | |||
651 | AT+FDR1 : Reset parameters to factory default values except for passwords | ||
652 | |||
653 | AT+FDR : Reset Parameters to Factory Default | ||
654 | |||
655 | AT+PWORD : Get or set the System password | ||
656 | |||
657 | AT+LDATA : Get the last upload data | ||
658 | |||
659 | AT+CDP : Read or Clear cached data | ||
660 | |||
661 | AT+PDTA: Print the sector data from start page to stop page | ||
662 | |||
663 | AT+PLDTA: Print the last few sets of data | ||
664 | |||
665 | AT+CLRDTA: Clear the storage, record position back to 1st | ||
666 | |||
667 | AT+GETLOG : Print serial port logs | ||
668 | |||
669 | ATZ : Trig a reset of the MCU | ||
670 | |||
671 | |||
672 | == 3.4 Test Uplink and Change Update Interval == | ||
673 | |||
674 | |||
675 | By default, Sensor will send uplinks **every 2 hours.** | ||
676 | |||
677 | User can use below commands to change the uplink interval. | ||
678 | |||
679 | (% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+TDC** (%%) | ||
680 | |||
681 | Example: AT+TDC=7200 ~/~/ Set Update Interval to 7200 seconds | ||
682 | |||
683 | (% style="color:blue" %)**Downlink Commands: **(% style="color:#037691" %)**0x01** | ||
684 | |||
685 | Format: Command Code (0x01) followed by 3 bytes. | ||
686 | |||
687 | Example: 12 hours= 43200 seconds 43200(D)=0xA8C0(H) | ||
688 | |||
689 | Downlink Payload: **01 00 A8 C0** ~/~/ AT+TDC=43200, Set Update Interval to 12 hours. | ||
690 | |||
691 | (% style="color:red" %)**Note: User can also push the button for more than 1 second to activate an uplink.** | ||
692 | |||
693 | |||
694 | == 3.5 Set the receiving time == | ||
695 | |||
696 | |||
697 | Feature: Extend the receiving time | ||
698 | |||
699 | (% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+RXDL** | ||
700 | |||
701 | Example: AT+RXDL=1000 ~/~/ Set the receiving time delay to 1000ms | ||
702 | |||
703 | (% style="color:blue" %)**Downlink Commands: **(% style="color:#037691" %)**0x03** | ||
704 | |||
705 | Format: Command Code (0x03) followed by 3 bytes. | ||
706 | |||
707 | Example: Downlink Payload: **03 00 03 E8 **~/~/ AT+RXDL=1000 | ||
708 | |||
709 | |||
710 | == 3.6 Reset == | ||
711 | |||
712 | |||
713 | Feature: Trig a reset of the MCU. | ||
714 | |||
715 | (% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**ATZ** | ||
716 | |||
717 | (% style="color:blue" %)**Downlink Commands: **(% style="color:#037691" %)**0x04FF** | ||
718 | |||
719 | |||
720 | == 3.7 +5V == | ||
721 | |||
722 | |||
723 | Feature: Set extend the time of 5V power. | ||
724 | |||
725 | (% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+5VT** | ||
726 | |||
727 | Example: AT+5VT=2000 ~/~/ Set extend the time of 5V power to 2000 ms | ||
728 | |||
729 | (% style="color:blue" %)**Downlink Commands: **(% style="color:#037691" %)**0x05** | ||
730 | |||
731 | Format: Command Code (0x05) followed by 3 bytes. | ||
732 | |||
733 | Example: Downlink Payload: **05 00 07 D0 **~/~/ AT+5VT=2000 | ||
734 | |||
735 | |||
736 | == 3.8 Trigger an uplink by external interrupt == | ||
737 | |||
738 | |||
739 | S31x-CB has an external trigger interrupt function. Users can use the PB15 pin to trigger the upload of data packets. | ||
740 | |||
741 | (% style="color:blue" %)**AT command:** | ||
742 | |||
743 | * (% style="color:#037691" %)**AT+INTMOD **(%%) ~/~/ Set the trigger interrupt mode | ||
744 | |||
745 | * (% style="color:#037691" %)**AT+INTMOD=0 **(%%) ~/~/ Disable Interrupt | ||
746 | |||
747 | * (% style="color:#037691" %)**AT+INTMOD=1 **(%%) ~/~/ Trigger by rising and falling edge | ||
748 | |||
749 | * (% style="color:#037691" %)**AT+INTMOD=2 **(%%) ~/~/ Trigger by falling edge | ||
750 | |||
751 | * (% style="color:#037691" %)**AT+INTMOD=3 **(%%) ~/~/ Trigger by rising edge | ||
752 | |||
753 | (% style="color:blue" %)**Downlink Commands: **(% style="color:#037691" %)**0x06** | ||
754 | |||
755 | Format: Command Code (0x06) followed by 3 bytes. | ||
756 | |||
757 | Example1: Downlink Payload: **06 00 00 01 **~/~/ AT+INTMOD=1 | ||
758 | |||
759 | Example2: Downlink Payload: **06 00 00 03 **~/~/ AT+INTMOD=3 | ||
760 | |||
761 | |||
762 | == 3.9 Set the QoS level == | ||
763 | |||
764 | |||
765 | This command is used to set the QoS level of **MQTT**. | ||
766 | |||
767 | (% style="color:blue" %)**AT command:** | ||
768 | |||
769 | * (% style="color:#037691" %)**AT+MQOS=xx**(%%)** **~/~/ 0~~2 | ||
770 | |||
771 | (% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x07(%%)** | ||
772 | |||
773 | Format: Command Code (0x07) followed by 1 byte. | ||
774 | |||
775 | **Ex1:** Downlink payload: **0x0700** ~/~/ AT+MQOS=0 | ||
776 | |||
777 | **Ex2:** Downlink payload: **0x0701** ~/~/ AT+MQOS=1 | ||
778 | |||
779 | |||
780 | == 3.10 Clock logging == | ||
781 | |||
782 | |||
783 | 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. | ||
784 | |||
785 | 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. | ||
786 | |||
787 | (% style="color:blue" %)**AT command:**(%%)** (% style="color:#037691" %)AT+CLOCKLOG=a,b,c,d(%%)** | ||
788 | |||
789 | (% style="color:#037691" %)**a: **(%%)**0:** Disable Clock logging. ** 1: **Enable Clock Logging | ||
790 | |||
791 | (% 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. | ||
792 | |||
793 | (% style="color:#037691" %)**c: **(%%)Specify the sampling interval: range **(0 ~~ 255 minutes)** | ||
794 | |||
795 | (% style="color:#037691" %)**d:**(%%)** **How many entries should be uplink on every TDC **(max 32)** | ||
796 | |||
797 | (% style="color:red" %)**Note: To disable clock recording, set the following parameters: AT+CLOCKLOG=1,65535,0,0** | ||
798 | |||
799 | [[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"]] | ||
800 | |||
801 | **Example:** | ||
802 | |||
803 | **AT+CLOCKLOG=1,65535,1,5** | ||
804 | |||
805 | 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). | ||
806 | |||
807 | (% class="wikigeneratedid" %) | ||
808 | [[image:image-20240620104257-1.png||height="676" width="1264"]] | ||
809 | |||
810 | (% class="wikigeneratedid" %) | ||
811 | (% 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.** | ||
812 | |||
813 | (% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x08(%%)** | ||
814 | |||
815 | Format: Command Code (0x08) followed by 5 bytes. | ||
816 | |||
817 | * **Example 1**: Downlink Payload:** 08 01 FFFF 0F 08** ~/~/ Set SHT record time: AT+CLOCKLOG=1,65535,15,8 | ||
818 | * **Example 2**: Downlink Payload:** 08 01 04B0 0F 08** ~/~/ Set SHT record time: AT+CLOCKLOG=1,1200,15,8 | ||
819 | |||
820 | (% style="color:red" %)**Note: When entering the downlink payload, there must be no Spaces between bytes.** | ||
821 | |||
822 | |||
823 | == 3.11 Set the TLS mode == | ||
824 | |||
825 | |||
826 | Refer to this link ([[MQTT Connection to send data to Tago.io>>http://wiki.dragino.com/xwiki/bin/view/Main/General%20Manual%20for%20-CB%20%2C%20-CS%20models/#H3.7Tago.io28viaMQTT29]])to use the TLS mode. | ||
827 | |||
828 | (% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+TLSMOD** | ||
829 | |||
830 | **Example 1: ** AT+TLSMOD=0,0 ~/~/ Disable TLS Mode. | ||
831 | |||
832 | **Example 2:** AT+TLSMOD=1,0 ~/~/ No authentication | ||
833 | |||
834 | AT+TLSMOD=1,1 ~/~/ Perform server authentication | ||
835 | |||
836 | AT+TLSMOD=1,2 ~/~/ Perform server and client authentication if requested by the remote server | ||
837 | |||
838 | (% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x09(%%)** | ||
839 | |||
840 | Format: Command Code (0x09) followed by 2 bytes. | ||
841 | |||
842 | Example1: Downlink Payload: **09 00 00 **~/~/ AT+TLSMOD=0,0 | ||
843 | |||
844 | Example2: Downlink Payload: **09 01 02 **~/~/ AT+TLSMOD=1,2 | ||
845 | |||
846 | |||
847 | == 3.12 Set GNSS open time == | ||
848 | |||
849 | |||
850 | Extend the time to turn on GNSS. The automatic GPS location time is extended when the node is activated. | ||
851 | |||
852 | (% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+GNSST** | ||
853 | |||
854 | Example: AT+GNSST=30 ~/~/ Set the GPS positioning time to 30 seconds | ||
855 | |||
856 | (% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x10(%%)** | ||
857 | |||
858 | Format: Command Code (0x10) followed by 2 bytes. | ||
859 | |||
860 | Example: Downlink Payload: **10 00 1E **~/~/ AT+GNSST=30 | ||
861 | |||
862 | |||
863 | == 3.13 Turn on/off GPS == | ||
864 | |||
865 | |||
866 | (% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+GPS ** | ||
867 | |||
868 | **Ex1: **AT+GPS=0 ~/~/ Turn off GPS | ||
869 | |||
870 | **Ex2: **AT+GPS=1 ~/~/ Turn on GPS | ||
871 | |||
872 | (% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x11(%%)** | ||
873 | |||
874 | Format: Command Code (0x11) followed by 1 byte. | ||
875 | |||
876 | Example: Downlink Payload: **11 01 **~/~/ AT+GPS=1 | ||
877 | |||
878 | |||
879 | == 3.14 Set GPS positioning interval == | ||
880 | |||
881 | |||
882 | Feature: Set GPS positioning interval (unit: hour). | ||
883 | |||
884 | When GPS is enabled, the node automatically locates and uplinks each time it passes **GTDC time** after activation. | ||
885 | |||
886 | (% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+GTDC** | ||
887 | |||
888 | Example: AT+GTDC=24 ~/~/ Set the GPS positioning interval to 24h. | ||
889 | |||
890 | (% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x12(%%)** | ||
891 | |||
892 | Format: Command Code (0x12) followed by 3 bytes. | ||
893 | |||
894 | Example: 24 hours: 24(D)=0x18(H) | ||
895 | |||
896 | Downlink Payload: **12 00 00 18 **~/~/ AT+GTDC=24 | ||
897 | |||
898 | |||
899 | == 3.15 Set the search network time == | ||
900 | |||
901 | |||
902 | Feature: Get or Set the time to join the network(unit: minutes). | ||
903 | |||
904 | (% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+CSQTIME** | ||
905 | |||
906 | Example: AT+CSQTIME=10 ~/~/ Set the search time to 10 minutes. | ||
907 | |||
908 | (% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x13(%%)** | ||
909 | |||
910 | Format: Command Code (0x13) followed by 1 byte. | ||
911 | |||
912 | Example: Downlink Payload: **13 0A **~/~/ AT+CSQTIME=10 | ||
913 | |||
914 | |||
915 | == 3.16 Humidity and Temperature alarm function == | ||
916 | |||
917 | |||
918 | On each sampling define by AT+CLOCKLOG=1,65535,(% style="color:red" %)**15**(%%),8 ( default 15 minutes), when the value exceed the range, it will trigger an Alarm and immediately sends a uplink. | ||
919 | |||
920 | (% style="color:blue" %)**AT Command:** | ||
921 | |||
922 | (% style="color:#037691" %)**AT+ SHTEMP=min,max** | ||
923 | |||
924 | SHTTEMP must be -40 to 125. | ||
925 | |||
926 | Example: AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20 or higher than 30 | ||
927 | |||
928 | (% style="color:#037691" %)**AT+ SHHUM=min,max** | ||
929 | |||
930 | Example: AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50 or higher than 80. | ||
931 | |||
932 | |||
933 | (% style="color:blue" %)**Downlink Commands: **(% style="color:#037691" %)**0x0A** | ||
934 | |||
935 | Format: Command Code (0x0A) followed by 4 bytes. | ||
936 | |||
937 | The first and second bytes following the function code are the minimum and maximum value of **SHTEMP**, and the third and fourth bytes are the minimum and maximum value of **SHHUM**. | ||
938 | |||
939 | * **Example 1**: Downlink Payload:** 0A 14 1E 32 50** ~/~/ AT+ SHTEMP=20,30 & AT+ SHHUM=50,80 | ||
940 | * **Example 2**: Downlink Payload:** 0A 00 00 00 00 ** ~/~/ disable temperature and humidity alarm. | ||
941 | |||
942 | For **negative payload temperature**, calculate it as follows: **65536+ temperature = FFaa**, the value is **aa**. | ||
943 | |||
944 | * **Example**: -40℃: 65536+(-40)=65496(D)=FFD8(H), Therefore, select a numerical representation of D8 as -40 ℃ for the downlink payload. | ||
945 | |||
946 | (% style="color:red" %)**Notice:** | ||
947 | |||
948 | * To disable Alarm, user can set min and max to same value , such as (% style="color:#037691" %)**AT+SHTEMP=0,0 and AT+SHHUM=50,50** | ||
949 | * 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=-40,0**(%%)(Alarm above 0 degrees Celsius). | ||
950 | |||
951 | == 3.17 Set the IPv4 or IPv6 == | ||
952 | |||
953 | |||
954 | This command is used to set IP version. | ||
955 | |||
956 | (% style="color:blue" %)**AT command:** | ||
957 | |||
958 | * (% style="color:#037691; font-weight:bold" %)**AT+IPTYPE**(% style="color:#037691" %)**=1**(%%)** **~/~/ IPv4 | ||
959 | * (% style="color:#037691; font-weight:bold" %)**AT+IPTYPE**(% style="color:#037691" %)**=2**(%%)** **~/~/ IPv6 | ||
960 | |||
961 | == 3.18 Configure Network Category to be Searched for under LTE RAT. == | ||
962 | |||
963 | |||
964 | (% style="color:blue" %)**AT command:**(%%)** (% style="color:#037691" %)AT+IOTMOD=xx(%%)** | ||
965 | |||
966 | (% style="color:#037691" %)**xx:**(%%) **0:** eMTC | ||
967 | |||
968 | **1:** NB-IoT | ||
969 | |||
970 | **2:** eMTC and NB-IoT | ||
971 | |||
972 | |||
973 | == 3.19 Factory data reset == | ||
974 | |||
975 | |||
976 | Two different restore factory Settings configurations. | ||
977 | |||
978 | (% style="color:blue" %)**AT command:** | ||
979 | |||
980 | * (% style="color:#037691; font-weight:bold" %)**AT+FDR**(%%)** **~/~/ Reset Parameters to Factory Default. | ||
981 | * (% style="color:#037691; font-weight:bold" %)**AT+FDR1**(%%)** **~/~/ Reset parameters to factory default values **except for passwords**. | ||
982 | |||
983 | == 3.20 Set CoAP option == | ||
984 | |||
985 | |||
986 | Feature: Set CoAP option, follow this link to set up the CoaP protocol. | ||
987 | |||
988 | (% style="color:blue" %)**AT command: **(% style="color:#037691; font-weight:bold" %)**AT+URI1~~AT+URI8** | ||
989 | |||
990 | (% style="color:#037691; font-weight:bold" %)**AT+URI1=11,"i" **(%%)~/~/ "i/" indicates that the endpoint supports observation mode. In -CB products, fixed setting AT+URI1=11,"i" | ||
991 | |||
992 | (% style="color:#037691; font-weight:bold" %)**AT+URI2=11,"CoAP endpoint URl" **(%%)~/~/ 11 is a fixed parameter. | ||
993 | |||
994 | **Example: ** i/13a35fbe-9515-6e55-36e8-081fb6aacf86 | ||
995 | |||
996 | AT+URI1=11,"i" | ||
997 | |||
998 | AT+URI2=11,"13a35fbe-9515-6e55-36e8-081fb6aacf86" | ||
999 | |||
1000 | ~-~-> If multiple groups of CoAP endpoint urls: | ||
1001 | |||
1002 | AT+URI3=11,"i" | ||
1003 | |||
1004 | AT+URI4=11,"CoAP endpoint URl" | ||
1005 | |||
1006 | |||
1007 | == 3.21 Power on / power off BG95 module == | ||
1008 | |||
1009 | |||
1010 | This command is used to power on and power off BG95 module. | ||
1011 | |||
1012 | * (% style="color:blue" %)**AT command: **(% style="color:#037691" %)**AT+QSW** | ||
1013 | |||
1014 | The module is powered on after the command is sent for the first time, and powered off after the command is sent again. | ||
1015 | |||
1016 | [[image:image-20240619155719-1.png||height="644" width="811"]] | ||
1017 | |||
1018 | |||
1019 | == 3.22 Example Query saved historical records == | ||
1020 | |||
1021 | |||
1022 | * (% style="color:blue" %)**AT command:**(%%)** (% style="color:#037691" %)AT+CDP(%%)** | ||
1023 | |||
1024 | 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. | ||
1025 | |||
1026 | (% class="wikigeneratedid" %) | ||
1027 | [[image:image-20240619163800-2.png||height="642" width="826"]] | ||
1028 | |||
1029 | |||
1030 | == 3.23 Uplink log query == | ||
1031 | |||
1032 | |||
1033 | * (% style="color:blue" %)**AT command:**(%%)** (% style="color:#037691" %)AT+GETLOG(%%)** | ||
1034 | |||
1035 | This command can be used to query upstream logs of data packets. | ||
1036 | |||
1037 | [[image:image-20240619163835-3.png||height="637" width="827"]] | ||
1038 | |||
1039 | |||
1040 | == 3.24 Print last few data entries == | ||
1041 | |||
1042 | |||
1043 | Feature: Print the last few data entries | ||
1044 | |||
1045 | (% style="color:blue" %)**AT command: **(% style="color:#037691" %)**AT+PLDTA** | ||
1046 | |||
1047 | (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %) | ||
1048 | |=(% style="width: 168px; background-color: rgb(79, 129, 189); color: white;" %)**Command Example**|=(% style="width: 342px; background-color: rgb(79, 129, 189); color: white;" %)**4 bytes** | ||
1049 | |(% style="width:148px" %)AT+PLDTA=5 | ||
1050 | Print last 5 entries|(% style="width:169px" %)((( | ||
1051 | Stop Tx events when read sensor data | ||
1052 | |||
1053 | 1 24/9/20 23:31:37 temp=29.4 hum=70.4 | ||
1054 | |||
1055 | 2 24/9/20 23:46:33 temp=29.4 hum=71.2 | ||
1056 | |||
1057 | 3 24/9/21 00:01:33 temp=29.4 hum=71.0 | ||
1058 | |||
1059 | 4 24/9/21 00:16:47 temp=29.5 hum=71.3 | ||
1060 | |||
1061 | 5 24/9/21 00:31:33 temp=27.5 hum=68.0 | ||
1062 | |||
1063 | Start Tx events | ||
1064 | |||
1065 | |||
1066 | OK | ||
1067 | ))) | ||
1068 | |||
1069 | (% style="color:blue" %)**Downlink Command: ** | ||
1070 | |||
1071 | No downlink commands for feature | ||
1072 | |||
1073 | |||
1074 | == 3.25 Print data entries base on page == | ||
1075 | |||
1076 | |||
1077 | Feature: Print the sector data from start page to stop page. | ||
1078 | |||
1079 | (% style="color:blue" %)**AT command: **(% style="color:#037691" %)**AT+PDTA** | ||
1080 | |||
1081 | (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %) | ||
1082 | |=(% style="width: 168px; background-color: rgb(79, 129, 189); color: white;" %)**Command Example**|=(% style="width: 342px; background-color: rgb(79, 129, 189); color: white;" %)**4 bytes** | ||
1083 | |(% style="width:148px" %)AT+PDTA=1,1 | ||
1084 | Print page 1 to 1|(% style="width:169px" %)((( | ||
1085 | Stop Tx events when read sensor data | ||
1086 | |||
1087 | 8028B00 24/9/20 10:31:33 temp=25.3 hum=60.0 | ||
1088 | |||
1089 | 8028B08 24/9/20 10:46:33 temp=25.3 hum=59.0 | ||
1090 | |||
1091 | 8028B10 24/9/20 11:01:33 temp=25.1 hum=59.3 | ||
1092 | |||
1093 | 8028B18 24/9/20 11:16:33 temp=25.0 hum=60.7 | ||
1094 | |||
1095 | 8028B20 24/9/20 11:31:33 temp=24.9 hum=61.4 | ||
1096 | |||
1097 | 8028B28 24/9/20 11:46:33 temp=24.7 hum=60.6 | ||
1098 | |||
1099 | 8028B30 24/9/20 12:01:33 temp=24.8 hum=60.8 | ||
1100 | |||
1101 | 8028B38 24/9/20 12:16:33 temp=24.6 hum=61.0 | ||
1102 | |||
1103 | 8028B40 24/9/20 12:31:33 temp=24.5 hum=60.8 | ||
1104 | |||
1105 | 8028B48 24/9/20 12:46:33 temp=24.6 hum=60.5 | ||
1106 | |||
1107 | 8028B50 24/9/20 13:01:33 temp=25.1 hum=60.5 | ||
1108 | |||
1109 | 8028B58 24/9/20 13:16:33 temp=26.4 hum=61.3 | ||
1110 | |||
1111 | 8028B60 24/9/20 13:31:33 temp=27.0 hum=61.9 | ||
1112 | |||
1113 | 8028B68 24/9/20 13:46:33 temp=27.4 hum=62.3 | ||
1114 | |||
1115 | 8028B70 24/9/20 14:01:33 temp=27.6 hum=62.6 | ||
1116 | |||
1117 | 8028B78 24/9/20 14:16:33 temp=27.8 hum=63.4 | ||
1118 | |||
1119 | Start Tx events | ||
1120 | |||
1121 | OK | ||
1122 | ))) | ||
1123 | |||
1124 | (% style="color:blue" %)**Downlink Command: ** | ||
1125 | |||
1126 | No downlink commands for feature | ||
1127 | |||
1128 | |||
1129 | == 3.26 Clear Flash Record == | ||
1130 | |||
1131 | |||
1132 | Feature: Clear flash storage for data log feature. | ||
1133 | |||
1134 | (% style="color:blue" %)**AT command: **(% style="color:#037691" %)**AT+CLRTDA** | ||
1135 | |||
1136 | (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %) | ||
1137 | |=(% style="width: 160px; background-color: rgb(79, 129, 189); color: white;" %)**Command Example**|=(% style="width: 130px; background-color: rgb(79, 129, 189); color: white;" %)**Function**|=(% style="width: 220px; background-color: rgb(79, 129, 189); color: white;" %)**Response** | ||
1138 | |(% style="width:160px" %)AT+CLRDTA |(% style="width:130px" %)((( | ||
1139 | Clear date record | ||
1140 | )))|(% style="width:213px" %)((( | ||
1141 | Stop Tx events,Please wait for the erase to complete | ||
1142 | |||
1143 | Clear all stored sensor data... | ||
1144 | |||
1145 | Start Tx events | ||
1146 | |||
1147 | OK | ||
1148 | ))) | ||
1149 | |||
1150 | (% style="color:blue" %)**Downlink Command: **(% style="color:#037691" %)**0x32** | ||
1151 | |||
1152 | * Example: 0x32 00 ~/~/ Same as AT+CLRDTA | ||
1153 | |||
1154 | == 3.27 Working mode selection(Since firmware V1.0.4) == | ||
1155 | |||
1156 | |||
1157 | Feature: Set interrupt mode or count mode (PB15 pin). | ||
1158 | |||
1159 | (% style="color:blue" %)**AT command: **(% style="color:#037691" %)**AT+CFGMOD** | ||
1160 | |||
1161 | (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:470px" %) | ||
1162 | |=(% style="width: 191px; background-color: rgb(79, 129, 189); color: white;" %)**Command Example**|=(% style="width: 279px; background-color: rgb(79, 129, 189); color: white;" %)**Function** | ||
1163 | |(% style="width:191px" %)AT+CFGMOD=1|(% style="width:277px" %)((( | ||
1164 | Interrupt mode (default mode) | ||
1165 | ))) | ||
1166 | |(% style="width:191px" %)AT+CFGMOD=2|(% style="width:277px" %)count mode | ||
1167 | |||
1168 | (% style="color:blue" %)**Downlink Command: **(% style="color:#037691" %)**0x02** | ||
1169 | |||
1170 | * Downlink command: 02 01 ~/~/ Equal to AT+CFGMOD=1 | ||
1171 | * Downlink command: 02 02 ~/~/ Equal to AT+CFGMOD=2 | ||
1172 | |||
1173 | == 3.28 Set Count value(Since firmware V1.0.4) == | ||
1174 | |||
1175 | |||
1176 | Feature: Set the count value of PB15. | ||
1177 | |||
1178 | (% style="color:blue" %)**AT command: **(% style="color:#037691" %)**AT+EXT** | ||
1179 | |||
1180 | (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:470px" %) | ||
1181 | |=(% style="width: 157px; background-color: rgb(79, 129, 189); color: white;" %)**Command Example**|=(% style="width: 211px; background-color: rgb(79, 129, 189); color: white;" %)**Function**|=(% style="width: 102px; background-color: rgb(79, 129, 189); color: white;" %)**Response** | ||
1182 | |(% style="width:157px" %)AT+EXT=?|(% style="width:211px" %)Show current count value.|(% style="width:110px" %)((( | ||
1183 | 0 (default) | ||
1184 | |||
1185 | OK | ||
1186 | ))) | ||
1187 | |(% style="width:157px" %)AT+EXT=100|(% style="width:211px" %)Set the count value to 100.|(% style="width:110px" %)OK | ||
1188 | |||
1189 | (% style="color:blue" %)**Downlink Command: **(% style="color:#037691" %)**0x0B** | ||
1190 | |||
1191 | Format: Command Code (0x0B) followed by 4 bytes. | ||
1192 | |||
1193 | * Downlink command: 0B 00 00 00 00 ~/~/ Set the count value to 0 | ||
1194 | * Downlink command: 0B 00 00 00 64 ~/~/ Set the count value to 100 | ||
1195 | |||
1196 | == 3.29 Set the downlink debugging mode(Since firmware v1.1.0) == | ||
1197 | |||
1198 | |||
1199 | Feature: Set the conversion between the standard version and 1T version downlinks. | ||
1200 | |||
1201 | (% style="color:blue" %)**AT command: AT+DOWNTE** | ||
1202 | |||
1203 | (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %) | ||
1204 | |=(% style="width: 134px; background-color: rgb(79, 129, 189); color: white;" %)**Command Example**|=(% style="width: 143px; background-color: rgb(79, 129, 189); color: white;" %)**Function/Parameters**|=(% style="width: 233px; background-color: rgb(79, 129, 189); color: white;" %)**Response/Explanation** | ||
1205 | |(% style="width:134px" %)AT+DOWNTE=?|(% style="width:143px" %)Get current Settings|(% style="width:229px" %)((( | ||
1206 | 0,0 (default) | ||
1207 | |||
1208 | OK | ||
1209 | ))) | ||
1210 | |(% colspan="1" rowspan="2" style="width:134px" %)((( | ||
1211 | |||
1212 | |||
1213 | |||
1214 | |||
1215 | AT+DOWNTE=a,b | ||
1216 | )))|(% style="width:143px" %)**a**: Set the conversion between the downlink of the standard version and 1T version|(% style="width:229px" %)((( | ||
1217 | **0**: Set the downlink of the standard version. | ||
1218 | **1**: Set the downlink of the 1T version(ThingsEye platform) | ||
1219 | ))) | ||
1220 | |(% style="width:143px" %)**b**: Enable/Disable downlink debugging|(% style="width:229px" %)((( | ||
1221 | **0**: Disable downlink debugging mode. | ||
1222 | **1**: Enable downlink debugging mode, users can see the original downlink reception. | ||
1223 | ))) | ||
1224 | |||
1225 | **Example:** | ||
1226 | |||
1227 | * AT+DOWNTE=0,1 ~/~/ Set to standard version downlink, and enable downlink debugging. | ||
1228 | * AT+DOWNTE=1,1 ~/~/ Set to 1T version downlink, and enable downlink debugging. | ||
1229 | |||
1230 | (% style="color:blue" %)**Downlink Command: ** | ||
1231 | |||
1232 | No downlink commands for feature | ||
1233 | |||
1234 | |||
1235 | = 4. Battery & Power Consumption = | ||
1236 | |||
1237 | |||
1238 | S31x-CB use ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace. | ||
1239 | |||
1240 | [[**Battery Info & Power Consumption Analyze**>>http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] . | ||
1241 | |||
1242 | |||
1243 | Please refer to the following instructions to ask the AI to let the AI intelligence help the user to calculate the battery life. | ||
1244 | |||
1245 | Ex1: | ||
1246 | |||
1247 | The S31x-CB using ER26500 + SPC1520 8500mAh battery packs. | ||
1248 | |||
1249 | ~1. CB version of AI questioning techniques: | ||
1250 | |||
1251 | Battery capacity is 8500mAh, self-discharge <2%/year | ||
1252 | Sleep current: 19.618uA | ||
1253 | Sampling current&Duration: 20mA. 10 seconds | ||
1254 | UDP Transmit/Receive Current & Duration: 58mA, 36 sec. | ||
1255 | MQTT protocol transmit current & duration: 63mA, 41 seconds | ||
1256 | TCP protocol transmit current & duration: 62mA, 41 seconds | ||
1257 | GSP positioning current & duration: 87.0756mA, 44.162 seconds | ||
1258 | Timed Acquisition Current & Duration: 8.78151mA, 0.125338s | ||
1259 | Acquisition every 120 minutes, launching once, GPS positioning once a day ,15 minutes timed acquisition once | ||
1260 | How many years can the battery be used in different transmission modes? | ||
1261 | |||
1262 | [[image:image-20250313105906-6.png]] | ||
1263 | |||
1264 | Example: | ||
1265 | Every 120 minutes to collect once, transmit once, GPS positioning once a day , 15 minutes timed collection once | ||
1266 | How many years can the battery be used in different transmission modes? | ||
1267 | |||
1268 | AI will automatically help the user to calculate the average power consumption and battery life of the device for each packet sent, as shown below: | ||
1269 | |||
1270 | [[image:image-20250314084804-1.png||height="1828" width="557"]] | ||
1271 | |||
1272 | |||
1273 | The S31x-CS uses a 3000mAh Li-Ion battery, please refer to the following instructions to ask the AI to let the AI intelligence help users calculate the battery life. | ||
1274 | |||
1275 | 2.CS version of AI questioning techniques: | ||
1276 | |||
1277 | Battery capacity is 8500mAh, self-discharge <2%/year | ||
1278 | Sleep current: 50.409uA | ||
1279 | Sampling current&Duration: 20mA. 10 seconds | ||
1280 | UDP Transmit/Receive Current & Duration: 58mA, 36 seconds. | ||
1281 | MQTT protocol transmit current & duration: 63mA, 41 seconds | ||
1282 | TCP protocol transmit current & duration: 62mA, 41 seconds | ||
1283 | GSP positioning current & duration: 87.0756mA, 44.162 seconds | ||
1284 | Timed Acquisition Current & Duration: 8.78151mA, 0.125338 seconds | ||
1285 | Acquisition every 120 minutes, launching once, GPS positioning once a day ,15 minutes timed acquisition once | ||
1286 | How many years can the battery be used in different transmission modes? | ||
1287 | |||
1288 | [[image:image-20250313105516-3.png]] | ||
1289 | |||
1290 | Example: | ||
1291 | Every 120 minutes to collect once, transmit once, GPS positioning once a day , 15 minutes timed collection once | ||
1292 | How many years can the battery be used in different transmission modes? | ||
1293 | |||
1294 | AI will automatically help the user to calculate the average power consumption and battery life of the device for each packet sent, as shown below: | ||
1295 | |||
1296 | [[image:image-20250314093630-2.png||height="1621" width="523"]] | ||
1297 | |||
1298 | = 5. Firmware update = | ||
1299 | |||
1300 | |||
1301 | User can change device firmware to:: | ||
1302 | |||
1303 | * Update with new features. | ||
1304 | |||
1305 | * Fix bugs. | ||
1306 | |||
1307 | Firmware and changelog can be downloaded from : **[[Firmware download link>>https://www.dropbox.com/scl/fo/1mzflb9p9kx15btnc11gr/AEfB-kKqgjZnzN6CA56bO3U/S31x-CB?dl=0&rlkey=ku98jt8u30coqy66saebai2co&subfolder_nav_tracking=1]]** | ||
1308 | |||
1309 | Methods to Update Firmware: | ||
1310 | |||
1311 | * (Recommended way) OTA firmware update via BLE: [[**Instruction**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/BLE_Firmware_Update_NB_Sensors_BC660K-GL/]]. | ||
1312 | |||
1313 | * Update through UART TTL interface : **[[Instruction>>http://wiki.dragino.com/xwiki/bin/view/Main/UART_Access_for_NB_ST_BC660K-GL/#H4.2UpdateFirmware28Assumethedevicealreadyhaveabootloader29]]**. | ||
1314 | |||
1315 | = 6. FAQ = | ||
1316 | |||
1317 | == 6.1 How can I access the BG95-NGFF AT Commands? == | ||
1318 | |||
1319 | |||
1320 | |||
1321 | User can access to BG95-NGFF directly and send AT Commands. | ||
1322 | |||
1323 | [[See BG95-NGFF AT Command set>>https://www.dropbox.com/scl/fo/1mzflb9p9kx15btnc11gr/ALDWTvDjuVoXvDJuYWCRh5U/Vendor%20Datasheet/BG95?dl=0&rlkey=ku98jt8u30coqy66saebai2co&subfolder_nav_tracking=1]] | ||
1324 | |||
1325 | |||
1326 | == 6.2 General Manual for -CB , -CS models == | ||
1327 | |||
1328 | |||
1329 | Users can follow the instructions in this [[link>>http://wiki.dragino.com/xwiki/bin/view/Main/General%20Manual%20for%20-CB%20%2C%20-CS%20models/]] to see how to configure to connect to different servers. | ||
1330 | |||
1331 | |||
1332 | = 7. Order Info = | ||
1333 | |||
1334 | |||
1335 | Part Number: (% style="color:blue" %)**S31-CB-XX / S31B-CB-XX** | ||
1336 | |||
1337 | (% style="color:red" %)**XX:**(%%) | ||
1338 | |||
1339 | * (% style="color:#037691" %)**GE**(%%): General version ( Exclude SIM card) | ||
1340 | |||
1341 | * (% style="color:#037691" %)**1T**(%%): with 1NCE* 10 years 500MB SIM card and Pre-configure to ThingsEye server | ||
1342 | |||
1343 | (% style="color:#037691" %)**1NCE SIM Card **(% style="color:red" %)**NB-IoT**(% style="color:#037691" %)** 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. | ||
1344 | |||
1345 | (% style="color:#037691" %)**1NCE SIM Card **(% style="color:red" %)**LTE-M **(% style="color:#037691" %)**network coverage**(%%): Argentina, Austria, Australia, Belgium, Canada, Denmark, Estonia, Finland, France, Germany, Great Britain, Hungary, Ireland, Japan, Jersey, Korea, Repiblic of, Latvia, Luxembourg, Mexico, Netherlands, New Zealand, Norway, Poland, Puerto Rico, Romania, Spain, Sweden, Switzerland, Taiwan, USA, US Virgin Islands. | ||
1346 | |||
1347 | |||
1348 | = 8. Packing Info = | ||
1349 | |||
1350 | |||
1351 | (% style="color:#037691" %)**Package Includes**: | ||
1352 | |||
1353 | * S31-CB or S31-CB Temperature & Humidity Sensor x 1 | ||
1354 | |||
1355 | * External antenna x 1 | ||
1356 | |||
1357 | (% style="color:#037691" %)**Dimension and weight**: | ||
1358 | |||
1359 | * Device Size: 13.0 x 5 x 4.5 cm | ||
1360 | |||
1361 | * Device Weight: 150g | ||
1362 | |||
1363 | * Package Size / pcs : 14.0 x 8x 5 cm | ||
1364 | |||
1365 | * Weight / pcs : 180g | ||
1366 | |||
1367 | = 9. Support = | ||
1368 | |||
1369 | |||
1370 | * 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. | ||
1371 | |||
1372 | * 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]]. | ||
1373 | |||
1374 | (% style="display:none" %) (%%) |