Summary

• Page properties (1 modified, 0 added, 0 removed)
• Attachments (0 modified, 19 added, 0 removed)
  • image-20240820112908-59.png
  • image-20240820113015-60.png
  • image-20240820140935-1.png
  • image-20240820141136-2.png
  • image-20240820141746-1.png
  • image-20240820141843-2.png
  • image-20240820143316-3.png
  • image-20240820143820-4.png
  • image-20240820144823-5.png
  • image-20240820144913-6.png
  • image-20240820145133-7.png
  • image-20240820145309-8.png
  • image-20240827145055-4.png
  • image-20240827150121-5.png
  • image-20240827150705-6.png
  • image-20240903094214-1.png
  • image-20240903094457-2.png
  • image-20240903100736-3.png
  • image-20240903100832-4.png

Details

Page properties

Content

...	...	@@ -201,7 +201,7 @@
201	201
202	202	* (% style="color:#037691" %)**AT+PRO=2,0**  (%%) ~/~/ Set to use UDP protocol to uplink ,Payload Type select Hex payload
203	203
204		-* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601**  (%%) ~/~/ Set UDP server address and port
	204	+* (% style="color:#037691" %)**AT+SERVADDR=8.217.91.207,1999**  (%%) ~/~/ Set UDP server address and port
205	205
206	206	[[image:image-20240819102802-1.png]]
207	207
...	...	@@ -614,13 +614,13 @@
614	614
615	615	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.
616	616
617		-[[image:image-20230802112413-44.png]]
	617	+[[image:image-20240820112516-41.png]]
618	618
619		-[[image:image-20230802112413-45.png]]
	619	+[[image:image-20240820112526-42.png]]
620	620
621	621	Go to the Device section and create a device. Then, go to the section tokens and copy your device-token.
622	622
623		-[[image:image-20230802112413-46.png]]
	623	+[[image:image-20240820112539-43.png]]
624	624
625	625	The device needs to enable the TLS mode and set the (% style="color:blue" %)**AT+TLSMOD=1,0**(%%) command.
626	626
...	...	@@ -660,21 +660,21 @@
660	660
661	661	=== 3.7.2 Simulate with MQTT.fx ===
662	662
663		-[[image:image-20230802112413-52.png]]
	663	+[[image:image-20240820112552-44.png]]
664	664
665		-[[image:image-20230808105300-2.png||height="553" width="1026"]]
	665	+[[image:image-20240820112604-45.png]]
666	666
667	667	Users can run the (% style="color:blue" %)**AT+PRO=3,5**(%%) command, and the payload will be converted to **JSON format**.
668	668
669		-[[image:image-20230808105217-1.png||height="556" width="1031"]]
	669	+[[image:image-20240820112615-46.png]]
670	670
671		-[[image:image-20230808105329-3.png]]
	671	+[[image:image-20240820112626-47.png]]
672	672
673	673	=== 3.7.3 tago data ===
674	674
675		-[[image:image-20230802112413-50.png||height="242" width="1037"]]
	675	+[[image:image-20240820112637-48.png]]
676	676
677		-[[image:image-20230802112413-51.png||height="184" width="696"]]
	677	+[[image:image-20240820112647-49.png]]
678	678
679	679	== 3.8 TCP Connection ==
680	680
...	...	@@ -688,16 +688,18 @@
688	688
689	689	(% style="color:blue" %)**Sensor Console Output when Uplink:**
690	690
691		-[[image:image-20230807233631-1.png]]
	691	+[[image:image-20240820112704-50.png]]
692	692
693	693	(% style="color:blue" %)**See result in TCP Server:**
694	694
695		-[[image:image-20230807233631-2.png]]
	695	+[[image:image-20240820112716-51.png]]
696	696
697	697	== 3.9 AWS Connection ==
698	698
699	699	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]]
700	700
	701	+= =
	702	+
