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