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

Version 31.2 by Xiaoling on 2022/05/23 09:47

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

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

Applications

Navigation