Wiki source code of Communicate with ABP End Node without LoRaWAN Network Server --- LG308

Version 14.5 by Xiaoling on 2022/06/01 11:12

version	line-number	content
1.5	1	Contents:
1.1	2
1.5	3	{{toc/}}
1.1	4
1.5	5
1.3	6	= 1. Introduction =
	7
1.2	8	The Dragino LoRaWAN gateway can commuicate with LoRaWAN ABP End Node without the need of LoRaWAN server. It can be used in some cases such as:
1.1	9
1.2	10	* No internet connection.
14.2	11	* User wants to get data forward in gateway and forward to their server base on MQTT/HTTP, etc. (Combine ABP communication method and [[MQTT forward together>>MQTT Forward Instruction]]).
1.1	12
1.7	13	(((
1.13	14	The basic of this feature is the decoding of (% style="color:red" %)LoRaWAN ABP End Node(%%). Requirements:
1.7	15	)))
1.1	16
1.2	17	1. LoRaWAN End Node in ABP mode. Make sure your end node works in this mode. End node most are default set to OTAA mode
	18	1. LoRaWAN Gateway model: [[LPS8>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/148-lps8.html]], [[LG308>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/140-lg308.html]], [[DLOS8>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/160-dlos8.html]] ,[[LIG16>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/171-lig16.html]]
1.13	19	1. Firmware version for below instruction:[[(% style="color:purple" %)Since LG02_LG08~~-~~-build-v5.4.1593400722-20200629-1120>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]](%%)
1.1	20
14.5	21
	22
