Wiki source code of RS485-LN – RS485 to LoRaWAN Converter

Version 57.26 by Xiaoling on 2022/06/06 09:20

version	line-number	content
3.2	1	(% style="text-align:center" %)
57.20	2	[[image:1653266934636-343.png\|\|height="385" width="385"]]
1.1	3
	4
	5
18.2	6	RS485-LN – RS485 to LoRaWAN Converter User Manual
1.1	7
	8
57.6	9
	10
3.2	11	Table of Contents:
1.1	12
57.20	13	{{toc/}}
1.1	14
	15
	16
	17
57.6	18
	19
	20
3.2	21	= 1.Introduction =
1.1	22
19.2	23	== 1.1 What is RS485-LN RS485 to LoRaWAN Converter ==
1.1	24
3.2	25	(((
	26	(((
32.3	27	The Dragino RS485-LN is a (% style="color:blue" %)RS485 to LoRaWAN Converter(%%). It converts the RS485 signal into LoRaWAN wireless signal which simplify the IoT installation and reduce the installation/maintaining cost.
3.2	28	)))
2.2	29
3.2	30	(((
32.3	31	RS485-LN allows user to (% style="color:blue" %)monitor / control RS485 devices(%%) and reach extremely long ranges. It provides ultra-long range spread spectrum communication and high interference immunity whilst minimizing current consumption. It targets professional wireless sensor network applications such as irrigation systems, smart metering, smart cities, smartphone detection, building automation, and so on.
3.2	32	)))
2.2	33
3.2	34	(((
32.3	35	(% style="color:blue" %)For data uplink(%%), RS485-LN sends user-defined commands to RS485 devices and gets the return from the RS485 devices. RS485-LN will process these returns according to user-define rules to get the final payload and upload to LoRaWAN server.
3.2	36	)))
2.2	37
3.2	38	(((
32.3	39	(% style="color:blue" %)For data downlink(%%), RS485-LN runs in LoRaWAN Class C. When there downlink commands from LoRaWAN server, RS485-LN will forward the commands from LoRaWAN server to RS485 devices.
32.2	40
32.3	41	(% style="color:blue" %)Demo Dashboard for RS485-LN(%%) connect to two energy meters: [[https:~~/~~/app.datacake.de/dashboard/d/58844a26-378d-4c5a-aaf5-b5b5b153447a>>url:https://app.datacake.de/dashboard/d/58844a26-378d-4c5a-aaf5-b5b5b153447a]]
3.2	42	)))
	43	)))
2.2	44
57.20	45	[[image:1653267211009-519.png\|\|height="419" width="724"]]
2.2	46
32.4	47
3.2	48	== 1.2 Specifications ==
2.2	49
32.6	50
2.2	51	Hardware System:
	52
	53	* STM32L072CZT6 MCU
22.4	54	* SX1276/78 Wireless Chip
2.2	55	* Power Consumption (exclude RS485 device):
19.3	56	** Idle: 32mA@12v
	57	** 20dB Transmit: 65mA@12v
2.2	58
	59	Interface for Model:
	60
19.3	61	* RS485
22.4	62	* Power Input 7~~ 24V DC.
2.2	63
	64	LoRa Spec:
	65
	66	* Frequency Range:
	67	** Band 1 (HF): 862 ~~ 1020 Mhz
	68	** Band 2 (LF): 410 ~~ 528 Mhz
	69	* 168 dB maximum link budget.
	70	* +20 dBm - 100 mW constant RF output vs.
19.3	71	* +14 dBm high efficiency PA.
2.2	72	* Programmable bit rate up to 300 kbps.
	73	* High sensitivity: down to -148 dBm.
	74	* Bullet-proof front end: IIP3 = -12.5 dBm.
	75	* Excellent blocking immunity.
19.3	76	* Low RX current of 10.3 mA, 200 nA register retention.
2.2	77	* Fully integrated synthesizer with a resolution of 61 Hz.
19.3	78	* FSK, GFSK, MSK, GMSK, LoRaTM and OOK modulation.
2.2	79	* Built-in bit synchronizer for clock recovery.
	80	* Preamble detection.
	81	* 127 dB Dynamic Range RSSI.
19.3	82	* Automatic RF Sense and CAD with ultra-fast AFC.
57.2	83	* Packet engine up to 256 bytes with CRC
2.2	84
3.3	85	== 1.3 Features ==
2.2	86
19.4	87	* LoRaWAN Class A & Class C protocol (default Class C)
2.2	88	* Frequency Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/IN865/RU864
	89	* AT Commands to change parameters
19.4	90	* Remote configure parameters via LoRa Downlink
2.2	91	* Firmware upgradable via program port
	92	* Support multiply RS485 devices by flexible rules
	93	* Support Modbus protocol
19.4	94	* Support Interrupt uplink (Since hardware version v1.2)
2.2	95
3.3	96	== 1.4 Applications ==
2.2	97
	98	* Smart Buildings & Home Automation
	99	* Logistics and Supply Chain Management
	100	* Smart Metering
	101	* Smart Agriculture
	102	* Smart Cities
	103	* Smart Factory
	104
6.2	105	== 1.5 Firmware Change log ==
2.2	106
19.4	107	[[RS485-LN Image files – Download link and Change log>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/]]
2.2	108
32.10	109
4.2	110	== 1.6 Hardware Change log ==
2.2	111
4.2	112	(((
	113	(((
19.4	114	v1.2: Add External Interrupt Pin.
2.2	115
19.4	116	v1.0: Release
32.10	117
	118
4.2	119	)))
	120	)))
2.2	121
20.2	122	= 2. Power ON Device =
2.2	123
6.2	124	(((
20.2	125	The RS485-LN can be powered by 7 ~~ 24V DC power source. Connection as below
2.2	126
20.2	127	* Power Source VIN to RS485-LN VIN+
	128	* Power Source GND to RS485-LN VIN-
2.2	129
20.3	130	(((
20.2	131	Once there is power, the RS485-LN will be on.
20.3	132	)))
2.2	133
57.20	134	[[image:1653268091319-405.png]]
32.11	135
	136
20.2	137	)))
2.2	138
6.2	139	= 3. Operation Mode =
2.2	140
6.2	141	== 3.1 How it works? ==
2.2	142
7.2	143	(((
21.2	144	The RS485-LN is configured as LoRaWAN OTAA Class C mode by default. It has OTAA keys to join network. To connect a local LoRaWAN network, user just need to input the OTAA keys in the network server and power on the RS485-LN. It will auto join the network via OTAA.
32.12	145
	146
7.2	147	)))
2.2	148
7.2	149	== 3.2 Example to join LoRaWAN network ==
2.2	150
6.2	151	Here shows an example for how to join the TTN V3 Network. Below is the network structure, we use [[LG308>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/140-lg308.html]] as LoRaWAN gateway here.
2.2	152
57.20	153	[[image:1653268155545-638.png\|\|height="334" width="724"]]
2.2	154
32.13	155
15.3	156	(((
32.13	157	(((
22.2	158	The RS485-LN in this example connected to two RS485 devices for demonstration, user can connect to other RS485 devices via the same method. The connection is as below:
32.13	159	)))
2.2	160
32.13	161	(((
22.2	162	485A+ and 485B- of the sensor are connected to RS485A and RA485B of RS485-LN respectively.
32.13	163	)))
22.2	164
57.20	165	[[image:1653268227651-549.png\|\|height="592" width="720"]]
22.2	166
15.3	167	(((
57.20	168	The LG308 is already set to connect to [[TTN V3 network >>path:https://www.thethingsnetwork.org/]]. So what we need to now is only configure the TTN V3:
15.3	169	)))
2.2	170
15.3	171	(((
22.2	172	Step 1: Create a device in TTN V3 with the OTAA keys from RS485-LN.
15.3	173	)))
2.2	174
15.3	175	(((
22.2	176	Each RS485-LN is shipped with a sticker with unique device EUI:
15.3	177	)))
22.2	178	)))
2.2	179
57.20	180	[[image:1652953462722-299.png]]
2.2	181
15.3	182	(((
22.3	183	(((
2.2	184	User can enter this key in their LoRaWAN Server portal. Below is TTN V3 screen shot:
15.3	185	)))
2.2	186
15.3	187	(((
2.2	188	Add APP EUI in the application.
15.3	189	)))
22.3	190	)))
2.2	191
57.20	192	[[image:image-20220519174512-1.png]]
2.2	193
57.20	194	[[image:image-20220519174512-2.png\|\|height="323" width="720"]]
2.2	195
57.20	196	[[image:image-20220519174512-3.png\|\|height="556" width="724"]]
2.2	197
57.20	198	[[image:image-20220519174512-4.png]]
2.2	199
	200	You can also choose to create the device manually.
	201
57.20	202	[[image:1652953542269-423.png\|\|height="710" width="723"]]
2.2	203
	204	Add APP KEY and DEV EUI
	205
57.20	206	[[image:1652953553383-907.png\|\|height="514" width="724"]]
2.2	207
	208
15.2	209	(((
22.4	210	Step 2: Power on RS485-LN and it will auto join to the TTN V3 network. After join success, it will start to upload message to TTN V3 and user can see in the panel.
15.2	211	)))
2.2	212
57.20	213	[[image:1652953568895-172.png\|\|height="232" width="724"]]
2.2	214
32.14	215
15.5	216	== 3.3 Configure Commands to read data ==
2.2	217
15.5	218	(((
22.4	219	(((
57.20	220	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.
15.5	221	)))
2.2	222
22.4	223	(((
	224	(% style="color:red" %)Note: below description and commands are for firmware version >v1.1, if you have firmware version v1.0. Please check the [[user manual v1.0>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/&file=RS485-LN_UserManual_v1.0.1.pdf]] or upgrade the firmware to v1.1
32.15	225
	226
22.4	227	)))
	228	)))
	229
15.5	230	=== 3.3.1 onfigure UART settings for RS485 or TTL communication ===
2.2	231
22.6	232	To use RS485-LN to read data from RS485 sensors, connect the RS485-LN A/B traces to the sensors. And user need to make sure RS485-LN use the match UART setting to access the sensors. The related commands for UART settings are:
2.2	233
32.16	234	(% border="1" style="background-color:#ffffcc; color:green; width:782px" %)
	235	\|(% style="width:128px" %)(((
15.5	236	AT Commands
32.16	237	)))\|(% style="width:305px" %)(((
15.5	238	Description
32.16	239	)))\|(% style="width:346px" %)(((
15.5	240	Example
	241	)))
32.16	242	\|(% style="width:128px" %)(((
15.5	243	AT+BAUDR
32.16	244	)))\|(% style="width:305px" %)(((
15.5	245	Set the baud rate (for RS485 connection). Default Value is: 9600.
32.16	246	)))\|(% style="width:346px" %)(((
15.5	247	(((
2.2	248	AT+BAUDR=9600
15.5	249	)))
2.2	250
15.5	251	(((
2.2	252	Options: (1200,2400,4800,14400,19200,115200)
	253	)))
15.5	254	)))
32.16	255	\|(% style="width:128px" %)(((
15.5	256	AT+PARITY
32.16	257	)))\|(% style="width:305px" %)(((
2.2	258	Set UART parity (for RS485 connection)
32.16	259	)))\|(% style="width:346px" %)(((
15.5	260	(((
2.2	261	AT+PARITY=0
15.5	262	)))
2.2	263
15.5	264	(((
2.2	265	Option: 0: no parity, 1: odd parity, 2: even parity
	266	)))
15.5	267	)))
32.16	268	\|(% style="width:128px" %)(((
15.5	269	AT+STOPBIT
32.16	270	)))\|(% style="width:305px" %)(((
15.5	271	(((
2.2	272	Set serial stopbit (for RS485 connection)
15.5	273	)))
2.2	274
15.5	275	(((
22.6	276
15.5	277	)))
32.16	278	)))\|(% style="width:346px" %)(((
15.5	279	(((
2.2	280	AT+STOPBIT=0 for 1bit
15.5	281	)))
2.2	282
15.5	283	(((
2.2	284	AT+STOPBIT=1 for 1.5 bit
15.5	285	)))
2.2	286
15.5	287	(((
2.2	288	AT+STOPBIT=2 for 2 bits
	289	)))
15.5	290	)))
2.2	291
15.6	292	=== 3.3.2 Configure sensors ===
2.2	293
15.6	294	(((
	295	(((
22.7	296	Some sensors might need to configure before normal operation. User can configure such sensor via PC and RS485 adapter or through RS485-LN AT Commands (% style="color:#4f81bd" %)AT+CFGDEV(%%). Each (% style="color:#4f81bd" %)AT+CFGDEV (%%)equals to send a RS485 command to sensors. This command will only run when user input it and won’t run during each sampling.
15.6	297	)))
22.7	298	)))
2.2	299
15.6	300	(% border="1" style="background-color:#ffffcc; color:green; width:806px" %)
	301	\|AT Commands\|(% style="width:418px" %)Description\|(% style="width:256px" %)Example
	302	\|AT+CFGDEV\|(% style="width:418px" %)(((
2.2	303	This command is used to configure the RS485/TTL devices; they won’t be used during sampling.
	304
15.6	305	AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,
2.2	306
15.6	307	mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
	308	)))\|(% style="width:256px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
2.2	309
15.6	310	=== 3.3.3 Configure read commands for each sampling ===
2.2	311
15.6	312	(((
35.2	313	During each sampling, we need confirm what commands we need to send to the RS485 sensors to read data. After the RS485 sensors send back the value, it normally include some bytes and we only need a few from them for a shorten payload.
2.2	314
	315	To save the LoRaWAN network bandwidth, we might need to read data from different sensors and combine their valid value into a short payload.
	316
	317	This section describes how to achieve above goals.
	318
35.2	319	During each sampling, the RS485-LN can support 15 commands to read sensors. And combine the return to one or several uplink payloads.
2.2	320
	321
35.2	322	Each RS485 commands include two parts:
2.2	323
35.2	324	~1. What commands RS485-LN will send to the RS485 sensors. There are total 15 commands from AT+COMMAD1, ATCOMMAND2,…, to AT+COMMANDF. All commands are of same grammar.
2.2	325
35.2	326	2. How to get wanted value the from RS485 sensors returns from by 1). There are total 15 AT Commands to handle the return, commands are AT+DATACUT1,AT+DATACUT2,…, AT+DATACUTF corresponding to the commands from 1). All commands are of same grammar.
2.2	327
35.4	328	3. Some RS485 device might has longer delay on reply, so user can use AT+CMDDL to set the timeout for getting reply after the RS485 command is sent. For example AT+CMDDL1=1000 to send the open time to 1000ms
2.2	329
	330
	331	After we got the valid value from each RS485 commands, we need to combine them together with the command AT+DATAUP.
	332
	333
	334	Below are examples for the how above AT Commands works.
	335
	336
35.2	337	AT+COMMANDx : This command will be sent to RS485 devices during each sampling, Max command length is 14 bytes. The grammar is:
	338
	339	(% border="1" style="background-color:#4bacc6; color:white; width:499px" %)
	340	\|(% style="width:496px" %)(((
2.2	341	AT+COMMANDx=xx xx xx xx xx xx xx xx xx xx xx xx,m
	342
	343	xx xx xx xx xx xx xx xx xx xx xx xx: The RS485 command to be sent
	344
	345	m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
	346	)))
	347
	348	For example, if we have a RS485 sensor. The command to get sensor value is: 01 03 0B B8 00 02 46 0A. Where 01 03 0B B8 00 02 is the Modbus command to read the register 0B B8 where stored the sensor value. The 46 0A is the CRC-16/MODBUS which calculate manually.
	349
35.2	350	In the RS485-LN, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
2.2	351
	352
	353	AT+DATACUTx : This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes.
	354
35.2	355	(% border="1" style="background-color:#4bacc6; color:white; width:725px" %)
	356	\|(% style="width:722px" %)(((
2.2	357	AT+DATACUTx=a,b,c
	358
	359	* a: length for the return of AT+COMMAND
	360	* b:1: grab valid value by byte, max 6 bytes. 2: grab valid value by bytes section, max 3 sections.
35.5	361	* c: define the position for valid value.
2.2	362	)))
	363
35.2	364	Examples:
	365
2.2	366	* Grab bytes:
	367
57.20	368	[[image:image-20220602153621-1.png]]
2.2	369
35.2	370
2.2	371	* Grab a section.
	372
57.20	373	[[image:image-20220602153621-2.png]]
2.2	374
35.2	375
2.2	376	* Grab different sections.
	377
57.20	378	[[image:image-20220602153621-3.png]]
35.3	379
	380
35.2	381	)))
2.2	382
29.2	383	=== 3.3.4 Compose the uplink payload ===
2.2	384
29.2	385	(((
2.2	386	Through AT+COMMANDx and AT+DATACUTx we got valid value from each RS485 commands, Assume these valid value are RETURN1, RETURN2, .., to RETURNx. The next step is how to compose the LoRa Uplink Payload by these RETURNs. The command is AT+DATAUP.
35.5	387
	388
29.2	389	)))
2.2	390
29.2	391	(((
35.5	392	(% style="color:#037691" %)Examples: AT+DATAUP=0
	393
	394
29.2	395	)))
2.2	396
29.2	397	(((
	398	Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)A SIGNLE UPLINK.
	399	)))
2.2	400
29.2	401	(((
2.2	402	Final Payload is
29.2	403	)))
2.2	404
29.2	405	(((
	406	(% style="color:#4f81bd" %)Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx
	407	)))
2.2	408
29.2	409	(((
2.2	410	Where PAYVER is defined by AT+PAYVER, below is an example screen shot.
29.2	411	)))
2.2	412
57.20	413	[[image:1653269759169-150.png\|\|height="513" width="716"]]
2.2	414
35.5	415
35.6	416	(% style="color:#037691" %)Examples: AT+DATAUP=1
2.2	417
35.5	418
30.2	419	Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)Multiply UPLINKs.
2.2	420
	421	Final Payload is
	422
30.2	423	(% style="color:#4f81bd" %)Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA
2.2	424
57.16	425
36.2	426	1. PAYVER: Defined by AT+PAYVER
	427	1. PAYLOAD COUNT: Total how many uplinks of this sampling.
	428	1. PAYLOAD#: Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
	429	1. DATA: Valid value: max 8 bytes for each uplink so each uplink <= 11 bytes. For the last uplink, DATA will might less than 8 bytes
2.2	430
57.20	431	[[image:image-20220602155039-4.png]]
2.2	432
	433
36.2	434	So totally there will be 3 uplinks for this sampling, each uplink include 8 bytes DATA
2.2	435
36.2	436	DATA1=RETURN1 Valid Value + the first two of Valid value of RETURN10= 20 20 0a 33 90 41 02 aa
2.2	437
36.2	438	DATA2=3^^rd^^ ~~ 10^^th^^ byte of Valid value of RETURN10= 05 81 0a 20 20 20 20 2d
2.2	439
36.2	440	DATA3=the rest of Valid value of RETURN10= 30
2.2	441
36.2	442
	443	(% style="color:red" %)Notice: In firmware v1.3, the Max bytes has been changed according to the max bytes in different Frequency Bands for lowest SF. As below:
	444
	445	~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink.
	446
	447	* For AU915/AS923 bands, if UplinkDwell time=0, max 11 bytes for each uplink.
	448
	449	* For US915 band, max 11 bytes for each uplink.
	450
	451	~* For all other bands: max 51 bytes for each uplink.
	452
	453
2.2	454	Below are the uplink payloads:
	455
57.20	456	[[image:1654157178836-407.png]]
2.2	457
	458
31.3	459	=== 3.3.5 Uplink on demand ===
2.2	460
37.4	461	Except uplink periodically, RS485-LN is able to uplink on demand. The server send downlink command to RS485-LN and RS485 will uplink data base on the command.
2.2	462
	463	Downlink control command:
	464
37.4	465	0x08 command: Poll an uplink with current command set in RS485-LN.
2.2	466
37.4	467	0xA8 command: Send a command to RS485-LN and uplink the output from sensors.
2.2	468
	469
	470
38.2	471	=== 3.3.6 Uplink on Interrupt ===
2.2	472
38.2	473	RS485-LN support external Interrupt uplink since hardware v1.2 release.
2.2	474
57.20	475	[[image:1654157342174-798.png]]
2.2	476
38.2	477	Connect the Interrupt pin to RS485-LN INT port and connect the GND pin to V- port. When there is a high voltage (Max 24v) on INT pin. Device will send an uplink packet.
2.2	478
	479
38.4	480	== 3.4 Uplink Payload ==
2.2	481
38.4	482	(% border="1" style="background-color:#4bacc6; color:white; width:734px" %)
	483	\|Size(bytes)\|(% style="width:120px" %)2\|(% style="width:116px" %)1\|(% style="width:386px" %)Length depends on the return from the commands
	484	\|Value\|(% style="width:120px" %)(((
2.2	485	Battery(mV)
	486
	487	&
	488
	489	Interrupt _Flag
38.4	490	)))\|(% style="width:116px" %)(((
2.2	491	PAYLOAD_VER
	492
	493
38.4	494	)))\|(% style="width:386px" %)If the valid payload is too long and exceed the maximum support payload length in server, server will show payload not provided in the LoRaWAN server.
2.2	495
	496	Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors.
	497
	498
38.4	499	== 3.5 Configure RS485-BL via AT or Downlink ==
2.2	500
38.4	501	User can configure RS485-LN via AT Commands or LoRaWAN Downlink Commands
2.2	502
38.4	503	There are two kinds of Commands:
2.2	504
57.20	505	* (% style="color:#4f81bd" %)Common Commands(%%): They should be available for each sensor, such as: change uplink interval, reset device. For firmware v1.3, user can find what common commands it supports: [[AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]
2.2	506
38.4	507	* (% style="color:#4f81bd" %)Sensor Related Commands(%%): These commands are special designed for RS485-LN. User can see these commands below:
2.2	508
38.4	509	=== 3.5.1 Common Commands ===
2.2	510
57.20	511	They should be available for each of Dragino Sensors, such as: change uplink interval, reset device. For firmware v1.3, user can find what common commands it supports: [[End Device AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]
2.2	512
	513
41.1	514	=== 3.5.2 Sensor related commands ===
2.2	515
41.1	516	Response feature is added to the server's downlink, a special package with a FPort of 200 will be uploaded immediately after receiving the data sent by the server.
2.2	517
57.20	518	[[image:image-20220602163333-5.png\|\|height="263" width="1160"]]
2.2	519
41.1	520	The first byte of this package represents whether the configuration is successful, 00 represents failure, 01 represents success. Except for the first byte, the other is the previous downlink. (All commands except A8 type commands are applicable)
2.2	521
	522
42.2	523	=== 3.5.3 Sensor related commands ===
2.2	524
	525
57.6	526
42.2	527	==== RS485 Debug Command ====
	528
	529	This command is used to configure the RS485 devices; they won’t be used during sampling.
	530
	531	* AT Command
	532
	533	(% class="box infomessage" %)
	534	(((
	535	AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
	536	)))
	537
	538	m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
	539
	540	* Downlink Payload
	541
	542	Format: A8 MM NN XX XX XX XX YY
	543
	544	Where:
	545
	546	* MM: 1: add CRC-16/MODBUS ; 0: no CRC
	547	* NN: The length of RS485 command
	548	* XX XX XX XX: RS485 command total NN bytes
	549	* YY: How many bytes will be uplink from the return of this RS485 command,
	550	** if YY=0, RS485-LN will execute the downlink command without uplink;
	551	** if YY>0, RS485-LN will uplink total YY bytes from the output of this RS485 command; Fport=200
	552	** if YY=FF, RS485-LN will uplink RS485 output with the downlink command content; Fport=200.
	553
	554	Example 1 ~-~-> Configure without ask for uplink (YY=0)
	555
	556	To connect a Modbus Alarm with below commands.
	557
	558	* The command to active alarm is: 0A 05 00 04 00 01 4C B0. Where 0A 05 00 04 00 01 is the Modbus command to read the register 00 40 where stored the DI status. The 4C B0 is the CRC-16/MODBUS which calculate manually.
	559
	560	* The command to deactivate alarm is: 0A 05 00 04 00 00 8D 70. Where 0A 05 00 04 00 00 is the Modbus command to read the register 00 40 where stored the DI status. The 8D 70 is the CRC-16/MODBUS which calculate manually.
	561
	562	So if user want to use downlink command to control to RS485 Alarm, he can use:
	563
	564	(% style="color:#4f81bd" %)A8 01 06 0A 05 00 04 00 01 00(%%): to activate the RS485 Alarm
	565
	566	(% style="color:#4f81bd" %)A8 01 06 0A 05 00 04 00 00 00(%%): to deactivate the RS485 Alarm
	567
	568	A8 is type code and 01 means add CRC-16/MODBUS at the end, the 3^^rd^^ byte is 06, means the next 6 bytes are the command to be sent to the RS485 network, the final byte 00 means this command don’t need to acquire output.
	569
	570
	571	Example 2 ~-~-> Configure with requesting uplink and original downlink command (YY=FF)
	572
	573	User in IoT server send a downlink command: (% style="color:#4f81bd" %)A8 01 06 0A 08 00 04 00 01 YY
	574
	575
	576	RS485-LN got this downlink command and send (% style="color:#4f81bd" %)0A 08 00 04 00 01 (%%)to Modbus network. One of the RS485 sensor in the network send back Modbus reply 0A 08 00 04 00 00. RS485-LN get this reply and combine with the original downlink command and uplink. The uplink message is:
	577
	578	A8 (% style="color:#4f81bd" %)0A 08 00 04 00 (% style="color:red" %)01 06 (% style="color:green" %)0A 08 00 04 00 00
	579
57.20	580	[[image:1654159460680-153.png]]
42.2	581
42.3	582
	583
	584	==== Set Payload version ====
	585
	586	This is the first byte of the uplink payload. RS485-BL can connect to different sensors. User can set the PAYVER field to tell server how to decode the current payload.
	587
	588	* AT Command:
	589
	590	(% class="box infomessage" %)
	591	(((
	592	AT+PAYVER: Set PAYVER field = 1
	593	)))
	594
	595	* Downlink Payload:
	596
	597	0xAE 01 ~-~-> Set PAYVER field = 0x01
	598
	599	0xAE 0F ~-~-> Set PAYVER field = 0x0F
	600
	601
	602
	603	==== Set RS485 Sampling Commands ====
	604
44.2	605	AT+COMMANDx or AT+DATACUTx
42.3	606
57.20	607	These three commands are used to configure how the RS485-LN polling data from Modbus device. Detail of usage please see : [[polling RS485 device>>\|\|anchor="H3.3.3Configurereadcommandsforeachsampling"]].
42.3	608
	609
	610	* AT Command:
	611
	612	(% class="box infomessage" %)
	613	(((
	614	AT+COMMANDx: Configure RS485 read command to sensor.
	615	)))
	616
	617	(% class="box infomessage" %)
	618	(((
	619	AT+DATACUTx: Configure how to handle return from RS485 devices.
	620	)))
	621
	622
	623	* Downlink Payload:
	624
	625	0xAF downlink command can be used to set AT+COMMANDx or AT+DATACUTx.
	626
	627	(% style="color:red" %)Note(%%): if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink.
	628
	629	Format: AF MM NN LL XX XX XX XX YY
	630
	631	Where:
	632
	633	* MM: the ATCOMMAND or AT+DATACUT to be set. Value from 01 ~~ 0F,
	634	* NN: 0: no CRC; 1: add CRC-16/MODBUS ; 2: set the AT+DATACUT value.
	635	* LL: The length of AT+COMMAND or AT+DATACUT command
	636	* XX XX XX XX: AT+COMMAND or AT+DATACUT command
44.2	637	* YY: If YY=0, RS485-BL will execute the downlink command without uplink; if YY=1, RS485-LN will execute an uplink after got this command.
42.3	638
	639	Example:
	640
	641	(% style="color:#037691" %)AF 03 01 06 0A 05 00 04 00 01 00(%%): Same as AT+COMMAND3=0A 05 00 04 00 01,1
	642
	643	(% style="color:#037691" %)AF 03 02 06(% style="color:orange" %) 10 (% style="color:red" %)01 (% style="color:green" %)05 06 09 0A(% style="color:#037691" %) 00(%%): Same as AT+DATACUT3=(% style="color:orange" %)16(%%),(% style="color:red" %)1(%%),(% style="color:green" %)5+6+9+10
	644
	645	(% style="color:#037691" %)AF 03 02 06 (% style="color:orange" %)0B(% style="color:red" %) 02 (% style="color:green" %)05 07 08 0A (% style="color:#037691" %)00(%%): Same as AT+DATACUT3=(% style="color:orange" %)11(%%),(% style="color:red" %)2(%%),(% style="color:green" %)5~~7+8~~10
	646
	647
	648
	649	==== Fast command to handle MODBUS device ====
	650
	651	AT+MBFUN is valid since v1.3 firmware version. The command is for fast configure to read Modbus devices. It is only valid for the devices which follow the [[MODBUS-RTU protocol>>url:https://www.modbustools.com/modbus.html]].
	652
	653	This command is valid since v1.3 firmware version
	654
44.2	655	AT+MBFUN can auto read the Modbus function code: 01, 02, 03 or 04. AT+MBFUN has lower priority vs AT+DATACUT command. If AT+DATACUT command is configured, AT+MBFUN will be ignore.
42.3	656
	657
	658	Example:
	659
44.2	660	* AT+MBFUN=1 and AT+DATACUT1/AT+DATACUT2 are not configure (0,0,0). So RS485-LN.
42.3	661	* AT+COMMAND1= 01 03 00 10 00 08,1 ~-~-> read slave address 01 , function code 03, start address 00 01, quantity of registers 00 08.
	662	* AT+COMMAND2= 01 02 00 40 00 10,1 ~-~-> read slave address 01 , function code 02, start address 00 40, quantity of inputs 00 10.
	663
57.20	664	[[image:image-20220602165351-6.png]]
42.3	665
57.20	666	[[image:image-20220602165351-7.png]]
42.3	667
	668
	669
	670	==== RS485 command timeout ====
	671
44.3	672	Some Modbus device has slow action to send replies. This command is used to configure the RS485-LN to use longer time to wait for their action.
42.3	673
44.3	674	Default value: 0, range: 0 ~~ 65 seconds
42.3	675
	676	* AT Command:
	677
	678	(% class="box infomessage" %)
	679	(((
44.3	680	*AT+CMDDLaa=hex(bb cc)1000**
42.3	681	)))
	682
	683	Example:
	684
	685	AT+CMDDL1=1000 to send the open time to 1000ms
	686
	687
	688	* Downlink Payload:
	689
44.3	690	0x AA aa bb cc
42.3	691
44.3	692	Same as: AT+CMDDLaa=hex(bb cc)*1000
42.3	693
	694	Example:
	695
44.3	696	0xAA 01 00 01 ~-~-> Same as AT+CMDDL1=1000 ms
42.3	697
	698
	699
	700	==== Uplink payload mode ====
	701
	702	Define to use one uplink or multiple uplinks for the sampling.
	703
57.20	704	The use of this command please see: [[Compose Uplink payload>>\|\|anchor="H3.3.4Composetheuplinkpayload"]]
42.3	705
	706	* AT Command:
	707
	708	(% class="box infomessage" %)
	709	(((
	710	AT+DATAUP=0
	711	)))
	712
	713	(% class="box infomessage" %)
	714	(((
	715	AT+DATAUP=1
	716	)))
	717
	718
	719	* Downlink Payload:
	720
	721	0xAD 00 ~-~-> Same as AT+DATAUP=0
	722
	723	0xAD 01 ~-~-> Same as AT+DATAUP=1
	724
	725
	726
	727	==== Manually trigger an Uplink ====
	728
	729	Ask device to send an uplink immediately.
	730
45.2	731	* AT Command:
	732
57.25	733	No AT Command for this, user can press the [[ACT button>>\|\|anchor="H3.7Buttons"]] for 1 second for the same.
45.2	734
	735
42.3	736	* Downlink Payload:
	737
45.2	738	0x08 FF, RS485-LN will immediately send an uplink.
42.3	739
	740
	741
	742	==== Clear RS485 Command ====
	743
	744	The AT+COMMANDx and AT+DATACUTx settings are stored in special location, user can use below command to clear them.
	745
	746	* AT Command:
	747
45.2	748	AT+CMDEAR=mm,nn mm: start position of erase ,nn: stop position of erase
	749
	750	Etc. AT+CMDEAR=1,10 means erase AT+COMMAND1/AT+DATACUT1 to AT+COMMAND10/AT+DATACUT10
	751
47.2	752	Example screen shot after clear all RS485 commands.
45.2	753
	754
	755	The uplink screen shot is:
	756
57.24	757	[[image:1654160691922-496.png]]
45.2	758
	759
45.3	760	* Downlink Payload:
45.2	761
45.3	762	0x09 aa bb same as AT+CMDEAR=aa,bb
45.2	763
	764
45.3	765
42.3	766	==== Set Serial Communication Parameters ====
	767
	768	Set the Rs485 serial communication parameters:
	769
	770	* AT Command:
	771
	772	Set Baud Rate:
	773
	774	(% class="box infomessage" %)
	775	(((
	776	AT+BAUDR=9600 ~/~/ Options: (1200,2400,4800,14400,19200,115200)
	777	)))
	778
	779	Set UART Parity
	780
	781	(% class="box infomessage" %)
	782	(((
	783	AT+PARITY=0 ~/~/ Option: 0: no parity, 1: odd parity, 2: even parity
	784	)))
	785
	786	Set STOPBIT
	787
	788	(% class="box infomessage" %)
	789	(((
	790	AT+STOPBIT=0 ~/~/ Option: 0 for 1bit; 1 for 1.5 bit ; 2 for 2 bits
	791	)))
	792
	793
	794	* Downlink Payload:
	795
	796	A7 01 aa bb: Same AT+BAUDR=hex(aa bb)*100
	797
	798	Example:
	799
	800	* A7 01 00 60 same as AT+BAUDR=9600
	801	* A7 01 04 80 same as AT+BAUDR=115200
	802
	803	A7 02 aa: Same as AT+PARITY=aa (aa value: 00 , 01 or 02)
	804
	805	A7 03 aa: Same as AT+STOPBIT=aa (aa value: 00 , 01 or 02)
	806
	807
47.2	808	== 3.6 Listening mode for RS485 network ==
42.3	809
47.2	810	This feature support since firmware v1.4
	811
	812	RS485-LN supports listening mode, it can listen the RS485 network packets and send them via LoRaWAN uplink. Below is the structure. The blue arrow shows the RS485 network packets to RS485-LN.
	813
57.20	814	[[image:image-20220602171200-8.png\|\|height="567" width="1007"]]
47.2	815
	816	To enable the listening mode, use can run the command AT+RXMODE.
	817
	818
	819	(% border="1" style="background-color:#ffffcc; width:500px" %)
	820	\|=(% style="width: 161px;" %)Command example:\|=(% style="width: 337px;" %)Function
	821	\|(% style="width:161px" %)AT+RXMODE=1,10 \|(% style="width:337px" %)Enable listening mode 1, if RS485-LN has received more than 10 RS485 commands from the network. RS485-LN will send these commands via LoRaWAN uplinks.
	822	\|(% style="width:161px" %)AT+RXMODE=2,500\|(% style="width:337px" %)Enable listening mode 2, RS485-LN will capture and send a 500ms content once from the first detect of character. Max value is 65535 ms
	823	\|(% style="width:161px" %)AT+RXMODE=0,0\|(% style="width:337px" %)Disable listening mode. This is the default settings.
	824	\|(% style="width:161px" %) \|(% style="width:337px" %)A6 aa bb cc same as AT+RXMODE=aa,(bb<<8 ~\| cc)
	825
	826	Downlink Command:
	827
	828	0xA6 aa bb cc same as AT+RXMODE=aa,(bb<<8 \| cc)
	829
	830
	831	Example:
	832
	833	The RS485-LN is set to AT+RXMODE=2,1000
	834
	835	There is a two Modbus commands in the RS485 network as below:
	836
	837	The Modbus master send a command: (% style="background-color:#ffc000" %)01 03 00 00 00 02 c4 0b
	838
	839	And Modbus slave reply with: (% style="background-color:green" %)01 03 04 00 00 00 00 fa 33
	840
	841	RS485-LN will capture both and send the uplink: (% style="background-color:#ffc000" %)01 03 00 00 00 02 c4 0b (% style="background-color:green" %)01 03 04 00 00 00 00 fa 33
	842
57.20	843	[[image:image-20220602171200-9.png]]
47.2	844
	845
47.3	846	(% style="color:red" %)Notice: Listening mode can work with the default polling mode of RS485-LN. When RS485-LN is in to send the RS485 commands (from AT+COMMANDx), the listening mode will be interrupt for a while.
47.2	847
	848
47.3	849	== 3.7 Buttons ==
	850
	851
	852	(% border="1" style="background-color:#f7faff; width:500px" %)
	853	\|=Button\|=(% style="width: 1420px;" %)Feature
	854	\|ACT\|(% style="width:1420px" %)If RS485 joined in network, press this button for more than 1 second, RS485 will upload a packet, and the SYS LED will give a (% style="color:blue" %)Blue blink
	855	\|RST\|(% style="width:1420px" %)Reboot RS485
57.20	856	\|PRO\|(% style="width:1420px" %)Use for upload image, see [[How to Update Image>>path:#upgrade_image]]
47.3	857
57.26	858
	859
47.3	860	== 3.8 LEDs ==
	861
	862	(% border="1" style="background-color:#f7faff; width:500px" %)
	863	\|=LEDs\|=Feature
	864	\|PWR\|Always on if there is power
	865	\|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.
	866
	867	= 4. Case Study =
	868
57.20	869	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]]
47.3	870
	871
	872	= 5. Use AT Command =
	873
	874	== 5.1 Access AT Command ==
	875
	876	RS485-BL supports AT Command set. User can use a USB to TTL adapter plus the 3.5mm Program Cable to connect to RS485-BL to use AT command, as below.
	877
57.20	878	[[image:1654162355560-817.png]]
47.3	879
	880
	881	In PC, User needs to set (% style="color:blue" %)serial tool(%%)(such as [[putty>>url:https://www.chiark.greenend.org.uk/~~sgtatham/putty/latest.html]], SecureCRT) baud rate to (% style="color:green" %)9600(%%) to access to access serial console of RS485-BL. The default password is 123456. Below is the output for reference:
	882
57.20	883	[[image:1654162368066-342.png]]
47.3	884
	885
57.20	886	More detail AT Command manual can be found at [[AT Command Manual>>\|\|anchor="3.5ConfigureRS485-BLviaATorDownlink"]]
47.3	887
	888
	889	== 5.2 Common AT Command Sequence ==
	890
	891	=== 5.2.1 Multi-channel ABP mode (Use with SX1301/LG308) ===
	892
	893	If device has not joined network yet:
	894
	895	(% class="box infomessage" %)
	896	(((
	897	AT+FDR
	898	)))
	899
	900	(% class="box infomessage" %)
	901	(((
	902	AT+NJM=0
	903	)))
	904
	905	(% class="box infomessage" %)
	906	(((
	907	ATZ
	908	)))
	909
	910
	911	If device already joined network:
	912
	913	(% class="box infomessage" %)
	914	(((
	915	AT+NJM=0
	916	)))
	917
	918	(% class="box infomessage" %)
	919	(((
	920	ATZ
	921	)))
	922
	923
	924	=== 5.5.2 Single-channel ABP mode (Use with LG01/LG02) ===
	925
	926
49.3	927	(% style="background-color:#dcdcdc" %)AT+FDR (%%) Reset Parameters to Factory Default, Keys Reserve
47.3	928
	929	(% style="background-color:#dcdcdc" %)AT+NJM=0 (%%)Set to ABP mode
	930
	931	(% style="background-color:#dcdcdc" %)AT+ADR=0 (%%)Set the Adaptive Data Rate Off
	932
51.3	933	(% style="background-color:#dcdcdc" %)AT+DR=5 (%%)Set Data Rate
47.3	934
	935	(% style="background-color:#dcdcdc" %)AT+TDC=60000 (%%) Set transmit interval to 60 seconds
	936
	937	(% style="background-color:#dcdcdc" %)AT+CHS=868400000(%%) Set transmit frequency to 868.4Mhz
	938
	939	(% style="background-color:#dcdcdc" %)AT+RX2FQ=868400000 (%%) Set RX2Frequency to 868.4Mhz (according to the result from server)
	940
	941	(% style="background-color:#dcdcdc" %)AT+RX2DR=5 (%%) Set RX2DR to match the downlink DR from server. see below
	942
	943	(% style="background-color:#dcdcdc" %)AT+DADDR=26 (%%) 01 1A F1 Set Device Address to 26 01 1A F1, this ID can be found in the LoRa Server portal.
	944
	945	(% style="background-color:#dcdcdc" %)ATZ (%%) Reset MCU
	946
	947
	948	(% style="color:red" %)Note:
	949
	950	(% style="color:red" %)1. Make sure the device is set to ABP mode in the IoT Server.
	951	2. Make sure the LG01/02 gateway RX frequency is exactly the same as AT+CHS setting.
	952	3. Make sure SF / bandwidth setting in LG01/LG02 match the settings of AT+DR. refer [[this link>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/&file=LoRaWAN%201.0.3%20Regional%20Parameters.xlsx]] to see what DR means.
	953	4. The command AT+RX2FQ and AT+RX2DR is to let downlink work. to set the correct parameters, user can check the actually downlink parameters to be used. As below. Which shows the RX2FQ should use 868400000 and RX2DR should be 5
	954
57.20	955	[[image:1654162478620-421.png]]
47.3	956
	957
	958	= 6. FAQ =
	959
	960	== 6.1 How to upgrade the image? ==
	961
51.2	962	The RS485-LN LoRaWAN Controller is shipped with a 3.5mm cable, the cable is used to upload image to RS485-LN to:
47.3	963
	964	* Support new features
	965	* For bug fix
	966	* Change LoRaWAN bands.
	967
51.2	968	Below shows the hardware connection for how to upload an image to RS485-LN:
47.3	969
57.20	970	[[image:1654162535040-878.png]]
47.3	971
	972	Step1: Download [[flash loader>>url:https://www.st.com/content/st_com/en/products/development-tools/software-development-tools/stm32-software-development-tools/stm32-programmers/flasher-stm32.html]].
	973
	974	Step2: Download the [[LT Image files>>url:http://www.dragino.com/downloads/index.php?dir=LT_LoRa_IO_Controller/LT33222-L/image/]].
	975
	976	Step3: Open flashloader; choose the correct COM port to update.
	977
52.2	978	(% style="color:blue" %) Hold down the PRO button and then momentarily press the RST reset button and the SYS led will change from OFF to ON, While SYS LED is RED ON, it means the RS485-LN is ready to be program.
51.3	979
47.3	980
57.20	981	[[image:image-20220602175818-12.png]]
47.3	982
	983
57.20	984	[[image:image-20220602175848-13.png]]
47.3	985
	986
57.20	987	[[image:image-20220602175912-14.png]]
56.2	988
56.4	989
52.2	990	Notice: In case user has lost the program cable. User can hand made one from a 3.5mm cable. The pin mapping is:
47.3	991
57.20	992	[[image:image-20220602175638-10.png]]
52.2	993
	994
47.3	995	== 6.2 How to change the LoRa Frequency Bands/Region? ==
	996
57.20	997	User can follow the introduction for [[how to upgrade image>>\|\|anchor="H6.1Howtoupgradetheimage3F"]]. When download the images, choose the required image file for download.
47.3	998
	999
	1000	== 6.3 How many RS485-Slave can RS485-BL connects? ==
	1001
57.20	1002	The RS485-BL can support max 32 RS485 devices. Each uplink command of RS485-BL can support max 16 different RS485 command. So RS485-BL can support max 16 RS485 devices pre-program in the device for uplink. For other devices no pre-program, user can use the [[downlink message (type code 0xA8) to poll their info>>\|\|anchor="H3.3.3Configurereadcommandsforeachsampling"]].
47.3	1003
	1004
51.4	1005	== 6.4 Compatible question to ChirpStack and TTI LoRaWAN server ? ==
47.3	1006
51.4	1007	When user need to use with ChirpStack or TTI. Please set AT+RPL=4.
	1008
57.20	1009	Detail info check this link: [[Set Packet Receiving Response Level>>doc:Main.End Device AT Commands and Downlink Command.WebHome\|\|anchor="H7.23SetPacketReceivingResponseLevel"]]
51.4	1010
	1011
47.3	1012	= 7. Trouble Shooting =
	1013
	1014	== 7.1 Downlink doesn’t work, how to solve it? ==
	1015
57.20	1016	Please see this link for debug: [[LoRaWAN Communication Debug>>doc:Main.LoRaWAN Communication Debug.WebHome]]
47.3	1017
	1018
	1019	== 7.2 Why I can’t join TTN V3 in US915 /AU915 bands? ==
	1020
57.20	1021	It might about the channels mapping. Please see for detail: [[Notice of Frequency band>>doc:Main.LoRaWAN Communication Debug.WebHome\|\|anchor="H2.NoticeofUS9152FCN4702FAU915Frequencyband"]]
47.3	1022
	1023
	1024	= 8. Order Info =
	1025
51.8	1026	(% style="color:blue" %)Part Number: RS485-LN-XXX
47.3	1027
	1028	(% style="color:blue" %)XXX:
	1029
	1030	* (% style="color:blue" %)EU433(%%): frequency bands EU433
	1031	* (% style="color:blue" %)EU868(%%): frequency bands EU868
	1032	* (% style="color:blue" %)KR920(%%): frequency bands KR920
	1033	* (% style="color:blue" %)CN470(%%): frequency bands CN470
	1034	* (% style="color:blue" %)AS923(%%): frequency bands AS923
	1035	* (% style="color:blue" %)AU915(%%): frequency bands AU915
	1036	* (% style="color:blue" %)US915(%%): frequency bands US915
	1037	* (% style="color:blue" %)IN865(%%): frequency bands IN865
	1038	* (% style="color:blue" %)RU864(%%): frequency bands RU864
	1039	* (% style="color:blue" %)KZ865(%%): frequency bands KZ865
	1040
51.8	1041	= 9.Packing Info =
	1042
	1043
	1044	Package Includes:
	1045
	1046	* RS485-LN x 1
	1047	* Stick Antenna for LoRa RF part x 1
	1048	* Program cable x 1
	1049
	1050	Dimension and weight:
	1051
	1052	* Device Size: 13.5 x 7 x 3 cm
	1053	* Device Weight: 105g
	1054	* Package Size / pcs : 14.5 x 8 x 5 cm
	1055	* Weight / pcs : 170g
	1056
	1057	= 10. FCC Caution for RS485LN-US915 =
	1058
	1059	Any Changes or modifications not expressly approved by the party responsible for compliance could void the user's authority to operate the equipment.
	1060
	1061	This device complies with part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) This device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation.
	1062
	1063
	1064	IMPORTANT NOTE:
	1065
	1066	Note: This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following measures:
	1067
	1068	—Reorient or relocate the receiving antenna.
	1069
	1070	—Increase the separation between the equipment and receiver.
	1071
	1072	—Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.
	1073
	1074	—Consult the dealer or an experienced radio/TV technician for help.
	1075
	1076
	1077	FCC Radiation Exposure Statement:
	1078
	1079	This equipment complies with FCC radiation exposure limits set forth for an uncontrolled environment.This equipment should be installed and operated with minimum distance 20cm between the radiator& your body.
	1080
	1081
	1082	= 11. Support =
	1083
	1084	* 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.
	1085	* Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[support@dragino.com>>url:file:///D:/市场资料/说明书/LoRa/LT系列/support@dragino.com]].

Wiki source code of RS485-LN – RS485 to LoRaWAN Converter

Applications