Version 205.1 by Mengting Qiu on 2025/05/05 10:44

Show last authors
1 (% style="text-align:center" %)
2 [[image:image-20250118092740-4.png]]
3
4
5
6
7
8
9
10 **Table of Contents :**
11
12 {{toc/}}
13
14
15
16
17
18
19 = 1. Introduction =
20
21 == 1.1 What is SE0X-CB/CS NB-IoT/LTE-M Soil Moisture & EC Sensor ==
22
23
24 The Dragino SE0X-CB/CS is a (% style="color:blue" %)**NB-IoT/LTE-M Soil Moisture & EC Sensor**(%%) for Agri-IoT with up to 4 sensor probes. It is designed to measure the (% style="color:blue" %)**soil moisture of saline-alkali soil and loamy soil**(%%). The soil sensor uses (% style="color:blue" %)**FDR method**(%%) to calculate the soil moisture with the compensation from soil temperature and conductivity. It also has been calibrated in factory for Mineral soil type.
25
26 It detects (% style="color:blue" %)**Soil Moisture**(%%), (% style="color:blue" %)**Soil Temperature**(%%) and (% style="color:blue" %)**Soil Conductivity**(%%), and then upload to IoT server via NB-IoT or CAT-M1 network.
27
28 SE0X-CB/CS supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP, MQTTs or CoAP**(%%) for different application requirement. and Support Uplinks to various IoT Servers.
29
30 SE0X-CB/CS (% style="color:blue" %)**supports BLE configure**(%%) and (% style="color:blue" %)**wireless OTA update**(%%) which make user easy to use.
31
32 SE0X-CB/CS is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery **(%%)or (% style="color:blue" %)**solar powered + Li-ion battery**(%%), it is designed for long-term use up to several years.
33
34 [[image:image-20250416170943-1.jpeg]]
35
36
37 == 1.2 ​Features ==
38
39
40 * For -NB Bands: B1/B2/B3/B4/B5/B8/B12/B13/B17/B18/B19/B20/B25/B28/B66/B70/B85
41 * For -CB Bands: B1/B2/B3/B4/B5/B8/B12/B13~/~/B18/B19/B20/B25/B28/B66/B71/B85
42 * CAT-M1 / LTE-M Bands: B1/B2/B3/B4/B5/B8/B12/B13/B18/B19/B20/B25/B26/B27/B28/B66/B85
43 * Ultra-low power consumption
44 * Up to 4 external sensor probes, probe length: 2.5 meters
45 * Monitor Soil Moisture
46 * Monitor Soil Temperature
47 * Monitor Soil Conductivity
48 * IP66 Waterproof Enclosure
49 * Multiply Sampling and one uplink
50 * Uplink via MQTT, MQTTs, TCP, UDP or CoAP
51 * GNSS for Location Report
52 * Support Bluetooth v5.1 remote configure and update firmware
53 * Uplink on periodically
54 * Downlink to change configure
55 * 8500mAh Li/SOCl2 Battery (SE0X-CB)
56 * Solar panel + 3000mAh Li-ion battery (SE0X-CS)
57 * Nano SIM card slot for NB-IoT SIM
58
59 (% style="color:blue" %)**Common DC Characteristics:**
60
61 * Supply Voltage: Built-in Battery , 2.6v ~~ 3.6v
62 * Operating Temperature: -40 ~~ 85°C
63
64 (% style="color:blue" %)**Soil Moisture:**
65
66 * Range: 0-100.00 V/V %
67 * Resolution: 0.01 V/V %
68 * Accuracy: ±3% (0-53%)V/V %, ±5% (>53%) V/V %
69 * Measure Method: FDR , with temperature &EC compensate
70
71 (% style="color:blue" %)**Soil Temperature**
72
73 * Range: -40.00℃~85.00℃
74 * Resolution: 0.01℃
75 * Accuracy: -10℃~50℃:<0.3℃ ,All other: <0.6℃
76 * Measure Method: RTD, and calibrate
77
78 (% style="color:blue" %)**Soil Conductivity**
79
80 * Range: 0-20000 uS/cm(25℃)(0-20.0EC)
81 * Resolution: 1 uS/cm
82 * Accuracy: 2%FS
83 * Measure Method: Conductivity , with temperature compensate
84
85 (% style="color:blue" %)**NB-IoT Spec:**
86
87 (% style="color:#037691" %)**NB-IoT Module: BG95-NGFF**
88
89 (% style="color:#037691" %)**Support Bands:**
90
91 * B1 @H-FDD: 2100MHz
92 * B2 @H-FDD: 1900MHz
93 * B3 @H-FDD: 1800MHz
94 * B4 @H-FDD: 2100MHz
95 * B5 @H-FDD: 860MHz
96 * B8 @H-FDD: 900MHz
97 * B12 @H-FDD: 720MHz
98 * B13 @H-FDD: 740MHz
99 * B17 @H-FDD: 730MHz
100 * B18 @H-FDD: 870MHz
101 * B19 @H-FDD: 870MHz
102 * B20 @H-FDD: 790MHz
103 * B25 @H-FDD: 1900MHz
104 * B28 @H-FDD: 750MHz
105 * B66 @H-FDD: 2000MHz
106 * B70 @H-FDD: 2000MHz
107 * B85 @H-FDD: 700MHz
108
109 (% style="color:blue" %)**Battery:**
110
111 * Li/SOCI2 un-chargeable battery
112 * Capacity: 8500mAh
113 * Self-Discharge: <1% / Year @ 25°C
114 * Max continuously current: 130mA
115 * Max boost current: 2A, 1 second
116
117 (% style="color:blue" %)**Power Consumption**
118
119 * Sleep Mode: 5uA @ 3.3v
120 * LoRa Transmit Mode: 125mA @ 20dBm, 82mA @ 14dBm
121
122 == 1.4 Applications ==
123
124
125 * Smart Agriculture
126
127 == 1.5 Sleep mode and working mode ==
128
129
130 (% 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.
131
132 (% 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.
133
134
135 == 1.6 Button & LEDs ==
136
137
138 [[image:image-20250416171038-2.jpeg]]
139
140 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
141 |=(% 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**
142 |(% style="width:167px" %)Pressing ACT between 1s < time < 3s|(% style="width:117px" %)Send an uplink|(% style="width:225px" %)(((
143 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.
144 Meanwhile, BLE module will be active and user can connect via BLE to configure device.
145 )))
146 |(% style="width:167px" %)Pressing ACT for more than 3s|(% style="width:117px" %)Active Device|(% style="width:225px" %)(((
147 (% 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.
148 (% style="color:green" %)**Green led**(%%) will solidly turn on for 5 seconds after joined in network.
149 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.
150 )))
151 |(% 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.
152
153 (% 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.**
154
155
156 == 1.7 BLE connection ==
157
158
159 SE0X-CB/CS support BLE remote configure and firmware update.
160
161 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:
162
163 * Press button to send an uplink
164 * Press button to active device.
165 * Device Power on or reset.
166
167 If there is no activity connection on BLE in 60 seconds, sensor will shut down BLE module to enter low power mode.
168
169
170 == 1.8 Pin Definitions ==
171
172 [[image:image-20250218141409-1.png||height="434" width="707"]]
173
174 === 1.8.1 Jumper JP2 ===
175
176
177 Power on Device when put this jumper.
178
179
180 === 1.8.2 BOOT MODE / SW1 ===
181
182
183 **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.
184
185 **2)** (% style="color:blue" %)**Flash:**(%%) work mode, device starts to work and send out console output for further debug
186
187
188 === 1.8.3 Reset Button ===
189
190
191 Press to reboot the device.
192
193
194 === 1.8.4 SIM Card Direction ===
195
196
197 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]].
198
199
200 == 1.9 Mechanical ==
201
202 === 1.9.1 for CB version ===
203
204 (% style="color:blue" %)**Main Device Dimension:**
205
206 [[image:image-20250118094401-6.png]]
207
208
209 (% style="color:blue" %)**Probe Dimension:**
210
211 [[image:image-20250331153423-1.jpeg]]
212
213
214 === 1.9.2 for CS version ===
215
216
217 [[image:image-20250331153444-2.jpeg]]
218
219
220 == 1.10 Installation in Soil ==
221
222
223 (% style="color:blue" %)**Measurement the soil surface**
224
225 [[image:image-20250331153503-3.jpeg]] ​
226
227 Choose the proper measuring position. Avoid the probe to touch rocks or hard things. Split the surface soil according to the measured deep. Keep the measured as original density. Vertical insert the probe into the soil to be measured. Make sure not shake when inserting.
228
229
230 [[image:image-20250331153512-4.jpeg]]
231
232 Dig a hole with diameter > 20CM.
233
234 Horizontal insert the probe to the soil and fill the hole for long term measurement.
235
236
237 = 2. Use SE0X-CB/CS to communicate with IoT Server =
238
239 == 2.1 Send data to IoT server via NB-IoT network ==
240
241
242 The SE0X-CB/CS is equipped with a NB-IoT module, the pre-loaded firmware in SE0X-CB/CS 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 SE0X-CB/CS.
243
244 Below shows the network structure:
245
246 (% style="display:none" %) (%%) [[image:image-20250120150934-2.png]]
247
248
249 There are two version: (% style="color:blue" %)**-GE**(%%) and (% style="color:blue" %)**-1T**(%%) version of SE0X-CB/CS.
250
251
252 (% 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 SE0X-CB/CS send data to IoT server.
253
254 * Install NB-IoT SIM card and configure APN. See instruction of [[Attach Network>>https://wiki.dragino.com/xwiki/bin/view/Main/General%20Manual%20for%20-CB%20%2C%20-CS%20models/#H2.AttachNetwork]].
255
256 * 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]]. 
257
258 Below shows result of different server as a glance.
259
260 (% border="1" cellspacing="4" style="width:515px" %)
261 |(% 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**
262 |(% 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" %)[[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/SE02-NB_NB-IoT_Soil_Moisture%26EC_Sensor_User_Manual/WebHome/image-20230819113244-8.png?width=367&height=183&rev=1.1||alt="image-20230819113244-8.png"]](((
263
264 )))|(% style="width:170px" %)
265 |(% 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" %)[[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/SE02-NB_NB-IoT_Soil_Moisture%26EC_Sensor_User_Manual/WebHome/image-20230819113244-9.png?width=367&height=119&rev=1.1||alt="image-20230819113244-9.png"]](((
266
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" %)[[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/SE02-NB_NB-IoT_Soil_Moisture%26EC_Sensor_User_Manual/WebHome/image-20230819113244-10.png?width=367&height=104&rev=1.1||alt="image-20230819113244-10.png"]](((
272
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" %)[[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/SE02-NB_NB-IoT_Soil_Moisture%26EC_Sensor_User_Manual/WebHome/image-20230819113244-11.png?width=367&height=141&rev=1.1||alt="image-20230819113244-11.png"]](((
275
276 )))
277
278 (% 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 SE0X-CB/CS 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/]].
279
280
281 === (% style="color:blue" %)**Soil Sensor Address Configuration**(%%) ===
282
283 All soil sensors are shipped with (% style="color:#037691" %)**default address 0x01**(%%). 
284
285 Do not use the same address repeatedly on the same node, otherwise the data will conflict, so if you connect more than 1 sensor to the SE0X-CB/CS node, you need to follow the steps below to change the address (supported addresses: **01-04**):
286
287 **Step 1**: Keep the default address **01** for the **first sensor**. No modification or operation is required.
288
289 **Step 2**: Connect the **second sensor**, and change its address to **02**.
290
291 **Step 3**:** **Disconnect the second sensor, connect the** third sensor**, and change its address to **03**.
292
293 **Step 3**: Repeat Step 3 to assign address **04** to the **fourth sensor**.
294
295
296 **For details, see [[Configure Methods>>||anchor="H3.1ConfigureMethods"]] in 3.1 and [[Command Description>>||anchor="H3.22Settingthesensoraddress"]] in 3.22.**
297
298 (% style="color:blue" %)**Connection:**
299
300 * Wiring during sensor operation:
301
302 [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/SE0X-LB--LoRaWAN_Soil_Moisture%26EC_Sensor_Transmitter_User_Manual/WebHome/image-20250414091358-1.jpeg?width=549&height=287&rev=1.1||alt="image-20250414091358-1.jpeg" height="287" width="549"]]
303
304 * Wiring when changing the sensor address:
305
306 [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/SE0X-LB--LoRaWAN_Soil_Moisture%26EC_Sensor_Transmitter_User_Manual/WebHome/image-20250414092154-2.jpeg?width=548&height=303&rev=1.1||alt="image-20250414092154-2.jpeg" height="303" width="548"]]
307
308 (% style="color:red" %)**Note: The yellow wire is only used when the address of the sensor is modified. After the address of the sensor is successfully modified, please disconnect the yellow cable and use tape to isolate the wire core to prevent the yellow wire from touching the motherboard element and causing a short circuit.**
309
310
311 == 2.2 ​Payload Types ==
312
313
314 To meet different server requirement, SE0X-CB/CS supports different payload type.
315
316 **Includes:**
317
318 * [[General JSON format payload>>||anchor="H2.2.1GeneralJsonFormat28Type3D529"]]. (Type=5)
319
320 * [[HEX format Payload>>||anchor="H2.2.2HEXformatPayload28Type3D029"]]. (Type=0)
321
322 * [[ThingSpeak Format>>||anchor="H2.2.4ThingSpeakPayload28Type3D129"]]. (Type=1)
323
324 * [[ThingsBoard Format>>||anchor="H2.2.3ThingsBoardPayload28Type3D329"]]. (Type=3)
325
326 User can specify the payload type when choose the connection protocol. Example:
327
328 (% style="color:#037691" %)**AT+PRO=1,0**  (%%) ~/~/ Use COAP Connection & hex Payload
329
330 (% style="color:#037691" %)**AT+PRO=1,5**   (%%) ~/~/ Use COAP Connection & Json Payload
331
332 (% style="color:#037691" %)**AT+PRO=2,0**  (%%) ~/~/ Use UDP Connection & hex Payload
333
334 (% style="color:#037691" %)**AT+PRO=2,5**   (%%) ~/~/ Use UDP Connection & Json Payload
335
336 (% style="color:#037691" %)**AT+PRO=3,0**  (%%) ~/~/ Use MQTT Connection & hex Payload
337
338 (% style="color:#037691" %)**AT+PRO=3,5**   (%%) ~/~/ Use MQTT Connection & Json Payload
339
340 (% style="color:#037691" %)**AT+PRO=4,0**  (%%) ~/~/ Use TCP Connection & hex Payload
341
342 (% style="color:#037691" %)**AT+PRO=4,5**   (%%) ~/~/ Use TCP Connection & Json Payload
343
344
345 === 2.2.1 General Json Format(Type~=5) ===
346
347
348 ==== 2.2.1.1 AT+CFGMOD~=0(Default Mode) ====
349
350
351 This is the General Json Format. As below:
352
353 (% style="color:#4472c4" %)**{"IMEI":"868508065605159","IMSI":"454312901015184","Model":"SE0X-CB","interrupt":0,"interrupt_level":0,"battery":3.22,"signal":17,"sensor_flag":"1111","water_soil1":40.32,"temp_soil1":19.33,"conduct_soil1":6716,"water_soil2":40.21,"temp_soil2":19.64,"conduct_soil2":6507,"water_soil3":36.35,"temp_soil3":19.67,"conduct_soil3":5858,"water_soil4":8.70,"temp_soil4":19.39,"conduct_soil4":2984,"time":"2025-01-20T08:01:12Z","latitude":0.000000,"longitude":0.000000,"gps_time":"1970-01-01T00:00:00Z"}**
354
355 [[image:image-20250120163312-3.png]]
356
357
358 (% style="color:red" %)**Notice, from above payload:**
359
360 * interrupt, interrupt_level, battery, signal, sensor_flag, water_soil1, temp_soil1, conduct_soil1, water_soil2, emp_soil2, conduct_soil2, water_soil3, temp_soil3, onduct_soil3, water_soil4, temp_soil4,
361
362 conduct_soil4, time, Latitude, Longitude & gps_time are the value at uplink time.
363
364
365 ==== 2.2.1.2 AT+CFGMOD~=1(Original value) ====
366
367
368 This is the General Json Format. As below:
369
370 (% style="color:#4472c4" %)**{"IMEI":"868508065605159","IMSI":"454312901015184","Model":"SE0X-CB","interrupt":0,"interrupt_level":0,"battery":3.23,"signal":16,"sensor_flag":"1111","Soil_dielectric_constant1":24.2,"raw_water_soil1":4854,"raw_conduct_soil1":17217,"Soil_dielectric_constant2":28.8,"raw_water_soil2":5130,"raw_conduct_soil2":18958,"Soil_dielectric_constant3":19.5,"raw_water_soil3":4630,"raw_conduct_soil3":17580,"Soil_dielectric_constant4":1.0,"raw_water_soil4":2607,"raw_conduct_soil4":262,"time":"2025-01-20T10:06:27Z","latitude":0.000000,"longitude":0.000000,"gps_time":"1970-01-01T00:00:00Z"}**
371
372 [[image:image-20250120180757-15.png]]
373
374 (% style="color:red" %)**Notice, from above payload:**
375
376 * interrupt, interrupt_level, battery, signal, sensor_flag, Soil_dielectric_constant1, raw_water_soil1, raw_conduct_soil1, Soil_dielectric_constant2, raw_water_soil2, raw_conduct_soil2,
377
378 Soil_dielectric_constant3, raw_water_soil3, raw_conduct_soil3, Soil_dielectric_constant4, raw_water_soil4, raw_conduct_soil4, time, Latitude, Longitude & gps_timeare the value at uplink time.
379
380
381 === 2.2.2 HEX format Payload(Type~=0) ===
382
383
384 ==== 2.2.2.1 AT+CFGMOD~=0(Default Mode) ====
385
386 This is the HEX Format. As below:
387
388 (% style="color:#4472c4" %)**f868508065605159f45431290101518469640ccd170000000f0ee207961a09106c07b7190b0e3d07b91914034c07ac0b94678e0ae2000000000000000000000000**
389
390 [[image:image-20250120182441-17.png]]
391
392 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
393
394 [[image:image-20250120164039-4.png]]
395
396
397 (% style="color:blue" %)**Device ID(f+IMEI):**(%%)** **f868508065605159  =868508065605159
398
399 (% style="color:blue" %)**SIM Card ID(f+IMSI):**(%%)** **f454312901015184  =454312901015184
400
401
402 (% style="color:blue" %)**Version:**
403
404 These bytes include the hardware and software version.
405
406 (% style="color:#037691" %)**Higher byte:**(%%) Specify Sensor Model: 0x69 for SE0X-CB/CS
407
408 (% style="color:#037691" %)**Lower byte:**(%%) Specify the software version: 0x64=100, means firmware version 1.0.0
409
410
411 (% style="color:blue" %)**BAT (Battery Info):**
412
413 Ex1: 0x0CD1 = 3281mV
414
415
416 (% style="color:blue" %)**Signal Strength:**
417
418 NB-IoT Network signal Strength.
419
420 **Ex1: 0x17 = 23**
421
422 **0**  -113dBm or less
423
424 **1**  -111dBm
425
426 **2...30** -109dBm... -53dBm
427
428 **31**   -51dBm or greater
429
430 **99**    Not known or not detectable
431
432
433 (% style="color:blue" %)**MOD**
434
435 This data field shows the current working mode.
436
437 **Ex1:** 0x00  default mode.
438
439 **Ex2: **0x01  original mode.
440
441
442 (% style="color:blue" %)**Interrupt**
443
444 This data field shows if this packet is generated by interrupt or not.
445
446 **Example:**
447
448 If byte[0]&0x01=0x00 : Normal uplink packet.
449
450 If byte[0]&0x01=0x01 : Interrupt Uplink Packet.
451
452
453 (% style="color:blue" %)**Interrupt_level:**
454
455 This byte shows whether the interrupt is triggered by a high or low level.
456
457 **Ex1:** 0x00  Interrupt triggered by falling edge (low level)
458
459 **Ex2: **0x01  Interrupt triggered by rising edge (high level)
460
461
462 (% style="color:blue" %)**Sensor_flag**
463
464 Displays whether sensors are connected.
465
466 **0:** Sensor connection not detected.
467
468 **1:** Sensor connection detected.
469
470 **For example,** s_flag=1111,.Represents recognition to four sensors.
471
472 Counting from left to right,
473
474 The first number represents the **01** address sensor,
475
476 The second number represents the **02** address sensor;
477
478 The third number represents the **03** address sensor;
479
480 The fourth number represents the **04** address sensor.
481
482
483 (% style="color:blue" %)**Soil Moisture **
484
485 (((
486 Get the moisture content of the soil. The value range of the register is 0-10000(Decimal), divide this value by 100 to get the percentage of moisture in the soil.
487 )))
488
489 (((
490 For example, if the data you get from the register is **__0x05 0xDC__**, the moisture content in the soil is (% style="color:blue" %)**05DC(H) = 1500(D) /100 = 15%.**
491 )))
492
493
494 (% style="color:blue" %)**Soil Temperature **
495
496 (((
497 Get the temperature in the soil. The value range of the register is -4000 - +800(Decimal), divide this value by 100 to get the temperature in the soil. For example, if the data you get from the register is 0x09 0xEC, the temperature content in the soil is
498 )))
499
500 (((
501 **Example**:
502 )))
503
504 (((
505 If payload is 0105H: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/100 = 2.61 °C
506 )))
507
508 (((
509 If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/100 = -1.29 °C
510 )))
511
512
513 (% style="color:blue" %)**Soil Conductivity (EC) **
514
515 (((
516 Obtain (% style="color:blue" %)**__soluble salt concentration__**(%%) in soil or (% style="color:blue" %)**__soluble ion concentration in liquid fertilizer__**(%%) or (% style="color:blue" %)**__planting medium__**(%%). The value range of the register is 0 - 20000(Decimal)( Can be greater than 20000).
517 )))
518
519 (((
520 For example, if the data you get from the register is 0x00 0xC8, the soil conductivity is 00C8(H) = 200(D) = 200 uS/cm.
521 )))
522
523 (((
524 Generally, the EC value of irrigation water is less than 800uS / cm.
525 )))
526
527
528 (% style="color:blue" %)**TimeStamp:   **
529
530 Unit TimeStamp Example: 678B1740(H) = 1737168704(D)
531
532 Put the decimal value into this link([[https:~~/~~/www.epochconverter.com)>>https://www.epochconverter.com]]) to get the time.
533
534
535 (% style="color:blue" %)**Latitude:**
536
537 EX1:** **0x00000000  ~/~/ Locating fails or is not enabled.
538
539 EX2:** **0x015a771e(H)=22705950(D)=22.705950
540
541
542 (% style="color:blue" %)**Longitude:**
543
544 EX1:** **0x00000000  ~/~/ Locating fails or is not enabled.
545
546 EX2:** **0x114242500(H)=114242500(D)=114.242500
547
548
549 (% style="color:blue" %)**GPS_Timestamp:**
550
551 EX1: 0x00000000  ~/~/ The value is "1970-01-01T00:00:00Z" in JSON format. The initial GPS time is not refreshed if GPS positioning is disabled or fails.
552
553 EX2: 0x6682595d =1719818589 = 2024-07-01 15:23:09
554
555
556 ==== 2.2.2.2 AT+CFGMOD~=1(Original value) ====
557
558 This is the HEX Format. As below:
559
560 (% style="color:#4472c4" %)**f868508065605159f45431290101518469640ccd110100000f00f312f74dc20120140b4a8200c312134d12000a0a2f0106678e2139000000000000000000000000**
561
562 [[image:image-20250120182922-18.png]]
563
564 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
565
566 [[image:image-20250120181405-16.png]]
567
568
569 === 2.2.3 ThingsBoard Payload(Type~=3) ===
570
571
572 ==== 2.2.3.1 AT+CFGMOD~=0(Default Mode) ====
573
574 (% style="color:#4472c4" %)**{
575 "IMEI": "868508065605159",
576 "IMSI": "454312901015184",
577 "Model": "SE0X-CB",
578 "interrupt": 0,
579 "interrupt_level": 0,
580 "battery": 3.27,
581 "signal": 21,
582 "sensor_flag": "1111",
583 "water_soil1": 39.07,
584 "temp_soil1": 19.51,
585 "conduct_soil1": 7301,
586 "water_soil2": 42.33,
587 "temp_soil2": 19.85,
588 "conduct_soil2": 6361,
589 "water_soil3": 36.5,
590 "temp_soil3": 19.81,
591 "conduct_soil3": 6783,
592 "water_soil4": 7.28,
593 "temp_soil4": 19.41,
594 "conduct_soil4": 2839,
595 "time": "2025-01-20T09:01:13Z",
596 "latitude": 0,
597 "longitude": 0,
598 "gps_time": "1970-01-01T00:00:00Z"
599 }**
600
601 [[image:image-20250120170747-6.png]]
602
603
604 ==== 2.2.3.2 AT+CFGMOD~=1(Original value) ====
605
606
607 (% style="color:#4472c4" %)**{
608 "IMEI": "868508065605159",
609 "IMSI": "454312901015184",
610 "Model": "SE0X-CB",
611 "interrupt": 0,
612 "interrupt_level": 0,
613 "battery": 3.23,
614 "signal": 17,
615 "sensor_flag": "1111",
616 "Soil_dielectric_constant1": 24.2,
617 "raw_water_soil1": 4852,
618 "raw_conduct_soil1": 22367,
619 "Soil_dielectric_constant2": 28.8,
620 "raw_water_soil2": 5130,
621 "raw_conduct_soil2": 18293,
622 "Soil_dielectric_constant3": 19.5,
623 "raw_water_soil3": 4631,
624 "raw_conduct_soil3": 15702,
625 "Soil_dielectric_constant4": 1,
626 "raw_water_soil4": 2614,
627 "raw_conduct_soil4": 283,
628 "time": "2025-01-20T10:00:57Z",
629 "latitude": 0,
630 "longitude": 0,
631 "gps_time": "1970-01-01T00:00:00Z"
632 }**
633
634 [[image:image-20250120180435-14.png]]
635
636
637 === 2.2.4 ThingSpeak Payload(Type~=1) ===
638
639
640 This payload meets ThingSpeak platform requirement.
641
642 ThingSpeak only supports a maximum of 8 field charts per channel, so the sample screenshot contains only 8 fields charts.
643
644
645 ==== 2.2.4.1 AT+CFGMOD~=0(Default Mode) ====
646
647
648 (% style="color:#4472c4" %)**field1=Battery value&field2=Signal value&field3=latitude value&field4=longitude value&field5=water_soil1 value&field6=temp_soil1 value&field7=conduct_soil1 value&field8=water_soil2 value**
649
650 [[image:image-20250120172417-9.png]]
651
652 [[image:image-20250120172439-10.png]]
653
654
655 ==== 2.2.4.2 AT+CFGMOD~=1(Original value) ====
656
657
658 (% style="color:#4472c4" %)**field1=Battery value&field2=Signal value&field3=latitude value&field4=longitude value&field5=Soil_dielectric_constant1 value&field6=raw_water_soil1 value&field7=raw_conduct_soil1 value&field8=Soil_dielectric_constant2 value**
659
660 [[image:image-20250120174208-11.png]]
661
662 [[image:image-20250120174216-12.png]]
663
664
665 = 3. Configure SE0X-CB/CS =
666
667 == 3.1 Configure Methods ==
668
669
670 SE0X-CB/CS supports below configure method:
671
672 * AT Command via Bluetooth Connection (**Recommended**): [[BLE Configure Instruction>>http://wiki.dragino.com/xwiki/bin/view/Main/BLE%20Bluetooth%20Remote%20Configure/]].
673
674 * 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]].
675
676 == ​​​3.2  Serial Access Password ==
677
678
679 After the Bluetooth or UART connection is successful, use the Serial Access Password to enter the AT command window.
680
681 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.
682
683 [[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"]]
684
685
686 If you need to change the password, use **AT+PWORD=**xxxxxx (6 characters), -CB nodes only support lowercase letters.
687
688 [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/SN50v3-CB_NB-IoTLTE-M_Sensor_Node_User_Manual/WebHome/image-20240826180321-2.png?rev=1.1||alt="image-20240826180321-2.png"]]
689
690
691 (% 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.**
692
693 [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/SN50v3-CB_NB-IoTLTE-M_Sensor_Node_User_Manual/WebHome/image-20240826180330-3.png?rev=1.1||alt="image-20240826180330-3.png"]]
694
695
696 == 3.3 AT Commands Set ==
697
698
699 AT+<CMD>? : Help on <CMD>
700
701 AT+<CMD> : Run <CMD>
702
703 AT+<CMD>=<value> : Set the value
704
705 AT+<CMD>=? : Get the value
706
707
708 (% style="color:blue" %)**General Commands**  
709
710 AT+MODEL : Get module information
711
712 ATZ : Trig a reset of the MCU
713
714 AT+CFGMOD : Working mode selection
715
716 AT+DEUI : Get or set the Device ID
717
718 AT+SERVADDR: Get or Set the Server address
719
720 AT+TDC : Get or set the application data transmission interval in s
721
722 AT+INTMOD : Get or Set the trigger interrupt mode (0:input,1:falling or rising,2:falling,3:rising)
723
724 AT+APN : Get or set the APN
725
726 AT+5VT : Get or Set extend the time of 5V power
727
728 AT+PRO : Get or Set usage agreement (1:COAP,2:UDP,3:MQTT,4:TCP)
729
730 AT+RXDL : Get or Set the receiving time
731
732 AT+GETSENSORVALUE : Returns the current sensor measurement
733
734 AT+DNSCFG : Get or Set DNS Server
735
736 AT+CSQTIME : Get or Set the time to join the network
737
738 AT+GDNS : Get or Set the DNS
739
740 AT+SLEEP : Get or Set the sleep mode
741
742 AT+IPTYPE : Set the IPv4 or IPv6
743
744 AT+QSW : Power on and power off BG95 module
745
746 AT+QBAND: Get or set Frequency Band
747
748 AT+IOTMOD: Configure Network Category to be Searched for under LTE RAT
749
750 AT+DOWNTE: Get or set the conversion between the standard version and 1T version downlinks
751
752 AT+MADD: Change the sensor address to 0x01, 0x02, 0x03, 0x04
753
754
755 (% style="color:blue" %)**MQTT Management**
756
757 AT+CLIENT : Get or Set the MQTT clientID
758
759 AT+UNAME : Get or Set the MQTT Username
760
761 AT+PWD : Get or Set the MQTT password
762
763 AT+PUBTOPIC: Get or set MQTT publishing topic
764
765 AT+SUBTOPIC: Get or set MQTT subscription topic
766
767 AT+MQOS : Set the QoS level of MQTT
768
769 AT+TLSMOD : Get or Set the TLS mode
770
771
772 (% style="color:blue" %)**COAP Management**
773
774 AT+URI1: Get or set CoAP option 1
775
776 AT+URI2: Get or set CoAP option 2
777
778 AT+URI3: Get or set CoAP option 3
779
780 AT+URI4: Get or set CoAP option 4
781
782 AT+URI5: Get or set CoAP option 5
783
784 AT+URI6: Get or set CoAP option 6
785
786 AT+URI7: Get or set CoAP option 7
787
788 AT+URI8: Get or set CoAP option 8
789
790
791 (% style="color:blue" %)**GPS**
792
793 AT+GNSST : Extend the time to turn on GNSS
794
795 AT+GPS : Turn off and on GPS
796
797 AT+GTDC : Get or set GPS positioning interval in units of h
798
799
800 (% style="color:blue" %)**Information**        
801
802 AT+FDR1 : Reset parameters to factory default values except for passwords
803
804 AT+FDR : Reset Parameters to Factory Default
805
806 AT+CFG : Print all settings
807
808 AT+PWORD : Get or set the System password
809
810 AT+LDATA : Get the last upload data
811
812 AT+GETLOG : Print serial port logs
813
814
815 == 3.4 Test Uplink and Change Update Interval ==
816
817
818 By default, Sensor will send uplinks **every 2 hours.**
819
820 User can use below commands to change the uplink interval.
821
822 (% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+TDC** (%%)
823
824 Example: AT+TDC=7200  ~/~/ Set Update Interval to 7200 seconds
825
826 (% style="color:blue" %)**Downlink Commands: **(% style="color:#037691" %)**0x01**
827
828 Format: Command Code (0x01) followed by 3 bytes.
829
830 Example:  12 hours= 43200 seconds  43200(D)=0xA8C0(H)
831
832 Downlink Payload: **01 00 A8 C0**  ~/~/ AT+TDC=43200, Set Update Interval to 12 hours.
833
834 (% style="color:red" %)**Note: User can also push the button for more than 1 second to activate an uplink.**
835
836
837 == 3.5 Working mode selection ==
838
839
840 Feature: Working mode selection.
841
842 (% style="color:blue" %)**AT command: **(% style="color:#037691" %)**AT+CFGMOD**
843
844 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:470px" %)
845 |=(% 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**
846 |(% style="width:191px" %)AT+CFGMOD=0|(% style="width:277px" %)(((
847 Set the operating mode to the default mode
848 )))
849 |(% style="width:191px" %)AT+CFGMOD=1|(% style="width:277px" %)Setting the operating mode to the original mode
850
851 (% style="color:blue" %)**Downlink Command:  **(% style="color:#037691" %)**0x02**
852
853 * Downlink command: 02 01  ~/~/ Equal to AT+CFGMOD=0
854 * Downlink command: 02 02  ~/~/ Equal to AT+CFGMOD=1
855
856 == 3.6 Set the receiving time ==
857
858
859 Feature: Extend the receiving time
860
861 (% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+RXDL**
862
863 Example: AT+RXDL=1000  ~/~/ Set the receiving time delay to 1000ms
864
865 (% style="color:blue" %)**Downlink Commands: **(% style="color:#037691" %)**0x03**
866
867 Format: Command Code (0x03) followed by 3 bytes.
868
869 Example:  Downlink Payload: **03 00 03 E8     **~/~/ AT+RXDL=1000
870
871
872 == 3.7 Reset ==
873
874
875 Feature: Trig a reset of the MCU.
876
877 (% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**ATZ**
878
879 (% style="color:blue" %)**Downlink Commands: **(% style="color:#037691" %)**0x04FF**
880
881
882 == 3.8 +5V ==
883
884
885 Feature: Set extend the time of 5V power.
886
887 (% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+5VT**
888
889 Example: AT+5VT=2000  ~/~/ Set extend the time of 5V power to 2000 ms
890
891 (% style="color:blue" %)**Downlink Commands: **(% style="color:#037691" %)**0x05**
892
893 Format: Command Code (0x05) followed by 3 bytes.
894
895 Example:  Downlink Payload: **05 00 07 D0    **~/~/ AT+5VT=2000
896
897
898 == 3.9 Trigger an uplink by external interrupt ==
899
900
901 SE0X-CB/CS has an external trigger interrupt function. Users can use the GPIO_EXTI pin to trigger the upload of data packets.
902
903 (% style="color:blue" %)**AT command:**
904
905 * (% style="color:#037691" %)**AT+INTMOD **(%%) ~/~/ Set the trigger interrupt mode
906
907 * (% style="color:#037691" %)**AT+INTMOD=0 **(%%) ~/~/ Disable Interrupt
908
909 * (% style="color:#037691" %)**AT+INTMOD=1 **(%%) ~/~/ Trigger by rising and falling edge
910
911 * (% style="color:#037691" %)**AT+INTMOD=2 **(%%) ~/~/ Trigger by falling edge
912
913 * (% style="color:#037691" %)**AT+INTMOD=3  **(%%) ~/~/ Trigger by rising edge
914
915 (% style="color:blue" %)**Downlink Commands: **(% style="color:#037691" %)**0x06**
916
917 Format: Command Code (0x06) followed by 3 bytes.
918
919 Example1:  Downlink Payload: **06 00 00 01    **~/~/ AT+INTMOD=1
920
921 Example2:  Downlink Payload: **06 00 00 03    **~/~/ AT+INTMOD=3
922
923
924 == 3.10 Set the QoS level ==
925
926
927 This command is used to set the QoS level of **MQTT**.
928
929 (% style="color:blue" %)**AT command:**
930
931 * (% style="color:#037691" %)**AT+MQOS=xx**(%%)**   **~/~/ 0~~2
932
933 (% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x07(%%)**
934
935 Format: Command Code (0x07) followed by 1 byte.
936
937 **Ex1:** Downlink payload: **0x0700**  ~/~/ AT+MQOS=0
938
939 **Ex2:** Downlink payload: **0x0701**  ~/~/ AT+MQOS=1
940
941
942 == 3.11 Set the TLS mode ==
943
944
945 Refer to this link ([[MQTT Connection to send data to Tago.io>>https://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.8A0Tago.ioA028viaA0MQTT29]])to use the TLS mode.
946
947 (% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+TLSMOD**
948
949 **Example 1: ** AT+TLSMOD=0,0  ~/~/ Disable TLS Mode.
950
951 **Example 2:**  AT+TLSMOD=1,0  ~/~/ No authentication
952
953 AT+TLSMOD=1,1  ~/~/ Perform server authentication
954
955 AT+TLSMOD=1,2  ~/~/ Perform server and client authentication if requested by the remote server
956
957 (% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x09(%%)**
958
959 Format: Command Code (0x09) followed by 2 bytes.
960
961 Example1:  Downlink Payload: **09 00 00    **~/~/ AT+TLSMOD=0,0
962
963 Example2:  Downlink Payload: **09 01 02    **~/~/ AT+TLSMOD=1,2
964
965
966 == 3.12 Set GNSS open time ==
967
968
969 Extend the time to turn on GNSS. The automatic GPS location time is extended when the node is activated.
970
971 (% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+GNSST**
972
973 Example: AT+GNSST=30  ~/~/ Set the GPS positioning time to 30 seconds
974
975 (% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x10(%%)**
976
977 Format: Command Code (0x10) followed by 2 bytes.
978
979 Example:  Downlink Payload: **10 00 1E    **~/~/ AT+GNSST=30
980
981
982 == 3.13 Turn on/off GPS ==
983
984
985 (% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+GPS**
986
987 **Ex1:  **AT+GPS=0  ~/~/ Turn off GPS
988
989 **Ex2:  **AT+GPS=1  ~/~/ Turn on GPS
990
991 (% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x11(%%)**
992
993 Format: Command Code (0x11) followed by 1 byte.
994
995 Example:  Downlink Payload: **11 01   **~/~/ AT+GPS=1
996
997
998 == 3.14 Set GPS positioning interval ==
999
1000
1001 Feature: Set GPS positioning interval (unit: hour).
1002
1003 When GPS is enabled, the node automatically locates and uplinks each time it passes **GTDC time** after activation.
1004
1005 (% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+GTDC**
1006
1007 Example: AT+GTDC=24  ~/~/ Set the GPS positioning interval to 24h.
1008
1009 (% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x12(%%)**
1010
1011 Format: Command Code (0x12) followed by 3 bytes.
1012
1013 Example: 24 hours:  24(D)=0x18(H)
1014
1015 Downlink Payload: **12 00 00 18   **~/~/ AT+GTDC=24
1016
1017
1018 == 3.15 Set the search network time ==
1019
1020
1021 Feature: Get or Set the time to join the network(unit: minutes).
1022
1023 (% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+CSQTIME**
1024
1025 Example: AT+CSQTIME=10  ~/~/ Set the search time to 10 minutes.
1026
1027 (% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x13(%%)**
1028
1029 Format: Command Code (0x13) followed by 1 byte.
1030
1031 Example:  Downlink Payload: **13 0A   **~/~/ AT+CSQTIME=10
1032
1033
1034 == 3.16 Set the IPv4 or IPv6 ==
1035
1036
1037 This command is used to set IP version.
1038
1039 (% style="color:blue" %)**AT Command: **
1040
1041 * (% style="color:#037691" %)**AT+IPTYPE=1**(%%)**     **~/~/ IPv4
1042 * (% style="color:#037691" %)**AT+IPTYPE=2**(%%)**     **~/~/ IPv6
1043
1044 == 3.17 Configure Network Category to be Searched for under LTE RAT. ==
1045
1046
1047 (% style="color:blue" %)**AT Command:**(%%)** (% style="color:#037691" %)AT+IOTMOD=xx(%%)**
1048
1049 (% style="color:#037691" %)**xx:**(%%)**  0:** eMTC
1050
1051 **1:** NB-IoT
1052
1053 **2:** eMTC and NB-IoT
1054
1055
1056 == 3.18 Factory data reset ==
1057
1058
1059 Two different restore factory Settings configurations.
1060
1061 (% style="color:blue" %)**AT command:**
1062
1063 * (% style="color:#037691; font-weight:bold" %)**AT+FDR**(%%)**       **~/~/ Reset Parameters to Factory Default.
1064 * (% style="color:#037691; font-weight:bold" %)**AT+FDR1**(%%)**     **~/~/ Reset parameters to factory default values **except for passwords**.
1065
1066 == 3.19 Set CoAP option ==
1067
1068
1069 Feature: Set CoAP option, follow this link to set up the CoaP protocol.
1070
1071 (% style="color:blue" %)**AT command: **(% style="color:#037691; font-weight:bold" %)**AT+URI1~~AT+URI8**
1072
1073 (% 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"
1074
1075 (% style="color:#037691; font-weight:bold" %)**AT+URI2=11,"CoAP endpoint URl"**(%%)**    **~/~/ 11 is a fixed parameter.
1076
1077 **Example: ** i/13a35fbe-9515-6e55-36e8-081fb6aacf86
1078
1079 AT+URI1=11,"i"
1080
1081 AT+URI2=11,"13a35fbe-9515-6e55-36e8-081fb6aacf86"
1082
1083 ~-~-> If multiple groups of CoAP endpoint urls:
1084
1085 AT+URI3=11,"i"
1086
1087 AT+URI4=11,"CoAP endpoint URl"
1088
1089 This command sets the connection parameters of the COAP.
1090
1091
1092 == 3.20 Power on / power off BG95 module ==
1093
1094
1095 This command is used to power on and power off BG95 module.
1096
1097 * (% style="color:blue" %)**AT command:**(%%)** (% style="color:#037691" %)AT+QSW(%%)**
1098
1099 The module is powered on after the command is sent for the first time, and powered off after the command is sent again.
1100
1101 [[image:image-20240619155719-1.png||height="644" width="811"]]
1102
1103
1104 == 3.21 Uplink log query ==
1105
1106
1107 * (% style="color:blue" %)**AT command:**(%%)** (% style="color:#037691" %)AT+GETLOG(%%)**
1108
1109 This command can be used to query upstream logs of data packets.
1110
1111 [[image:image-20250120102551-1.png]]
1112
1113
1114 == 3.22 Setting the sensor address ==
1115
1116
1117 Function:Change the sensor address to 0x01, 0x02, 0x03, 0x04
1118
1119 (% style="color:red" %)**(Note:When setting the address of the sensor, you need to connect the device individually for each one, and when modifying the address, you can't connect more than one sensor at the same time, otherwise it will be impossible to modify it, and when modifying it, you need to connect the yellow wire to VBAT_OUT, and after modifying it, you need to disconnect it.)**
1120
1121 (% style="color:blue" %)**AT Command: AT+MADD**
1122
1123 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
1124 |=(% style="width: 155px;background-color:#4F81BD;color:white" %)**Command Example**|=(% style="width: 197px;background-color:#4F81BD;color:white" %)**Function**|=(% style="width: 158px;background-color:#4F81BD;color:white" %)**Response**
1125 |(% style="width:154px" %)AT+MADD=1|(% style="width:196px" %)Set sensor address to 01|(% style="width:157px" %)(((
1126 Successfully modified sensor address to 0x01
1127
1128
1129 OK
1130 )))
1131 |(% style="width:154px" %)AT+MADD=2|(% style="width:196px" %)Set sensor address to 02|(% style="width:157px" %)(((
1132 Successfully modified sensor address to 0x02
1133
1134
1135 OK
1136 )))
1137
1138 (% style="color:blue" %)**Downlink Command:**
1139
1140 No downlink command for this feature.
1141
1142
1143 == 3.23 Domain name resolution settings ==
1144
1145
1146 Feature: Set dynamic domain name resolution IP.
1147
1148 (% style="color:blue" %)**AT command: AT+BKDNS**
1149
1150 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %)
1151 |=(% style="width: 138px; 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: 229px; background-color: rgb(79, 129, 189); color: white;" %)**Response/Explanation**
1152 |(% style="width:134px" %)(((
1153 AT+BKDNS=?
1154 )))|(% style="width:143px" %)Get current Settings|(% style="width:606px" %)(((
1155 0,0,NULL  (default)
1156 OK
1157 )))
1158 |(% colspan="1" rowspan="3" style="width:134px" %)(((
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170 AT+BKDNS=a,b,c
1171 )))|(% style="width:143px" %)(((
1172 **a**: Enable/Disable dynamic domain name resolution.
1173 )))|(% style="width:606px" %)**1**: Disable dynamic domain name update. The ip address will be saved after the domain name is resolved, if the next domain name resolution fails, the last saved ip address will be used.
1174 **2**: Enable dynamic domain name update. The ip address will be saved after domain name resolution, if the next domain name resolution fails, the last saved ip address will be used, and the domain name resolution will be updated regularly according to the time set by the customer.
1175 |(% style="width:143px" %)**b**: Set the time to update the domain name resolution at regular intervals.|(% style="width:606px" %)(((
1176 Unit: hour
1177 )))
1178 |(% style="width:143px" %)(((
1179 **c**: Set the IP address manually.
1180 )))|(% style="width:606px" %)(((
1181 The format is the same as AT+SERVADDR.
1182 If domain name resolution fails, this ip address will be used directly, if domain name resolution succeeds, parameter c will be updated to the successfully resolved IP address.
1183 )))
1184
1185 **Example:**
1186
1187 * AT+BKDNS=1,0  ~/~/ Dynamic domain name resolution is disabled.
1188 * AT+BKDNS=2,1  ~/~/ The dynamic domain name resolution function is enabled and the automatic update time is set to 1 hour.
1189 * AT+BKDNS=2,4,3.69.98.183,1883  ~/~/ The dynamic domain name resolution function is enabled and the automatic update time is set to 4 hour, and manually set the ip address, if the domain name failed to resolve, it will directly use this ip to communicate. When the next domain name resolution is successful, it will be updated to the ip address of the successful resolution.
1190
1191 (% style="color:blue" %)**Downlink Command:  **
1192
1193 No downlink commands for feature
1194
1195
1196 == 3.24 Set the downlink debugging mode ==
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 == 3.25 Domain name resolution settings(Since firmware v1.1.1) ==
1236
1237
1238 Feature: Set static DNS resolution IP address.
1239
1240 (% style="color:blue" %)**AT command: AT+BKDNS**
1241
1242 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %)
1243 |=(% style="width: 138px; 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: 229px; background-color: rgb(79, 129, 189); color: white;" %)**Response/Explanation**
1244 |(% style="width:134px" %)(((
1245 AT+BKDNS=?
1246 )))|(% style="width:143px" %)Get current Settings|(% style="width:606px" %)(((
1247 1,0,NULL  (default)
1248 OK
1249 )))
1250 |(% colspan="1" rowspan="3" style="width:134px" %)(((
1251
1252
1253
1254
1255
1256
1257 AT+BKDNS=a,b,c
1258 )))|(% style="width:143px" %)(((
1259 **a**: Enable/Disable static DNS resolution.
1260 )))|(% style="width:606px" %)(((
1261 **0:** Disable static DNS resolution
1262
1263 **1**: Enable static DNS resolution. The ip address will be saved after the domain name is resolved, if the next domain name resolution fails, the last saved ip address will be used.
1264 )))
1265 |(% style="width:143px" %)**b**: Meaningless.|(% style="width:606px" %)(((
1266 Set to **0**.
1267 )))
1268 |(% style="width:143px" %)(((
1269 **c**: Set the IP address manually.
1270 )))|(% style="width:606px" %)(((
1271 The format is the same as AT+SERVADDR.
1272 If domain name resolution fails, this ip address will be used directly, if domain name resolution succeeds, parameter c will be updated to the successfully resolved IP address.
1273 )))
1274
1275 **Example:**
1276
1277 * AT+BKDNS=0,0,NULL  ~/~/Disable static DNS resolution.
1278 * AT+BKDNS=1,0,NULL  ~/~/ Enable static DNS resolution.
1279 * AT+BKDNS=1,0,3.69.98.183,1883  ~/~/Enable static DNS resolution, if domain name resolution succeeds, the node uses the ip address successfully resolved and saves it to parameter c. If the domain name resolution fails, use the manually set ip address: 3.69.98.183 for communication.
1280
1281 (% style="color:blue" %)**Downlink Command:  **
1282
1283 No downlink commands for feature.
1284
1285
1286 = 4. Battery & Power Consumption =
1287
1288
1289 SE0X-CB use ER26500 + SPC1520 battery pack and SE0X-NS use 3000mAh Recharable Battery with Solar Panel.  See below link for detail information about the battery info and how to replace.
1290
1291 [[**Battery Info & Power Consumption Analyze**>>http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] .
1292
1293
1294 = 5. Firmware update =
1295
1296 User can change device firmware to::
1297
1298 * Update with new features.
1299
1300 * Fix bugs.
1301
1302 Firmware and changelog can be downloaded from : **[[Firmware download link>>https://www.dropbox.com/scl/fo/ztlw35a9xbkomu71u31im/AN4-uDeet2A-GUFPoEedTag/LTE-M/SE0X-CB?dl=0&rlkey=ojjcsw927eaow01dgooldq3nu&subfolder_nav_tracking=1]]**
1303
1304 Methods to Update Firmware:
1305
1306 * (Recommended way) OTA firmware update via BLE: [[**Instruction**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/BLE_Firmware_Update_NB_Sensors_BC660K-GL/]].
1307
1308 * Update through UART TTL interface : **[[Instruction>>url:http://wiki.dragino.com/xwiki/bin/view/Main/UART_Access_for_NB_ST_BC660K-GL/#H4.2UpdateFirmware28Assumethedevicealreadyhaveabootloader29]]**.
1309
1310 (((
1311
1312 )))
1313
1314 = 6. FAQ =
1315
1316 == 6.1 AT Commands input doesn't work ==
1317
1318
1319 In the case if user can see the console output but can't type input to the device. Please check if you already include the (% style="color:green" %)**ENTER**(%%) while sending out the command. Some serial tool doesn't send (% style="color:green" %)**ENTER**(%%) while press the send key, user need to add ENTER in their string.
1320
1321
1322 == 6.2 Can I calibrate SE0X-CB/CS to different soil types? ==
1323
1324
1325 SE0X-CB/CS can be used to measure EC/Moisture in different type of soil event concrete.
1326
1327 (((
1328 SE0X-CB/CS is calibrated for saline-alkali soil and loamy soil. If users want to use it for other soil, they can calibrate the value in the IoT platform base on the value measured by saline-alkali soil and loamy soil. The formula can be found at [[this link>>https://www.dragino.com/downloads/downloads/LoRa_End_Node/LSE01/Calibrate_to_other_Soil_20230522.pdf]].
1329 )))
1330
1331
1332 = 7. Order Info =
1333
1334
1335 **Part Number: (% style="color:blue" %)SE0X-CB/CS-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 = 8. ​Packing Info =
1344
1345
1346 (% style="color:#037691" %)**Package Includes**:
1347
1348 * SE0X-CB/CS NB-IoT Soil Moisture & EC Sensor Transmitter
1349
1350 * External antenna x 1
1351
1352 (% style="color:#037691" %)**Dimension and weight**:
1353
1354 * Device Size: cm
1355
1356 * Device Weight: g
1357
1358 * Package Size / pcs : cm
1359
1360 * Weight / pcs : g
1361
1362 = 9. Support =
1363
1364
1365 * 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.
1366
1367 * 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]].