Changes for page N95S31B -- NB-IoT Temperature & Humidity Sensor User Manual
Last modified by Mengting Qiu on 2024/04/02 16:44
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 2 removed)
Details
- Page properties
-
- Content
-
... ... @@ -9,7 +9,6 @@ 9 9 10 10 **Table of Contents:** 11 11 12 -{{toc/}} 13 13 14 14 15 15 ... ... @@ -42,6 +42,7 @@ 42 42 43 43 == 1.2 Features == 44 44 44 + 45 45 * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD 46 46 * Monitor Temperature & Humidity via SHT31 47 47 * AT Commands to change parameters ... ... @@ -53,6 +53,8 @@ 53 53 * Micro SIM card slot for NB-IoT SIM 54 54 * 8500mAh Battery for long term use 55 55 56 + 57 + 56 56 == 1.3 Specification == 57 57 58 58 ... ... @@ -79,6 +79,8 @@ 79 79 * Max continuously current: 130mA 80 80 * Max boost current: 2A, 1 second 81 81 84 + 85 + 82 82 == 1.4 Applications == 83 83 84 84 * Smart Buildings & Home Automation ... ... @@ -126,6 +126,9 @@ 126 126 1. When boot the device in flash mode 127 127 1. Send an uplink packet 128 128 133 + 134 + 135 + 129 129 = 2. Use N95S31B to communicate with IoT Server = 130 130 131 131 == 2.1 How it works == ... ... @@ -169,6 +169,7 @@ 169 169 * The local NB-IoT network used the band that N95S31B supports. 170 170 * Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 171 171 179 + 172 172 Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 173 173 174 174 N95S31B supports different communication protocol such as : ... ... @@ -294,7 +294,7 @@ 294 294 295 295 === 2.2.7 Use MQTT protocol to uplink data === 296 296 297 -N95S31B supports only plain MQTT now it doesn 't support TLS and other related encryption.305 +N95S31B supports only plain MQTT now it doesn’t support TLS and other related encryption. 298 298 299 299 * (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 300 300 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port ... ... @@ -301,8 +301,8 @@ 301 301 * (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 302 302 * (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 303 303 * (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 304 -* (% style="color:blue" %)**AT+PUBTOPIC=f9527 305 -* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 312 +* (% style="color:blue" %)**AT+PUBTOPIC=f9527 **(%%)~/~/Set the sending topic of MQTT 313 +* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 **(%%) ~/~/Set the subscription topic of MQTT 306 306 307 307 [[image:1657352634421-276.png]] 308 308 ... ... @@ -320,21 +320,20 @@ 320 320 321 321 322 322 323 -=== 2.2. 8Use TCP protocol to uplink data ===331 +=== 2.2.7 Use TCP protocol to uplink data === 324 324 325 -This feature is supported since firmware version v110 326 326 327 327 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 328 328 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 329 329 330 -[[image: 1657352898400-901.png]]337 +[[image:image-20220709093918-1.png]] 331 331 332 332 333 -[[image: 1657352914475-252.png]]340 +[[image:image-20220709093918-2.png]] 334 334 335 335 336 336 337 -=== 2.2. 9Change Update Interval ===344 +=== 2.2.8 Change Update Interval === 338 338 339 339 User can use below command to change the (% style="color:green" %)**uplink interval**. 340 340 ... ... @@ -341,208 +341,227 @@ 341 341 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 342 342 343 343 ((( 344 - 351 +(% style="color:red" %)**NOTE:** 345 345 ))) 346 346 354 +((( 355 +(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour. 356 +))) 347 347 348 348 359 + 349 349 == 2.3 Uplink Payload == 350 350 362 +In this mode, uplink payload includes in total 14 bytes 351 351 352 -NBSN95 has different working mode for the connections of different type of sensors. This section describes these modes. User can use the AT Command (% style="color:blue" %)**AT+MOD**(%%) to set NBSN95 to different working modes. 353 353 365 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %) 366 +|=(% style="width: 60px;" %)((( 367 +**Size(bytes)** 368 +)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1** 369 +|(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:41px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:120px" %)[[Distance (unit: mm)>>||anchor="H2.4.5A0Distance"]]|(% style="width:80px" %)[[Interrupt>>||anchor="H2.4.6A0DigitalInterrupt"]] 354 354 355 -For example: 371 +((( 372 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data. 373 +))) 356 356 357 - (% style="color:blue" %)**AT+CFGMOD=2 ** (%%)~/~/will set the NBSN95 to work in MOD=2 distance mode which target to measure distance via Ultrasonic Sensor. 358 358 376 +[[image:1657331036973-987.png]] 359 359 360 -The uplink payloads are composed in ASCII String. For example: 378 +((( 379 +The payload is ASCII string, representative same HEX: 380 +))) 361 361 362 -0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload: 382 +((( 383 +0x72403155615900640c6c19029200 where: 384 +))) 363 363 364 -0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes 386 +* ((( 387 +Device ID: 0x724031556159 = 724031556159 388 +))) 389 +* ((( 390 +Version: 0x0064=100=1.0.0 391 +))) 365 365 393 +* ((( 394 +BAT: 0x0c6c = 3180 mV = 3.180V 395 +))) 396 +* ((( 397 +Signal: 0x19 = 25 398 +))) 399 +* ((( 400 +Distance: 0x0292= 658 mm 401 +))) 402 +* ((( 403 +Interrupt: 0x00 = 0 366 366 367 -(% style="color:red" %)**NOTE:** 368 368 369 -(% style="color:red" %) 370 -1. All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]]. 371 -1. By default, the device will send an uplink message every 1 hour. 372 372 407 + 408 +))) 373 373 410 +== 2.4 Payload Explanation and Sensor Interface == 374 374 375 -=== 2.3.1 Payload Analyze === 376 376 377 - N95S31Buplink payload includesintotal 21 bytes413 +=== 2.4.1 Device ID === 378 378 379 - 380 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %) 381 -|=(% style="width: 60px;" %)((( 382 -**Size(bytes)** 383 -)))|=(% style="width: 50px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 55px;" %)1|=(% style="width: 115px;" %)5|=(% style="width: 60px;" %)**2**|=(% style="width: 60px;" %)**2** 384 -|(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H2.3.2A0DeviceID"]]|(% style="width:41px" %)[[Ver>>||anchor="H2.3.3A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.3.4A0BatteryInfo"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H2.3.5A0SignalStrength"]]|(% style="width:123px" %)MOD 0X01|(% style="width:99px" %)((( 385 385 ((( 386 - Reserve/Same asNBSN95CFGMOD=1416 +By default, the Device ID equal to the last 6 bytes of IMEI. 387 387 ))) 388 388 389 389 ((( 390 - Nofunctionhere.420 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 391 391 ))) 392 - )))|(% style="width:77px" %)(((422 + 393 393 ((( 394 - [[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]424 +**Example:** 395 395 ))) 396 396 397 397 ((( 398 - By SHT31428 +AT+DEUI=A84041F15612 399 399 ))) 400 - )))|(% style="width:80px" %)(((430 + 401 401 ((( 402 - [[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]432 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID. 403 403 ))) 404 404 435 + 436 + 437 +=== 2.4.2 Version Info === 438 + 405 405 ((( 406 - BySHT31440 +Specify the software version: 0x64=100, means firmware version 1.00. 407 407 ))) 408 -))) 409 409 410 410 ((( 411 -((( 412 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. 444 +For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0. 413 413 ))) 414 -))) 415 415 416 416 417 -[[image:1657354294009-643.png]] 418 418 449 +=== 2.4.3 Battery Info === 419 419 420 -The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where: 421 - 422 -* Device ID: 0x724031607457 = 724031607457 423 -* Version: 0x006e=110=1.1.0 424 - 425 -* BAT: 0x0ccd = 3277 mV = 3.277V 426 -* Signal: 0x1b = 27 427 -* Model: 0x01 = 1 428 -* 0x00dc000ccc= reserve, ignore in N95S31B 429 -* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C 430 -* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh 431 - 432 432 ((( 433 - 452 +Ex1: 0x0B45 = 2885mV 434 434 ))) 435 435 436 436 ((( 437 - 456 +Ex2: 0x0B49 = 2889mV 438 438 ))) 439 439 440 440 441 -=== 2.3.2 Device ID === 442 442 461 +=== 2.4.4 Signal Strength === 462 + 443 443 ((( 444 -B ydefault,the Device ID equal to thelast6 bytes of IMEI.464 +NB-IoT Network signal Strength. 445 445 ))) 446 446 447 447 ((( 448 - User can use (% style="color:blue" %)**AT+DEUI**(%%)tosetDevice ID468 +**Ex1: 0x1d = 29** 449 449 ))) 450 450 451 451 ((( 452 - **Example:**472 +(% style="color:blue" %)**0**(%%) -113dBm or less 453 453 ))) 454 454 455 455 ((( 456 - AT+DEUI=A84041F15612476 +(% style="color:blue" %)**1**(%%) -111dBm 457 457 ))) 458 458 459 459 ((( 460 - TheDevice ID isstored in a none-erase area, Upgrade the firmwareorrun**AT+FDR**won't erase Device ID.480 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm 461 461 ))) 462 462 483 +((( 484 +(% style="color:blue" %)**31** (%%) -51dBm or greater 485 +))) 463 463 487 +((( 488 +(% style="color:blue" %)**99** (%%) Not known or not detectable 489 +))) 464 464 465 -=== 2.3.3 Version Info === 466 466 467 467 468 - Thesebytesinclude the hardware andsoftwareversion.493 +=== 2.4.5 Distance === 469 469 470 - Higherbyte:Specifyhardwareversion: always0x00forN95S31B495 +Get the distance. Flat object range 280mm - 7500mm. 471 471 472 -Lower byte: Specify the software version: 0x6E=110, means firmware version 110 497 +((( 498 +For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is 499 +))) 473 473 474 - 475 -For example: 0x00 6E: this device is N95S31B with firmware version 110. 476 - 477 477 ((( 478 - 502 +((( 503 +(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.** 479 479 ))) 505 +))) 480 480 481 - 482 -=== 2.3.4 Battery Info === 483 - 484 484 ((( 485 - Ex1:0x0B45 = 2885mV508 + 486 486 ))) 487 487 488 488 ((( 489 - Ex2:0x0B49 = 2889mV512 + 490 490 ))) 491 491 515 +=== 2.4.6 Digital Interrupt === 492 492 493 - 494 -=== 2.3.5 Signal Strength === 495 - 496 496 ((( 497 - NB-IoTNetworksignalStrength.518 +Digital Interrupt refers to pin (% style="color:blue" %)**GPIO_EXTI**(%%), and there are different trigger methods. When there is a trigger, the NDDS75 will send a packet to the server. 498 498 ))) 499 499 500 500 ((( 501 - **Ex1:0x1d= 29**522 +The command is: 502 502 ))) 503 503 504 504 ((( 505 -(% style="color:blue" %)** 0**(%%)-113dBmor less526 +(% style="color:blue" %)**AT+INTMOD=3 **(%%) ~/~/(more info about INMOD please refer [[**AT Command Manual**>>url:https://www.dragino.com/downloads/downloads/NB-IoT/NBSN95/DRAGINO_NBSN95-NB_AT%20Commands_v1.1.0.pdf]])**.** 506 506 ))) 507 507 529 + 508 508 ((( 509 - (%style="color:blue"%)**1**(%%)-111dBm531 +The lower four bits of this data field shows if this packet is generated by interrupt or not. Click here for the hardware and software set up. 510 510 ))) 511 511 534 + 512 512 ((( 513 - (% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm536 +Example: 514 514 ))) 515 515 516 516 ((( 517 -( %style="color:blue"%)**31** (%%) -51dBm or greater540 +0x(00): Normal uplink packet. 518 518 ))) 519 519 520 520 ((( 521 -( %style="color:blue" %)**99** (%%) Notknownor not detectable544 +0x(01): Interrupt Uplink Packet. 522 522 ))) 523 523 524 524 525 525 526 -=== 2. 3.6Temperature& Humidity===549 +=== 2.4.7 +5V Output === 527 527 528 -The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server. 551 +((( 552 +NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 553 +))) 529 529 530 -[[image:image-20220709161741-3.png]] 531 531 556 +((( 557 +The 5V output time can be controlled by AT Command. 558 +))) 532 532 533 -Convert the read byte to decimal and divide it by ten. 560 +((( 561 +(% style="color:blue" %)**AT+5VT=1000** 562 +))) 534 534 564 +((( 565 +Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors. 566 +))) 535 535 536 -**Example:** 537 537 538 -Temperature: Read:00ec (H) = 236(D) Value: 236 /10=23.6℃ 539 539 540 - Humidity:Read:0295(H)=661(D)Value:661 / 10=66.1, So66.1%570 +== 2.5 Downlink Payload == 541 541 542 - 543 - 544 -== 2.4 Downlink Payload == 545 - 546 546 By default, NDDS75 prints the downlink payload to console port. 547 547 548 548 [[image:image-20220709100028-1.png]] ... ... @@ -593,16 +593,51 @@ 593 593 594 594 595 595 596 -== 2. 5BatteryAnalysis==622 +== 2.6 LED Indicator == 597 597 598 -=== 2.5.1 Battery Type === 599 599 625 +The NDDS75 has an internal LED which is to show the status of different state. 600 600 627 + 628 +* When power on, NDDS75 will detect if sensor probe is connected, if probe detected, LED will blink four times. (no blinks in this step is no probe) 629 +* Then the LED will be on for 1 second means device is boot normally. 630 +* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds. 631 +* For each uplink probe, LED will be on for 500ms. 632 + 601 601 ((( 602 - TheN95S31B battery is a combination of an 8500mAh Li/SOCI2 Battery and a Super Capacitor. The battery is none-rechargeable battery type with a low discharge rate (<2% per year). This type of battery is commonly used in IoT devices such as water meter.634 + 603 603 ))) 604 604 637 + 638 + 639 +== 2.7 Firmware Change Log == 640 + 641 + 605 605 ((( 643 +Download URL & Firmware Change log 644 +))) 645 + 646 +((( 647 +[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/Firmware/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/Firmware/]] 648 +))) 649 + 650 + 651 +((( 652 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 653 +))) 654 + 655 + 656 + 657 +== 2.8 Battery Analysis == 658 + 659 +=== 2.8.1 Battery Type === 660 + 661 + 662 +((( 663 +The NDDS75 battery is a combination of an 8500mAh Li/SOCI2 Battery and a Super Capacitor. The battery is none-rechargeable battery type with a low discharge rate (<2% per year). This type of battery is commonly used in IoT devices such as water meter. 664 +))) 665 + 666 +((( 606 606 The battery is designed to last for several years depends on the actually use environment and update interval. 607 607 ))) 608 608 ... ... @@ -620,35 +620,56 @@ 620 620 621 621 622 622 623 -=== 2. 5.2 Power consumption Analyze ===684 +=== 2.8.2 Power consumption Analyze === 624 624 625 625 ((( 626 - The file**DRAGINO_N95S31B-Power-Analyzer.pdf**from [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/]] describesadetailmeasurementtoanalyzethepowerconsumption indifferentcase. User can useitfordesignguideline fortheirproject.687 +Dragino battery powered product are all runs in Low Power mode. We have an update battery calculator which base on the measurement of the real device. User can use this calculator to check the battery life and calculate the battery life if want to use different transmit interval. 627 627 ))) 628 628 690 + 629 629 ((( 630 - 692 +Instruction to use as below: 631 631 ))) 632 632 695 +((( 696 +(% style="color:blue" %)**Step 1: **(%%)Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/]] 697 +))) 633 633 634 -=== 2.5.3 Battery Note === 635 635 636 636 ((( 637 - TheLi-SICO batteryis designed for small current / long period application. It is not good tousea high current, short periodtransmitmethod.Therecommendedminimum period for use ofthisbattery is 5 minutes.If you use a shorter period time to uplink data, then the battery life may be decreased.701 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose 638 638 ))) 639 639 704 +* ((( 705 +Product Model 706 +))) 707 +* ((( 708 +Uplink Interval 709 +))) 710 +* ((( 711 +Working Mode 712 +))) 640 640 714 +((( 715 +And the Life expectation in difference case will be shown on the right. 716 +))) 641 641 642 - === 2.5.4 Replacethe battery ===718 +[[image:image-20220709110451-3.png]] 643 643 644 644 721 + 722 +=== 2.8.3 Battery Note === 723 + 645 645 ((( 646 - You can changethebattery intheN95S31B.Thetype ofbatteryis notlimitedaslongas theutput isbetween3vto3.6v.Onthemainboard,there isa diode(D1)betweenthebatteryandthemaincircuit. If youneed touse abatterywith less than 3.3v,pleaseremove the D1 andshortcut the twopadsofitso there won'tbe voltagedropbetween batteryandmainboard.725 +The Li-SICO battery is designed for small current / long period application. It is not good to use a high current, short period transmit method. The recommended minimum period for use of this battery is 5 minutes. If you use a shorter period time to transmit LoRa, then the battery life may be decreased. 647 647 ))) 648 648 649 649 729 + 730 +=== 2.8.4 Replace the battery === 731 + 650 650 ((( 651 -The default battery pack of N 95S31Bincludes a ER26500 plus super capacitor. If user can't find this pack locally, they can find ER26500 or equivalence without the SPC1520 capacitor, which will also work in most case. The SPC can enlarge the battery life for high frequency use (update period below 5 minutes).733 +The default battery pack of NDDS75 includes a ER26500 plus super capacitor. If user can't find this pack locally, they can find ER26500 or equivalence without the SPC1520 capacitor, which will also work in most case. The SPC can enlarge the battery life for high frequency use (update period below 5 minutes). 652 652 ))) 653 653 654 654 ... ... @@ -671,7 +671,7 @@ 671 671 672 672 == 4.1 Access AT Commands == 673 673 674 -See NBSN95 AT Command inthis link for detail:BSN95/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN95/]]756 +See this link for detail: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/]] 675 675 676 676 677 677 AT+<CMD>? : Help on <CMD> ... ... @@ -759,9 +759,7 @@ 759 759 ))) 760 760 761 761 ((( 762 - 763 - 764 -(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update. 844 +(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update. 765 765 ))) 766 766 767 767 ... ... @@ -793,7 +793,7 @@ 793 793 = 7. Order Info = 794 794 795 795 796 -Part Number**:** (% style="color:#4f81bd" %)**N 95S31B-YY**876 +Part Number**:** (% style="color:#4f81bd" %)**NSDDS75** 797 797 798 798 799 799 (% class="wikigeneratedid" %) ... ... @@ -808,7 +808,7 @@ 808 808 809 809 (% style="color:#037691" %)**Package Includes**: 810 810 811 -* N 95S31BNB-IoTTemperatureandHumiditySensor891 +* NSE01 NB-IoT Distance Detect Sensor Node x 1 812 812 * External antenna x 1 813 813 ))) 814 814 ... ... @@ -817,10 +817,11 @@ 817 817 818 818 (% style="color:#037691" %)**Dimension and weight**: 819 819 900 + 820 820 * Device Size: 13.0 x 5 x 4.5 cm 821 821 * Device Weight: 150g 822 -* Package Size / pcs : 1 4.0x8x 5 cm823 -* Weight / pcs : 180g903 +* Package Size / pcs : 15 x 12x 5.5 cm 904 +* Weight / pcs : 220g 824 824 ))) 825 825 826 826 (((
- 1657354294009-643.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -214.7 KB - Content
- image-20220709161741-3.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -111.2 KB - Content