Last modified by Mengting Qiu on 2024/12/26 09:56
Show last authors
1
2
3
4 (% style="text-align:center" %)
5 [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/D20-LBD22-LBD23-LB_LoRaWAN_Temperature_Sensor_User_Manual/WebHome/D2x.jpg?rev=1.1||alt="D2x.jpg" height="327" width="1315"]]
6
7
8
9
10
11
12
13
14
15 **Table of Contents:**
16
17 {{toc/}}
18
19
20
21
22
23
24 = 1. Introduction =
25
26 == 1.1 What is D2x-CB NB-IoT/LTE-M Temperature Sensor ==
27
28
29 The Dragino D2x-CB is a (% style="color:blue" %)**NB-IoT/LTE-M Temperature Sensor**(%%) for Internet of Things solution. D2x-CB has 1 ~~ 3 temperature probes. D2x-CB will convert the Temperature reading to upload the sensor data send to IoT platform via NB-IoT/CAT-M1 network.
30
31 The temperature sensor used in D2x-CB can (% style="color:blue" %)**measure -55°C ~~ 125°C with accuracy ±0.5°C (max ±2.0 °C)**.
32
33 D2x-CB supports (% style="color:blue" %)**temperature alarm feature**(%%), user can set temperature alarm for instant notice. D2x-CB supports Datalog feature, it can save the data when there is no NB-IoT network and uplink when network recover.
34
35 D2x-CB has max 3 probes which measure maximum 3 temperature points.
36
37 D2x-CB supports different uplink methods including (% style="color:blue" %)**MQTT, MQTTs, UDP , TCP or CoAP**(%%) for different application requirement, and support uplinks to various IoT Servers.
38
39 D2x-CB (% style="color:blue" %)**supports BLE configure and OTA update**(%%) which make user easy to use.
40
41 D2x-CB is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), it is designed for long-term use up to several years.
42
43 D2x-CB has optional built-in SIM card and default IoT server connection version. Which makes it works with simple configuration.
44
45
46 == 1.2 ​Features ==
47
48
49 * For -NB Bands: B1/B2/B3/B4/B5/B8/B12/B13/B17/B18/B19/B20/B25/B28/B66/B70/B85
50 * For -CB Bands: B1/B2/B3/B4/B5/B8/B12/B13~/~/B18/B19/B20/B25/B28/B66/B71/B85
51 * CAT-M1 / LTE-M Bands: B1/B2/B3/B4/B5/B8/B12/B13/B18/B19/B20/B25/B26/B27/B28/B66/B85
52 * Ultra-low power consumption
53 * 1 ~~ 3 External Temperature Probes
54 * Measure range -55°C ~~ 125°C
55 * Temperature alarm
56 * Multiply Sampling and one uplink
57 * Uplink via MQTT, MQTTs, TCP, UDP or CoAP
58 * GNSS for Location Report
59 * Support Bluetooth v5.1 remote configure and update firmware
60 * Uplink on periodically
61 * Downlink to change configure
62 * 8500mAh Battery for long term use
63 * Nano SIM card slot for NB-IoT SIM
64
65 == 1.3 Specification ==
66
67
68 (% style="color:blue" %)**Common DC Characteristics:**
69
70 * Supply Voltage: 2.6v ~~ 3.6v
71 * Operating Temperature: -40 ~~ 85°C
72
73 (% style="color:blue" %)**Temperature Sensor:**
74
75 * Dallas DS18B20
76 * Range: -55 to + 125°C
77 * Accuracy ±0.5°C (max ±2.0 °C)
78
79 (% style="color:blue" %)**NB-IoT Spec:**
80
81 (% style="color:#037691" %)**NB-IoT Module: BG95-NGFF**
82
83 (% style="color:#037691" %)**Support Bands:**
84
85 * B1 @H-FDD: 2100MHz
86 * B2 @H-FDD: 1900MHz
87 * B3 @H-FDD: 1800MHz
88 * B4 @H-FDD: 2100MHz
89 * B5 @H-FDD: 860MHz
90 * B8 @H-FDD: 900MHz
91 * B12 @H-FDD: 720MHz
92 * B13 @H-FDD: 740MHz
93 * B17 @H-FDD: 730MHz
94 * B18 @H-FDD: 870MHz
95 * B19 @H-FDD: 870MHz
96 * B20 @H-FDD: 790MHz
97 * B25 @H-FDD: 1900MHz
98 * B28 @H-FDD: 750MHz
99 * B66 @H-FDD: 2000MHz
100 * B70 @H-FDD: 2000MHz
101 * B85 @H-FDD: 700MHz
102
103 (% style="color:blue" %)**Battery:**
104
105 * Li/SOCI2 un-chargeable battery
106 * Capacity: 8500mAh
107 * Self Discharge: <1% / Year @ 25°C
108 * Max continuously current: 130mA
109 * Max boost current: 2A, 1 second
110
111 (% style="color:blue" %)**Power Consumption**
112
113 * STOP Mode: 10uA @ 3.3v
114 * Max transmit power: 350mA@3.3v
115
116 (% class="wikigeneratedid" %)
117 (% style="display:none" %) (%%)
118
119
120 == 1.4 Applications ==
121
122
123 * Smart Buildings & Home Automation
124 * Logistics and Supply Chain Management
125 * Smart Metering
126 * Smart Agriculture
127 * Smart Cities
128 * Smart Factory
129
130 == 1.5 Sleep mode and working mode ==
131
132
133 (% 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.
134
135 (% 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.
136
137
138 == 1.6 Button & LEDs ==
139
140
141 [[image:Main.User Manual for LoRaWAN End Nodes.D20-LBD22-LBD23-LB_LoRaWAN_Temperature_Sensor_User_Manual.WebHome@1675071855856-879.png]]
142
143
144 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %)
145 |=(% 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**
146 |(% style="width:167px" %)Pressing ACT between 1s < time < 3s|(% style="width:117px" %)Send an uplink|(% style="width:225px" %)(((
147 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.
148 Meanwhile, BLE module will be active and user can connect via BLE to configure device.
149 )))
150 |(% style="width:167px" %)Pressing ACT for more than 3s|(% style="width:117px" %)Active Device|(% style="width:225px" %)(((
151 (% 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.
152 (% style="color:green" %)**Green led**(%%) will solidly turn on for 5 seconds after joined in network.
153 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.
154 )))
155 |(% 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.
156
157 (% 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.**
158
159
160 == 1.7 BLE connection ==
161
162
163 D2x-CB support BLE remote configure and firmware update.
164
165
166 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:
167
168 * Press button to send an uplink
169 * Press button to active device.
170 * Device Power on or reset.
171
172 If there is no activity connection on BLE in 60 seconds, sensor will shut down BLE module to enter low power mode.
173
174
175 == 1.8 Pin Definitions , Switch & SIM Direction ==
176
177
178 D2x-CB use the mother board from D2x-CB which as below.
179
180 [[image:image-20240716143323-1.png]]
181
182
183 === 1.8.1 Jumper JP2 ===
184
185
186 Power on Device when put this jumper.
187
188
189 === 1.8.2 BOOT MODE / SW1 ===
190
191
192 **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.
193
194 **2)** (% style="color:blue" %)**Flash**(%%): work mode, device starts to work and send out console output for further debug
195
196
197 === 1.8.3 Reset Button ===
198
199
200 Press to reboot the device.
201
202
203 === 1.8.4 SIM Card Direction ===
204
205 See this link. [[How to insert SIM Card>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H2.AttachNetwork]].
206
207
208 == 1.9 Hardware Variant ==
209
210
211 (% border="1" cellspacing="3" style="width:510px" %)
212 |=(% style="width: 102px;background-color:#4F81BD;color:white" %)Model|=(% style="width: 190px;background-color:#4F81BD;color:white" %)Photo|=(% style="width: 218px;background-color:#4F81BD;color:white" %)Probe Info
213 |(% style="width:102px" %)D20-CB|(% style="width:190px" %)[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/D20-LBD22-LBD23-LB_LoRaWAN_Temperature_Sensor_User_Manual/WebHome/image-20230526153320-2.jpeg?rev=1.1||alt="image-20230526153320-2.jpeg"]](((
214
215 )))|(% style="width:297px" %)(((
216 1 x DS28B20 Probe
217
218 Cable Length : 2 meters
219
220
221 )))
222 |(% style="width:102px" %)D20S-CB|(% style="width:190px" %)[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/D20-LBD22-LBD23-LB_LoRaWAN_Temperature_Sensor_User_Manual/WebHome/image-20230526150859-1.jpeg?rev=1.1||alt="image-20230526150859-1.jpeg"]](((
223
224 )))|(% style="width:297px" %)(((
225 1 x DS28B20 Probe (Suitable for bury in soil)
226
227 Material: TPE, Cable Length: 2meters
228 )))
229 |(% style="width:102px" %)D22-CB|(% style="width:190px" %)[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/D20-LBD22-LBD23-LB_LoRaWAN_Temperature_Sensor_User_Manual/WebHome/image-20230526153345-3.jpeg?rev=1.1||alt="image-20230526153345-3.jpeg"]](((
230
231 )))|(% style="width:297px" %)(((
232 2 x DS28B20 Probes
233
234 Cable lengths total 1.5meters per probe
235
236 Cable Drawing: [[See This Link>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LSN50v2-D20/Cable_Drawing/&file=CAB0-35IC-K21G-210811.pdf]]
237 )))
238 |(% style="width:102px" %)(((
239 (((
240 D23-CB
241 )))
242
243 (((
244
245 )))
246 )))|(% style="width:190px" %)[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/D20-LBD22-LBD23-LB_LoRaWAN_Temperature_Sensor_User_Manual/WebHome/image-20230526153417-4.jpeg?rev=1.1||alt="image-20230526153417-4.jpeg"]](((
247
248 )))|(% style="width:297px" %)(((
249 3 x DS28B20 Probes
250
251 Cable lengths total 1.5meters per probe
252
253 Cable Drawing: [[See This Link>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LSN50v2-D20/Cable_Drawing/&file=CAB0-35IC-K31G-210811.pdf]]
254 )))
255
256 (% style="display:none" %)
257
258
259
260 = 2. Use D2x-CB to communicate with IoT Server =
261
262 == 2.1 Send data to IoT server via NB-IoT/CAT-M1 network ==
263
264
265 The D2x-CB is equipped with a NB-IoT module, the pre-loaded firmware in D2x-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 D2x-CB.
266
267 Below shows the network structure:
268
269 [[image:image-20240722084453-1.jpeg]]
270
271
272 There are two version: (% style="color:blue" %)**-GE**(%%) and (% style="color:blue" %)**-1T**(%%) version of D2x-CB.
273
274
275 (% 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 D2x-CB send data to IoT server.
276
277 * 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]].
278
279 * 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]]. 
280
281 Below shows result of different server as a glance.
282
283 (% border="1" cellspacing="3" style="width:515px" %)
284 |(% 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**
285 |(% 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" %)(((
286 (% style="text-align:center" %)
287 [[image:image-20230819113244-8.png||height="183" width="367"]]
288 )))|(% style="width:170px" %)
289 |(% 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" %)(((
290 (% style="text-align:center" %)
291 [[image:image-20230819113244-9.png||height="119" width="367"]]
292 )))|(% style="width:170px" %)
293 |(% 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" %)
294 |(% 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" %)
295 |(% 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" %)
296 |(% 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" %)(((
297 (% style="text-align:center" %)
298 [[image:image-20230819113244-10.png||height="104" width="367"]]
299 )))|(% style="width:170px" %)
300 |(% 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" %)(((
301 (% style="text-align:center" %)
302 [[image:image-20230819113244-11.png||height="141" width="367"]]
303 )))|(% style="width:170px" %)
304
305 (% 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 D2x-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/]].
306
307
308 == 2.2 ​Payload Types ==
309
310
311 To meet different server requirement, D2x-CB supports different payload type.
312
313 **Includes:**
314
315 * [[General JSON format payload>>||anchor="H2.2.1GeneralJsonFormat28Type3D529"]]. (Type=5)
316
317 * [[HEX format Payload>>||anchor="H2.2.2HEXformatPayload28Type3D029"]]. (Type=0)
318
319 * [[ThingSpeak Format>>||anchor="H2.2.4ThingSpeakPayload28Type3D129"]]. (Type=1)
320
321 * [[ThingsBoard Format>>||anchor="H2.2.3ThingsBoardPayload28Type3D329"]]. (Type=3)
322
323 User can specify the payload type when choose the connection protocol. Example:
324
325 (% style="color:#037691" %)**AT+PRO=2,0**  (%%) ~/~/ Use UDP Connection & hex Payload
326
327 (% style="color:#037691" %)**AT+PRO=2,5**   (%%) ~/~/ Use UDP Connection & Json Payload
328
329 (% style="color:#037691" %)**AT+PRO=3,5 ** (%%) ~/~/ Use MQTT Connection & Json Payload
330
331
332 === 2.2.1 General Json Format(Type~=5) ===
333
334
335 **(D23-CB)**This is the General Json Format. As below:
336
337 (% style="color:#4472c4" %)**{"IMEI":"868508065628110","IMSI":"460240210507481","Model":"D23-CB","temperature1":28.1,"temperature2":28.7,"temperature3":28.5,"interrupt":0,"interrupt_level":0,"battery":3.15,"signal":23,"time":"2024-12-09T08:02:48Z","latitude":0.000000,"longitude":0.000000,"gps_time":"1970-01-01T00:00:00Z","1":[204.8,1.0,0.4,"2024-12-09T07:47:05Z"],"2":[204.8,1.0,0.4,"2024-12-09T07:32:05Z"],"3":[23.3,54.2,0.4,"2024-12-09T06:09:17Z"],"4":[23.1,53.9,0.4,"2024-12-09T05:54:17Z"],"5":[22.5,54.8,0.4,"2024-12-09T05:39:17Z"],"6":[21.6,55.2,1.3,"2024-12-09T05:24:17Z"],"7":[21.8,55.1,1.3,"2024-12-09T05:09:17Z"],"8":[21.7,55.4,1.3,"2024-12-09T04:54:17Z"]}**
338
339 [[image:image-20241209160643-1.png]]
340
341
342 (% style="color:red" %)**Notice, from above payload:**
343
344 * Temperature1 , Temperature2, Temperature3, Interrupt, Interrupt_level, Battery, Signal, Latitude, Longitude & GPS_time are the value at uplink time.
345
346 * 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): Temperature1, Temperature2, Temperature3, Sampling time.
347
348 === 2.2.2 HEX format Payload(Type~=0) ===
349
350
351 This is the HEX Format. As below:
352
353 (% style="color:#4472c4" %)**f868508065628110f460240210507481496e0c9218010000000000011c012701206756a5650000000000000000000000000800000a00046756a0790800000a000467569cf500e9021e00046756898d00e7021b00046756860900e1022400046756828500d80228000d67567f0100da0227000d67567b7d00d9022a000d675677f9**
354
355 [[image:image-20241226095653-1.png||height="287" width="1727"]]
356
357
358 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
359
360 [[image:image-20241209160959-2.png]]
361
362
363 (% style="color:blue" %)**Version:**
364
365 These bytes include the hardware and software version.
366
367 (% style="color:#037691" %)**Higher byte:**(%%) Specify Sensor Model: 0x49 for D2x-CB
368
369 (% style="color:#037691" %)**Lower byte:**(%%) Specify the software version: 0x6e=110, means firmware version 1.1.0
370
371
372 (% style="color:blue" %)**BAT (Battery Info):**
373
374 Ex1: 0x0cea = 3306mV
375
376
377 (% style="color:blue" %)**Signal Strength:**
378
379 NB-IoT Network signal Strength.
380
381 **Ex1: 0x1C = 28**
382
383 **0**  -113dBm or less
384
385 **1**  -111dBm
386
387 **2...30** -109dBm... -53dBm
388
389 **31**   -51dBm or greater
390
391 **99**    Not known or not detectable
392
393
394 (% style="color:blue" %)**ADC:**
395
396 Ex1: 0x0000=0  /The error value is 50mV.
397
398 Ex2: 0x0b94 =2964= 2964.00mv
399
400
401 (% style="color:blue" %)**PA4_level:**
402
403 Level of PA4 pin. (0: Low level  1: High level)
404
405
406 (% style="color:blue" %)**Interrupt:**
407
408 This data field shows if this packet is generated by interrupt or not.
409
410 **Example:**
411
412 If byte[0]&0x01=0x00 : Normal uplink packet.
413
414 If byte[0]&0x01=0x01 : Interrupt Uplink Packet.
415
416
417 (% style="color:blue" %)**Interrupt_level:**
418
419 This byte shows whether the interrupt is triggered by a high or low level.
420
421 **Ex1:** 0x00  Interrupt triggered by falling edge (low level)
422
423 **Ex2: **0x01  Interrupt triggered by rising edge (high level)
424
425
426 (% style="color:blue" %)**Temperature: **
427
428 If payload is: 0105H:  (0105 & 8000 == 0), temp = 0105H /10 = 26.1 degree
429
430 If payload is: FF3FH :  (FF3F & 8000 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees.
431
432 (FF3F & 8000: Judge whether the highest bit is 1, when the highest bit is 1, it is negative)
433
434 If payload is: FFFF(H): (FFFF & 8000 == 1), Fixed display temp = -409.5℃, Indicates that the DS18B20 sensor is not connected, or no data.
435
436
437 (% style="color:blue" %)**TimeStamp/GPS_Timestamp:   **
438
439 Unit TimeStamp Example: 668613d7(H) = 1720062935(D)
440
441 Put the decimal value into this link([[https:~~/~~/www.epochconverter.com)>>https://www.epochconverter.com]]) to get the time.
442
443
444 (% style="color:blue" %)**Latitude:**
445
446 **Example: **0x015a758e(H)=22705550(D)=22.705550
447
448
449 (% style="color:blue" %)**Longitude:**
450
451 **Example: **0x06cf36da(H)=114243290(D)=114.243290
452
453
454 === 2.2.3 ThingsBoard Payload(Type~=3) ===
455
456
457 Type3 payload special design for ThingsBoard, it will also configure other default server to ThingsBoard.
458
459 (% style="color:#4472c4" %)**{
460 "topic": "002_CB",
461 "payload": {
462 "IMEI": "868508065628110",
463 "IMSI": "460240210507481",
464 "Model": "D23-CB",
465 "temperature1": 28.1,
466 "temperature2": 29.3,
467 "temperature3": 28.8,
468 "interrupt": 0,
469 "interrupt_level": 0,
470 "battery": 3.14,
471 "signal": 24,
472 "time": "2024-12-09T08:14:39Z",
473 "latitude": 0.0,
474 "longitude": 0.0,
475 "gps_time": "1970-01-01T00:00:00Z",
476 "1": [204.8, 1.0, 0.4, "2024-12-09T07:47:05Z"],
477 "2": [204.8, 1.0, 0.4, "2024-12-09T07:32:05Z"],
478 "3": [23.3, 54.2, 0.4, "2024-12-09T06:09:17Z"],
479 "4": [23.1, 53.9, 0.4, "2024-12-09T05:54:17Z"],
480 "5": [22.5, 54.8, 0.4, "2024-12-09T05:39:17Z"],
481 "6": [21.6, 55.2, 1.3, "2024-12-09T05:24:17Z"],
482 "7": [21.8, 55.1, 1.3, "2024-12-09T05:09:17Z"],
483 "8": [21.7, 55.4, 1.3, "2024-12-09T04:54:17Z"]
484 }
485 }**
486
487 [[image:image-20241209161612-3.png||height="462" width="1144"]]
488
489
490 === 2.2.4 ThingSpeak Payload(Type~=1) ===
491
492
493 This payload meets ThingSpeak platform requirement. It includes only four fields. Form 1~~5 are:
494
495 Temperature1, Temperature 2, Temperature 3,Battery & Signal. This payload type only valid for ThingsSpeak Platform
496
497 As below:
498
499 (% style="color:#4472c4" %)**field1=temp1 value&field2=temp2 value&field3=temp3 value&field4=Battery value&field5=Signal value**
500
501 [[image:image-20240710103122-5.png]]
502
503 [[image:image-20240710103236-6.png]]
504
505
506 == 2.3 Uplink Payload ==
507
508
509 (((
510 D2x-CB will uplink payload via NB-IoT with below payload format:
511 )))
512
513 (((
514 Uplink payload includes in total 29 bytes.
515 )))
516
517 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:517px" %)
518 |=(% style="width: 53px; background-color: rgb(79, 129, 189); color: white;" %)Size(bytes)|=(% style="width: 38px; background-color: rgb(79, 129, 189); color: white;" %)8|=(% style="width: 28px; background-color: rgb(79, 129, 189); color: white;" %)2|=(% style="width: 28px;background-color:#4F81BD;color:white" %)2|=(% style="width: 40px; background-color: rgb(79, 129, 189); color: white;" %)1|=(% style="background-color: rgb(79, 129, 189); color: white; width: 30px;" %)1|=(% style="width: 30px; background-color: rgb(79, 129, 189); color: white;" %)2|=(% style="width: 40px; background-color: rgb(79, 129, 189); color: white;" %)1|=(% style="width: 40px; background-color: rgb(79, 129, 189); color: white;" %)1|=(% style="background-color: rgb(79, 129, 189); color: white; width: 42px;" %)1|=(% style="width: 34px; background-color: rgb(79, 129, 189); color: white;" %)2|=(% style="width: 34px; background-color: rgb(79, 129, 189); color: white;" %)2|=(% style="width: 34px; background-color: rgb(79, 129, 189); color: white;" %)2|=(% style="width: 47px; background-color: rgb(79, 129, 189); color: white;" %)4
519 |(% style="width:38px" %)Value|(% style="width:45px" %)f+IMEI|(% style="width:30px" %)Ver|(% style="width:30px" %)BAT|(% style="width:40px" %)(((
520 Signal Strength
521 )))|(% style="width:30px" %)Mod|(% style="width:30px" %)ADC |(% style="width:40px" %)PA4_level|(% style="width:40px" %)Interrupt|(% style="width:42px" %)(((
522 Interrupt
523 _level
524 )))|(% style="width:35px" %)(((
525 Temp1 (% style="color:red" %)**(PC13)**
526 )))|(% style="width:35px" %)(((
527 Temp2 (% style="color:red" %)**(PB9)**
528 )))|(% style="width:35px" %)(((
529 Temp3 (% style="color:red" %)**(PB8)**
530 )))|(% style="width:52px" %)Timestamp
531
532 (((
533 If the cache upload mechanism is turned on, you will receive the payload shown in the figure below.
534 )))
535
536 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:512px" %)
537 |(% style="width:115px" %)**Frame header**|(% style="width:118px" %)**Frame data(1)**|(% style="width:116px" %)**Frame data(2)**|(% style="width:39px" %)**F…**|(% style="width:117px" %)**Frame data(X)**
538
539 === (% style="color:blue" %)**Decode corresponding probe color**(%%) ===
540
541 **D20:**
542
543 Red <~-~-> C1
544
545
546 **D22:**
547
548 White <~-~-> C1 , Red <~-~-> C2
549
550
551 **D23:**
552
553 White <~-~->C1  , Red <~-~-> C2  , Black <~-~-> C3
554
555
556 === (% style="color:blue" %)**Temperature RED or Temperature White**(%%) ===
557
558 (% style="color:red" %)**This point to the Red probe in D20-CB or the probe of D22-CB/D23-CB White**
559
560 When the cache upload mechanism is turned on and the sensor is not identified, the uploaded real-time data is FFFF and the uploaded historical data is F001.
561
562
563 **Example**:
564
565 **Real-time data:**
566
567 If payload is: 0105H:  (0105 & 8000 == 0), temp = 0105H /10 = 26.1 degree
568
569 If payload is: FF3FH :  (FF3F & 8000 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees.
570
571 (FF3F & 8000：Judge whether the highest bit is 1, when the highest bit is 1, it is negative)
572
573 When no sensor is identified,payload is: FFFFH : (FFFF&8000 == 1),temp = (FFFFH-65536)/10=-409.5 degrees.
574
575 (FF3F & 8000：Judge whether the highest bit is 1, when the highest bit is 1, it is negative)
576
577 **Caching data:**
578
579 If payload is: 0109H:  (0105 & 8000 == 0), temp = 0105H /10 = 26.5 degree
580
581 if payload is: F001H: (F001&8000 == 1),temp = (F001-65536)/10 = -409.5 degrees.
582
583 (F001 & 8000：Judge whether the highest bit is 1, when the highest bit is 1, it is negative)
584
585
586 === (% style="color:blue" %)**Temperature White**(%%) ===
587
588 (% style="color:red" %)**This point to the Red probe in D22-CB/D23-CB.**
589
590 When the cache upload mechanism is turned on and the sensor is not identified, the uploaded real-time data is FFFF and the uploaded historical data is F001.
591
592
593 **Example**:
594
595 **Real-time data:**
596
597 If payload is: 0105H:  (0105 & 8000 == 0), temp = 0105H /10 = 26.1 degree
598
599 If payload is: FF3FH :  (FF3F & 8000 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees.
600
601 (FF3F & 8000：Judge whether the highest bit is 1, when the highest bit is 1, it is negative)
602
603 When no sensor is identified,payload is: FFFFH : (FFFF&8000 == 1),temp = (FFFFH-65536)/10=-409.5 degrees.
604
605 (FF3F & 8000：Judge whether the highest bit is 1, when the highest bit is 1, it is negative)
606
607 **Caching data:**
608
609 If payload is: 0109H:  (0105 & 8000 == 0), temp = 0105H /10 = 26.5 degree
610
611 if payload is: F001H: (F001&8000 == 1),temp = (F001-65536)/10 = -409.5 degrees.
612
613 (F001 & 8000：Judge whether the highest bit is 1, when the highest bit is 1, it is negative)
614
615
616 === (% style="color:blue" %)**Temperature Black**(%%) ===
617
618 (% style="color:red" %)**This point to the BLACK probe in D23-CB**
619
620 When the cache upload mechanism is turned on and the sensor is not identified, the uploaded real-time data is FFFF and the uploaded historical data is F001.
621
622
623 **Example**:
624
625 **Real-time data:**
626
627 If payload is: 0105H:  (0105 & 8000 == 0), temp = 0105H /10 = 26.1 degree
628
629 If payload is: FF3FH :  (FF3F & 8000 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees.
630
631 (FF3F & 8000：Judge whether the highest bit is 1, when the highest bit is 1, it is negative)
632
633 When no sensor is identified,payload is: **FFFF**H : (FFFF & 8000 == 1),temp = (**FFFF**H - 65536)/10=-409.5 degrees.
634
635 (FF3F & 8000：Judge whether the highest bit is 1, when the highest bit is 1, it is negative)
636
637 **Caching data:**
638
639 If payload is: 0109H:  (0105 & 8000 == 0), temp = 0105H /10 = 26.5 degree
640
641 if payload is: F001H: (F001&8000 == 1),temp = (F001-65536)/10 = -409.5 degrees.
642
643 (F001 & 8000：Judge whether the highest bit is 1, when the highest bit is 1, it is negative)
644
645
646 = 3. Configure D2x-CB =
647
648 == 3.1 Configure Methods ==
649
650
651 D2x-CB supports below configure method:
652
653 * AT Command via Bluetooth Connection (**Recommended**): [[BLE Configure Instruction>>http://wiki.dragino.com/xwiki/bin/view/Main/BLE%20Bluetooth%20Remote%20Configure/]].
654
655 * 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]].
656
657 ​​​
658
659 == 3.2  Serial Access Password ==
660
661
662 After the Bluetooth or UART connection is successful, use the Serial Access Password to enter the AT command window.
663
664 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.
665
666 [[image:image-20240826182452-2.png]]
667
668
669 If you need to change the password, use **AT+PWORD=**xxxxxx (6 characters), -CB nodes only support lowercase letters.
670
671 [[image:image-20240826182457-3.png]]
672
673
674 (% 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.**
675
676 [[image:image-20240826182505-4.png]]
677
678
679 == 3.3 AT Commands Set ==
680
681
682 AT+<CMD>? : Help on <CMD>
683
684 AT+<CMD> : Run <CMD>
685
686 AT+<CMD>=<value> : Set the value
687
688 AT+<CMD>=? : Get the value
689
690
691 (% style="color:blue" %)**General Commands**      
692
693 AT                    : Attention       
694
695 AT?  : Short Help     
696
697 ATZ : Trig a reset of the MCU
698
699 AT+MODEL : Get module information
700
701 AT+CFGMOD : Working mode selection
702
703 AT+DEUI : Get or set the Device ID
704
705 AT+CFG : Print all settings
706
707 AT+SERVADDR: Get or Set the Server address
708
709 AT+TDC : Get or set the application data transmission interval in s
710
711 AT+INTMOD : Get or Set the trigger interrupt mode (0:input,1:falling or rising,2:falling,3:rising)
712
713 AT+APN : Get or set the APN
714
715 AT+5VT : Get or Set extend the time of 5V power
716
717 AT+PRO : Get or Set usage agreement (1:COAP,2:UDP,3:MQTT,4:TCP)
718
719 AT+RXDL : Get or Set the receiving time
720
721 AT+EXT : Get or Set Count value
722
723 ATAT+TEMPALARM1:Get or Set alarm of temp1
724
725 ATAT+TEMPALARM2:Get or Set alarm of temp2
726
727 ATAT+TEMPALARM3:Get or Set alarm of temp3
728
729 AT+GETSENSORVALUE : Returns the current sensor measurement
730
731 AT+DNSCFG : Get or Set DNS Server
732
733 AT+CSQTIME : Get or Set the time to join the network
734
735 AT+GDNS : Get or Set the DNS
736
737 AT+TLSMOD : Get or Set the TLS mode
738
739 AT+SLEEP : Get or Set the sleep mode
740
741 AT+MQOS : Set the QoS level of MQTT
742
743 AT+IPTYPE : Set the IPv4 or IPv6
744
745 AT+QSW : Power on and power off BG95 module
746
747 AT+GETLOG : Print serial port logs
748
749 AT+CLOCKLOG: Get or set SHT record time
750
751 AT+QBAND: Get or set Frequency Band
752
753 AT+IOTMOD: Configure Network Category to be Searched for under LTE RAT
754
755
756 (% style="color:blue" %)**MQTT Management**
757
758 AT+CLIENT : Get or Set the MQTT clientID
759
760 AT+UNAME : Get or Set the MQTT Username
761
762 AT+PWD : Get or Set the MQTT password
763
764 AT+PUBTOPIC: Get or set MQTT publishing topic
765
766 AT+SUBTOPIC: Get or set MQTT subscription topic
767
768
769 (% style="color:blue" %)**Coap Management:**
770
771 AT+URI1: Get or set CoAP option 1
772
773 AT+URI2: Get or set CoAP option 2
774
775 AT+URI3: Get or set CoAP option 3
776
777 AT+URI4: Get or set CoAP option 4
778
779 AT+URI5: Get or set CoAP option 5
780
781 AT+URI6: Get or set CoAP option 6
782
783 AT+URI7: Get or set CoAP option 7
784
785 AT+URI8: Get or set CoAP option 8
786
787
788 (% style="color:blue" %)**GPS:**
789
790 AT+GNSST : Extend the time to turn on GNSS
791
792 AT+GPS : Turn off and on GPS
793
794 AT+GTDC : Get or set GPS positioning interval in units of h
795
796
797 (% style="color:blue" %)**Information**          
798
799 AT+FDR1 : Reset parameters to factory default values except for passwords
800
801 AT+FDR : Reset Parameters to Factory Default
802
803 AT+PWORD : Get or set the System password
804
805 AT+CDP : Read or Clear cached data
806
807 AT+LDATA : Get the last upload data
808
809
810 == 3.4 Test Uplink and Change Update Interval ==
811
812
813 By default, Sensor will send uplinks **every 2 hours.**
814
815 User can use below commands to change the uplink interval.
816
817 (% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+TDC** (%%)
818
819 Example: AT+TDC=600  ~/~/ Set Update Interval to 600 seconds
820
821 (% style="color:blue" %)**Downlink Commands: **(% style="color:#037691" %)**0x01**
822
823 Format: Command Code (0x01) followed by 3 bytes.
824
825 Example:  12 hours= 43200 seconds  43200(D)=0xA8C0(H)
826
827 Downlink Payload: **01 00 A8 C0**  ~/~/ AT+TDC=43200, Set Update Interval to 12 hours.
828
829 (% style="color:red" %)**Note: User can also push the button for more than 1 seconds to activate an uplink.**
830
831
832 == 3.5 Set the receiving time ==
833
834
835 Feature: Extend the receiving time
836
837 (% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+RXDL**
838
839 Example: AT+RXDL=1000  ~/~/ Set the receiving time delay to 1000ms
840
841 (% style="color:blue" %)**Downlink Commands: **(% style="color:#037691" %)**0x03**
842
843 Format: Command Code (0x03) followed by 3 bytes.
844
845 Example:  Downlink Payload: **03 00 03 E8     **~/~/ AT+RXDL=1000
846
847
848 == 3.6 Reset ==
849
850
851 Feature: Trig a reset of the MCU.
852
853 (% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**ATZ**
854
855 (% style="color:blue" %)**Downlink Commands: **(% style="color:#037691" %)**0x04FF**
856
857
858 == 3.7 +5V ==
859
860
861 Feature: Set extend the time of 5V power.
862
863 (% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+5VT**
864
865 Example: AT+5VT=2000  ~/~/Set extend the time of 5V power to 2000 ms
866
867 (% style="color:blue" %)**Downlink Commands: **(% style="color:#037691" %)**0x05**
868
869 Format: Command Code (0x05) followed by 3 bytes.
870
871 Example:  Downlink Payload: **05 00 07 D0    **~/~/ AT+5VT=2000
872
873
874 == 3.8 Trigger an uplink by external interrupt ==
875
876
877 D2x-CB has an external trigger interrupt function. Users can use the PB15 pin to trigger the upload of data packets.
878
879 (% style="color:blue" %)**AT command:**
880
881 * (% style="color:#037691" %)**AT+INTMOD **(%%) ~/~/ Set the trigger interrupt mode
882
883 * (% style="color:#037691" %)**AT+INTMOD=0 **(%%) ~/~/ Disable Interrupt
884
885 * (% style="color:#037691" %)**AT+INTMOD=1 **(%%) ~/~/ Trigger by rising and falling edge
886
887 * (% style="color:#037691" %)**AT+INTMOD=2 **(%%) ~/~/ Trigger by falling edge
888
889 * (% style="color:#037691" %)**AT+INTMOD=3  **(%%) ~/~/ Trigger by rising edge
890
891 (% style="color:blue" %)**Downlink Commands: **(% style="color:#037691" %)**0x06**
892
893 Format: Command Code (0x06) followed by 3 bytes.
894
895 Example1:  Downlink Payload: **06 00 00 01    **~/~/AT+INTMOD=1
896
897 Example2:  Downlink Payload: **06 00 00 03    **~/~/AT+INTMOD=3
898
899
900 == 3.9 Set the QoS level ==
901
902
903 This command is used to set the QoS level of **MQTT**.
904
905 (% style="color:blue" %)**AT command:**
906
907 * (% style="color:#037691" %)**AT+MQOS=xx**(%%)**   **~/~/ 0~~2
908
909 (% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x07(%%)**
910
911 Format: Command Code (0x07) followed by 1 byte.
912
913 **Ex1:** Downlink payload: **0x0700**  ~/~/ AT+MQOS=0
914
915 **Ex2:** Downlink payload: **0x0701**  ~/~/ AT+MQOS=1
916
917
918 == 3.10 Clock logging ==
919
920
921 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.
922
923 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.
924
925 (% style="color:blue" %)**AT command:**(%%)** (% style="color:#037691" %)AT+CLOCKLOG=a,b,c,d(%%)**
926
927 (% style="color:#037691" %)**a: **(%%)**0:** Disable Clock logging.  ** 1: **Enable Clock Logging
928
929 (% 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.
930
931 (% style="color:#037691" %)**c: **(%%)Specify the sampling interval: range **(0 ~~ 255 minutes)**
932
933 (% style="color:#037691" %)**d:**(%%)** **How many entries should be uplink on every TDC **(max 32)**
934
935 (% style="color:red" %)**Note: To disable clock recording, set the following parameters: AT+CLOCKLOG=1,65535,0,0**
936
937 [[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"]]
938
939 **Example:**
940
941 **AT+CLOCKLOG=1,65535,1,5**
942
943 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).
944
945 [[image:image-20240712103240-1.png||height="626" width="1330"]]
946
947
948 (% class="wikigeneratedid" %)
949 (% 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.**
950
951 (% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x08(%%)**
952
953 Format: Command Code (0x08) followed by 5 bytes.
954
955 * **Example 1**: Downlink Payload:** 08 01 FFFF 0F 08**  ~/~/ Set SHT record time: AT+CLOCKLOG=1,65535,15,8
956 * **Example 2**: Downlink Payload:** 08 01 04B0 0F 08**  ~/~/ Set SHT record time: AT+CLOCKLOG=1,1200,15,8
957
958 (% style="color:red" %)**Note: When entering the downlink payload, there must be no Spaces between bytes.**
959
960
961 == 3.11 Set the TLS mode ==
962
963
964 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.
965
966 (% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+TLSMOD**
967
968 **Example 1: ** AT+TLSMOD=0,0  ~/~/Disable TLS Mode.
969
970 **Example 2:**  AT+TLSMOD=1,0  ~/~/No authentication
971
972 AT+TLSMOD=1,1  ~/~/Perform server authentication
973
974 AT+TLSMOD=1,2  ~/~/Perform server and client authentication if requested by the remote server
975
976 (% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x09(%%)**
977
978 Format: Command Code (0x09) followed by 2 bytes.
979
980 Example1:  Downlink Payload: **09 00 00    **~/~/AT+TLSMOD=0,0
981
982 Example2:  Downlink Payload: **09 01 02    **~/~/AT+TLSMOD=1,2
983
984
985 == 3.12 Set GNSS open time ==
986
987
988 Extend the time to turn on GNSS. The automatic GPS location time is extended when the node is activated.
989
990 (% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+GNSST**
991
992 Example: AT+GNSST=30  ~/~/Set the GPS positioning time to 30 seconds
993
994 (% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x10(%%)**
995
996 Format: Command Code (0x10) followed by 2 bytes.
997
998 Example:  Downlink Payload: **10 00 1E    **~/~/AT+GNSST=30
999
1000
1001 == 3.13 Turn on/off GPS ==
1002
1003
1004 (% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+GPS **
1005
1006 **Ex1:  **AT+GPS=0  ~/~/Turn off GPS
1007
1008 **Ex2:  **AT+GPS=1  ~/~/Turn on GPS
1009
1010 (% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x11(%%)**
1011
1012 Format: Command Code (0x11) followed by 1 byte.
1013
1014 Example:  Downlink Payload: **11 01   **~/~/AT+GPS=1
1015
1016
1017 == 3.14 Set GPS positioning interval ==
1018
1019
1020 Feature: Set GPS positioning interval (unit: hour).
1021
1022 When GPS is enabled, the node automatically locates and uplinks each time it passes **GTDC time** after activation.
1023
1024 (% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+GTDC**
1025
1026 Example: AT+GTDC=24  ~/~/Set the GPS positioning interval to 24h.
1027
1028 (% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x12(%%)**
1029
1030 Format: Command Code (0x12) followed by 3 bytes.
1031
1032 Example: 24 hours:  24(D)=0x18(H)
1033
1034 Downlink Payload: **12 00 00 18  **~/~/AT+GTDC=24
1035
1036
1037 == 3.15 Set the search network time ==
1038
1039
1040 Feature: Get or Set the time to join the network(unit: minutes).
1041
1042 (% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+CSQTIME**
1043
1044 Example: AT+CSQTIME=10 ~/~/Set the search time to 10 minutes.
1045
1046 (% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x13(%%)**
1047
1048 Format: Command Code (0x13) followed by 1 byte.
1049
1050 Example:  Downlink Payload: **13 0A  **~/~/AT+CSQTIME=10
1051
1052
1053 == 3.16 Temperature Alarm Feature ==
1054
1055
1056 D2x-CB work flow with Alarm feature.
1057
1058 [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LSN50v2-D20-D22-D23%20LoRaWAN%20Temperature%20Sensor%20User%20Manual/WebHome/image-20220623090437-1.png?rev=1.1||alt="图片-20220623090437-1.png" height="727" width="1039"]]
1059
1060
1061 === (% style="color:red" %)**Set Alarm Thredhold**(%%) ===
1062
1063
1064 (% style="color:blue" %)**Set for Separate Probes:**
1065
1066
1067 (% style="color:#037691" %)**AT+TEMPALARM1 index=min,max**
1068
1069 Index:
1070
1071 * 1: Temperature_Red
1072 * 2: Temperature_White
1073 * 3: Temperature_Black
1074
1075 min,max:
1076
1077 * When min=max, Alarm is not enabled
1078 * When min=0, and max≠0, Alarm trigger when higher than max
1079 * When min≠0, and max=0, Alarm trigger when lower than min
1080 * When min≠0 and max≠0, Alarm trigger when higher than max or lower than min
1081
1082 (% style="color:#037691" %)**Downlink command: 0x0A**
1083
1084 Format: Command Code (0x0A) followed by 6 bytes.
1085
1086 The first and second bytes after 0x0A are min and max for temperature 1, the third and fourth bytes are min and max for temperature 2, and the fifth and sixth bytes are min and max for temperature 3.
1087
1088
1089 **Example:**
1090
1091 AT+TEMPALARM1=-10,30  ~/~/ Temperature 1 alarm when < -10 or higher than 30.
1092
1093 AT+TEMPALARM2=20,20  ~/~/ The alarm for temperature 2 is disabled.  ~-~->  Downlink payload: 0A  F6  1E 14 14 00 23                                    
1094
1095 AT+TEMPALARM3=0,35  ~/~/ Temperature 3 alarm when higher than 30.
1096
1097
1098 For the negative temperature x represented in the downlink payload, it can be calculated as follows:  256+x
1099
1100 Ex1: -10℃  256+(-10)= 246(D) =0xF6(H)
1101
1102 Ex2: -25℃  256+(-25)= 231(D) =0xE7(H)
1103
1104
1105 == 3.17 Set the IPv4 or IPv6 ==
1106
1107
1108 This command is used to set IP version.
1109
1110 (% style="color:blue" %)**AT command:**
1111
1112 * (% style="color:#037691; font-weight:bold" %)**AT+IPTYPE**(% style="color:#037691" %)**=1**(%%)**      **~/~/ IPv4
1113 * (% style="color:#037691; font-weight:bold" %)**AT+IPTYPE**(% style="color:#037691" %)**=2**(%%)**      **~/~/ IPv6
1114
1115 == 3.18 Configure Network Category to be Searched for under LTE RAT. ==
1116
1117
1118 (% style="color:blue" %)**AT command:**(%%)** (% style="color:#037691" %)AT+IOTMOD=xx(%%)**
1119
1120 (% style="color:#037691" %)**xx:**(%%)  **0:** eMTC
1121
1122 **1:** NB-IoT
1123
1124 **2:** eMTC and NB-IoT
1125
1126
1127 == 3.19 Factory data reset ==
1128
1129
1130 Two different restore factory Settings configurations.
1131
1132 (% style="color:blue" %)**AT command:**
1133
1134 * (% style="color:#037691; font-weight:bold" %)**AT+FDR**(%%)**       **~/~/ Reset Parameters to Factory Default.
1135 * (% style="color:#037691; font-weight:bold" %)**AT+FDR1**(%%)**     **~/~/ Reset parameters to factory default values **except for passwords**.
1136
1137 == 3.20 Set CoAP option ==
1138
1139
1140 Feature: Set CoAP option, follow this link to set up the CoaP protocol.
1141
1142 (% style="color:blue" %)**AT command: **(% style="color:#037691; font-weight:bold" %)**AT+URI1~~AT+URI8**
1143
1144 (% 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"
1145
1146 (% style="color:#037691; font-weight:bold" %)**AT+URI2=11,"CoAP endpoint URl"   **(%%)~/~/ 11 is a fixed parameter.
1147
1148 **Example: ** i/13a35fbe-9515-6e55-36e8-081fb6aacf86
1149
1150 AT+URI1=11,"i"
1151
1152 AT+URI2=11,"13a35fbe-9515-6e55-36e8-081fb6aacf86"
1153
1154 ~-~->If multiple groups of CoAP endpoint urls:
1155
1156 AT+URI3=11,"i"
1157
1158 AT+URI4=11,"CoAP endpoint URl"
1159
1160
1161 == 3.21 Power on / power off BG95 module ==
1162
1163
1164 This command is used to power on and power off BG95 module.
1165
1166 * (% style="color:blue" %)**AT command: **(% style="color:#037691" %)**AT+QSW**
1167
1168 The module is powered on after the command is sent for the first time, and powered off after the command is sent again.
1169
1170
1171 [[image:image-20240712104123-5.png||height="626" width="776"]]
1172
1173
1174 == 3.22 Example Query saved historical records ==
1175
1176
1177 * (% style="color:blue" %)**AT command:**(%%)** (% style="color:#037691" %)AT+CDP(%%)**
1178
1179 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.
1180
1181 (% class="wikigeneratedid" %)
1182 [[image:image-20240712103848-2.png||height="624" width="771"]]
1183
1184
1185 == 3.23 Uplink log query ==
1186
1187
1188 * (% style="color:blue" %)**AT command:**(%%)** (% style="color:#037691" %)AT+GETLOG(%%)**
1189
1190 This command can be used to query upstream logs of data packets.
1191
1192 [[image:image-20240712103938-3.png||height="634" width="779"]]
1193
1194
1195 == 3.24 Set the downlink debugging mode(Since firmware v1.1.0) ==
1196
1197
1198 Feature: Set the conversion between the standard version and 1T version downlinks.
1199
1200 (% style="color:blue" %)**AT command: AT+DOWNTE**
1201
1202 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %)
1203 |=(% 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**
1204 |(% style="width:134px" %)AT+DOWNTE=?|(% style="width:143px" %)Get current Settings|(% style="width:229px" %)(((
1205 0,0  (default)
1206 OK
1207 )))
1208 |(% colspan="1" rowspan="2" style="width:134px" %)(((
1209
1210
1211
1212
1213 AT+DOWNTE=a,b
1214 )))|(% style="width:143px" %)**a**: Set the conversion between the downlink of the standard version and 1T version|(% style="width:229px" %)(((
1215 **0**: Set the downlink of the standard version.
1216 **1**: Set the downlink of the 1T version(ThingsEye platform)
1217 )))
1218 |(% style="width:143px" %)**b**: Enable/Disable downlink debugging|(% style="width:229px" %)(((
1219 **0**: Disable downlink debugging mode.
1220 **1**: Enable downlink debugging mode, users can see the original downlink reception.
1221 )))
1222
1223 **Example:**
1224
1225 * AT+DOWNTE=0,1  ~/~/ Set to standard version downlink, and enable downlink debugging.
1226 * AT+DOWNTE=1,1  ~/~/ Set to 1T version downlink, and enable downlink debugging.
1227
1228 (% style="color:blue" %)**Downlink Command:  **
1229
1230 No downlink commands for feature
1231
1232
1233
1234 = 4. Battery & Power Consumption =
1235
1236
1237 D2x-CB use ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace.
1238
1239 [[**Battery Info & Power Consumption Analyze**>>http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] .
1240
1241
1242 = 5. Firmware update =
1243
1244
1245 User can change device firmware to::
1246
1247 * Update with new features.
1248
1249 * Fix bugs.
1250
1251 Firmware and changelog can be downloaded from : **[[Firmware download link>>https://www.dropbox.com/scl/fo/1mzflb9p9kx15btnc11gr/AEp3kdQy4VER0NWQeHrZxZ8/D2x-CB?dl=0&rlkey=ku98jt8u30coqy66saebai2co&subfolder_nav_tracking=1]]**
1252
1253 Methods to Update Firmware:
1254
1255 * (Recommended way) OTA firmware update via BLE: [[**Instruction**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/BLE_Firmware_Update_NB_Sensors_BC660K-GL/]].
1256
1257 * Update through UART TTL interface : **[[Instruction>>http://wiki.dragino.com/xwiki/bin/view/Main/UART_Access_for_NB_ST_BC660K-GL/#H4.2UpdateFirmware28Assumethedevicealreadyhaveabootloader29]]**.
1258
1259 = 6. FAQ =
1260
1261 == 6.1 How can I access the BG95-NGFF AT Commands? ==
1262
1263
1264 User can access to BG95-NGFF directly and send AT Commands.
1265
1266 [[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]]
1267
1268
1269 == 6.2 General Manual for -CB , -CS models ==
1270
1271
1272 Users can follow the instructions in this [[link>>url: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.
1273
1274
1275 = 7. Order Info =
1276
1277
1278 Part Number: (% style="color:blue" %)**D20-CB-XX  / D20S-CB**(%%)** (designed for used in Soil or Road)/(% style="color:blue" %)D22-CB-XX / D23-CB-XX(%%)**
1279
1280 (% style="color:red" %)**XX**(%%):
1281
1282 * (% style="color:#037691" %)**GE**(%%): General version ( Exclude SIM card)
1283
1284 * (% style="color:#037691" %)**1T**(%%): with 1NCE* 10 years 500MB SIM card and Pre-configure to ThingsEye server
1285
1286 = 8. ​Packing Info =
1287
1288
1289 (% style="color:#037691" %)**Package Includes**:
1290
1291 * D2x-CB NB-IoT/LTE-M Temperature Sensor x 1
1292
1293 * External antenna x 1
1294
1295 (% style="color:#037691" %)**Dimension and weight**:
1296
1297 * Device Size: cm
1298
1299 * Device Weight: g
1300
1301 * Package Size / pcs : cm
1302
1303 * Weight / pcs : g
1304
1305 = 9. Support =
1306
1307
1308 * 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.
1309
1310 * 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]].
1311
1312 (% style="display:none" %) (%%)

Applications

Navigation

Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0