Changes for page DMT01

Last modified by Xiaoling on 2025/08/16 17:21

From 48.11 to 48.12 From 57.2 to 58.1

From version 48.12

edited by Mengting Qiu
on 2025/08/04 18:12

Change comment: There is no comment for this version

To version 57.2

edited by Mengting Qiu
on 2025/08/05 08:48

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (1 modified, 0 added, 0 removed)
Attachments (0 modified, 4 added, 0 removed)

Details

Page properties

Content

@@ -189,21 +189,6 @@
  )))
--== 2.2  How it works? ==
--
--(((
--(((
--
--)))
--
--The DMT01 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 DMT01. It will automatically join the network via OTAA and start to send the sensor value.
--
--(((
--On each uplink, DMT01 will get the temperature from the sensor and send it to the server.
--)))
--)))
--
--
  == 2.3  Quick guide to connect to LoRaWAN server (OTAA) ==
@@ -350,8 +350,7 @@
--(% class="wikigeneratedid" id="HUnittimestamp" %)
--(% style="color:#4472c4" %)**Unit timestamp**
++==== (% style="color:#4472c4" %)**Unit timestamp**(%%) ====
  Unit TimeStamp Example: 689085D7(H) = 1754301911(D)
@@ -358,83 +358,308 @@
  Put the decimal value into this link([[https:~~/~~/www.epochconverter.com)>>https://www.epochconverter.com]])to get the time.
--(% class="wikigeneratedid" id="HDevMode" %)
--(% style="color:#4472c4" %)**DevMode**
++==== (% style="color:#4472c4" %)**DevMode**(%%) ====
--Example：
++**Example**：
--if payload is 0x01: BLE_LoRa
++If payload is 0x01: BLE_LoRa
--if payload is 0x02: LoRa
++If payload is 0x02: LoRa
--if payload is 0x03: BLE
++If payload is 0x03: BLE
--(% class="wikigeneratedid" id="HMACaddr" %)
--(% style="color:#4472c4" %)**MACaddr**
++==== (% style="color:#4472c4" %)**MACaddr**(%%) ====
--Example:
++**Example**:
--If payload is 0xC12309250F1A =
++If the payload is C12309250F1A, the MACaddr is C12309250F1A
--(% class="wikigeneratedid" id="HProbeBat" %)
--(% style="color:#4472c4" %)**ProbeBat**
++==== (% style="color:#4472c4" %)**ProbeBat**(%%) ====
  **Example:**
--If payload & 0x01 = 0x01  **~-~->** This is an Alarm Message.It means that the temperature and humidity exceed the alarm value or trigger an interrupt.
++If payload is 0x64 = 100%
--If payload & 0x01 = 0x00  **~-~->** This is a normal uplink message, no alarm.
--If payload & 0x80>>7 = 0x01  **~-~->** The PA8 is low level.
++==== (% style="color:#4472c4" %)**BoxBat**(%%) ====
--If payload & 0x80>>7 =0x00  **~-~->** The PA8 is high level.
++**Example:**
--If payload >> 2 = 0x00     **~-~->**  means MOD=1, This is a sampling uplink message.
++If payload is 0x46 = 70%
--If payload >> 2 = 0x31     **~-~->**  means MOD=31, this message is a reply message for polling, this message contains the alarm settings. see [[this link>>path:#HPolltheAlarmsettings:]] for detail.
++==== (% style="color:#4472c4" %)**Food temperature**(%%) ====
--(% class="wikigeneratedid" id="HBoxBat" %)
--(% style="color:#4472c4" %)**BoxBat**
++Because the food temperature data is a little-endian sequence, the order of the front and back bytes needs to be swapped during decoding.
--Sensor Battery Level.
++**Example**:
--Ex1: 0x0B45 = 2885mV
++If payload is: D300H = 00D3H, temp = 00D3H /10 = 21.1 degree
--Ex2: 0x0B49 = 2889mV
++If payload is: 3FFFH  = FF3F , temp = (FF3FH - 65536)/10 = -19.3 degrees.
--(% style="color:#4472c4" %)**Food temperature**
++==== (% style="color:#4472c4" %)**Ambient temperature**(%%) ====
++Because the food temperature data is a little-endian sequence, the order of the front and back bytes needs to be swapped during decoding.
++
  **Example**:
--If payload is: 0105H:  (0105 & 8000 == 0), temp = 0105H /10 = 26.1 degree
++If payload is: D200H = 00D2H, temp = 00D2H /10 = 21.0 degree
--If payload is: FF3FH :  (FF3F & 8000 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees.
++If payload is: 3FFFH  = FF3F , temp = (FF3FH - 65536)/10 = -19.3 degrees.
--(FF3F & 8000:Judge whether the highest bit is 1, when the highest bit is 1, it is negative)
--(% style="color:#4472c4" %)**Ambient temperature**
++== 2.4 Bluetoothe Broadcast Payload ==
++Scan and obtain DMT01 device broadcast data through a third-party mobile phone app (such as nRF Connect)
++
++Example：
++
++Note: The following data is obtained through the **nRF Connect tool**.
++
++[[image:1754305290140-806.jpg||height="680" width="432"]]
++
++
++If the scanned payload is 0x0201060609444D5430310EFF  **01C12309250F1AD100CD006446   **0512E001E001
++
++(% style="color:red" %)**Note**(%%)：
++
++* The first 12 bytes in the payload are the Bluetooth packet header data and do not need to be decoded.
++* The last 6 bytes in the payload are the Bluetooth packet trailer data and do not need to be decoded.
++
++So the payload is：**01C12309250F1AD100CD006446**
++
++
++==== (% style="color:#4472c4" %)**Bluetooth data packet frame header**(%%) ====
++
++Example: 0x0201060609444D5430310EFF
++
++
++==== (% style="color:#4472c4" %)**DevMode**(%%) ====
++
++**Example**：
++
++If payload is 0x01: BLE_LoRa
++
++If payload is 0x02: LoRa
++
++If payload is 0x03: BLE
++
++
++==== (% style="color:#4472c4" %)**MACaddr**(%%) ====
++
  **Example**:
--If payload is: 0105H:  (0105 & 8000 == 0), temp = 0105H /10 = 26.1 degree
++If the payload is C12309250F1A, the MACaddr is C12309250F1A
--If payload is: FF3FH :  (FF3F & 8000 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees.
--(FF3F & 8000:Judge whether the highest bit is 1, when the highest bit is 1, it is negative)
++==== (% style="color:#4472c4" %)**ProbeBat**(%%) ====
++**Example:**
++If payload is 0x64 = 100%
--== 2.4 Bluetoothe Broadcast Payload ==
++==== (% style="color:#4472c4" %)**BoxBat**(%%) ====
++**Example:**
++If payload is 0x46 = 70%
++==== (% style="color:#4472c4" %)**Food temperature**(%%) ====
++
++Because the food temperature data is a little-endian sequence, the order of the front and back bytes needs to be swapped during decoding.
++
++**Example**:
++
++If payload is: D300H = 00D3H, temp = 00D3H /10 = 21.1 degree
++
++If payload is: 3FFFH  = FF3F , temp = (FF3FH - 65536)/10 = -19.3 degrees.
++
++
++==== (% style="color:#4472c4" %)**Ambient temperature**(%%) ====
++
++Because the food temperature data is a little-endian sequence, the order of the front and back bytes needs to be swapped during decoding.
++
++**Example**:
++
++If payload is: D200H = 00D2H, temp = 00D2H /10 = 21.0 degree
++
++If payload is: 3FFFH  = FF3F , temp = (FF3FH - 65536)/10 = -19.3 degrees.
++
++
++==== (% style="color:#4472c4" %)**Bluetooth data packet frame tail**(%%) ====
++
++Example: 0x0512E001E001
++
++
++
++== 2.5 Datalog Feature ==
++
++
++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.
++
++
++=== 2.5.1 How datalog works ===
++
++
++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.
++
++* (((
++a) DMT01 will do an ACK check for data records sending to make sure every data arrive server.
++)))
++* (((
++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.
++
++
++)))
++
++=== 2.5.2 Enable Datalog ===
++
++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.
++
++* (((
++a) DMT01 performs an ACK check for each data record to ensure it successfully reaches the server.
++)))
++* (((
++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.
++)))
++
++
++
++=== 2.5.3 Unix TimeStamp ===
++
++
++DMT01 uses Unix TimeStamp format based on
++
++[[image:1754354802681-163.jpeg]]
++
++User can get this time from link:  [[https:~~/~~/www.epochconverter.com/>>url:https://www.epochconverter.com/]] :
++
++Below is the converter example
++
++[[image:1754354818964-624.jpeg]]
++
++
++
++=== 2.5.4 Set Device Time ===
++
++
++You need to run downlink command 28 01 to enable time synchronization.
++
++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.)//
++
++{{info}}
++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.
++{{/info}}
++
++(% style="color:#4f81bd" %)**Downlink Command: 0x28**
++
++* Example: 0x28 01        ~/~/ Automatic time synchronization Enabled
++* Example: 0x28 00       ~/~/  Automatic time synchronization Disable.
++
++=== 2.5.5 Datalog Uplink payload (FPORT~=3) ===
++
++
++The Datalog uplinks will use below payload format.
++
++**Retrieval data payload:**
++
++(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:500px" %)
++|=(% style="width: 60px;background-color:#4F81BD;color:white" %)(((
++**Size(bytes)**
++)))|=(% style="width: 40px; background-color:#4F81BD;color:white" %)**2**|=(% style="width: 55px; background-color:#4F81BD;color:white" %)**2**|=(% style="width: 65px; background-color:#4F81BD;color:white" %)**2**|=(% style="width: 180px; background-color:#4F81BD;color:white" %)**1**|=(% style="width: 100px; background-color:#4F81BD;color:white" %)**4**
++|(% style="width:103px" %)Value|(% style="width:68px" %)(((
++ignore
++)))|(% style="width:104px" %)(((
++(((
++Humidity
++)))
++)))|(% style="width:87px" %)(((
++Temperature
++)))|(% style="width:178px" %)(((
++Poll message flag & Alarm Flag& Level of PA8
++)))|(% style="width:137px" %)Unix Time Stamp
++
++**Poll message flag & Alarm Flag & Level of PA8:**
++
++[[image:image-20230524114302-1.png||height="115" width="736"]]
++
++
++**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)
++
++**Poll Message Flag**: 1: This message is a poll message reply.
++
++* Poll Message Flag is set to 1.
++
++* Each data entry is 11 bytes, to save airtime and battery, devices will send max bytes according to the current DR and Frequency bands.
++
++For example, in US915 band, the max payload for different DR is:
++
++**a) DR0:** max is 11 bytes so one entry of data
++
++**b) DR1:** max is 53 bytes so devices will upload 4 entries of data (total 44 bytes)
++
++**c) DR2:** total payload includes 11 entries of data
++
++**d) DR3: **total payload includes 22 entries of data.
++
++If devise doesn't have any data in the polling time. Device will uplink 11 bytes of 0
++
++**Example:**
++
++If DMT01 has below data inside Flash:
++
++[[image:image-20230524114654-2.png]]
++
++
++If user sends below downlink command:  31646D84E1646D856C05
++
++Where : Start time: 646D84E1 = time 23/5/24 03:30:41
++
++             Stop time: 646D856C= time 23/5/24 03:33:00
++
++
++DMT01 **will uplink this payload.**
++
++[[image:image-20230524114826-3.png||height="448" width="1244"]]
++
++(((
++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
++)))
++
++(((
++Where the first 11 bytes is for the first entry:
++)))
++
++(((
++00 00 02 36 01 10 40 64 6D 84 E1
++)))
++
++(((
++**Hum**=0x0236/10=56.6
++)))
++
++(((
++**Temp**=0x0110/10=27.2
++)))
++
++(((
++**poll message flag & Alarm Flag & Level of PA8**=0x40,means reply data,sampling uplink message,the PA8 is low level.
++)))
++
++(((
++**Unix time** is 0x646D84E1=1684899041s=23/5/24 03:30:41
++)))
++
++
++
++
  = 3. Configure DMT01  ~-~- 需要修改 =
  == 3.1 Configure Methods ==

1754305091443-355.jpg

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+408.8 KB

Content

1754305290140-806.jpg

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+133.1 KB

Content

1754354802681-163.jpeg

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+18.9 KB

Content

1754354818964-624.jpeg

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+67.4 KB

Content

Changes for page DMT01

Summary

Details

Applications

Navigation