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

Version 35.4 by Xiaoling on 2022/06/02 15:46

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

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

Applications