Wiki source code of LTC2-LB -- LoRaWAN Temperature Transmitter User Manual
Last modified by Mengting Qiu on 2025/01/16 11:21
Show last authors
author | version | line-number | content |
---|---|---|---|
1 | (% style="text-align:center" %) | ||
2 | [[image:image-20240905135235-4.png||height="443" width="837"]] | ||
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-LB LoRaWAN Temperature Transmitter == | ||
28 | |||
29 | |||
30 | The Dragino LTC2-LB Industrial LoRaWAN 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 uplink to IoT server via LoRaWAN protocol. | ||
31 | |||
32 | LTC2-LB supports (% style="color:blue" %)**Datalog feature**(%%). User can retrieve the sensor value via LoRaWAN downlink command. | ||
33 | |||
34 | LTC2-LB has (% style="color:blue" %)**two internal 24-bit ADC interfaces**(%%). | ||
35 | |||
36 | LTC2-LB (% style="color:blue" %)**supports BLE configure**(%%) and (% style="color:blue" %)**wireless OTA update**(%%) which make user easy to use. | ||
37 | |||
38 | LTC2-LB is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%)**, **it is designed for long-term use up to several years. | ||
39 | |||
40 | Each LTC2-LB is pre-load with a set of unique keys for LoRaWAN registrations, register these keys to local LoRaWAN server and it will auto-connect after power on. | ||
41 | |||
42 | |||
43 | == 1.2 Features == | ||
44 | |||
45 | |||
46 | * LoRaWAN v1.0.3 Class A | ||
47 | * max: 2 x monitor temperature channels | ||
48 | * Support 3 -wire PT-100 | ||
49 | * Temperature alarm | ||
50 | * Datalog Feature | ||
51 | * Support Bluetooth v5.1 and LoRaWAN remote configure | ||
52 | * Support wireless OTA update firmware | ||
53 | * Uplink on periodically | ||
54 | * Downlink to change configure | ||
55 | * 8500mAh Li/SOCl2 Battery | ||
56 | |||
57 | (% style="display:none" %) | ||
58 | |||
59 | == 1.3 Specification == | ||
60 | |||
61 | |||
62 | **Common DC Characteristics:** | ||
63 | |||
64 | * Supply Voltage: Built-in Battery , 2.5v ~~ 3.6v | ||
65 | * Operating Temperature: -40 ~~ 85°C | ||
66 | |||
67 | **LoRa Spec:** | ||
68 | |||
69 | * Frequency Range, Band 1 (HF): 862 ~~ 1020 Mhz | ||
70 | * Max +22 dBm constant RF output vs. | ||
71 | * RX sensitivity: down to -139 dBm. | ||
72 | * Excellent blocking immunity | ||
73 | |||
74 | **Battery:** | ||
75 | |||
76 | * Li/SOCI2 un-chargeable battery | ||
77 | * Capacity: 8500mAh | ||
78 | * Self-Discharge: <1% / Year @ 25°C | ||
79 | * Max continuously current: 130mA | ||
80 | * Max boost current: 2A, 1 second | ||
81 | |||
82 | **Power Consumption** | ||
83 | |||
84 | * Sleep Mode: 5uA @ 3.3v | ||
85 | * LoRa Transmit Mode: 125mA @ 20dBm, 82mA @ 14dBm | ||
86 | |||
87 | == 1.4 Applications == | ||
88 | |||
89 | |||
90 | * Logistics and Supply Chain Management | ||
91 | * Food management | ||
92 | * Cold chains solution | ||
93 | * Industrial Monitoring and Control | ||
94 | |||
95 | == 1.5 Sleep mode and working mode == | ||
96 | |||
97 | |||
98 | (% style="color:blue" %)**Deep Sleep Mode: **(%%)Sensor doesn't have any LoRaWAN activate. This mode is used for storage and shipping to save battery life. | ||
99 | |||
100 | (% style="color:blue" %)**Working Mode:** (%%)In this mode, Sensor will work as LoRaWAN Sensor to Join LoRaWAN 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. | ||
101 | |||
102 | |||
103 | == 1.6 Button & LEDs == | ||
104 | |||
105 | |||
106 | [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/PS-LB-NA--LoRaWAN_Analog_Sensor_User_Manual/WebHome/1675071855856-879.png?rev=1.1||alt="1675071855856-879.png"]] | ||
107 | |||
108 | (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %) | ||
109 | |=(% 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** | ||
110 | |(% 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" %)((( | ||
111 | If sensor is already Joined to LoRaWAN network, sensor will send an uplink packet, (% style="color:blue" %)**blue led** (%%)will blink once. | ||
112 | Meanwhile, BLE module will be active and user can connect via BLE to configure device. | ||
113 | ))) | ||
114 | |(% 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" %)((( | ||
115 | (% 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 JOIN LoRaWAN network. | ||
116 | (% style="background-color:#f2f2f2; color:green" %)**Green led**(%%) will solidly turn on for 5 seconds after joined in network. | ||
117 | Once sensor is active, BLE module will be active and user can connect via BLE to configure device, no matter if device join or not join LoRaWAN network. | ||
118 | ))) | ||
119 | |(% 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" %)(% style="color:red" %)**Red led**(%%) will solid on for 5 seconds. Means LTC2-LB is in Deep Sleep Mode. | ||
120 | |||
121 | == 1.7 BLE connection == | ||
122 | |||
123 | |||
124 | LTC2-LB supports BLE remote configure. | ||
125 | |||
126 | 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: | ||
127 | |||
128 | * Press button to send an uplink | ||
129 | * Press button to active device. | ||
130 | * Device Power on or reset. | ||
131 | |||
132 | If there is no activity connection on BLE in 60 seconds, sensor will shut down BLE module to enter low power mode. | ||
133 | |||
134 | |||
135 | == 1.8 Pin Definitions == | ||
136 | |||
137 | |||
138 | [[image:image-20240924112455-2.png||height="330" width="585"]] | ||
139 | |||
140 | |||
141 | == 1.9 Mechanical == | ||
142 | |||
143 | |||
144 | [[image:image-20240924112107-1.png||height="505" width="829"]] | ||
145 | |||
146 | |||
147 | == 1.10 Probe Variant == | ||
148 | |||
149 | |||
150 | LTC2-LB provide default probe version. See below for the variant: | ||
151 | |||
152 | (% border="1" cellspacing="3" style="width:505px" %) | ||
153 | |=(% style="width: 78px;background-color:#4F81BD;color:white" %)((( | ||
154 | **Model** | ||
155 | )))|=(% style="width: 127px;background-color:#4F81BD;color:white" %)((( | ||
156 | **Photo** | ||
157 | )))|=(% style="width: 300px;background-color:#4F81BD;color:white" %)((( | ||
158 | **Description** | ||
159 | ))) | ||
160 | |(% style="width:78px" %)((( | ||
161 | DR-SI | ||
162 | )))|(% style="width:117px" %)((( | ||
163 | (% style="text-align:center" %) | ||
164 | [[image:image-20240905135914-8.png||height="107" width="100"]] | ||
165 | )))|(% style="width:314px" %)((( | ||
166 | Standard IP68 Probe Version: | ||
167 | |||
168 | * LTC2-LB with 1 x Standard IP68 PT100 probe. | ||
169 | * Installation: Insert | ||
170 | * Cable Length : 2m | ||
171 | * PT100 Class : Class A | ||
172 | * Probe Dimension: φ5*30mm | ||
173 | * Measure Range: -60 ~~ 200 °C | ||
174 | * Suitable Environment: General environment | ||
175 | ))) | ||
176 | |(% style="width:78px" %)((( | ||
177 | DR-LT | ||
178 | )))|(% style="width:117px" %)((( | ||
179 | (% style="text-align:center" %) | ||
180 | [[image:image-20240905140414-9.png||height="114" width="100"]] | ||
181 | )))|(% style="width:314px" %)((( | ||
182 | Low Temperature Version: | ||
183 | |||
184 | * LTC2-LB with 1 x Low Temperature PT100 probe. | ||
185 | * Installation: Insert | ||
186 | * Cable Length : 2m | ||
187 | * PT100 Class : Class A | ||
188 | * Probe Dimension: φ5*30mm | ||
189 | * Measure Range: -196 ~~ 150 °C | ||
190 | * Suitable Environment: Low temperature measurement, such as COVID vaccine transport | ||
191 | ))) | ||
192 | |(% style="width:78px" %)DR-HT|(% style="width:117px" %)((( | ||
193 | (% contenteditable="false" tabindex="-1" %) | ||
194 | ((( | ||
195 | (% data-widget="image" style="text-align:center" %) | ||
196 | [[image:image-20240905140957-12.png||height="118" width="100"]](% title="Click and drag to resize" %) | ||
197 | ))) | ||
198 | )))|(% style="width:314px" %)((( | ||
199 | High Temperature Version: | ||
200 | |||
201 | * LTC2-LB with 1 x high temperature PT100 probe. | ||
202 | * Installation: Insert | ||
203 | * Cable Length : 3m | ||
204 | * PT100 Class : Class A | ||
205 | * Probe Dimension: φ4.5*30mm | ||
206 | * Measure Range: -70 ~~ 450 °C | ||
207 | * Suitable Environment: High Temperature | ||
208 | ))) | ||
209 | |(% style="width:78px" %)DR-FSA|(% style="width:117px" %)((( | ||
210 | (% style="text-align:center" %) | ||
211 | [[image:image-20240905140643-10.png||height="120" width="100"]] | ||
212 | )))|(% style="width:314px" %)((( | ||
213 | Food Safety Version: | ||
214 | |||
215 | * LTC2-LB with 1 x Food Safety PT100 probe. Installation: Insert | ||
216 | * Cable Length : 2m | ||
217 | * PT100 Class : Class A | ||
218 | * Probe Dimension: φ4*150mm | ||
219 | * Measure Range: -40 ~~ 260 °C | ||
220 | * Suitable Environment: Food temperature measurement | ||
221 | ))) | ||
222 | |(% style="width:78px" %)((( | ||
223 | DR-FT | ||
224 | )))|(% style="width:117px" %)((( | ||
225 | (% style="text-align:center" %) | ||
226 | [[image:image-20240905140832-11.png||height="115" width="100"]] | ||
227 | )))|(% style="width:314px" %)((( | ||
228 | Flat Type Version: | ||
229 | |||
230 | * LTC2-LB with 1 x Flat Type PT100 probe. | ||
231 | * Installation: Attached | ||
232 | * Cable Length : 2m | ||
233 | * PT100 Class : Class A | ||
234 | * Probe Dimension: 3.6*7.5*20mm | ||
235 | * Measure Range: -60 ~~ 200 °C | ||
236 | * Suitable Environment: Attached to the measure point. | ||
237 | ))) | ||
238 | |||
239 | = 2. How to use LTC2-LB? = | ||
240 | |||
241 | == 2.1 How it works? == | ||
242 | |||
243 | ((( | ||
244 | ((( | ||
245 | |||
246 | ))) | ||
247 | |||
248 | The LTC2-LB is configured as (% style="color:#037691" %)**LoRaWAN OTAA Class A**(%%) mode by default. It has OTAA keys to join LoRaWAN network. To connect a local LoRaWAN network, you need to input the OTAA keys in the LoRaWAN IoT server and press the button to activate the LTC2-LB. It will automatically join the network via OTAA and start to send the sensor value. The default uplink interval is **20 minutes**. | ||
249 | |||
250 | ((( | ||
251 | On each uplink, LTC2-LB will check its two ADC Interfaces and get the temperature from the sensor and send out to server. | ||
252 | ))) | ||
253 | ))) | ||
254 | |||
255 | |||
256 | == 2.2 Quick guide to connect to LoRaWAN server (OTAA) == | ||
257 | |||
258 | |||
259 | Following is an example for how to join the [[TTN v3 LoRaWAN Network>>url:https://console.cloud.thethings.network/]]. Below is the network structure; we use the [[LPS8v2>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/228-lps8v2.html]] as a LoRaWAN gateway in this example. | ||
260 | |||
261 | The LPS8V2 is already set to connected to [[TTN network >>url:https://console.cloud.thethings.network/]], so what we need to now is configure the TTN server. | ||
262 | |||
263 | [[image:image-20240905150538-1.png||height="275" width="730"]] | ||
264 | |||
265 | |||
266 | (% style="color:blue" %)**Step 1:**(%%) Create a device in TTN with the OTAA keys from LTC2-LB. | ||
267 | |||
268 | Each LTC2-LB is shipped with a sticker with the default device EUI as below: | ||
269 | |||
270 | [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LTC2%20-%20LoRaWAN%20Temperature%20Transmitter%20User%20Manual/WebHome/image-20230426083905-2.png?rev=1.1||alt="image-20230426083905-2.png" height="287" width="618"]] | ||
271 | |||
272 | You can enter this key in the LoRaWAN Server portal. Below is TTN screen shot: | ||
273 | |||
274 | (% style="color:blue" %)**Create the application.** | ||
275 | |||
276 | [[image:image-20240907111048-1.png||height="183" width="1001"]] | ||
277 | |||
278 | [[image:image-20240907111305-2.png||height="572" width="1000"]] | ||
279 | |||
280 | (% style="color:blue" %)**Add devices to the created Application.** | ||
281 | |||
282 | [[image:image-20240907111659-3.png||height="185" width="977"]] | ||
283 | |||
284 | [[image:image-20240907111820-5.png||height="377" width="975"]] | ||
285 | |||
286 | (% style="color:blue" %)**Enter end device specifics manually.** | ||
287 | |||
288 | [[image:image-20240907112136-6.png||height="687" width="697"]] | ||
289 | |||
290 | (% style="color:blue" %)**Add DevEUI and AppKey.** | ||
291 | |||
292 | (% style="color:blue" %)**Customize a platform ID for the device.** | ||
293 | |||
294 | [[image:image-20240907112427-7.png]] | ||
295 | |||
296 | |||
297 | (% style="color:blue" %)**Step 2: **(%%)Add decoder | ||
298 | |||
299 | In TTN, user can add a custom payload so it shows friendly reading. | ||
300 | |||
301 | Click this link to get the decoder: [[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/>>url:https://github.com/dragino/dragino-end-node-decoder/tree/main/]] | ||
302 | |||
303 | Below is TTN screen shot: | ||
304 | |||
305 | [[image:image-20240907113746-8.png||height="567" width="1166"]] | ||
306 | |||
307 | [[image:image-20240907115849-10.png||height="615" width="1038"]] | ||
308 | |||
309 | (% style="color:blue" %)**Step 3:**(%%) Activate on LTC2-LB | ||
310 | |||
311 | Press the button for 5 seconds to activate the LTC2-LB. | ||
312 | |||
313 | (% style="color:green" %)**Green led**(%%) will fast blink 5 times, device will enter (% style="color:blue" %)**OTA mode**(%%) for 3 seconds. And then start to JOIN LoRaWAN network. (% style="color:green" %)**Green led**(%%) will solidly turn on for 5 seconds after joined in network. | ||
314 | |||
315 | After join success, it will start to upload messages to TTN and you can see the messages in the panel. | ||
316 | |||
317 | |||
318 | == 2.3 Working Mode & Uplink Payload == | ||
319 | |||
320 | === 2.3.1 Device Status, FPORT~=5 === | ||
321 | |||
322 | |||
323 | Users can use the downlink command(**0x26 01**) to ask LTC2-LB to send device configure detail, include device configure status. LTC2-LB will uplink a payload via FPort=5 to server. | ||
324 | |||
325 | The Payload format is as below. | ||
326 | |||
327 | (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %) | ||
328 | |(% colspan="6" style="background-color:#4f81bd; color:white" %)**Device Status (FPORT=5)** | ||
329 | |(% style="width:103px" %)**Size (bytes)**|(% style="width:72px" %)**1**|**2**|(% style="width:91px" %)**1**|(% style="width:86px" %)**1**|(% style="width:44px" %)**2** | ||
330 | |(% style="width:103px" %)Value|(% style="width:72px" %)Sensor Model|Firmware Version|(% style="width:91px" %)Frequency Band|(% style="width:86px" %)Sub-band|(% style="width:44px" %)BAT | ||
331 | |||
332 | Example in TTN: | ||
333 | |||
334 | [[image:image-20240907151051-11.png||height="334" width="1203"]] | ||
335 | |||
336 | |||
337 | (% style="color:#037691" %)**Sensor Model**(%%): For LTC2-LB, this value is 0x3D | ||
338 | |||
339 | (% style="color:#037691" %)**Firmware Version**(%%): 0x0100, Means: v1.0.0 version | ||
340 | |||
341 | (% style="color:#037691" %)**Frequency Band**(%%): | ||
342 | |||
343 | 0x01: EU868 | ||
344 | |||
345 | 0x02: US915 | ||
346 | |||
347 | 0x03: IN865 | ||
348 | |||
349 | 0x04: AU915 | ||
350 | |||
351 | 0x05: KZ865 | ||
352 | |||
353 | 0x06: RU864 | ||
354 | |||
355 | 0x07: AS923 | ||
356 | |||
357 | 0x08: AS923-1 | ||
358 | |||
359 | 0x09: AS923-2 | ||
360 | |||
361 | 0x0a: AS923-3 | ||
362 | |||
363 | 0x0b: CN470 | ||
364 | |||
365 | 0x0c: EU433 | ||
366 | |||
367 | 0x0d: KR920 | ||
368 | |||
369 | 0x0e: MA869 | ||
370 | |||
371 | (% style="color:#037691" %)**Sub-Band**(%%): | ||
372 | |||
373 | AU915 and US915:value 0x00 ~~ 0x08 | ||
374 | |||
375 | CN470: value 0x0B ~~ 0x0C | ||
376 | |||
377 | Other Bands: Always 0x00 | ||
378 | |||
379 | (% style="color:#037691" %)**Battery Info**(%%): | ||
380 | |||
381 | Check the battery voltage. | ||
382 | |||
383 | Ex1: 0x0B45 = 2885mV | ||
384 | |||
385 | Ex2: 0x0B49 = 2889mV | ||
386 | |||
387 | |||
388 | === 2.3.2 MOD~=1(General acquisition mode), FPORT~=2 === | ||
389 | |||
390 | |||
391 | MOD=1 is the default mode. End Node will uplink the real-time current sensor value in three case: | ||
392 | |||
393 | * Each [[TDC>>||anchor="H3.1A0SetTransmitIntervalTime"]] Interval. | ||
394 | * **[[Interrupt>>||anchor="H3.2SetInterruptMode"]]** packet sending. | ||
395 | * Trigger Alarm according to **[[AT+WMOD>>||anchor="H3.3A0Setalarmmode | ||
396 | "]], [[AT+CITEMP>>||anchor="H3.4Alarmchecktime"]], [[AT+ARTEMP>>||anchor="H3.5SetAlarmThreshold"]] **configure. | ||
397 | |||
398 | Below is the uplink payload which shows. | ||
399 | |||
400 | (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %) | ||
401 | |=(% style="width: 70px;background-color:#4F81BD;color:white" %)((( | ||
402 | **Size(bytes)** | ||
403 | )))|=(% style="width: 40px; background-color: rgb(79, 129, 189); color: white;" %)**2**|=(% style="width: 180px; background-color: rgb(79, 129, 189); color: white;" %)**1**|=(% style="width: 80px; background-color: rgb(79, 129, 189); color: white;" %)2|=(% style="width: 80px; background-color: rgb(79, 129, 189); color: white;" %)2|=(% style="width: 60px; background-color: rgb(79, 129, 189); color: white;" %)**4** | ||
404 | |(% style="width:62.5px" %)Value|(% style="width:54px" %)((( | ||
405 | BAT | ||
406 | )))|(% style="width:97px" %)((( | ||
407 | Interrupt flag & Interrupt Level & TEMP1H flag & TEMP1L flag&TEMP2H flag&TEMP1L flag | ||
408 | )))|(% style="width:110px" %)((( | ||
409 | Channel1 temperature | ||
410 | )))|(% style="width:90px" %)((( | ||
411 | Channel2 temperature | ||
412 | )))|(% style="width:123px" %)((( | ||
413 | Unix TimeStamp | ||
414 | |||
415 | |||
416 | ))) | ||
417 | |||
418 | (% 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==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]] | ||
419 | |||
420 | Example in TTN: | ||
421 | |||
422 | [[image:image-20240907151447-12.png||height="286" width="1217"]] | ||
423 | |||
424 | |||
425 | ((( | ||
426 | ==== (% style="color:blue" %)**Battery**(%%) ==== | ||
427 | |||
428 | Sensor Battery Level. | ||
429 | |||
430 | Ex1: 0x0B45 = 2885mV | ||
431 | |||
432 | Ex2: 0x0B49 = 2889mV | ||
433 | |||
434 | |||
435 | ==== (% style="color:blue" %)**Interrupt flag & Interrupt Level & TEMP1H flag & TEMP1L flag& TEMP2H flag & TEMP2L flag**(%%) ==== | ||
436 | |||
437 | **Interrupt flag & Interrupt Level:** | ||
438 | |||
439 | This data field shows if this packet is generated by interrupt or not. | ||
440 | |||
441 | Note: The Interrupt Pin refers to the **PA8** pin in the screw terminal. | ||
442 | |||
443 | **Example:** | ||
444 | |||
445 | If byte[2]&0x01=0x00 : Normal uplink packet. | ||
446 | |||
447 | If byte[2]&0x01=0x01 : Interrupt Uplink Packet. | ||
448 | |||
449 | If byte[2]&0x02>>1=0x00 : Interrupt pin low level. | ||
450 | |||
451 | If byte[2]&0x02>>1=0x01 : Interrupt pin high level. | ||
452 | |||
453 | **TEMP1H flag & TEMP1L flag&TEMP2H flag & TEMP2L flag:** | ||
454 | |||
455 | Temperature alarm flag. | ||
456 | |||
457 | Turn on the alarm mode, the TEMP1L fag flag is True when the channel1 temperature is below the set minimum value, otherwise it is False. | ||
458 | |||
459 | And the TEMP1H fag flag is True when the channel1 temperature is higher than the set maximum value, and False otherwise. | ||
460 | |||
461 | Turn on the alarm mode, the TEMP2L fag flag is True when the channel2 temperature is below the set minimum value, otherwise it is False. | ||
462 | |||
463 | And the TEMP2H fag flag is True when the channel2 temperature is higher than the set maximum value, and False otherwise. | ||
464 | ))) | ||
465 | |||
466 | ((( | ||
467 | |||
468 | |||
469 | ==== (% style="color:blue" %)**Channel 1 temperature**(%%) ==== | ||
470 | |||
471 | **Example**: | ||
472 | |||
473 | If payload is: 0105H: (0105 & 8000 == 0), temp = 0105H /10 = 26.1 degree | ||
474 | |||
475 | If payload is: FF3FH : (FF3F & 8000 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees. | ||
476 | |||
477 | (FF3F & 8000:Judge whether the highest bit is 1, when the highest bit is 1, it is negative) | ||
478 | |||
479 | If the value is -327.6, it means the channel1 PT100 probe is not connected. | ||
480 | |||
481 | If the value is -983, it means the PT100 converter is not connected. | ||
482 | |||
483 | |||
484 | ==== (% style="color:blue" %)**Channel 2 temperature**(%%) ==== | ||
485 | ))) | ||
486 | |||
487 | **Example**: | ||
488 | |||
489 | If payload is: 0105H: (0105 & 8000 == 0), temp = 0105H /10 = 26.1 degree | ||
490 | |||
491 | If payload is: FF3FH : (FF3F & 8000 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees. | ||
492 | |||
493 | (FF3F & 8000:Judge whether the highest bit is 1, when the highest bit is 1, it is negative) | ||
494 | |||
495 | If the value is -327.6, it means the channel2 PT100 probe is not connected. | ||
496 | |||
497 | If the value is -983, it means the PT100 converter is not connected. | ||
498 | |||
499 | (% 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" %) | ||
500 | |||
501 | === 2.3.2 MOD~=2(Continuous Sampling Mode), FPORT~=7 === | ||
502 | |||
503 | |||
504 | In Continuous Sampling Mode**[[(AT+MOD=2,aa,bb)>>||anchor="H3.10Setworkingmode28SinceV1.229 | ||
505 | "]]**, LTC2-LB will record the current sensor data at a fix interval, and report multiply group of data together to IoT server later. | ||
506 | |||
507 | (% style="color:red" %)**Notice: This mode has high power consumption. External power supply might be needed. More detail please check power consumption section.** | ||
508 | |||
509 | |||
510 | **AT+MOD=2,aa,bb format:** | ||
511 | |||
512 | * (% style="color:blue" %)**First Parameter set to 2**(%%)**:** Set LTC2-LB to work in Continuous Sampling Mode. | ||
513 | * (% style="color:blue" %)**aa** (%%): Set Sampling Interval, Unit: Second. | ||
514 | * (% style="color:blue" %)**bb** (%%): Define how many group of data will be uplink together. | ||
515 | |||
516 | When LTC2-LB is in Continuous Sampling Mode, the TDC time setting is disabled, and LTC2-LB will send uplink once it finished the number of sampling define in "bb". | ||
517 | |||
518 | |||
519 | **Example Command:(% style="color:blue" %)AT+MOD=2,60,5(%%)** | ||
520 | |||
521 | The LTC2-LB will read 2 channels every 1 minute. When the LTC2-LB reads 5 groups, the uplink is sent. So the uplink interval is 5 minutes. Each uplink will contain 5 sets of sensor values. Each group contains 2 channel data. So the payload for each uplink will include: | ||
522 | |||
523 | * Battery (2 bytes) | ||
524 | * + Group1 Sensor Value (4 Bytes): **the last 4th** reading for Channel 1 + Channel 2 | ||
525 | * + Group2 Sensor Value (4 Bytes): **the last 3rd** reading for Channel 1 + Channel 2 | ||
526 | * + Group3 Sensor Value (4 Bytes): **the last 2nd** reading for Channel 1 + Channel 2 | ||
527 | * + Group4 Sensor Value (4 Bytes): **the last** reading for Channel 1 + Channel 2 | ||
528 | * + Group5 Sensor Value (4 Bytes): reading for Channel 1 + Channel 2 | ||
529 | |||
530 | So totally 22 bytes payload in this example. | ||
531 | |||
532 | (% style="color:red" %)**Notice: Continuous Sampling Mode might generate a long payload, **(%%)LTC2-LB(% style="color:red" %)** will choose the suitable DR to uplink the data. This might decrease the transmit distance.** | ||
533 | |||
534 | |||
535 | Uplink packets use FPORT=7. | ||
536 | |||
537 | (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:500px" %) | ||
538 | |=(% style="width: 60px;background-color:#4F81BD;color:white" %)((( | ||
539 | **Size(bytes)** | ||
540 | )))|=(% colspan="3" rowspan="1" style="width: 54px; background-color: rgb(79, 129, 189); color: white;" %)2|=(% colspan="4" rowspan="1" style="width: 355px; background-color: rgb(79, 129, 189); color: white;" %)Dynamic Lenght , Depend on how many groups | ||
541 | |(% style="width:99px" %)((( | ||
542 | Value | ||
543 | )))|(% colspan="3" rowspan="1" style="width:54px" %)((( | ||
544 | BAT | ||
545 | )))|(% colspan="4" rowspan="1" style="width:355px" %)((( | ||
546 | Sensor value, each 4 bytes is a set of sensor values(The maximum is 30 groups). | ||
547 | ))) | ||
548 | |||
549 | Example parse in TTNv3. | ||
550 | |||
551 | [[image:image-20250115183628-1.png]] | ||
552 | |||
553 | (% 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" %)(% 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" %)(%%) | ||
554 | |||
555 | == 2.4 Datalog Feature == | ||
556 | |||
557 | |||
558 | LTC2-LB will auto get the time from LoRaWAN server during Join, and each uplink will then include a timestamp. When user want to retrieve sensor value, user can send a poll command from the IoT platform to ask sensor to send value in the required time slot. | ||
559 | |||
560 | |||
561 | === 2.4.1 Ways to get datalog via LoRaWAN === | ||
562 | |||
563 | |||
564 | There are two methods: | ||
565 | |||
566 | (% style="color:blue" %)**Method 1:** (%%)IoT Server sends a downlink LoRaWAN command to [[poll the value>>||anchor="H2.5.4A0Pollsensorvalue"]] for specified time range. | ||
567 | |||
568 | (% style="color:blue" %)**Method 2: **(%%)Set [[PNACKMD=1>>||anchor="H3.8AutoSendNone-ACKmessages"]], LTC2-LB will wait for ACK for every uplink, when there is no LoRaWAN network, LTC2-LB will mark these records with non-ack messages and store the sensor data, and it will send all messages (10s interval) after the network recovery. | ||
569 | |||
570 | |||
571 | (% style="color:red" %)**Note for method 2:** | ||
572 | |||
573 | * a) LTC2-LB will do an ACK check for data records sending to make sure every data arrive server. | ||
574 | * b) LTC2-LB will send data in **CONFIRMED Mode** when PNACKMD=1, but LTC2-LB won't re-transmit the packet if it doesn't get ACK, it will just mark it as a NONE-ACK message. In a future uplink if LTC2-LB gets a ACK, LTC2-LB will consider there is a network connection and resend all NONE-ACK Message. | ||
575 | |||
576 | |||
577 | === 2.4.2 Unix TimeStamp === | ||
578 | |||
579 | |||
580 | LTC2-LB uses Unix TimeStamp format based on | ||
581 | |||
582 | [[image:1655694312268-590.png]] | ||
583 | |||
584 | |||
585 | Users can get this time from the link: [[https:~~/~~/www.epochconverter.com/>>url:https://www.epochconverter.com/]] : | ||
586 | |||
587 | Below is the converter example | ||
588 | |||
589 | [[image:1655694332878-202.png]] | ||
590 | |||
591 | |||
592 | ((( | ||
593 | So, we can use AT+TIMESTAMP=1725693900 or downlink 3066DBFFCC00 to set current time : 2024-September-7 Saturday 07:25:00 | ||
594 | ))) | ||
595 | |||
596 | |||
597 | === 2.4.3 Set Device Time === | ||
598 | |||
599 | |||
600 | ((( | ||
601 | ((( | ||
602 | There are two ways to set the device's time: | ||
603 | ))) | ||
604 | ))) | ||
605 | |||
606 | ((( | ||
607 | ((( | ||
608 | (% style="color:#4f81bd" %)**1. Through LoRaWAN MAC Command (Default settings)** | ||
609 | ))) | ||
610 | ))) | ||
611 | |||
612 | ((( | ||
613 | ((( | ||
614 | Users need to set SYNCMOD=1 to enable sync time via the MAC command. | ||
615 | ))) | ||
616 | ))) | ||
617 | |||
618 | ((( | ||
619 | Once LTC2-LB Joined LoRaWAN network, it will send the MAC command (DeviceTimeReq) and server will reply with (DeviceTimeAns) to send the current time to LTC2-LB. If LTC2-LB fails to get the time from server, LTC2-LB will use the internal time and wait for next time request (AT+SYNCTDC to set time request period, default is 10 days). | ||
620 | |||
621 | |||
622 | ))) | ||
623 | |||
624 | ((( | ||
625 | ((( | ||
626 | (% style="color:red" %)**Note**(%%): (% style="color:#4f81bd" %)LoRaWAN Server needs to support LoRaWAN v1.0.3(MAC v1.0.3) (%%)or higher to support this MAC command feature, Chirpstack,TTN v3 and loriot support but TTN v2 doesn't support. If server doesn't support this command, it will through away uplink packet with this command, so user will lose the packet with time request for TTN v2 if SYNCMOD=1. | ||
627 | |||
628 | |||
629 | ))) | ||
630 | |||
631 | ((( | ||
632 | (% style="color:#4f81bd" %)**2. Manually Set Time** | ||
633 | ))) | ||
634 | |||
635 | ((( | ||
636 | Users need to set SYNCMOD=0 to manual time, otherwise, the user set time will be overwritten by the time set by the server. | ||
637 | ))) | ||
638 | ))) | ||
639 | |||
640 | |||
641 | === 2.4.4 Poll sensor value === | ||
642 | |||
643 | |||
644 | Users can poll sensor values based on timestamps. Below is the downlink command. | ||
645 | |||
646 | (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:431px" %) | ||
647 | |=(% colspan="4" style="width: 428px;background-color:#4F81BD;color:white" %)**Downlink Command to poll Open/Close status (0x31)** | ||
648 | |(% style="width:60px" %)**1byte**|(% style="width:127px" %)**4bytes**|(% style="width:122px" %)**4bytes**|(% style="width:116px" %)**1byte** | ||
649 | |(% style="width:60px" %)31|(% style="width:127px" %)Timestamp start|(% style="width:122px" %)Timestamp end|(% style="width:116px" %)Uplink Interval | ||
650 | |||
651 | ((( | ||
652 | |||
653 | ))) | ||
654 | |||
655 | ((( | ||
656 | Timestamp start and Timestamp end use Unix TimeStamp format as mentioned above. Devices will reply with all data log during this time period, use the uplink interval. | ||
657 | |||
658 | For example, downlink command [[image:image-20240907154739-16.png||height="36" width="204"]] | ||
659 | ))) | ||
660 | |||
661 | ((( | ||
662 | Is to check 2024-09-07 15:25:00 to 2024-09-07 15:30:00's data | ||
663 | |||
664 | Uplink Internal =10s,means LTC2-LB will send one packet every 10s. range 5~~255s. | ||
665 | ))) | ||
666 | |||
667 | |||
668 | === 2.4.5 Datalog Uplink payload === | ||
669 | |||
670 | |||
671 | When server senser a datalog polling to LTC2-LB, LTC2-LB will reply with one or more uplink messages as reply. Each uplink message includes multiply data entries value. Each entry has the same payload format as[[ normal uplink payload>>||anchor="H2.4A0200BUplinkPayload"]]. | ||
672 | |||
673 | (% style="color:red" %)**Note:** | ||
674 | |||
675 | * Poll Message Flag is set to 1. | ||
676 | * Each data entry is 11 bytes, to save airtime and battery, devices will send max bytes according to the current DR and Frequency bands. | ||
677 | |||
678 | For example, in US915 band, the max payload for different DR is: | ||
679 | |||
680 | 1. **DR0: **max is 11 bytes so one entry of data | ||
681 | 1. **DR1:** max is 53 bytes so devices will upload 4 entries of data (total 44 bytes) | ||
682 | 1. **DR2:** total payload includes 11 entries of data | ||
683 | 1. **DR3:** total payload includes 22 entries of data. | ||
684 | |||
685 | If devise doesn't have any data in the polling time. Device will uplink 11 bytes of 0 | ||
686 | |||
687 | |||
688 | **Example:** | ||
689 | |||
690 | If LTC2-LB has below data inside Flash: | ||
691 | |||
692 | (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %) | ||
693 | |(% style="background-color:#4f81bd; color:white; width:88px" %)**Flash Add**|(% style="background-color:#4f81bd; color:white; width:151px" %)**Unix Time**|(% style="background-color:#4f81bd; color:white; width:38px" %)**Ext**|(% style="background-color:#4f81bd; color:white; width:107px" %)**BAT voltage**|(% style="background-color:#4f81bd; color:white; width:126px" %)**Value** | ||
694 | |(% style="width:88px" %)8021630|(% style="width:151px" %)systime= 2021/5/16 01:17:44|(% style="width:38px" %)1|(% style="width:107px" %)3684|(% style="width:123px" %)temp1=24.7 temp2=25.2 | ||
695 | |(% style="width:88px" %)8021640|(% style="width:151px" %)systime= 2021/5/16 01:37:44|(% style="width:38px" %)1|(% style="width:107px" %)3681|(% style="width:123px" %)temp1=24.7 temp2=25.2 | ||
696 | |(% style="width:88px" %)8021650|(% style="width:151px" %)systime= 2021/5/16 01:57:44|(% style="width:38px" %)1|(% style="width:107px" %)3681|(% style="width:123px" %)temp1=24.7 temp2=25.1 | ||
697 | |(% style="width:88px" %)8021660|(% style="width:151px" %)systime= 2021/5/16 02:17:44|(% style="width:38px" %)1|(% style="width:107px" %)3684|(% style="width:123px" %)temp1=24.7 temp2=25.0 | ||
698 | |(% style="width:88px" %)8021670|(% style="width:151px" %)systime= 2021/5/16 02:37:44|(% style="width:38px" %)1|(% style="width:107px" %)3684|(% style="width:123px" %)temp1=24.6 temp2=25.0 | ||
699 | |(% style="width:88px" %)8021680|(% style="width:151px" %)systime= 2021/5/16 02:57:44|(% style="width:38px" %)1|(% style="width:107px" %)3684|(% style="width:123px" %)temp1=24.6 temp2=25.1 | ||
700 | |(% style="width:88px" %)8021690|(% style="width:151px" %)systime= 2021/5/16 03:17:44|(% style="width:38px" %)1|(% style="width:107px" %)3684|(% style="width:123px" %)temp1=24.5 temp2=25.0 | ||
701 | |(% style="width:88px" %)80216A0|(% style="width:151px" %)systime= 2021/5/16 03:37:44|(% style="width:38px" %)1|(% style="width:107px" %)3684|(% style="width:123px" %)temp1=24.5 temp2=25.0 | ||
702 | |(% style="width:88px" %)80216B0|(% style="width:151px" %)systime= 2021/5/16 03:57:44|(% style="width:38px" %)1|(% style="width:107px" %)3684|(% style="width:123px" %)temp1=24.4 temp2=25.0 | ||
703 | |||
704 | If user send below downlink command: **3166DBFFCC66DC00F80A** | ||
705 | |||
706 | Where : Start time: 66DBFFCC = time 2024/9/7 15:25:00 | ||
707 | |||
708 | Stop time: 66DC00F8 = time 2024/9/7 15:30:00 | ||
709 | |||
710 | |||
711 | LTC2-LB will uplink this payload. | ||
712 | |||
713 | [[image:image-20240907161952-18.png||height="413" width="1192"]](% style="display:none" %) | ||
714 | |||
715 | (% style="color:red" %)**000000F700FC4266DBFFD0**(%%) 000000F700FC4266DC000C 000000F700FB4266DC0048 000000F700FB4266DC0084 000000F800FC4266DC00C0 | ||
716 | |||
717 | Where the first 11 bytes is for the first entry: | ||
718 | |||
719 | (% style="color:red" %)**0000 00F7 00FC 42 66DBFFD0** | ||
720 | |||
721 | (% style="color:#4f81bd" %)**0x0000:**(%%) The first two bytes are reserved positions and have no meaning. | ||
722 | |||
723 | (% style="color:#4f81bd" %)**0x00F7:**(%%) **Channel 2 temp**=0x00F7/10=24.7℃ | ||
724 | |||
725 | (% style="color:#4f81bd" %)**0x00FC:**(%%) **Channel 1 temp**=0x0FC/10=25.2℃ | ||
726 | |||
727 | (% style="color:#4f81bd" %)**0x42:**(%%) **Interrupt flag & Interrupt Level:** | ||
728 | |||
729 | * If payload & 0x02 = 0x02 **~-~->** The** **interrupt Level is "High"; | ||
730 | * If payload & 0x02 = 0x00 **~-~->** The** **interrupt Level is "Low"; | ||
731 | * If payload & 0x01 = 0x01 **~-~->** The** **interrupt flag is "Ture"; | ||
732 | * If payload & 0x01 = 0x00 **~-~->** The** **interrupt flag is "False"; | ||
733 | |||
734 | (% style="color:#4f81bd" %)** 0x66DBFFD0:**(%%) **System timestamp**=0x66DBFFD0=1725693904(UTC) | ||
735 | |||
736 | |||
737 | **Example:** | ||
738 | |||
739 | The datalog data is as follows: | ||
740 | |||
741 | 000000F700FC4266DBFFD0 000000F700FC4266DC000C 000000F700FB4266DC0048 000000F700FB4266DC0084 000000F800FC4266DC00C0 | ||
742 | |||
743 | |||
744 | And the decoding on the server is: | ||
745 | |||
746 | "DATALOG": "[25.2,24.7,High,False,2024-09-07 07:25:04],[25.2,24.7,High,False,2024-09-07 07:26:04],[25.1,24.7,High,False,2024-09-07 07:27:04],[25.1,24.7,High,False,2024-09-07 07:28:04],[25.2,24.8,High,False,2024-09-07 07:29:04],", | ||
747 | |||
748 | Its data format is: | ||
749 | |||
750 | [Temp_Channel1,Temp_Channel2,Interrupt_level,Interrupt_flag,Data_time],[Temp_Channel1,Temp_Channel2,Interrupt_level,Interrupt_flag,Data_time],... | ||
751 | |||
752 | |||
753 | = 3. Configure LTC2-LB via AT Command or LoRaWAN Downlink = | ||
754 | |||
755 | |||
756 | ((( | ||
757 | ((( | ||
758 | Use can configure LTC2-LB via AT Command or LoRaWAN Downlink. | ||
759 | ))) | ||
760 | ))) | ||
761 | |||
762 | * ((( | ||
763 | ((( | ||
764 | AT Command Connection: See [[FAQ>>||anchor="H6.A0FAQ"]]. | ||
765 | ))) | ||
766 | ))) | ||
767 | * ((( | ||
768 | ((( | ||
769 | LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>doc:Main.WebHome]] | ||
770 | ))) | ||
771 | ))) | ||
772 | |||
773 | ((( | ||
774 | ((( | ||
775 | |||
776 | ))) | ||
777 | |||
778 | ((( | ||
779 | There are two kinds of commands to configure LTC2-LB, they are: | ||
780 | ))) | ||
781 | ))) | ||
782 | |||
783 | ((( | ||
784 | ((( | ||
785 | (% style="color:#4f81bd" %)** General Commands**. | ||
786 | ))) | ||
787 | ))) | ||
788 | |||
789 | ((( | ||
790 | ((( | ||
791 | These commands are to configure: | ||
792 | ))) | ||
793 | ))) | ||
794 | |||
795 | * ((( | ||
796 | ((( | ||
797 | General system settings like: uplink interval. | ||
798 | ))) | ||
799 | ))) | ||
800 | * ((( | ||
801 | ((( | ||
802 | LoRaWAN protocol & radio related command. | ||
803 | ))) | ||
804 | ))) | ||
805 | |||
806 | ((( | ||
807 | ((( | ||
808 | They are same for all Dragino Device which support DLWS-005 LoRaWAN Stack. These commands can be found on the wiki: [[End Device AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]] | ||
809 | ))) | ||
810 | ))) | ||
811 | |||
812 | ((( | ||
813 | ((( | ||
814 | (% style="color:#4f81bd" %)**Commands special design for LTC2-LB** | ||
815 | ))) | ||
816 | ))) | ||
817 | |||
818 | ((( | ||
819 | ((( | ||
820 | These commands only valid for LTC2-LB, as below:(% title="Click and drag to resize" %) | ||
821 | ))) | ||
822 | ))) | ||
823 | |||
824 | (% 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"]](% 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"]](% 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" title="Click and drag to resize" %) | ||
825 | |||
826 | |||
827 | == 3.1 Set Transmit Interval Time == | ||
828 | |||
829 | |||
830 | Feature: Change LoRaWAN End Node Transmit Interval. | ||
831 | |||
832 | (% style="color:#037691" %)**AT Command: AT+TDC** | ||
833 | |||
834 | (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:501px" %) | ||
835 | |(% style="background-color:#4f81bd; color:white; width:155px" %)**Command Example**|(% style="background-color:#4f81bd; color:white; width:166px" %)**Function**|(% style="background-color:#4f81bd; color:white; width:180px" %)**Response** | ||
836 | |(% style="width:155px" %)AT+TDC=?|(% style="width:162px" %)Show current transmit Interval|(% style="width:177px" %)((( | ||
837 | 1200000(Default value) | ||
838 | OK | ||
839 | the interval is 1200000ms=1200s | ||
840 | ))) | ||
841 | |(% style="width:155px" %)AT+TDC=600000|(% style="width:162px" %)Set Transmit Interval|(% style="width:177px" %)((( | ||
842 | OK | ||
843 | Set transmit interval to 600000ms=600 seconds | ||
844 | ))) | ||
845 | |||
846 | ((( | ||
847 | (% style="color:#037691" %)**Downlink Command: 0x01** | ||
848 | ))) | ||
849 | |||
850 | ((( | ||
851 | ((( | ||
852 | Format: Command Code (0x01) followed by 3 bytes time value. | ||
853 | |||
854 | ((( | ||
855 | If the downlink payload=0100003C, it means set the END Node's Transmit Interval to 0x00003C=60(S), while type code is 01. | ||
856 | ))) | ||
857 | |||
858 | * Example 1: Downlink Payload: **0100001E** ~/~/ Set Transmit Interval (TDC) = 30 seconds | ||
859 | * Example 2: Downlink Payload: **0100003C** ~/~/ Set Transmit Interval (TDC) = 60 seconds | ||
860 | ))) | ||
861 | ))) | ||
862 | |||
863 | |||
864 | == 3.2 Set Interrupt Mode == | ||
865 | |||
866 | |||
867 | Feature, Set Interrupt mode for **PA8** of pin. | ||
868 | |||
869 | When AT+INTMOD=0 is set, **PA8** is used as a digital input port. | ||
870 | |||
871 | (% style="color:#037691" %)**AT Command: AT+INTMOD** | ||
872 | |||
873 | (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) | ||
874 | |=(% style="width: 155px;background-color:#4F81BD;color:white" %)**Command Example**|=(% style="width: 197px;background-color:#4F81BD;color:white" %)**Function**|=(% style="width: 158px;background-color:#4F81BD;color:white" %)**Response** | ||
875 | |(% style="width:154px" %)AT+INTMOD=?|(% style="width:196px" %)Show current interrupt mode|(% style="width:157px" %)((( | ||
876 | 2 (Default) | ||
877 | |||
878 | OK | ||
879 | ))) | ||
880 | |(% style="width:154px" %)AT+INTMOD=2|(% style="width:196px" %)((( | ||
881 | Set Transmit Interval | ||
882 | 0. (Disable Interrupt), | ||
883 | ~1. (Trigger by rising and falling edge) | ||
884 | 2. (Trigger by falling edge) | ||
885 | 3. (Trigger by rising edge) | ||
886 | )))|(% style="width:157px" %)OK | ||
887 | |||
888 | (% style="color:#037691" %)**Downlink Command: 0x06** | ||
889 | |||
890 | Format: Command Code (0x06) followed by 3 bytes. | ||
891 | |||
892 | This means that the interrupt mode of the end node is set to 0x000003=3 (rising edge trigger), and the type code is 06. | ||
893 | |||
894 | * Example 1: Downlink Payload: 06000000 ~/~/ Turn off interrupt mode | ||
895 | * Example 2: Downlink Payload: 06000003 ~/~/ Set the interrupt mode to rising edge trigger | ||
896 | |||
897 | == 3.3 Set alarm mode == | ||
898 | |||
899 | |||
900 | Feature: Enable/Disable Alarm Mode. | ||
901 | |||
902 | (% style="color:#037691" %)**AT Command: AT+WMOD** | ||
903 | |||
904 | * AT+WMOD=0 ~/~/ Disable the alarm mode, default. | ||
905 | * AT+WMOD=1 ~/~/ Enable the alarm mode. | ||
906 | |||
907 | (% style="color:#037691" %)**Downlink Command: 0xA5** | ||
908 | |||
909 | * Downlink payload: **0xA500** ~/~/ Same as AT+WMOD=0 | ||
910 | * Downlink payload: **0xA501** ~/~/ Same as AT+WMOD=1 | ||
911 | |||
912 | == 3.4 Alarm check time == | ||
913 | |||
914 | |||
915 | Feature: The time interval to check sensor value for Alarm. ( Default: AT+CITEMP=1; Unit: minute ) | ||
916 | |||
917 | (% style="color:#037691" %)**AT Command: AT+CITEMP** | ||
918 | |||
919 | Example: | ||
920 | |||
921 | * AT+CITEMP=10 ~/~/ Set collection interval in 10 min, only in alarm mode. | ||
922 | |||
923 | (% style="color:#037691" %)**Downlink Command: 0xA6** | ||
924 | |||
925 | Format: Command Code (0xA6) followed by 2 bytes. | ||
926 | |||
927 | Example: | ||
928 | |||
929 | * Downlink payload: **0xA6000A** ~/~/ Same as AT+CITEMP=10 | ||
930 | |||
931 | == 3.5 Set Alarm Threshold == | ||
932 | |||
933 | |||
934 | Feature: Set Alarm Threshold. (Unit: ℃) | ||
935 | |||
936 | (% style="color:#037691" %)**AT Command: AT+ARTEMP** | ||
937 | |||
938 | The first parameter sets the low limit of channel 1, and the second parameter sets the high limit of channel 1. | ||
939 | |||
940 | The third parameter sets the low limit for channel 2, and the fourth parameter sets the high limit for channel 2. | ||
941 | |||
942 | Example: | ||
943 | |||
944 | * AT+ARTEMP=-200,800,-200,800 ~/~/ Channel 1 & Channel 2 operating temp: -200℃~~800℃,alarm when out of range. | ||
945 | * AT+ARTEMP=10,100,10,101 ~/~/ Channel 1 operating temp: 10℃~~100℃; Channel 2 operating temp: 10℃~~101℃, alarm when out of range. | ||
946 | |||
947 | (% style="color:#037691" %)**Downlink Command: 0xA7** | ||
948 | |||
949 | Format: Command Code (0xA7) followed by 8 bytes. | ||
950 | |||
951 | Each two bytes after the function code 0xA7 is a parameter, corresponding to the four parameters of AT+ARTEMP in sequence. | ||
952 | |||
953 | Example: | ||
954 | |||
955 | * Downlink payload: **0xA7FF380320FF380320** ~/~/ Same as AT+ARTEMP=-200,800,-200,800 | ||
956 | * Downlink payload: **0xA7000A0064000A0065** ~/~/ Same as AT+ARTEMP=10,100,10,101 | ||
957 | |||
958 | (% style="color:red" %)**Note: For negative temperature -200℃: 65536-200= 65336(D) = 0XFF38(H)** | ||
959 | |||
960 | |||
961 | == 3.6 Print data entries base on page == | ||
962 | |||
963 | |||
964 | Feature: Print the sector data from start page to stop page (max is 400 pages). | ||
965 | |||
966 | (% style="color:#037691" %)**AT Command: AT+PDTA** | ||
967 | |||
968 | (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %) | ||
969 | |(% style="background-color:#4f81bd; color:white; width:157px" %)**Command Example**|(% style="background-color:#4f81bd; color:white; width:353px" %)**Response** | ||
970 | |(% style="width:156px" %)((( | ||
971 | |||
972 | |||
973 | AT+PDTA=259,260 | ||
974 | |||
975 | Print page 259 to 260 | ||
976 | |||
977 | |||
978 | )))|(% style="width:362px" %)((( | ||
979 | Stop Tx events when read sensor data | ||
980 | |||
981 | 8021600 systime= 2021/5/16 00:17:44 1 3684 temp1=28.7 temp2=28.5 | ||
982 | |||
983 | 8021610 systime= 2021/5/16 00:37:44 1 3685 temp1=28.7 temp2=28.4 | ||
984 | |||
985 | 8021620 systime= 2021/5/16 00:57:44 1 3684 temp1=28.8 temp2=28.4 | ||
986 | |||
987 | 8021630 systime= 2021/5/16 01:17:44 1 3684 temp1=28.8 temp2=28.4 | ||
988 | |||
989 | 8021640 systime= 2021/5/16 01:37:44 1 3681 temp1=28.7 temp2=28.4 | ||
990 | |||
991 | 8021650 systime= 2021/5/16 01:57:44 1 3681 temp1=28.6 temp2=28.4 | ||
992 | |||
993 | 8021660 systime= 2021/5/16 02:17:44 1 3684 temp1=28.6 temp2=28.4 | ||
994 | |||
995 | 8021670 systime= 2021/5/16 02:37:44 1 3684 temp1=28.5 temp2=28.4 | ||
996 | |||
997 | 8021680 systime= 2021/5/16 02:57:44 1 3684 temp1=28.5 temp2=28.4 | ||
998 | |||
999 | 8021690 systime= 2021/5/16 03:17:44 1 3684 temp1=28.5 temp2=28.4 | ||
1000 | |||
1001 | 80216A0 systime= 2021/5/16 03:37:44 1 3684 temp1=28.5 temp2=28.4 | ||
1002 | |||
1003 | 80216B0 systime= 2021/5/16 03:57:44 1 3684 temp1=28.4 temp2=28.4 | ||
1004 | |||
1005 | 80216C0 systime= 2021/5/16 04:17:44 1 3684 temp1=28.4 temp2=28.4 | ||
1006 | |||
1007 | 80216D0 systime= 2021/5/16 04:37:44 1 3683 temp1=28.3 temp2=28.4 | ||
1008 | |||
1009 | 80216E0 systime= 2021/5/16 04:57:44 1 3684 temp1=28.3 temp2=28.4 | ||
1010 | |||
1011 | 80216F0 systime= 2021/5/16 05:17:44 1 3685 temp1=28.3 temp2=28.4 | ||
1012 | |||
1013 | Start Tx events | ||
1014 | |||
1015 | OK | ||
1016 | ))) | ||
1017 | |||
1018 | (% style="color:#037691" %)**Downlink Command:** | ||
1019 | |||
1020 | No downlink commands for feature | ||
1021 | |||
1022 | |||
1023 | == 3.7 Print last few data entries == | ||
1024 | |||
1025 | |||
1026 | Feature: Print the last few data entries | ||
1027 | |||
1028 | (% style="color:#037691" %)**AT Command: AT+PLDTA** | ||
1029 | |||
1030 | (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %) | ||
1031 | |(% style="background-color:#4f81bd; color:white; width:156px" %)**Command Example**|(% style="background-color:#4f81bd; color:white; width:354px" %)**Response** | ||
1032 | |((( | ||
1033 | AT+PLDTA=5 | ||
1034 | |||
1035 | Print last 5 entries | ||
1036 | )))|(% style="width:278px" %)((( | ||
1037 | Stop Tx events when read sensor data | ||
1038 | |||
1039 | 1 systime= 2021/5/17 03:12:37 1 3681 | ||
1040 | |||
1041 | temp1=26.0 temp2=26.1 | ||
1042 | |||
1043 | 2 systime= 2021/5/17 03:17:37 1 3682 | ||
1044 | |||
1045 | temp1=26.0 temp2=26.1 | ||
1046 | |||
1047 | 3 systime= 2021/5/17 03:22:37 1 3687 | ||
1048 | |||
1049 | temp1=25.9 temp2=26.1 | ||
1050 | |||
1051 | 4 systime= 2021/5/17 03:27:37 1 3684 | ||
1052 | |||
1053 | temp1=25.9 temp2=26.1 | ||
1054 | |||
1055 | 5 systime= 2021/5/17 03:32:37 1 3684 | ||
1056 | |||
1057 | temp1=26.2 temp2=26.1 | ||
1058 | |||
1059 | Start Tx events | ||
1060 | |||
1061 | OK | ||
1062 | ))) | ||
1063 | |||
1064 | (% style="color:#037691" %)**Downlink Command:** | ||
1065 | |||
1066 | No downlink commands for feature | ||
1067 | |||
1068 | |||
1069 | == 3.8 Clear Flash Record == | ||
1070 | |||
1071 | |||
1072 | Feature: Clear flash storage for data log feature. | ||
1073 | |||
1074 | (% style="color:#037691" %)**AT Command: AT+CLRDTA** | ||
1075 | |||
1076 | (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %) | ||
1077 | |=(% style="width: 157px;background-color:#4F81BD;color:white" %)**Command Example**|=(% style="width: 137px;background-color:#4F81BD;color:white" %)**Function**|=(% style="width: 216px;background-color:#4F81BD;color:white" %)**Response** | ||
1078 | |(% style="width:157px" %)AT+CLRDTA|(% style="width:136px" %)Clear date record|(% style="width:213px" %)((( | ||
1079 | Clear all stored sensor data… | ||
1080 | OK | ||
1081 | ))) | ||
1082 | |||
1083 | (% style="color:#037691" %)**Downlink Command: 0xA3** | ||
1084 | |||
1085 | * Example: **0xA301** ~/~/ Same as AT+CLRDTA | ||
1086 | |||
1087 | == 3.9 Auto Send None-ACK messages == | ||
1088 | |||
1089 | |||
1090 | Feature: LTC2-LB will wait for ACK for each uplink, If LTC2-LB doesn't get ACK from the IoT server, it will consider the message doesn't arrive server and store it. LTC2-LB keeps sending messages in normal periodically. Once LTC2-LB gets ACK from a server, it will consider the network is ok and start to send the not-arrive message. | ||
1091 | |||
1092 | (% style="color:#037691" %)**AT Command: AT+PNACKMD** | ||
1093 | |||
1094 | The default factory setting is 0 | ||
1095 | |||
1096 | (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:367px" %) | ||
1097 | |=(% style="width: 158px;background-color:#4F81BD;color:white" %)**Command Example**|=(% style="width: 121px;background-color:#4F81BD;color:white" %)**Function**|=(% style="width: 88px;background-color:#4F81BD;color:white" %)**Response** | ||
1098 | |(% style="width:158px" %)AT+PNACKMD=1|(% style="width:118px" %)Poll None-ACK message|(% style="width:87px" %)OK | ||
1099 | |||
1100 | (% style="color:#037691" %)**Downlink Command: 0x34** | ||
1101 | |||
1102 | * Example: 0x3401 ~/~/ Same as AT+PNACKMD=1 | ||
1103 | |||
1104 | == 3.10 Set working mode (Since V1.2) == | ||
1105 | |||
1106 | |||
1107 | Feature: Get or Set working mode. | ||
1108 | |||
1109 | (% style="color:#037691" %)**AT Command: AT+MOD** | ||
1110 | |||
1111 | (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %) | ||
1112 | |=(% style="width: 155px;background-color:#4F81BD;color:white" %)**Command Example**|=(% style="width: 197px;background-color:#4F81BD;color:white" %)**Function**|=(% style="width: 158px;background-color:#4F81BD;color:white" %)**Response** | ||
1113 | |(% style="width:154px" %)AT+MOD=?|(% style="width:196px" %)Shows the current working mode|(% style="width:157px" %)1 (default) | ||
1114 | OK | ||
1115 | |(% style="width:154px" %)AT+MOD=2,60,5|(% style="width:196px" %)Set working mode 2|(% style="width:157px" %)OK | ||
1116 | |||
1117 | (% style="color:blue" %)**Description of AT instruction for setting working mode 2:** | ||
1118 | |||
1119 | (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %) | ||
1120 | |=(% style="width: 155px; background-color:#4F81BD; color: white" %)**Command Example**|=(% style="width: 186.5px; background-color:#4F81BD; color: white" %)**Function**|=(% style="width: 168.5px; background-color:#4F81BD;color: white" %)Parameter | ||
1121 | |(% colspan="1" style="width:158px" %)AT+MOD=1|(% style="width:185px" %)Set General acquisition mode.|(% style="width:165px" %)1:General acquisition mode. | ||
1122 | |(% colspan="1" rowspan="3" style="width:158px" %)AT+MOD=2,60,5|(% style="width:185px" %)The first parameter sets the continuous detection mode 2.|(% style="width:165px" %)2: Continuous acquisition mode. | ||
1123 | |(% style="width:185px" %)The second parameter sets the detection sampling interval.|(% style="width:165px" %)60: Data were collected every 60 seconds. | ||
1124 | |(% style="width:185px" %)The third bit parameter sets the number of groups to record data.|(% style="width:165px" %)5: After 5 groups of data are collected, the uplink is performed. | ||
1125 | |||
1126 | (% style="color:#037691" %)**Downlink Command: 0x0A** | ||
1127 | |||
1128 | Format: Command Code (0x0A) followed by 1 byte or 4bytes,5 bytes. | ||
1129 | |||
1130 | * Example 1: Downlink Payload: 0A 01 **~-~-->** AT+MOD=1 | ||
1131 | * Example 2: Downlink Payload: 0A 02 00 3C 05 **~-~-->** AT+MOD=2,60,5 | ||
1132 | |||
1133 | == 3.11 Set time synchronization method (Since V1.2) == | ||
1134 | |||
1135 | |||
1136 | Feature: This command is used to enable automatic time calibration by time zone(Get or Set time synchronization method). | ||
1137 | |||
1138 | (% style="color:#037691" %)**AT Command: AT+SYNCMOD** | ||
1139 | |||
1140 | (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) | ||
1141 | |=(% style="width: 155px;background-color:#4F81BD;color:white" %)**Command Example**|=(% style="width: 156px; background-color: rgb(79, 129, 189); color: white;" %)**Function**|=(% style="width: 188px; background-color: rgb(79, 129, 189); color: white;" %)**Response/**Parameter | ||
1142 | |(% style="width:154px" %)((( | ||
1143 | AT+SYNCMOD=? | ||
1144 | )))|(% style="width:156px" %)Get the current time synchronization method|(% style="width:188px" %)((( | ||
1145 | 1,0 (Default) | ||
1146 | |||
1147 | OK | ||
1148 | ))) | ||
1149 | |(% colspan="1" rowspan="2" style="width:154px" %)AT+SYNCMOD=aa,bb|(% style="width:156px" %)((( | ||
1150 | **aa:** Enable/disable automatic time zone calibration | ||
1151 | )))|(% style="width:188px" %)((( | ||
1152 | **0:** Disable automatic time zone calibration. | ||
1153 | |||
1154 | **1:** Enable automatic time zone calibration | ||
1155 | ))) | ||
1156 | |(% style="width:156px" %)**bb: **Set the time zone: -12 ~~ 12|(% style="width:188px" %)((( | ||
1157 | Negative number: West Time Zone | ||
1158 | |||
1159 | Positive number: Eastern Time Zone | ||
1160 | ))) | ||
1161 | |||
1162 | (% style="color:#037691" %)**Downlink Command: 0x28** | ||
1163 | |||
1164 | Format: Command Code (0x28) followed by 2 bytes. | ||
1165 | |||
1166 | * Example 1: Downlink Payload: 28 00 00 ~/~/ Turn off the time zone calibration time. | ||
1167 | * Example 2: Downlink Payload: 28 01 FA ~/~/ Turn on time zone calibration time, UTC-6 | ||
1168 | * Example 3: Downlink Payload: 28 01 06 ~/~/ Turn on time zone calibration time, UTC+6 | ||
1169 | |||
1170 | (% style="color:red" %)**Note: UTC-6: 256+(-6)=250(D)=0xFA(H)** | ||
1171 | |||
1172 | |||
1173 | == 3.12 Set time synchronization interval (Since V1.2) == | ||
1174 | |||
1175 | |||
1176 | Feature: Get or set time synchronization interval in day or hour. | ||
1177 | |||
1178 | (% style="color:#037691" %)**AT Command: AT+SYNCTDC** | ||
1179 | |||
1180 | (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) | ||
1181 | |=(% style="width: 155px;background-color:#4F81BD;color:white" %)**Command Example**|=(% style="width: 188px; background-color: rgb(79, 129, 189); color: white;" %)**Function**|=(% style="width: 164px; background-color: rgb(79, 129, 189); color: white;" %)**Response/**Parameter | ||
1182 | |(% style="width:154px" %)((( | ||
1183 | AT+SYNCTDC=? | ||
1184 | )))|(% style="width:188px" %)Gets the current time synchronization interval|(% style="width:164px" %)((( | ||
1185 | 12,1 (Default) | ||
1186 | |||
1187 | OK | ||
1188 | ))) | ||
1189 | |(% colspan="1" rowspan="2" style="width:154px" %)((( | ||
1190 | AT+SYNCTDC=aa,bb | ||
1191 | )))|(% style="width:188px" %)((( | ||
1192 | **aa:** Set the interval for automatic synchronization | ||
1193 | )))|(% style="width:164px" %)Range: 0~~255 | ||
1194 | |(% style="width:188px" %)**bb:** Set the unit of the time synchronization interval|(% style="width:164px" %)((( | ||
1195 | **0:** Unit: day | ||
1196 | |||
1197 | **1:** Unit: hour | ||
1198 | ))) | ||
1199 | |||
1200 | (% style="color:#037691" %)**Downlink Command: 0x29** | ||
1201 | |||
1202 | Format: Command Code (0x29) followed by 3 bytes. | ||
1203 | |||
1204 | * Example 1: Downlink Payload: 29 0C 00 ~/~/ Calibrate once every 12 days | ||
1205 | * Example 2: Downlink Payload: 29 0C 01 ~/~/ Calibrate once every 12 hours | ||
1206 | |||
1207 | = 4. Battery & Power Consumption = | ||
1208 | |||
1209 | |||
1210 | LTC2-LB uses ER26500 + SPC1520 battery pack. 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. OTA Firmware update = | ||
1216 | |||
1217 | |||
1218 | (% class="wikigeneratedid" %) | ||
1219 | User can change firmware LTC2-LB to: | ||
1220 | |||
1221 | * Change Frequency band/ region. | ||
1222 | * Update with new features. | ||
1223 | * Fix bugs. | ||
1224 | |||
1225 | ((( | ||
1226 | **Firmware and changelog can be downloaded from :** **[[Firmware download link>>https://www.dropbox.com/scl/fo/q3w10zxznqvf0bdtdflab/AP_PngyY1vh2bCjn2nJl67M?rlkey=gxs04he1zbtv0cr37tt5bl2nr&st=rqy2x03q&dl=0]]** | ||
1227 | |||
1228 | **Methods to Update Firmware:** | ||
1229 | |||
1230 | * (Recommanded way) OTA firmware update via wireless : **[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Firmware%20OTA%20Update%20for%20Sensors/>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20OTA%20Update%20for%20Sensors/]]** | ||
1231 | * Update through UART TTL interface : **[[Instruction>>url:http://wiki.dragino.com/xwiki/bin/view/Main/UART%20Access%20for%20LoRa%20ST%20v4%20base%20model/#H1.LoRaSTv4baseHardware]]**. | ||
1232 | |||
1233 | |||
1234 | ))) | ||
1235 | |||
1236 | = 6. FAQ = | ||
1237 | |||
1238 | == 6.1 How to use AT Command to configure LTC2-LB == | ||
1239 | |||
1240 | |||
1241 | LTC2-LB supports AT Command set. User can use a USB to TTL adapter plus the Program Cable to connect to LTC2-LB for using AT command, as below. | ||
1242 | |||
1243 | **Connection:** | ||
1244 | |||
1245 | * (% style="background-color:yellow" %)**USB to TTL GND <~-~-> LTC2-LB GND** | ||
1246 | |||
1247 | * (% style="background-color:yellow" %)**USB to TTL RXD <~-~-> LTC2-LB TXD** | ||
1248 | |||
1249 | * (% style="background-color:yellow" %)**USB to TTL TXD <~-~-> LTC2-LB RXD** | ||
1250 | |||
1251 | ((( | ||
1252 | In PC, User needs to set (% style="color:blue" %)**serial tool**(%%)(such as [[putty>>url:https://www.chiark.greenend.org.uk/~~sgtatham/putty/latest.html]], SecureCRT) baud rate to (% style="color:green" %)**9600**(%%) to access to access serial console for LTC2-LB. The AT commands are disable by default and need to enter password ((% style="color:green" %)**default password is the AT+PIN on the box label**(%%))to active it. Timeout to input AT Command is 5 min, after 5-minute, user need to input password again. | ||
1253 | ))) | ||
1254 | |||
1255 | ((( | ||
1256 | Input password and ATZ to activate LTC2-LB,As shown below: | ||
1257 | ))) | ||
1258 | |||
1259 | [[image:image-20240907172040-19.png||height="499" width="700"]] | ||
1260 | |||
1261 | |||
1262 | = 7. Trouble Shooting = | ||
1263 | |||
1264 | == 7.1 AT Command input doesn't work == | ||
1265 | |||
1266 | |||
1267 | In the case if user can see the console output but can't type input to the device. Please check if you already include the (% style="color:green" %)**ENTER**(%%) while sending out the command. Some serial tool doesn't send (% style="color:green" %)**ENTER**(%%) while press the send key, user need to add ENTER in their string. | ||
1268 | |||
1269 | |||
1270 | = 8. Order Info = | ||
1271 | |||
1272 | |||
1273 | (% style="color:red" %)**Notice: This part number doesn't include the Temperature sensor. Users need to purchase separately.** | ||
1274 | |||
1275 | Part Number **:** (% style="color:blue" %)**LTC2-LB-XX** | ||
1276 | |||
1277 | (% style="color:blue" %)**XX**(%%)**: **The default frequency band | ||
1278 | |||
1279 | * (% style="color:red" %)**AS923 **(%%)**:** LoRaWAN AS923 band | ||
1280 | * (% style="color:red" %)**AU915 **(%%)**:** LoRaWAN AU915 band | ||
1281 | * (% style="color:red" %)**EU433 **(%%)**:** LoRaWAN EU433 band | ||
1282 | * (% style="color:red" %)**EU868 **(%%)**:** LoRaWAN EU868 band | ||
1283 | * (% style="color:red" %)**KR920 **(%%)**:** LoRaWAN KR920 band | ||
1284 | * (% style="color:red" %)**US915 **(%%)**:** LoRaWAN US915 band | ||
1285 | * (% style="color:red" %)**IN865 **(%%)**:** LoRaWAN IN865 band | ||
1286 | * (% style="color:red" %)**CN470 **(%%)**:** LoRaWAN CN470 band | ||
1287 | |||
1288 | (% 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** | ||
1289 | |||
1290 | |||
1291 | = 9. Packing Info = | ||
1292 | |||
1293 | |||
1294 | **Package Includes**: | ||
1295 | |||
1296 | * LTC2-LB LoRaWAN Temperature Transmitter x 1 | ||
1297 | |||
1298 | **Dimension and weight**: | ||
1299 | |||
1300 | * Device Size: cm | ||
1301 | * Device Weight: g | ||
1302 | * Package Size / pcs : cm | ||
1303 | * Weight / pcs : g | ||
1304 | |||
1305 | = 10. Support = | ||
1306 | |||
1307 | |||
1308 | * Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule. | ||
1309 | * 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]]. |