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

Last modified by Xiaoling on 2023/04/20 18:14

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