701	701	= 4. COAP/UDP/MQTT/TCP downlink =
702	702
703	703	== 4.1 MQTT (via MQTT.fx) ==
...	...	@@ -722,11 +722,11 @@
722	722
723	723	(% style="color:red" %)**Note: To uplink and downlink via MQTT.fx, we need set the publish topic and subscribe topic different, for example: AT+SUBTOPIC=SE01_SUB & AT+PUBTOPIC=SE01_PUB.**
724	724
725		-[[image:image-20240417180145-2.png||height="434" width="587"]][[ width="584">> width="584"]]
	727	+[[image:image-20240820112732-52.png]][[image:image-20240820112758-53.png]]
726	726
727	727	**2. **When the node uplink packets, we can observe the data in MQTT.fx.
728	728
729		-[[image:image-20240418144337-1.png||height="709" width="802"]]
	731	+[[image:image-20240820112813-54.png]]
730	730
731	731	**3. **The downlink command can be successfully sent only when the downlink port is open.
732	732
...	...	@@ -734,12 +734,42 @@
734	734
735	735	Therefore, when we see the node uplink packets in the **Subscribe** window, we need to immediately switch to the **publish** window to publish the **hex format** command.
736	736
737		-[[image:image-20240418150435-3.png||height="582" width="659"]]
	739	+[[image:image-20240820112824-55.png]]
738	738
739		-[[image:image-20240418150932-4.png||height="492" width="1061"]]
	741	+[[image:image-20240820112835-56.png]]
