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

Version 32.11 by Xiaoling on 2022/06/02 15:26

version	line-number	content
3.2	1	(% style="text-align:center" %)
18.2	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
3.2	9	Table of Contents:
1.1	10
	11
	12
	13
	14
3.2	15	= 1.Introduction =
1.1	16
19.2	17	== 1.1 What is RS485-LN RS485 to LoRaWAN Converter ==
1.1	18
3.2	19	(((
	20	(((
32.3	21	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	22	)))
2.2	23
3.2	24	(((
32.3	25	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	26	)))
2.2	27
3.2	28	(((
32.3	29	(% 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	30	)))
2.2	31
3.2	32	(((
32.3	33	(% 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	34
32.3	35	(% 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	36	)))
	37	)))
2.2	38
19.2	39	[[image:1653267211009-519.png\|\|height="419" width="724"]]
2.2	40
32.4	41
3.2	42	== 1.2 Specifications ==
2.2	43
32.6	44
2.2	45	Hardware System:
	46
	47	* STM32L072CZT6 MCU
22.4	48	* SX1276/78 Wireless Chip
2.2	49	* Power Consumption (exclude RS485 device):
19.3	50	** Idle: 32mA@12v
	51	** 20dB Transmit: 65mA@12v
2.2	52
	53	Interface for Model:
	54
19.3	55	* RS485
22.4	56	* Power Input 7~~ 24V DC.
2.2	57
	58	LoRa Spec:
	59
	60	* Frequency Range:
	61	** Band 1 (HF): 862 ~~ 1020 Mhz
	62	** Band 2 (LF): 410 ~~ 528 Mhz
	63	* 168 dB maximum link budget.
	64	* +20 dBm - 100 mW constant RF output vs.
19.3	65	* +14 dBm high efficiency PA.
2.2	66	* Programmable bit rate up to 300 kbps.
	67	* High sensitivity: down to -148 dBm.
	68	* Bullet-proof front end: IIP3 = -12.5 dBm.
	69	* Excellent blocking immunity.
19.3	70	* Low RX current of 10.3 mA, 200 nA register retention.
2.2	71	* Fully integrated synthesizer with a resolution of 61 Hz.
19.3	72	* FSK, GFSK, MSK, GMSK, LoRaTM and OOK modulation.
2.2	73	* Built-in bit synchronizer for clock recovery.
	74	* Preamble detection.
	75	* 127 dB Dynamic Range RSSI.
19.3	76	* Automatic RF Sense and CAD with ultra-fast AFC.
	77	* Packet engine up to 256 bytes with CRC.
2.2	78
32.7	79
	80
3.3	81	== 1.3 Features ==
2.2	82
19.4	83	* LoRaWAN Class A & Class C protocol (default Class C)
2.2	84	* Frequency Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/IN865/RU864
	85	* AT Commands to change parameters
19.4	86	* Remote configure parameters via LoRa Downlink
2.2	87	* Firmware upgradable via program port
	88	* Support multiply RS485 devices by flexible rules
	89	* Support Modbus protocol
19.4	90	* Support Interrupt uplink (Since hardware version v1.2)
2.2	91
32.7	92
	93
3.3	94	== 1.4 Applications ==
2.2	95
	96	* Smart Buildings & Home Automation
	97	* Logistics and Supply Chain Management
	98	* Smart Metering
	99	* Smart Agriculture
	100	* Smart Cities
	101	* Smart Factory
	102
32.8	103
	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
20.2	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.
7.2	145	)))
2.2	146
7.2	147	== 3.2 Example to join LoRaWAN network ==
2.2	148
6.2	149	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	150
21.2	151	[[image:1653268155545-638.png\|\|height="334" width="724"]]
2.2	152
15.3	153	(((
22.2	154	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:
2.2	155
22.2	156	485A+ and 485B- of the sensor are connected to RS485A and RA485B of RS485-LN respectively.
	157
	158	[[image:1653268227651-549.png\|\|height="592" width="720"]]
	159
15.3	160	(((
22.2	161	The LG308 is already set to connect to [[TTN V3 network >>path:eu1.cloud.thethings.network/]]. So what we need to now is only configure the TTN V3:
15.3	162	)))
2.2	163
15.3	164	(((
22.2	165	Step 1: Create a device in TTN V3 with the OTAA keys from RS485-LN.
15.3	166	)))
2.2	167
15.3	168	(((
22.2	169	Each RS485-LN is shipped with a sticker with unique device EUI:
15.3	170	)))
22.2	171	)))
2.2	172
15.2	173	[[image:1652953462722-299.png]]
2.2	174
15.3	175	(((
22.3	176	(((
2.2	177	User can enter this key in their LoRaWAN Server portal. Below is TTN V3 screen shot:
15.3	178	)))
2.2	179
15.3	180	(((
2.2	181	Add APP EUI in the application.
15.3	182	)))
22.3	183	)))
2.2	184
15.2	185	[[image:image-20220519174512-1.png]]
2.2	186
22.3	187	[[image:image-20220519174512-2.png\|\|height="323" width="720"]]
2.2	188
15.2	189	[[image:image-20220519174512-3.png\|\|height="556" width="724"]]
2.2	190
15.2	191	[[image:image-20220519174512-4.png]]
2.2	192
	193	You can also choose to create the device manually.
	194
