Summary

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

Details

Page properties

Content

...	...	@@ -63,7 +63,6 @@
63	63	* Downlink to change configure
64	64	* 8500mAh Battery for long term use
65	65
66		-
67	67	== 1.3  Probe Specification ==
68	68
69	69	* Storage temperature ：-20℃~~75℃
...	...	@@ -79,7 +79,6 @@
79	79	* Material of enclosure - ABS+PC
80	80	* Wire length - 25cm
81	81
82		-
83	83	== 1.4  Probe Dimension ==
84	84
85	85
...	...	@@ -96,7 +96,6 @@
96	96	* Automatic control
97	97	* Sewer
98	98
99		-
100	100	== 1.6  Pin mapping and power on ==
101	101
102	102
...	...	@@ -303,7 +303,6 @@
303	303	|(% style="width:160px" %)0x01|(% style="width:163px" %)Normal Uplink|(% style="width:173px" %)[[Normal Uplink Payload>>||anchor="H2.3A0200BUplinkPayload"]]
304	304	|(% style="width:160px" %)0x02|(% style="width:163px" %)Reply configures info|(% style="width:173px" %)[[Configure Info Payload>>||anchor="H4.3A0GetFirmwareVersionInfo"]]
305	305
306		-
307	307	=== 2.3.8  Decode payload in The Things Network ===
308	308
309	309	While using TTN network, you can add the payload format to decode the payload.
...	...	@@ -472,7 +472,6 @@
472	472	* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
473	473	* Use the Join successful sub-band if the server doesn’t include sub-band info in the OTAA Join Accept message ( TTN v2 doesn't include)
474	474
475		-
476	476	=== 2.6.3  CN470-510 (CN470) ===
477	477
478	478	(((
...	...	@@ -583,7 +583,6 @@
583	583	* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
584	584	* Use the Join successful sub-band if the server doesn’t include sub-band info in the OTAA Join Accept message ( TTN v2 doesn't include)
585	585
586		-
587	587	=== 2.6.5  AS920-923 & AS923-925 (AS923) ===
588	588
589	589	(((
...	...	@@ -810,7 +810,6 @@
810	810	* The sensor is detected when the device is turned on, and it will flash 4 times quickly when it is detected.
811	811	* Blink once when device transmit a packet.
812	812
813		-
814	814	== 2.8  ​Firmware Change Log ==
815	815
816	816
...	...	@@ -882,81 +882,56 @@
882	882	* The sensor window is made by Acrylic. Don’t touch it with alcohol material. This will destroy the sensor window.
883	883
884	884
	878	+
885	885	= 4.  Configure LLDS12 via AT Command or LoRaWAN Downlink =
886	886
887	887	(((
888		-(((
889	889	Use can configure LLDS12 via AT Command or LoRaWAN Downlink.
890	890	)))
891		-)))
892	892
893	893	* (((
894		-(((
895	895	AT Command Connection: See [[FAQ>>||anchor="H7.A0FAQ"]].
896	896	)))
897		-)))
898	898	* (((
899		-(((
900	900	LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>doc:Main.WebHome]]
901	901	)))
902		-)))
903	903
904	904	(((
905		-(((
906	906
907		-)))
908	908
909		-(((
910	910	There are two kinds of commands to configure LLDS12, they are:
911	911	)))
912		-)))
913	913
914	914	* (((
915		-(((
916	916	(% style="color:#4f81bd" %)** General Commands**.
917	917	)))
918		-)))
919	919
920	920	(((
921		-(((
922	922	These commands are to configure:
923	923	)))
924		-)))
925	925
926	926	* (((
927		-(((
928	928	General system settings like: uplink interval.
929	929	)))
930		-)))
931	931	* (((
932		-(((
933	933	LoRaWAN protocol & radio related command.
934	934	)))
935		-)))
936	936
937	937	(((
938		-(((
939	939	They are same for all Dragino Device which support DLWS-005 LoRaWAN Stack. These commands can be found on the wiki: [[End Device AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]
940	940	)))
941		-)))
942	942
943	943	(((
944		-(((
945	945
946	946	)))
947		-)))
948	948
949	949	* (((
950		-(((
951	951	(% style="color:#4f81bd" %)** Commands special design for LLDS12**
952	952	)))
953		-)))
954	954
955	955	(((
956		-(((
957	957	These commands only valid for LLDS12, as below:
958	958	)))
959		-)))
960	960
961	961
962	962
...	...	@@ -969,6 +969,7 @@
969	969	[[image:image-20220607171554-8.png]]
970	970
971	971
	940	+
972	972	(((
973	973	(% style="color:#037691" %)**Downlink Command: 0x01**
974	974	)))
...	...	@@ -986,9 +986,11 @@
986	986	)))
987	987	* (((
988	988	Example 2: Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds
989		-)))
990	990
991	991
	960	+
	961	+)))
	962	+
992	992	== 4.2  Set Interrupt Mode ==
993	993
994	994	Feature, Set Interrupt mode for GPIO_EXIT.
...	...	@@ -1017,7 +1017,6 @@
1017	1017	Example 2: Downlink Payload: 06000003 ~/~/ Set the interrupt mode to rising edge trigger
1018	1018	)))
1019	1019
1020		-
1021	1021	== 4.3  Get Firmware Version Info ==
1022	1022
1023	1023	Feature: use downlink to get firmware version.
...	...	@@ -1214,14 +1214,10 @@
1214	1214
1215	1215
1216	1216	(((
1217		-(((
1218	1218	In the PC, you need to set the serial baud rate to (% style="color:green" %)**9600**(%%) to access the serial console for LLDS12.
1219		-)))
1220	1220
1221		-(((
1222	1222	LLDS12 will output system info once power on as below:
1223	1223	)))
1224		-)))
1225	1225
1226	1226
1227	1227	[[image:1654593712276-618.png]]
...	...	@@ -1242,9 +1242,7 @@
1242	1242	== 8.1  AT Commands input doesn’t work ==
1243	1243
1244	1244
1245		-(((
1246	1246	In the case if user can see the console output but can’t type input to the device. Please check if you already include the (% style="color:green" %)**ENTER**(%%) while sending out the command. Some serial tool doesn’t send (% style="color:green" %)**ENTER**(%%) while press the send key, user need to add ENTER in their string.
1247		-)))
1248	1248
1249	1249
1250	1250	== 8.2  Significant error between the output distant value of LiDAR and actual distance ==
...	...	@@ -1289,7 +1289,6 @@
1289	1289	* (% style="color:red" %)**IN865**(%%):  LoRaWAN IN865 band
1290	1290	* (% style="color:red" %)**CN470**(%%): LoRaWAN CN470 band
1291	1291
1292		-
1293	1293	= 10. ​ Packing Info =
1294	1294
1295	1295
...	...	@@ -1304,7 +1304,6 @@
1304	1304	* Package Size / pcs : cm
1305	1305	* Weight / pcs : g
1306	1306
1307		-
1308	1308	= 11.  ​Support =
1309	1309
1310	1310	* Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule.