Changes for page DMT01
Last modified by Mengting Qiu on 2025/08/11 18:25
From version 53.1
edited by Mengting Qiu
on 2025/08/04 19:17
on 2025/08/04 19:17
Change comment:
There is no comment for this version
To version 55.2
edited by Mengting Qiu
on 2025/08/05 08:36
on 2025/08/05 08:36
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -189,21 +189,6 @@ 189 189 ))) 190 190 191 191 192 -== 2.2 How it works? == 193 - 194 -((( 195 -((( 196 - 197 -))) 198 - 199 -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. 200 - 201 -((( 202 -On each uplink, DMT01 will get the temperature from the sensor and send it to the server. 203 -))) 204 -))) 205 - 206 - 207 207 == 2.3 Quick guide to connect to LoRaWAN server (OTAA) == 208 208 209 209 ... ... @@ -414,8 +414,13 @@ 414 414 415 415 == 2.4 Bluetoothe Broadcast Payload == 416 416 417 -=== 2.4.1 ScanningTools===402 +=== 2.4.1 How to use the scanning tool === 418 418 404 + 405 + 406 + 407 +=== 2.4.2 Data Analysis === 408 + 419 419 Scan and obtain DMT01 device broadcast data through a third-party mobile phone app (such as nRF Connect) 420 420 421 421 Example: ... ... @@ -425,7 +425,7 @@ 425 425 [[image:1754305290140-806.jpg||height="680" width="432"]] 426 426 427 427 428 -If the scanned payload is 0x0201060609444D5430310EFF **01C12309250F1AD100CD006446 418 +If the scanned payload is 0x0201060609444D5430310EFF **01C12309250F1AD100CD006446 **0512E001E001 429 429 430 430 (% style="color:red" %)**Note**(%%): 431 431 ... ... @@ -435,9 +435,71 @@ 435 435 So the payload is:**01C12309250F1AD100CD006446** 436 436 437 437 428 +==== (% style="color:#4472c4" %)**Bluetooth data packet frame header**(%%) ==== 438 438 430 +Example: 0x0201060609444D5430310EFF 439 439 440 440 433 +==== (% style="color:#4472c4" %)**DevMode**(%%) ==== 434 + 435 +**Example**: 436 + 437 +If payload is 0x01: BLE_LoRa 438 + 439 +If payload is 0x02: LoRa 440 + 441 +If payload is 0x03: BLE 442 + 443 + 444 +==== (% style="color:#4472c4" %)**MACaddr**(%%) ==== 445 + 446 +**Example**: 447 + 448 +If the payload is C12309250F1A, the MACaddr is C12309250F1A 449 + 450 + 451 +==== (% style="color:#4472c4" %)**ProbeBat**(%%) ==== 452 + 453 +**Example:** 454 + 455 +If payload is 0x64 = 100% 456 + 457 + 458 +==== (% style="color:#4472c4" %)**BoxBat**(%%) ==== 459 + 460 +**Example:** 461 + 462 +If payload is 0x46 = 70% 463 + 464 + 465 +==== (% style="color:#4472c4" %)**Food temperature**(%%) ==== 466 + 467 +Because the food temperature data is a little-endian sequence, the order of the front and back bytes needs to be swapped during decoding. 468 + 469 +**Example**: 470 + 471 +If payload is: D300H = 00D3H, temp = 00D3H /10 = 21.1 degree 472 + 473 +If payload is: 3FFFH = FF3F , temp = (FF3FH - 65536)/10 = -19.3 degrees. 474 + 475 + 476 +==== (% style="color:#4472c4" %)**Ambient temperature**(%%) ==== 477 + 478 +Because the food temperature data is a little-endian sequence, the order of the front and back bytes needs to be swapped during decoding. 479 + 480 +**Example**: 481 + 482 +If payload is: D200H = 00D2H, temp = 00D2H /10 = 21.0 degree 483 + 484 +If payload is: 3FFFH = FF3F , temp = (FF3FH - 65536)/10 = -19.3 degrees. 485 + 486 + 487 +==== (% style="color:#4472c4" %)**Bluetooth data packet frame tail**(%%) ==== 488 + 489 +Example: 0x0512E001E001 490 + 491 + 492 + 441 441 = 3. Configure DMT01 ~-~- 需要修改 = 442 442 443 443 == 3.1 Configure Methods ==