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

Version 16.8 by Xiaoling on 2022/07/22 11:46

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