Wiki source code of RS485-BL – Waterproof RS485 to LoRaWAN Converter

Version 41.8 by Xiaoling on 2022/06/06 10:56

version	line-number	content
3.2	1	(% style="text-align:center" %)
	2	[[image:1652947681187-144.png\|\|height="385" width="385"]]
1.1	3
	4
	5
	6
2.2	7	RS485-BL – Waterproof RS485 to LoRaWAN Converter User Manual
1.1	8
	9
29.4	10
3.2	11	Table of Contents:
1.1	12
29.5	13	{{toc/}}
1.1	14
	15
	16
	17
29.4	18
3.2	19	= 1.Introduction =
1.1	20
3.2	21	== 1.1 What is RS485-BL RS485 to LoRaWAN Converter ==
1.1	22
3.2	23	(((
	24
	25	)))
1.1	26
3.2	27	(((
29.15	28	The Dragino RS485-BL is a (% style="color:blue" %)RS485 / UART to LoRaWAN Converter(%%) for Internet of Things solutions. User can connect RS485 or UART sensor to RS485-BL converter, and configure RS485-BL to periodically read sensor data and upload via LoRaWAN network to IoT server.
3.2	29	)))
2.2	30
3.2	31	(((
29.15	32	RS485-BL can interface to RS485 sensor, 3.3v/5v UART sensor or interrupt sensor. RS485-BL provides (% style="color:blue" %)a 3.3v output(%%) and (% style="color:blue" %)a 5v output(%%) to power external sensors. Both output voltages are controllable to minimize the total system power consumption.
3.2	33	)))
2.2	34
3.2	35	(((
29.15	36	RS485-BL is IP67 (% style="color:blue" %)waterproof(%%) and powered by (% style="color:blue" %)8500mAh Li-SOCI2 battery(%%), it is designed for long term use for several years.
3.2	37	)))
2.2	38
3.2	39	(((
29.15	40	RS485-BL runs standard (% style="color:blue" %)LoRaWAN 1.0.3 in Class A(%%). It can reach long transfer range and easy to integrate with LoRaWAN compatible gateway and IoT server.
3.2	41	)))
2.2	42
3.2	43	(((
2.2	44	For data uplink, RS485-BL sends user-defined commands to RS485 devices and gets the return from the RS485 devices. RS485-BL will process these returns data according to user-define rules to get the final payload and upload to LoRaWAN server.
3.2	45	)))
2.2	46
3.2	47	(((
2.2	48	For data downlink, RS485-BL runs in LoRaWAN Class A. When there is downlink commands from LoRaWAN server, RS485-BL will forward the commands from LoRaWAN server to RS485 devices.
3.2	49	)))
2.2	50
3.2	51	(((
2.2	52	Each RS485-BL pre-load with a set of unique keys for LoRaWAN registration, register these keys to LoRaWAN server and it will auto connect after power on.
3.2	53	)))
2.2	54
6.2	55	[[image:1652953304999-717.png\|\|height="424" width="733"]]
2.2	56
29.14	57
	58
3.2	59	== 1.2 Specifications ==
2.2	60
29.17	61
2.2	62	Hardware System:
	63
	64	* STM32L072CZT6 MCU
6.2	65	* SX1276/78 Wireless Chip
2.2	66	* Power Consumption (exclude RS485 device):
	67	** Idle: 6uA@3.3v
	68	** 20dB Transmit: 130mA@3.3v
	69
	70	Interface for Model:
	71
	72	* 1 x RS485 Interface
	73	* 1 x TTL Serial , 3.3v or 5v.
	74	* 1 x I2C Interface, 3.3v or 5v.
	75	* 1 x one wire interface
	76	* 1 x Interrupt Interface
	77	* 1 x Controllable 5V output, max
	78
	79	LoRa Spec:
	80
	81	* Frequency Range:
	82	** Band 1 (HF): 862 ~~ 1020 Mhz
	83	** Band 2 (LF): 410 ~~ 528 Mhz
	84	* 168 dB maximum link budget.
	85	* +20 dBm - 100 mW constant RF output vs.
	86	* Programmable bit rate up to 300 kbps.
	87	* High sensitivity: down to -148 dBm.
	88	* Bullet-proof front end: IIP3 = -12.5 dBm.
	89	* Excellent blocking immunity.
	90	* Fully integrated synthesizer with a resolution of 61 Hz.
	91	* LoRa modulation.
	92	* Built-in bit synchronizer for clock recovery.
	93	* Preamble detection.
	94	* 127 dB Dynamic Range RSSI.
3.3	95	* Automatic RF Sense and CAD with ultra-fast AFC.
2.2	96
3.3	97	== 1.3 Features ==
2.2	98
	99	* LoRaWAN Class A & Class C protocol (default Class A)
	100	* Frequency Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/IN865/RU864
	101	* AT Commands to change parameters
	102	* Remote configure parameters via LoRaWAN Downlink
	103	* Firmware upgradable via program port
	104	* Support multiply RS485 devices by flexible rules
	105	* Support Modbus protocol
	106	* Support Interrupt uplink
	107
3.3	108	== 1.4 Applications ==
2.2	109
	110	* Smart Buildings & Home Automation
	111	* Logistics and Supply Chain Management
	112	* Smart Metering
	113	* Smart Agriculture
	114	* Smart Cities
	115	* Smart Factory
	116
6.2	117	== 1.5 Firmware Change log ==
2.2	118
4.2	119	[[RS485-BL Image files – Download link and Change log>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/RS485-BL/Firmware/\|\|style="background-color: rgb(255, 255, 255);"]]
2.2	120
29.10	121
4.2	122	== 1.6 Hardware Change log ==
2.2	123
4.2	124	(((
29.18	125
	126
40.34	127	(((
2.2	128	v1.4
4.2	129	)))
40.34	130	)))
2.2	131
4.2	132	(((
40.34	133	(((
2.2	134	~1. Change Power IC to TPS22916
4.2	135	)))
40.34	136	)))
2.2	137
40.34	138	(((
	139
	140	)))
2.2	141
4.2	142	(((
40.34	143	(((
2.2	144	v1.3
4.2	145	)))
40.34	146	)))
2.2	147
4.2	148	(((
40.34	149	(((
2.2	150	~1. Change JP3 from KF350-8P to KF350-11P, Add one extra interface for I2C and one extra interface for one-wire
4.2	151	)))
40.34	152	)))
2.2	153
40.34	154	(((
	155
	156	)))
2.2	157
4.2	158	(((
40.34	159	(((
2.2	160	v1.2
4.2	161	)))
40.34	162	)))
2.2	163
4.2	164	(((
40.34	165	(((
4.2	166	Release version
40.34	167	)))
29.9	168
	169
4.2	170	)))
2.2	171
4.2	172	= 2. Pin mapping and Power ON Device =
2.2	173
6.2	174	(((
2.2	175	The RS485-BL is powered on by 8500mAh battery. To save battery life, RS485-BL is shipped with power off. User can put the jumper to power on RS485-BL.
6.2	176	)))
2.2	177
4.2	178	[[image:1652953055962-143.png\|\|height="387" width="728"]]
2.2	179
	180
	181	The Left TXD and RXD are TTL interface for external sensor. TTL level is controlled by 3.3/5v Jumper.
	182