1.4	23	= 2. How it works =
1.1	24
1.4	25
1.13	26	(% style="color:#037691" %)Video Instruction(%%): [[https:~~/~~/youtu.be/ZBjXwmp7rwM>>url:https://youtu.be/ZBjXwmp7rwM]]
1.4	27
1.14	28
1.2	29	Assume we have the LoRaWAN tracker LGT92 which works in ABP mode and US915 band. It has below keys:
1.1	30
1.8	31	(% class="box infomessage" %)
	32	(((
	33	AT+NWKSKEY=72 32 63 95 dd 8f e2 b2 13 66 e4 35 93 8f 55 df
1.2	34	AT+APPSKEY=b3 17 f8 14 7a 43 27 8a 6a 31 c4 47 3d 55 5d 33
	35	AT+DADDR=2602111D
1.8	36	)))
1.1	37
1.8	38	(((
1.2	39	and we have the LG308 works and US915 band and support ABP decryption. User can input these keys in LG308 so the LG308 can communicate with LGT92.
1.8	40	)))
1.2	41
	42	We need to input above keys in LG308 and enable ABP decryption.
	43
3.2	44	[[image:image-20220527161119-1.png]]
1.2	45
	46	Input the ABP keys in LG308
	47
	48
1.3	49	== 2.1 Upstream ==
1.2	50
	51	Now when this End Node (Dev Addr=2602111D) send a uplink packet. When this packet arrive LG308, LG308 will decode it and put the decode data on the file /var/iot/channels/2602111D . So we have this data for further process with other applications in LG308.
	52
1.8	53	(((
1.2	54	We can see the log of LG308 to know this packet arrive
1.8	55	)))
1.2	56
3.2	57	[[image:image-20220527161149-2.png]]
1.2	58
	59	LG308 log by "logread -f" command
	60
	61
	62	The data of End Node is stored in the file /var/iot/channels/2602111D. We can use hexdump command to check it.
	63
1.8	64	(% class="box" %)
	65	(((
	66	root@dragino-1d25dc:~~# hexdump /var/iot/channels/2602111D
3.3	67	0000000 (% style="color:#037691" %)4646 4646 4646 3946 3030 3030 3030 3546(%%) ~-~-> Got RSSI and SNR
	68	0000010 (% style="color:#037691" %)cc0c 0b63 0266 017f ff7f ff00 (%%) ~-~-> Payload
1.2	69	000001c
1.8	70	)))
1.2	71
	72	* RSSI: 4646 4646 4646 3946 = 0xFFFF FF9F : So RSSI = (0xFFFF FF9F - 0x100000000) = -97
	73	* SNR: 3030 3030 3030 3546 = 0x0000 005F = 95, need to divide 10 so SNR is 9.5
	74	* Payload: 0xcc0c 0b63 0266 017f ff7f ff00
	75
1.8	76	(% class="box" %)
	77	(((
3.3	78	(% style="color:red" %)Notice 1(%%): The data file stored in LG308 for the end node is bin file. If the end node sends ASCII string to gateway, the output will as below:
3.6	79	in LGT92, use (% style="color:#037691" %)AT+SEND=12:hello world (%%)to send ASCII string
1.8	80	root@dragino-1d25dc:~~# hexdump /var/iot/channels/2602111D
1.2	81	0000000 4646 4646 4646 3946 3030 3030 3030 3546
1.8	82	0000010 6865 6c6c 6f20 776f 726c 6400 ~-~-> Got ASCII code "hello world"
1.2	83	000001c
1.8	84	)))
1.2	85
1.8	86	(% class="box" %)
	87	(((
3.3	88	(% style="color:#037691" %)Notice 2(%%): The upstream payload length should match the LoRaWAN length requirement (max length depends on Frequency and DR), otherwise the gateway can't decode the payload.
1.8	89	)))
1.2	90
3.4	91
1.3	92	=== 2.2.1 Decode Method ===
1.2	93
3.6	94	The decode methods: (% style="color:#037691" %)ASCII String, Decode_LHT65(%%) doesn't affect how the sensor data is stored, they are to define how should the sensor data to be sent.
1.2	95
	96	For example we have a LHT65 , works in ABP mode and gateway successful get the data, which are:
	97
1.8	98	(% class="box" %)
	99	(((
	100	root@dragino-1baf44:~~# hexdump /var/iot/channels/01826108
1.2	101	0000000 4646 4646 4646 4537 3030 3030 3030 3438
1.8	102	0000010 ccd1 7fff 7fff 017f ff7f ff00
1.2	103	000001c
1.8	104	)))
1.2	105
	106	If we choose ASCII decoder, the MQTT process will send out with mqtt-data:
	107
1.8	108	(% class="box" %)
	109	(((
	110	Sun Sep 27 04:33:16 2020 user.notice root: [IoT.MQTT]:pub_topic[-t]: dragino-1baf44/01826108/data
1.2	111	Sun Sep 27 04:33:16 2020 user.notice root: [IoT.MQTT]:decoder: ASCII
3.6	112	Sun Sep 27 04:33:16 2020 user.notice root: [IoT.MQTT]:mqtt_data[-m]: (% style="color:#037691" %)ffffffe700000048ccd17fff7fff017fff7fff00
1.8	113	)))
1.2	114
	115	If we choose Decode_LHT65, the MQTT process will send out with mqtt-data
	116
1.8	117	(% class="box" %)
	118	(((
	119	Sun Sep 27 04:36:45 2020 user.notice root: [IoT.MQTT]:pub_topic[-t]: dragino-1baf44/01826108/data
1.2	120	Sun Sep 27 04:36:45 2020 user.notice root: [IoT.MQTT]:decoder: Dragino_LHT65
3.6	121	Sun Sep 27 04:36:45 2020 user.notice root: [IoT.MQTT]:mqtt_data[-m]:** (% style="color:#037691" %){"Hum_SHT":32.7,"BatV":3.281,"TempC_DS":32.9,
	122	"EXT":"Temperature Sensor","RSSI":-24,"TempC_SHT":85.0,"SNR":8.2,"ext_sensor":0}(%%)**
1.8	123	)))
1.2	124
	125	Above scripts are store in /etc/lora/decoder/. User can put their scripts here and select it in the UI.
	126
	127
1.3	128	=== 2.2.2 How to Decode My End Node ===
1.2	129
	130	1/ Configure the ABP keys for your end node in the gateway. enable ABP decode in Web UI
	131
	132	2/ Don't choose MQTT service, use LoRaWAN.
	133
	134	3/ When your end node send a message to the gateway, there will be a file store in /var/iot/channels. full path should be /var/iot/channels/END_NODE_DEV_ADDR
	135
	136	4/ Use the /etc/lora/decoder/Dragino_LHT65 as template to decode your payload. This script is written in Lua language. User can manually call this script when you see the data file in /var/iot/channels by running:
	137
	138	{{{/etc/lora/decoder/Dragino_LHT65 END_NODE_DEV_ADDR
	139	}}}
	140
	141	5/ What you see as output is the MQTT data device will upload, user's end node has different payload compare with LHT65, most properly this file will report with error. User need to modify to match the actual payload. Some notice:
	142
	143	* RSSI and SNR are added when gateway receive the packet, so there is always this field.
	144	* If you rename the file, please make it executable.
	145	* See this link for lua.bit module: [[http:~~/~~/luaforge.net/projects/bit/>>url:http://luaforge.net/projects/bit/]]
	146	* Lua json module: [[http:~~/~~/json.luaforge.net/>>url:http://json.luaforge.net/]]
	147	* the last line return is what will be used for MQTT
	148	* User can use other language ,not limited to Lua, just make sure the return is what you want to send.
	149
3.9	150
1.3	151	== 2.2 Downstream ==
1.2	152
	153	In LG308, we can create a file in the directory /var/iot/push for downstream purpose. We recommend using each command to generate this file. This file will be used for transmission and auto-deleted after used
	154
	155	The file should use below format:
	156
3.7	157	(% style="color:#037691" %)dev_addr,imme/time,txt/hex,payload
1.2	158
	159	Since fimware > Dragino-v2 lgw-5.4.1608518541 . Support more option
	160
3.7	161	(% style="color:#037691" %)dev_addr,imme/time,txt/hex,payload,txpw,txbw,SF,frequency,rxwindow
1.2	162
	163	* dev_addr: Inptu the device address
	164	* imme/time:
	165	** imme: send downstream immediately,For Class C end node.
	166	** time: send downstream after receive device's uplink. For Class A end node
	167	* txt/hex:
	168	** txt: send payload in ASCII
	169	** hex: send payload in HEX
	170	* payload: payload to be sent, payload lenght should match the LoRaWAN protocol requirement.
	171	* txpw: Transmit Power. example: 20
	172	* txbw: bandwidth:
	173	** 1: 500 kHz
	174	** 2: 250 kHz
	175	** 3: 125 kHz
	176	** 4: 62.5 kHz
	177	* SF: Spreading Factor : SF7/SF8/SF9/SF10/SF11/SF12
	178	* Frequency: Transmit Frequency: example: 923300000
	179	* rxwindow: transmit on Rx1Window or Rx2Window.
	180
	181	Completely exmaple:
	182
	183	* Old version: echo 018193F4,imme,hex,0101 > /var/iot/push/test
	184	* New version: echo 018193F4,imme,hex,0101,20,1,SF12,923300000,2 > /var/iot/push/test
	185
3.7	186	(% style="color:#037691" %)Downstream Frequency
	187
1.2	188	The LG308 will use the RX2 window info to send the downstream payload, use the default LoRaWAN settings, as below:
	189
	190	* EU868: 869.525Mhz, DR0(SF12BW125)
	191	* US915: 923.3Mhz, SF12 BW500
	192	* CN470: 505.3Mhz, SF12 BW125
	193	* AU915: 923.3Mhz, SF12 BW500
	194	* AS923: 923.2Mhz, SF10 BW125
	195	* KR920: 921.9Mhz, SF12 BW125
	196	* IN865: 866.55Mhz, SF10 BW125
	197	* RU864: 869.1Mhz, SF12 BW125
	198
3.6	199	(% style="color:#037691" %)Examples:
1.2	200
1.10	201	(% class="box" %)
	202	(((
	203	we can use echo command to create files in LG308 for downstream.
	204	root@dragino-1d25dc:~~# echo 2602111D,time,hex,12345678 > /var/iot/push/test
	205	)))
1.2	206
1.10	207	(% class="box" %)
	208	(((
	209	1) From logread -f of gateway, we can see it has been added as pedning.
	210	lora_pkt_fwd[4286]: INFO~~ [DNLK]Looking file : test
	211	lora_pkt_fwd[4286]: INFO~~ [DNLK]devaddr:2602111D, txmode:time, pdfm:hex, size:4, payload1:4Vx,payload_hex:77C1BB90
	212	lora_pkt_fwd[4286]: INFO~~ [DNLK] DNLINK PENDING!(1 elems).
	213	)))
1.2	214
1.10	215	(% class="box" %)
	216	(((
	217	2) When there is an upstrea from end node, this downstream will be sent and shows:
1.2	218	lora_pkt_fwd[4286]: INFO: tx_start_delay=1497 (1497.000000) - (1497, bw_delay=0.000000, notch_delay=0.000000)
	219	lora_pkt_fwd[4286]: [LGWSEND]lgw_send done: count_us=3537314420, freq=923300000, size=17
1.10	220	)))
1.2	221
1.10	222	(% class="box" %)
	223	(((
	224	3) and the end node will got:
	225	[5764825]~~~~* UpLinkCounter= 98 ~~~~*
1.2	226	[5764827]TX on freq 905300000 Hz at DR 0
	227	Update Interval: 60000 ms
	228	[5765202]txDone
	229	[5766193]RX on freq 927500000 Hz at DR 10
	230	[5766225]rxTimeOut
	231	[5767205]RX on freq 923300000 Hz at DR 8
	232	[5767501]rxDone
	233	Rssi= -41
	234	Receive data
3.8	235	(% style="color:#037691" %)2:12345678 (%%) ~-~-> Hex
1.10	236	)))
1.2	237
1.10	238	(% class="box" %)
	239	(((
	240	4) If we use the command "echo 2602111D,time,txt,12345678 > /var/iot/push/test" for downstream, the end node will got:
	241	[5955877]~~~~* UpLinkCounter= 102 ~~~~*
1.2	242	[5955879]TX on freq 904100000 Hz at DR 0
	243	Update Interval: 60000 ms
	244	[5956254]txDone
	245	[5957246]RX on freq 923900000 Hz at DR 10
	246	[5957278]rxTimeOut
	247	[5958257]RX on freq 923300000 Hz at DR 8
	248	[5958595]rxDone
	249	Rssi= -37
	250	Receive data
3.8	251	(% style="color:#037691" %)2:3132333435363738(%%) ~-~-> ASCII string "12345678"
1.10	252	)))
1.2	253
3.8	254
1.3	255	= 3. Example 1: Communicate with LT-22222-L =
1.2	256
	257	Script can be download from: [[Example Script 1>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/customized_script/&file=talk_to_lt-22222-l_v0.1.sh]]
	258
1.10	259	(% class="box" %)
	260	(((
	261	#!/bin/sh
1.2	262	# This scripts shows how to use LPS8/LG308/DLOS8 to communicate with two LoRaWAN End Nodes, without the use of internet or LoRaWAN server
	263	#
1.10	264	# Hardware Prepare:
	265	# 1. LT-22222-L x 2, both are configured to work in
	266	# a) Class C ;
	267	# b) ABP Mode ;
1.2	268	# c) AT+Mod=1
1.10	269	# 2. LPS8,
	270	# a) Firmware version >
	271	# b) Input the LT-22222-L keys in LPS so LPS8 can talk with them.
	272	# c) Lorawan server choose built-in
	273	# d) in Custom page, select custom script to point to this script. (put this script in /etc/iot/scripts directory)
1.2	274	#
1.10	275	# How it works?
	276	# a) Devices 1 sends a uplink payload to LPS8. LPS8 will get the DI1 and DI2 info from the payload
	277	# b) LPS8 will send a message to Device 2 to set the Device2 DO1 = Device1 DI1, and Device DO2 = Device DI2.
	278	# c) Device2 will change DO1 and DO2 to according to the message from LPS8, and send back a message to LPS8 with the its DO1
	279	# and DO2 value. LPS8 will ask Device1 to change its DO1 to same as Device 2, and change the DO2 to the same as Device 2.
	280	# ( The purpose of this step is to show that the Device2 has already do the change there).
	281	#
	282	# For example: If current status of Device1 and Device2 leds shows:
	283	# Device1: DI1: ON, DI2: ON , DO1: OFF, DO2: OFF
	284	# Device2: DI1: OFF, DI2: OFF , DO1: OFF, DO2: OFF
	285	#
	286	# Step2 will cause below change:
	287	# Device1: DI1: ON, DI2: ON , DO1: OFF, DO2: OFF
	288	# Device2: DI1: OFF, DI2: OFF , DO1: ON, DO2: ON
	289	#
	290	# Step3 will cause below change:
	291	# Device1: DI1: ON, DI2: ON , DO1: ON, DO2: ON
	292	# Device2: DI1: OFF, DI2: OFF , DO1: ON, DO2: ON
	293	# So if a person is in the Device 1 location, he can check if the DO LED match DI LEDs on Device 1 to confirm
	294	# whether the Device 2 has been changed.
	295	)))
1.2	296
	297	~1. Input keys
	298
5.2	299	[[image:image-20220527162450-3.png]]
1.2	300
	301	Input Keys in LPS8
	302
5.2	303
1.2	304	2. Make sure the LPS8 and LT use the same frequency bands, choose EU868 in this test.
	305
	306	3. Choose Built-in server
	307
5.2	308	[[image:image-20220527162518-4.png]]
1.2	309
	310	Choose Built-in server
	311
5.2	312
1.2	313	4. Run the script.
	314
7.2	315	[[image:image-20220527162552-5.png]]
1.2	316
	317	Run the script
	318
7.2	319
1.2	320	5. Output:
	321
7.2	322	[[image:image-20220527162619-6.png]]
1.2	323
	324	Output from LPS8
	325
	326
1.3	327	= 4. Example 2: Communicate to TCP Server =
1.2	328
10.2	329	[[image:image-20220527162648-7.png]]
1.2	330
	331	Network Structure
	332
	333
	334	Full instruction video inlcude how to write scripts to fit server needed is here:
	335
	336
10.2	337	(% style="color:#037691" %)Video Instruction(%%): [[https:~~/~~/youtu.be/-nevW6U2TsE>>url:https://youtu.be/-nevW6U2TsE]]
1.2	338
	339
10.2	340	(% style="color:red" %)Note: Firmware version must be higher than lgw-5.4.1607519907
	341
1.2	342	Assume we already set up ABP keys in the gateway:
	343
10.2	344	[[image:image-20220527162852-8.png]]
1.2	345
	346	Input Keys in LPS8
	347
10.2	348
1.2	349	run socket tool in PC
	350
10.2	351	[[image:image-20220527163028-9.png]]
1.2	352
10.2	353
1.2	354	Socket tool
	355
	356
	357	Input Server address and port
	358
11.2	359	[[image:image-20220527163106-10.png]]
1.2	360
	361	Input Server address and port
	362
	363
	364	See value receive in socket tool. :
	365
12.2	366	[[image:image-20220527163144-11.png]]
1.2	367
	368	value receive in socket tool
	369
	370	If user want to modify the TCP connection method. He can refer: [[https:~~/~~/github.com/dragino/dragino-packages/blob/lg02/haserl-ui/root/usr/bin/tcp_process.sh>>url:https://github.com/dragino/dragino-packages/blob/lg02/haserl-ui/root/usr/bin/tcp_process.sh]]. Same script is on /usr/bin of gateway.

Wiki source code of Communicate with ABP End Node without LoRaWAN Network Server --- LG308

Applications

Navigation