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

Version 57.21 by Xiaoling on 2022/06/06 09:14

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
57.21	85
3.3	86	== 1.3 Features ==
2.2	87
19.4	88	* LoRaWAN Class A & Class C protocol (default Class C)
2.2	89	* Frequency Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/IN865/RU864
	90	* AT Commands to change parameters
19.4	91	* Remote configure parameters via LoRa Downlink
2.2	92	* Firmware upgradable via program port
	93	* Support multiply RS485 devices by flexible rules
	94	* Support Modbus protocol
19.4	95	* Support Interrupt uplink (Since hardware version v1.2)
2.2	96
57.21	97
3.3	98	== 1.4 Applications ==
2.2	99
	100	* Smart Buildings & Home Automation
	101	* Logistics and Supply Chain Management
	102	* Smart Metering
	103	* Smart Agriculture
	104	* Smart Cities
	105	* Smart Factory
	106
57.21	107
6.2	108	== 1.5 Firmware Change log ==
2.2	109
19.4	110	[[RS485-LN Image files – Download link and Change log>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/]]
2.2	111
32.10	112
4.2	113	== 1.6 Hardware Change log ==
2.2	114
4.2	115	(((
	116	(((
19.4	117	v1.2: Add External Interrupt Pin.
2.2	118
19.4	119	v1.0: Release
32.10	120
	121
4.2	122	)))
	123	)))
2.2	124
20.2	125	= 2. Power ON Device =
2.2	126
6.2	127	(((
20.2	128	The RS485-LN can be powered by 7 ~~ 24V DC power source. Connection as below
2.2	129
20.2	130	* Power Source VIN to RS485-LN VIN+
	131	* Power Source GND to RS485-LN VIN-
2.2	132
20.3	133	(((
20.2	134	Once there is power, the RS485-LN will be on.
20.3	135	)))
2.2	136
57.20	137	[[image:1653268091319-405.png]]
32.11	138
	139
20.2	140	)))
2.2	141
6.2	142	= 3. Operation Mode =
2.2	143
6.2	144	== 3.1 How it works? ==
2.2	145
7.2	146	(((
21.2	147	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	148
	149
7.2	150	)))
2.2	151
7.2	152	== 3.2 Example to join LoRaWAN network ==
2.2	153
6.2	154	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	155
57.20	156	[[image:1653268155545-638.png\|\|height="334" width="724"]]
2.2	157
32.13	158
15.3	159	(((
32.13	160	(((
22.2	161	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	162	)))
2.2	163
32.13	164	(((
22.2	165	485A+ and 485B- of the sensor are connected to RS485A and RA485B of RS485-LN respectively.
32.13	166	)))
22.2	167
57.20	168	[[image:1653268227651-549.png\|\|height="592" width="720"]]
22.2	169
15.3	170	(((
57.20	171	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	172	)))
2.2	173
15.3	174	(((
22.2	175	Step 1: Create a device in TTN V3 with the OTAA keys from RS485-LN.
15.3	176	)))
2.2	177
15.3	178	(((
22.2	179	Each RS485-LN is shipped with a sticker with unique device EUI:
15.3	180	)))
22.2	181	)))
2.2	182
57.20	183	[[image:1652953462722-299.png]]
2.2	184
15.3	185	(((
22.3	186	(((
2.2	187	User can enter this key in their LoRaWAN Server portal. Below is TTN V3 screen shot:
15.3	188	)))
2.2	189
15.3	190	(((
2.2	191	Add APP EUI in the application.
15.3	192	)))
22.3	193	)))
2.2	194
57.20	195	[[image:image-20220519174512-1.png]]
2.2	196
57.20	197	[[image:image-20220519174512-2.png\|\|height="323" width="720"]]
2.2	198
57.20	199	[[image:image-20220519174512-3.png\|\|height="556" width="724"]]
2.2	200
57.20	201	[[image:image-20220519174512-4.png]]
2.2	202
	203	You can also choose to create the device manually.
	204
57.20	205	[[image:1652953542269-423.png\|\|height="710" width="723"]]
2.2	206
	207	Add APP KEY and DEV EUI
	208
57.20	209	[[image:1652953553383-907.png\|\|height="514" width="724"]]
2.2	210
	211
