Skip to Content
Last modified by Kilight Cao on 2025/07/23 16:27
From version 160.1
edited by Mengting Qiu
on 2024/04/18 15:10
Change comment: There is no comment for this version
To version 236.1
edited by Kilight Cao
on 2025/07/23 16:27
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ting
1 +XWiki.Kilight
Content
... ... @@ -40,11 +40,15 @@
40 40  |(% style="width:117px" %)**[[1NCE>>https://1nce.com]]**|(% style="width:151px" %)iot.1nce.net|(% style="width:474px" %)(((
41 41  **[[Coverage Reference Link>>https://1nce.com/en-ap/1nce-connect]]**
42 42  
43 -Austria, Belgium, Bulgaria, Croatia, Czech Republic, Denmark, Finland, Germany, Great Britain, Greece, Hungary, Ireland, Italy, Latvia, Malta, Netherlands, Norway, Puerto Rico, Russia, Slovak , Republic, Slovenia, Spain, Sweden, Switzerland, Taiwan, USA, US Virgin Islands
44 -)))|(% style="width:135px" %)
43 +Austria, Belgium, Bulgaria, Croatia, Czech Republic, Denmark, Finland, Germany, Great Britain, Greece, Hungary, Ireland, Italy, Latvia, Malta, Netherlands, Norway, Puerto Rico, Russia, Slovak , Republic, Slovenia, Spain, Sweden, Switzerland, Taiwan, USA, UK, US Virgin Islands
44 +)))|(% style="width:135px" %)UK: Band20
45 45  |(% style="width:117px" %)China Mobile|(% style="width:151px" %)No need configure|(% style="width:474px" %)China Mainland, HongKong|(% style="width:135px" %)
46 46  |(% style="width:117px" %)China Telecom|(% style="width:151px" %)ctnb|(% style="width:474px" %)China Mainland|(% style="width:135px" %)
47 47  
48 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:878px" %)
49 +|(% style="background-color:#4f81bd; color:white; width:152px" %)**SIM Provider**|(% style="background-color:#4f81bd; color:white; width:169px" %)**AT+QCGDEFCONT=**|(% style="background-color:#4f81bd; color:white; width:427px" %)**Command Explanation**|(% style="background-color:#4f81bd; color:white; width:135px" %)**Comments**
50 +|(% style="width:152px" %)**[[1NCE>>https://1nce.com]]/[[NB card purchased by the customer>>https://1nce.com]]**|(% style="width:169px" %)iot.1nce.net/xxx|(% style="width:427px" %)This command sets the PSD connection settings for PDN connection on power-up. When the MT attaches to the NB-IoT network on power-on, a PDN connection setup is performed. Therefore, PDN connection settings are stored in NVRAM so that they can be used by the modem during the attachment.|(% style="width:135px" %)
51 +
48 48  == 2.2 Speed Up Network Attach time ==
49 49  
50 50  
... ... @@ -62,6 +62,7 @@
62 62  
63 63  After connection is successful, user can use (% style="color:#037691" %)**AT+QENG=0 **(%%) to check which band is actually in used.
64 64  
69 +By default, device will search network for 5 minutes. User can set the time to 10 minutes by (% style="color:#037691" %)**AT+CSQTIME=10 **(%%)so it can search longer.
65 65  
66 66  See bands used for different provider:** [[NB-IoT Deployment , Bands, Operator list>>http://wiki.dragino.com/xwiki/bin/view/Main/NB-IoT%20Deployment%20%2C%20Bands%2C%20Operator%20list/]]**
67 67  
... ... @@ -283,6 +283,7 @@
283 283  
284 284  ==== 3.4.1.1 Create Device ====
285 285  
291 +
286 286  (% style="color:blue" %)**Add Device**(%%) in DataCake.
287 287  
288 288  [[image:image-20230808162301-1.png||height="453" width="952"]]
... ... @@ -353,8 +353,11 @@
353 353  
354 354  **Step6: Please add the decoder at the payload decoder of the device configuration.**
355 355  
356 -**Decoder location:**[[dragino-end-node-decoder/Datacake-Dragino_NB at main · dragino/dragino-end-node-decoder (github.com)>>url:https://github.com/dragino/dragino-end-node-decoder/tree/main/Datacake-Dragino_NB]]
362 +**Decoder location: **[[dragino-end-node-decoder/Datacake-Dragino_NB at main · dragino/dragino-end-node-decoder (github.com)>>url:https://github.com/dragino/dragino-end-node-decoder/tree/main/Datacake-Dragino_NB]]
357 357  
364 +**Due to version update, please use the following decoder for the new version firmware:**
365 +[[dragino-end-node-decoder/Datacake-Dragino_NB_New_Version at main · dragino/dragino-end-node-decoder (github.com)>>url:https://github.com/dragino/dragino-end-node-decoder/tree/main/Datacake-Dragino_NB_New_Version]]
366 +
358 358  [[image:image-20240129172056-7.png||height="457" width="816"]]
359 359  
360 360  [[image:image-20240129173116-9.png||height="499" width="814"]]
... ... @@ -385,11 +385,66 @@
385 385  (% style="color:blue" %)**AT+SERVADDR=67.207.76.90,4445**
386 386  
387 387  
388 -== 3.5 Node-Red (via MQTT) ==
397 +== 3.5 Telemetry2U ==
389 389  
390 -=== 3.5.1 Configure [[Node-Red>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/]] ===
391 391  
400 +=== Configuring the Dragino NB Sensor Settings ===
392 392  
402 +
403 +(% style="color:blue" %)**AT+SERVADDR=telemetry2u.com,4483**(%%) – Sets the server address and port for sending data to the Telemetry2U IoT platform.
404 +
405 +(% style="color:blue" %)**AT+APN=simbase**(%%) – Sets the APN required for LTE-M connectivity using a Simbase global SIM card.
406 +
407 +(% style="color:blue" %)**ATZ**(%%) – Reboots the device to apply the changes. It won’t transmit to Telemetry2U until added and configured on the platform.
408 +
409 +(% style="color:blue" %)**AT+CFG**(%%) – Displays the current configuration. Take note of the 8-byte (HEX) **DEUI**, which you’ll need in the next setup step.
410 +
411 +And that’s it! These simple steps will get your device up and running on our Telemetry2U servers in no time.
412 +
413 +
414 +**Step 1: Log in Telemetry2U**
415 +
416 +
417 +Users can register a Telemetry2U account for their first use
418 +
419 +**[[https:~~/~~/telemetry2u.com/Identity/Account/Register>>https://telemetry2u.com/Identity/Account/Register]]**
420 +
421 +
422 +**Step 2: Add the device**
423 +
424 +[[image:1753258256594-216.png||height="686" width="1382"]]
425 +
426 +
427 +**1. Select Network provide:**Users need to select Telemetry2U NB-IoT over UDP in order to connect to the platform
428 +
429 +**2. Select device type:**Select the template you need to use
430 +
431 +**3. Fill in Description:**Fill in the unique description
432 +
433 +4. **Fill in IMEI:**The IMEI corresponds to the IME of the device
434 +
435 +After completion, click "**Greate**"
436 +
437 +[[image:1753258480811-335.png||height="789" width="1380"]]
438 +
439 +
440 +**Step 3: Check the data**
441 +
442 +
443 +[[image:1753258821265-310.png||height="681" width="1365"]]
444 +
445 +
446 +
447 +For more information, please refer to the user manual on the Telemetry2U official website:
448 +
449 +**[[https:~~/~~/telemetry2u.com/Documentation/dragino-lte-m-nb-iot-sensors-iot-platform-integration>>https://telemetry2u.com/Documentation/dragino-lte-m-nb-iot-sensors-iot-platform-integration]]**
450 +
451 +
452 +== 3.6 Node-Red (via MQTT) ==
453 +
454 +=== 3.6.1 Configure [[Node-Red>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/]] ===
455 +
456 +
393 393  Take S31-NB UDP protocol as an example.
394 394  
395 395  Dragino provides input flow examples for the sensors.
... ... @@ -425,7 +425,7 @@
425 425  [[image:image-20230809174053-9.png]]
426 426  
427 427  
428 -=== 3.5.2 Simulate Connection ===
492 +=== 3.6.2 Simulate Connection ===
429 429  
430 430  
431 431  We have completed the configuration of UDP. We can try sending packets to node red.
... ... @@ -435,7 +435,7 @@
435 435  [[image:image-20230810084048-2.png||height="535" width="1052"]]
436 436  
437 437  
438 -=== 3.5.3 Configure NB-IoT Sensors ===
502 +=== 3.6.3 Configure NB-IoT Sensors ===
439 439  
440 440  
441 441  * (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%) **~/~/ hex format or json format**
... ... @@ -445,11 +445,11 @@
445 445  * (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
446 446  * (% style="color:#037691" %)**AT+PWD=“Your device token”**
447 447  
448 -== 3.6 ThingsBoard.Cloud (via MQTT) ==
512 +== 3.7 ThingsBoard.Cloud (via MQTT) ==
449 449  
450 -=== 3.6.1 Configure ThingsBoard ===
514 +=== 3.7.1 Configure ThingsBoard ===
451 451  
452 -==== 3.6.1.1 Create Device ====
516 +==== 3.7.1.1 Create Device ====
453 453  
454 454  
455 455  Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]]. Record Device Name which is used for MQTT connection.
... ... @@ -457,7 +457,7 @@
457 457  [[image:image-20230802112413-32.png||height="583" width="1066"]]
458 458  
459 459  
460 -==== 3.6.1.2 Create Uplink & Downlink Converter ====
524 +==== 3.7.1.2 Create Uplink & Downlink Converter ====
461 461  
462 462  
463 463  (% style="color:blue" %)**Uplink Converter**
... ... @@ -478,7 +478,7 @@
478 478  (% style="color:red" %)**Note: Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default.**
479 479  
480 480  
481 -==== 3.6.1.3 MQTT Integration Setup ====
545 +==== 3.7.1.3 MQTT Integration Setup ====
482 482  
483 483  
484 484  Go to the (% style="color:blue" %)**Integrations center**(%%) **->** (% style="color:blue" %)**Integrations page**(%%) and click **“(% style="color:blue" %)plus(%%)”** icon to add a new integration. Name it (% style="color:blue" %)**“MQTT Integration”**(%%), select type (% style="color:blue" %)**MQTT**;
... ... @@ -504,13 +504,12 @@
504 504  
505 505  === 3.6.2 Simulate with MQTT.fx ===
506 506  
507 -
508 508  [[image:image-20230802112413-39.png]]
509 509  
510 510  [[image:image-20230802112413-40.png||height="525" width="980"]]
511 511  
512 512  
513 -=== 3.6.3 Configure NB-IoT Sensor ===
576 +=== 3.7.3 Configure NB-IoT Sensor ===
514 514  
515 515  
516 516  (% style="color:blue" %)**AT Commands**
... ... @@ -536,11 +536,80 @@
536 536  [[image:image-20230802112413-43.png||height="407" width="825"]]
537 537  
538 538  
539 -== 3.7 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
602 +== 3.8 ThingsBoard.Cloud (via COAP) ==
540 540  
541 -=== 3.7.1 Create device & Get Credentials ===
604 +=== 3.8.1 Configure ThingsBoard ===
542 542  
606 +==== 3.8.1.1 Create Uplink & Downlink Converter ====
543 543  
608 +
609 +(% style="color:blue" %)**Uplink Converter**
610 +
611 +The purpose of the decoder function is to parse the incoming data and metadata to a format that ThingsBoard can consume. deviceName and deviceType are required, while attributes and telemetry are optional. Attributes and telemetry are flat key-value objects. Nested objects are not supported.
612 +
613 +To create an uplink converter go to the (% style="color:blue" %)**Integrations center**(%%) -> (% style="color:blue" %)**Data converters**(%%) page and click (% style="color:blue" %)**“plus”** (%%)button. Name it (% style="color:blue" %)**“COAP Uplink Converter”**(%%) and select type (% style="color:blue" %)"**Uplink"**(%%). Use debug mode for now.
614 +
615 +[[image:image-20240729141300-1.png||height="552" width="1115"]]
616 +
617 +
618 +(% style="color:blue" %)**Downlink Converter**
619 +
620 +The Downlink converter transforming outgoing RPC message and then the Integration sends it to external COAP broker.
621 +
622 +[[image:image-20240729142505-3.png||height="507" width="1023"]]
623 +
624 +
625 +==== 3.8.1.2 COAP Integration Setup ====
626 +
627 +
628 +Go to the (% style="color:blue" %)**Integrations center**(%%) **->** (% style="color:blue" %)**Integrations page**(%%) and click **“(% style="color:blue" %)plus(%%)”** icon to add a new integration. Name it (% style="color:blue" %)**“CoAP Integration”**(%%), select type **COAP    **(% style="color:blue" %);
629 +
630 +[[image:image-20240729144058-4.png||height="506" width="1021"]]
631 +
632 +
633 +The next steps is to add the recently created uplink converters;
634 +
635 +[[image:image-20240729150142-5.png||height="507" width="1023"]]
636 +
637 +
638 +==== 3.8.1.3 Add COAP Integration ====
639 +
640 +
641 +(% class="wikigeneratedid" id="H" %)
642 +[[image:image-20240729161543-9.png||height="500" width="1009"]]
643 +
644 +
645 +=== 3.8.2 Node Configuration(Example: Connecting to the Thingsboard platform) ===
646 +
647 +==== 3.8.2.1 Instruction Description ====
648 +
649 +
650 +* AT+PRO=1,0(HEX format uplink)  &AT+PRO=1,5(JSON format uplink)
651 +* AT+SERVADDR=COAP Server Address,5683
652 +
653 +Example: AT+SERVADDR=int.thingsboard.cloud,5683(The address is automatically generated when the COAP integration is created)
654 +
655 +[[image:image-20240729172305-12.png||height="361" width="624"]]
656 +
657 +Note:The port for the COAP protocol has been fixed to 5683
658 +
659 +
660 +* AT+URI1=11,(% style="color:red" %)**character length**(%%),"Needs to be consistent with the CoAP endpoint URL in the platform",
661 +
662 +-NB/NS products use the (% style="color:red" %)**BC660K**(%%) module, only need to configure (% style="color:red" %)**only one URL**(%%) command.
663 +
664 +e.g.
665 +
666 +* AT+URI1=11,38, "i/faaaa241f-af4a-b780-4468-c671bb574858"
667 +
668 +[[image:image-20240729172415-13.png||height="401" width="694"]]
669 +
670 +
671 +== 3.9 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
672 +
673 +=== 3.9.1 Create device & Get Credentials ===
674 +
675 +
544 544  We use MQTT Connection to send data to [[Tago.io>>url:https://admin.tago.io/]]. We need to Create Device and Get MQTT Credentials first.
545 545  
546 546  [[image:image-20230802112413-44.png]]
... ... @@ -589,7 +589,7 @@
589 589  
590 590  * (% style="color:#037691" %)**AT+PWD=“Your device token”**
591 591  
592 -=== 3.7.2 Simulate with MQTT.fx ===
724 +=== 3.9.2 Simulate with MQTT.fx ===
593 593  
594 594  
595 595  [[image:image-20230802112413-52.png]]
... ... @@ -605,7 +605,7 @@
605 605  [[image:image-20230808105329-3.png]]
606 606  
607 607  
608 -=== 3.7.3 tago data ===
740 +=== 3.9.3 tago data ===
609 609  
610 610  
611 611  [[image:image-20230802112413-50.png||height="242" width="1037"]]
... ... @@ -613,7 +613,7 @@
613 613  [[image:image-20230802112413-51.png||height="184" width="696"]]
614 614  
615 615  
616 -== 3.8 TCP Connection ==
748 +== 3.10 TCP Connection ==
617 617  
618 618  
619 619  (% style="color:blue" %)**AT command:**
... ... @@ -634,12 +634,163 @@
634 634  [[image:image-20230807233631-2.png]]
635 635  
636 636  
769 +== 3.11 AWS Connection ==
637 637  
638 638  
772 +Users can refer to [[Dragino NB device connection to AWS platform instructions>>http://wiki.dragino.com/xwiki/bin/view/Dragino%20NB%20device%20connection%20to%20AWS%20platform%20instructions/#H1.LogintotheplatformandfindIoTcore]]
773 +
774 +
775 +== 3.12 ThingsEye (via MQTT) ==
776 +
777 +=== 3.12.1 Configure ThingsEye ===
778 +
779 +==== 3.12.1.1 Create MQTT integration ====
780 +
781 +
782 +Go to the (% style="color:blue" %)**Integrations center**(%%) **->** (% style="color:blue" %)**Integrations page**(%%) and click **“(% style="color:blue" %)plus(%%)”** icon to add a new integration. Name it (% style="color:blue" %)**“MQTT Integration_NB”**(%%), select type (% style="color:blue" %)**MQTT**;
783 +
784 +[[image:image-20241126175509-1.png||height="518" width="1081"]]
785 +
786 +
787 +Next, directly select to create a new Uplink data converter and downlink data converter.
788 +
789 +[[image:image-20241126180135-2.png||height="535" width="1092"]]
790 +
791 +[[image:image-20241126180223-3.png||height="518" width="1093"]]
792 +
793 +
794 +(% style="color:blue" %)**Add a topic filter:**
795 +
796 +Consistent with the theme of the node setting.
797 +
798 +(% style="color:red" %)**Note: Recommended MQTT broker: lns1.thingseye.io 8883, fixed use. Topic can be changed on their own, but it need to be consistent with the node's publish and subscribe topic.**
799 +
800 +You can also select an MQTT QoS level. We use MQTT QoS level 0 (At most once) by default;
801 +
802 +[[image:image-20241126181024-4.png||height="521" width="1081"]]
803 +
804 +
805 +==== 3.12.1.2 Add credentials to the MQTT integration ====
806 +
807 +
808 +Click on the MQTT integration you just created.
809 +
810 +[[image:image-20241126181837-5.png||height="365" width="1079"]]
811 +
812 +
813 +Click the edit icon in the upper right corner to enter the edit mode.
814 +
815 +[[image:image-20241126184523-13.png||height="330" width="1075"]]
816 +
817 +
818 +(% style="color:blue" %)**Add credential files.**
819 +
820 +Click this [[link>>https://www.dropbox.com/scl/fo/d5s1wf36f4syv30a8laup/AK8FjVpNXYXCWodRnnQ1Hig?rlkey=jrz1ip0f0xwwq5z2m2gu1tuij&e=1&st=kl4caub0&dl=0]] to download the certificates.
821 +
822 +[[image:image-20241126183032-8.png||height="757" width="976"]]
823 +
824 +When the addition is complete, save the Settings.
825 +
826 +[[image:image-20241126184303-12.png||height="284" width="975"]]
827 +
828 +[[image:image-20241126184211-11.png||height="161" width="977"]]
829 +
830 +
831 +==== 3.12.1.3 Setup uplink and downlink converters ====
832 +
833 +
834 +First, you need to download the [[**MQTT uplink/downlink JS** **code**>>https://www.dropbox.com/scl/fo/d5s1wf36f4syv30a8laup/AK8FjVpNXYXCWodRnnQ1Hig?rlkey=jrz1ip0f0xwwq5z2m2gu1tuij&e=1&st=kl4caub0&dl=0]].
835 +
836 +* (% style="color:blue" %)**Uplink Converter**
837 +
838 +The purpose of the decoder function is to parse the incoming data and metadata to a format that ThingsBoard can consume.
839 +
840 +Go to the (% style="color:blue" %)**Integrations center**(%%) -> (% style="color:blue" %)**Data converters**(%%) page, and find that MQTT uplink converter that was newly created when the integration was created.
841 +
842 +[[image:image-20241126184906-14.png||height="424" width="1100"]]
843 +
844 +Enter edit mode and apply **MQTT uplink JS code** to this uplink converter.
845 +
846 +[[image:image-20241126190131-15.png||height="542" width="1103"]]
847 +
848 +
849 +* (% style="color:blue" %)**Downlink Converter**
850 +
851 +Go to the (% style="color:blue" %)**Integrations center**(%%) -> (% style="color:blue" %)**Data converters**(%%) page, and find that MQTT downlink converter that was newly created when the integration was created.
852 +
853 +[[image:image-20241126190251-16.png||height="372" width="1113"]]
854 +
855 +Enter edit mode and apply **MQTT downlink JS code** to this downlink converter.
856 +
857 +[[image:image-20241126190737-17.png||height="527" width="1114"]]
858 +
859 +
860 +=== 3.12.2 Simulate with MQTT.fx ===
861 +
862 +
863 +[[image:image-20241126191118-18.png||height="605" width="835"]]
864 +
865 +[[image:image-20241126193252-25.png||height="663" width="803"]]
866 +
867 +
868 +=== 3.12.3 Configure -NB node ===
869 +
870 +
871 +First you need to configure the certificate to the -NB node. Follow the instructions in this **[[link>>https://wiki.dragino.com/xwiki/bin/view/Dragino%20NB%20device%20connection%20to%20AWS%20platform%20instructions/#H4.1.2Configurecertificate]]** to configure the certificate.
872 +
873 +Screenshot of successful certificate configuration:
874 +
875 +* Configuring the CA Certificate
876 +
877 +[[image:image-20241126192009-19.png||height="431" width="697"]]
878 +
879 +[[image:image-20241126192130-21.png||height="426" width="694"]]
880 +
881 +* Configure client certificate
882 +
883 +[[image:image-20241126192246-22.png||height="397" width="693"]][[image:image-20241126192315-23.png||height="402" width="645"]]
884 +
885 +* Configure client private key
886 +
887 +[[image:image-20241126192415-24.png||height="435" width="737"]]
888 +
889 +
890 +When the certificate is configured, burn the boot program, burn the working firmware, and then restart the device.
891 +
892 +Then configure the -NB node to connect to the ThingsEye platform:
893 +
894 +(% style="color:blue" %)**AT Commands**
895 +
896 +* (% style="color:#037691" %)**AT+PRO=3,5  **(%%)** **~/~/ Use MQTT Connection & Json Payload
897 +* (% style="color:#037691" %)**AT+SERVADDR=lns1.thingseye.io,8883**
898 +* (% style="color:#037691" %)**AT+SUBTOPIC=8899     **(%%)~/~/ Consistent with the Topic of MQTT integration created by ThingsEye
899 +* (% style="color:#037691" %)**AT+PUBTOPIC=8899     **(%%)~/~/ Consistent with the Topic of MQTT integration created by ThingsEye
900 +* (% style="color:#037691" %)**AT+CLIENT=NULL**
901 +* (% style="color:#037691" %)**AT+UNAME=NULL**
902 +* (% style="color:#037691" %)**AT+PWD=NULL**
903 +* (% style="color:#037691" %)**AT+TLSMOD=1,2**
904 +
905 +Test Uplink by click the button for 1~~3 seconds, the MQTT integration in ThingsEye allows you to view the data upstream from the device:
906 +
907 +[[image:image-20241126193458-26.png||height="375" width="1012"]]
908 +
909 +[[image:image-20241126193609-27.png||height="424" width="1014"]]
910 +
911 +
912 +Go to (% style="color:blue" %)**"Device" **(%%) -> (% style="color:blue" %)** "Search Device"**(%%), enter the (% style="color:blue" %)** IMEI**(%%) of the device to find the device.
913 +
914 +[[image:image-20241126194018-28.png||height="318" width="1076"]]
915 +
916 +You can view the data that has just been uplink on the device:
917 +
918 +[[image:image-20241126194123-29.png||height="486" width="1073"]]
919 +
920 +
639 639  = 4. MQTT/UDP/TCP downlink =
640 640  
641 641  == 4.1 MQTT (via MQTT.fx) ==
642 642  
925 +
643 643  Configure MQTT connections properly and send downlink commands to configure nodes through the Publish function of MQTT.fx//.//
644 644  
645 645  **1.** Configure node MQTT connection (via MQTT.fx):
... ... @@ -680,11 +680,6 @@
680 680  (% style="color:red" %)**Note: Users can edit the hex command in advance. When the node uplink, directly click the publish button several times to increase the success rate of command configuration.**
681 681  
682 682  
683 -
684 -
685 -
686 -
687 -
688 688  = 5. FAQ =
689 689  
690 690  == 5.1 What is the usage of Multi Sampling and One Uplink? ==
... ... @@ -700,8 +700,8 @@
700 700  1. Give more sampling data points.
701 701  1. Increase reliable in transmission. For example. If user set
702 702  1*. **AT+TR=1800** ~/~/ The unit is seconds, and the default is to record data once every 1800 seconds (30 minutes, the minimum can be set to 180 seconds)
703 -1*. **AT+NOUD=24** ~/~/  The device uploads 24 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
704 -1*. **AT+TDC=7200**  ~/~/ Uplink every 2 hours.
981 +1*. **AT+NOUD=24**  ~/~/  The device uploads 24 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
982 +1*. **AT+TDC=7200**  ~/~/  Uplink every 2 hours.
705 705  1*. this will mean each uplink will actually include the 6 uplink data (24 set data which cover 12 hours). So if device doesn't lost 6 continue data. There will not data lost.
706 706  
707 707  == 5.2 Why the uplink JSON format is not standard? ==
... ... @@ -714,6 +714,14 @@
714 714  [[image:image-20240229233154-1.png]]
715 715  
716 716  
995 +== 5.3 What is the data consumption for different transfer mode？ ==
996 +
997 +
998 +For the data consumption of NB-IoT End node in different transfer mode, reference link:
999 +
1000 +[[https:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Traffic%20Statistics%20~~-~~-%20NBCB/>>https://wiki.dragino.com/xwiki/bin/view/Main/Traffic%20Statistics%20--%20NBCB/]]
1001 +
1002 +
717 717  = 6. Trouble Shooting: =
718 718  
719 719  == 6.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
... ... @@ -785,9 +785,254 @@
785 785  Make sure that the SIM card is insert in correct direction and device is power off/on during insert. Here is reference link: [[Insert SIM Card>>||anchor="H2.1GeneralConfiguretoattachnetwork"]].
786 786  
787 787  
788 -== 6.4 Why sometime the AT Command is slow in reponse? ==
1074 +== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.4 Why sometime the AT Command is slow in reponse?(%%) ==
789 789  
790 790  
791 791  When the MCU is communicating with the NB-IoT module, the MCU response of AT Command will become slower, it might takes several seconds to response.
792 792  
793 793  [[image:image-20240226111928-1.png]]
1080 +
1081 +
1082 +== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.5 (%%)What is the Downlink Command Format for NB Devices? ==
1083 +
1084 +
1085 +Firstly, it is recommended that users upgrade the firmware of the -NB node to the latest version, as the processing method for downlink commands varies depending on the firmware version. Below, we will introduce the latest downlink command format.
1086 +
1087 +(% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %)
1088 +=== **UDP Protocol:** ===
1089 +
1090 +Only supports valid **HEX-format downlink commands** corresponding to AT command.
1091 +
1092 +Take the AT+TDC command of S31-NB as an example, that is, only the valid HEX format downstream command corresponding to the AT+TDC command can be used:
1093 +Downward format: (% style="color:blue" %)**01000384**(%%)  ~/~/ There are no Spaces. 0x0384(H)=900(D), that is, modify TDC to 900 seconds.
1094 +
1095 +[[image:1750035991532-434.png||height="237" width="495"]]
1096 +
1097 +
1098 +(% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %)
1099 +=== **MQTT Protocol:** ===
1100 +
1101 +==== **1. HEX-format** ====
1102 +
1103 +Supports **HEX-format** downlink commands (corresponding to AT commands).
1104 +
1105 +//Example~:// For the S31-NB's uplink interval modification (AT+TDC=900):
1106 +
1107 +Downlink command:  (% style="color:blue" %)**01000384**(%%)  ~/~/ There are no Spaces. 0x0384(H)=900(D), that is, modify TDC to 900 seconds.
1108 +
1109 +[[image:1750035004731-376.png||height="276" width="557"]]
1110 +
1111 +
1112 +==== **2. JSON-format ** ====
1113 +
1114 +===== **2. 1 JSON format template.** =====
1115 +
1116 +All -NB nodes support downlink configuration modification using (% style="color:blue" %)**JSON format templates.**
1117 +
1118 +We can use templates to configure multiple commands AT once. Users only need to modify the parameters of the required AT commands in the correct template for each device.
1119 +Template.
1120 +
1121 +Take the template of D2x-NB as an example:
1122 +
1123 +{
1124 +"AT+SERVADDR":"119.91.62.30,1882",
1125 +"AT+CLIENT":"JwcXKjQBNhQ2JykDDAA5Ahs",
1126 +"AT+UNAME":"usenamedragino",
1127 +"AT+PWD":"passworddragino",
1128 +"AT+PUBTOPIC":"123",
1129 +"AT+SUBTOPIC":"321",
1130 +"AT+TDC":"7200",
1131 +"AT+INTMOD":"0",
1132 +"AT+APN":"NULL",
1133 +"AT+5VT":"0",
1134 +"AT+PRO":"3,5",
1135 +"AT+TR":"900",
1136 +"AT+NOUD":"0",
1137 +"AT+CSQTIME":"5",
1138 +"AT+DNSTIMER":"0",
1139 +"AT+TLSMOD":"0,0",
1140 +"AT+MQOS":"0",
1141 +"AT+TEMPALARM1":"0",
1142 +"AT+TEMPALARM2":"10",
1143 +"AT+TEMPALARM3":"0"
1144 +}
1145 +
1146 +Explanations of two special commands in the template: AT+TR (set the detection interval: 0 ~~ 255 minutes) and AT+NOUD (set the number of groups) correspond to parameters in AT+CLOCKLOG.
1147 +
1148 +[[image:1751538862245-924.png]]
1149 +
1150 +
1151 +**Instructions for Using the Template:**
1152 +
1153 +1. Modify the parameters for each AT command in the template as needed.
1154 +1. Send the entire template in one downlink command.
1155 +
1156 +(% style="color:red" %)**Note:**
1157 +
1158 +* The template may vary depending on the device model.
1159 +* **Currently, each specific template is being updated and tested**. If you need a template for your specific device, please contact **Dragino Technical Support** at [[support@dragino.com>>url:https://mailto:support@dragino.com/]] to request the latest downlink template.
1160 +
1161 +
1162 +
1163 +===== **2.2 Support sending json format commands separately** =====
1164 +
1165 +Some models of nodes support sending json format commands separately：(% style="color:blue" %)**RS485-NB, LDS25-NB, CS01-NB, SDI-12-NB, SW3L-NB, WL03A-NB, PS-NB, LTC2-NB.**
1166 +
1167 +//Example~:// For the PS-NB's uplink interval modification (AT+TDC=900):
1168 +
1169 +Downlink command:  (% style="color:blue" %)**{AT+TDC=900}**(%%)**       **~/~/ The correct format is (% style="color:blue" %)**{AT Command}**(%%). No extra characters other than valid AT commands can be added within {}.
1170 +
1171 +(% style="color:red" %)**Note:**
1172 +
1173 +(% style="color:red" %)**1. Only when the correct and valid download command is used and the format is correct can the device be configured through the download command. Invalid download content cannot be processed by the device and will be automatically restarted.**
1174 +
1175 +(% style="color:red" %)**2. Devices designed with downlink commands can utilize different downlink formats (e.g., JSON or HEX) for configuration. However, regardless of the format, the functionality is strictly limited to the downlink command specifications described in the user manual's AT command explanation.**
1176 +
1177 +(% style="color:red" %)**For example, the HEX-format downlink command corresponding to AT+TDC can only be used to configure TDC and cannot be used for queries. There is no HEX-format downlink command equivalent to AT+TDC=? , so querying TDC via downlink is not supported.**
1178 +
1179 +
1180 +== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.6 How to get the debug log for further analyze?(%%) ==
1181 +
1182 +
1183 +If user is not able to solve the connection issue, user can use below method and get the device log and send to Dragino (Support@dragino.cc) for further analyze.
1184 +
1185 +
1186 +(% class="lead" %)
1187 +Step1: Use Mobile Phone to connect device
1188 +
1189 +See this link: **[[how to connect via Mobile Phone:>>https://wiki.dragino.com/xwiki/bin/view/Main/BLE%20Bluetooth%20Remote%20Configure/#H3.1UseDraginoDeviceTooltoconfigureorupgradefirmware]]**
1190 +
1191 +
1192 +(% class="lead" %)
1193 +Step2: Get Log by different commands.
1194 +
1195 +Use below three method to generate logs.
1196 +
1197 +* **AT+CFG       ~-~-> Command to show the current configuration**
1198 +* **AT** **+GETLOG   ~-~-> Command to get the previous upstream log**
1199 +* **press the toggle button for 1 ~~2 seconds     ~-~-> Trigger a uplink**
1200 +
1201 +Above are the output example for about three action:
1202 +
1203 +[[image:image-20250121235119-1.png||height="493" width="455"]]
1204 +
1205 +[[image:image-20240207002129-2.png]]
1206 +
1207 +
1208 +(% class="lead" %)
1209 +Step3: Export Log
1210 +
1211 +[[image:https://wiki.dragino.com/xwiki/bin/download/Main/BLE%20Bluetooth%20Remote%20Configure/WebHome/image-20241230155425-16.png?width=330&height=85&rev=1.1||alt="image-20241230155425-16.png" height="85" width="330"]]
1212 +
1213 +select the log you want to export, then click the share icon on the far right to enter the document that comes with your phone and choose to export it.
1214 +
1215 +[[image:https://wiki.dragino.com/xwiki/bin/download/Main/BLE%20Bluetooth%20Remote%20Configure/WebHome/image-20241230155528-17.png?width=327&height=324&rev=1.1||alt="image-20241230155528-17.png" height="324" width="327"]]
1216 +
1217 +
1218 +== 6.7 How to find the AT Command Password if lost? ==
1219 +
1220 +
1221 +=== Why can't the password access AT command after upgrade(-NB)? ===
1222 +
1223 +
1224 +Because the new version of -NB firmware has updated the factory reset function, users can choose to restore all parameters to factory Settings, or keep the password to restore the rest of the parameters to factory Settings.
1225 +
1226 +This update changes the password address of the firmware, so the password will be invalid after the customer upgrades from the old version of firmware (without FDR1 function) to the new version of firmware (with FDR1 function).
1227 +
1228 +Two different restore factory Settings configurations.
1229 +
1230 +(% style="color:blue" %)**AT command:**
1231 +
1232 +* (% style="color:#037691; font-weight:bold" %)**AT+FDR**(%%)**       **~/~/ Reset Parameters to Factory Default.
1233 +* (% style="color:#037691; font-weight:bold" %)**AT+FDR1**(%%)**     **~/~/ Reset parameters to factory default values except for passwords.(new)
1234 +
1235 +=== Version Confirmation ===
1236 +
1237 +
1238 +We are now dividing the **old firmware**(without FDR1 function) with the **new firmware**(with FDR1 function) by whether it contains FDR1 functionality. Please refer to the table:
1239 +
1240 +(% border="1" style="background-color:#f2f2f2; width:912px" %)
1241 +|(% style="background-color:#4f81bd; color:white; width:306px" %)**General Model**|(% style="background-color:#4f81bd; color:white; width:311px" %)(((
1242 +**Firmware version (without FDR1 function)**
1243 +)))|(% style="background-color:#4f81bd; color:white; width:289px" %)(((
1244 +**Firmware version (with FDR1 function)**
1245 +)))
1246 +|(% style="width:306px" %)(((
1247 +CPL03-NB, S31-NB, SN50V3-NB, TS01-NB, D20-NB, DS03A-NB, DDS04-NB, DDS45-NB, DDS20-NB, DDS75-NB, LDS12-NB, LDS40-NB, LMS01-NB, MDS120-NB,  MDS200-NB, SE01-NB, SPH01-NB;
1248 +)))|(% style="width:311px" %)Before V1.2.1|(% style="width:289px" %)After V1.2.1 (including V1.2.1)
1249 +|(% style="width:306px" %)(((
1250 +WL03A-NB, SDI-12-NB;
1251 +)))|(% style="width:311px" %)Before V1.0.2|(% style="width:289px" %)(((
1252 +After V1.0.8 (including V1.0.2)
1253 +)))
1254 +|(% style="width:306px" %)(((
1255 +SW3L-NB, PS-NB;
1256 +)))|(% style="width:311px" %)Before V1.0.5|(% style="width:289px" %)(((
1257 +After V1.0.5 (including V1.0.5)
1258 +)))
1259 +|(% style="width:306px" %)RS485-NB|(% style="width:311px" %)Before V1.0.8|(% style="width:289px" %)After V1.0.8 (including V1.0.8)
1260 +
1261 +=== UART connection and firmware update methods ===
1262 +
1263 +
1264 +Users can query passwords only using the UART interface via the STM32CubeProgrammer.
1265 +
1266 +See **[[UART Connection>>url:http://wiki.dragino.com/xwiki/bin/view/Main/UART%20Access%20for%20LoRa%20ST%20v4%20base%20model/#H2.3UARTConnectionforSN50v3basemotherboard]]**.
1267 +
1268 +update firmware through UART TTL interface :** [[Instruction>>url:http://wiki.dragino.com/xwiki/bin/view/Main/UART_Access_for_NB_ST_BC660K-GL/#H4.2UpdateFirmware28Assumethedevicealreadyhaveabootloader29]]**.
1269 +
1270 +
1271 +=== query the password via STM32CubeProgrammer ===
1272 +
1273 +
1274 +Users can use the password address to query the password through STM32CubeProgrammer.
1275 +
1276 +* The password address for old firmware(without FDR1 function) : **0x08019000**
1277 +* The password address for new firmware(with FDR1 function) : **0x08025D00**
1278 +
1279 +(% style="color:red" %)**Notice: The password can only be queried after the firmware is run once.**
1280 +
1281 +
1282 +**Procedure for querying the password(old firmware):**
1283 +
1284 +* After the firmware upgrade is complete, switch back to the **FLASH** and reset the node to **run the firmware once**.
1285 +* Then place the switch at the **ISP** and connect to the STM32CubeProgrammer (same as when burning the firmware).
1286 +* Click "Device memory", enter **0x08019000** in "Address", and click "Read"
1287 +* Find the 0x08019000 address field and then read the current password as shown in the screenshot below.
1288 +
1289 +[[image:http://wiki.dragino.com/xwiki/bin/download/Why%20can%27t%20the%20password%20access%20AT%20command%20after%20upgrade%28-NB%29%3F/WebHome/image-20240827171901-3.png?width=912&height=528&rev=1.1||alt="image-20240827171901-3.png"]]
1290 +
1291 +
1292 +**Procedure for querying the password(new firmware):**
1293 +
1294 +Refer to [[the old and new firmware division>>http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#HVersionConfirmation]] above, and run the firmware first after updating the firmware.
1295 +
1296 +* After the firmware upgrade is complete, switch back to the **FLASH** and reset the node to **run the new firmware once**.
1297 +* Then place the switch at the **ISP** and connect to the STM32CubeProgrammer (same as when burning the firmware).
1298 +* Click "Device memory", enter **0x08025D00** in "Address", and click "Read"
1299 +* Find the 0x08025D00 address field and then read the current password as shown in the screenshot below.
1300 +
1301 +[[image:http://wiki.dragino.com/xwiki/bin/download/Why%20can%27t%20the%20password%20access%20AT%20command%20after%20upgrade%28-NB%29%3F/WebHome/image-20240827180414-1.png?width=910&height=527&rev=1.1||alt="image-20240827180414-1.png"]]
1302 +
1303 +
1304 +=== Special case ===
1305 +
1306 +
1307 +If the user has never changed the password manually, the user cannot find the valid password through the above two password addresses. In this case, the valid password is still the original password on the node box label (**AT+PIN**).
1308 +
1309 +Invalid query screenshot example:
1310 +
1311 +[[image:http://wiki.dragino.com/xwiki/bin/download/Why%20can%27t%20the%20password%20access%20AT%20command%20after%20upgrade%28-NB%29%3F/WebHome/image-20240827181447-4.png?width=889&height=519&rev=1.1||alt="image-20240827181447-4.png"]]
1312 +
1313 +[[image:http://wiki.dragino.com/xwiki/bin/download/Why%20can%27t%20the%20password%20access%20AT%20command%20after%20upgrade%28-NB%29%3F/WebHome/image-20240827181431-3.png?width=892&height=515&rev=1.1||alt="image-20240827181431-3.png"]]
1314 +
1315 +
1316 +
1317 +== 6.8 ==
1318 +
1319 +
1320 +
1321 +
1322 +
1323 +
1324 +
1750035004731-376.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +55.1 KB
Content
1750035991532-434.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +54.4 KB
Content
1751538862245-924.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +114.7 KB
Content
1753258256594-216.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +153.1 KB
Content
1753258480811-335.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +110.5 KB
Content
1753258821265-310.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +189.0 KB
Content
image-20240701114700-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +291.5 KB
Content
image-20240729141300-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.kai
Size
... ... @@ -1,0 +1,1 @@
1 +176.9 KB
Content
image-20240729142505-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.kai
Size
... ... @@ -1,0 +1,1 @@
1 +202.0 KB
Content
image-20240729144058-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.kai
Size
... ... @@ -1,0 +1,1 @@
1 +140.7 KB
Content
image-20240729150142-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.kai
Size
... ... @@ -1,0 +1,1 @@
1 +128.0 KB
Content
image-20240729160802-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.kai
Size
... ... @@ -1,0 +1,1 @@
1 +162.8 KB
Content
image-20240729161543-9.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.kai
Size
... ... @@ -1,0 +1,1 @@
1 +166.8 KB
Content
image-20240729172234-11.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.kai
Size
... ... @@ -1,0 +1,1 @@
1 +57.8 KB
Content
image-20240729172305-12.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.kai
Size
... ... @@ -1,0 +1,1 @@
1 +49.3 KB
Content
image-20240729172415-13.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.kai
Size
... ... @@ -1,0 +1,1 @@
1 +54.3 KB
Content
image-20240729172500-14.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.kai
Size
... ... @@ -1,0 +1,1 @@
1 +48.6 KB
Content
image-20241126175509-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +241.0 KB
Content
image-20241126180135-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +192.8 KB
Content
image-20241126180223-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +213.1 KB
Content
image-20241126181024-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +238.8 KB
Content
image-20241126181837-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +106.7 KB
Content
image-20241126182007-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +136.3 KB
Content
image-20241126182135-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +91.3 KB
Content
image-20241126183032-8.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +111.4 KB
Content
image-20241126183803-9.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +54.1 KB
Content
image-20241126184136-10.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +15.7 KB
Content
image-20241126184211-11.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +22.3 KB
Content
image-20241126184303-12.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +81.7 KB
Content
image-20241126184523-13.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +88.7 KB
Content
image-20241126184906-14.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +108.0 KB
Content
image-20241126190131-15.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +267.9 KB
Content
image-20241126190251-16.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +94.2 KB
Content
image-20241126190737-17.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +253.7 KB
Content
image-20241126191118-18.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +61.4 KB
Content
image-20241126192009-19.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +113.6 KB
Content
image-20241126192122-20.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +105.2 KB
Content
image-20241126192130-21.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +105.2 KB
Content
image-20241126192246-22.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +87.7 KB
Content
image-20241126192315-23.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +99.0 KB
Content
image-20241126192415-24.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +88.2 KB
Content
image-20241126193252-25.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +64.2 KB
Content
image-20241126193458-26.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +144.3 KB
Content
image-20241126193609-27.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +167.5 KB
Content
image-20241126194018-28.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +63.5 KB
Content
image-20241126194123-29.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +126.7 KB
Content
image-20250121235119-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +145.4 KB
Content