Wiki source code of DMT01

Version 59.7 by Mengting Qiu on 2025/08/05 10:57

version	line-number	content
1.1	1
	2
5.1	3	[[image:1753592237986-145.png\|\|height="354" width="118"]] [[image:1753592287802-550.png\|\|height="237" width="341"]]
1.1	4
	5
	6	Table of Contents:
	7
	8	{{toc/}}
	9
	10	(% aria-label="macro:toc widget" contenteditable="false" role="region" tabindex="-1" %)
	11	(((
	12	(% 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"]]
	13	)))
	14
	15
	16
	17	= 1. Introduction =
	18
6.1	19	== 1.1 What is DMT01 Wireless Meat Thermometer ==
1.1	20
	21
6.1	22	The DMT01 is a (% style="color:blue" %)professional-grade wireless meat thermometer(%%) engineered for accurate, real-time temperature monitoring in commercial cooking environments. Ideal for restaurants, central kitchens, catering services, and food processing facilities, the DMT01 ensures consistent results across various cooking methods—including grilling, smoking, roasting, deep-frying, sous vide, baking, and more. Its precise monitoring helps improve cooking efficiency, ensure food safety, and meet HACCP compliance standards.
1.1	23
6.1	24	The system consists of two components:
	25	- (% style="color:blue" %)Food-grade BLE High-Temperature Probe(%%) – A durable, high-heat resistant probe that measures internal food temperature during cooking.
	26	- (% style="color:blue" %)Charging Base with BLE & LoRaWAN Forwarder(%%) – This base not only charges the probe but also acts as a communication bridge. It receives temperature data from the BLE probe and transmits it via the LoRaWAN long-range wireless protocol to your IoT platform or monitoring system.
1.1	27
12.1	28	With its dual wireless support ((% style="color:blue" %)BLE for close-range/small design(%%) and (% style="color:blue" %)LoRaWAN for long-range data transmission(%%)), the DMT01 is ideal for both home cooking enthusiasts and commercial kitchen environments seeking smart, connected temperature monitoring.
1.1	29
	30	== 1.2 Features ==
6.2	31
6.1	32	* Wireless Meat Thermometer – Designed for accurate and reliable cooking temperature monitoring
	33	* Food-Grade Probe – Safe for food contact and dishwasher-compatible for easy cleaning
	34	* BLE 5.1 Broadcasting – Supports real-time local data transmission via Bluetooth Low Energy
	35	* LoRaWAN Connectivity – Enables long-range, low-power data transmission to IoT platforms
	36	* Smart Uplink Triggering – Supports periodic data reporting and real-time alerts on temperature thresholds
1.1	37
	38	(% style="display:none" %)
	39
	40	== 1.3 Specification ==
	41
	42
	43	(% style="color:blue" %)Common DC Characteristics:
	44
13.1	45	* Supply Voltage: +5v via USB Type-C
	46	* Operating Temperature:
1.1	47
6.2	48	(% style="color:blue" %)Food Probe Spec:
1.1	49
19.2	50	* Length: 126mm
	51	* Diameter: 6mm
19.3	52	* Food temperature: -30 ~~110 °C, Accuracy: ±0.5°C
	53	* Ambient temperature: 0 ~~380°C, Accuracy: ±5°C
19.2	54	* Wireless: BLE 5.1
19.3	55	* Distance: ≥ 30m
	56	* Battery: 4mAh
19.18	57	* Recharge time: ＜ 2 hours
19.12	58	* Battery Duration: ＞30 hours
19.6	59	* IP Rate: IP67, Dish Washer proof
1.1	60
	61
	62
19.12	63	(% style="color:blue" %)Charger Spec:
1.1	64
19.16	65	* BLE v5.1 + LoRaWAN
19.18	66	* Power Input: USB Type-C, +5v
	67	* Battery: Li-ion , 3000mAh
19.19	68	* Recharge time: ＜ 2 hours
1.1	69
17.27	70
17.26	71
20.2	72
1.1	73	== 1.4 Applications ==
	74
6.2	75	* Commercial Kitchen
7.1	76	* Restaurant
	77	* Catering
	78	* Food Processing
	79	* Central Kitchen
	80	* Cloud Kitchen
	81	* HACCP Monitoring
	82	* Food Safety
	83	* Meat Factory
	84	* Industrial Cooking
1.1	85
16.1	86	== 1.5 Product Apperance ==
1.1	87
14.33	88	(% class="wikigeneratedid" %)
	89	[[image:1753594523550-152.png\|\|height="462" width="416"]]
1.1	90
14.31	91
14.33	92	== 1.6 Working mode ==
14.31	93
14.33	94
20.4	95	(% 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.
1.1	96
20.4	97	(% 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.
1.1	98
	99
14.33	100	== 1.7 LED Status ==
1.1	101
	102
20.5	103	The DMT01 uses a dual-color LED to indicate system status:
	104
23.2	105	(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:503px" %)
23.6	106	\|(% style="background-color:#4f81bd; color:white; width:196px" %)LED Behavior\|(% style="background-color:#4f81bd; color:white; width:305px" %)Description
	107	\|(% style="width:196px" %)Green breathing effect\|(% style="width:305px" %)Probe is inserted and charging
23.5	108	(LED turns off immediately when probe is removed)
23.6	109	\|(% style="width:196px" %)Red solid (5 seconds)\|(% style="width:305px" %)Mode switched successfully (after 1-3s button press)
	110	\|(% style="width:196px" %)Red blinking (15 seconds)\|(% style="width:305px" %)Charging base low battery (<15% capacity)
26.2	111	\|(% style="width:196px" %)Red/Green alternating blink (3 seconds)\|(% style="width:305px" %)Device reset in progress (after 3s long press)
23.7	112	\|(% style="width:196px" %)Single green blink\|(% style="width:305px" %)BLE connection established between probe and base
20.5	113
	114
	115
14.33	116	== 1.8 Button Function ==
1.1	117
29.2	118	[[image:1754120439617-600.jpg\|\|height="404" width="404"]]
1.1	119
27.1	120	(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:536.222px" %)
	121	\|=(% style="width: 147px; background-color: rgb(79, 129, 189); color: white;" %)Behavior on ACT\|=(% style="width: 130px; background-color: rgb(79, 129, 189); color: white;" %)Function\|=(% style="width: 254px; background-color: rgb(79, 129, 189); color: white;" %)Action
	122	\|(% style="background-color:#f2f2f2; width:147px" %) [[image:1754045287749-587.png]]>3s\|(% style="background-color:#f2f2f2; width:130px" %)Active Device\|(% style="background-color:#f2f2f2; width:254px" %)(((
26.4	123	Red/Green alternating blink (3 seconds), DMT01 will enter working mode and start to JOIN LoRaWAN network.
26.5	124	When the probe is placed in the repeater to charge, the green LED above the relay box will have a breathing effect. When the probe is taken out, the LED light will go out.
26.2	125	)))
27.1	126	\|(% style="background-color:#f2f2f2; width:147px" %)[[image:1754045287749-587.png]] 1~~3s\|(% style="background-color:#f2f2f2; width:130px" %)Switch working mode\|(% style="background-color:#f2f2f2; width:254px" %)(((
	127	There are three operating modes:
26.7	128	Default LoRaWAN and Bluetooth broadcast mode,
27.1	129	Separate LoRaWAN mode
	130
	131	Separate Bluetooth broadcast mode.
26.7	132	(% style="color:red" %)Note:(%%) To switch modes, remove the probe and press the button; otherwise, the mode will not switch.
27.1	133	)))
26.2	134
	135
	136
16.1	137	== 1.9 Power on device and Recharge Probe ==
14.31	138
14.33	139
29.3	140
	141
9.1	142	= 2. Use DMT01 =
1.1	143
14.2	144	== 2.1 How it works ==
1.1	145
	146	(((
	147	(((
	148
14.2	149
18.2	150	DMT01 Include two parts,
	151
	152	1. The food grade probe : used to measure the meat temperature
18.7	153	1. The Charger which is also a LoRaWAN End node: used to connect the probe via BLE and get the temperature and send via LoRaWAN to IoT server.
18.2	154
18.8	155
	156
	157	Consider the BLE coverage , there is two cases:
	158
19.2	159	=== Connection Mode: Probe is near by the Charge, within BLE range ===
18.9	160
	161	Probe will establish connection to the charge via BLE. and the data flow is as below.
1.1	162	)))
	163
14.7	164	[[image:1753622303925-386.png]]
1.1	165
14.2	166
19.2	167	=== Broadcast Mode: Probe is far away from the Charge, out of BLE range ===
18.10	168
18.14	169	Probe will auto swtich to BLE broadcast mode and broadcast the data via BLE. Any BLE Scaner can pick up the signal and send to IoT server.
18.10	170
18.14	171	For example:
18.10	172
18.14	173	1) User can use BH01 BLE to LoRaWAN converter to pick up the BLE signal to IoT Server
	174
18.22	175	2) User can use Mobile phone to get the broadcast signal and further process.
18.14	176
	177
14.8	178	== 2.2 Activate Device ==
	179
	180	To use DMT01 send data to LoRaWAN network, user need to:
	181
	182	1. Input the OTAA Keys in LoRaWAN Network Server
14.10	183	1. Make sure there is LoraWAN network
14.13	184	1. Press the button on the DMT01 for more than 3 seconds, DMT01 will start to connect to LoRaWAN network
14.14	185
	186
	187
14.27	188	After the DMT01 Join LoRaWAN network, once user take out the probe, the probe will start to measure temperature and user will be to see the data on the server.
1.1	189	)))
	190
	191
31.1	192	== 2.3 Quick guide to connect to LoRaWAN server (OTAA) ==
1.1	193
	194
31.1	195	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.
	196
	197	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.
	198
34.2	199	[[image:1754298519453-808.jpg\|\|height="211" width="951"]]
31.1	200
	201
31.3	202	(% style="color:blue" %)Step 1:(%%) Create a device in TTN with the OTAA keys from DMT01.
31.1	203
31.3	204	Each DMT01 is shipped with a sticker with the default device EUI as below:
31.1	205
34.2	206	[[image:1754298588891-599.jpeg]](% style="display:none" %)
31.1	207
	208	You can enter this key in the LoRaWAN Server portal. Below is TTN screen shot:(% style="display:none" %)
	209
	210	(% style="color:blue" %)Create the application.
	211
39.2	212	[[image:1754298671647-982.png]]
31.1	213
39.2	214	[[image:1754298685721-106.png]]
31.1	215
	216	(% style="color:blue" %)Add devices to the created Application.
	217
39.2	218	[[image:1754298708270-733.png]]
31.1	219
39.2	220	[[image:1754298719336-394.png]]
31.1	221
	222	(% style="color:blue" %)Enter end device specifics manually.
	223
40.2	224	[[image:1754298737089-161.png]]
31.1	225
	226	(% style="color:blue" %)Add DevEUI and AppKey.
	227
	228	(% style="color:blue" %)Customize a platform ID for the device.
	229
40.2	230	[[image:1754298751553-229.png]]
31.1	231
	232
	233	(% style="color:blue" %)Step 2: (%%)Add decoder
	234
	235	In TTN, user can add a custom payload so it shows friendly reading.
	236
	237	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/]]
	238
	239	Below is TTN screen shot:
	240
41.2	241	[[image:1754298862776-783.png\|\|height="609" width="1426"]]
31.1	242
44.1	243	[[image:1754299076396-787.png]]
31.1	244
32.2	245	(% style="color:blue" %)Step 3:(%%) Activate on DMT01
31.1	246
32.2	247	Press the button for 3 seconds to activate the DMT01.
31.1	248
	249	After join success, it will start to upload messages to TTN and you can see the messages in the panel.
	250
41.2	251	[[image:1754298481895-828.png\|\|height="441" width="1387"]]
31.1	252
	253
	254
30.2	255	== 2.3 LoRaWAN Payload ==
1.1	256
45.2	257	=== 2.3.1 Device Status, FPORT~=5 ===
30.2	258
	259
46.1	260	Users can use the downlink command(0x26 01) to ask DMT01 to send device configure detail, include device configure status. DMT01 will uplink a payload via FPort=5 to server.
45.2	261
	262	The Payload format is as below.
	263
	264	(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %)
	265	\|(% colspan="6" style="background-color:#4f81bd; color:white" %)Device Status (FPORT=5)
45.3	266	\|(% style="width:103px" %)Size (bytes)\|(% style="width:91px" %)1\|(% style="width:98px" %)2\|(% style="width:103px" %)1\|(% style="width:112px" %)1
	267	\|(% style="width:103px" %)Value\|(% style="width:91px" %)Sensor Model\|(% style="width:98px" %)Firmware Version\|(% style="width:103px" %)Frequency Band\|(% style="width:112px" %)Sub-band
45.2	268
	269	Example in TTN:
	270
	271	[[image:1754299464263-797.png\|\|height="274" width="1384"]]
	272
	273
	274	(% style="color:#037691" %)Sensor Model(%%): For DMT01, this value is 0x4B
	275
45.3	276	(% style="color:#037691" %)Firmware Version(%%): 0x0101, Means: v1.0.1 version
45.2	277
	278	(% style="color:#037691" %)Frequency Band(%%):
	279
	280	0x01: EU868
	281
	282	0x02: US915
	283
	284	0x03: IN865
	285
	286	0x04: AU915
	287
	288	0x05: KZ865
	289
	290	0x06: RU864
	291
	292	0x07: AS923
	293
	294	0x08: AS923-1
	295
	296	0x09: AS923-2
	297
	298	0x0a: AS923-3
	299
	300	0x0b: CN470
	301
	302	0x0c: EU433
	303
	304	0x0d: KR920
	305
	306	0x0e: MA869
	307
	308	(% style="color:#037691" %)Sub-Band(%%):
	309
	310	AU915 and US915:value 0x00 ~~ 0x08
	311
	312	CN470: value 0x0B ~~ 0x0C
	313
	314	Other Bands: Always 0x00
	315
	316
46.2	317	=== 2.3.2 Sensor Data. FPORT~=2 ===
45.2	318
46.2	319
	320	Sensor Data is uplink via FPORT=2
	321
47.2	322	(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %)
46.2	323	\|=(% style="width: 60px;background-color:#4F81BD;color:white" %)(((
47.2	324	Size(bytes)
48.7	325	)))\|=(% style="width: 40px;background-color:#4F81BD;color:white" %)4\|=(% style="width: 90px;background-color:#4F81BD;color:white" %)1\|=(% style="width: 150px; background-color: #4F81BD;color:white" %)6\|=(% style="width: 80px; background-color: #4F81BD;color:white" %)1\|=(% style="width: 80px; background-color: #4F81BD;color:white" %)1\|=(% style="width: 80px; background-color: #4F81BD;color:white" %)2\|=(% style="width: 80px; background-color: #4F81BD;color:white" %)2
46.2	326	\|(% style="width:99px" %)Value\|(% style="width:69px" %)(((
47.20	327	Timestamp
47.19	328
	329
	330	)))\|(% style="width:130px" %)DevMode\|(% style="width:194px" %)MACaddr\|(% style="width:106px" %)ProbeBat\|(% style="width:97px" %)(((
48.7	331	BoxBat
	332	)))\|(% style="width:97px" %)Food temperature\|(% style="width:97px" %)Ambient temperature
47.19	333
47.3	334	[[image:1754300947187-648.png\|\|height="641" width="1351"]]
46.2	335
	336
48.4	337
50.1	338	==== (% style="color:#4472c4" %)Unit timestamp(%%) ====
46.2	339
48.6	340	Unit TimeStamp Example: 689085D7(H) = 1754301911(D)
46.2	341
48.2	342	Put the decimal value into this link([[https:~~/~~/www.epochconverter.com)>>https://www.epochconverter.com]])to get the time.
46.2	343
	344
50.1	345	==== (% style="color:#4472c4" %)DevMode(%%) ====
46.2	346
49.2	347	Example：
46.2	348
49.1	349	If payload is 0x01: BLE_LoRa
46.2	350
49.1	351	If payload is 0x02: LoRa
48.8	352
49.1	353	If payload is 0x03: BLE
48.10	354
	355
50.1	356	==== (% style="color:#4472c4" %)MACaddr(%%) ====
46.2	357
49.2	358	Example:
46.2	359
49.1	360	If the payload is C12309250F1A, the MACaddr is C12309250F1A
46.2	361
48.11	362
50.1	363	==== (% style="color:#4472c4" %)ProbeBat(%%) ====
46.2	364
	365	Example:
	366
49.2	367	If payload is 0x64 = 100%
46.2	368
	369
50.1	370	==== (% style="color:#4472c4" %)BoxBat(%%) ====
48.3	371
49.2	372	Example:
48.3	373
49.2	374	If payload is 0x46 = 70%
48.3	375
	376
50.1	377	==== (% style="color:#4472c4" %)Food temperature(%%) ====
46.2	378
50.1	379	Because the food temperature data is a little-endian sequence, the order of the front and back bytes needs to be swapped during decoding.
	380
47.9	381	Example:
47.8	382
50.1	383	If payload is: D300H = 00D3H, temp = 00D3H /10 = 21.1 degree
47.8	384
50.1	385	If payload is: 3FFFH = FF3F , temp = (FF3FH - 65536)/10 = -19.3 degrees.
47.8	386
47.9	387
50.1	388	==== (% style="color:#4472c4" %)Ambient temperature(%%) ====
47.9	389
50.1	390	Because the food temperature data is a little-endian sequence, the order of the front and back bytes needs to be swapped during decoding.
47.9	391
47.11	392	Example:
47.9	393
50.1	394	If payload is: D200H = 00D2H, temp = 00D2H /10 = 21.0 degree
47.9	395
50.1	396	If payload is: 3FFFH = FF3F , temp = (FF3FH - 65536)/10 = -19.3 degrees.
47.11	397
	398
	399
30.2	400	== 2.4 Bluetoothe Broadcast Payload ==
	401
51.2	402	Scan and obtain DMT01 device broadcast data through a third-party mobile phone app (such as nRF Connect)
30.2	403
50.1	404	Example：
30.2	405
50.2	406	Note: The following data is obtained through the nRF Connect tool.
30.2	407
52.3	408	[[image:1754305290140-806.jpg\|\|height="680" width="432"]]
50.1	409
	410
53.2	411	If the scanned payload is 0x0201060609444D5430310EFF 01C12309250F1AD100CD006446 0512E001E001
50.1	412
52.6	413	(% style="color:red" %)Note(%%)：
50.1	414
52.6	415	* The first 12 bytes in the payload are the Bluetooth packet header data and do not need to be decoded.
	416	* The last 6 bytes in the payload are the Bluetooth packet trailer data and do not need to be decoded.
50.2	417
52.7	418	So the payload is：01C12309250F1AD100CD006446
52.4	419
	420
53.4	421	==== (% style="color:#4472c4" %)Bluetooth data packet frame header(%%) ====
53.3	422
53.6	423	Example: 0x0201060609444D5430310EFF
53.3	424
53.4	425
53.2	426	==== (% style="color:#4472c4" %)DevMode(%%) ====
52.5	427
53.2	428	Example：
52.6	429
53.2	430	If payload is 0x01: BLE_LoRa
52.6	431
53.2	432	If payload is 0x02: LoRa
	433
	434	If payload is 0x03: BLE
	435
	436
	437	==== (% style="color:#4472c4" %)MACaddr(%%) ====
	438
	439	Example:
	440
	441	If the payload is C12309250F1A, the MACaddr is C12309250F1A
	442
	443
	444	==== (% style="color:#4472c4" %)ProbeBat(%%) ====
	445
	446	Example:
	447
	448	If payload is 0x64 = 100%
	449
	450
	451	==== (% style="color:#4472c4" %)BoxBat(%%) ====
	452
	453	Example:
	454
	455	If payload is 0x46 = 70%
	456
	457
	458	==== (% style="color:#4472c4" %)Food temperature(%%) ====
	459
	460	Because the food temperature data is a little-endian sequence, the order of the front and back bytes needs to be swapped during decoding.
	461
	462	Example:
	463
	464	If payload is: D300H = 00D3H, temp = 00D3H /10 = 21.1 degree
	465
	466	If payload is: 3FFFH = FF3F , temp = (FF3FH - 65536)/10 = -19.3 degrees.
	467
	468
	469	==== (% style="color:#4472c4" %)Ambient temperature(%%) ====
	470
	471	Because the food temperature data is a little-endian sequence, the order of the front and back bytes needs to be swapped during decoding.
	472
	473	Example:
	474
	475	If payload is: D200H = 00D2H, temp = 00D2H /10 = 21.0 degree
	476
	477	If payload is: 3FFFH = FF3F , temp = (FF3FH - 65536)/10 = -19.3 degrees.
	478
	479
53.7	480	==== (% style="color:#4472c4" %)Bluetooth data packet frame tail(%%) ====
53.2	481
53.8	482	Example: 0x0512E001E001
53.6	483
53.7	484
	485
57.2	486	== 2.5 Datalog Feature ==
	487
	488
	489	Datalog Feature is to ensure IoT Server can get all sampling data from Sensor even if the LoRaWAN network is down. For each sampling, DMT01 will store the reading for future retrieving purposes.
	490
	491
	492	=== 2.5.1 How datalog works ===
	493
	494
	495	DMT01 will wait for ACK for every uplink, when there is no LoRaWAN network,DMT01 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.
	496
	497	* (((
	498	a) DMT01 will do an ACK check for data records sending to make sure every data arrive server.
	499	)))
	500	* (((
	501	b) DMT01 will send data in CONFIRMED Mode, but DMT01 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 DMT01 gets a ACK, DMT01 will consider there is a network connection and resend all NONE-ACK messages.
	502
	503
	504	)))
	505
	506	=== 2.5.2 Enable Datalog ===
	507
	508	Using the platform downlink 07 01, you can enable the device to automatically send non-ACK messages. Once enabled, the LC01 will wait for an acknowledgment (ACK) for every uplink. If there is no LoRaWAN network available, DMT01 will mark these records as non-ACK messages, store the sensor data, and continue checking for network availability (at 10-second intervals) to resend all stored messages once the network is restored.
	509
	510	* (((
	511	a) DMT01 performs an ACK check for each data record to ensure it successfully reaches the server.
	512	)))
	513	* (((
	514	b) When automatic sending of non-ACK messages is enabled, the DMT01 transmits data in CONFIRMED mode. If an ACK is not received, it does not resend the packet; instead, it marks it as a non-ACK message. During subsequent uplinks, if the DMT01 receives an ACK, it considers the network restored and will resend all stored non-ACK messages.
	515	)))
	516
	517
	518
	519	=== 2.5.3 Unix TimeStamp ===
	520
	521
	522	DMT01 uses Unix TimeStamp format based on
	523
	524	[[image:1754354802681-163.jpeg]]
	525
	526	User can get this time from link: [[https:~~/~~/www.epochconverter.com/>>url:https://www.epochconverter.com/]] :
	527
	528	Below is the converter example
	529
	530	[[image:1754354818964-624.jpeg]]
	531
	532
	533
	534	=== 2.5.4 Set Device Time ===
	535
	536
	537	You need to run downlink command 28 01 to enable time synchronization.
	538
	539	Once the LC01 joins the LoRaWAN network, it will send the MAC command DeviceTimeReq, and the server will reply with DeviceTimeAns to provide the current time to the LC01. If the LC01 fails to receive the time from the server, it will use its internal time and wait for the next time request. //(By default, this occurs once every 10 days.)//
	540
	541	{{info}}
	542	The LoRaWAN server must support LoRaWAN v1.0.3 (MAC v1.0.3) or higher to use this MAC command feature. ChirpStack, The Things Stack v3, and Loriot support it, but The Things Stack v2 does not. If the server does not support this command, it will discard the uplink packet containing it. As a result, the user will lose the time request packet when the automatic time synchronization function is enabled on TTN v2.
	543	{{/info}}
	544
	545	(% style="color:#4f81bd" %)Downlink Command: 0x28
	546
	547	* Example: 0x28 01 ~/~/ Automatic time synchronization Enabled
	548	* Example: 0x28 00 ~/~/ Automatic time synchronization Disable.
	549
58.1	550
	551
57.2	552	=== 2.5.5 Datalog Uplink payload (FPORT~=3) ===
	553
	554
	555	The Datalog uplinks will use below payload format.
	556
	557	Retrieval data payload:
	558
59.2	559	(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %)
57.2	560	\|=(% style="width: 60px;background-color:#4F81BD;color:white" %)(((
	561	Size(bytes)
59.7	562	)))\|=(% style="width: 40px;background-color:#4F81BD;color:white" %)4\|=(% style="width: 90px;background-color:#4F81BD;color:white" %)1\|=(% style="width: 150px; background-color: #4F81BD;color:white" %)6\|=(% style="width: 80px; background-color: #4F81BD;color:white" %)1\|=(% style="width: 80px; background-color: #4F81BD;color:white" %)1\|=(% style="width: 80px; background-color: #4F81BD;color:white" %)1\|=(% style="width: 80px; background-color: #4F81BD;color:white" %)2\|=(% style="width: 80px; background-color: #4F81BD;color:white" %)2
58.2	563	\|(% style="width:99px" %)Value\|(% style="width:69px" %)(((
	564	Timestamp
57.2	565
58.2	566
	567	)))\|(% style="width:130px" %)DevMode\|(% style="width:194px" %)MACaddr\|(% style="width:106px" %)ProbeBat\|(% style="width:97px" %)(((
	568	BoxBat
59.7	569	)))\|(% style="width:97px" %)Message Type\|(% style="width:97px" %)Food temperature\|(% style="width:97px" %)Ambient temperature
58.2	570
57.2	571	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 feature)
	572
	573	Poll Message Flag: 1: This message is a poll message reply.
	574
	575	* Poll Message Flag is set to 1.
	576
	577	* Each data entry is 11 bytes, to save airtime and battery, devices will send max bytes according to the current DR and Frequency bands.
	578
	579	For example, in US915 band, the max payload for different DR is:
	580
	581	a) DR0: max is 11 bytes so one entry of data
	582
	583	b) DR1: max is 53 bytes so devices will upload 4 entries of data (total 44 bytes)
	584
	585	c) DR2: total payload includes 11 entries of data
	586
	587	d) DR3: total payload includes 22 entries of data.
	588
	589	If devise doesn't have any data in the polling time. Device will uplink 11 bytes of 0
	590
	591	Example:
	592
	593	If DMT01 has below data inside Flash:
	594
	595	[[image:image-20230524114654-2.png]]
	596
	597
	598	If user sends below downlink command: 31646D84E1646D856C05
	599
	600	Where : Start time: 646D84E1 = time 23/5/24 03:30:41
	601
	602	Stop time: 646D856C= time 23/5/24 03:33:00
	603
	604
	605	DMT01 will uplink this payload.
	606
	607	[[image:image-20230524114826-3.png\|\|height="448" width="1244"]]
	608
	609	(((
	610	00 00 02 36 01 10 40 64 6D 84 E1 00 00 02 37 01 10 40 64 6D 84 F8 00 00 02 37 01 0F 40 64 6D 85 04 00 00 02 3A 01 0F 40 64 6D 85 18 00 00 02 3C 01 0F 40 64 6D 85 36 00 00 02 3D 01 0E 40 64 6D 85 3F 00 00 02 3F 01 0E 40 64 6D 85 60 00 00 02 40 01 0E 40 64 6D 85 6A
	611	)))
	612
	613	(((
	614	Where the first 11 bytes is for the first entry:
	615	)))
	616
	617	(((
	618	00 00 02 36 01 10 40 64 6D 84 E1
	619	)))
	620
	621	(((
	622	Hum=0x0236/10=56.6
	623	)))
	624
	625	(((
	626	Temp=0x0110/10=27.2
	627	)))
	628
	629	(((
	630	poll message flag & Alarm Flag & Level of PA8=0x40,means reply data,sampling uplink message,the PA8 is low level.
	631	)))
	632
	633	(((
	634	Unix time is 0x646D84E1=1684899041s=23/5/24 03:30:41
	635	)))
	636
	637
	638
	639
