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

Version 40.52 by Xiaoling on 2022/06/06 10:50

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
15.6	385	=== 3.3.2 Configure sensors ===
2.2	386
15.6	387	(((
	388	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.
	389	)))
2.2	390
15.6	391	(((
	392	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.
	393	)))
2.2	394
40.48	395	(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
40.50	396	\|=(% style="width: 120px;" %)AT Commands\|=(% style="width: 190px;" %)Description\|=(% style="width: 190px;" %)Example
	397	\|AT+CFGDEV\|(% style="width:120px" %)(((
2.2	398	This command is used to configure the RS485/TTL devices; they won’t be used during sampling.
	399
15.6	400	AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,
2.2	401
15.6	402	mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
40.48	403	)))\|(% style="width:190px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
2.2	404
29.24	405	Detail of AT+CFGDEV command see [[AT+CFGDEV detail>>\|\|anchor="HRS485DebugCommand28AT2BCFGDEV29"]].
2.2	406
29.22	407
40.52	408
15.6	409	=== 3.3.3 Configure read commands for each sampling ===
2.2	410
15.6	411	(((
2.2	412	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	413	)))
2.2	414
15.6	415	(((
2.2	416	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	417	)))
2.2	418
15.6	419	(((
2.2	420	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	421	)))
2.2	422
15.6	423	(((
2.2	424	This section describes how to achieve above goals.
15.6	425	)))
2.2	426
15.6	427	(((
2.2	428	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	429	)))
2.2	430
15.6	431	(((
2.2	432	Command from RS485-BL to Sensor:
15.6	433	)))
2.2	434
15.6	435	(((
2.2	436	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	437	)))
2.2	438
15.6	439	(((
2.2	440	Handle return from sensors to RS485-BL:
15.6	441	)))
2.2	442
15.6	443	(((
2.2	444	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	445	)))
2.2	446
15.6	447	* (((
	448	AT+DATACUT
	449	)))
2.2	450
15.6	451	(((
2.2	452	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	453	)))
2.2	454
15.6	455	* (((
	456	AT+SEARCH
	457	)))
2.2	458
15.6	459	(((
2.2	460	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	461	)))
2.2	462
15.6	463	(((
2.2	464	Define wait timeout:
15.6	465	)))
2.2	466
15.6	467	(((
2.2	468	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	469	)))
2.2	470
15.6	471	(((
2.2	472	After we got the valid value from each RS485 commands, we need to combine them together with the command AT+DATAUP.
15.6	473	)))
2.2	474
	475	Examples:
	476
	477	Below are examples for the how above AT Commands works.
	478
	479	AT+COMMANDx : This command will be sent to RS485/TTL devices during each sampling, Max command length is 14 bytes. The grammar is:
	480
40.49	481	(% border="1" class="table-bordered" style="background-color:#4f81bd; color:white; width:500px" %)
18.2	482	\|(% style="width:498px" %)(((
2.2	483	AT+COMMANDx=xx xx xx xx xx xx xx xx xx xx xx xx,m
	484
	485	xx xx xx xx xx xx xx xx xx xx xx xx: The RS485 command to be sent
	486
	487	m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
	488	)))
	489
	490	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.
	491
	492	In the RS485-BL, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
	493
	494	AT+SEARCHx: This command defines how to handle the return from AT+COMMANDx.
	495
40.49	496	(% border="1" class="table-bordered" style="background-color:#4f81bd; color:white; width:500px" %)
18.2	497	\|(% style="width:577px" %)(((
2.2	498	AT+SEARCHx=aa,xx xx xx xx xx
	499
	500	* aa: 1: prefix match mode; 2: prefix and suffix match mode
	501	* xx xx xx xx xx: match string. Max 5 bytes for prefix and 5 bytes for suffix
	502	)))
	503
18.2	504	Examples:
2.2	505
29.27	506	1）For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
2.2	507
	508	If we set AT+SEARCH1=1,1E 56 34. (max 5 bytes for prefix)
	509
18.2	510	The valid data will be all bytes after 1E 56 34 , so it is (% style="background-color:yellow" %)2e 30 58 5f 36 41 30 31 00 49
2.2	511
18.2	512	[[image:1653271044481-711.png]]
2.2	513
29.27	514	2）For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
2.2	515
	516	If we set AT+SEARCH1=2, 1E 56 34+31 00 49
	517
18.2	518	Device will search the bytes between 1E 56 34 and 31 00 49. So it is(% style="background-color:yellow" %) 2e 30 58 5f 36 41 30
2.2	519
19.2	520	[[image:1653271276735-972.png]]
2.2	521
	522	AT+DATACUTx : This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes.
	523
40.49	524	(% style="background-color:#4f81bd; color:white; width:510px" %)
23.2	525	\|(% style="width:726px" %)(((
2.2	526	AT+DATACUTx=a,b,c
	527
	528	* a: length for the return of AT+COMMAND
	529	* b:1: grab valid value by byte, max 6 bytes. 2: grab valid value by bytes section, max 3 sections.
6.2	530	* c: define the position for valid value.
2.2	531	)))
	532
29.27	533	Examples:
2.2	534
	535	* Grab bytes:
	536
23.2	537	[[image:1653271581490-837.png\|\|height="313" width="722"]]
2.2	538
29.26	539
2.2	540	* Grab a section.
	541
23.2	542	[[image:1653271648378-342.png\|\|height="326" width="720"]]
2.2	543
29.29	544
2.2	545	* Grab different sections.
	546
23.2	547	[[image:1653271657255-576.png\|\|height="305" width="730"]]
2.2	548
24.2	549	(((
23.2	550	(% style="color:red" %)Note:
24.2	551	)))
2.2	552
24.2	553	(((
2.2	554	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	555	)))
2.2	556
24.2	557	(((
23.2	558	Example:
24.2	559	)))
2.2	560
24.2	561	(((
23.2	562	(% style="color:red" %)AT+COMMAND1=11 01 1E D0,0
24.2	563	)))
2.2	564
24.2	565	(((
23.2	566	(% style="color:red" %)AT+SEARCH1=1,1E 56 34
24.2	567	)))
2.2	568
24.2	569	(((
23.2	570	(% style="color:red" %)AT+DATACUT1=0,2,1~~5
24.2	571	)))
2.2	572
24.2	573	(((
23.2	574	(% 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	575	)))
2.2	576
24.2	577	(((
23.2	578	(% style="color:red" %)String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
24.2	579	)))
2.2	580
24.2	581	(((
23.2	582	(% style="color:red" %)Valid payload after DataCUT command: 2e 30 58 5f 36
24.2	583	)))
2.2	584
24.2	585	[[image:1653271763403-806.png]]
2.2	586
29.30	587
26.2	588	=== 3.3.4 Compose the uplink payload ===
2.2	589
26.2	590	(((
2.2	591	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	592
	593
26.2	594	)))
2.2	595
26.2	596	(((
29.33	597	(% style="color:#037691" %)Examples: AT+DATAUP=0
40.51	598
	599
26.2	600	)))
2.2	601
26.2	602	(((
	603	Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)A SIGNLE UPLINK.
	604	)))
2.2	605
26.2	606	(((
2.2	607	Final Payload is
26.2	608	)))
2.2	609
26.2	610	(((
29.33	611	(% style="color:#4f81bd" %)Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx
26.2	612	)))
2.2	613
26.2	614	(((
2.2	615	Where PAYVER is defined by AT+PAYVER, below is an example screen shot.
26.2	616	)))
2.2	617
26.2	618	[[image:1653272787040-634.png\|\|height="515" width="719"]]
2.2	619
29.31	620
29.33	621
26.2	622	(((
29.33	623	(% style="color:#037691" %)Examples: AT+DATAUP=1
29.32	624
	625
26.2	626	)))
2.2	627
26.2	628	(((
	629	Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)Multiply UPLINKs.
	630	)))
2.2	631
26.2	632	(((
2.2	633	Final Payload is
26.2	634	)))
2.2	635
26.2	636	(((
29.33	637	(% style="color:#4f81bd" %)Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA
26.2	638	)))
2.2	639
26.2	640	1. (((
	641	Battery Info (2 bytes): Battery voltage
	642	)))
	643	1. (((
	644	PAYVER (1 byte): Defined by AT+PAYVER
	645	)))
	646	1. (((
	647	PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling.
	648	)))
	649	1. (((
	650	PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
	651	)))
	652	1. (((
	653	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
	654	)))
2.2	655
26.2	656	[[image:1653272817147-600.png\|\|height="437" width="717"]]
2.2	657
	658	So totally there will be 3 uplinks for this sampling, each uplink includes 6 bytes DATA
	659
29.36	660
28.2	661	DATA1=RETURN1 Valid Value = (% style="background-color:#4f81bd; color:white" %) 20 20 0a 33 90 41
2.2	662
28.2	663	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	664
28.2	665	DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 =(% style="background-color:#4f81bd; color:white" %) 20 20 20 2d 30
2.2	666
29.36	667
2.2	668	Below are the uplink payloads:
	669
28.2	670	[[image:1653272901032-107.png]]
2.2	671
29.34	672
28.2	673	(% 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	674
	675	~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink ( so 51 -5 = 46 max valid date)
	676
	677	* For AU915/AS923 bands, if UplinkDwell time=1, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date).
	678
	679	* For US915 band, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date).
	680
	681	~* For all other bands: max 51 bytes for each uplink ( so 51 -5 = 46 max valid date).
	682
