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

Version 40.8 by Xiaoling on 2022/06/06 09:17

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

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

Applications