Summary

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

Details

Page properties

Content

...	...	@@ -83,7 +83,6 @@
83	83	* Packet engine up to 256 bytes with CRC
84	84
85	85
86		-
87	87	== 1.3 Features ==
88	88
89	89	* LoRaWAN Class A & Class C protocol (default Class C)
...	...	@@ -96,7 +96,6 @@
96	96	* Support Interrupt uplink (Since hardware version v1.2)
97	97
98	98
99		-
100	100	== 1.4 Applications ==
101	101
102	102	* Smart Buildings & Home Automation
...	...	@@ -107,7 +107,6 @@
107	107	* Smart Factory
108	108
109	109
110		-
111	111	== 1.5 Firmware Change log ==
112	112
113	113	[[RS485-LN Image files – Download link and Change log>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/]]
...	...	@@ -223,7 +223,7 @@
223	223
224	224	(((
225	225	(((
226		-There are plenty of RS485 devices in the market and each device has different command to read the valid data. To support these devices in flexible, RS485-LN supports flexible command set. User can use [[AT Commands>>path:#AT_COMMAND]] or LoRaWAN Downlink Command to configure what commands RS485-LN should send for each sampling and how to handle the return from RS485 devices.
	223	+There are plenty of RS485 devices in the market and each device has different command to read the valid data. To support these devices in flexible, RS485-LN supports flexible command set. User can use [[AT Commands>>||anchor="H3.5ConfigureRS485-BLviaATorDownlink"]] or LoRaWAN Downlink Command to configure what commands RS485-LN should send for each sampling and how to handle the return from RS485 devices.
227	227	)))
228	228
229	229	(((
...	...	@@ -295,6 +295,8 @@
295	295	)))
296	296	)))
297	297
	295	+
	296	+
298	298	=== 3.3.2 Configure sensors ===
299	299
300	300	(((
...	...	@@ -313,6 +313,8 @@
313	313	mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
314	314	)))|(% style="width:256px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
315	315
	315	+
	316	+
316	316	=== 3.3.3 Configure read commands for each sampling ===
317	317
318	318	(((
...	...	@@ -428,6 +428,7 @@
428	428
429	429	(% style="color:#4f81bd" %)**Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA**
430	430
	432	+
431	431	1. PAYVER: Defined by AT+PAYVER
432	432	1. PAYLOAD COUNT: Total how many uplinks of this sampling.
433	433	1. PAYLOAD#: Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
...	...	@@ -527,8 +527,6 @@
527	527
528	528	=== 3.5.3 Sensor related commands ===
529	529
530		-(% class="wikigeneratedid" id="H" %)
531		-
532	532
533	533
534	534	==== **RS485 Debug Command** ====
...	...	@@ -745,7 +745,6 @@
745	745	**0x08 FF**, RS485-LN will immediately send an uplink.
746	746
747	747
748		-==== ====
749	749
750	750	==== **Clear RS485 Command** ====
751	751
...	...	@@ -864,7 +864,6 @@
864	864	|**PRO**|(% style="width:1420px" %)Use for upload image, see [[How to Update Image>>path:#upgrade_image]]
865	865
866	866
867		-
868	868	== 3.8 LEDs ==
869	869
870	870	(% border="1" style="background-color:#f7faff; width:500px" %)
...	...	@@ -873,7 +873,6 @@
873	873	|**SYS**|After device is powered on, the SYS will (% style="color:green" %)**fast blink in GREEN** (%%)for 5 times, means RS485-LN start to join LoRaWAN network. If join success, SYS will be (% style="color:green" %)**on GREEN for 5 seconds**(%%)**. **SYS will (% style="color:green" %)**blink Blue**(%%) on every upload and (% style="color:green" %)**blink Green**(%%) once receive a downlink message.
874	874
875	875
876		-
877	877	= 4. Case Study =
878	878
879	879	User can check this URL for some case studies: [[APP RS485 COMMUNICATE WITH SENSORS>>doc:Main.Application Note \: Communicate with Different Sensors ----- RS485-LN RS485-BL.WebHome]]
...	...	@@ -1049,7 +1049,6 @@
1049	1049	* (% style="color:blue" %)**KZ865**(%%): frequency bands KZ865
1050	1050
1051	1051
1052		-
1053	1053	= 9.Packing Info =
1054	1054
1055	1055
...	...	@@ -1066,6 +1066,7 @@
1066	1066	* Package Size / pcs : 14.5 x 8 x 5 cm
1067	1067	* Weight / pcs : 170g
1068	1068
	1065	+
1069	1069	= 10. FCC Caution for RS485LN-US915 =
1070	1070
1071	1071	Any Changes or modifications not expressly approved by the party responsible for compliance could void the user's authority to operate the equipment.