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

Version 29.9 by Xiaoling on 2022/06/01 18:01

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

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

Applications