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

Version 29.14 by Xiaoling on 2022/06/01 18:02

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

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

Applications