29.36	683
	684
28.2	685	=== 3.3.5 Uplink on demand ===
2.2	686
28.2	687	(((
2.2	688	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	689	)))
2.2	690
28.2	691	(((
2.2	692	Downlink control command:
28.2	693	)))
2.2	694
28.2	695	(((
	696	0x08 command: Poll an uplink with current command set in RS485-BL.
	697	)))
2.2	698
28.2	699	(((
	700	0xA8 command: Send a command to RS485-BL and uplink the output from sensors.
29.37	701
	702
28.2	703	)))
2.2	704
28.2	705	=== 3.3.6 Uplink on Interrupt ===
2.2	706
28.2	707	Put the interrupt sensor between 3.3v_out and GPIO ext.
2.2	708
28.2	709	[[image:1653273818896-432.png]]
2.2	710
29.38	711
28.4	712	(((
2.2	713	AT+INTMOD=0 Disable Interrupt
28.4	714	)))
2.2	715
28.4	716	(((
2.2	717	AT+INTMOD=1 Interrupt trigger by rising or falling edge.
28.4	718	)))
2.2	719
28.4	720	(((
2.2	721	AT+INTMOD=2 Interrupt trigger by falling edge. ( Default Value)
28.4	722	)))
2.2	723
28.4	724	(((
2.2	725	AT+INTMOD=3 Interrupt trigger by rising edge.
29.38	726
	727
28.4	728	)))
2.2	729
28.2	730	== 3.4 Uplink Payload ==
2.2	731
28.3	732	(% border="1" style="background-color:#4f81bd; color:white; width:850px" %)
	733	\|Size(bytes)\|(% style="width:130px" %)2\|(% style="width:93px" %)1\|(% style="width:509px" %)Length depends on the return from the commands
	734	\|Value\|(% style="width:130px" %)(((
	735	(((
2.2	736	Battery(mV)
28.3	737	)))
2.2	738
28.3	739	(((
2.2	740	&
28.3	741	)))
2.2	742
28.3	743	(((
2.2	744	Interrupt _Flag
28.3	745	)))
	746	)))\|(% style="width:93px" %)(((
2.2	747	PAYLOAD_VER
	748
	749
28.3	750	)))\|(% style="width:509px" %)If the valid payload is too long and exceed the maximum support payload length in server, server will show payload not provided in the LoRaWAN server.
2.2	751
	752	Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors.
	753