14.31	640	= 3. Configure DMT01 ~-~- 需要修改 =
1.1	641
	642	== 3.1 Configure Methods ==
	643
17.1	644	User can use LoRaWAN downlink command to configure the DMT01
1.1	645
	646	(((
	647	(((
17.23	648	== 3.2 Downlink Commands Set ==
1.1	649
	650
	651	(% class="box infomessage" %)
	652	(((
	653	To be updated...
	654	)))
	655	)))
	656	)))
	657
	658
17.16	659	= 4. Firmware update =
1.1	660
	661
17.7	662	Firmware download link (% class="mark" %)(To be updated...)
	663
17.6	664	User can upgrade the firmware for DMT01 charger. The charger include two piece of software:
1.1	665
17.8	666	* For LoRa part: OTA firmware update via LoRa:.
17.6	667
17.9	668	* For BLE and controller part.
1.1	669
17.17	670	== 4.1 Update LoRa software ==
17.10	671
17.13	672
17.17	673	== 4.2 Update BLE software ==
17.14	674
1.1	675
	676	(((
	677
	678	)))
	679
17.17	680	= 5. FAQ =
1.1	681
	682
	683
17.18	684	= 6. Order Info =
1.1	685
	686
7.2	687	Part Number: (% style="color:blue" %)DMT01-XX
1.1	688
	689	(% style="color:red" %)XX:
	690
17.19	691	* EU433: Frequency bands EU433
17.20	692	* EU868: Frequency bands EU868
	693	* KR920: Frequency bands KR920
17.21	694	* CN470: Frequency bands CN470
	695	* AS923: Frequency bands AS923
17.22	696	* AU915: Frequency bands AU915
17.23	697	* US915: Frequency bands US915
	698	* IN865: Frequency bands IN865
	699	* CN779: Frequency bands CN779
1.1	700
17.18	701	= 7. Packing Info =
1.1	702
	703
	704	(% style="color:#037691" %)Package Includes:
	705
10.1	706	* DMT01 - Digital Meat Thermoneter x 1
1.1	707
	708	(% style="color:#037691" %)Dimension and weight:
	709
	710	* Device Size: cm
	711	* Device Weight: g
	712	* Package Size / pcs : cm
	713	* Weight / pcs : g
	714
17.19	715	= 8. Support =
1.1	716
	717
	718	* 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.
	719	* 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]].

Wiki source code of DMT01

Applications