15.2	212	(((
22.4	213	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	214	)))
2.2	215
57.20	216	[[image:1652953568895-172.png\|\|height="232" width="724"]]
2.2	217
32.14	218
15.5	219	== 3.3 Configure Commands to read data ==
2.2	220
15.5	221	(((
22.4	222	(((
57.20	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.
15.5	224	)))
2.2	225
22.4	226	(((
	227	(% 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	228
	229
22.4	230	)))
	231	)))
	232
15.5	233	=== 3.3.1 onfigure UART settings for RS485 or TTL communication ===
2.2	234
22.6	235	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	236
32.16	237	(% border="1" style="background-color:#ffffcc; color:green; width:782px" %)
	238	\|(% style="width:128px" %)(((
15.5	239	AT Commands
32.16	240	)))\|(% style="width:305px" %)(((
15.5	241	Description
32.16	242	)))\|(% style="width:346px" %)(((
15.5	243	Example
	244	)))
32.16	245	\|(% style="width:128px" %)(((
15.5	246	AT+BAUDR
32.16	247	)))\|(% style="width:305px" %)(((
15.5	248	Set the baud rate (for RS485 connection). Default Value is: 9600.
32.16	249	)))\|(% style="width:346px" %)(((
15.5	250	(((
2.2	251	AT+BAUDR=9600
15.5	252	)))
2.2	253
15.5	254	(((
2.2	255	Options: (1200,2400,4800,14400,19200,115200)
	256	)))
15.5	257	)))
32.16	258	\|(% style="width:128px" %)(((
15.5	259	AT+PARITY
32.16	260	)))\|(% style="width:305px" %)(((
2.2	261	Set UART parity (for RS485 connection)
32.16	262	)))\|(% style="width:346px" %)(((
15.5	263	(((
2.2	264	AT+PARITY=0
15.5	265	)))
2.2	266
15.5	267	(((
2.2	268	Option: 0: no parity, 1: odd parity, 2: even parity
	269	)))
15.5	270	)))
32.16	271	\|(% style="width:128px" %)(((
15.5	272	AT+STOPBIT
32.16	273	)))\|(% style="width:305px" %)(((
15.5	274	(((
2.2	275	Set serial stopbit (for RS485 connection)
15.5	276	)))
2.2	277
15.5	278	(((
22.6	279
15.5	280	)))
32.16	281	)))\|(% style="width:346px" %)(((
15.5	282	(((
2.2	283	AT+STOPBIT=0 for 1bit
15.5	284	)))
2.2	285
15.5	286	(((
2.2	287	AT+STOPBIT=1 for 1.5 bit
15.5	288	)))
2.2	289
15.5	290	(((
2.2	291	AT+STOPBIT=2 for 2 bits
	292	)))
15.5	293	)))
2.2	294
57.14	295
57.21	296
15.6	297	=== 3.3.2 Configure sensors ===
2.2	298
15.6	299	(((
	300	(((
22.7	301	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	302	)))
22.7	303	)))
2.2	304
15.6	305	(% border="1" style="background-color:#ffffcc; color:green; width:806px" %)
	306	\|AT Commands\|(% style="width:418px" %)Description\|(% style="width:256px" %)Example
	307	\|AT+CFGDEV\|(% style="width:418px" %)(((
2.2	308	This command is used to configure the RS485/TTL devices; they won’t be used during sampling.
	309
15.6	310	AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,
2.2	311
15.6	312	mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
	313	)))\|(% style="width:256px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
2.2	314
57.15	315
57.21	316
15.6	317	=== 3.3.3 Configure read commands for each sampling ===
2.2	318
15.6	319	(((
35.2	320	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	321
	322	To save the LoRaWAN network bandwidth, we might need to read data from different sensors and combine their valid value into a short payload.
	323
	324	This section describes how to achieve above goals.
	325
35.2	326	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	327
	328
35.2	329	Each RS485 commands include two parts:
2.2	330
35.2	331	~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	332
35.2	333	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	334
35.4	335	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	336
	337
	338	After we got the valid value from each RS485 commands, we need to combine them together with the command AT+DATAUP.
	339
	340
	341	Below are examples for the how above AT Commands works.
	342
	343
35.2	344	AT+COMMANDx : This command will be sent to RS485 devices during each sampling, Max command length is 14 bytes. The grammar is:
	345
	346	(% border="1" style="background-color:#4bacc6; color:white; width:499px" %)
	347	\|(% style="width:496px" %)(((
2.2	348	AT+COMMANDx=xx xx xx xx xx xx xx xx xx xx xx xx,m
	349
	350	xx xx xx xx xx xx xx xx xx xx xx xx: The RS485 command to be sent
	351
	352	m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
	353	)))
	354
	355	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.
	356
35.2	357	In the RS485-LN, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
2.2	358
	359
	360	AT+DATACUTx : This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes.
	361
35.2	362	(% border="1" style="background-color:#4bacc6; color:white; width:725px" %)
	363	\|(% style="width:722px" %)(((
2.2	364	AT+DATACUTx=a,b,c
	365
	366	* a: length for the return of AT+COMMAND
	367	* b:1: grab valid value by byte, max 6 bytes. 2: grab valid value by bytes section, max 3 sections.
35.5	368	* c: define the position for valid value.
2.2	369	)))
	370
35.2	371	Examples:
	372
2.2	373	* Grab bytes:
	374
57.20	375	[[image:image-20220602153621-1.png]]
2.2	376
35.2	377
2.2	378	* Grab a section.
	379
57.20	380	[[image:image-20220602153621-2.png]]
2.2	381
35.2	382
2.2	383	* Grab different sections.
	384
57.20	385	[[image:image-20220602153621-3.png]]
35.3	386
	387
35.2	388	)))
2.2	389
29.2	390	=== 3.3.4 Compose the uplink payload ===
2.2	391
29.2	392	(((
2.2	393	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	394
	395
29.2	396	)))
2.2	397
29.2	398	(((
35.5	399	(% style="color:#037691" %)Examples: AT+DATAUP=0
	400
	401
29.2	402	)))
2.2	403
29.2	404	(((
	405	Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)A SIGNLE UPLINK.
	406	)))
2.2	407
29.2	408	(((
2.2	409	Final Payload is
29.2	410	)))
2.2	411
29.2	412	(((
	413	(% style="color:#4f81bd" %)Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx
	414	)))
2.2	415
29.2	416	(((
2.2	417	Where PAYVER is defined by AT+PAYVER, below is an example screen shot.
29.2	418	)))
2.2	419
57.20	420	[[image:1653269759169-150.png\|\|height="513" width="716"]]
2.2	421
35.5	422
35.6	423	(% style="color:#037691" %)Examples: AT+DATAUP=1
2.2	424
35.5	425
30.2	426	Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)Multiply UPLINKs.
2.2	427
	428	Final Payload is
	429
