Skip to Content
Last modified by Kilight Cao on 2025/07/23 16:27
From version 223.1
edited by Edwin Chen
on 2025/01/21 23:55
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.Edwin
1 +XWiki.Kilight
Content
... ... @@ -394,11 +394,66 @@
394 394  (% style="color:blue" %)**AT+SERVADDR=67.207.76.90,4445**
395 395  
396 396  
397 -== 3.5 Node-Red (via MQTT) ==
397 +== 3.5 Telemetry2U ==
398 398  
399 -=== 3.5.1 Configure [[Node-Red>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/]] ===
400 400  
400 +=== Configuring the Dragino NB Sensor Settings ===
401 401  
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 +
402 402  Take S31-NB UDP protocol as an example.
403 403  
404 404  Dragino provides input flow examples for the sensors.
... ... @@ -434,7 +434,7 @@
434 434  [[image:image-20230809174053-9.png]]
435 435  
436 436  
437 -=== 3.5.2 Simulate Connection ===
492 +=== 3.6.2 Simulate Connection ===
438 438  
439 439  
440 440  We have completed the configuration of UDP. We can try sending packets to node red.
... ... @@ -444,7 +444,7 @@
444 444  [[image:image-20230810084048-2.png||height="535" width="1052"]]
445 445  
446 446  
447 -=== 3.5.3 Configure NB-IoT Sensors ===
502 +=== 3.6.3 Configure NB-IoT Sensors ===
448 448  
449 449  
450 450  * (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%) **~/~/ hex format or json format**
... ... @@ -454,11 +454,11 @@
454 454  * (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
455 455  * (% style="color:#037691" %)**AT+PWD=“Your device token”**
456 456  
457 -== 3.6 ThingsBoard.Cloud (via MQTT) ==
512 +== 3.7 ThingsBoard.Cloud (via MQTT) ==
458 458  
459 -=== 3.6.1 Configure ThingsBoard ===
514 +=== 3.7.1 Configure ThingsBoard ===
460 460  
461 -==== 3.6.1.1 Create Device ====
516 +==== 3.7.1.1 Create Device ====
462 462  
463 463  
464 464  Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]]. Record Device Name which is used for MQTT connection.
... ... @@ -466,7 +466,7 @@
466 466  [[image:image-20230802112413-32.png||height="583" width="1066"]]
467 467  
468 468  
469 -==== 3.6.1.2 Create Uplink & Downlink Converter ====
524 +==== 3.7.1.2 Create Uplink & Downlink Converter ====
470 470  
471 471  
472 472  (% style="color:blue" %)**Uplink Converter**
... ... @@ -487,7 +487,7 @@
487 487  (% style="color:red" %)**Note: Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default.**
488 488  
489 489  
490 -==== 3.6.1.3 MQTT Integration Setup ====
545 +==== 3.7.1.3 MQTT Integration Setup ====
491 491  
492 492  
493 493  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**;
... ... @@ -518,7 +518,7 @@
518 518  [[image:image-20230802112413-40.png||height="525" width="980"]]
519 519  
520 520  
521 -=== 3.6.3 Configure NB-IoT Sensor ===
576 +=== 3.7.3 Configure NB-IoT Sensor ===
522 522  
523 523  
524 524  (% style="color:blue" %)**AT Commands**
... ... @@ -544,11 +544,11 @@
544 544  [[image:image-20230802112413-43.png||height="407" width="825"]]
545 545  
546 546  
547 -== 3.7 ThingsBoard.Cloud (via COAP) ==
602 +== 3.8 ThingsBoard.Cloud (via COAP) ==
548 548  
549 -=== 3.7.1 Configure ThingsBoard ===
604 +=== 3.8.1 Configure ThingsBoard ===
550 550  
551 -==== 3.7.1.1 Create Uplink & Downlink Converter ====
606 +==== 3.8.1.1 Create Uplink & Downlink Converter ====
552 552  
553 553  
554 554  (% style="color:blue" %)**Uplink Converter**
... ... @@ -567,7 +567,7 @@
567 567  [[image:image-20240729142505-3.png||height="507" width="1023"]]
568 568  
569 569  
570 -==== 3.7.1.2 COAP Integration Setup ====
625 +==== 3.8.1.2 COAP Integration Setup ====
571 571  
572 572  
573 573  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" %);
... ... @@ -580,7 +580,7 @@
580 580  [[image:image-20240729150142-5.png||height="507" width="1023"]]
581 581  
582 582  
583 -==== 3.7.1.3 Add COAP Integration ====
638 +==== 3.8.1.3 Add COAP Integration ====
584 584  
585 585  
586 586  (% class="wikigeneratedid" id="H" %)
... ... @@ -587,9 +587,9 @@
587 587  [[image:image-20240729161543-9.png||height="500" width="1009"]]
588 588  
589 589  
590 -=== 3.7.2 Node Configuration(Example: Connecting to the Thingsboard platform) ===
645 +=== 3.8.2 Node Configuration(Example: Connecting to the Thingsboard platform) ===
591 591  
592 -==== 3.7.2.1 Instruction Description ====
647 +==== 3.8.2.1 Instruction Description ====
593 593  
594 594  
595 595  * AT+PRO=1,0(HEX format uplink)  &AT+PRO=1,5(JSON format uplink)
... ... @@ -602,31 +602,22 @@
602 602  Note:The port for the COAP protocol has been fixed to 5683
603 603  
604 604  
605 -* AT+URL1=11,(% style="color:red" %)**character length**(%%),"Needs to be consistent with the CoAP endpoint URL in the platform"
660 +* AT+URI1=11,(% style="color:red" %)**character length**(%%),"Needs to be consistent with the CoAP endpoint URL in the platform",
606 606  
607 -If the module used is (% style="color:red" %)**BC660K, only one **(%%)URL directive needs to be configured,
662 +-NB/NS products use the (% style="color:red" %)**BC660K**(%%) module, only need to configure (% style="color:red" %)**only one URL**(%%) command.
608 608  
609 609  e.g.
610 610  
611 -* AT+URL1=11,38, "i/faaaa241f-af4a-b780-4468-c671bb574858"
666 +* AT+URI1=11,38, "i/faaaa241f-af4a-b780-4468-c671bb574858"
612 612  
613 613  [[image:image-20240729172415-13.png||height="401" width="694"]]
614 614  
615 -If you are using a (% style="color:red" %)**BG95-M2**(%%) module, you need to configure (% style="color:red" %)**TWO**(%%) URL commands,
616 616  
617 -e.g.
671 +== 3.9 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
618 618  
619 -* AT+URL1=11, "i"
620 -* AT+URL2=11,"faaaa241f-af4a-b780-4468-c671bb574858"
673 +=== 3.9.1 Create device & Get Credentials ===
621 621  
622 -[[image:image-20240729172500-14.png||height="403" width="700"]]
623 623  
624 -
625 -== 3.8 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
626 -
627 -=== 3.8.1 Create device & Get Credentials ===
628 -
629 -
630 630  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.
631 631  
632 632  [[image:image-20230802112413-44.png]]
... ... @@ -675,7 +675,7 @@
675 675  
676 676  * (% style="color:#037691" %)**AT+PWD=“Your device token”**
677 677  
678 -=== 3.8.2 Simulate with MQTT.fx ===
724 +=== 3.9.2 Simulate with MQTT.fx ===
679 679  
680 680  
681 681  [[image:image-20230802112413-52.png]]
... ... @@ -691,7 +691,7 @@
691 691  [[image:image-20230808105329-3.png]]
692 692  
693 693  
694 -=== 3.8.3 tago data ===
740 +=== 3.9.3 tago data ===
695 695  
696 696  
697 697  [[image:image-20230802112413-50.png||height="242" width="1037"]]
... ... @@ -699,7 +699,7 @@
699 699  [[image:image-20230802112413-51.png||height="184" width="696"]]
700 700  
701 701  
702 -== 3.9 TCP Connection ==
748 +== 3.10 TCP Connection ==
703 703  
704 704  
705 705  (% style="color:blue" %)**AT command:**
... ... @@ -720,17 +720,17 @@
720 720  [[image:image-20230807233631-2.png]]
721 721  
722 722  
723 -== 3.10 AWS Connection ==
769 +== 3.11 AWS Connection ==
724 724  
725 725  
726 726  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]]
727 727  
728 728  
729 -== 3.11 ThingsEye (via MQTT) ==
775 +== 3.12 ThingsEye (via MQTT) ==
730 730  
731 -=== 3.11.1 Configure ThingsEye ===
777 +=== 3.12.1 Configure ThingsEye ===
732 732  
733 -==== 3.11.1.1 Create MQTT integration ====
779 +==== 3.12.1.1 Create MQTT integration ====
734 734  
735 735  
736 736  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**;
... ... @@ -756,7 +756,7 @@
756 756  [[image:image-20241126181024-4.png||height="521" width="1081"]]
757 757  
758 758  
759 -==== 3.11.1.2 Add credentials to the MQTT integration ====
805 +==== 3.12.1.2 Add credentials to the MQTT integration ====
760 760  
761 761  
762 762  Click on the MQTT integration you just created.
... ... @@ -782,7 +782,7 @@
782 782  [[image:image-20241126184211-11.png||height="161" width="977"]]
783 783  
784 784  
785 -==== 3.11.1.3 Setup uplink and downlink converters ====
831 +==== 3.12.1.3 Setup uplink and downlink converters ====
786 786  
787 787  
788 788  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]].
... ... @@ -811,7 +811,7 @@
811 811  [[image:image-20241126190737-17.png||height="527" width="1114"]]
812 812  
813 813  
814 -=== 3.11.2 Simulate with MQTT.fx ===
860 +=== 3.12.2 Simulate with MQTT.fx ===
815 815  
816 816  
817 817  [[image:image-20241126191118-18.png||height="605" width="835"]]
... ... @@ -819,7 +819,7 @@
819 819  [[image:image-20241126193252-25.png||height="663" width="803"]]
820 820  
821 821  
822 -=== 3.11.3 Configure -NB node ===
868 +=== 3.12.3 Configure -NB node ===
823 823  
824 824  
825 825  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.
... ... @@ -854,7 +854,7 @@
854 854  * (% style="color:#037691" %)**AT+CLIENT=NULL**
855 855  * (% style="color:#037691" %)**AT+UNAME=NULL**
856 856  * (% style="color:#037691" %)**AT+PWD=NULL**
857 -* (% style="color:#037691" %)**AT+TLSMOD=1,0**
903 +* (% style="color:#037691" %)**AT+TLSMOD=1,2**
858 858  
859 859  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:
860 860  
... ... @@ -1033,30 +1033,47 @@
1033 1033  [[image:image-20240226111928-1.png]]
1034 1034  
1035 1035  
1036 -== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.5 What is the Downlink Command by the NB device?(%%) ==
1082 +== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.5 (%%)What is the Downlink Command Format for NB Devices? ==
1037 1037  
1038 1038  
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 +
1039 1039  (% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %)
1040 -=== UDP: ===
1088 +=== **UDP Protocol:** ===
1041 1041  
1090 +Only supports valid **HEX-format downlink commands** corresponding to AT command.
1042 1042  
1043 -(% data-sider-select-id="14a4790e-7faa-4508-a4dd-7605a53f1cb3" %)
1044 -Its downlink command is the same as the AT command, but brackets are required.
1045 -Example:
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.
1046 1046  
1047 -{AT+TDC=300}
1095 +[[image:1750035991532-434.png||height="237" width="495"]]
1048 1048  
1049 1049  
1050 1050  (% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %)
1051 -=== MQTT: ===
1099 +=== **MQTT Protocol:** ===
1052 1052  
1101 +==== **1. HEX-format** ====
1053 1053  
1054 -Json：
1103 +Supports **HEX-format** downlink commands (corresponding to AT commands).
1055 1055  
1056 -The Json format in MQTT mode needs to be configured with all commands.
1057 -If you have configurations that need to be changed, please change them in the template below.
1058 -Template:
1105 +//Example~:// For the S31-NB's uplink interval modification (AT+TDC=900):
1059 1059  
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 +
1060 1060  {
1061 1061  "AT+SERVADDR":"119.91.62.30,1882",
1062 1062  "AT+CLIENT":"JwcXKjQBNhQ2JykDDAA5Ahs",
... ... @@ -1080,16 +1080,40 @@
1080 1080  "AT+TEMPALARM3":"0"
1081 1081  }
1082 1082  
1083 -Hex：
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.
1084 1084  
1085 -MQTT's hex format. Since many commands need to support strings, only a few commands are supported.
1148 +[[image:1751538862245-924.png]]
1086 1086  
1087 -The supported commands are consistent with LoRaWAN's hex commands.
1088 -Please refer to the following link to obtain the hex format:
1089 1089  
1090 -[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/>>http://wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/]]
1151 +**Instructions for Using the Template:**
1091 1091  
1153 +1. Modify the parameters for each AT command in the template as needed.
1154 +1. Send the entire template in one downlink command.
1092 1092  
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 +
1093 1093  == (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.6 How to get the debug log for further analyze?(%%) ==
1094 1094  
1095 1095  
... ... @@ -1111,7 +1111,6 @@
1111 1111  * **AT** **+GETLOG   ~-~-> Command to get the previous upstream log**
1112 1112  * **press the toggle button for 1 ~~2 seconds     ~-~-> Trigger a uplink**
1113 1113  
1114 -
1115 1115  Above are the output example for about three action:
1116 1116  
1117 1117  [[image:image-20250121235119-1.png||height="493" width="455"]]
... ... @@ -1151,30 +1151,26 @@
1151 1151  
1152 1152  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:
1153 1153  
1154 -(% border="1" style="background-color:#f2f2f2; width:510px" %)
1155 -|(% style="background-color:#4f81bd; color:white; width:210px" %)**General Model**|(% style="background-color:#4f81bd; color:white; width:150px" %)(((
1156 -**Firmware version**
1157 -
1158 -**(without FDR1 function)**
1159 -)))|(% style="background-color:#4f81bd; color:white; width:150px" %)(((
1160 -**Firmware version**
1161 -
1162 -**(with FDR1 function)**
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)**
1163 1163  )))
1164 -|(% style="width:210px" %)(((
1246 +|(% style="width:306px" %)(((
1165 1165  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;
1166 -)))|(% style="width:150px" %)Before V1.2.1|(% style="width:150px" %)After V1.2.1 (including V1.2.1)
1167 -|(% style="width:210px" %)(((
1248 +)))|(% style="width:311px" %)Before V1.2.1|(% style="width:289px" %)After V1.2.1 (including V1.2.1)
1249 +|(% style="width:306px" %)(((
1168 1168  WL03A-NB, SDI-12-NB;
1169 -)))|(% style="width:150px" %)Before V1.0.2|(% style="width:150px" %)(((
1251 +)))|(% style="width:311px" %)Before V1.0.2|(% style="width:289px" %)(((
1170 1170  After V1.0.8 (including V1.0.2)
1171 1171  )))
1172 -|(% style="width:210px" %)(((
1254 +|(% style="width:306px" %)(((
1173 1173  SW3L-NB, PS-NB;
1174 -)))|(% style="width:150px" %)Before V1.0.5|(% style="width:150px" %)(((
1256 +)))|(% style="width:311px" %)Before V1.0.5|(% style="width:289px" %)(((
1175 1175  After V1.0.5 (including V1.0.5)
1176 1176  )))
1177 -|(% style="width:210px" %)RS485-NB|(% style="width:150px" %)Before V1.0.8|(% style="width:150px" %)After V1.0.8 (including V1.0.8)
1259 +|(% style="width:306px" %)RS485-NB|(% style="width:311px" %)Before V1.0.8|(% style="width:289px" %)After V1.0.8 (including V1.0.8)
1178 1178  
1179 1179  === UART connection and firmware update methods ===
1180 1180  
... ... @@ -1232,4 +1232,11 @@
1232 1232  
1233 1233  
1234 1234  
1317 +== 6.8 ==
1318 +
1319 +
1320 +
1321 +
1322 +
1323 +
1235 1235  
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