740	740
741	741	(% 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.**
742	742
	745	+
	746	+== 4.2 UDP (via Thingseye) ==
	747	+
	748	+(% style="color:red" %)**Note:**(%%) The UDP service on the ThingsEye platform needs to be built by the user. (Description Link:[[UDP service building instructions>>http://www.ithingsboard.com/docs/user-guide/integrations/udp/]])
	749	+
	750	+After the node is successfully connected to the platform, you need to select the corresponding node (you can refer to the node's IMEI to find it)
	751	+
	752	+[[image:image-20240820141843-2.png||height="546" width="821"]]
	753	+
	754	+After clicking Show Node Details Page, (% style="color:blue" %)**Select Properties ~-~-- select Shared Properties ~-~-- click Add Properties**
	755	+
	756	+[[image:image-20240820143316-3.png||height="555" width="1170"]]
	757	+
	758	+After clicking Add Shared Attribute, set the key to (% style="color:red" %)**value**(%%), and write the command that needs to be downlinked in the Downlink Command Input box
	759	+
	760	+(% style="color:red" %)**(Note: Downlinks can only be downlinked in string format, otherwise the node will not recognize the downlink command.)**
	761	+
	762	+[[image:image-20240820143820-4.png||height="554" width="1168"]]
	763	+
	764	+After the command is successfully added, the platform will send the command down on the node's next uplink.
	765	+
	766	+[[image:image-20240820144913-6.png||height="585" width="1232"]]
	767	+
	768	+[[image:image-20240820145133-7.png||height="582" width="1227"]]
	769	+
	770	+Upon successful issuance, the platform automatically eliminates the attributes from the queue and waits for the next addition of new attributes
	771	+
	772	+[[image:image-20240820145309-8.png]]
	773	+
	774	+
743	743	= 5. GPS positioning function =
744	744
745	745	=== 1. Turn on GPS function ===
...	...	@@ -782,7 +782,7 @@
782	782
783	783	The firmware version released after 2024, Mar will use change back to use Json format. Detail please check changelog.
784	784
785		-[[image:image-20240229233154-1.png]]
	817	+[[image:image-20240820112848-57.png]]
786	786
787	787	= 6. Trouble Shooting: =
788	788
...	...	@@ -792,11 +792,11 @@
792	792
793	793	If end device successfully attached NB-IoT Network, User can normally see the signal strengh as below (between 0~~31)
794	794
795		-[[image:image-20240207002003-1.png]]
	827	+[[image:image-20240820112859-58.png]]
796	796
797	797	If fail to attach network, it will shows signal 99. as below:
798	798
799		-[[image:image-20240207002129-2.png]]
	831	+[[image:image-20240820112908-59.png]]
800	800
801	801	(% class="lead" %)
802	802	When see this issue, below are the checklist:
...	...	@@ -810,13 +810,13 @@
810	810	If you have check all above and still fail. please send console log files (as many as possible) to [[support@dragino.com>>mailto:support@dragino.com]] so we can check.
811	811
812	812
813		-== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.4 Why sometime the AT Command is slow in reponse?(%%) ==
	845	+== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.2 Why sometime the AT Command is slow in reponse?(%%) ==
814	814
815	815	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.
816	816
817		-[[image:image-20240226111928-1.png]]
	849	+[[image:image-20240820113015-60.png]]
818	818
819		-== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.5 What is the Downlink Command by the NB device?(%%) ==
	851	+== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.3 What is the Downlink Command by the -CB device?(%%) ==
820	820
821	821	(% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %)
822	822	=== UDP: ===
...	...	@@ -868,5 +868,125 @@
868	868
869	869	[[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/]]
870	870
	903	+
	904	+== 6.4 What if the signal is good but the domain name resolution fails? ==
	905	+
	906	+
	907	+If the domain name resolution fails, first check whether the domain name is correct, users can use their own website domain name resolution tool to verify the domain name.
	908	+
	909	+[[image:image-20240827150705-6.png||height="489" width="687"]]
	910	+
	911	+If the domain name is correct, but the domain name cannot be resolved, the user can turn off the domain name resolution function(AT+GDNS=1) and use the domain name communication directly.
	912	+
	913	+* Set the DNS
	914	+
	915	+(% style="color:blue" %)**AT Command: AT+GDNS**
	916	+
	917	+**AT+GDNS=0**  ~/~/Default. Automatically resolves the domain name and uses the resolved IP to communicate.
	918	+
	919	+**AT+GDNS=1    **~/~/Disabling Domain name resolution. Use the domain name directly to communicate.
	920	+
	921	+(% style="color:red" %)**Note: For -CB products, with the exception of AT+PRO=2,5, all protocols and payload formats support direct domain communication.**
	922	+
	923	+Example:
	924	+
	925	+[[image:image-20240827150121-5.png||height="476" width="680"]][[image:image-20240827145055-4.png||height="484" width="678"]]
	926	+
	927	+
	928	+== 6.5 GPS debugging ==
	929	+
	930	+
	931	+Indoor GPS signal is very weak, outdoor positioning is generally recommended.
	932	+
	933	+=== 6.5.1 GPS commands ===
	934	+
	935	+
	936	+The following are three related AT commands that introduce GPS functions.
	937	+
	938	+* **Turn on/off GPS**
	939	+
	940	+(% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+GPS **
	941	+
	942	+**Ex1:  **AT+GPS=0  ~/~/ Turn off GPS
	943	+
	944	+**Ex2:  **AT+GPS=1  ~/~/ Turn on GPS
	945	+
	946	+(% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x11(%%)**
	947	+
	948	+Format: Command Code (0x11) followed by 1 byte.
	949	+
	950	+Example:  Downlink Payload: **11 01   **~/~/ AT+GPS=1
	951	+
	952	+* **Set GNSS open time**
	953	+
	954	+Extend the time to turn on GNSS. The automatic GPS location time is extended when the node is activated.
	955	+
	956	+(% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+GNSST**
	957	+
	958	+Example: AT+GNSST=30  ~/~/ Set the GPS positioning time to 30 seconds
	959	+
	960	+(% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x10(%%)**
	961	+
	962	+Format: Command Code (0x10) followed by 2 bytes.
	963	+
	964	+Example:  Downlink Payload: **10 00 1E    **~/~/ AT+GNSST=30
	965	+
	966	+* **Set GPS positioning interval**
	967	+
	968	+Feature: Set GPS positioning interval (unit: hour).
	969	+
	970	+When GPS is enabled, the node automatically locates and uplinks each time it passes **GTDC time** after activation.
	971	+
	972	+(% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+GTDC**
	973	+
	974	+Example: AT+GTDC=24  ~/~/ Set the GPS positioning interval to 24h.
	975	+
	976	+(% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x12(%%)**
	977	+
	978	+Format: Command Code (0x12) followed by 3 bytes.
	979	+
	980	+Example: 24 hours:  24(D)=0x18(H)
	981	+
	982	+ Downlink Payload: **12 00 00 18   **~/~/ AT+GTDC=24
	983	+
	984	+
	985	+=== 6.5.2 GPS workflow ===
	986	+
	987	+
	988	+The whole working process after the GPS function is enabled((% style="color:#037691" %)**AT+GPS=1**(%%)) is as follows:
	989	+
	990	+~1. When activate the node, the node will turn on the GNSS, if the GPS signal is good, the node will print and upload the position information with the first data packet immediately.
	991	+
	992	+ If the signal is not good, it may take the whole (% style="color:#037691" %)**GNSST**(%%) time but still can not search the latitude and longitude information, at this time the node uploads the latitude and longitude all to 0.
	993	+
	994	+ So if there is a failure of positioning, the user can extend the (% style="color:#037691" %)**GNSST**(%%) time appropriately.
	995	+
	996	+2. Each TDC time node is not repositioned and the positioning interval is determined by the AT+GTDC time.
	997	+
	998	+ The latitude and longitude payload uplinked at each TDC time is the GPS positioning information from the previous (% style="color:#037691" %)**GTDC**(%%) time.
	999	+
	1000	+ Only when the node is activated or every (% style="color:#037691" %)**GTDC**(%%) time is reached, the node turns on the GNSS and we can observe the GPS search information through the serial assistant or Bluetooth tool.
	1001	+
	1002	+
	1003	+=== 6.5.3 GPS debugging methods ===
	1004	+
	1005	+
	1006	+In summary, we can deduce the method of debugging GPS:
	1007	+
	1008	+* **Check whether the GPS antenna is loose**.
	1009	+
	1010	+If the GPS antenna is loose, the GPS signal is weak, and the positioning fails.
	1011	+
	1012	+[[image:image-20240903094214-1.png||height="340" width="461"]]
	1013	+
	1014	+* **Use the AT+GNSST command to extend the positioning time.**
	1015	+
	1016	+The default AT+GNSST=30, that is, the default positioning time is 30 seconds.
	1017	+
	1018	+If the location fails, users can extend the location time.
	1019	+
	1020	+
	1021	+
	1022	+
	1023	+
871	871
872		-​

image-20240820112908-59.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+17.9 KB

Content

image-20240820113015-60.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+52.0 KB

Content

image-20240820140935-1.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+159.2 KB

Content

image-20240820141136-2.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+107.6 KB

Content

image-20240820141746-1.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+122.2 KB

Content

image-20240820141843-2.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+123.2 KB

Content

image-20240820143316-3.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+152.3 KB

Content

image-20240820143820-4.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+161.7 KB

Content

image-20240820144823-5.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+145.6 KB

Content

image-20240820144913-6.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+136.4 KB

Content

image-20240820145133-7.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+164.5 KB

Content

image-20240820145309-8.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+32.6 KB

Content

image-20240827145055-4.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+74.2 KB

Content

image-20240827150121-5.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+86.0 KB

Content

image-20240827150705-6.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+86.7 KB

Content

image-20240903094214-1.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+4.5 MB

Content

image-20240903094457-2.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+2.6 MB

Content

image-20240903100736-3.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+250.8 KB

Content

image-20240903100832-4.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+181.5 KB

Content