30.2	430	(% style="color:#4f81bd" %)Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA
2.2	431
57.16	432
36.2	433	1. PAYVER: Defined by AT+PAYVER
	434	1. PAYLOAD COUNT: Total how many uplinks of this sampling.
	435	1. PAYLOAD#: Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
	436	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	437
57.20	438	[[image:image-20220602155039-4.png]]
2.2	439
	440
36.2	441	So totally there will be 3 uplinks for this sampling, each uplink include 8 bytes DATA
2.2	442
36.2	443	DATA1=RETURN1 Valid Value + the first two of Valid value of RETURN10= 20 20 0a 33 90 41 02 aa
2.2	444
36.2	445	DATA2=3^^rd^^ ~~ 10^^th^^ byte of Valid value of RETURN10= 05 81 0a 20 20 20 20 2d
2.2	446
36.2	447	DATA3=the rest of Valid value of RETURN10= 30
2.2	448
36.2	449
	450	(% 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:
	451
	452	~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink.
	453
	454	* For AU915/AS923 bands, if UplinkDwell time=0, max 11 bytes for each uplink.
	455
	456	* For US915 band, max 11 bytes for each uplink.
	457
	458	~* For all other bands: max 51 bytes for each uplink.
	459
	460
2.2	461	Below are the uplink payloads:
	462
57.20	463	[[image:1654157178836-407.png]]
2.2	464
	465
31.3	466	=== 3.3.5 Uplink on demand ===
2.2	467
37.4	468	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	469
	470	Downlink control command:
	471
37.4	472	0x08 command: Poll an uplink with current command set in RS485-LN.
2.2	473
37.4	474	0xA8 command: Send a command to RS485-LN and uplink the output from sensors.
2.2	475
	476
	477
38.2	478	=== 3.3.6 Uplink on Interrupt ===
2.2	479
38.2	480	RS485-LN support external Interrupt uplink since hardware v1.2 release.
2.2	481
57.20	482	[[image:1654157342174-798.png]]
2.2	483
38.2	484	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	485
	486
38.4	487	== 3.4 Uplink Payload ==
2.2	488
38.4	489	(% border="1" style="background-color:#4bacc6; color:white; width:734px" %)
	490	\|Size(bytes)\|(% style="width:120px" %)2\|(% style="width:116px" %)1\|(% style="width:386px" %)Length depends on the return from the commands
	491	\|Value\|(% style="width:120px" %)(((
2.2	492	Battery(mV)
	493
	494	&
	495
	496	Interrupt _Flag
38.4	497	)))\|(% style="width:116px" %)(((
2.2	498	PAYLOAD_VER
	499
	500
38.4	501	)))\|(% 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	502
	503	Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors.
	504
	505
38.4	506	== 3.5 Configure RS485-BL via AT or Downlink ==
2.2	507
38.4	508	User can configure RS485-LN via AT Commands or LoRaWAN Downlink Commands
2.2	509
38.4	510	There are two kinds of Commands:
2.2	511
57.20	512	* (% 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	513
38.4	514	* (% style="color:#4f81bd" %)Sensor Related Commands(%%): These commands are special designed for RS485-LN. User can see these commands below:
2.2	515
57.17	516
57.21	517
38.4	518	=== 3.5.1 Common Commands ===
2.2	519
57.20	520	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	521
	522
41.1	523	=== 3.5.2 Sensor related commands ===
2.2	524
41.1	525	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	526
57.20	527	[[image:image-20220602163333-5.png\|\|height="263" width="1160"]]
2.2	528
41.1	529	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	530
	531
42.2	532	=== 3.5.3 Sensor related commands ===
2.2	533
	534
57.6	535
42.2	536	==== RS485 Debug Command ====
	537
	538	This command is used to configure the RS485 devices; they won’t be used during sampling.
	539
	540	* AT Command
	541
	542	(% class="box infomessage" %)
	543	(((
	544	AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
	545	)))
	546
	547	m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
	548
	549	* Downlink Payload
	550
	551	Format: A8 MM NN XX XX XX XX YY
	552
	553	Where:
	554
	555	* MM: 1: add CRC-16/MODBUS ; 0: no CRC
	556	* NN: The length of RS485 command
	557	* XX XX XX XX: RS485 command total NN bytes
	558	* YY: How many bytes will be uplink from the return of this RS485 command,
	559	** if YY=0, RS485-LN will execute the downlink command without uplink;
	560	** if YY>0, RS485-LN will uplink total YY bytes from the output of this RS485 command; Fport=200
	561	** if YY=FF, RS485-LN will uplink RS485 output with the downlink command content; Fport=200.
	562
	563	Example 1 ~-~-> Configure without ask for uplink (YY=0)
	564
	565	To connect a Modbus Alarm with below commands.
	566
	567	* 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.
	568
	569	* 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.
	570
	571	So if user want to use downlink command to control to RS485 Alarm, he can use:
	572
	573	(% style="color:#4f81bd" %)A8 01 06 0A 05 00 04 00 01 00(%%): to activate the RS485 Alarm
	574
	575	(% style="color:#4f81bd" %)A8 01 06 0A 05 00 04 00 00 00(%%): to deactivate the RS485 Alarm
	576
	577	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.
	578
	579
	580	Example 2 ~-~-> Configure with requesting uplink and original downlink command (YY=FF)
	581
	582	User in IoT server send a downlink command: (% style="color:#4f81bd" %)A8 01 06 0A 08 00 04 00 01 YY
	583
	584
	585	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:
	586
	587	A8 (% style="color:#4f81bd" %)0A 08 00 04 00 (% style="color:red" %)01 06 (% style="color:green" %)0A 08 00 04 00 00
	588
57.20	589	[[image:1654159460680-153.png]]
42.2	590
42.3	591
	592
	593	==== Set Payload version ====
	594
	595	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.
	596
	597	* AT Command:
	598
	599	(% class="box infomessage" %)
	600	(((
	601	AT+PAYVER: Set PAYVER field = 1
	602	)))
	603
	604	* Downlink Payload:
	605
	606	0xAE 01 ~-~-> Set PAYVER field = 0x01
	607
	608	0xAE 0F ~-~-> Set PAYVER field = 0x0F
	609
	610
	611
	612	==== Set RS485 Sampling Commands ====
	613
44.2	614	AT+COMMANDx or AT+DATACUTx
42.3	615
57.20	616	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	617
	618
	619	* AT Command:
	620
	621	(% class="box infomessage" %)
	622	(((
	623	AT+COMMANDx: Configure RS485 read command to sensor.
	624	)))
	625
	626	(% class="box infomessage" %)
	627	(((
	628	AT+DATACUTx: Configure how to handle return from RS485 devices.
	629	)))
	630
	631
	632	* Downlink Payload:
	633
	634	0xAF downlink command can be used to set AT+COMMANDx or AT+DATACUTx.
	635
	636	(% style="color:red" %)Note(%%): if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink.
	637
	638	Format: AF MM NN LL XX XX XX XX YY
	639
	640	Where:
	641
	642	* MM: the ATCOMMAND or AT+DATACUT to be set. Value from 01 ~~ 0F,
	643	* NN: 0: no CRC; 1: add CRC-16/MODBUS ; 2: set the AT+DATACUT value.
	644	* LL: The length of AT+COMMAND or AT+DATACUT command
	645	* XX XX XX XX: AT+COMMAND or AT+DATACUT command
44.2	646	* 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	647
	648	Example:
	649
	650	(% 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
	651
	652	(% 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
	653
	654	(% 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
	655
	656
	657
	658	==== Fast command to handle MODBUS device ====
	659
	660	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]].
	661
	662	This command is valid since v1.3 firmware version
	663
44.2	664	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	665
	666
	667	Example:
	668
44.2	669	* AT+MBFUN=1 and AT+DATACUT1/AT+DATACUT2 are not configure (0,0,0). So RS485-LN.
42.3	670	* 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.
	671	* 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.
	672
57.20	673	[[image:image-20220602165351-6.png]]
42.3	674
57.20	675	[[image:image-20220602165351-7.png]]
42.3	676
	677
	678
	679	==== RS485 command timeout ====
	680
44.3	681	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	682
44.3	683	Default value: 0, range: 0 ~~ 65 seconds
42.3	684
	685	* AT Command:
	686
	687	(% class="box infomessage" %)
	688	(((
44.3	689	*AT+CMDDLaa=hex(bb cc)1000**
42.3	690	)))
	691
	692	Example:
	693
	694	AT+CMDDL1=1000 to send the open time to 1000ms
	695
	696
	697	* Downlink Payload:
	698
44.3	699	0x AA aa bb cc
42.3	700
44.3	701	Same as: AT+CMDDLaa=hex(bb cc)*1000
42.3	702
	703	Example:
	704
44.3	705	0xAA 01 00 01 ~-~-> Same as AT+CMDDL1=1000 ms
42.3	706
	707
	708
	709	==== Uplink payload mode ====
	710
	711	Define to use one uplink or multiple uplinks for the sampling.
	712
57.20	713	The use of this command please see: [[Compose Uplink payload>>\|\|anchor="H3.3.4Composetheuplinkpayload"]]
42.3	714
	715	* AT Command:
	716
	717	(% class="box infomessage" %)
	718	(((
	719	AT+DATAUP=0
	720	)))
	721
	722	(% class="box infomessage" %)
	723	(((
	724	AT+DATAUP=1
	725	)))
	726
	727
	728	* Downlink Payload:
	729
	730	0xAD 00 ~-~-> Same as AT+DATAUP=0
	731
	732	0xAD 01 ~-~-> Same as AT+DATAUP=1
	733
	734
	735
	736	==== Manually trigger an Uplink ====
	737
	738	Ask device to send an uplink immediately.
	739
45.2	740	* AT Command:
	741
57.21	742	No AT Command for this, user can press the [[ACT button>>\|\|anchor="3.7Buttons"]] for 1 second for the same.
45.2	743
	744
42.3	745	* Downlink Payload:
	746
45.2	747	0x08 FF, RS485-LN will immediately send an uplink.
42.3	748
	749
	750
	751	==== Clear RS485 Command ====
	752
	753	The AT+COMMANDx and AT+DATACUTx settings are stored in special location, user can use below command to clear them.
	754
	755	* AT Command:
	756
45.2	757	AT+CMDEAR=mm,nn mm: start position of erase ,nn: stop position of erase
	758
	759	Etc. AT+CMDEAR=1,10 means erase AT+COMMAND1/AT+DATACUT1 to AT+COMMAND10/AT+DATACUT10
	760
47.2	761	Example screen shot after clear all RS485 commands.
45.2	762
	763
	764	The uplink screen shot is:
	765
57.20	766	[[image:1654160691922-496.png]][[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image001.png]]
45.2	767
	768
45.3	769	* Downlink Payload:
45.2	770
45.3	771	0x09 aa bb same as AT+CMDEAR=aa,bb
45.2	772
	773
45.3	774
42.3	775	==== Set Serial Communication Parameters ====
	776
	777	Set the Rs485 serial communication parameters:
	778
	779	* AT Command:
	780
	781	Set Baud Rate:
	782
	783	(% class="box infomessage" %)
	784	(((
	785	AT+BAUDR=9600 ~/~/ Options: (1200,2400,4800,14400,19200,115200)
	786	)))
	787
	788	Set UART Parity
	789
	790	(% class="box infomessage" %)
	791	(((
	792	AT+PARITY=0 ~/~/ Option: 0: no parity, 1: odd parity, 2: even parity
	793	)))
	794
	795	Set STOPBIT
	796
	797	(% class="box infomessage" %)
	798	(((
	799	AT+STOPBIT=0 ~/~/ Option: 0 for 1bit; 1 for 1.5 bit ; 2 for 2 bits
	800	)))
	801
	802
	803	* Downlink Payload:
	804
	805	A7 01 aa bb: Same AT+BAUDR=hex(aa bb)*100
	806
	807	Example:
	808
	809	* A7 01 00 60 same as AT+BAUDR=9600
	810	* A7 01 04 80 same as AT+BAUDR=115200
	811
	812	A7 02 aa: Same as AT+PARITY=aa (aa value: 00 , 01 or 02)
	813
	814	A7 03 aa: Same as AT+STOPBIT=aa (aa value: 00 , 01 or 02)
	815
	816
47.2	817	== 3.6 Listening mode for RS485 network ==
42.3	818
47.2	819	This feature support since firmware v1.4
	820
	821	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.
	822
57.20	823	[[image:image-20220602171200-8.png\|\|height="567" width="1007"]]
47.2	824
	825	To enable the listening mode, use can run the command AT+RXMODE.
	826
	827
	828	(% border="1" style="background-color:#ffffcc; width:500px" %)
	829	\|=(% style="width: 161px;" %)Command example:\|=(% style="width: 337px;" %)Function
	830	\|(% 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.
	831	\|(% 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
	832	\|(% style="width:161px" %)AT+RXMODE=0,0\|(% style="width:337px" %)Disable listening mode. This is the default settings.
	833	\|(% style="width:161px" %) \|(% style="width:337px" %)A6 aa bb cc same as AT+RXMODE=aa,(bb<<8 ~\| cc)
	834
	835	Downlink Command:
	836
	837	0xA6 aa bb cc same as AT+RXMODE=aa,(bb<<8 \| cc)
	838
	839
	840	Example:
	841
	842	The RS485-LN is set to AT+RXMODE=2,1000
	843
	844	There is a two Modbus commands in the RS485 network as below:
	845
	846	The Modbus master send a command: (% style="background-color:#ffc000" %)01 03 00 00 00 02 c4 0b
	847
	848	And Modbus slave reply with: (% style="background-color:green" %)01 03 04 00 00 00 00 fa 33
	849
	850	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
	851
57.20	852	[[image:image-20220602171200-9.png]]
47.2	853
	854
47.3	855	(% 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	856
	857
47.3	858	== 3.7 Buttons ==
	859
	860
	861	(% border="1" style="background-color:#f7faff; width:500px" %)
	862	\|=Button\|=(% style="width: 1420px;" %)Feature
	863	\|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
	864	\|RST\|(% style="width:1420px" %)Reboot RS485
57.20	865	\|PRO\|(% style="width:1420px" %)Use for upload image, see [[How to Update Image>>path:#upgrade_image]]
47.3	866
57.21	867
47.3	868	== 3.8 LEDs ==
	869
	870	(% border="1" style="background-color:#f7faff; width:500px" %)
	871	\|=LEDs\|=Feature
	872	\|PWR\|Always on if there is power
	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
57.21	875
47.3	876	= 4. Case Study =
	877
57.20	878	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	879
	880
	881	= 5. Use AT Command =
	882
	883	== 5.1 Access AT Command ==
	884
	885	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.
	886
57.20	887	[[image:1654162355560-817.png]]
47.3	888
	889
	890	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:
	891
57.20	892	[[image:1654162368066-342.png]]
47.3	893
	894
57.20	895	More detail AT Command manual can be found at [[AT Command Manual>>\|\|anchor="3.5ConfigureRS485-BLviaATorDownlink"]]
47.3	896
	897
	898	== 5.2 Common AT Command Sequence ==
	899
	900	=== 5.2.1 Multi-channel ABP mode (Use with SX1301/LG308) ===
	901
	902	If device has not joined network yet:
	903
	904	(% class="box infomessage" %)
	905	(((
	906	AT+FDR
	907	)))
	908
	909	(% class="box infomessage" %)
	910	(((
	911	AT+NJM=0
	912	)))
	913
	914	(% class="box infomessage" %)
	915	(((
	916	ATZ
	917	)))
	918
	919
	920	If device already joined network:
	921
	922	(% class="box infomessage" %)
	923	(((
	924	AT+NJM=0
	925	)))
	926
	927	(% class="box infomessage" %)
	928	(((
	929	ATZ
	930	)))
	931
	932
	933	=== 5.5.2 Single-channel ABP mode (Use with LG01/LG02) ===
	934
	935
49.3	936	(% style="background-color:#dcdcdc" %)AT+FDR (%%) Reset Parameters to Factory Default, Keys Reserve
47.3	937
	938	(% style="background-color:#dcdcdc" %)AT+NJM=0 (%%)Set to ABP mode
	939
	940	(% style="background-color:#dcdcdc" %)AT+ADR=0 (%%)Set the Adaptive Data Rate Off
	941
51.3	942	(% style="background-color:#dcdcdc" %)AT+DR=5 (%%)Set Data Rate
47.3	943
	944	(% style="background-color:#dcdcdc" %)AT+TDC=60000 (%%) Set transmit interval to 60 seconds
	945
	946	(% style="background-color:#dcdcdc" %)AT+CHS=868400000(%%) Set transmit frequency to 868.4Mhz
	947
	948	(% style="background-color:#dcdcdc" %)AT+RX2FQ=868400000 (%%) Set RX2Frequency to 868.4Mhz (according to the result from server)
	949
	950	(% style="background-color:#dcdcdc" %)AT+RX2DR=5 (%%) Set RX2DR to match the downlink DR from server. see below
	951
	952	(% 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.
	953
	954	(% style="background-color:#dcdcdc" %)ATZ (%%) Reset MCU
	955
	956
	957	(% style="color:red" %)Note:
	958
	959	(% style="color:red" %)1. Make sure the device is set to ABP mode in the IoT Server.
	960	2. Make sure the LG01/02 gateway RX frequency is exactly the same as AT+CHS setting.
	961	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.
	962	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
	963
57.20	964	[[image:1654162478620-421.png]]
47.3	965
	966
	967	= 6. FAQ =
	968
	969	== 6.1 How to upgrade the image? ==
	970
51.2	971	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	972
	973	* Support new features
	974	* For bug fix
	975	* Change LoRaWAN bands.
	976
51.2	977	Below shows the hardware connection for how to upload an image to RS485-LN:
47.3	978
57.20	979	[[image:1654162535040-878.png]]
47.3	980
	981	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]].
	982
	983	Step2: Download the [[LT Image files>>url:http://www.dragino.com/downloads/index.php?dir=LT_LoRa_IO_Controller/LT33222-L/image/]].
	984
	985	Step3: Open flashloader; choose the correct COM port to update.
	986
52.2	987	(% 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	988
47.3	989
57.20	990	[[image:image-20220602175818-12.png]]
47.3	991
	992
57.20	993	[[image:image-20220602175848-13.png]]
47.3	994
	995
57.20	996	[[image:image-20220602175912-14.png]]
56.2	997
56.4	998
52.2	999	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	1000
57.20	1001	[[image:image-20220602175638-10.png]]
52.2	1002
	1003
47.3	1004	== 6.2 How to change the LoRa Frequency Bands/Region? ==
	1005
57.20	1006	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	1007
	1008
	1009	== 6.3 How many RS485-Slave can RS485-BL connects? ==
	1010
57.20	1011	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	1012
	1013
51.4	1014	== 6.4 Compatible question to ChirpStack and TTI LoRaWAN server ? ==
47.3	1015
51.4	1016	When user need to use with ChirpStack or TTI. Please set AT+RPL=4.
	1017
57.20	1018	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	1019
	1020
47.3	1021	= 7. Trouble Shooting =
	1022
	1023	== 7.1 Downlink doesn’t work, how to solve it? ==
	1024
57.20	1025	Please see this link for debug: [[LoRaWAN Communication Debug>>doc:Main.LoRaWAN Communication Debug.WebHome]]
47.3	1026
	1027
	1028	== 7.2 Why I can’t join TTN V3 in US915 /AU915 bands? ==
	1029
57.20	1030	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	1031
	1032
	1033	= 8. Order Info =
	1034
51.8	1035	(% style="color:blue" %)Part Number: RS485-LN-XXX
47.3	1036
	1037	(% style="color:blue" %)XXX:
	1038
	1039	* (% style="color:blue" %)EU433(%%): frequency bands EU433
	1040	* (% style="color:blue" %)EU868(%%): frequency bands EU868
	1041	* (% style="color:blue" %)KR920(%%): frequency bands KR920
	1042	* (% style="color:blue" %)CN470(%%): frequency bands CN470
	1043	* (% style="color:blue" %)AS923(%%): frequency bands AS923
	1044	* (% style="color:blue" %)AU915(%%): frequency bands AU915
	1045	* (% style="color:blue" %)US915(%%): frequency bands US915
	1046	* (% style="color:blue" %)IN865(%%): frequency bands IN865
	1047	* (% style="color:blue" %)RU864(%%): frequency bands RU864
	1048	* (% style="color:blue" %)KZ865(%%): frequency bands KZ865
	1049
57.21	1050
51.8	1051	= 9.Packing Info =
	1052
	1053
	1054	Package Includes:
	1055
	1056	* RS485-LN x 1
	1057	* Stick Antenna for LoRa RF part x 1
	1058	* Program cable x 1
	1059
	1060	Dimension and weight:
	1061
	1062	* Device Size: 13.5 x 7 x 3 cm
	1063	* Device Weight: 105g
	1064	* Package Size / pcs : 14.5 x 8 x 5 cm
	1065	* Weight / pcs : 170g
	1066
57.21	1067
51.8	1068	= 10. FCC Caution for RS485LN-US915 =
	1069
	1070	Any Changes or modifications not expressly approved by the party responsible for compliance could void the user's authority to operate the equipment.
	1071
	1072	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.
	1073
	1074
	1075	IMPORTANT NOTE:
	1076
	1077	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:
	1078
	1079	—Reorient or relocate the receiving antenna.
	1080
	1081	—Increase the separation between the equipment and receiver.
	1082
	1083	—Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.
	1084
	1085	—Consult the dealer or an experienced radio/TV technician for help.
	1086
	1087
	1088	FCC Radiation Exposure Statement:
	1089
	1090	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.
	1091
	1092
	1093	= 11. Support =
	1094
	1095	* 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.
	1096	* 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