29.8	183
6.2	184	= 3. Operation Mode =
2.2	185
6.2	186	== 3.1 How it works? ==
2.2	187
7.2	188	(((
2.2	189	The RS485-BL is configured as LoRaWAN OTAA Class A 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-BL. It will auto join the network via OTAA.
29.7	190
	191
7.2	192	)))
2.2	193
7.2	194	== 3.2 Example to join LoRaWAN network ==
2.2	195
6.2	196	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	197
7.2	198	[[image:1652953414711-647.png\|\|height="337" width="723"]]
2.2	199
15.3	200	(((
2.2	201	The RS485-BL in this example connected to two RS485 devices for demonstration, user can connect to other RS485 devices via the same method.
15.3	202	)))
2.2	203
15.3	204	(((
2.2	205	The LG308 is already set to connect to [[TTN V3 network >>url:https://www.thethingsnetwork.org/]]. So what we need to now is only configure the TTN V3:
15.3	206	)))
2.2	207
15.3	208	(((
2.2	209	Step 1: Create a device in TTN V3 with the OTAA keys from RS485-BL.
15.3	210	)))
2.2	211
15.3	212	(((
2.2	213	Each RS485-BL is shipped with a sticker with unique device EUI:
15.3	214	)))
2.2	215
15.2	216	[[image:1652953462722-299.png]]
2.2	217
15.3	218	(((
2.2	219	User can enter this key in their LoRaWAN Server portal. Below is TTN V3 screen shot:
15.3	220	)))
2.2	221
15.3	222	(((
2.2	223	Add APP EUI in the application.
15.3	224	)))
2.2	225
	226
15.2	227	[[image:image-20220519174512-1.png]]
2.2	228
15.2	229	[[image:image-20220519174512-2.png\|\|height="328" width="731"]]
2.2	230
15.2	231	[[image:image-20220519174512-3.png\|\|height="556" width="724"]]
2.2	232
15.2	233	[[image:image-20220519174512-4.png]]
2.2	234
	235	You can also choose to create the device manually.
	236
15.2	237	[[image:1652953542269-423.png\|\|height="710" width="723"]]
2.2	238
	239	Add APP KEY and DEV EUI
	240
15.2	241	[[image:1652953553383-907.png\|\|height="514" width="724"]]
2.2	242
	243
15.2	244	(((
2.2	245	Step 2: Power on RS485-BL 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	246	)))
2.2	247
15.2	248	[[image:1652953568895-172.png\|\|height="232" width="724"]]
2.2	249
29.21	250
15.5	251	== 3.3 Configure Commands to read data ==
2.2	252
15.5	253	(((
29.6	254	There are plenty of RS485 and TTL level devices in the market and each device has different command to read the valid data. To support these devices in flexible, RS485-BL supports flexible command set. User can use [[AT Commands or LoRaWAN Downlink>>\|\|anchor="H3.5ConfigureRS485-BLviaATorDownlink"]] Command to configure how RS485-BL should read the sensor and how to handle the return from RS485 or TTL sensors.
	255
	256
15.5	257	)))
2.2	258
15.5	259	=== 3.3.1 onfigure UART settings for RS485 or TTL communication ===
2.2	260
40.35	261	(((
2.2	262	RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect.
40.35	263	)))
2.2	264
40.35	265	(((
15.5	266	~1. RS485-MODBUS mode:
40.35	267	)))
2.2	268
40.35	269	(((
2.2	270	AT+MOD=1 ~/~/ Support RS485-MODBUS type sensors. User can connect multiply RS485 , Modbus sensors to the A / B pins.
40.35	271	)))
2.2	272
40.35	273	(((
15.5	274	2. TTL mode:
40.35	275	)))
2.2	276
40.35	277	(((
2.2	278	AT+MOD=2 ~/~/ Support TTL Level sensors, User can connect one TTL Sensor to the TXD/RXD/GND pins.
40.35	279	)))
2.2	280
40.35	281	(((
2.2	282	RS485-BL default UART settings is 9600, no parity, stop bit 1. If the sensor has a different settings, user can change the RS485-BL setting to match.
40.35	283	)))
2.2	284
40.45	285	(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
40.46	286	\|=(% style="width: 120px;" %)(((
40.35	287	(((
15.5	288	AT Commands
40.35	289	)))
40.45	290	)))\|=(% style="width: 190px;" %)(((
40.35	291	(((
15.5	292	Description
40.35	293	)))
40.45	294	)))\|=(% style="width: 190px;" %)(((
40.35	295	(((
15.5	296	Example
	297	)))
40.35	298	)))
40.46	299	\|(% style="width:120px" %)(((
40.35	300	(((
15.5	301	AT+BAUDR
40.35	302	)))
40.45	303	)))\|(% style="width:190px" %)(((
40.35	304	(((
15.5	305	Set the baud rate (for RS485 connection). Default Value is: 9600.
40.35	306	)))
40.45	307	)))\|(% style="width:190px" %)(((
15.5	308	(((
40.35	309	(((
2.2	310	AT+BAUDR=9600
15.5	311	)))
40.35	312	)))
2.2	313
15.5	314	(((
40.35	315	(((
2.2	316	Options: (1200,2400,4800,14400,19200,115200)
	317	)))
15.5	318	)))
40.35	319	)))
40.46	320	\|(% style="width:120px" %)(((
40.35	321	(((
15.5	322	AT+PARITY
40.35	323	)))
40.45	324	)))\|(% style="width:190px" %)(((
15.5	325	(((
40.35	326	(((
2.2	327	Set UART parity (for RS485 connection)
15.5	328	)))
40.35	329	)))
2.2	330
15.5	331	(((
40.35	332	(((
2.2	333	Default Value is: no parity.
15.5	334	)))
40.35	335	)))
40.45	336	)))\|(% style="width:190px" %)(((
15.5	337	(((
40.35	338	(((
2.2	339	AT+PARITY=0
15.5	340	)))
40.35	341	)))
2.2	342
15.5	343	(((
40.35	344	(((
2.2	345	Option: 0: no parity, 1: odd parity, 2: even parity
	346	)))
15.5	347	)))
40.35	348	)))
40.46	349	\|(% style="width:120px" %)(((
40.35	350	(((
15.5	351	AT+STOPBIT
40.35	352	)))
40.45	353	)))\|(% style="width:190px" %)(((
15.5	354	(((
40.35	355	(((
2.2	356	Set serial stopbit (for RS485 connection)
15.5	357	)))
40.35	358	)))
2.2	359
15.5	360	(((
40.35	361	(((
2.2	362	Default Value is: 1bit.
15.5	363	)))
40.35	364	)))
40.45	365	)))\|(% style="width:190px" %)(((
15.5	366	(((
40.35	367	(((
2.2	368	AT+STOPBIT=0 for 1bit
15.5	369	)))
40.35	370	)))
2.2	371
15.5	372	(((
40.35	373	(((
2.2	374	AT+STOPBIT=1 for 1.5 bit
15.5	375	)))
40.35	376	)))
2.2	377
15.5	378	(((
40.35	379	(((
2.2	380	AT+STOPBIT=2 for 2 bits
	381	)))
15.5	382	)))
40.35	383	)))
2.2	384
40.53	385
	386
15.6	387	=== 3.3.2 Configure sensors ===
2.2	388
15.6	389	(((
	390	Some sensors might need to configure before normal operation. User can configure such sensor via PC or through RS485-BL AT Commands (% style="color:#4f81bd" %)AT+CFGDEV.
	391	)))
2.2	392
15.6	393	(((
	394	When user issue an (% style="color:#4f81bd" %)AT+CFGDEV(%%) command, Each (% style="color:#4f81bd" %)AT+CFGDEV(%%) equals to send a command to the RS485 or TTL sensors. This command will only run when user input it and won’t run during each sampling.
	395	)))
2.2	396
40.48	397	(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
40.50	398	\|=(% style="width: 120px;" %)AT Commands\|=(% style="width: 190px;" %)Description\|=(% style="width: 190px;" %)Example
	399	\|AT+CFGDEV\|(% style="width:120px" %)(((
2.2	400	This command is used to configure the RS485/TTL devices; they won’t be used during sampling.
	401
15.6	402	AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,
2.2	403
15.6	404	mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
40.48	405	)))\|(% style="width:190px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
2.2	406
29.24	407	Detail of AT+CFGDEV command see [[AT+CFGDEV detail>>\|\|anchor="HRS485DebugCommand28AT2BCFGDEV29"]].
2.2	408
29.22	409
40.52	410
15.6	411	=== 3.3.3 Configure read commands for each sampling ===
2.2	412
15.6	413	(((
2.2	414	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	415	)))
2.2	416
15.6	417	(((
2.2	418	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	419	)))
2.2	420
15.6	421	(((
2.2	422	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	423	)))
2.2	424
15.6	425	(((
2.2	426	This section describes how to achieve above goals.
15.6	427	)))
2.2	428
15.6	429	(((
2.2	430	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	431	)))
2.2	432
15.6	433	(((
2.2	434	Command from RS485-BL to Sensor:
15.6	435	)))
2.2	436
15.6	437	(((
2.2	438	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	439	)))
2.2	440
15.6	441	(((
2.2	442	Handle return from sensors to RS485-BL:
15.6	443	)))
2.2	444
15.6	445	(((
2.2	446	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	447	)))
2.2	448
15.6	449	* (((
	450	AT+DATACUT
	451	)))
2.2	452
15.6	453	(((
2.2	454	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	455	)))
2.2	456
15.6	457	* (((
	458	AT+SEARCH
	459	)))
2.2	460
15.6	461	(((
2.2	462	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	463	)))
2.2	464
15.6	465	(((
2.2	466	Define wait timeout:
15.6	467	)))
2.2	468
15.6	469	(((
2.2	470	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	471	)))
2.2	472
15.6	473	(((
2.2	474	After we got the valid value from each RS485 commands, we need to combine them together with the command AT+DATAUP.
15.6	475	)))
2.2	476
40.54	477	(((
2.2	478	Examples:
40.54	479	)))
2.2	480
40.54	481	(((
2.2	482	Below are examples for the how above AT Commands works.
40.54	483	)))
2.2	484
40.54	485	(((
2.2	486	AT+COMMANDx : This command will be sent to RS485/TTL devices during each sampling, Max command length is 14 bytes. The grammar is:
40.54	487	)))
2.2	488
40.49	489	(% border="1" class="table-bordered" style="background-color:#4f81bd; color:white; width:500px" %)
18.2	490	\|(% style="width:498px" %)(((
40.54	491	(((
2.2	492	AT+COMMANDx=xx xx xx xx xx xx xx xx xx xx xx xx,m
40.54	493	)))
2.2	494
40.54	495	(((
2.2	496	xx xx xx xx xx xx xx xx xx xx xx xx: The RS485 command to be sent
40.54	497	)))
2.2	498
40.54	499	(((
2.2	500	m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
	501	)))
40.54	502	)))
2.2	503
40.55	504	(((
2.2	505	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.
40.55	506	)))
2.2	507
40.55	508	(((
2.2	509	In the RS485-BL, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
40.55	510	)))
2.2	511
40.55	512	(((
2.2	513	AT+SEARCHx: This command defines how to handle the return from AT+COMMANDx.
40.55	514	)))
2.2	515
40.49	516	(% border="1" class="table-bordered" style="background-color:#4f81bd; color:white; width:500px" %)
18.2	517	\|(% style="width:577px" %)(((
40.55	518	(((
2.2	519	AT+SEARCHx=aa,xx xx xx xx xx
40.55	520	)))
2.2	521
40.55	522	* (((
	523	aa: 1: prefix match mode; 2: prefix and suffix match mode
2.2	524	)))
40.55	525	* (((
	526	xx xx xx xx xx: match string. Max 5 bytes for prefix and 5 bytes for suffix
	527	)))
	528	)))
2.2	529
40.55	530	(((
18.2	531	Examples:
40.55	532	)))
2.2	533
40.55	534	(((
29.27	535	1）For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
40.55	536	)))
2.2	537
40.55	538	(((
2.2	539	If we set AT+SEARCH1=1,1E 56 34. (max 5 bytes for prefix)
40.55	540	)))
2.2	541
40.55	542	(((
18.2	543	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
40.55	544	)))
2.2	545
40.55	546	(((
18.2	547	[[image:1653271044481-711.png]]
40.55	548	)))
2.2	549
40.55	550	(((
29.27	551	2）For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
40.55	552	)))
2.2	553
40.55	554	(((
2.2	555	If we set AT+SEARCH1=2, 1E 56 34+31 00 49
40.55	556	)))
2.2	557
40.55	558	(((
18.2	559	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
40.55	560	)))
2.2	561
40.55	562	(((
19.2	563	[[image:1653271276735-972.png]]
40.55	564	)))
2.2	565
40.55	566	(((
2.2	567	AT+DATACUTx : This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes.
40.55	568	)))
2.2	569
40.49	570	(% style="background-color:#4f81bd; color:white; width:510px" %)
23.2	571	\|(% style="width:726px" %)(((
40.55	572	(((
2.2	573	AT+DATACUTx=a,b,c
40.55	574	)))
2.2	575
40.55	576	* (((
	577	a: length for the return of AT+COMMAND
2.2	578	)))
40.55	579	* (((
	580	b:1: grab valid value by byte, max 6 bytes. 2: grab valid value by bytes section, max 3 sections.
	581	)))
	582	* (((
	583	c: define the position for valid value.
	584	)))
	585	)))
2.2	586
40.55	587	(((
29.27	588	Examples:
40.55	589	)))
2.2	590
40.55	591	* (((
	592	Grab bytes:
	593	)))
2.2	594
40.55	595	(((
23.2	596	[[image:1653271581490-837.png\|\|height="313" width="722"]]
40.55	597	)))
2.2	598
40.55	599	(((
	600
	601	)))
29.26	602
40.55	603	* (((
	604	Grab a section.
	605	)))
2.2	606
40.55	607	(((
23.2	608	[[image:1653271648378-342.png\|\|height="326" width="720"]]
40.55	609	)))
2.2	610
40.55	611	(((
	612
	613	)))
29.29	614
40.55	615	* (((
	616	Grab different sections.
	617	)))
2.2	618
40.55	619	(((
23.2	620	[[image:1653271657255-576.png\|\|height="305" width="730"]]
40.55	621	)))
2.2	622
24.2	623	(((
40.55	624	(((
23.2	625	(% style="color:red" %)Note:
24.2	626	)))
40.55	627	)))
2.2	628
24.2	629	(((
40.55	630	(((
2.2	631	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.
24.2	632	)))
40.55	633	)))
2.2	634
24.2	635	(((
40.55	636	(((
23.2	637	Example:
24.2	638	)))
40.55	639	)))
2.2	640
24.2	641	(((
40.55	642	(((
23.2	643	(% style="color:red" %)AT+COMMAND1=11 01 1E D0,0
24.2	644	)))
40.55	645	)))
2.2	646
24.2	647	(((
40.55	648	(((
23.2	649	(% style="color:red" %)AT+SEARCH1=1,1E 56 34
24.2	650	)))
40.55	651	)))
2.2	652
24.2	653	(((
40.55	654	(((
23.2	655	(% style="color:red" %)AT+DATACUT1=0,2,1~~5
24.2	656	)))
40.55	657	)))
2.2	658
24.2	659	(((
40.55	660	(((
23.2	661	(% style="color:red" %)Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
24.2	662	)))
40.55	663	)))
2.2	664
24.2	665	(((
40.55	666	(((
23.2	667	(% style="color:red" %)String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
24.2	668	)))
40.55	669	)))
2.2	670
24.2	671	(((
40.55	672	(((
23.2	673	(% style="color:red" %)Valid payload after DataCUT command: 2e 30 58 5f 36
24.2	674	)))
40.55	675	)))
2.2	676
40.55	677	(((
24.2	678	[[image:1653271763403-806.png]]
40.55	679	)))
2.2	680
29.30	681
26.2	682	=== 3.3.4 Compose the uplink payload ===
2.2	683
26.2	684	(((
2.2	685	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.
40.51	686
	687
26.2	688	)))
2.2	689
26.2	690	(((
29.33	691	(% style="color:#037691" %)Examples: AT+DATAUP=0
40.51	692
	693
26.2	694	)))
2.2	695
26.2	696	(((
	697	Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)A SIGNLE UPLINK.
	698	)))
2.2	699
26.2	700	(((
2.2	701	Final Payload is
26.2	702	)))
2.2	703
26.2	704	(((
29.33	705	(% style="color:#4f81bd" %)Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx
26.2	706	)))
2.2	707
26.2	708	(((
2.2	709	Where PAYVER is defined by AT+PAYVER, below is an example screen shot.
26.2	710	)))
2.2	711
26.2	712	[[image:1653272787040-634.png\|\|height="515" width="719"]]
2.2	713
29.31	714
29.33	715
26.2	716	(((
29.33	717	(% style="color:#037691" %)Examples: AT+DATAUP=1
29.32	718
	719
26.2	720	)))
2.2	721
26.2	722	(((
	723	Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)Multiply UPLINKs.
	724	)))
2.2	725
26.2	726	(((
2.2	727	Final Payload is
26.2	728	)))
2.2	729
26.2	730	(((
29.33	731	(% style="color:#4f81bd" %)Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA
26.2	732	)))
2.2	733
26.2	734	1. (((
	735	Battery Info (2 bytes): Battery voltage
	736	)))
	737	1. (((
	738	PAYVER (1 byte): Defined by AT+PAYVER
	739	)))
	740	1. (((
	741	PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling.
	742	)))
	743	1. (((
	744	PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
	745	)))
	746	1. (((
	747	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
	748	)))
2.2	749
26.2	750	[[image:1653272817147-600.png\|\|height="437" width="717"]]
2.2	751
	752	So totally there will be 3 uplinks for this sampling, each uplink includes 6 bytes DATA
	753
29.36	754
28.2	755	DATA1=RETURN1 Valid Value = (% style="background-color:#4f81bd; color:white" %) 20 20 0a 33 90 41
2.2	756
28.2	757	DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= (% style="background-color:#4f81bd; color:white" %)02 aa 05 81 0a 20
2.2	758
28.2	759	DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 =(% style="background-color:#4f81bd; color:white" %) 20 20 20 2d 30
2.2	760
29.36	761
2.2	762	Below are the uplink payloads:
	763
28.2	764	[[image:1653272901032-107.png]]
2.2	765
29.34	766
28.2	767	(% 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	768
	769	~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink ( so 51 -5 = 46 max valid date)
	770
	771	* For AU915/AS923 bands, if UplinkDwell time=1, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date).
	772
	773	* For US915 band, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date).
	774
	775	~* For all other bands: max 51 bytes for each uplink ( so 51 -5 = 46 max valid date).
	776
29.36	777
	778
28.2	779	=== 3.3.5 Uplink on demand ===
2.2	780
28.2	781	(((
2.2	782	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.
28.2	783	)))
2.2	784
28.2	785	(((
2.2	786	Downlink control command:
28.2	787	)))
2.2	788
28.2	789	(((
	790	0x08 command: Poll an uplink with current command set in RS485-BL.
	791	)))
2.2	792
28.2	793	(((
	794	0xA8 command: Send a command to RS485-BL and uplink the output from sensors.
29.37	795
	796
28.2	797	)))
2.2	798
28.2	799	=== 3.3.6 Uplink on Interrupt ===
2.2	800
28.2	801	Put the interrupt sensor between 3.3v_out and GPIO ext.
2.2	802
28.2	803	[[image:1653273818896-432.png]]
2.2	804
29.38	805
28.4	806	(((
2.2	807	AT+INTMOD=0 Disable Interrupt
28.4	808	)))
2.2	809
28.4	810	(((
2.2	811	AT+INTMOD=1 Interrupt trigger by rising or falling edge.
28.4	812	)))
2.2	813
28.4	814	(((
2.2	815	AT+INTMOD=2 Interrupt trigger by falling edge. ( Default Value)
28.4	816	)))
2.2	817
28.4	818	(((
2.2	819	AT+INTMOD=3 Interrupt trigger by rising edge.
29.38	820
	821
28.4	822	)))
2.2	823
28.2	824	== 3.4 Uplink Payload ==
2.2	825
41.2	826	[[image:image-20220606105412-1.png]]
2.2	827
	828	Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors.
	829
29.2	830	(((
29.39	831	{{{function Decoder(bytes, port) {}}}
29.2	832	)))
2.2	833
29.2	834	(((
29.39	835	{{{//Payload Formats of RS485-BL Deceive}}}
29.2	836	)))
2.2	837
29.2	838	(((
29.39	839	{{{return {}}}
29.2	840	)))
2.2	841
29.2	842	(((
29.39	843	{{{ //Battery,units:V}}}
29.2	844	)))
2.2	845
29.2	846	(((
29.39	847	{{{ BatV:((bytes[0]<<8 \| bytes[1])&0x7fff)/1000,}}}
29.2	848	)))
2.2	849
29.2	850	(((
29.39	851	{{{ //GPIO_EXTI }}}
29.2	852	)))
2.2	853
29.2	854	(((
29.39	855	{{{ EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE",}}}
29.2	856	)))
2.2	857
29.2	858	(((
29.39	859	{{{ //payload of version}}}
29.2	860	)))
2.2	861
29.2	862	(((
29.39	863	{{{ Pay_ver:bytes[2],}}}
29.2	864	)))
2.2	865
29.2	866	(((
29.39	867	{{{ }; }}}
29.2	868	)))
2.2	869
29.2	870	(((
40.19	871	}
29.39	872
	873
29.2	874	)))
2.2	875
29.2	876	(((
2.2	877	TTN V3 uplink screen shot.
29.2	878	)))
2.2	879
29.2	880	[[image:1653274001211-372.png\|\|height="192" width="732"]]
2.2	881
29.39	882
29.3	883	== 3.5 Configure RS485-BL via AT or Downlink ==
2.2	884
29.40	885	User can configure RS485-BL via AT Commands or LoRaWAN Downlink Commands
2.2	886
	887	There are two kinds of Commands:
	888
40.8	889	* (% style="color:#4f81bd" %)Common Commands(%%): They should be available for each sensor, such as: change uplink interval, reset device. For firmware v1.3, user can find what common commands it supports: [[AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]
2.2	890
29.40	891	* (% style="color:#4f81bd" %)Sensor Related Commands(%%): These commands are special designed for RS485-BL. User can see these commands below:
2.2	892
41.4	893
	894
29.40	895	=== 3.5.1 Common Commands: ===
2.2	896
29.40	897	They should be available for each of Dragino Sensors, such as: change uplink interval, reset device. For firmware v1.3, user can find what common commands it supports: [[End Device AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]
2.2	898
29.40	899
	900	=== 3.5.2 Sensor related commands: ===
	901
2.2	902
29.41	903	==== Choose Device Type (RS485 or TTL) ====
	904
2.2	905	RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect.
	906
29.42	907	* AT Command
2.2	908
30.3	909	(% class="box infomessage" %)
	910	(((
2.2	911	AT+MOD=1 ~/~/ Set to support RS485-MODBUS type sensors. User can connect multiply RS485 , Modbus sensors to the A / B pins.
30.3	912	)))
2.2	913
30.3	914	(% class="box infomessage" %)
	915	(((
2.2	916	AT+MOD=2 ~/~/ Set to support TTL Level sensors, User can connect one TTL Sensor to the TXD/RXD/GND pins.
30.3	917	)))
2.2	918
	919
29.42	920	* Downlink Payload
2.2	921
29.42	922	0A aa ~-~-> same as AT+MOD=aa
2.2	923
	924
	925
41.5	926
29.43	927	==== RS485 Debug Command (AT+CFGDEV) ====
2.2	928
	929	This command is used to configure the RS485 or TTL sensors; they won’t be used during sampling.
	930
29.43	931	* AT Command
2.2	932
30.3	933	(% class="box infomessage" %)
	934	(((
	935	AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
	936	)))
2.2	937
	938	m: 0: no CRC; 1: add CRC-16/MODBUS in the end of this command.
	939
	940
29.43	941	* Downlink Payload
2.2	942
	943	Format: A8 MM NN XX XX XX XX YY
	944
	945	Where:
	946
	947	* MM: 1: add CRC-16/MODBUS ; 0: no CRC
	948	* NN: The length of RS485 command
	949	* XX XX XX XX: RS485 command total NN bytes
	950	* 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
	951
	952	Example 1:
	953
	954	To connect a Modbus Alarm with below commands.
	955
30.2	956	* 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.
2.2	957
30.2	958	* 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.
2.2	959
	960	So if user want to use downlink command to control to RS485 Alarm, he can use:
	961
30.2	962	(% style="color:#037691" %)A8 01 06 0A 05 00 04 00 01 00(%%): to activate the RS485 Alarm
2.2	963
30.2	964	(% style="color:#037691" %)A8 01 06 0A 05 00 04 00 00 00(%%): to deactivate the RS485 Alarm
2.2	965
	966	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.
	967
	968
	969	Example 2:
	970
	971	Check TTL Sensor return:
	972
30.2	973	[[image:1654132684752-193.png]]
2.2	974
	975
	976
40.10	977
41.6	978
30.3	979	==== Set Payload version ====
2.2	980
	981	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.
	982
30.3	983	* AT Command:
2.2	984
30.3	985	(% class="box infomessage" %)
	986	(((
	987	AT+PAYVER: Set PAYVER field = 1
	988	)))
2.2	989
	990
30.3	991	* Downlink Payload:
2.2	992
30.4	993	0xAE 01 ~-~-> Set PAYVER field = 0x01
2.2	994
30.4	995	0xAE 0F ~-~-> Set PAYVER field = 0x0F
2.2	996
	997
	998
41.7	999
30.4	1000	==== Set RS485 Sampling Commands ====
	1001
2.2	1002	AT+COMMANDx, AT+DATACUTx and AT+SEARCHx
	1003
30.5	1004	These three commands are used to configure how the RS485-BL polling data from Modbus device. Detail of usage please see : [[polling RS485 device>>\|\|anchor="H3.3.3Configurereadcommandsforeachsampling"]].
2.2	1005
	1006
30.7	1007	* AT Command:
2.2	1008
30.7	1009	(% class="box infomessage" %)
	1010	(((
	1011	AT+COMMANDx: Configure RS485 read command to sensor.
	1012	)))
2.2	1013
30.7	1014	(% class="box infomessage" %)
	1015	(((
	1016	AT+DATACUTx: Configure how to handle return from RS485 devices.
	1017	)))
2.2	1018
30.7	1019	(% class="box infomessage" %)
	1020	(((
	1021	AT+SEARCHx: Configure search command
	1022	)))
2.2	1023
	1024
30.7	1025	* Downlink Payload:
2.2	1026
30.7	1027	0xAF downlink command can be used to set AT+COMMANDx or AT+DATACUTx.
2.2	1028
30.7	1029	(% style="color:red" %)Note(%%): if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink.
2.2	1030
	1031	Format: AF MM NN LL XX XX XX XX YY
	1032
	1033	Where:
	1034
	1035	* MM: the ATCOMMAND or AT+DATACUT to be set. Value from 01 ~~ 0F,
30.7	1036	* NN: 0: no CRC; 1: add CRC-16/MODBUS ; 2: set the AT+DATACUT value.
	1037	* LL: The length of AT+COMMAND or AT+DATACUT command
2.2	1038	* XX XX XX XX: AT+COMMAND or AT+DATACUT command
30.7	1039	* 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.
2.2	1040
30.7	1041	Example:
2.2	1042
30.7	1043	(% style="color:#037691" %)AF 03 01 06 0A 05 00 04 00 01 00(%%): Same as AT+COMMAND3=0A 05 00 04 00 01,1
2.2	1044
30.7	1045	(% style="color:#037691" %)AF 03 02 06(% style="color:orange" %) 10 (% style="color:red" %)01 (% style="color:green" %)05 06 09 0A(% style="color:#037691" %) 00(%%): Same as AT+DATACUT3=(% style="color:orange" %)16(%%),(% style="color:red" %)1(%%),(% style="color:green" %)5+6+9+10
2.2	1046
30.7	1047	(% style="color:#037691" %)AF 03 02 06 (% style="color:orange" %)0B(% style="color:red" %) 02 (% style="color:green" %)05 07 08 0A (% style="color:#037691" %)00(%%): Same as AT+DATACUT3=(% style="color:orange" %)11(%%),(% style="color:red" %)2(%%),(% style="color:green" %)5~~7+8~~10
2.2	1048
	1049
30.8	1050	0xAB downlink command can be used for set AT+SEARCHx
2.2	1051
30.8	1052	Example: AB aa 01 03 xx xx xx (03 here means there are total 3 bytes after 03) So
2.2	1053
	1054	* AB aa 01 03 xx xx xx same as AT+SEARCHaa=1,xx xx xx
	1055	* 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
	1056
	1057	AB aa 02 03 xx xx xx 02 yy yy same as AT+SEARCHaa=2,xx xx xx+yy yy
	1058
	1059
30.8	1060
41.8	1061
31.2	1062	==== Fast command to handle MODBUS device ====
2.2	1063
	1064	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]].
	1065
	1066	This command is valid since v1.3 firmware version
	1067
	1068
31.2	1069	AT+MBFUN has only two value:
2.2	1070
32.2	1071	* AT+MBFUN=1: Enable Modbus reading. And get response base on the MODBUS return
2.2	1072
	1073	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.
	1074
32.2	1075	* AT+MBFUN=0: Disable Modbus fast reading.
2.2	1076
31.2	1077	Example:
	1078
2.2	1079	* AT+MBFUN=1 and AT+DATACUT1/AT+DATACUT2 are not configure (0,0,0).
	1080	* 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.
	1081	* 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.
	1082
31.2	1083	[[image:1654133913295-597.png]]
2.2	1084
	1085
32.2	1086	[[image:1654133954153-643.png]]
2.2	1087
	1088
32.3	1089	* Downlink Commands:
2.2	1090
32.3	1091	A9 aa ~-~-> Same as AT+MBFUN=aa
2.2	1092
	1093
32.3	1094
32.4	1095	==== RS485 command timeout ====
2.2	1096
	1097	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.
	1098
	1099	Default value: 0, range: 0 ~~ 5 seconds
	1100
	1101
32.4	1102	* AT Command:
2.2	1103
32.4	1104	(% class="box infomessage" %)
	1105	(((
	1106	AT+CMDDLaa=hex(bb cc)
	1107	)))
2.2	1108
32.5	1109	Example:
2.2	1110
	1111	AT+CMDDL1=1000 to send the open time to 1000ms
	1112
	1113
32.4	1114	* Downlink Payload:
2.2	1115
	1116	0x AA aa bb cc
	1117
	1118	Same as: AT+CMDDLaa=hex(bb cc)
	1119
32.5	1120	Example:
2.2	1121
32.5	1122	0xAA 01 03 E8 ~-~-> Same as AT+CMDDL1=1000 ms
2.2	1123
	1124
	1125
32.6	1126	==== Uplink payload mode ====
	1127
2.2	1128	Define to use one uplink or multiple uplinks for the sampling.
	1129
32.7	1130	The use of this command please see: [[Compose Uplink payload>>\|\|anchor="H3.3.4Composetheuplinkpayload"]]
2.2	1131
32.8	1132	* AT Command:
2.2	1133
32.8	1134	(% class="box infomessage" %)
	1135	(((
	1136	AT+DATAUP=0
	1137	)))
2.2	1138
32.8	1139	(% class="box infomessage" %)
	1140	(((
	1141	AT+DATAUP=1
	1142	)))
2.2	1143
	1144
32.8	1145	* Downlink Payload:
2.2	1146
32.9	1147	0xAD 00 ~-~-> Same as AT+DATAUP=0
2.2	1148
32.9	1149	0xAD 01 ~-~-> Same as AT+DATAUP=1
2.2	1150
	1151
	1152
40.20	1153
32.9	1154	==== Manually trigger an Uplink ====
	1155
2.2	1156	Ask device to send an uplink immediately.
	1157
32.10	1158	* Downlink Payload:
2.2	1159
32.10	1160	0x08 FF, RS485-BL will immediately send an uplink.
2.2	1161
	1162
	1163
40.21	1164
32.10	1165	==== Clear RS485 Command ====
	1166
2.2	1167	The AT+COMMANDx and AT+DATACUTx settings are stored in special location, user can use below command to clear them.
	1168
	1169
33.2	1170	* AT Command:
2.2	1171
33.2	1172	(% style="color:#037691" %)AT+CMDEAR=mm,nn (%%) mm: start position of erase ,nn: stop position of erase Etc. AT+CMDEAR=1,10 means erase AT+COMMAND1/AT+DATACUT1 to AT+COMMAND10/AT+DATACUT10
2.2	1173
6.2	1174	Example screen shot after clear all RS485 commands.
2.2	1175
	1176
	1177	The uplink screen shot is:
	1178
33.2	1179	[[image:1654134704555-320.png]]
2.2	1180
	1181
33.2	1182	* Downlink Payload:
2.2	1183
33.2	1184	0x09 aa bb same as AT+CMDEAR=aa,bb
2.2	1185
	1186
	1187
33.2	1188	==== Set Serial Communication Parameters ====
	1189
2.2	1190	Set the Rs485 serial communication parameters:
	1191
33.2	1192	* AT Command:
2.2	1193
	1194	Set Baud Rate:
	1195
33.2	1196	(% class="box infomessage" %)
	1197	(((
	1198	AT+BAUDR=9600 ~/~/ Options: (1200,2400,4800,14400,19200,115200)
	1199	)))
2.2	1200
33.2	1201	Set UART Parity
2.2	1202
33.2	1203	(% class="box infomessage" %)
	1204	(((
	1205	AT+PARITY=0 ~/~/ Option: 0: no parity, 1: odd parity, 2: even parity
	1206	)))
2.2	1207
	1208	Set STOPBIT
	1209
33.2	1210	(% class="box infomessage" %)
	1211	(((
	1212	AT+STOPBIT=0 ~/~/ Option: 0 for 1bit; 1 for 1.5 bit ; 2 for 2 bits
	1213	)))
2.2	1214
	1215
33.2	1216	* Downlink Payload:
2.2	1217
33.2	1218	A7 01 aa bb: Same AT+BAUDR=hex(aa bb)*100
2.2	1219
33.2	1220	Example:
2.2	1221
	1222	* A7 01 00 60 same as AT+BAUDR=9600
	1223	* A7 01 04 80 same as AT+BAUDR=115200
	1224
	1225	A7 02 aa: Same as AT+PARITY=aa (aa value: 00 , 01 or 02)
	1226
	1227	A7 03 aa: Same as AT+STOPBIT=aa (aa value: 00 , 01 or 02)
	1228
	1229
	1230
33.2	1231	==== Control output power duration ====
	1232
2.2	1233	User can set the output power duration before each sampling.
	1234
33.3	1235	* AT Command:
2.2	1236
33.3	1237	Example:
2.2	1238
33.3	1239	AT+3V3T=1000 ~/~/ 3V3 output power will open 1s before each sampling.
2.2	1240
33.3	1241	AT+5VT=1000 ~/~/ +5V output power will open 1s before each sampling.
2.2	1242
	1243
33.3	1244	* LoRaWAN Downlink Command:
2.2	1245
33.3	1246	07 01 aa bb Same as AT+5VT=(aa bb)
2.2	1247
33.3	1248	07 02 aa bb Same as AT+3V3T=(aa bb)
2.2	1249
	1250
40.22	1251
33.4	1252	== 3.6 Buttons ==
2.2	1253
33.4	1254	(% border="1" style="background-color:#ffffcc; color:green; width:233px" %)
	1255	\|=(% style="width: 89px;" %)Button\|=(% style="width: 141px;" %)Feature
	1256	\|(% style="width:89px" %)RST\|(% style="width:141px" %)Reboot RS485-BL
2.2	1257
33.4	1258	== 3.7 +3V3 Output ==
2.2	1259
	1260	RS485-BL has a Controllable +3V3 output, user can use this output to power external sensor.
	1261
6.2	1262	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	1263
	1264	The +3V3 output time can be controlled by AT Command.
	1265
	1266
33.4	1267	(% style="color:#037691" %)AT+3V3T=1000
	1268
	1269
2.2	1270	Means set +3v3 valid time to have 1000ms. So, the real +3v3 output will actually have 1000ms + sampling time for other sensors.
	1271
	1272	By default, the AT+3V3T=0. This is a special case, means the +3V3 output is always on at any time
	1273
	1274
33.4	1275	== 3.8 +5V Output ==
2.2	1276
	1277	RS485-BL has a Controllable +5V output, user can use this output to power external sensor.
	1278
6.2	1279	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	1280
	1281	The 5V output time can be controlled by AT Command.
	1282
33.6	1283
33.4	1284	(% style="color:#037691" %)AT+5VT=1000
2.2	1285
33.6	1286
2.2	1287	Means set 5V valid time to have 1000ms. So, the real 5V output will actually have 1000ms + sampling time for other sensors.
	1288
	1289	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.
	1290
	1291
33.4	1292	== 3.9 LEDs ==
2.2	1293
33.6	1294	(% border="1" style="background-color:#ffffcc; color:green; width:332px" %)
	1295	\|=LEDs\|=(% style="width: 274px;" %)Feature
	1296	\|LED1\|(% style="width:274px" %)Blink when device transmit a packet.
2.2	1297
33.4	1298	== 3.10 Switch Jumper ==
2.2	1299
33.8	1300	(% border="1" style="background-color:#ffffcc; color:green; width:515px" %)
	1301	\|=(% style="width: 124px;" %)Switch Jumper\|=(% style="width: 388px;" %)Feature
	1302	\|(% style="width:124px" %)SW1\|(% style="width:388px" %)(((
2.2	1303	ISP position: Upgrade firmware via UART
	1304
	1305	Flash position: Configure device, check running status.
	1306	)))
33.8	1307	\|(% style="width:124px" %)SW2\|(% style="width:388px" %)(((
2.2	1308	5V position: set to compatible with 5v I/O.
	1309
	1310	3.3v position: set to compatible with 3.3v I/O.,
	1311	)))
	1312
33.8	1313	+3.3V: is always ON
2.2	1314
33.8	1315	+5V: Only open before every sampling. The time is by default, it is AT+5VT=0. Max open time. 5000 ms.
2.2	1316
33.8	1317
33.9	1318	= 4. Case Study =
2.2	1319
33.10	1320	User can check this URL for some case studies: [[APP RS485 COMMUNICATE WITH SENSORS>>doc:Main.Application Note \: Communicate with Different Sensors ----- RS485-LN RS485-BL.WebHome]]
2.2	1321
	1322
33.11	1323	= 5. Use AT Command =
2.2	1324
33.11	1325	== 5.1 Access AT Command ==
2.2	1326
	1327	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.
	1328
34.2	1329	[[image:1654135840598-282.png]]
2.2	1330
	1331
35.2	1332	In PC, User needs to set (% style="color:blue" %)serial tool(%%)(such as [[putty>>url:https://www.chiark.greenend.org.uk/~~sgtatham/putty/latest.html]], SecureCRT) baud rate to (% style="color:green" %)9600(%%) to access to access serial console of RS485-BL. The default password is 123456. Below is the output for reference:
2.2	1333
35.2	1334	[[image:1654136105500-922.png]]
2.2	1335
	1336
40.27	1337	More detail AT Command manual can be found at [[AT Command Manual>>\|\|anchor="H3.5ConfigureRS485-BLviaATorDownlink"]]
2.2	1338
	1339
35.2	1340	== 5.2 Common AT Command Sequence ==
2.2	1341
35.2	1342	=== 5.2.1 Multi-channel ABP mode (Use with SX1301/LG308) ===
2.2	1343
	1344	If device has not joined network yet:
	1345
35.4	1346	(% class="box infomessage" %)
	1347	(((
	1348	AT+FDR
	1349	)))
2.2	1350
35.4	1351	(% class="box infomessage" %)
	1352	(((
	1353	AT+NJM=0
	1354	)))
2.2	1355
35.4	1356	(% class="box infomessage" %)
	1357	(((
	1358	ATZ
	1359	)))
2.2	1360
	1361
	1362	If device already joined network:
	1363
35.4	1364	(% class="box infomessage" %)
	1365	(((
	1366	AT+NJM=0
	1367	)))
2.2	1368
35.4	1369	(% class="box infomessage" %)
	1370	(((
	1371	ATZ
	1372	)))
2.2	1373
	1374
35.4	1375	=== 5.5.2 Single-channel ABP mode (Use with LG01/LG02) ===
	1376
	1377
35.5	1378	(% style="background-color:#dcdcdc" %)AT+FDR (%%) Reset Parameters to Factory Default, Keys Reserve
2.2	1379
35.5	1380	(% style="background-color:#dcdcdc" %)AT+NJM=0 (%%)Set to ABP mode
2.2	1381
35.5	1382	(% style="background-color:#dcdcdc" %)AT+ADR=0 (%%)Set the Adaptive Data Rate Off
2.2	1383
35.5	1384	(% style="background-color:#dcdcdc" %)AT+DR=5 (%%)Set Data Rate
2.2	1385
35.5	1386	(% style="background-color:#dcdcdc" %)AT+TDC=60000 (%%) Set transmit interval to 60 seconds
2.2	1387
35.5	1388	(% style="background-color:#dcdcdc" %)AT+CHS=868400000(%%) Set transmit frequency to 868.4Mhz
2.2	1389
35.5	1390	(% style="background-color:#dcdcdc" %)AT+RX2FQ=868400000 (%%) Set RX2Frequency to 868.4Mhz (according to the result from server)
2.2	1391
35.5	1392	(% style="background-color:#dcdcdc" %)AT+RX2DR=5 (%%) Set RX2DR to match the downlink DR from server. see below
2.2	1393
35.5	1394	(% style="background-color:#dcdcdc" %)AT+DADDR=26 (%%) 01 1A F1 Set Device Address to 26 01 1A F1, this ID can be found in the LoRa Server portal.
2.2	1395
35.5	1396	(% style="background-color:#dcdcdc" %)ATZ (%%) Reset MCU
2.2	1397
36.3	1398
35.5	1399	(% style="color:red" %)Note:
2.2	1400
36.2	1401	(% style="color:red" %)1. Make sure the device is set to ABP mode in the IoT Server.
	1402	2. Make sure the LG01/02 gateway RX frequency is exactly the same as AT+CHS setting.
	1403	3. Make sure SF / bandwidth setting in LG01/LG02 match the settings of AT+DR. refer [[this link>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/&file=LoRaWAN%201.0.3%20Regional%20Parameters.xlsx]] to see what DR means.
	1404	4. The command AT+RX2FQ and AT+RX2DR is to let downlink work. to set the correct parameters, user can check the actually downlink parameters to be used. As below. Which shows the RX2FQ should use 868400000 and RX2DR should be 5
2.2	1405
36.2	1406	[[image:1654136435598-589.png]]
2.2	1407
	1408
37.2	1409	= 6. FAQ =
2.2	1410
37.2	1411	== 6.1 How to upgrade the image? ==
	1412
2.2	1413	The RS485-BL LoRaWAN Controller is shipped with a 3.5mm cable, the cable is used to upload image to RS485-BL to:
	1414
	1415	* Support new features
	1416	* For bug fix
	1417	* Change LoRaWAN bands.
	1418
	1419	Below shows the hardware connection for how to upload an image to RS485-BL:
	1420
37.2	1421	[[image:1654136646995-976.png]]
2.2	1422
	1423	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]].
	1424
	1425	Step2: Download the [[LT Image files>>url:http://www.dragino.com/downloads/index.php?dir=LT_LoRa_IO_Controller/LT33222-L/image/]].
	1426
	1427	Step3: Open flashloader; choose the correct COM port to update.
	1428
38.2	1429	[[image:image-20220602102605-1.png]]
2.2	1430
	1431
39.2	1432	[[image:image-20220602102637-2.png]]
2.2	1433
	1434
40.2	1435	[[image:image-20220602102715-3.png]]
39.2	1436
	1437
	1438
40.3	1439	== 6.2 How to change the LoRa Frequency Bands/Region? ==
39.2	1440
40.32	1441	(((
40.3	1442	User can follow the introduction for [[how to upgrade image>>\|\|anchor="H6.1Howtoupgradetheimage3F"]]. When download the images, choose the required image file for download.
40.32	1443	)))
2.2	1444
	1445
	1446
40.3	1447	== 6.3 How many RS485-Slave can RS485-BL connects? ==
2.2	1448
40.31	1449	(((
40.3	1450	The RS485-BL can support max 32 RS485 devices. Each uplink command of RS485-BL can support max 16 different RS485 command. So RS485-BL can support max 16 RS485 devices pre-program in the device for uplink. For other devices no pre-program, user can use the [[downlink message (type code 0xA8) to poll their info>>\|\|anchor="H3.3.3Configurereadcommandsforeachsampling"]].
40.31	1451	)))
2.2	1452
	1453
	1454
40.3	1455	= 7. Trouble Shooting =
2.2	1456
	1457
40.3	1458	== 7.1 Downlink doesn’t work, how to solve it? ==
2.2	1459
40.3	1460	Please see this link for debug: [[LoRaWAN Communication Debug>>doc:Main.LoRaWAN Communication Debug.WebHome]]
2.2	1461
	1462
40.3	1463	== 7.2 Why I can’t join TTN V3 in US915 /AU915 bands? ==
2.2	1464
40.3	1465	It might about the channels mapping. Please see for detail: [[Notice of Frequency band>>doc:Main.LoRaWAN Communication Debug.WebHome\|\|anchor="H2.NoticeofUS9152FCN4702FAU915Frequencyband"]]
2.2	1466
	1467
40.3	1468	= 8. Order Info =
2.2	1469
40.5	1470	(% style="color:blue" %)Part Number: RS485-BL-XXX
2.2	1471
40.5	1472	(% style="color:blue" %)XXX:
2.2	1473
40.5	1474	* (% style="color:blue" %)EU433(%%): frequency bands EU433
	1475	* (% style="color:blue" %)EU868(%%): frequency bands EU868
	1476	* (% style="color:blue" %)KR920(%%): frequency bands KR920
	1477	* (% style="color:blue" %)CN470(%%): frequency bands CN470
	1478	* (% style="color:blue" %)AS923(%%): frequency bands AS923
	1479	* (% style="color:blue" %)AU915(%%): frequency bands AU915
	1480	* (% style="color:blue" %)US915(%%): frequency bands US915
	1481	* (% style="color:blue" %)IN865(%%): frequency bands IN865
	1482	* (% style="color:blue" %)RU864(%%): frequency bands RU864
	1483	* (% style="color:blue" %)KZ865(%%): frequency bands KZ865
2.2	1484
40.3	1485	= 9. Packing Info =
2.2	1486
40.4	1487	(((
2.2	1488	Package Includes:
40.4	1489	)))
2.2	1490
40.4	1491	* (((
	1492	RS485-BL x 1
	1493	)))
	1494	* (((
	1495	Stick Antenna for LoRa RF part x 1
	1496	)))
	1497	* (((
	1498	Program cable x 1
	1499	)))
2.2	1500
40.4	1501	(((
2.2	1502	Dimension and weight:
40.4	1503	)))
2.2	1504
40.4	1505	* (((
	1506	Device Size: 13.5 x 7 x 3 cm
	1507	)))
	1508	* (((
	1509	Device Weight: 105g
	1510	)))
	1511	* (((
	1512	Package Size / pcs : 14.5 x 8 x 5 cm
	1513	)))
	1514	* (((
	1515	Weight / pcs : 170g
40.6	1516
	1517
40.4	1518	)))
2.2	1519
40.3	1520	= 10. Support =
	1521
40.30	1522	* (((
	1523	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.
	1524	)))
	1525	* (((
	1526	Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[support@dragino.com>>url:file:///D:/市场资料/说明书/LoRa/LT系列/support@dragino.com]]
	1527	)))

Wiki source code of RS485-BL – Waterproof RS485 to LoRaWAN Converter

Applications