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

Version 15.6 by Xiaoling on 2022/05/19 17:59

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

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

Applications

Navigation