15.2	195	[[image:1652953542269-423.png\|\|height="710" width="723"]]
2.2	196
	197	Add APP KEY and DEV EUI
	198
15.2	199	[[image:1652953553383-907.png\|\|height="514" width="724"]]
2.2	200
	201
15.2	202	(((
22.4	203	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	204	)))
2.2	205
15.2	206	[[image:1652953568895-172.png\|\|height="232" width="724"]]
2.2	207
15.5	208	== 3.3 Configure Commands to read data ==
2.2	209
15.5	210	(((
22.4	211	(((
	212	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.
15.5	213	)))
2.2	214
22.4	215	(((
	216	(% 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
	217	)))
	218	)))
	219
15.5	220	=== 3.3.1 onfigure UART settings for RS485 or TTL communication ===
2.2	221
22.6	222	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	223
15.5	224	(% border="1" style="background-color:#ffffcc; color:green; width:795px" %)
	225	\|(((
	226	AT Commands
	227	)))\|(% style="width:285px" %)(((
	228	Description
	229	)))\|(% style="width:347px" %)(((
	230	Example
	231	)))
	232	\|(((
	233	AT+BAUDR
	234	)))\|(% style="width:285px" %)(((
	235	Set the baud rate (for RS485 connection). Default Value is: 9600.
	236	)))\|(% style="width:347px" %)(((
	237	(((
2.2	238	AT+BAUDR=9600
15.5	239	)))
2.2	240
15.5	241	(((
2.2	242	Options: (1200,2400,4800,14400,19200,115200)
	243	)))
15.5	244	)))
	245	\|(((
	246	AT+PARITY
	247	)))\|(% style="width:285px" %)(((
2.2	248	Set UART parity (for RS485 connection)
15.5	249	)))\|(% style="width:347px" %)(((
	250	(((
2.2	251	AT+PARITY=0
15.5	252	)))
2.2	253
15.5	254	(((
2.2	255	Option: 0: no parity, 1: odd parity, 2: even parity
	256	)))
15.5	257	)))
	258	\|(((
	259	AT+STOPBIT
	260	)))\|(% style="width:285px" %)(((
	261	(((
2.2	262	Set serial stopbit (for RS485 connection)
15.5	263	)))
2.2	264
15.5	265	(((
22.6	266
15.5	267	)))
	268	)))\|(% style="width:347px" %)(((
	269	(((
2.2	270	AT+STOPBIT=0 for 1bit
15.5	271	)))
2.2	272
15.5	273	(((
2.2	274	AT+STOPBIT=1 for 1.5 bit
15.5	275	)))
2.2	276
15.5	277	(((
2.2	278	AT+STOPBIT=2 for 2 bits
	279	)))
15.5	280	)))
2.2	281
15.6	282	=== 3.3.2 Configure sensors ===
2.2	283
15.6	284	(((
	285	(((
22.7	286	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	287	)))
22.7	288	)))
2.2	289
15.6	290	(% border="1" style="background-color:#ffffcc; color:green; width:806px" %)
	291	\|AT Commands\|(% style="width:418px" %)Description\|(% style="width:256px" %)Example
	292	\|AT+CFGDEV\|(% style="width:418px" %)(((
2.2	293	This command is used to configure the RS485/TTL devices; they won’t be used during sampling.
	294
15.6	295	AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,
2.2	296
15.6	297	mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
	298	)))\|(% style="width:256px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
2.2	299
15.6	300	=== 3.3.3 Configure read commands for each sampling ===
2.2	301
15.6	302	(((
2.2	303	RS485-BL is a battery powered device; it will sleep most of time. And wake up on each period and read RS485 / TTL sensor data and uplink.
15.6	304	)))
2.2	305
15.6	306	(((
2.2	307	During each sampling, we need to confirm what commands we need to send to the sensors to read data. After the RS485/TTL sensors send back the value, it normally includes some bytes and we only need a few from them for a shorten payload.
15.6	308	)))
2.2	309
15.6	310	(((
2.2	311	To save the LoRaWAN network bandwidth, we might need to read data from different sensors and combine their valid value into a short payload.
15.6	312	)))
2.2	313
15.6	314	(((
2.2	315	This section describes how to achieve above goals.
15.6	316	)))
2.2	317
15.6	318	(((
2.2	319	During each sampling, the RS485-BL can support 15 commands to read sensors. And combine the return to one or several uplink payloads.
15.6	320	)))
2.2	321
15.6	322	(((
2.2	323	Command from RS485-BL to Sensor:
15.6	324	)))
2.2	325
15.6	326	(((
2.2	327	RS485-BL can send out pre-set max 15 strings via AT+COMMAD1, ATCOMMAND2,…, to AT+COMMANDF . All commands are of same grammar.
15.6	328	)))
2.2	329
15.6	330	(((
2.2	331	Handle return from sensors to RS485-BL:
15.6	332	)))
2.2	333
15.6	334	(((
2.2	335	After RS485-BL send out a string to sensor, RS485-BL will wait for the return from RS485 or TTL sensor. And user can specify how to handle the return, by AT+DATACUT or AT+SEARCH commands
15.6	336	)))
2.2	337
15.6	338	* (((
	339	AT+DATACUT
	340	)))
2.2	341
15.6	342	(((
2.2	343	When the return value from sensor have fix length and we know which position the valid value we should get, we can use AT+DATACUT command.
15.6	344	)))
2.2	345
15.6	346	* (((
	347	AT+SEARCH
	348	)))
2.2	349
15.6	350	(((
2.2	351	When the return value from sensor is dynamic length and we are not sure which bytes the valid data is, instead, we know what value the valid value following. We can use AT+SEARCH to search the valid value in the return string.
15.6	352	)))
2.2	353
15.6	354	(((
2.2	355	Define wait timeout:
15.6	356	)))
2.2	357
15.6	358	(((
2.2	359	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
15.6	360	)))
2.2	361
15.6	362	(((
2.2	363	After we got the valid value from each RS485 commands, we need to combine them together with the command AT+DATAUP.
15.6	364	)))
2.2	365
	366	Examples:
	367
	368	Below are examples for the how above AT Commands works.
	369
	370	AT+COMMANDx : This command will be sent to RS485/TTL devices during each sampling, Max command length is 14 bytes. The grammar is:
	371
16.1	372	(% border="1" class="table-bordered" %)
2.2	373	\|(((
	374	AT+COMMANDx=xx xx xx xx xx xx xx xx xx xx xx xx,m
	375
	376	xx xx xx xx xx xx xx xx xx xx xx xx: The RS485 command to be sent
	377
	378	m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
	379	)))
	380
29.2	381	(((
2.2	382	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.
29.2	383	)))
2.2	384
29.2	385	(((
2.2	386	In the RS485-BL, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
29.2	387	)))
2.2	388
29.2	389	(((
2.2	390	AT+SEARCHx: This command defines how to handle the return from AT+COMMANDx.
29.2	391	)))
2.2	392
16.1	393	(% border="1" class="table-bordered" %)
2.2	394	\|(((
	395	AT+SEARCHx=aa,xx xx xx xx xx
	396
	397	* aa: 1: prefix match mode; 2: prefix and suffix match mode
	398	* xx xx xx xx xx: match string. Max 5 bytes for prefix and 5 bytes for suffix
	399
	400
	401	)))
	402
29.2	403	Examples:
2.2	404
29.2	405	~1. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
2.2	406
	407	If we set AT+SEARCH1=1,1E 56 34. (max 5 bytes for prefix)
	408
29.2	409	The valid data will be all bytes after 1E 56 34 , so it is (% style="background-color:yellow" %) 2e 30 58 5f 36 41 30 31 00 49
2.2	410
29.2	411	[[image:1653269403619-508.png]]
2.2	412
29.2	413	2. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
2.2	414
	415	If we set AT+SEARCH1=2, 1E 56 34+31 00 49
	416
29.2	417	Device will search the bytes between 1E 56 34 and 31 00 49. So it is (% style="background-color:yellow" %) 2e 30 58 5f 36 41 30
2.2	418
29.2	419	[[image:1653269438444-278.png]]
2.2	420
	421	AT+DATACUTx : This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes.
	422
	423	\|(((
	424	AT+DATACUTx=a,b,c
	425
	426	* a: length for the return of AT+COMMAND
	427	* b:1: grab valid value by byte, max 6 bytes. 2: grab valid value by bytes section, max 3 sections.
6.2	428	* c: define the position for valid value.
2.2	429	)))
	430
	431	Examples:
	432
	433	* Grab bytes:
	434
29.2	435	[[image:1653269551753-223.png\|\|height="311" width="717"]]
2.2	436
	437	* Grab a section.
	438
29.2	439	[[image:1653269568276-930.png\|\|height="325" width="718"]]
2.2	440
	441	* Grab different sections.
	442
29.2	443	[[image:1653269593172-426.png\|\|height="303" width="725"]]
2.2	444
29.2	445	(% style="color:red" %)Note:
2.2	446
	447	AT+SEARCHx and AT+DATACUTx can be used together, if both commands are set, RS485-BL will first process AT+SEARCHx on the return string and get a temporary string, and then process AT+DATACUTx on this temporary string to get the final payload. In this case, AT+DATACUTx need to set to format AT+DATACUTx=0,xx,xx where the return bytes set to 0.
	448
	449	Example:
	450
29.2	451	(% style="color:red" %)AT+COMMAND1=11 01 1E D0,0
2.2	452
29.2	453	(% style="color:red" %)AT+SEARCH1=1,1E 56 34
2.2	454
29.2	455	(% style="color:red" %)AT+DATACUT1=0,2,1~~5
2.2	456
29.2	457	(% style="color:red" %)Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
2.2	458
29.2	459	(% style="color:red" %)String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
2.2	460
29.2	461	(% style="color:red" %)Valid payload after DataCUT command: 2e 30 58 5f 36
2.2	462
29.2	463	[[image:1653269618463-608.png]]
2.2	464
29.2	465	=== 3.3.4 Compose the uplink payload ===
2.2	466
29.2	467	(((
2.2	468	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.
29.2	469	)))
2.2	470
29.2	471	(((
	472	(% style="color:#4f81bd" %)Examples: AT+DATAUP=0
	473	)))
2.2	474
29.2	475	(((
	476	Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)A SIGNLE UPLINK.
	477	)))
2.2	478
29.2	479	(((
2.2	480	Final Payload is
29.2	481	)))
2.2	482
29.2	483	(((
	484	(% style="color:#4f81bd" %)Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx
	485	)))
2.2	486
29.2	487	(((
2.2	488	Where PAYVER is defined by AT+PAYVER, below is an example screen shot.
29.2	489	)))
2.2	490
29.3	491	[[image:1653269759169-150.png\|\|height="513" width="716"]]
2.2	492
30.2	493	(% style="color:#4f81bd" %)Examples: AT+DATAUP=1
2.2	494
30.2	495	Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)Multiply UPLINKs.
2.2	496
	497	Final Payload is
	498
