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

Version 19.2 by Xiaoling on 2022/09/17 16:42

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