Wiki source code of RS485-LN – RS485 to LoRaWAN Converter

Version 32.13 by Xiaoling on 2022/06/02 15:26

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

Wiki source code of RS485-LN – RS485 to LoRaWAN Converter

Applications

Navigation