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

Version 38.1 by Xiaoling on 2022/06/02 16:09

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

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

Applications