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