30.2	499	(% style="color:#4f81bd" %)Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA
2.2	500
	501	1. Battery Info (2 bytes): Battery voltage
	502	1. PAYVER (1 byte): Defined by AT+PAYVER
	503	1. PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling.
	504	1. PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
30.2	505	1. DATA: Valid value: max 6 bytes(US915 version here, Notice*!) for each uplink so each uplink <= 11 bytes. For the last uplink, DATA will might less than 6 bytes
2.2	506
31.2	507	[[image:1653269916228-732.png\|\|height="433" width="711"]]
2.2	508
	509
	510	So totally there will be 3 uplinks for this sampling, each uplink includes 6 bytes DATA
	511
31.2	512	DATA1=RETURN1 Valid Value = (% style="background-color:green; color:white" %)20 20 0a 33 90 41
2.2	513
31.2	514	DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10=(% style="background-color:green; color:white" %) 02 aa 05 81 0a 20
2.2	515
31.2	516	DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 = (% style="background-color:green; color:white" %)20 20 20 2d 30
2.2	517
	518	Below are the uplink payloads:
	519
31.2	520	[[image:1653270130359-810.png]]
2.2	521
	522
31.2	523	(% style="color:red" %)Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:
2.2	524
	525	~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink ( so 51 -5 = 46 max valid date)
	526
	527	* For AU915/AS923 bands, if UplinkDwell time=1, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date).
	528
	529	* For US915 band, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date).
	530
	531	~* For all other bands: max 51 bytes for each uplink ( so 51 -5 = 46 max valid date).
	532
