Skip to Content
Last modified by Kilight Cao on 2025/07/23 16:27
From version 183.1
edited by Mengting Qiu
on 2024/08/28 14:44
Change comment: There is no comment for this version
To version 235.1
edited by Kilight Cao
on 2025/07/23 16:25
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
... ... @@ -45,6 +45,10 @@
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  
... ... @@ -390,6 +390,61 @@
390 390  (% style="color:blue" %)**AT+SERVADDR=67.207.76.90,4445**
391 391  
392 392  
397 +== 3.5 Telemetry2U ==
398 +
399 +
400 +=== Configuring the Dragino NB Sensor Settings ===
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 +
393 393  == 3.5 Node-Red (via MQTT) ==
394 394  
395 395  === 3.5.1 Configure [[Node-Red>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/]] ===
... ... @@ -509,7 +509,6 @@
509 509  
510 510  === 3.6.2 Simulate with MQTT.fx ===
511 511  
512 -
513 513  [[image:image-20230802112413-39.png]]
514 514  
515 515  [[image:image-20230802112413-40.png||height="525" width="980"]]
... ... @@ -580,7 +580,8 @@
580 580  ==== 3.7.1.3 Add COAP Integration ====
581 581  
582 582  
583 -==== [[image:image-20240729161543-9.png||height="500" width="1009"]] ====
641 +(% class="wikigeneratedid" id="H" %)
642 +[[image:image-20240729161543-9.png||height="500" width="1009"]]
584 584  
585 585  
586 586  === 3.7.2 Node Configuration(Example: Connecting to the Thingsboard platform) ===
... ... @@ -598,26 +598,17 @@
598 598  Note:The port for the COAP protocol has been fixed to 5683
599 599  
600 600  
601 -* 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",
602 602  
603 -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.
604 604  
605 605  e.g.
606 606  
607 -* AT+URL1=11,38, "i/faaaa241f-af4a-b780-4468-c671bb574858"
666 +* AT+URI1=11,38, "i/faaaa241f-af4a-b780-4468-c671bb574858"
608 608  
609 609  [[image:image-20240729172415-13.png||height="401" width="694"]]
610 610  
611 -If you are using a (% style="color:red" %)**BG95-M2**(%%) module, you need to configure (% style="color:red" %)**TWO**(%%) URL commands,
612 612  
613 -e.g.
614 -
615 -* AT+URL1=11, "i";  
616 -* AT+URL2=11,"/faaaa241f-af4a-b780-4468-c671bb574858"
617 -
618 -[[image:image-20240729172500-14.png||height="403" width="700"]]
619 -
620 -
621 621  == 3.8 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
622 622  
623 623  === 3.8.1 Create device & Get Credentials ===
... ... @@ -722,6 +722,152 @@
722 722  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]]
723 723  
724 724  
775 +== 3.11 ThingsEye (via MQTT) ==
776 +
777 +=== 3.11.1 Configure ThingsEye ===
778 +
779 +==== 3.11.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.11.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.11.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.11.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.11.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 +
725 725  = 4. MQTT/UDP/TCP downlink =
726 726  
727 727  == 4.1 MQTT (via MQTT.fx) ==
... ... @@ -782,8 +782,8 @@
782 782  1. Give more sampling data points.
783 783  1. Increase reliable in transmission. For example. If user set
784 784  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)
785 -1*. **AT+NOUD=24** ~/~/  The device uploads 24 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
786 -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.
787 787  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.
788 788  
789 789  == 5.2 Why the uplink JSON format is not standard? ==
... ... @@ -796,6 +796,14 @@
796 796  [[image:image-20240229233154-1.png]]
797 797  
798 798  
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 +
799 799  = 6. Trouble Shooting: =
800 800  
801 801  == 6.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
... ... @@ -875,27 +875,47 @@
875 875  [[image:image-20240226111928-1.png]]
876 876  
877 877  
878 -== (% 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? ==
879 879  
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 +
880 880  (% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %)
881 -=== UDP: ===
1088 +=== **UDP Protocol:** ===
882 882  
883 -(% data-sider-select-id="14a4790e-7faa-4508-a4dd-7605a53f1cb3" %)
884 -Its downlink command is the same as the AT command, but brackets are required.
885 -Example:
1090 +Only supports valid **HEX-format downlink commands** corresponding to AT command.
886 886  
887 -{AT+TDC=300}
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.
888 888  
1095 +[[image:1750035991532-434.png||height="237" width="495"]]
889 889  
1097 +
890 890  (% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %)
891 -=== MQTT: ===
1099 +=== **MQTT Protocol:** ===
892 892  
893 -Json：
1101 +==== **1. HEX-format** ====
894 894  
895 -The Json format in MQTT mode needs to be configured with all commands.
896 -If you have configurations that need to be changed, please change them in the template below.
897 -Template:
1103 +Supports **HEX-format** downlink commands (corresponding to AT commands).
898 898  
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 +
899 899  {
900 900  "AT+SERVADDR":"119.91.62.30,1882",
901 901  "AT+CLIENT":"JwcXKjQBNhQ2JykDDAA5Ahs",
... ... @@ -919,26 +919,78 @@
919 919  "AT+TEMPALARM3":"0"
920 920  }
921 921  
922 -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.
923 923  
924 -MQTT's hex format. Since many commands need to support strings, only a few commands are supported.
1148 +[[image:1751538862245-924.png]]
925 925  
926 -The supported commands are consistent with LoRaWAN's hex commands.
927 -Please refer to the following link to obtain the hex format:
928 928  
929 -[[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:**
930 930  
1153 +1. Modify the parameters for each AT command in the template as needed.
1154 +1. Send the entire template in one downlink command.
931 931  
932 -== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.6 How to obtain device logs?(%%) ==
1156 +(% style="color:red" %)**Note:**
933 933  
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.
934 934  
935 -* **AT Command: AT** **+GETLOG**
936 936  
937 -This command can be used to query upstream logs of data packets.
938 938  
939 -[[image:image-20240701114700-1.png]]
1163 +===== **2.2 Support sending json format commands separately** =====
940 940  
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.**
941 941  
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 +
942 942  == 6.7 How to find the AT Command Password if lost? ==
943 943  
944 944  
... ... @@ -958,32 +958,29 @@
958 958  
959 959  === Version Confirmation ===
960 960  
1237 +
961 961  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:
962 962  
963 -(% border="1" style="background-color:#f2f2f2; width:510px" %)
964 -|(% style="background-color:#4f81bd; color:white; width:210px" %)**General Model**|(% style="background-color:#4f81bd; color:white; width:150px" %)(((
965 -**Firmware version**
966 -
967 -**(without FDR1 function)**
968 -)))|(% style="background-color:#4f81bd; color:white; width:150px" %)(((
969 -**Firmware version**
970 -
971 -**(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)**
972 972  )))
973 -|(% style="width:210px" %)(((
1246 +|(% style="width:306px" %)(((
974 974  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;
975 -)))|(% style="width:150px" %)Before V1.2.1|(% style="width:150px" %)After V1.2.1 (including V1.2.1)
976 -|(% 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" %)(((
977 977  WL03A-NB, SDI-12-NB;
978 -)))|(% style="width:150px" %)Before V1.0.2|(% style="width:150px" %)(((
1251 +)))|(% style="width:311px" %)Before V1.0.2|(% style="width:289px" %)(((
979 979  After V1.0.8 (including V1.0.2)
980 980  )))
981 -|(% style="width:210px" %)(((
1254 +|(% style="width:306px" %)(((
982 982  SW3L-NB, PS-NB;
983 -)))|(% style="width:150px" %)Before V1.0.5|(% style="width:150px" %)(((
1256 +)))|(% style="width:311px" %)Before V1.0.5|(% style="width:289px" %)(((
984 984  After V1.0.5 (including V1.0.5)
985 985  )))
986 -|(% 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)
987 987  
988 988  === UART connection and firmware update methods ===
989 989  
... ... @@ -1028,7 +1028,6 @@
1028 1028  [[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"]]
1029 1029  
1030 1030  
1031 -
1032 1032  === Special case ===
1033 1033  
1034 1034  
... ... @@ -1036,7 +1036,6 @@
1036 1036  
1037 1037  Invalid query screenshot example:
1038 1038  
1039 -
1040 1040  [[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"]]
1041 1041  
1042 1042  [[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"]]
... ... @@ -1043,4 +1043,11 @@
1043 1043  
1044 1044  
1045 1045  
1317 +== 6.8 ==
1318 +
1319 +
1320 +
1321 +
1322 +
1323 +
1046 1046  
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-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