Skip to Content
Last modified by Xiaoling on 2025/06/10 10:33
Show last authors
1 [[image:image-20241224165001-1.jpeg||data-xwiki-image-style-alignment="center"]]
2
3
4
5
6
7 **Table of Contents:**
8
9 {{toc/}}
10
11 (% aria-label="macro:toc widget" contenteditable="false" role="region" tabindex="-1" %)
12 (((
13 (% style="background-image:url(http://wiki1.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||height="15" role="presentation" title="Click and drag to move" width="15"]]
14 )))
15
16
17
18
19
20
21
22
23
24 = 1.  Introduction =
25
26 == 1.1 ​ What is LTC2-NB/NS NB-IoT Temperature Transmitter ==
27
28
29 The Dragino LTC2-NB/NS Industrial NB-IoT Temperature Transmitter is designed to monitor temperature for different environment. It supports to read (% style="color:blue" %)**PT100 probe**(%%) and convert the value to temperature and then upload to IoT server via NB-IoT network*.
30
31 LTC2-NB/NS has (% style="color:blue" %)**two internal 24-bit ADC interfaces**(%%).
32
33 LTC2-NB/NS (% style="color:blue" %)**supports BLE configure**(%%) and (% style="color:blue" %)**wireless OTA update**(%%) which make user easy to use.
34
35 LTC2-NB/NS supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP, MQTTs or CoAP**(%%) for different application requirement. and Support Uplinks to various IoT Servers.
36
37 LTC2-NB/NS is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery or solar powered + Li-ion battery,**(%%) It is designed for long term use up to several years. (Real-world battery life depends on the use environment, update period and uplink method. Please check related Power Analyze report).
38
39 *make sure you have NB-IoT coverage locally.
40
41
42 == ​1.2  Features ==
43
44
45 * NB-IoT Bands: B1/B2/B3/B4/B5/B8/B12/B13/B17/B18/B19/B20/B25/B28/B66/B70/B85 @H-FDD
46 * Ultra-low power consumption
47 * max: 2 x monitor temperature channels
48 * Support 3 -wire PT-100
49 * Temperature alarm
50 * Multiply Sampling and one uplink
51 * Uplink via MQTT, MQTTs, TCP, UDP or CoAP
52 * Support Bluetooth v5.1 remote configure and update firmware
53 * Uplink on periodically
54 * Downlink to change configure
55 * 8500mAh Battery for long term use  (LTC2-NB)
56 * Solar panel + 3000mAh Li-ion battery (LTC2-NS)
57
58 (% style="display:none" %)
59
60 == 1.3 Specification ==
61
62
63 (% style="color:blue" %)**Common DC Characteristics:**
64
65 * Supply Voltage: Built-in Battery , 2.5v ~~ 3.6v
66 * Operating Temperature: -40 ~~ 85°C
67
68 (% style="color:blue" %)**Temperature Sensor:**
69
70 * Range: -40 to + 80°C
71 * Accuracy: ±0.2 @ 0-90 °C
72 * Resolution: 0.1°C
73 * Long Term Shift: <0.03 °C/yr
74
75 (% style="color:blue" %)**NB-IoT Spec:**
76
77 (% style="color:#037691" %)**NB-IoT Module: BC660K-GL**
78
79 (% style="color:#037691" %)**Support Bands:**
80
81 * B1 @H-FDD: 2100MHz
82 * B2 @H-FDD: 1900MHz
83 * B3 @H-FDD: 1800MHz
84 * B4 @H-FDD: 2100MHz
85 * B5 @H-FDD: 860MHz
86 * B8 @H-FDD: 900MHz
87 * B12 @H-FDD: 720MHz
88 * B13 @H-FDD: 740MHz
89 * B17 @H-FDD: 730MHz
90 * B18 @H-FDD: 870MHz
91 * B19 @H-FDD: 870MHz
92 * B20 @H-FDD: 790MHz
93 * B25 @H-FDD: 1900MHz
94 * B28 @H-FDD: 750MHz
95 * B66 @H-FDD: 2000MHz
96 * B70 @H-FDD: 2000MHz
97 * B85 @H-FDD: 700MHz
98
99 (% style="color:blue" %)**Battery:**
100
101 * Li/SOCI2 un-chargeable battery
102 * Capacity: 8500mAh
103 * Self Discharge: <1% / Year @ 25°C
104 * Max continuously current: 130mA
105 * Max boost current: 2A, 1 second
106
107 (% style="color:blue" %)**Power Consumption**
108
109 * STOP Mode: 10uA @ 3.3v
110 * Max transmit power: 350mA@3.3v
111
112 == 1.4 ​ Applications ==
113
114
115 * Logistics and Supply Chain Management
116 * Food management
117 * Cold chains solution
118 * Industrial Monitoring and Control
119
120 == 1.5 Sleep mode and working mode ==
121
122
123 (% 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.
124
125 (% 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.
126
127
128 == 1.6 Button & LEDs ==
129
130
131 [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/RS485-LB_Waterproof_RS485UART_to_LoRaWAN_Converter/WebHome/image-20240103160425-4.png?rev=1.1||alt="image-20240103160425-4.png"]]
132
133 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %)
134 |=(% 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**
135 |[[image:1749522715132-552.png]] 1~~3s|(% style="background-color:#f2f2f2; width:117px" %)Send an uplink|(% style="background-color:#f2f2f2; width:225px" %)(((
136 If sensor has already attached to NB-IoT network, sensor will send an uplink packet, (% style="color:blue" %)**blue led**(%%) will blink once.
137 Meanwhile, BLE module will be active and user can connect via BLE to configure device.
138 )))
139 |[[image:1749522716915-729.png]] >3s|(% style="background-color:#f2f2f2; width:117px" %)Active Device|(% style="background-color:#f2f2f2; width:225px" %)(((
140 (% style="background-color:#f2f2f2; color:green" %)**Green led**(%%) will fast blink 5 times, device will enter (% style="color:#037691" %)**OTA mode**(%%) for 3 seconds. And then start to attach NB-IoT network.
141 Once sensor is active, BLE module will be active and user can connect via BLE to configure device, no matter if device attach NB-IoT network or not
142 )))
143 |[[image:1749522785197-807.png]] x5|(% style="background-color:#f2f2f2; width:117px" %)Deactivate Device|(% style="background-color:#f2f2f2; width:225px" %)(((
144 (% style="color:red" %)**Red led**(%%) will solid on for 5 seconds. Means device is in Deep Sleep Mode.
145 )))
146
147 == 1.7 BLE connection ==
148
149
150 LTC2-NB/NS support BLE remote configure and firmware update.
151
152 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:
153
154 * Press button to send an uplink
155 * Press button to active device.
156 * Device Power on or reset.
157
158 If there is no activity connection on BLE in 60 seconds, sensor will shut down BLE module to enter low power mode.
159
160
161 == 1.8 Pin Definitions , Switch & SIM Direction ==
162
163
164 [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/S31-NBS31B-NB_BN-IoT_Outdoor_Temperature_Humidity_Sensor_User_Manual/WebHome/image-20230819104805-5.png?rev=1.1||alt="image-20230819104805-5.png"]]
165
166 === 1.8.1 Jumper JP2 ===
167
168 Power on Device when put this jumper.
169
170 Power off device when take out this jumper
171
172
173 === 1.8.2 BOOT MODE / SW1 ===
174
175 **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.
176
177 **2)** (% style="color:blue" %)**Flash:**(%%) work mode, device starts to work and send out console output for further debug
178
179
180 === 1.8.3 Reset Button ===
181
182 Press to reboot the device.
183
184
185 === 1.8.4 SIM Card Direction ===
186
187 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]].
188
189
190 == 1.9 Mechanical ==
191
192 === 1.9.1 for NB version ===
193
194 [[image:image-20250328140611-1.jpeg]]
195
196 === 1.9.2 for NS version ===
197
198 [[image:image-20250328140630-2.jpeg]]
199
200
201 == 1.10  Probe Variant ==
202
203
204 LTC2-NB/NS provide default probe version. See below for the variant:
205
206 (% border="1" cellspacing="3" style="width:505px" %)
207 |=(% style="width: 78px;background-color:#4F81BD;color:white" %)(((
208 **Model**
209 )))|=(% style="width: 127px;background-color:#4F81BD;color:white" %)(((
210 **Photo**
211 )))|=(% style="width: 300px;background-color:#4F81BD;color:white" %)(((
212 **Description**
213 )))
214 |(% style="width:78px" %)(((
215 DR-SI
216 )))|(% style="width:117px" %)(((
217 [[image:image-20240905135914-8.png||data-xwiki-image-style-alignment="center" height="107" width="100"]]
218 )))|(% style="width:314px" %)(((
219 Standard IP68 Probe Version:
220
221 * LTC2-NB/NS with 1 x Standard IP68 PT100 probe.
222 * Installation: Insert
223 * Cable Length : 2m
224 * PT100 Class : Class A
225 * Probe Dimension: φ5*30mm
226 * Measure Range: -60 ~~ 200 °C
227 * Suitable Environment: General environment
228 )))
229 |(% style="width:78px" %)(((
230 DR-LT
231 )))|(% style="width:117px" %)(((
232 [[image:image-20240905140414-9.png||data-xwiki-image-style-alignment="center" height="114" width="100"]]
233 )))|(% style="width:314px" %)(((
234 Low Temperature Version:
235
236 * LTC2-NB/NS with 1 x Low Temperature PT100 probe.
237 * Installation: Insert
238 * Cable Length : 2m
239 * PT100 Class : Class A
240 * Probe Dimension: φ5*30mm
241 * Measure Range: -196 ~~ 150 °C
242 * Suitable Environment: Low temperature measurement, such as COVID vaccine transport
243 )))
244 |(% style="width:78px" %)DR-HT|(% style="width:117px" %)(((
245 (% contenteditable="false" tabindex="-1" %)
246 (((
247 (% data-widget="image" style="text-align:center;" %)
248 [[image:image-20240905140957-12.png||height="118" width="100"]](% title="Click and drag to resize" %)​
249 )))
250 )))|(% style="width:314px" %)(((
251 High Temperature Version:
252
253 * LTC2-NB/NS with 1 x high temperature PT100 probe.
254 * Installation: Insert
255 * Cable Length : 3m
256 * PT100 Class : Class A
257 * Probe Dimension: φ4.5*30mm
258 * Measure Range: -70 ~~ 450 °C
259 * Suitable Environment: High Temperature
260 )))
261 |(% style="width:78px" %)DR-FSA|(% style="width:117px" %)(((
262 [[image:image-20240905140643-10.png||data-xwiki-image-style-alignment="center" height="120" width="100"]]
263 )))|(% style="width:314px" %)(((
264 Food Safety Version:
265
266 * LTC2-NB/NS with 1 x Food Safety PT100 probe. Installation: Insert
267 * Cable Length : 2m
268 * PT100 Class : Class A
269 * Probe Dimension: φ4*150mm
270 * Measure Range: -40 ~~ 260 °C
271 * Suitable Environment: Food temperature measurement
272 )))
273 |(% style="width:78px" %)(((
274 DR-FT
275 )))|(% style="width:117px" %)(((
276 [[image:image-20240905140832-11.png||data-xwiki-image-style-alignment="center" height="115" width="100"]]
277 )))|(% style="width:314px" %)(((
278 Flat Type Version:
279
280 * LTC2-NB/NS with 1 x Flat Type PT100 probe.
281 * Installation: Attached
282 * Cable Length : 2m
283 * PT100 Class : Class A
284 * Probe Dimension: 3.6*7.5*20mm
285 * Measure Range: -60 ~~ 200 °C
286 * Suitable Environment: Attached to the measure point.
287 )))
288
289 = 2.  Use LTC2-NB/NS to communicate with IoT Server =
290
291 == 2.1  Send data to IoT server via NB-IoT network ==
292
293 (((
294 (((
295
296 )))
297
298 The LTC2-NB/NS is equipped with a NB-IoT module, the pre-loaded firmware in LTC2-NB/NS 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 LTC2-NB/NS.
299
300 Below shows the network structure:
301 )))
302
303 [[image:image-20241224134932-2.png]]
304
305 There are two version: (% style="color:blue" %)**-GE**(%%) and (% style="color:blue" %)**-1T**(%%) version of LTC2-NB/NS.
306
307 (% 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 LTC2-NB/NS send data to IoT server.
308
309 * 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]].
310
311 * 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]]. 
312
313 Below shows result of different server as a glance.
314
315 (% border="1" cellspacing="3" style="width:515px" %)
316 |(% 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**
317 |(% style="width:127px" %)[[Node-Red>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H3.5A0Node-RedA028viaA0MQTT29]]|(% style="width:385px" %)[[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/S31-NBS31B-NB_BN-IoT_Outdoor_Temperature_Humidity_Sensor_User_Manual/WebHome/image-20230819113244-8.png?width=367&height=183&rev=1.1||alt="image-20230819113244-8.png"]](((
318
319 )))|(% style="width:170px" %)
320 |(% style="width:127px" %)[[DataCake>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H3.4Datacake]]|(% style="width:385px" %)[[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/S31-NBS31B-NB_BN-IoT_Outdoor_Temperature_Humidity_Sensor_User_Manual/WebHome/image-20230819113244-9.png?width=367&height=119&rev=1.1||alt="image-20230819113244-9.png"]](((
321
322 )))|(% style="width:170px" %)
323 |(% 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" %)
324 |(% 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" %)
325 |(% 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" %)
326 |(% style="width:127px" %)[[ThingSpeak>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H3.3A0ThingSpeakA028viaA0MQTT29]]|(% style="width:385px" %)[[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/S31-NBS31B-NB_BN-IoT_Outdoor_Temperature_Humidity_Sensor_User_Manual/WebHome/image-20230819113244-10.png?width=367&height=104&rev=1.1||alt="image-20230819113244-10.png"]](((
327
328 )))|(% style="width:170px" %)
329 |(% style="width:127px" %)[[ThingsBoard>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H3.6A0ThingsBoard.CloudA028viaA0MQTT29]]|(% style="width:385px" %)[[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/S31-NBS31B-NB_BN-IoT_Outdoor_Temperature_Humidity_Sensor_User_Manual/WebHome/image-20230819113244-11.png?width=367&height=141&rev=1.1||alt="image-20230819113244-11.png"]](((
330
331 )))|(% style="width:170px" %)
332
333 (% 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 LTC2-NB/NS 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/]].
334
335
336 == 2.2 ​Payload Types ==
337
338
339 To meet different server requirement, LTC2-NB/NS supports different payload type.
340
341 **Includes:**
342
343 * [[General JSON format payload>>||anchor="H2.2.1GeneralJsonFormat28Type3D529"]]. (Type=5)
344
345 * [[HEX format Payload>>||anchor="H2.2.2HEXformatPayload28Type3D029"]]. (Type=0)
346
347 * [[ThingSpeak Format>>||anchor="H2.2.4ThingSpeakPayload28Type3D129"]]. (Type=1)
348
349 * [[ThingsBoard Format>>||anchor="H2.2.3ThingsBoardPayload28Type3D329"]]. (Type=3)
350
351 User can specify the payload type when choose the connection protocol. Example:
352
353
354 (% style="color:#037691" %)**AT+PRO=1,0**  (%%) ~/~/ Use COAP Connection & hex Payload
355
356 (% style="color:#037691" %)**AT+PRO=1,5**   (%%) ~/~/ Use COAP Connection & Json Payload
357
358 (% style="color:#037691" %)**AT+PRO=2,0**  (%%) ~/~/ Use UDP Connection & hex Payload
359
360 (% style="color:#037691" %)**AT+PRO=2,5**   (%%) ~/~/ Use UDP Connection & Json Payload
361
362 (% style="color:#037691" %)**AT+PRO=3,0**  (%%) ~/~/ Use MQTT Connection & hex Payload
363
364 (% style="color:#037691" %)**AT+PRO=3,5 ** (%%) ~/~/ Use MQTT Connection & Json Payload
365
366 (% style="color:#037691" %)**AT+PRO=4,0**  (%%) ~/~/ Use TCP Connection & hex Payload
367
368 (% style="color:#037691" %)**AT+PRO=4,5 ** (%%) ~/~/ Use TCP Connection & Json Payload
369
370
371 === 2.2.1 General Json Format(Type~=5) ===
372
373
374 This is the General Json Format. As below:
375
376 (% style="color:#4472c4" %)**{"IMEI":"863663062765285","IMSI":"460086859301435","Model":"LTC2-NB","temp_alarm":"NN","channel1_temp":22.7,"channel2_temp":22.7,"battery":3.522,"signal":23,"time":"2024/12/31 05:33:12","1":[22.7,22.7,"2024/12/31 05:22:00"],"2":[22.7,22.7,"2024/12/31 05:07:00"],"3":[22.7,22.9,"2024/12/31 04:52:00"],"4":[22.9,22.9,"2024/12/31 04:37:00"],"5":[22.9,23.1,"2024/12/31 04:22:00"],"6":[23.1,23.4,"2024/12/31 04:07:00"],"7":[23.1,23.6,"2024/12/31 03:52:00"],"8":[23.0,23.2,"2024/12/31 03:37:00"]}**
377
378 Example:
379
380 [[image:image-20241231134128-1.png]]
381
382 (% style="color:red" %)**Notice, from above payload:**
383
384 * Temp_alarm, Channel1_temp, Channel2_temp, Battery, Signal & time are the value at uplink time.
385
386 * 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): TChannel1_temp, Channel2_temp, Sampling time.
387
388 (% style="color:blue" %)**Temp_alarm:**
389
390 This data field shows whether the packet was generated by a temperature alarm.
391
392 "**L**" stands for low temperature alarm, "**H**" stands for high temperature alarm.
393
394 **Example:**
395
396 * **NN:** No temperature alarm.
397 * **NH:** Channel 1 does not alarm, channel 2 high temperature alarm.
398 * **NL:** Channel 1 does not alarm, channel 2 low temperature alarm.
399 * **HH:** Both channel 1 and channel 2 have high temperature alarms.
400 * **LL: **Both channel 1 and channel 2 have low temperature alarms
401
402 === 2.2.2 HEX format Payload(Type~=0) ===
403
404
405 This is the HEX Format. As below:
406
407 (% style="color:#4472c4" %)**f863663062765285f4600868593014353d640dce1500000000e300e56773846100e300e3677382fc00e300e367737f7800e300e367737bf400e300e56773787000e500e5677374ec00e500e76773716800e700ea67736de400e700ec67736a60**
408
409 [[image:image-20250321105038-1.png]]
410
411 [[image:image-20241231134435-3.png]]
412
413 (% style="color:blue" %)**Device ID(f+IMEI): **(%%)f863663062765285 =863663062765285
414
415
416 (% style="color:blue" %)**SIM Card ID(f+IMSI): **(%%)f460086859301435 =460086859301435
417
418
419 (% style="color:blue" %)**Version:**
420
421 These bytes include the hardware and software version.
422
423 (% style="color:#037691" %)**Higher byte:**(%%) Specify Sensor Model: 0x3d for LTC2-NB/NS
424
425 (% style="color:#037691" %)**Lower byte:**(%%) Specify the software version: 0x64=100, means firmware version 1.0.0
426
427
428 (% style="color:blue" %)**BAT (Battery Info):**
429
430 Ex1: 0x0cbc = 3260mV
431
432
433 (% style="color:blue" %)**Signal Strength:**
434
435 NB-IoT Network signal Strength.
436
437 **Ex1: 0x15 = 21**
438
439 **0**  -113dBm or less
440
441 **1**  -111dBm
442
443 **2...30** -109dBm... -53dBm
444
445 **31**   -51dBm or greater
446
447 **99**    Not known or not detectable
448
449
450 (% style="color:blue" %)**Interrupt:**
451
452 This data field shows if this packet is generated by interrupt or not.
453
454 **Example:**
455
456 If byte[0]&0x01=0x00 : Normal uplink packet.
457
458 If byte[0]&0x01=0x01 : Interrupt Uplink Packet.
459
460
461 (% style="color:blue" %)**Interrupt_level:**
462
463 This byte shows whether the interrupt is triggered by a high or low level.
464
465 **Ex1:** 0x00  Interrupt triggered by falling edge (low level)
466
467 **Ex2: **0x01  Interrupt triggered by rising edge (high level)
468
469
470 (% style="color:blue" %)**Temp_alarm:**
471
472 This data field shows whether the packet was generated by a temperature alarm.
473
474 **Example:**
475
476 Ex1: 0x00(H) = 0000(B)  No temperature alarm.
477
478 Ex2: 0x04(H) = 0100(B)  Channel 1 does not alarm, channel 2 alarms.
479
480 Ex3: 0x01(H) = 0001(B)  Channel 1 alarms, channel 2 does not alarm.
481
482 Ex4: 0x05(H) = 0101(B)  Channel 1 and channel 2 alarms.
483
484
485 (% style="color:blue" %)**channel1_temp**
486
487 If payload is: 0105H:  (0105 & 8000 == 0), temp = 0105H /10 = 26.1 degree
488
489 If payload is: FF3FH :  (FF3F & 8000 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees.
490
491 (FF3F & 8000：Judge whether the highest bit is 1, when the highest bit is 1, it is negative)
492
493 If the value is -327.6, it means the channel1 PT100 probe is not connected.
494
495 If the value is -983, it means the PT100 converter is not connected.
496
497
498 (% style="color:blue" %)**channel2_temp**
499
500 If payload is: 0105H:  (0105 & 8000 == 0), temp = 0105H /10 = 26.1 degree
501
502 If payload is: FF3FH :  (FF3F & 8000 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees.
503
504 (FF3F & 8000：Judge whether the highest bit is 1, when the highest bit is 1, it is negative)
505
506 If the value is -327.6, it means the channel2 PT100 probe is not connected.
507
508 If the value is -983, it means the PT100 converter is not connected.
509
510 ​
511
512 (% style="color:blue" %)**TimeStamp:**(%%)**  **
513
514 Unit TimeStamp Example: 676b5f85(H) = 1735090053(D)
515
516 Put the decimal value into this link(https:~/~/www.epochconverter.com/) to get the time.
517
518
519 === 2.2.3 ThingsBoard Payload(Type~=3) ===
520
521
522 Type3 payload special design for ThingsBoard, it will also configure other default server to ThingsBoard.
523
524 (% style="color:#4472c4" %)**{
525 "topic": "LTC2_NB",
526 "payload": {
527 "IMEI": "863663062765285",
528 "IMSI": "460086859301435",
529 "Model": "LTC2-NB",
530 "temp_alarm": "NN",
531 "channel1_temp": 23.3,
532 "channel2_temp": 22.7,
533 "battery": 3.577,
534 "signal": 21,
535 "time": "2024/12/26 03:54:18",
536 "1": [23.1, 22.5, "2024/12/26 03:31:19"],
537 "2": [23.1, 22.4, "2024/12/26 03:16:19"],
538 "3": [22.9, 22.2, "2024/12/26 03:01:19"],
539 "4": [22.7, 22.1, "2024/12/26 02:46:19"],
540 "5": [23.0, 22.2, "2024/12/26 02:31:19"],
541 "6": [22.2, 22.2, "2024/12/26 02:16:19"],
542 "7": [22.1, 22.1, "2024/12/26 02:01:19"],
543 "8": [21.0, 20.1, "2024/12/25 09:29:50"]
544 }
545 }**
546
547 [[image:image-20241231134224-2.png||height="611" width="1180"]]
548
549
550 (((
551 === 2.2.4 ThingSpeak Payload(Type~=1) ===
552
553
554 This payload meets ThingSpeak platform requirement. It includes only four fields. Form 1~~4 are:
555
556 Temperature, Humidity, Battery & Signal. This payload type only valid for ThingsSpeak Platform
557
558 As below:
559
560 (% style="color:#4472c4" %)**field1=channel1_temp&field2=channel2_temp&field3=BatV&field4=Singal**
561
562 [[image:image-20241225103212-5.png]]
563 )))
564
565 (% aria-label="Data URI image image widget" contenteditable="false" role="region" style="background-image:url(http://wiki1.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" tabindex="-1" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]][[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)​
566
567 = 3. Configure LTC2-NB/NS =
568
569 == 3.1 Configure Methods ==
570
571
572 LTC2-NB/NS supports below configure method:
573
574 * AT Command via Bluetooth Connection (**Recommended**): [[BLE Configure Instruction>>url:http://wiki.dragino.com/xwiki/bin/view/Main/BLE%20Bluetooth%20Remote%20Configure/]].
575
576 * AT Command via UART Connection : See [[UART Connection>>url:http://wiki.dragino.com/xwiki/bin/view/Main/UART%20Access%20for%20LoRa%20ST%20v4%20base%20model/#H2.3UARTConnectionforSN50v3basemotherboard]].
577
578 == ​​​3.2  Serial Access Password ==
579
580
581 After the Bluetooth or UART connection is successful, use the Serial Access Password to enter the AT command window.
582
583 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.
584
585 (((
586 (((
587 [[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"]]
588 )))
589
590 (((
591 (% title="Click and drag to resize" %)​(%%)If you need to change the password, use **AT+PWORD=**xxxxxx (6 characters), -CB nodes only support lowercase letters.
592
593 [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/S31-CBS31B-CB--NB-IoTLTE-M_Temperature%26Humidity_Sensor_User_Manual/WebHome/image-20240826183254-2.png?rev=1.1||alt="image-20240826183254-2.png"]]
594
595 (% 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.**
596
597 [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/S31-CBS31B-CB--NB-IoTLTE-M_Temperature%26Humidity_Sensor_User_Manual/WebHome/image-20240826183302-3.png?rev=1.1||alt="image-20240826183302-3.png"]]
598
599
600 == 3.3 AT Commands Set ==
601
602
603 AT+<CMD>? : Help on <CMD>
604
605 AT+<CMD> : Run <CMD>
606
607 AT+<CMD>=<value> : Set the value
608
609 AT+<CMD>=? : Get the value
610
611
612 (% style="color:blue" %)**General Commands**
613
614 AT+MODEL : Get module information
615
616 ATZ : Trig a reset of the MCU
617
618 AT+DEUI : Get or set the Device ID
619
620 AT+SLEEP : Get or set the sleep status
621
622 AT+DEBUG : Set more info output
623
624 AT+SERVADDR: Get or Set the Server address
625
626 AT+TDC : Get or set the application data transmission interval in s
627
628 AT+APN : Get or set the APN
629
630 AT+PRO : Get or Set usage agreement (1:COAP,2:UDP,3:MQTT,4:TCP)
631
632 AT+RXDL : Get or Set the receiving time
633
634 AT+GETSENSORVALUE : Returns the current sensor measurement
635
636 AT+DNSCFG : Get or Set DNS Server
637
638 AT+CSQTIME : Get or Set the time to join the network
639
640 AT+BKDNS : Get or Set dynamic domain name resolution IP
641
642 AT+TLSMOD : Get or Set the TLS mode
643
644 AT+INTMOD : Get or Set the trigger interrupt mode (0:input,1:falling or rising,2:falling,3:rising)
645
646 AT+WMOD : Get or Set the Alarm Mode
647
648 AT+CITEMP : Get or Set the time interval to check sensor value for Alarm
649
650 AT+ARTEMP : Get or Set the Alarm Threshold
651
652 AT+CLOCKLOG: Enable or Disable Clock Logging
653
654 AT+TIMESTAMP : Get or Set UNIX timestamp in second
655
656 AT+DOWNTE: Get or set the conversion between the standard version and 1T version downlinks
657
658
659 (% style="color:blue" %)**MQTT Management  **
660
661 AT+MQOS : Set the QoS level of MQTT
662
663 AT+CLIENT : Get or Set the MQTT clientID
664
665 AT+UNAME : Get or Set the MQTT Username
666
667 AT+PWD : Get or Set the MQTT password
668
669 AT+PUBTOPIC: Get or set MQTT publishing topic
670
671 AT+SUBTOPIC: Get or set MQTT subscription topic
672
673
674 (% style="color:blue" %)**COAP Management**
675
676 AT+URI1: Get or set CoAP option 1
677
678 AT+URI2: Get or set CoAP option 2
679
680 AT+URI3: Get or set CoAP option 3
681
682 AT+URI4: Get or set CoAP option 4
683
684
685 (% style="color:blue" %)**Information**
686
687 AT+CFG : Print all settings
688
689 AT+FDR1 : Reset parameters to factory default values except for passwords
690
691 AT+FDR : Reset Parameters to Factory Default
692
693 AT+PWORD : Get or set the System password
694
695 AT+CDP : Read or Clear cached data
696
697 AT+LDATA : Get the last upload data
698
699 AT+PDTA: Print the sector data from start page to stop page
700
701 AT+PLDTA: Print the last few sets of data
702
703 AT+CLRDTA: Clear the storage, record position back to 1st
704
705 AT+GETLOG : Print serial port logs
706 )))
707 )))
708
709
710 == 3.4 Test Uplink and Change Update Interval ==
711
712
713 By default, Sensor will send uplinks **every 2 hours.**
714
715 User can use below commands to change the uplink interval.
716
717 (% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+TDC** (%%)
718
719 Example: AT+TDC=7200  ~/~/ Set Update Interval to 7200 seconds
720
721 (% style="color:blue" %)**Downlink Commands: **(% style="color:#037691" %)**0x01**
722
723 Format: Command Code (0x01) followed by 3 bytes.
724
725 Example:  12 hours= 43200 seconds  43200(D)=0xA8C0(H)
726
727 Downlink Payload: **01 00 A8 C0**  ~/~/ AT+TDC=43200, Set Update Interval to 12 hours.
728
729 (% style="color:red" %)**Note: User can also push the button for more than 1 second to activate an uplink.**
730
731
732 == 3.5 Set the receiving time ==
733
734
735 Feature: Extend the receiving time
736
737 (% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+RXDL**
738
739 Example: AT+RXDL=1000  ~/~/ Set the receiving time delay to 1000ms
740
741 (% style="color:blue" %)**Downlink Commands: **(% style="color:#037691" %)**0x03**
742
743 Format: Command Code (0x03) followed by 3 bytes.
744
745 Example:  Downlink Payload: **03 00 03 E8     **~/~/ AT+RXDL=1000
746
747
748 == 3.6 Reset ==
749
750
751 Feature: Trig a reset of the MCU.
752
753 (% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**ATZ**
754
755 (% style="color:blue" %)**Downlink Commands: **(% style="color:#037691" %)**0x04FF**
756
757
758 == 3.7 Trigger an uplink by external interrupt ==
759
760
761 LTC2-NB/NS has an external trigger interrupt function. Users can use the PB15 pin to trigger the upload of data packets.
762
763 (% style="color:blue" %)**AT command:**
764
765 * (% style="color:#037691" %)**AT+INTMOD **(%%) ~/~/ Set the trigger interrupt mode
766
767 * (% style="color:#037691" %)**AT+INTMOD=0 **(%%) ~/~/ Disable Interrupt
768
769 * (% style="color:#037691" %)**AT+INTMOD=1 **(%%) ~/~/ Trigger by rising and falling edge
770
771 * (% style="color:#037691" %)**AT+INTMOD=2 **(%%) ~/~/ Trigger by falling edge
772
773 * (% style="color:#037691" %)**AT+INTMOD=3  **(%%) ~/~/ Trigger by rising edge
774
775 (% style="color:blue" %)**Downlink Commands: **(% style="color:#037691" %)**0x06**
776
777 Format: Command Code (0x06) followed by 3 bytes.
778
779 Example1:  Downlink Payload: **06 00 00 01    **~/~/ AT+INTMOD=1
780
781 Example2:  Downlink Payload: **06 00 00 03    **~/~/ AT+INTMOD=3
782
783
784 == 3.8 Set the QoS level ==
785
786
787 This command is used to set the QoS level of **MQTT**.
788
789 (% style="color:blue" %)**AT command:**
790
791 * (% style="color:#037691" %)**AT+MQOS=xx**(%%)**   **~/~/ 0~~2
792
793 (% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x07(%%)**
794
795 Format: Command Code (0x07) followed by 1 byte.
796
797 **Ex1:** Downlink payload: **0x0700**  ~/~/ AT+MQOS=0
798
799 **Ex2:** Downlink payload: **0x0701**  ~/~/ AT+MQOS=1
800
801
802 == 3.9 Clock logging ==
803
804
805 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.
806
807 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.
808
809 (% style="color:blue" %)**AT command:**(%%)** (% style="color:#037691" %)AT+CLOCKLOG=a,b,c,d(%%)**
810
811 (% style="color:#037691" %)**a: **(%%)**0:** Disable Clock logging.  ** 1: **Enable Clock Logging
812
813 (% 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.
814
815 (% style="color:#037691" %)**c: **(%%)Specify the sampling interval: range **(0 ~~ 255 minutes)**
816
817 (% style="color:#037691" %)**d:**(%%)** **How many entries should be uplink on every TDC **(max 32)**
818
819 (% style="color:red" %)**Note: To disable clock recording, set the following parameters: AT+CLOCKLOG=1,65535,0,0**
820
821 [[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"]]
822
823 **Example:**
824
825 **AT+CLOCKLOG=1,65535,1,5**
826
827 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).
828
829 (% class="wikigeneratedid" %)
830 [[image:image-20241226135420-7.png||height="541" width="740"]]
831
832 (% class="wikigeneratedid" %)
833 (% 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.**
834
835 (% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x03(%%)**
836
837 Format: Command Code (0x03) followed by 5 bytes.
838
839 * **Example 1**: Downlink Payload:** 03 01 FFFF 0F 08**  ~/~/ Set SHT record time: AT+CLOCKLOG=1,65535,15,8
840 * **Example 2**: Downlink Payload:** 03 01 04B0 0F 08**  ~/~/ Set SHT record time: AT+CLOCKLOG=1,1200,15,8
841
842 (% style="color:red" %)**Note: When entering the downlink payload, there must be no Spaces between bytes.**
843
844
845 == 3.10 Set the TLS mode ==
846
847
848 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.
849
850 (% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+TLSMOD**
851
852 **Example 1: ** AT+TLSMOD=0,0  ~/~/ Disable TLS Mode.
853
854 **Example 2:**  AT+TLSMOD=1,0  ~/~/ No authentication
855
856 AT+TLSMOD=1,1  ~/~/ Perform server authentication
857
858 AT+TLSMOD=1,2  ~/~/ Perform server and client authentication if requested by the remote server
859
860 (% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x09(%%)**
861
862 Format: Command Code (0x09) followed by 2 bytes.
863
864 Example1:  Downlink Payload: **09 00 00    **~/~/ AT+TLSMOD=0,0
865
866 Example2:  Downlink Payload: **09 01 02    **~/~/ AT+TLSMOD=1,2
867
868
869 == 3.11 Set the search network time ==
870
871
872 Feature: Get or Set the time to join the network(unit: minutes).
873
874 (% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+CSQTIME**
875
876 Example: AT+CSQTIME=10  ~/~/ Set the search time to 10 minutes.
877
878 (% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x13(%%)**
879
880 Format: Command Code (0x13) followed by 1 byte.
881
882 Example:  Downlink Payload: **13 0A   **~/~/ AT+CSQTIME=10
883
884
885 == 3.12  Set alarm mode ==
886
887
888 Feature: Enable/Disable Alarm Mode.
889
890 (% style="color:#037691" %)**AT Command: AT+WMOD**
891
892 * AT+WMOD=0  ~/~/ Disable the alarm mode, default.
893 * AT+WMOD=1  ~/~/ Enable the alarm mode.
894
895 (% style="color:#037691" %)**Downlink Command: 0xA5**
896
897 * Downlink payload: **0xA500**  ~/~/ Same as AT+WMOD=0
898 * Downlink payload: **0xA501**   ~/~/  Same as AT+WMOD=1
899
900 == 3.13 Alarm check time ==
901
902
903 Feature: The time interval to check sensor value for Alarm. ( Default: AT+CITEMP=5; Unit: minute )
904
905 (% style="color:#037691" %)**AT Command: AT+CITEMP**
906
907 Example:
908
909 * AT+CITEMP=10  ~/~/ Set collection interval in 10 min, only in alarm mode.
910
911 (% style="color:#037691" %)**Downlink Command: 0xA6**
912
913 Format: Command Code (0xA6) followed by 2 bytes.
914
915 Example:
916
917 * Downlink payload: **0xA6000A**  ~/~/ Same as AT+CITEMP=10
918
919 == 3.14 Set Alarm Threshold ==
920
921
922 Feature: Set Alarm Threshold. (Unit: ℃)
923
924 (% style="color:#037691" %)**AT Command: AT+ARTEMP**
925
926 The first parameter sets the low limit of channel 1, and the second parameter sets the high limit of channel 1.
927
928 The third parameter sets the low limit for channel 2, and the fourth parameter sets the high limit for channel 2.
929
930 Example:
931
932 * AT+ARTEMP=-200,800,-200,800  ~/~/ Channel 1 & Channel 2 operating temp: -200℃~~800℃，alarm when out of range.
933 * AT+ARTEMP=10,100,10,101  ~/~/ Channel 1 operating temp: 10℃~~100℃; Channel 2 operating temp: 10℃~~101℃, alarm when out of range.
934
935 (% style="color:#037691" %)**Downlink Command: 0xA7**
936
937 Format: Command Code (0xA7) followed by 8 bytes.
938
939 Each two bytes after the function code 0xA7 is a parameter, corresponding to the four parameters of AT+ARTEMP in sequence.
940
941 Example:
942
943 * Downlink payload: **0xA7FF380320FF380320**  ~/~/ Same as AT+ARTEMP=-200,800,-200,800
944 * Downlink payload: **0xA7000A0064000A0065**  ~/~/ Same as AT+ARTEMP=10,100,10,101  
945
946 (% style="color:red" %)**Note: For negative temperature -200℃: 65536-200= 65336(D) = 0XFF38(H)**
947
948
949 == 3.15 Factory data reset ==
950
951
952 Two different restore factory Settings configurations.
953
954 (% style="color:blue" %)**AT command:**
955
956 * (% style="color:#037691; font-weight:bold" %)**AT+FDR**(%%)**       **~/~/ Reset Parameters to Factory Default.
957 * (% style="color:#037691; font-weight:bold" %)**AT+FDR1**(%%)**     **~/~/ Reset parameters to factory default values **except for passwords**.
958
959 == 3.16 Set CoAP option ==
960
961
962 This command sets the connection parameters of the COAP.
963
964 (% style="color:blue" %)**AT command:**
965
966 * AT+URI1       ~/~/ CoAP option name, CoAP option length, "CoAP option value"
967 * AT+URI2      ~/~/ CoAP option name, CoAP option length,  "CoAP option value"
968 * AT+URI3     ~/~/ CoAP option name, CoAP option length,  "CoAP option value"
969 * AT+URI4     ~/~/ CoAP option name, CoAP option length,  "CoAP option value"
970
971 **Example:**
972
973 * AT+URI1=11,38,"i/faaa241f-af4a-b780-4468-c671bb574858"
974
975 == 3.17 Example Query saved historical records ==
976
977
978 * (% style="color:blue" %)**AT command:**(%%)** (% style="color:#037691" %)AT+CDP(%%)**
979
980 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.
981
982 (% class="wikigeneratedid" %)
983 [[image:image-20241226115759-4.png||height="551" width="718"]]
984
985
986 == 3.18 Uplink log query ==
987
988
989 * (% style="color:blue" %)**AT command:**(%%)** (% style="color:#037691" %)AT+GETLOG(%%)**
990
991 This command can be used to query upstream logs of data packets.
992
993 [[image:image-20241226115849-5.png||height="528" width="697"]]
994
995
996 == 3.19 Print last few data entries ==
997
998
999 Feature: Print the last few data entries
1000
1001 (% style="color:blue" %)**AT command: **(% style="color:#037691" %)**AT+PLDTA**
1002
1003 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %)
1004 |=(% style="width: 168px; background-color: rgb(79, 129, 189); color: white;" %)**Command Example**|=(% style="width: 342px; background-color: rgb(79, 129, 189); color: white;" %)**4 bytes**
1005 |(% style="width:148px" %)AT+PLDTA=5
1006 Print last 5 entries|(% style="width:169px" %)(((
1007 Stop Tx events when read sensor data
1008
1009 1 24/12/26 02:31:19 channel1_temp=23.0 channel2_temp=22.2
1010
1011 2 24/12/26 02:46:19 channel1_temp=22.7 channel2_temp=22.1
1012
1013 3 24/12/26 03:01:19 channel1_temp=22.9 channel2_temp=22.2
1014
1015 4 24/12/26 03:16:19 channel1_temp=23.1 channel2_temp=22.4
1016
1017 5 24/12/26 03:31:19 channel1_temp=23.1 channel2_temp=22.5
1018
1019
1020 OK
1021 )))
1022
1023 (% style="color:blue" %)**Downlink Command: **
1024
1025 No downlink commands for feature
1026
1027
1028 == 3.20 Print data entries base on page ==
1029
1030
1031 Feature: Print the sector data from start page to stop page.
1032
1033 (% style="color:blue" %)**AT command: **(% style="color:#037691" %)**AT+PDTA**
1034
1035 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %)
1036 |=(% style="width: 168px; background-color: rgb(79, 129, 189); color: white;" %)**Command Example**|=(% style="width: 342px; background-color: rgb(79, 129, 189); color: white;" %)**4 bytes**
1037 |(% style="width:148px" %)AT+PDTA=1,1
1038 Print page 1 to 1|(% style="width:169px" %)(((
1039 Stop Tx events when read sensor data
1040
1041 8028A00 24/12/24 10:00:27 channel1_temp=22.2 channel2_temp=23.0
1042
1043 8028A08 24/12/24 10:02:27 channel1_temp=22.2 channel2_temp=22.7
1044
1045 8028A10 24/12/24 10:04:27 channel1_temp=22.2 channel2_temp=22.7
1046
1047 8028A18 24/12/24 10:06:27 channel1_temp=22.2 channel2_temp=22.6
1048
1049 8028A20 24/12/24 10:08:27 channel1_temp=22.2 channel2_temp=22.4
1050
1051 8028A28 24/12/24 10:10:27 channel1_temp=22.2 channel2_temp=22.4
1052
1053 8028A30 24/12/24 10:12:27 channel1_temp=22.2 channel2_temp=22.2
1054
1055 8028A38 24/12/24 10:14:31 channel1_temp=22.1 channel2_temp=22.2
1056
1057 8028A40 24/12/24 10:16:27 channel1_temp=22.1 channel2_temp=22.1
1058
1059 8028A48 24/12/24 10:18:27 channel1_temp=22.1 channel2_temp=22.1
1060
1061 8028A50 24/12/24 10:20:27 channel1_temp=22.1 channel2_temp=22.2
1062
1063 8028A58 24/12/24 10:22:27 channel1_temp=22.0 channel2_temp=22.1
1064
1065 8028A60 24/12/24 10:24:27 channel1_temp=22.0 channel2_temp=22.1
1066
1067 8028A68 24/12/24 10:26:27 channel1_temp=22.0 channel2_temp=22.1
1068
1069 8028A70 24/12/24 10:28:27 channel1_temp=21.9 channel2_temp=22.0
1070
1071 8028A78 24/12/24 10:30:27 channel1_temp=22.0 channel2_temp=22.0
1072
1073
1074 OK
1075 )))
1076
1077 (% style="color:blue" %)**Downlink Command: **
1078
1079 No downlink commands for feature
1080
1081
1082 == 3.21 Clear Flash Record ==
1083
1084
1085 Feature: Clear flash storage for data log feature.
1086
1087 (% style="color:blue" %)**AT command: **(% style="color:#037691" %)**AT+CLRDTA**
1088
1089 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %)
1090 |=(% style="width: 160px; background-color: rgb(79, 129, 189); color: white;" %)**Command Example**|=(% style="width: 130px; background-color: rgb(79, 129, 189); color: white;" %)**Function**|=(% style="width: 220px; background-color: rgb(79, 129, 189); color: white;" %)**Response**
1091 |(% style="width:160px" %)AT+CLRDTA |(% style="width:130px" %)(((
1092 Clear date record
1093 )))|(% style="width:213px" %)(((
1094 Please wait for the erase to complete
1095
1096 Clear all stored sensor data...
1097
1098
1099 OK
1100 )))
1101
1102 (% style="color:blue" %)**Downlink Command:  **(% style="color:#037691" %)**0x32**
1103
1104 * Example: 0x32 00   ~/~/  Same as AT+CLRDTA
1105
1106 == 3.22 Set the downlink debugging mode ==
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: 134px; background-color: rgb(79, 129, 189); color: white;" %)**Command Example**|=(% style="width: 143px; background-color: rgb(79, 129, 189); color: white;" %)**Function/Parameters**|=(% style="width: 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
1118 OK
1119 )))
1120 |(% colspan="1" rowspan="2" style="width:134px" %)(((
1121
1122
1123
1124
1125 AT+DOWNTE=a,b
1126 )))|(% style="width:143px" %)**a**: Set the conversion between the downlink of the standard version and 1T version|(% style="width:229px" %)(((
1127 **0**: Set the downlink of the standard version.
1128 **1**: Set the downlink of the 1T version(ThingsEye platform)
1129 )))
1130 |(% style="width:143px" %)**b**: Enable/Disable downlink debugging|(% style="width:229px" %)(((
1131 **0**: Disable downlink debugging mode.
1132 **1**: Enable downlink debugging mode, users can see the original downlink reception.
1133 )))
1134
1135 **Example:**
1136
1137 * AT+DOWNTE=0,1  ~/~/ Set to standard version downlink, and enable downlink debugging.
1138 * AT+DOWNTE=1,1  ~/~/ Set to 1T version downlink, and enable downlink debugging.
1139
1140 (% style="color:blue" %)**Downlink Command:  **
1141
1142 No downlink commands for feature
1143
1144
1145 == 3.23 Domain name resolution settings ==
1146
1147
1148 Feature: Set dynamic domain name resolution IP.
1149
1150 (% style="color:blue" %)**AT command: AT+BKDNS**
1151
1152 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %)
1153 |=(% style="width: 134px; background-color: rgb(79, 129, 189); color: white;" %)**Command Example**|=(% style="width: 143px; background-color: rgb(79, 129, 189); color: white;" %)**Function/Parameters**|=(% style="width: 233px; background-color: rgb(79, 129, 189); color: white;" %)**Response/Explanation**
1154 |(% style="width:134px" %)(((
1155 AT+BKDNS=?
1156 )))|(% style="width:143px" %)Get current Settings|(% style="width:606px" %)(((
1157 0,0,NULL  (default)
1158 OK
1159 )))
1160 |(% colspan="1" rowspan="3" style="width:134px" %)(((
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172 AT+BKDNS=a,b,c
1173 )))|(% style="width:143px" %)(((
1174
1175
1176
1177
1178
1179 **a**: Enable/Disable dynamic domain name resolution.
1180 )))|(% style="width:606px" %)**1**: Disable dynamic domain name update. The ip address will be saved after the domain name is resolved, if the next domain name resolution fails, the last saved ip address will be used.
1181 **2**: Enable dynamic domain name update. The ip address will be saved after domain name resolution, if the next domain name resolution fails, the last saved ip address will be used, and the domain name resolution will be updated regularly according to the time set by the customer.
1182 |(% style="width:143px" %)**b**: Set the time to update the domain name resolution at regular intervals.|(% style="width:606px" %)(((
1183 Unit: hour
1184 )))
1185 |(% style="width:143px" %)(((
1186
1187
1188
1189 **c**: Set the IP address manually.
1190 )))|(% style="width:606px" %)(((
1191 The format is the same as AT+SERVADDR.
1192
1193 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.
1194 )))
1195
1196 **Example:**
1197
1198 * AT+BKDNS=1,0  ~/~/ Dynamic domain name resolution is disabled.
1199 * AT+BKDNS=2,1  ~/~/ The dynamic domain name resolution function is enabled and the automatic update time is set to 1 hour.
1200 * AT+BKDNS=2,4,3.69.98.183,1883  ~/~/ The dynamic domain name resolution function is enabled and the automatic update time is set to 4 hour, and manually set the ip address, if the domain name failed to resolve, it will directly use this ip to communicate. When the next domain name resolution is successful, it will be updated to the ip address of the successful resolution.
1201
1202 (% style="color:blue" %)**Downlink Command:  **
1203
1204 No downlink commands for feature
1205
1206
1207 = 4. Battery & Power Consumption =
1208
1209
1210 LTC2-NB use ER26500 + SPC1520 battery pack and LTC2-NS use 3000mAh Recharable Battery with Solar Panel. See below link for detail information about the battery info and how to replace.
1211
1212 [[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] .
1213
1214
1215 = 5. Firmware update =
1216
1217
1218 User can change device firmware to::
1219
1220 * Update with new features.
1221
1222 * Fix bugs.
1223
1224 Firmware and changelog can be downloaded from : **[[Firmware download link>>https://www.dropbox.com/scl/fo/ztlw35a9xbkomu71u31im/APYi-JAo4xE08lTQHnSa7hg/NB-IoT/LTC2-NB?rlkey=ojjcsw927eaow01dgooldq3nu&subfolder_nav_tracking=1&dl=0]]**
1225
1226 Methods to Update Firmware:
1227
1228 * (Recommended way) OTA firmware update via BLE: [[**Instruction**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/BLE_Firmware_Update_NB_Sensors_BC660K-GL/]].
1229
1230 * Update through UART TTL interface : **[[Instruction>>url:http://wiki.dragino.com/xwiki/bin/view/Main/UART_Access_for_NB_ST_BC660K-GL/#H4.2UpdateFirmware28Assumethedevicealreadyhaveabootloader29]]**.
1231
1232 (((
1233
1234 )))
1235
1236 = 6.  FAQ =
1237
1238 == 6.1 How can I access t BC660K-GL AT Commands? ==
1239
1240
1241 User can access to BC660K-GL directly and send AT Commands.
1242
1243 [[See BC660K-GL AT Command set>>url:https://www.dropbox.com/sh/5f6ssda5fum8rvs/AABT68l8ZzWOvZ5eg2qwOoFda?dl=0]]
1244
1245
1246 == 6.2 How do users connect custom PT100 sensors? ==
1247
1248 ~1. The user needs to cut off one end of the original probe and peel off the wire core.
1249
1250 [[image:image-20250510102413-2.png]]
1251
1252 2. Connect according to the corresponding positive and negative poles.
1253
1254 [[image:image-20250510102212-1.png||height="523" width="658"]]
1255
1256
1257 = 7.  Order Info =
1258
1259
1260 (% style="color:red" %)**Notice: This part number doesn't include the Temperature sensor. Users need to purchase separately.**
1261
1262 Part Number: (% style="color:blue" %)**LTC2-NB/NS-XX**
1263
1264 (% style="color:red" %)**XX:**
1265
1266 * (% style="color:#037691" %)**GE: **(%%)General version ( Exclude SIM card)
1267
1268 * (% style="color:#037691" %)**1T:**(%%) with 1NCE * 10 years 500MB SIM card and Pre-configure to ThingsEye server
1269
1270 (% style="color:blue" %)**Probe Options:**(%%)** (% style="color:red" %)DR-SI(%%)**, (% style="color:red" %)**DR-LT**(%%), (% style="color:red" %)**DR-HT**(%%), (% style="color:red" %)**DR-FSA**(%%), (% style="color:red" %)**DR-FT**
1271
1272
1273 = 8. ​ Packing Info =
1274
1275
1276 (% style="color:#037691" %)**Package Includes:**
1277
1278 * LTC2-NB/NS NB-IoT Temperature Transmitter x 1
1279
1280 (% style="color:#037691" %)**Dimension and weight:**
1281
1282 * Device Size: cm
1283 * Device Weight: g
1284 * Package Size / pcs : cm
1285 * Weight / pcs : g
1286
1287 = 9.  ​Support =
1288
1289
1290 * 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.
1291 * 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.com>>url:http://../../../../../../D:%5C%E5%B8%82%E5%9C%BA%E8%B5%84%E6%96%99%5C%E8%AF%B4%E6%98%8E%E4%B9%A6%5CLoRa%5CLT%E7%B3%BB%E5%88%97%5Csupport@dragino.com]].