29.2	754	(((
29.39	755	{{{function Decoder(bytes, port) {}}}
29.2	756	)))
2.2	757
29.2	758	(((
29.39	759	{{{//Payload Formats of RS485-BL Deceive}}}
29.2	760	)))
2.2	761
29.2	762	(((
29.39	763	{{{return {}}}
29.2	764	)))
2.2	765
29.2	766	(((
29.39	767	{{{ //Battery,units:V}}}
29.2	768	)))
2.2	769
29.2	770	(((
29.39	771	{{{ BatV:((bytes[0]<<8 \| bytes[1])&0x7fff)/1000,}}}
29.2	772	)))
2.2	773
29.2	774	(((
29.39	775	{{{ //GPIO_EXTI }}}
29.2	776	)))
2.2	777
29.2	778	(((
29.39	779	{{{ EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE",}}}
29.2	780	)))
2.2	781
29.2	782	(((
29.39	783	{{{ //payload of version}}}
29.2	784	)))
2.2	785
29.2	786	(((
29.39	787	{{{ Pay_ver:bytes[2],}}}
29.2	788	)))
2.2	789
29.2	790	(((
29.39	791	{{{ }; }}}
29.2	792	)))
2.2	793
29.2	794	(((
40.19	795	}
29.39	796
	797
29.2	798	)))
2.2	799
29.2	800	(((
2.2	801	TTN V3 uplink screen shot.
29.2	802	)))
2.2	803
29.2	804	[[image:1653274001211-372.png\|\|height="192" width="732"]]
2.2	805
29.39	806
29.3	807	== 3.5 Configure RS485-BL via AT or Downlink ==
2.2	808
29.40	809	User can configure RS485-BL via AT Commands or LoRaWAN Downlink Commands
2.2	810
	811	There are two kinds of Commands:
	812
40.8	813	* (% 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	814
29.40	815	* (% style="color:#4f81bd" %)Sensor Related Commands(%%): These commands are special designed for RS485-BL. User can see these commands below:
2.2	816
29.40	817	=== 3.5.1 Common Commands: ===
2.2	818
29.40	819	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	820
29.40	821
	822	=== 3.5.2 Sensor related commands: ===
	823
2.2	824
29.41	825	==== Choose Device Type (RS485 or TTL) ====
	826
2.2	827	RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect.
	828
29.42	829	* AT Command
2.2	830
30.3	831	(% class="box infomessage" %)
	832	(((
2.2	833	AT+MOD=1 ~/~/ Set to support RS485-MODBUS type sensors. User can connect multiply RS485 , Modbus sensors to the A / B pins.
30.3	834	)))
2.2	835
30.3	836	(% class="box infomessage" %)
	837	(((
2.2	838	AT+MOD=2 ~/~/ Set to support TTL Level sensors, User can connect one TTL Sensor to the TXD/RXD/GND pins.
30.3	839	)))
2.2	840
	841
29.42	842	* Downlink Payload
2.2	843
29.42	844	0A aa ~-~-> same as AT+MOD=aa
2.2	845
	846
	847
29.43	848	==== RS485 Debug Command (AT+CFGDEV) ====
2.2	849
	850	This command is used to configure the RS485 or TTL sensors; they won’t be used during sampling.
	851
29.43	852	* AT Command
2.2	853
30.3	854	(% class="box infomessage" %)
	855	(((
	856	AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
	857	)))
2.2	858
	859	m: 0: no CRC; 1: add CRC-16/MODBUS in the end of this command.
	860
	861
29.43	862	* Downlink Payload
2.2	863
	864	Format: A8 MM NN XX XX XX XX YY
	865
	866	Where:
	867
	868	* MM: 1: add CRC-16/MODBUS ; 0: no CRC
	869	* NN: The length of RS485 command
	870	* XX XX XX XX: RS485 command total NN bytes
	871	* 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
	872
	873	Example 1:
	874
	875	To connect a Modbus Alarm with below commands.
	876
30.2	877	* 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	878
30.2	879	* 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	880
	881	So if user want to use downlink command to control to RS485 Alarm, he can use:
	882
30.2	883	(% style="color:#037691" %)A8 01 06 0A 05 00 04 00 01 00(%%): to activate the RS485 Alarm
2.2	884
30.2	885	(% style="color:#037691" %)A8 01 06 0A 05 00 04 00 00 00(%%): to deactivate the RS485 Alarm
2.2	886
	887	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.
	888
	889
	890	Example 2:
	891
	892	Check TTL Sensor return:
	893
30.2	894	[[image:1654132684752-193.png]]
2.2	895
	896
	897
40.10	898
30.3	899	==== Set Payload version ====
2.2	900
	901	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.
	902
30.3	903	* AT Command:
2.2	904
30.3	905	(% class="box infomessage" %)
	906	(((
	907	AT+PAYVER: Set PAYVER field = 1
	908	)))
2.2	909
	910
30.3	911	* Downlink Payload:
2.2	912
30.4	913	0xAE 01 ~-~-> Set PAYVER field = 0x01
2.2	914
30.4	915	0xAE 0F ~-~-> Set PAYVER field = 0x0F
2.2	916
	917
	918
30.4	919	==== Set RS485 Sampling Commands ====
	920
2.2	921	AT+COMMANDx, AT+DATACUTx and AT+SEARCHx
	922
30.5	923	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	924
	925
30.7	926	* AT Command:
2.2	927
30.7	928	(% class="box infomessage" %)
	929	(((
	930	AT+COMMANDx: Configure RS485 read command to sensor.
	931	)))
2.2	932
30.7	933	(% class="box infomessage" %)
	934	(((
	935	AT+DATACUTx: Configure how to handle return from RS485 devices.
	936	)))
2.2	937
30.7	938	(% class="box infomessage" %)
	939	(((
	940	AT+SEARCHx: Configure search command
	941	)))
2.2	942
	943
30.7	944	* Downlink Payload:
2.2	945
30.7	946	0xAF downlink command can be used to set AT+COMMANDx or AT+DATACUTx.
2.2	947
30.7	948	(% style="color:red" %)Note(%%): if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink.
2.2	949
	950	Format: AF MM NN LL XX XX XX XX YY
	951
	952	Where:
	953
	954	* MM: the ATCOMMAND or AT+DATACUT to be set. Value from 01 ~~ 0F,
30.7	955	* NN: 0: no CRC; 1: add CRC-16/MODBUS ; 2: set the AT+DATACUT value.
	956	* LL: The length of AT+COMMAND or AT+DATACUT command
2.2	957	* XX XX XX XX: AT+COMMAND or AT+DATACUT command
30.7	958	* 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	959
30.7	960	Example:
2.2	961
30.7	962	(% 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	963
30.7	964	(% 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	965
30.7	966	(% 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	967
	968
30.8	969	0xAB downlink command can be used for set AT+SEARCHx
2.2	970
30.8	971	Example: AB aa 01 03 xx xx xx (03 here means there are total 3 bytes after 03) So
2.2	972
	973	* AB aa 01 03 xx xx xx same as AT+SEARCHaa=1,xx xx xx
	974	* 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
	975
	976	AB aa 02 03 xx xx xx 02 yy yy same as AT+SEARCHaa=2,xx xx xx+yy yy
	977
	978
30.8	979
31.2	980	==== Fast command to handle MODBUS device ====
2.2	981
	982	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]].
	983
	984	This command is valid since v1.3 firmware version
	985
	986
31.2	987	AT+MBFUN has only two value:
2.2	988
32.2	989	* AT+MBFUN=1: Enable Modbus reading. And get response base on the MODBUS return
2.2	990
	991	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.
	992
32.2	993	* AT+MBFUN=0: Disable Modbus fast reading.
2.2	994
31.2	995	Example:
	996
2.2	997	* AT+MBFUN=1 and AT+DATACUT1/AT+DATACUT2 are not configure (0,0,0).
	998	* 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.
	999	* 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.
	1000
31.2	1001	[[image:1654133913295-597.png]]
2.2	1002
	1003
32.2	1004	[[image:1654133954153-643.png]]
2.2	1005
	1006
32.3	1007	* Downlink Commands:
2.2	1008
32.3	1009	A9 aa ~-~-> Same as AT+MBFUN=aa
2.2	1010
	1011
32.3	1012
32.4	1013	==== RS485 command timeout ====
2.2	1014
	1015	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.
	1016
	1017	Default value: 0, range: 0 ~~ 5 seconds
	1018
	1019
32.4	1020	* AT Command:
2.2	1021
32.4	1022	(% class="box infomessage" %)
	1023	(((
	1024	AT+CMDDLaa=hex(bb cc)
	1025	)))
2.2	1026
32.5	1027	Example:
2.2	1028
	1029	AT+CMDDL1=1000 to send the open time to 1000ms
	1030
	1031
32.4	1032	* Downlink Payload:
2.2	1033
	1034	0x AA aa bb cc
	1035
	1036	Same as: AT+CMDDLaa=hex(bb cc)
	1037
32.5	1038	Example:
2.2	1039
32.5	1040	0xAA 01 03 E8 ~-~-> Same as AT+CMDDL1=1000 ms
2.2	1041
	1042
	1043
32.6	1044	==== Uplink payload mode ====
	1045
2.2	1046	Define to use one uplink or multiple uplinks for the sampling.
	1047
32.7	1048	The use of this command please see: [[Compose Uplink payload>>\|\|anchor="H3.3.4Composetheuplinkpayload"]]
2.2	1049
32.8	1050	* AT Command:
2.2	1051
32.8	1052	(% class="box infomessage" %)
	1053	(((
	1054	AT+DATAUP=0
	1055	)))
2.2	1056
32.8	1057	(% class="box infomessage" %)
	1058	(((
	1059	AT+DATAUP=1
	1060	)))
2.2	1061
	1062
32.8	1063	* Downlink Payload:
2.2	1064
32.9	1065	0xAD 00 ~-~-> Same as AT+DATAUP=0
2.2	1066
32.9	1067	0xAD 01 ~-~-> Same as AT+DATAUP=1
2.2	1068
	1069
	1070
40.20	1071
32.9	1072	==== Manually trigger an Uplink ====
	1073
2.2	1074	Ask device to send an uplink immediately.
	1075
32.10	1076	* Downlink Payload:
2.2	1077
32.10	1078	0x08 FF, RS485-BL will immediately send an uplink.
2.2	1079
	1080
	1081
40.21	1082
32.10	1083	==== Clear RS485 Command ====
	1084
2.2	1085	The AT+COMMANDx and AT+DATACUTx settings are stored in special location, user can use below command to clear them.
	1086
	1087
33.2	1088	* AT Command:
2.2	1089
33.2	1090	(% 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	1091
6.2	1092	Example screen shot after clear all RS485 commands.
2.2	1093
	1094
	1095	The uplink screen shot is:
	1096
33.2	1097	[[image:1654134704555-320.png]]
2.2	1098
	1099
33.2	1100	* Downlink Payload:
2.2	1101
33.2	1102	0x09 aa bb same as AT+CMDEAR=aa,bb
2.2	1103
	1104
	1105
33.2	1106	==== Set Serial Communication Parameters ====
	1107
2.2	1108	Set the Rs485 serial communication parameters:
	1109
33.2	1110	* AT Command:
2.2	1111
	1112	Set Baud Rate:
	1113
33.2	1114	(% class="box infomessage" %)
	1115	(((
	1116	AT+BAUDR=9600 ~/~/ Options: (1200,2400,4800,14400,19200,115200)
	1117	)))
2.2	1118
33.2	1119	Set UART Parity
2.2	1120
33.2	1121	(% class="box infomessage" %)
	1122	(((
	1123	AT+PARITY=0 ~/~/ Option: 0: no parity, 1: odd parity, 2: even parity
	1124	)))
2.2	1125
	1126	Set STOPBIT
	1127
33.2	1128	(% class="box infomessage" %)
	1129	(((
	1130	AT+STOPBIT=0 ~/~/ Option: 0 for 1bit; 1 for 1.5 bit ; 2 for 2 bits
	1131	)))
2.2	1132
	1133
33.2	1134	* Downlink Payload:
2.2	1135
33.2	1136	A7 01 aa bb: Same AT+BAUDR=hex(aa bb)*100
2.2	1137
33.2	1138	Example:
2.2	1139
	1140	* A7 01 00 60 same as AT+BAUDR=9600
	1141	* A7 01 04 80 same as AT+BAUDR=115200
	1142
	1143	A7 02 aa: Same as AT+PARITY=aa (aa value: 00 , 01 or 02)
	1144
	1145	A7 03 aa: Same as AT+STOPBIT=aa (aa value: 00 , 01 or 02)
	1146
	1147
	1148
33.2	1149	==== Control output power duration ====
	1150
2.2	1151	User can set the output power duration before each sampling.
	1152
33.3	1153	* AT Command:
2.2	1154
33.3	1155	Example:
2.2	1156
33.3	1157	AT+3V3T=1000 ~/~/ 3V3 output power will open 1s before each sampling.
2.2	1158
33.3	1159	AT+5VT=1000 ~/~/ +5V output power will open 1s before each sampling.
2.2	1160
	1161
33.3	1162	* LoRaWAN Downlink Command:
2.2	1163
33.3	1164	07 01 aa bb Same as AT+5VT=(aa bb)
2.2	1165
33.3	1166	07 02 aa bb Same as AT+3V3T=(aa bb)
2.2	1167
	1168
40.22	1169
33.4	1170	== 3.6 Buttons ==
2.2	1171
33.4	1172	(% border="1" style="background-color:#ffffcc; color:green; width:233px" %)
	1173	\|=(% style="width: 89px;" %)Button\|=(% style="width: 141px;" %)Feature
	1174	\|(% style="width:89px" %)RST\|(% style="width:141px" %)Reboot RS485-BL
2.2	1175
33.4	1176	== 3.7 +3V3 Output ==
2.2	1177
	1178	RS485-BL has a Controllable +3V3 output, user can use this output to power external sensor.
	1179
6.2	1180	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	1181
	1182	The +3V3 output time can be controlled by AT Command.
	1183
	1184
33.4	1185	(% style="color:#037691" %)AT+3V3T=1000
	1186
	1187
2.2	1188	Means set +3v3 valid time to have 1000ms. So, the real +3v3 output will actually have 1000ms + sampling time for other sensors.
	1189
	1190	By default, the AT+3V3T=0. This is a special case, means the +3V3 output is always on at any time
	1191
	1192
33.4	1193	== 3.8 +5V Output ==
2.2	1194
	1195	RS485-BL has a Controllable +5V output, user can use this output to power external sensor.
	1196
6.2	1197	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	1198
	1199	The 5V output time can be controlled by AT Command.
	1200
33.6	1201
33.4	1202	(% style="color:#037691" %)AT+5VT=1000
2.2	1203
33.6	1204
2.2	1205	Means set 5V valid time to have 1000ms. So, the real 5V output will actually have 1000ms + sampling time for other sensors.
	1206
	1207	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.
	1208
	1209
33.4	1210	== 3.9 LEDs ==
2.2	1211
33.6	1212	(% border="1" style="background-color:#ffffcc; color:green; width:332px" %)
	1213	\|=LEDs\|=(% style="width: 274px;" %)Feature
	1214	\|LED1\|(% style="width:274px" %)Blink when device transmit a packet.
2.2	1215
33.4	1216	== 3.10 Switch Jumper ==
2.2	1217
33.8	1218	(% border="1" style="background-color:#ffffcc; color:green; width:515px" %)
	1219	\|=(% style="width: 124px;" %)Switch Jumper\|=(% style="width: 388px;" %)Feature
	1220	\|(% style="width:124px" %)SW1\|(% style="width:388px" %)(((
2.2	1221	ISP position: Upgrade firmware via UART
	1222
	1223	Flash position: Configure device, check running status.
	1224	)))
33.8	1225	\|(% style="width:124px" %)SW2\|(% style="width:388px" %)(((
2.2	1226	5V position: set to compatible with 5v I/O.
	1227
	1228	3.3v position: set to compatible with 3.3v I/O.,
	1229	)))
	1230
33.8	1231	+3.3V: is always ON
2.2	1232
33.8	1233	+5V: Only open before every sampling. The time is by default, it is AT+5VT=0. Max open time. 5000 ms.
2.2	1234
33.8	1235
33.9	1236	= 4. Case Study =
2.2	1237
33.10	1238	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	1239
	1240
33.11	1241	= 5. Use AT Command =
2.2	1242
33.11	1243	== 5.1 Access AT Command ==
2.2	1244
	1245	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.
	1246
34.2	1247	[[image:1654135840598-282.png]]
2.2	1248
	1249
35.2	1250	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	1251
35.2	1252	[[image:1654136105500-922.png]]
2.2	1253
	1254
40.27	1255	More detail AT Command manual can be found at [[AT Command Manual>>\|\|anchor="H3.5ConfigureRS485-BLviaATorDownlink"]]
2.2	1256
	1257
35.2	1258	== 5.2 Common AT Command Sequence ==
2.2	1259
35.2	1260	=== 5.2.1 Multi-channel ABP mode (Use with SX1301/LG308) ===
2.2	1261
	1262	If device has not joined network yet:
	1263
35.4	1264	(% class="box infomessage" %)
	1265	(((
	1266	AT+FDR
	1267	)))
2.2	1268
35.4	1269	(% class="box infomessage" %)
	1270	(((
	1271	AT+NJM=0
	1272	)))
2.2	1273
35.4	1274	(% class="box infomessage" %)
	1275	(((
	1276	ATZ
	1277	)))
2.2	1278
	1279
	1280	If device already joined network:
	1281
35.4	1282	(% class="box infomessage" %)
	1283	(((
	1284	AT+NJM=0
	1285	)))
2.2	1286
35.4	1287	(% class="box infomessage" %)
	1288	(((
	1289	ATZ
	1290	)))
2.2	1291
	1292
35.4	1293	=== 5.5.2 Single-channel ABP mode (Use with LG01/LG02) ===
	1294
	1295
35.5	1296	(% style="background-color:#dcdcdc" %)AT+FDR (%%) Reset Parameters to Factory Default, Keys Reserve
2.2	1297
35.5	1298	(% style="background-color:#dcdcdc" %)AT+NJM=0 (%%)Set to ABP mode
2.2	1299
35.5	1300	(% style="background-color:#dcdcdc" %)AT+ADR=0 (%%)Set the Adaptive Data Rate Off
2.2	1301
35.5	1302	(% style="background-color:#dcdcdc" %)AT+DR=5 (%%)Set Data Rate
2.2	1303
35.5	1304	(% style="background-color:#dcdcdc" %)AT+TDC=60000 (%%) Set transmit interval to 60 seconds
2.2	1305
35.5	1306	(% style="background-color:#dcdcdc" %)AT+CHS=868400000(%%) Set transmit frequency to 868.4Mhz
2.2	1307
35.5	1308	(% style="background-color:#dcdcdc" %)AT+RX2FQ=868400000 (%%) Set RX2Frequency to 868.4Mhz (according to the result from server)
2.2	1309
35.5	1310	(% style="background-color:#dcdcdc" %)AT+RX2DR=5 (%%) Set RX2DR to match the downlink DR from server. see below
2.2	1311
35.5	1312	(% 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	1313
35.5	1314	(% style="background-color:#dcdcdc" %)ATZ (%%) Reset MCU
2.2	1315
36.3	1316
35.5	1317	(% style="color:red" %)Note:
2.2	1318
36.2	1319	(% style="color:red" %)1. Make sure the device is set to ABP mode in the IoT Server.
	1320	2. Make sure the LG01/02 gateway RX frequency is exactly the same as AT+CHS setting.
	1321	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.
	1322	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	1323
36.2	1324	[[image:1654136435598-589.png]]
2.2	1325
	1326
37.2	1327	= 6. FAQ =
2.2	1328
37.2	1329	== 6.1 How to upgrade the image? ==
	1330
2.2	1331	The RS485-BL LoRaWAN Controller is shipped with a 3.5mm cable, the cable is used to upload image to RS485-BL to:
	1332
	1333	* Support new features
	1334	* For bug fix
	1335	* Change LoRaWAN bands.
	1336
	1337	Below shows the hardware connection for how to upload an image to RS485-BL:
	1338
37.2	1339	[[image:1654136646995-976.png]]
2.2	1340
	1341	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]].
	1342
	1343	Step2: Download the [[LT Image files>>url:http://www.dragino.com/downloads/index.php?dir=LT_LoRa_IO_Controller/LT33222-L/image/]].
	1344
	1345	Step3: Open flashloader; choose the correct COM port to update.
	1346
38.2	1347	[[image:image-20220602102605-1.png]]
2.2	1348
	1349
39.2	1350	[[image:image-20220602102637-2.png]]
2.2	1351
	1352
40.2	1353	[[image:image-20220602102715-3.png]]
39.2	1354
	1355
	1356
40.3	1357	== 6.2 How to change the LoRa Frequency Bands/Region? ==
39.2	1358
40.32	1359	(((
40.3	1360	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	1361	)))
2.2	1362
	1363
	1364
40.3	1365	== 6.3 How many RS485-Slave can RS485-BL connects? ==
2.2	1366
40.31	1367	(((
40.3	1368	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	1369	)))
2.2	1370
	1371
	1372
40.3	1373	= 7. Trouble Shooting =
2.2	1374
	1375
40.3	1376	== 7.1 Downlink doesn’t work, how to solve it? ==
2.2	1377
40.3	1378	Please see this link for debug: [[LoRaWAN Communication Debug>>doc:Main.LoRaWAN Communication Debug.WebHome]]
2.2	1379
	1380
40.3	1381	== 7.2 Why I can’t join TTN V3 in US915 /AU915 bands? ==
2.2	1382
40.3	1383	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	1384
	1385
40.3	1386	= 8. Order Info =
2.2	1387
40.5	1388	(% style="color:blue" %)Part Number: RS485-BL-XXX
2.2	1389
40.5	1390	(% style="color:blue" %)XXX:
2.2	1391
40.5	1392	* (% style="color:blue" %)EU433(%%): frequency bands EU433
	1393	* (% style="color:blue" %)EU868(%%): frequency bands EU868
	1394	* (% style="color:blue" %)KR920(%%): frequency bands KR920
	1395	* (% style="color:blue" %)CN470(%%): frequency bands CN470
	1396	* (% style="color:blue" %)AS923(%%): frequency bands AS923
	1397	* (% style="color:blue" %)AU915(%%): frequency bands AU915
	1398	* (% style="color:blue" %)US915(%%): frequency bands US915
	1399	* (% style="color:blue" %)IN865(%%): frequency bands IN865
	1400	* (% style="color:blue" %)RU864(%%): frequency bands RU864
	1401	* (% style="color:blue" %)KZ865(%%): frequency bands KZ865
2.2	1402
40.3	1403	= 9. Packing Info =
2.2	1404
40.4	1405	(((
2.2	1406	Package Includes:
40.4	1407	)))
2.2	1408
40.4	1409	* (((
	1410	RS485-BL x 1
	1411	)))
	1412	* (((
	1413	Stick Antenna for LoRa RF part x 1
	1414	)))
	1415	* (((
	1416	Program cable x 1
	1417	)))
2.2	1418
40.4	1419	(((
2.2	1420	Dimension and weight:
40.4	1421	)))
2.2	1422
40.4	1423	* (((
	1424	Device Size: 13.5 x 7 x 3 cm
	1425	)))
	1426	* (((
	1427	Device Weight: 105g
	1428	)))
	1429	* (((
	1430	Package Size / pcs : 14.5 x 8 x 5 cm
	1431	)))
	1432	* (((
	1433	Weight / pcs : 170g
40.6	1434
	1435
40.4	1436	)))
2.2	1437
40.3	1438	= 10. Support =
	1439
40.30	1440	* (((
	1441	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.
	1442	)))
	1443	* (((
	1444	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]]
	1445	)))

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

Applications