31.3	533	=== 3.3.5 Uplink on demand ===
2.2	534
	535	Except uplink periodically, RS485-BL is able to uplink on demand. The server sends downlink command to RS485-BL and RS485 will uplink data base on the command.
	536
	537	Downlink control command:
	538
	539	[[0x08 command>>path:#downlink_08]]: Poll an uplink with current command set in RS485-BL.
	540
	541	[[0xA8 command>>path:#downlink_A8]]: Send a command to RS485-BL and uplink the output from sensors.
	542
	543
	544
32.3	545	1.
	546	11.
2.2	547	111. Uplink on Interrupt
	548
	549	Put the interrupt sensor between 3.3v_out and GPIO ext.[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image022.png]]
	550
	551	AT+INTMOD=0 Disable Interrupt
	552
	553	AT+INTMOD=1 Interrupt trigger by rising or falling edge.
	554
	555	AT+INTMOD=2 Interrupt trigger by falling edge. ( Default Value)
	556
	557	AT+INTMOD=3 Interrupt trigger by rising edge.
	558
	559
32.3	560	1.
2.2	561	11. Uplink Payload
	562
	563	\|Size(bytes)\|2\|1\|Length depends on the return from the commands
	564	\|Value\|(((
	565	Battery(mV)
	566
	567	&
	568
	569	Interrupt _Flag
	570	)))\|(((
	571	PAYLOAD_VER
	572
	573
	574	)))\|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.
	575
	576	Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors.
	577
	578
	579	function Decoder(bytes, port) {
	580
	581	~/~/Payload Formats of RS485-BL Deceive
	582
	583	return {
	584
	585	~/~/Battery,units:V
	586
	587	BatV:((bytes[0]<<8 \| bytes[1])&0x7fff)/1000,
	588
	589	~/~/GPIO_EXTI
	590
	591	EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE",
	592
	593	~/~/payload of version
	594
	595	Pay_ver:bytes[2],
	596
	597	};
	598
	599	}
	600
	601
	602
	603
	604
	605
	606
	607	TTN V3 uplink screen shot.
	608
	609	[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]
	610
6.2	611	1.
2.2	612	11. Configure RS485-BL via AT or Downlink
	613
	614	User can configure RS485-BL via [[AT Commands >>path:#_Using_the_AT]]or LoRaWAN Downlink Commands
	615
	616	There are two kinds of Commands:
	617
	618	* 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: http:~/~/wiki.dragino.com/index.php?title=End_Device_AT_Commands_and_Downlink_Commands
	619
	620	* Sensor Related Commands: These commands are special designed for RS485-BL. User can see these commands below:
	621
32.3	622	1.
	623	11.
2.2	624	111. Common Commands:
	625
	626	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: [[http:~~/~~/wiki.dragino.com/index.php?title=End_Device_AT_Commands_and_Downlink_Commands>>url:http://wiki.dragino.com/index.php?title=End_Device_AT_Commands_and_Downlink_Commands]]
	627
	628
32.3	629	1.
	630	11.
2.2	631	111. Sensor related commands:
	632
	633	==== Choose Device Type (RS485 or TTL) ====
	634
	635	RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect.
	636
	637	* AT Command
	638
	639	AT+MOD=1 ~/~/ Set to support RS485-MODBUS type sensors. User can connect multiply RS485 , Modbus sensors to the A / B pins.
	640
	641	AT+MOD=2 ~/~/ Set to support TTL Level sensors, User can connect one TTL Sensor to the TXD/RXD/GND pins.
	642
	643
	644	* Downlink Payload
	645
	646	0A aa à same as AT+MOD=aa
	647
	648
	649
	650	==== [[RS485 Debug Command>>path:#downlink_A8]] (AT+CFGDEV) ====
	651
	652	This command is used to configure the RS485 or TTL sensors; they won’t be used during sampling.
	653
	654	* AT Command
	655
	656	AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
	657
	658	m: 0: no CRC; 1: add CRC-16/MODBUS in the end of this command.
	659
	660
	661
	662	* Downlink Payload
	663
	664	Format: A8 MM NN XX XX XX XX YY
	665
	666	Where:
	667
	668	* MM: 1: add CRC-16/MODBUS ; 0: no CRC
	669	* NN: The length of RS485 command
	670	* XX XX XX XX: RS485 command total NN bytes
	671	* YY: How many bytes will be uplink from the return of this RS485 command, if YY=0, RS485-BL will execute the downlink command without uplink; if YY>0, RS485-BL will uplink total YY bytes from the output of this RS485 command
	672
	673	Example 1:
	674
	675	To connect a Modbus Alarm with below commands.
	676
	677	* 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.
	678
	679	* 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.
	680
	681	So if user want to use downlink command to control to RS485 Alarm, he can use:
	682
	683	A8 01 06 0A 05 00 04 00 01 00: to activate the RS485 Alarm
	684
	685	A8 01 06 0A 05 00 04 00 00 00: to deactivate the RS485 Alarm
	686
	687	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.
	688
	689
	690	Example 2:
	691
	692	Check TTL Sensor return:
	693
	694	[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image024.png]]
	695
	696
	697
	698
	699	==== Set Payload version ====
	700
	701	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.
	702
	703	* AT Command:
	704
	705	AT+PAYVER: Set PAYVER field = 1
	706
	707
	708	* Downlink Payload:
	709
	710	0xAE 01 à Set PAYVER field = 0x01
	711
	712	0xAE 0F à Set PAYVER field = 0x0F
	713
	714
	715	==== Set RS485 Sampling Commands ====
	716
	717	AT+COMMANDx, AT+DATACUTx and AT+SEARCHx
	718
	719	These three commands are used to configure how the RS485-BL polling data from Modbus device. Detail of usage please see : [[polling RS485 device>>path:#polling_485]].
	720
	721
	722	* AT Command:
	723
	724	AT+COMMANDx: Configure RS485 read command to sensor.
	725
	726	AT+DATACUTx: Configure how to handle return from RS485 devices.
	727
	728	AT+SEARCHx: Configure search command
	729
	730
	731	* Downlink Payload:
	732
	733	0xAF downlink command can be used to set AT+COMMANDx or AT+DATACUTx.
	734
	735	Note: if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink.
	736
	737	Format: AF MM NN LL XX XX XX XX YY
	738
	739	Where:
	740
	741	* MM: the ATCOMMAND or AT+DATACUT to be set. Value from 01 ~~ 0F,
	742	* NN: 0: no CRC; 1: add CRC-16/MODBUS ; 2: set the AT+DATACUT value.
	743	* LL: The length of AT+COMMAND or AT+DATACUT command
	744	* XX XX XX XX: AT+COMMAND or AT+DATACUT command
	745	* YY: If YY=0, RS485-BL will execute the downlink command without uplink; if YY=1, RS485-BL will execute an uplink after got this command.
	746
	747	Example:
	748
	749	AF 03 01 06 0A 05 00 04 00 01 00: Same as AT+COMMAND3=0A 05 00 04 00 01,1
	750
	751	AF 03 02 06 10 01 05 06 09 0A 00: Same as AT+DATACUT3=16,1,5+6+9+10
	752
	753	AF 03 02 06 0B 02 05 07 08 0A 00: Same as AT+DATACUT3=11,2,5~~7+8~~10
	754
	755
	756	0xAB downlink command can be used for set AT+SEARCHx
	757
	758	Example: AB aa 01 03 xx xx xx (03 here means there are total 3 bytes after 03) So
	759
	760	* AB aa 01 03 xx xx xx same as AT+SEARCHaa=1,xx xx xx
	761	* AB aa 02 03 xx xx xx 02 yy yy(03 means there are 3 bytes after 03, they are xx xx xx;02 means there are 2 bytes after 02, they are yy yy) so the commands
	762
	763	AB aa 02 03 xx xx xx 02 yy yy same as AT+SEARCHaa=2,xx xx xx+yy yy
	764
	765
	766	==== Fast command to handle MODBUS device ====
	767
	768	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]].
	769
	770	This command is valid since v1.3 firmware version
	771
	772
	773	AT+MBFUN has only two value:
	774
	775	* AT+MBFUN=1: Enable Modbus reading. And get response base on the MODBUS return
	776
	777	AT+MBFUN=1, device 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.
	778
	779	* AT+MBFUN=0: Disable Modbus fast reading.
	780
	781	Example:
	782
	783	* AT+MBFUN=1 and AT+DATACUT1/AT+DATACUT2 are not configure (0,0,0).
	784	* 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.
	785	* 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.
	786
	787	[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image025.png]]
	788
	789
	790	[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image026.png]]
	791
	792
	793	* Downlink Commands:
	794
	795	A9 aa -à Same as AT+MBFUN=aa
	796
	797
	798	==== RS485 command timeout ====
	799
	800	Some Modbus device has slow action to send replies. This command is used to configure the RS485-BL to use longer time to wait for their action.
	801
	802	Default value: 0, range: 0 ~~ 5 seconds
	803
	804
	805	* AT Command:
	806
	807	AT+CMDDLaa=hex(bb cc)
	808
	809	Example:
	810
	811	AT+CMDDL1=1000 to send the open time to 1000ms
	812
	813
	814	* Downlink Payload:
	815
	816	0x AA aa bb cc
	817
	818	Same as: AT+CMDDLaa=hex(bb cc)
	819
	820	Example:
	821
	822	0xAA 01 03 E8 à Same as AT+CMDDL1=1000 ms
	823
	824
	825	==== [[Uplink>>path:#downlink_A8]] payload mode ====
	826
	827	Define to use one uplink or multiple uplinks for the sampling.
	828
	829	The use of this command please see: [[Compose Uplink payload>>path:#DataUP]]
	830
	831	* AT Command:
	832
	833	AT+DATAUP=0
	834
	835	AT+DATAUP=1
	836
	837
	838	* Downlink Payload:
	839
	840	0xAD 00 à Same as AT+DATAUP=0
	841
	842	0xAD 01 à Same as AT+DATAUP=1
	843
	844
	845	==== Manually trigger an Uplink ====
	846
	847	Ask device to send an uplink immediately.
	848
	849	* Downlink Payload:
	850
	851	0x08 FF, RS485-BL will immediately send an uplink.
	852
	853
	854	==== Clear RS485 Command ====
	855
	856	The AT+COMMANDx and AT+DATACUTx settings are stored in special location, user can use below command to clear them.
	857
	858
	859	* AT Command:
	860
	861	AT+CMDEAR=mm,nn mm: start position of erase ,nn: stop position of erase
	862
	863	Etc. AT+CMDEAR=1,10 means erase AT+COMMAND1/AT+DATACUT1 to AT+COMMAND10/AT+DATACUT10
	864
6.2	865	Example screen shot after clear all RS485 commands.
2.2	866
	867
	868
	869	The uplink screen shot is:
	870
	871	[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]
	872
	873
	874	* Downlink Payload:
	875
	876	0x09 aa bb same as AT+CMDEAR=aa,bb
	877
	878
	879	==== Set Serial Communication Parameters ====
	880
	881	Set the Rs485 serial communication parameters:
	882
	883	* AT Command:
	884
	885	Set Baud Rate:
	886
	887	AT+BAUDR=9600 ~/~/ Options: (1200,2400,4800,14400,19200,115200)
	888
	889
	890	Set UART parity
	891
	892	AT+PARITY=0 ~/~/ Option: 0: no parity, 1: odd parity, 2: even parity
	893
	894
	895	Set STOPBIT
	896
	897	AT+STOPBIT=0 ~/~/ Option: 0 for 1bit; 1 for 1.5 bit ; 2 for 2 bits
	898
	899
	900	* Downlink Payload:
	901
	902	A7 01 aa bb: Same AT+BAUDR=hex(aa bb)*100
	903
	904	Example:
	905
	906	* A7 01 00 60 same as AT+BAUDR=9600
	907	* A7 01 04 80 same as AT+BAUDR=115200
	908
	909	A7 02 aa: Same as AT+PARITY=aa (aa value: 00 , 01 or 02)
	910
	911	A7 03 aa: Same as AT+STOPBIT=aa (aa value: 00 , 01 or 02)
	912
	913
	914	==== Control output power duration ====
	915
	916	User can set the output power duration before each sampling.
	917
	918	* AT Command:
	919
	920	Example:
	921
	922	AT+3V3T=1000 ~/~/ 3V3 output power will open 1s before each sampling.
	923
	924	AT+5VT=1000 ~/~/ +5V output power will open 1s before each sampling.
	925
	926
	927	* LoRaWAN Downlink Command:
	928
	929	07 01 aa bb Same as AT+5VT=(aa bb)
	930
	931	07 02 aa bb Same as AT+3V3T=(aa bb)
	932
	933
	934
	935
32.3	936	1.
2.2	937	11. Buttons
	938
	939	\|Button\|Feature
	940	\|RST\|Reboot RS485-BL
	941
32.3	942	1.
2.2	943	11. +3V3 Output
	944
	945	RS485-BL has a Controllable +3V3 output, user can use this output to power external sensor.
	946
6.2	947	The +3V3 output will be valid for every sampling. RS485-BL will enable +3V3 output before all sampling and disable the +3V3 after all sampling.
2.2	948
	949
	950	The +3V3 output time can be controlled by AT Command.
	951
	952	AT+3V3T=1000
	953
	954	Means set +3v3 valid time to have 1000ms. So, the real +3v3 output will actually have 1000ms + sampling time for other sensors.
	955
	956
	957	By default, the AT+3V3T=0. This is a special case, means the +3V3 output is always on at any time
	958
	959
32.3	960	1.
2.2	961	11. +5V Output
	962
	963	RS485-BL has a Controllable +5V output, user can use this output to power external sensor.
	964
6.2	965	The +5V output will be valid for every sampling. RS485-BL will enable +5V output before all sampling and disable the +5v after all sampling.
2.2	966
	967
	968	The 5V output time can be controlled by AT Command.
	969
	970	AT+5VT=1000
	971
	972	Means set 5V valid time to have 1000ms. So, the real 5V output will actually have 1000ms + sampling time for other sensors.
	973
	974
	975	By default, the AT+5VT=0. If the external sensor which require 5v and require more time to get stable state, user can use this command to increase the power ON duration for this sensor.
	976
	977
	978
	979
32.3	980	1.
2.2	981	11. LEDs
	982
	983	\|LEDs\|Feature
	984	\|LED1\|Blink when device transmit a packet.
	985
32.3	986	1.
2.2	987	11. Switch Jumper
	988
	989	\|Switch Jumper\|Feature
	990	\|SW1\|(((
	991	ISP position: Upgrade firmware via UART
	992
	993	Flash position: Configure device, check running status.
	994	)))
	995	\|SW2\|(((
	996	5V position: set to compatible with 5v I/O.
	997
	998	3.3v position: set to compatible with 3.3v I/O.,
	999	)))
	1000
	1001	+3.3V: is always ON
	1002
	1003	+5V: Only open before every sampling. The time is by default, it is AT+5VT=0. Max open time. 5000 ms.
	1004
	1005	1. Case Study
	1006
	1007	User can check this URL for some case studies.
	1008
	1009	[[http:~~/~~/wiki.dragino.com/index.php?title=APP_RS485_COMMUNICATE_WITH_SENSORS>>url:http://wiki.dragino.com/index.php?title=APP_RS485_COMMUNICATE_WITH_SENSORS]]
	1010
	1011
	1012
	1013
	1014	1. Use AT Command
	1015	11. Access AT Command
	1016
	1017	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.
	1018
	1019	[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image027.png]]
	1020
	1021
	1022	In PC, User needs to set serial tool(such as [[putty>>url:https://www.chiark.greenend.org.uk/~~sgtatham/putty/latest.html]], SecureCRT) baud rate to 9600 to access to access serial console of RS485-BL. The default password is 123456. Below is the output for reference:
	1023
	1024	[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image028.png]]
	1025
	1026
	1027
	1028	More detail AT Command manual can be found at [[AT Command Manual>>path:#AT_COMMAND]]
	1029
	1030
	1031
32.3	1032	1.
2.2	1033	11. Common AT Command Sequence
	1034	111. Multi-channel ABP mode (Use with SX1301/LG308)
	1035
	1036	If device has not joined network yet:
	1037
	1038	AT+FDR
	1039
	1040	AT+NJM=0
	1041
	1042	ATZ
	1043
	1044
	1045	If device already joined network:
	1046
	1047	AT+NJM=0
	1048
	1049	ATZ
	1050
32.3	1051	1.
	1052	11.
2.2	1053	111. Single-channel ABP mode (Use with LG01/LG02)
	1054
	1055	AT+FDR Reset Parameters to Factory Default, Keys Reserve
	1056
	1057	AT+NJM=0 Set to ABP mode
	1058
	1059	AT+ADR=0 Set the Adaptive Data Rate Off
	1060
	1061	AT+DR=5 Set Data Rate
	1062
	1063	AT+TDC=60000 Set transmit interval to 60 seconds
	1064
	1065	AT+CHS=868400000 Set transmit frequency to 868.4Mhz
	1066
	1067	AT+RX2FQ=868400000 Set RX2Frequency to 868.4Mhz (according to the result from server)
	1068
	1069	AT+RX2DR=5 Set RX2DR to match the downlink DR from server. see below
	1070
	1071	AT+DADDR=26 01 1A F1 Set Device Address to 26 01 1A F1, this ID can be found in the LoRa Server portal.
	1072
	1073	ATZ Reset MCU
	1074
	1075	Note:
	1076
	1077	1. Make sure the device is set to ABP mode in the IoT Server.
	1078	1. Make sure the LG01/02 gateway RX frequency is exactly the same as AT+CHS setting.
	1079	1. 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.
	1080	1. 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
	1081
	1082	[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image029.png]]
	1083
	1084
	1085	1. FAQ
	1086	11. How to upgrade the image?
	1087
	1088	The RS485-BL LoRaWAN Controller is shipped with a 3.5mm cable, the cable is used to upload image to RS485-BL to:
	1089
	1090	* Support new features
	1091	* For bug fix
	1092	* Change LoRaWAN bands.
	1093
	1094	Below shows the hardware connection for how to upload an image to RS485-BL:
	1095
	1096	[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image030.png]]
	1097
	1098	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]].
	1099
	1100	Step2: Download the [[LT Image files>>url:http://www.dragino.com/downloads/index.php?dir=LT_LoRa_IO_Controller/LT33222-L/image/]].
	1101
	1102	Step3: Open flashloader; choose the correct COM port to update.
	1103
	1104
	1105	\|(((
	1106	HOLD PRO then press the RST button, SYS will be ON, then click next
	1107	)))
	1108
	1109	\|(((
	1110	Board detected
	1111	)))
	1112
	1113	\|(((
	1114
	1115	)))
	1116
	1117	[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image031.png]] [[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image032.png]]
	1118
	1119
	1120
	1121	[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image033.png]] [[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image034.png]]
	1122
	1123
	1124	[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image035.png]] [[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image036.png]]
	1125
	1126
32.3	1127	1.
2.2	1128	11. How to change the LoRa Frequency Bands/Region?
	1129
	1130	User can follow the introduction for [[how to upgrade image>>path:#upgrade_image]]. When download the images, choose the required image file for download.
	1131
	1132
	1133
32.3	1134	1.
2.2	1135	11. How many RS485-Slave can RS485-BL connects?
	1136
	1137	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>>path:#downlink_A8]].
	1138
	1139
	1140
	1141
	1142	1. Trouble Shooting
	1143	11. Downlink doesn’t work, how to solve it?
	1144
	1145	Please see this link for debug:
	1146
6.2	1147	[[http:~~/~~/wiki.dragino.com/index.php?title=Main_Page#LoRaWAN_Communication_Debug>>url:http://wiki.dragino.com/index.php?title=Main_Page#LoRaWAN_Communication_Debug]]
2.2	1148
	1149
	1150
32.3	1151	1.
2.2	1152	11. Why I can’t join TTN V3 in US915 /AU915 bands?
	1153
	1154	It might about the channels mapping. Please see for detail.
	1155
	1156	[[http:~~/~~/wiki.dragino.com/index.php?title=LoRaWAN_Communication_Debug#Notice_of_US915.2FCN470.2FAU915_Frequency_band>>url:http://wiki.dragino.com/index.php?title=LoRaWAN_Communication_Debug#Notice_of_US915.2FCN470.2FAU915_Frequency_band]]
	1157
	1158
	1159
	1160	1. Order Info
	1161
	1162	Part Number: RS485-BL-XXX
	1163
	1164	XXX:
	1165
	1166	* EU433: frequency bands EU433
	1167	* EU868: frequency bands EU868
	1168	* KR920: frequency bands KR920
	1169	* CN470: frequency bands CN470
	1170	* AS923: frequency bands AS923
	1171	* AU915: frequency bands AU915
	1172	* US915: frequency bands US915
	1173	* IN865: frequency bands IN865
	1174	* RU864: frequency bands RU864
	1175	* KZ865: frequency bands KZ865
	1176
	1177	1. Packing Info
	1178
	1179	Package Includes:
	1180
	1181	* RS485-BL x 1
	1182	* Stick Antenna for LoRa RF part x 1
	1183	* Program cable x 1
	1184
	1185	Dimension and weight:
	1186
	1187	* Device Size: 13.5 x 7 x 3 cm
	1188	* Device Weight: 105g
	1189	* Package Size / pcs : 14.5 x 8 x 5 cm
	1190	* Weight / pcs : 170g
	1191
	1192	1. Support
	1193
	1194	* 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.
	1195	* 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
	1196
	1197	[[support@dragino.com>>url:file:///D:/市场资料/说明书/LoRa/LT系列/support@dragino.com]]

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

Applications