Summary

• Page properties (1 modified, 0 added, 0 removed)

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=8.217.91.207,1999**  (%%) ~/~/ Set UDP server address and port
	204	+* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601**  (%%) ~/~/ Set UDP server address and port
205	205
206	206	[[image:image-20240819102802-1.png]]
207	207
...	...	@@ -698,6 +698,7 @@
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	+(% class="wikigeneratedid" %)
701	701	= =
702	702
703	703	= 4. COAP/UDP/MQTT/TCP downlink =
...	...	@@ -745,33 +745,9 @@
745	745
746	746	== 4.2 UDP (via Thingseye) ==
747	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	+(% style="color:red" %)**Note:**(%%) The UDP service on the ThingsEye platform needs to be built by the user.
749	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	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		-
775	775	= 5. GPS positioning function =
776	776
777	777	=== 1. Turn on GPS function ===
...	...	@@ -848,7 +848,7 @@
848	848
849	849	[[image:image-20240820113015-60.png]]
850	850
851		-== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.3 What is the Downlink Command by the -CB device?(%%) ==
	828	+== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.3 What is the Downlink Command by the NB device?(%%) ==
852	852
853	853	(% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %)
854	854	=== UDP: ===
...	...	@@ -902,31 +902,3 @@
902	902
903	903
904	904	​
905		-
906		-== 6.4 What if the signal is good but the domain name resolution fails? ==
907		-
908		-
909		-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.
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		-
926		-
927		-
928		-
929		-
930		-
931		-
932		-