Show last authors
1 (% style="text-align:center" %)
2 [[image:image-20241205103955-1.jpeg||height="513" width="513"]]
3
4
5
6
7
8
9 **Table of Contents:**
10
11 {{toc/}}
12
13
14
15
16
17 = 1. Introduction =
18
19 == 1.1 What is T68DL LoRaWAN Temperature Sensor ==
20
21
22 (((
23 The Dragino (% style="color:blue" %)**T68DL Temperature sensor**(%%) is a Long Range LoRaWAN Sensor.
24 )))
25
26 (((
27 The T68DL allows users to send data and reach extremely long ranges. It provides ultra-long range spread spectrum communication and high interference immunity whilst minimizing current consumption. It targets professional wireless sensor network applications such as irrigation systems, smart metering, smart cities, building automation, and so on.
28 )))
29
30 (((
31 T68DL has a (% style="color:blue" %)**built-in 2400mAh non-chargeable battery**(%%) which can be used for up to 10 years*.
32 )))
33
34 (((
35 T68FL is full compatible with LoRaWAN v1.0.3 Class A protocol, it can work with a standard LoRaWAN gateway.
36 )))
37
38 (((
39 T68DL supports (% style="color:blue" %)**Datalog Feature**(%%). It will record the data when there is no network coverage and users can retrieve the sensor value later to ensure no miss for every sensor reading.
40 )))
41
42 (((
43 *The actual battery life depends on how often to send data, please see the battery analyzer chapter.
44 )))
45
46
47 == 1.2 Features ==
48
49
50 * LoRaWAN v1.0.3 Class A protocol
51 * Frequency Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915
52 * AT Commands to change parameters
53 * Remote configure parameters via LoRaWAN Downlink
54 * Firmware can be upgraded via OTA
55 * Built-in 2400mAh battery for up to 10 years of use.
56 * Built-in Temperature sensor
57 * Tri-color LED to indicate working status
58 * Datalog feature (Max 3328 records)
59
60 == 1.3 Specification ==
61
62
63 (% style="color:#037691" %)**Built-in Temperature Sensor:**
64
65 * Resolution: 0.01 °C
66 * Accuracy Tolerance : Typ ±0.3 °C
67 * Long Term Drift: < 0.02 °C/yr
68 * Operating Range: -40 ~~ 85 °C
69
70 = 2. Connect T68DL to IoT Server =
71
72 == 2.1 How does T68DL work? ==
73
74
75 (((
76 T68DL is configured as LoRaWAN OTAA Class A mode by default. Each T68DL is shipped with a worldwide unique set of OTAA keys. To use T68DL in a LoRaWAN network, first, we need to put the OTAA keys in LoRaWAN Network Server and then activate T68DL.
77 )))
78
79 (((
80 If T68DL is under the coverage of this LoRaWAN network. T68DL can join the LoRaWAN network automatically. After successfully joining, T68DL will start to measure environment temperature, and start to transmit sensor data to the LoRaWAN server. The default period for each uplink is 20 minutes.
81 )))
82
83
84 == 2.2 How to Activate T68DL? ==
85
86
87 (((
88 The T68DL has two working modes:
89 )))
90
91 * (((
92 (% style="color:blue" %)**Deep Sleep Mode**(%%): T68DL doesn't have any LoRaWAN activities. This mode is used for storage and shipping to save battery life.
93 )))
94 * (((
95 (% style="color:blue" %)**Working Mode**(%%): In this mode, T68DL works as LoRaWAN Sensor mode to Join LoRaWAN network and send out the sensor data to the server. Between each sampling/tx/rx periodically, T68DL will be in STOP mode (IDLE mode), in STOP mode, T68DLhas the same power consumption as Deep Sleep mode. 
96 )))
97
98 (((
99 The T68DL is set in deep sleep mode by default; The ACT button on the front is to switch to different modes:
100 )))
101
102 [[image:image-20241120092829-3.png||height="387" width="387"]]
103
104 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %)
105 |=(% 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**
106 |(% style="background-color:#f2f2f2; width:167px" %)Pressing ACT between 1s < time < 3s|(% style="background-color:#f2f2f2; width:117px" %)Test uplink status|(% style="background-color:#f2f2f2; width:225px" %)(((
107 If T68DL is already Joined to rhe LoRaWAN network, T68DL will send an uplink packet, (% style="color:blue" %)**Blue led** (%%)will blink once.
108 )))
109 |(% 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" %)(((
110 (% style="background-color:#f2f2f2; color:green" %)**Green led**(%%) will fast blink 5 times, T68DL  will enter working mode and start to JOIN LoRaWAN network.
111 (% style="background-color:#f2f2f2; color:green" %)**Green led**(%%) will solidly turn on for 5 seconds after join in network.
112 )))
113 |(% 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 T68DL is in Deep Sleep Mode.
114
115 == 2.3 Quick guide to connect to LoRaWAN server (OTAA) ==
116
117
118 (% class="wikigeneratedid" %)
119 This section shows an example of how to join the TTN V3 LoRaWAN IoT server. Use with other LoRaWAN IoT servers is of a similar procedure.
120
121 (% class="wikigeneratedid" %)
122 [[image:image-20241127085835-1.png]]
123
124
125 (((
126 Assume the LPS8v2 is already set to connect to [[TTN V3 network>>url:https://eu1.cloud.thethings.network]], So it provides network coverage for T68DL. Next we need to add the T68DL device in TTN V3:
127 )))
128
129
130 (% style="color:blue" %)**Step 1: **(%%)Create a device in TTN V3 with the OTAA keys from T68DL.
131
132 (((
133 Each T68DL is shipped with a sticker with its device EUI, APP Key and APP EUI as below:
134 )))
135
136 [[image:image-20230426083319-1.png||_mstalt="431106" height="258" width="556"]]
137
138
139 User can enter these keys in the LoRaWAN Server portal. Below is TTN V3 screenshot:
140
141 **Create the application.**
142
143 [[image:image-20241025090511-1.png]]
144
145
146 [[image:image-20241025090534-2.png]]
147
148
149 **Add devices to the created Application.**
150
151 [[image:image-20241025090607-3.png]]
152
153 [[image:image-20241025090624-4.png]]
154
155
156 **Enter end device specifics manually.**
157
158 [[image:image-20241025090709-5.png]]
159
160
161 **Add DevEUI and AppKey.**
162
163 **Customize a platform ID for the device.**
164
165 [[image:image-20241025090805-6.png]]
166
167
168 (% style="color:blue" %)**Step 2: **(%%)Add decoder
169
170 In TTN, user can add a custom payload so it shows friendly reading.
171
172 Click this link to get the decoder: [[T68DL decoder>>url:https://github.com/dragino/dragino-end-node-decoder/tree/main/LWL04-LB]].
173
174 Below is TTN screen shot:
175
176 [[image:image-20241025101057-9.png||height="570" width="1202"]]
177
178
179 (% style="color:blue" %)**Step 3: **(%%)[[**Power on**>>||anchor="H2.2HowtoActivateT68DL3F"]] T68DL and it will auto join to the TTN V3 network. After join success, it will start to upload message to TTN V3 and user can see in the panel.
180
181 [[image:image-20241024114317-1.png||height="432" width="1204"]]
182
183
184 == 2.4 Uplink Payload ==
185
186 === 2.4.1 Device Status, FPORT~=5 ===
187
188
189 Users can use the downlink command(**0x26 01**) to ask T68DL to send device configure detail, include device configure status. T68DL will uplink a payload via FPort=5 to server.
190
191 The Payload format is as below.
192
193 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
194 |(% colspan="6" style="background-color:#4f81bd; color:white" %)**Device Status (FPORT=5)**
195 |(% style="width:103px" %)**Size (bytes)**|(% style="width:72px" %)**1**|**2**|(% style="width:91px" %)**1**|(% style="width:86px" %)**1**|(% style="width:44px" %)**2**
196 |(% 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
197
198 Example parse in TTNv3:
199
200 [[image:image-20241025101800-10.png||height="275" width="1199"]]
201
202 (% style="color:#037691" %)**Sensor Model**(%%): For T68DL, this value is 0x34
203
204 (% style="color:#037691" %)**Firmware Version**(%%): 0x0100, Means: v1.0.0 version
205
206 (% style="color:#037691" %)**Frequency Band**:
207
208 0x01: EU868
209
210 0x02: US915
211
212 0x03: IN865
213
214 0x04: AU915
215
216 0x05: KZ865
217
218 0x06: RU864
219
220 0x07: AS923
221
222 0x08: AS923-1
223
224 0x09: AS923-2
225
226 0x0a: AS923-3
227
228 0x0b: CN470
229
230 0x0c: EU433
231
232 0x0d: KR920
233
234 0x0e: MA869
235
236
237 (% style="color:#037691" %)**Sub-Band**:
238
239 AU915 and US915:value 0x00 ~~ 0x08
240
241 CN470: value 0x0B ~~ 0x0C
242
243 Other Bands: Always 0x00
244
245
246 (% style="color:#037691" %)**Battery Info**:
247
248 Check the battery voltage.
249
250 Ex1: 0x0CD5 = 3285mV
251
252 Ex2: 0x0B49 = 2889mV
253
254
255 === 2.4.2 Real-Time Temperature data, Uplink FPORT~=2 ===
256
257 (((
258
259
260 T68DL will send this uplink **after** Device Status once join the LoRaWAN network successfully. And T68DL will:
261
262 periodically send this uplink every 20 minutes, this interval [[can be changed>>||anchor="H4.1SetTransmitIntervalTime"]].
263
264 Uplink Payload totals 9 bytes.
265 )))
266
267 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %)
268 |=(% style="width: 60px;background-color:#4F81BD;color:white" %)(((
269 **Size(bytes)**
270 )))|=(% style="width: 30px;background-color:#4F81BD;color:white" %)(((
271 **2**
272 )))|=(% style="width: 170px;background-color:#4F81BD;color:white" %)(((
273 **2**
274 )))|=(% style="width: 150px;background-color:#4F81BD;color:white" %)(((
275 **1**
276 )))|=(% style="width: 100px;background-color:#4F81BD;color:white" %)(((
277 **4**
278 )))
279 |(% style="width:97px" %)(((
280 Value
281 )))|(% style="width:39px" %)(((
282 BAT
283 )))|(% style="width:100px" %)(((
284 (((
285 Built-In Temperature(TMP116)
286 )))
287 )))|(% style="width:47px" %)(((
288 TEMPH_flag & TEMPL_flag
289 )))|(% style="width:51px" %)(((
290 Data_time
291 )))
292
293 * (% style="color:blue" %)**Battery**
294
295 Check the battery voltage.
296
297 Example: 0x0CBF(H)= 3263(D) mV
298
299
300 * (% style="color:blue" %)**Built-In Temperature (TMP116)**
301
302 **Example**:
303
304 If payload is: 0x0AFE:  (0AFE & 8000 == 0), temp = 0AFEH/10 = 28.14 degree
305
306 If payload is: 0xFF3F :  (FF3F & 8000 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees.
307
308 (FF3F & 8000:Judge whether the highest bit is 1, when the highest bit is 1, it is negative)
309
310
311 * (% style="color:blue" %)**TEMPH_flag & TEMPL_flag**
312
313 **Example**:
314
315 TEMPH_flag:
316
317 If payload is: 0x02:  (0x02 & 0x01 == 0), TEMPH_flag = False
318
319 If payload is: 0x01:  (0x01 & 0x01 == 1). TEMPH_flag = True
320
321
322 TEMPL_flag:
323
324 If payload is: 0x01:  (0x01 & 0x02 == 0), TEMPL_flag = False
325
326 If payload is: 0x02:  (0x02 & 0x02 == 1). TEMPL_flag = True
327
328
329
330 * (% style="color:blue" %)**Data_time**
331
332 Unit TimeStamp Example: 671F024A(H) = 1730085450(D)
333
334 Put the decimal value into this link([[https:~~/~~/www.epochconverter.com)>>url:https://www.epochconverter.com/]])to get the time.
335
336
337 Example parse in TTNv3:
338
339 [[image:image-20241025103329-11.png||height="357" width="1381"]]
340
341
342 == 2.5 Show data on Datacake ==
343
344
345 (((
346 Datacake IoT platform provides a human-friendly interface to show the sensor data, once we have sensor data in TTN V3, we can use Datacake to connect to TTN V3 and see the data in Datacake. Below are the steps:
347 )))
348
349 (% style="color:blue" %)**Step 1:**(%%) **Link TTNv3 to Datacake. **[[https:~~/~~/docs.datacake.de/lorawan/lns/thethingsindustries#create-integration-on-tti>>url:https://docs.datacake.de/lorawan/lns/thethingsindustries#create-integration-on-tti]]
350
351 (% style="color:blue" %)**Step 2:**(%%)** Add T68DL to Datacake.** Go to TTN V3 Console ~-~-> Applications ~-~-> Integrations ~-~-> Add Integrations.
352
353 [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LWL04--LoRaWAN_Water_Leak_Sensor_User_Manual/WebHome/image-20240910150951-1.png?width=694&height=561&rev=1.1||alt="image-20240910150951-1.png"]]
354
355 [[image:image-20241028112746-1.png||height="522" width="693"]]
356
357 [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LWL04--LoRaWAN_Water_Leak_Sensor_User_Manual/WebHome/image-20240910151137-3.png?width=611&height=679&rev=1.1||alt="image-20240910151137-3.png"]]
358
359 [[image:image-20241028113010-2.png||height="477" width="564"]]
360
361
362 (% style="color:blue" %)**Step 3:**(%%)** Configure T68DL in Datacake.**
363
364 [[image:image-20241028113331-3.png||height="305" width="801"]]
365
366
367 [[image:image-20241028113428-4.png||height="373" width="803"]]
368
369 [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LWL03A%20%E2%80%93%20LoRaWAN%20None-Position%20Rope%20Type%20Water%20Leak%20Controller%20User%20Manual/WebHome/image-20221102092921-5.png?rev=1.1||alt="image-20221102092921-5.png" height="414" width="780"]]
370
371
372 == 2.6 Datalog Feature ==
373
374
375 (((
376 Datalog Feature is to ensure IoT Server can get all sampling data from Sensor even if the LoRaWAN network is down. For each sampling, T68DL will store the reading for future retrieving purposes. There are two ways for IoT servers to get datalog from T68DL.
377 )))
378
379
380 === 2.6.1 Ways to get datalog via LoRaWAN ===
381
382
383 There are two methods:
384
385 (% style="color:blue" %)**Method 1:** (%%)IoT Server sends a downlink LoRaWAN command to [[poll the value>>||anchor="H2.6.4Pollsensorvalue"]] for specified time range.
386
387
388 (% style="color:blue" %)**Method 2: **(%%)Set [[PNACKMD=1>>||anchor="H4.13AutoSendNone-ACKmessages"]], T68DL will wait for ACK for every uplink, when there is no LoRaWAN network, T68DL 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.
389
390
391 (% style="color:red" %)**Note for method 2:**
392
393 * a) T68DL will do an ACK check for data records sending to make sure every data arrive server.
394 * b) T68DL will send data in **CONFIRMED Mode** when PNACKMD=1, but T68DL 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 T68DL gets a ACK, T68DL will consider there is a network connection and resend all NONE-ACK Message.
395
396 Below is the typical case for the auto-update datalog feature (Set PNACKMD=1)
397
398 [[image:image-20241127092254-2.png||height="411" width="1181"]]
399
400 === 2.6.2 Unix TimeStamp ===
401
402
403 T68DL uses Unix TimeStamp format based on
404
405 [[image:image-20220523001219-11.png||_mstalt="450450" height="97" width="627"]]
406
407
408 User can get this time from link:  [[https:~~/~~/www.epochconverter.com/>>url:https://www.epochconverter.com/]] :
409
410 Below is the converter example
411
412 [[image:image-20220523001219-12.png||_mstalt="450827" height="298" width="720"]]
413
414
415 So, we can use AT+TIMESTAMP=1730085450 or downlink 30671F024A to set the current time 2024 – October ~-~- 28 Monday 3:17:30
416
417
418 === 2.6.3 Set Device Time ===
419
420
421 (((
422 (% style="color:blue" %)**There are two ways to set device's time:**
423 )))
424
425 (((
426
427
428 **1.  Through LoRaWAN MAC Command (Default settings)**
429 )))
430
431 (((
432 User need to set SYNCMOD=1 to enable sync time via MAC command.
433 )))
434
435 (((
436 Once T68DL Joined LoRaWAN network, it will send the MAC command (DeviceTimeReq) and the server will reply with (DeviceTimeAns) to send the current time to T68DL. If  T68DL fails to get the time from the server, T68DL will use the internal time and wait for next time request (AT+SYNCTDC to set the time request period, default is 10 days).
437 )))
438
439 (((
440 (% style="color:red" %)**Note: LoRaWAN Server need to support LoRaWAN v1.0.3(MAC v1.0.3) or higher to support this MAC command feature, Chirpstack,TTN V3 v3 and loriot support but TTN V3 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 V3 v2 if SYNCMOD=1.**
441 )))
442
443
444 (((
445 **2. Manually Set Time**
446 )))
447
448 (((
449 User needs to set SYNCMOD=0 to manual time, otherwise, the user set time will be overwritten by the time set by the server.
450 )))
451
452
453 === 2.6.4 Poll sensor value ===
454
455
456 User can poll sensor value based on timestamps from the server. Below is the downlink command.
457
458 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:428px" %)
459 |(% style="background-color:#4f81bd; color:white; width:59px" %)**1byte**|(% style="background-color:#4f81bd; color:white; width:128px" %)**4bytes**|(% style="background-color:#4f81bd; color:white; width:124px" %)**4bytes**|(% style="background-color:#4f81bd; color:white; width:117px" %)**1byte**
460 |(% style="width:58px" %)31|(% style="width:128px" %)Timestamp start|(% style="width:123px" %)Timestamp end|(% style="width:116px" %)Uplink Interval
461
462 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.
463
464 For example, downlink command (% _mstmutation="1" %)**31  67180C82  671836B2  05**(%%)
465
466 Is to check 2024/10/22 20:35:14 to 2024/10/22 23:35:14's data
467
468 Uplink Internal =5s, means T68DL will send one packet every 5s. range 5~~255s.
469
470
471 === 2.6.5 Datalog Uplink payload ===
472
473
474 The Datalog poll reply uplink will use below payload format.
475
476 **Retrieval data payload:**
477
478 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %)
479 |=(% style="width: 60px;background-color:#4F81BD;color:white" %)(((
480 **Size(bytes)**
481 )))|=(% style="width: 90px;background-color:#4F81BD;color:white" %)4|=(% style="width: 90px;background-color:#4F81BD;color:white" %)**2**|=(% style="width: 120px;background-color:#4F81BD;color:white" %)**1**|=(% style="width: 150px;background-color:#4F81BD;color:white" %)**4**
482 |(% style="width:97px" %)Value|(% style="width:123px" %)Reserved|(% style="width:108px" %)TMP116_Temp|(% style="width:159px" %)ACK message flag |(% style="width:80px" %)[[Unix Time Stamp>>||anchor="H2.6.2UnixTimeStamp"]]
483
484 **ACK message flag:**
485
486 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %)
487 |(% style="background-color:#4f81bd; color:white; width:60px" %)**Bits**|(% style="background-color:#4f81bd; color:white; width:150px" %)**7**|(% style="background-color:#4f81bd; color:white; width:150px" %)**6**|(% style="background-color:#4f81bd; color:white; width:150px" %)**[5:0]**
488 |(% style="width:96px" %)Status|(% style="width:124px" %)No ACK Message|(% style="width:146px" %)Poll Message Flag|(% style="width:109px" %)Reserved
489
490 (% style="color:blue" %)**No ACK Message**(%%):  1: This message means this payload is fromn Uplink Message which doesn't get ACK from the server before ( for [[PNACKMD=1>>||anchor="H4.13AutoSendNone-ACKmessages"]] feature)
491
492 (% style="color:blue" %)**Poll Message Flag**(%%): 1: This message is a poll message reply.
493
494 * Poll Message Flag is set to 1.
495
496 * Each data entry is 11 bytes, to save airtime and battery, devices will send max bytes according to the current DR and Frequency bands.
497
498 For example, in US915 band, the max payload for different DR is:
499
500 (% style="color:blue" %)**a) DR0:** (%%)max is 11 bytes so one entry of data
501
502 (% style="color:blue" %)**b) DR1:**(%%) max is 53 bytes so devices will upload 4 entries of data (total 44 bytes)
503
504 (% style="color:blue" %)**c) DR2:**(%%) total payload includes 11 entries of data
505
506 (% style="color:blue" %)**d) DR3: **(%%)total payload includes 22 entries of data.
507
508 If devise doesn't have any data in the polling time. Device will uplink 11 bytes of 0   
509
510
511 **Example:**
512
513 If T68DL has below data inside Flash:
514
515 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %)
516 |=(% style="width: 88px; background-color:#4F81BD;color:white" %)Flash Add|=(% style="width: 172px; background-color:#4F81BD;color:white" %)**Unix Time**|=(% style="width: 105px; background-color:#4F81BD;color:white" %)**BAT voltage**|=(% style="width: 145px; background-color:#4F81BD;color:white" %)**Value**
517 |(% style="width:89px" %)(((
518 8031460
519 )))|(% style="width:133px" %)(((
520 2024/10/22 20:35:14
521 )))|(% style="width:103px" %)(((
522 2913
523 )))|(% style="width:131px" %)(((
524 tmp116_temp:28.80
525 )))
526 |(% style="width:89px" %)(((
527 8031470
528 )))|(% style="width:133px" %)(((
529 2024/10/22 20:55:14
530 )))|(% style="width:103px" %)(((
531 2912
532 )))|(% style="width:131px" %)(((
533 tmp116_temp:28.82
534 )))
535 |(% style="width:89px" %)(((
536 8031480
537 )))|(% style="width:133px" %)(((
538 2024/10/22 21:15:14
539 )))|(% style="width:103px" %)(((
540 2911
541 )))|(% style="width:131px" %)(((
542 tmp116_temp:28.85
543 )))
544 |(% style="width:89px" %)(((
545 8031490
546 )))|(% style="width:133px" %)(((
547 2024/10/22 21:35:14
548 )))|(% style="width:103px" %)(((
549 2921
550 )))|(% style="width:131px" %)(((
551 tmp116_temp:28.10
552 )))
553 |(% style="width:89px" %)(((
554 80314A0
555 )))|(% style="width:133px" %)(((
556 2024/10/22 21:55:14
557 )))|(% style="width:103px" %)(((
558 2923
559 )))|(% style="width:131px" %)(((
560 tmp116_temp:28.06
561 )))
562 |(% style="width:89px" %)(((
563 80314B0
564 )))|(% style="width:133px" %)(((
565 2024/10/22 22:15:14
566 )))|(% style="width:103px" %)(((
567 2924
568 )))|(% style="width:131px" %)(((
569 tmp116_temp:28.13
570 )))
571 |(% style="width:89px" %)(((
572 80314C0
573 )))|(% style="width:133px" %)(((
574 2024/10/22 22:35:14
575 )))|(% style="width:103px" %)(((
576 2925
577 )))|(% style="width:131px" %)(((
578 tmp116_temp:28.09
579 )))
580 |(% style="width:89px" %)(((
581 80314D0
582 )))|(% style="width:133px" %)(((
583 2024/10/22 22:55:14
584 )))|(% style="width:103px" %)(((
585 2924
586 )))|(% style="width:131px" %)(((
587 tmp116_temp:28.12
588 )))
589 |(% style="width:89px" %)(((
590 80314E0
591 )))|(% style="width:133px" %)(((
592 2024/10/22 23:15:14
593 )))|(% style="width:103px" %)(((
594 2924
595 )))|(% style="width:131px" %)(((
596 tmp116_temp:28.13
597 )))
598 |(% style="width:89px" %)(((
599 80314F0
600 )))|(% style="width:133px" %)(((
601 2024/10/22 23:35:14
602 )))|(% style="width:103px" %)(((
603 2924
604 )))|(% style="width:131px" %)(((
605 tmp116_temp:27.98
606 )))
607
608 If user sends below downlink command: (% style="background-color:yellow" %)31 67180C82 671836B2 05
609
610 Where : Start time: 67180C82 = time 24/10/24 20:35:14
611
612 Stop time:  671836B2 = time 24/10/24 23:35:14
613
614
615 **T68DL will uplink this payload.**
616
617 [[image:image-20241025162743-14.png]]
618
619
620 __**FFFFFFFF 0B4040 67180C82**__
621
622 __**FFFFFFFF0B424067181132FFFFFFFF0B4540671815E2FFFFFFFF0AFA4067181A92FFFFFFFF0AF64067181F42FFFFFFFF0AFD40671823F2FFFFFFFF0AF940671828A2FFFFFFFF0AFC4067182D52FFFFFFFF0AFD4067183202FFFFFFFF0AEE40671836B2**__
623
624 Where the first 11 bytes is for the first entry:
625
626 __**FFFFFFFF 0B40 40 67180C82**__
627
628 Bytes not used, so reserved: FFFFFFFF
629
630 Temp=0x0B40/100=28.8℃
631
632 PNACK status flag: ((bytes[6]>>7)&0x01) ? "True":"False" =(0x40>>7)&0x01=0
633
634 Unix time is 0x67180C82=1729629314s=24/10/22 20:35:14
635
636
637 == 2.7 Alarm Mode & Feature "Multi sampling, one uplink" ==
638
639
640 (((
641 when the device is in alarm mode, it checks the built-in sensor temperature for a short time. if the temperature exceeds the preconfigured range, it sends an uplink immediately.
642 )))
643
644 (((
645 (% style="color:red" %)**Note: alarm mode adds a little power consumption, and we recommend extending the normal read time when this feature is enabled.**
646
647
648 === 2.7.1 Threshold alarm with built-in temperature sensor (TMP116) ===
649
650
651 (% style="color:blue" %)**AT+WMOD=1,60,-10,20**
652
653 Explain:
654
655 * (% style="color:#037691" %)**parameter1: **(%%)Set Working Mode to **Mode 1,Threshold Alarm(Out of range alarm)**
656 * (% style="color:#037691" %)**parameter2:**(%%) Sampling Interval is **60**s.
657 * (% style="color:#037691" %)**parameter3 & parameter4: **(%%)Temperature alarm range is **-10** to 20°C(Set the temperature range value with a coefficient of 100)
658
659 (% style="color:#4f81bd" %)**Downlink Command:**
660
661 **Example: **A5013CFC1807D0
662
663 MOD=01
664
665 CITEMP=3C(S) =60(S)
666
667 TEMPlow=FC18 = -1000/100=-10(°C)
668
669 TEMPhigh=07D0=2000/100=20(°C)
670
671
672 === 2.7.2 Fluctuation alarm for TMP116 ===
673
674
675 Acquisition time: minimum 1s.
676
677 (% style="color:blue" %)**AT+WMOD=2,60,5**
678
679 Explain:
680
681 * (% style="color:#037691" %)**parameter1: **(%%)Set Working Mode to **Mode 2,Fluctuation alarm**
682 * (% style="color:#037691" %)**parameter2:**(%%) Sampling Interval is **60**s.
683 * (% style="color:#037691" %)**parameter3: **(%%)The temperature fluctuation is +-5 °C
684
685 (% style="color:#4f81bd" %)**Downlink Command**
686
687 **Example: **A5023C05
688
689 MOD=02
690
691 CITEMP=3C(S)=60(S)
692
693 temperature fluctuation=05(°C)
694
695
696 === 2.7.3 Sampling multiple times and uplink together ===
697
698
699 Internal TMP116 temperature alarm(Acquisition time: fixed at one minute)
700
701 (% style="color:blue" %)**AT+WMOD=3,60,20,-16,32,1**
702
703 Explain:
704
705 * (% style="color:#037691" %)**parameter1: **(%%)Set Working Mode to **Mode 3,Sampling multiple times and uplink together**
706 * (% style="color:#037691" %)**parameter2: **(%%)Sampling Interval is **60**s.(This parameter has no effect on internal sensors)
707 * (% style="color:#037691" %)**parameter3: **(%%)When there is **20** sampling dats, Device will send these data via one uplink. (max value is 60, means max 60 sampling in one uplink)
708 * (% style="color:#037691" %)**parameter4 & parameter5: **(%%)Temperature alarm range is **-16** to **32**°C,
709 * (% style="color:#037691" %)**parameter6:**(%%) 1 to enable temperature alarm, **0** to disable the temperature alarm. If alarm is enabled, a data will be sent immediately  if temperate exceeds the Alarm range.
710
711 (% style="color:#4f81bd" %)**Downlink Command:**
712
713 **Example: **A50301003C14FFF0002001
714
715 MOD=03
716
717 CITEMP=003C(S)=60(S)
718
719 Total number of acquisitions=14
720
721 TEMPlow=FFF0=-16(°C)
722
723 TEMPhigh=0020=20(°C)
724
725 ARTEMP=01
726
727
728 **Uplink payload( Fport=3)**
729
730 **Example: 0BEA**01**0992**//0A41//**09C4**
731
732 BatV=0BEA
733
734 TEMP=DS18B20
735
736 Temp1=0992  ~/~/ 24.50°C
737
738 Temp2=0A41  ~/~/ 26.25°C
739
740 Temp3=09C4  ~/~/ 25.00°C
741
742 (% style="color:red" %)**Note: This uplink will automatically select the appropriate DR according to the data length.**
743 )))
744
745
746 = 3. Configure T68DL via AT command or LoRaWAN downlink =
747
748
749 (((
750 Use can configure T68DL via AT Command or LoRaWAN Downlink.
751 )))
752
753 * (((
754 AT Command Connection:
755
756 [[image:image-20241029110142-1.jpeg||height="395" width="579"]]
757 )))
758
759 * (((
760 LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>doc:Main.WebHome]]
761 )))
762
763 (((
764 There are two kinds of commands to configure T68DL, they are:
765 )))
766
767 * (((
768 (% style="color:#4f81bd" %)**General Commands**.
769 )))
770
771 (((
772 These commands are to configure:
773 )))
774
775 1. (((
776 General system settings like: uplink interval.
777 )))
778 1. (((
779 LoRaWAN protocol & radio-related commands.
780 )))
781
782 (((
783 They are the same for all Dragino Devices which supports DLWS-005 LoRaWAN Stack(Note~*~*). These commands can be found on the wiki: [[End Device Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]
784 )))
785
786 * (((
787 (% style="color:#4f81bd" %)**Commands special design for T68DL**
788 )))
789
790 (((
791 These commands are only valid for T68DL, as below:
792 )))
793
794
795 == 3.1 Set Transmit Interval Time ==
796
797
798 Feature: Change LoRaWAN End Node Transmit Interval.
799
800
801 (% style="color:#4f81bd" %)**AT Command: AT+TDC**
802
803 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:501px" %)
804 |(% 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**
805 |(% style="width:155px" %)AT+TDC=?|(% style="width:162px" %)Show current transmit Interval|(% style="width:177px" %)30000 OK the interval is 30000ms = 30s
806 |(% style="width:155px" %)AT+TDC=60000|(% style="width:162px" %)Set Transmit Interval|(% style="width:177px" %)OK Set transmit interval to 60000ms = 60 seconds
807
808 (% style="color:#4f81bd" %)**Downlink Command: 0x01**
809
810 Format: Command Code (0x01) followed by 3 bytes time value.
811
812 If the downlink payload=0100003C, it means set the END Node's Transmit Interval to 0x00003C=60(S), while type code is 01.
813
814 * **Example 1**: Downlink Payload: 0100001E  ~/~/ Set Transmit Interval (TDC) = 30 seconds
815
816 * **Example 2**: Downlink Payload: 0100003C  ~/~/ Set Transmit Interval (TDC) = 60 seconds
817
818 == 3.2 Set Password ==
819
820
821 Feature: Set device password, max 9 digits
822
823 (% style="color:#4f81bd" %)**AT Command: AT+PWORD**
824
825 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:372px" %)
826 |(% style="background-color:#4f81bd; color:white; width:155px" %)**Command Example**|(% style="background-color:#4f81bd; color:white; width:128px" %)**Function**|(% style="background-color:#4f81bd; color:white; width:89px" %)**Response**
827 |(% style="width:155px" %)AT+PWORD=?|(% style="width:124px" %)Show password|(% style="width:86px" %)(((
828 123456
829
830 OK
831 )))
832 |(% style="width:155px" %)AT+PWORD=999999|(% style="width:124px" %)Set password|(% style="width:86px" %)OK
833
834 (% style="color:#4f81bd" %)**Downlink Command:**
835
836 No downlink command for this feature.
837
838
839 == 3.3 Quit AT Command ==
840
841
842 Feature: Quit AT Command mode, so user needs to input password again before use AT Commands.
843
844 (% style="color:#4f81bd" %)**AT Command: AT+DISAT**
845
846 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:433px" %)
847 |(% style="background-color:#4f81bd; color:white; width:155px" %)**Command Example**|(% style="background-color:#4f81bd; color:white; width:191px" %)**Function**|(% style="background-color:#4f81bd; color:white; width:87px" %)**Response**
848 |(% style="width:155px" %)AT+DISAT|(% style="width:191px" %)Quit AT Commands mode|(% style="width:86px" %)OK
849
850 (% style="color:#4f81bd" %)**Downlink Command:**
851
852 No downlink command for this feature.
853
854
855 == 3.4 Set to sleep mode ==
856
857
858 Feature: Set device to sleep mode
859
860 * **AT+Sleep=0**  : Normal working mode, device will sleep and use lower power when there is no LoRa message
861 * **AT+Sleep=1** :  Device is in deep sleep mode, no LoRa activation happen, used for storage or shipping.
862
863 (% style="color:#4f81bd" %)**AT Command: AT+SLEEP**
864
865 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:513px" %)
866 |(% style="background-color:#4f81bd; color:white; width:155px" %)**Command Example**|(% style="background-color:#4f81bd; color:white; width:140px" %)**Function**|(% style="background-color:#4f81bd; color:white; width:218px" %)**Response**
867 |(% style="width:155px" %)AT+SLEEP|(% style="width:139px" %)Set to sleep mode|(% style="width:213px" %)(((
868 Clear all stored sensor data…
869
870 OK
871 )))
872
873 (% style="color:#4f81bd" %)**Downlink Command:**
874
875 * There is no downlink command to set to Sleep mode.
876
877 == 3.5 Set system time ==
878
879
880 Feature: Set system time, unix format. [[See here for format detail.>>||anchor="H2.6.2UnixTimeStamp"]]
881
882 (% style="color:#4f81bd" %)**AT Command:**
883
884 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:506px" %)
885 |(% style="background-color:#4f81bd; color:white; width:188px" %)**Command Example**|(% style="background-color:#4f81bd; color:white; width:318px" %)**Function**
886 |(% style="width:154px" %)AT+TIMESTAMP=1611104352|(% style="width:285px" %)(((
887 OK
888
889 Set System time to 2021-01-20 00:59:12
890 )))
891
892 (% style="color:#4f81bd" %)**Downlink Command:**
893
894 0x306007806000  ~/~/  Set timestamp to 0x(6007806000),Same as AT+TIMESTAMP=1611104352
895
896
897 == 3.6 Set Time Sync Mode ==
898
899
900 (((
901 Feature: Enable/Disable Sync system time via LoRaWAN MAC Command (DeviceTimeReq), LoRaWAN server must support v1.0.3 protocol to reply this command.
902 )))
903
904 (((
905 SYNCMOD is set to 1 by default. If user want to set a different time from LoRaWAN server, user need to set this to 0.
906 )))
907
908 (% style="color:#4f81bd" %)**AT Command:**
909
910 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:475px" %)
911 |(% style="background-color:#4f81bd; color:white; width:158px" %)**Command Example**|(% style="background-color:#4f81bd; color:white; width:317px" %)**Function**
912 |(% style="width:156px" %)AT+SYNCMOD=1|(% style="width:315px" %)Enable Sync system time via LoRaWAN MAC Command (DeviceTimeReq)
913
914 (% style="color:#4f81bd" %)**Downlink Command:**
915
916 0x28 01  ~/~/  Same As AT+SYNCMOD=1
917 0x28 00  ~/~/  Same As AT+SYNCMOD=0
918
919
920 == 3.7 Set Time Sync Interval ==
921
922
923 Feature: Define System time sync interval. SYNCTDC default value: 10 days.
924
925 (% style="color:#4f81bd" %)**AT Command:**
926
927 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:472px" %)
928 |(% style="background-color:#4f81bd; color:white; width:158px" %)**Command Example**|(% style="background-color:#4f81bd; color:white; width:314px" %)**Function**
929 |(% style="width:156px" %)AT+SYNCTDC=0x0A |(% style="width:311px" %)Set SYNCTDC to 10 (0x0A), so the sync time is 10 days.
930
931 (% style="color:#4f81bd" %)**Downlink Command:**
932
933 **0x29 0A**  ~/~/ Same as AT+SYNCTDC=0x0A
934
935
936 == 3.8 Get data ==
937
938
939 Feature: Get the current sensor data.
940
941 (% style="color:#4f81bd" %)**AT Command:**
942
943 * **AT+GETSENSORVALUE=0**      ~/~/ The serial port gets the reading of the current sensor
944 * **AT+GETSENSORVALUE=1**      ~/~/ The serial port gets the current sensor reading and uploads it.
945
946 == 3.11 Print data entries base on page ==
947
948
949 Feature: Print the sector data from start page to stop page (max is 416 pages).
950
951 (% style="color:#4f81bd" %)**AT Command: AT+PDTA**
952
953 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %)
954 |(% style="background-color:#4f81bd; color:white; width:158px" %)**Command Example**|(% style="background-color:#4f81bd; color:white; width:352px" %)**Function**
955 |(% style="width:156px" %)(((
956 AT+PDTA=1,1
957 Print page 1 to 1
958 )))|(% style="width:311px" %)(((
959 Stop Tx events when read sensor data
960
961 8031000 1970/1/1 00:04:53 2 tmp116_temp:31.18
962
963 8031010 2024/10/21 02:23:09 2 tmp116_temp:31.24
964
965 8031020 2024/10/21 02:25:04 1 tmp116_temp:31.23
966
967 8031030 2024/10/21 02:25:28 2 tmp116_temp:31.24
968
969 8031040 2024/10/21 02:40:35 2 tmp116_temp:31.28
970
971 8031050 2024/10/21 03:00:29 2 tmp116_temp:31.65
972
973 8031060 2024/10/21 03:15:40 2 tmp116_temp:0.00
974
975 8031070 2024/10/21 03:17:22 2 tmp116_temp:0.00
976
977 Start Tx events
978
979
980 OK
981 )))
982
983 (% style="color:#4f81bd" %)**Downlink Command:**
984
985 No downlink commands for feature
986
987
988 == 3.12 Print last few data entries ==
989
990
991 Feature: Print the last few data entries
992
993 (% style="color:#4f81bd" %)**AT Command: AT+PLDTA**
994
995 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %)
996 |(% style="background-color:#4f81bd; color:white; width:158px" %)**Command Example**|(% style="background-color:#4f81bd; color:white; width:352px" %)**Function**
997 |(% style="width:156px" %)(((
998 AT+PLDTA=5
999 Print last 5 entries
1000 )))|(% style="width:311px" %)(((
1001 Stop Tx events when read sensor data
1002
1003 0001 2024/10/25 02:29:19 3273 tmp116_temp:28.16
1004
1005 0002 2024/10/25 02:31:19 3258 tmp116_temp:28.21
1006
1007 0003 2024/10/25 02:33:19 3255 tmp116_temp:28.26
1008
1009 0004 2024/10/25 02:35:19 3266 tmp116_temp:28.40
1010
1011 0005 1970/1/1 00:00:13 3255 tmp116_temp:25.74
1012
1013 Start Tx events
1014
1015 OK
1016 )))
1017
1018 (% style="color:#4f81bd" %)**Downlink Command:**
1019
1020 No downlink commands for feature
1021
1022
1023 == 3.13 Clear Flash Record ==
1024
1025
1026 Feature: Clear flash storage for data log feature.
1027
1028 (% style="color:#4f81bd" %)**AT Command: AT+CLRDTA**
1029
1030 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:503px" %)
1031 |(% style="background-color:#4f81bd; color:white; width:157px" %)**Command Example**|(% style="background-color:#4f81bd; color:white; width:137px" %)**Function**|(% style="background-color:#4f81bd; color:white; width:209px" %)**Response**
1032 |(% style="width:155px" %)AT+CLRDTA |(% style="width:134px" %)Clear date record|(% style="width:209px" %)(((
1033 Clear all stored sensor data…
1034
1035 OK
1036 )))
1037
1038 (% style="color:#4f81bd" %)**Downlink Command: 0xA3**
1039
1040 * Example: 0xA301  ~/~/  Same as AT+CLRDTA
1041
1042 == 3.14 Auto Send None-ACK messages ==
1043
1044
1045 Feature: T68DL will wait for ACK for each uplink, If T68DL doesn't get ACK from the IoT server, it will consider the message doesn't arrive server and store it. T68DL keeps sending messages in normal periodically. Once T68DL gets ACK from a server, it will consider the network is ok and start to send the not-arrive message.
1046
1047 (% style="color:#4f81bd" %)**AT Command: AT+PNACKMD**
1048
1049 The default factory setting is 0
1050
1051 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:367px" %)
1052 |=(% 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**
1053 |(% style="width:158px" %)AT+PNACKMD=1|(% style="width:118px" %)Poll None-ACK message|(% style="width:87px" %)OK
1054
1055 (% style="color:#4f81bd" %)**Downlink Command: 0x34**
1056
1057 * Example: 0x3401  ~/~/  Same as AT+PNACKMD=1
1058
1059 == 3.15 high datarate function ==
1060
1061
1062 Feature:  Enable or disable high datarate
1063
1064 (% style="color:#4f81bd" %)**AT Command: AT+HDR**
1065
1066 The default factory setting is 0
1067
1068 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:367px" %)
1069 |=(% 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**
1070 |(% style="width:158px" %)AT+HDR=1|(% style="width:118px" %)Enable high datarate|(% style="width:87px" %)OK
1071
1072 (% style="color:#4f81bd" %)**Downlink Command: 0xA1**
1073
1074 * Example: 0xA101  ~/~/  Same as AT+HDR=1
1075 * Example: 0xA100  ~/~/  Same as AT+HDR=0
1076
1077 == 3.16 Revised WMOD Command for Internal Sensor TMP116 Temperature Alarms ==
1078
1079
1080 Feature: Set internal and external temperature sensor alarms.
1081
1082 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:500px" %)
1083 |=(% style="width: 250px;background-color:#4F81BD;color:white" %)**Command Example**|=(% style="width: 200px;background-color:#4F81BD;color:white" %)**Function**|=(% style="width: 50px;background-color:#4F81BD;color:white" %)**Response**
1084 |(% style="width:268px" %)AT+WMOD=parameter1,parameter2,parameter3,parameter4|(% style="width:255px" %)Set internal and external temperature sensor alarms|(% style="width:181px" %)OK
1085
1086 (% style="color:#037691" %)**AT+WMOD=parameter1,parameter2,parameter3,parameter4**
1087
1088 (% style="color:#037691" %)**Parameter 1**(%%):  Alarm mode:
1089
1090 0): Cancel
1091
1092 1): Threshold alarm
1093
1094 2): Fluctuation alarm
1095
1096 3): Sampling multiple times and uplink together
1097
1098
1099 (% style="color:#037691" %)** Parameter 2**(%%):  Sampling time. Unit: seconds, up to 255 seconds.
1100
1101 (% style="color:red" %)**Note: When the collection time is less than 60 seconds and always exceeds the set alarm threshold, the sending interval will not be the collection time, but will be sent every 60 seconds.**
1102
1103
1104 (% style="color:#037691" %) **Parameter 3 and parameter 4:**
1105
1106 **1):  If Alarm Mode is set to 1:** Parameter 3 and parameter 4 are valid, as before, they represent low temperature and high temperature.
1107
1108 Such as AT+WMOD=1,60,45,105, it means high and low temperature alarm.
1109
1110
1111 **2):  If Alarm Mode is set to 2:** Parameter 3 is valid, which represents the difference between the currently collected temperature and the last uploaded temperature.
1112
1113 Such as AT+WMOD=2,10,2,it means that it is a fluctuation alarm.
1114
1115 If the difference between the current collected temperature and the last Uplin is ±2 degrees, the alarm will be issued.
1116
1117
1118 **3): If Alarm Mode is set to 3:**
1119
1120 * (% style="color:#037691" %)**parameter1: **(%%)Set Working Mode to **Mode 3**
1121 * (% style="color:#037691" %)**parameter2: **(%%)Sampling Interval is **60**s.
1122 * (% style="color:#037691" %)**parameter3: **(%%)When there is **20** sampling dats, Device will send these data via one uplink. (max value is 60, means max 60 sampling in one uplink)
1123 * (% style="color:#037691" %)**parameter4 & parameter5: **(%%)Temperature alarm range is **-16** to **32**°C,
1124 * (% style="color:#037691" %)**parameter6:**(%%) 1 to enable temperature alarm, **0** to disable the temperature alarm. If alarm is enabled, a data will be sent immediately  if temperate exceeds the Alarm range.
1125
1126 (% style="color:#4f81bd" %)**Downlink Command: 0xA5**
1127
1128 0xA5 00 ~-~- AT+WMOD=0.
1129
1130 0xA5 01 0A 11 94 29 04 ~-~- AT+WMOD=1,10,45,105  (AT+WMOD = second byte, third byte, fourth and fifth bytes divided by 100, sixth and seventh bytes divided by 100 )
1131
1132 0XA5 01 0A F9 C0 29 04 ~-~-AT+WMOD=1,10,-16,105(Need to convert -16 to -1600 for calculation,-1600(DEC)=FFFFFFFFFFFFF9C0(HEX)  FFFFFFFFFFFFF9C0(HEX) +10000(HEX)=F9C0(HEX))
1133
1134 0xA5 02 0A 02 ~-~- AT+WMOD=2,10,2  (AT+WMOD = second byte, third byte, fourth byte)
1135
1136 0xA5 03  00 3C 14 FF F0 00 20 01~-~-AT+WMOD=3,60,20,-16,32,1
1137
1138 0xA5 FF ~-~- After the device receives it, upload the current alarm configuration (FPORT=8). Such as 01 0A 11 94 29 04 or 02 0A 02.
1139
1140
1141 = 4. Battery =
1142
1143 == 4.1 Battery Type ==
1144
1145
1146 (((
1147 T68DL is equipped with a 2400mAH Li-MnO2 (CR17450) battery . The battery is an un-rechargeable battery with low discharge rate targeting for up to 8~~10 years use.
1148 )))
1149
1150 The minimum Working Voltage for the T68DL is about 2.5v. When battery is lower than 2.6v, it is time to change the battery.
1151 [[image:image-20241028180829-4.png||height="430" width="397"]]
1152
1153
1154 == 4.2 Power Consumption Analyze ==
1155
1156
1157 Dragino battery powered products are all run in Low Power mode. User can check the guideline from this link to calculate the estimate battery life:
1158
1159 [[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] .
1160
1161
1162 = 5. OTA Firmware update =
1163
1164
1165 **User can change firmware T68DL to:**
1166
1167 * Change Frequency band/ region.
1168 * Update with new features.
1169 * Fix bugs.
1170
1171 **Firmware and changelog can be downloaded from :** [[**Firmware download link**>>https://www.dropbox.com/scl/fo/ztlw35a9xbkomu71u31im/AHWC467h4jcFvS5-q1p7wkk/LoRaWAN%20End%20Node/T68DL?rlkey=ojjcsw927eaow01dgooldq3nu&subfolder_nav_tracking=1&dl=0]]
1172
1173 **Methods to Update Firmware:**
1174
1175 * (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/]]**
1176 * Update through UART TTL interface: **[[Instruction>>url:http://wiki.dragino.com/xwiki/bin/view/Main/UART%20Access%20for%20LoRa%20ST%20v4%20base%20model/#H2.7A0A0UARTConnectionforLWL04motherboard]]**.
1177
1178 = 6. FAQ =
1179
1180 == 6.1 Why can't I see the datalog information ==
1181
1182
1183 ~1. The time is not aligned, and the correct query command is not used.
1184
1185 2. Decoder error, did not parse the datalog data, the data was filtered.
1186
1187
1188 = 7. Order Info =
1189
1190
1191 Part Number: (% style="color:#4f81bd" %)** T68DL-XX**
1192
1193 (% style="color:#4f81bd" %)**XX **(%%): The default frequency band
1194
1195 * (% style="color:#4f81bd" %)** **(% _mstmutation="1" style="color:red" %)**AS923**(%%): LoRaWAN AS923 band
1196 * (% style="color:#4f81bd" %)** **(% _mstmutation="1" style="color:red" %)**AU915**(%%): LoRaWAN AU915 band
1197 * (% style="color:#4f81bd" %)** **(% _mstmutation="1" style="color:red" %)**EU433**(%%): LoRaWAN EU433 band
1198 * (% style="color:#4f81bd" %)** **(% _mstmutation="1" style="color:red" %)**EU868**(%%): LoRaWAN EU868 band
1199 * (% style="color:#4f81bd" %)** **(% _mstmutation="1" style="color:red" %)**KR920**(%%): LoRaWAN KR920 band
1200 * (% style="color:#4f81bd" %)** **(% _mstmutation="1" style="color:red" %)**US915**(%%): LoRaWAN US915 band
1201 * (% style="color:#4f81bd" %)** **(% _mstmutation="1" style="color:red" %)**IN865**(%%): LoRaWAN IN865 band
1202 * (% style="color:#4f81bd" %)** **(% _mstmutation="1" style="color:red" %)**CN470**(%%): LoRaWAN CN470 band
1203
1204 = 8. Packing Info =
1205
1206
1207 **Package Includes**:
1208
1209 * T68DL Temperature Sensor x 1
1210
1211 = 9. Support =
1212
1213 * 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.
1214
1215 * Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[Support@dragino.cc>>mailto:Support@dragino.cc]].
Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0