Changes for page Communicate with ABP End Node without LoRaWAN Network Server --- LG308

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

From version < 19.1 >

edited by Xiaoye
on 2022/08/02 11:54

To version < 12.1 >

edited by Xiaoling
on 2022/05/27 16:31

Change comment: Uploaded new attachment "image-20220527163144-11.png", version {1}

Raw
Rendered

Summary

Page properties (2 modified, 0 added, 0 removed)
Attachments (0 modified, 0 added, 2 removed)
- image-20220722115133-1.png
- image-20220722115213-2.png

Details

Page properties

Author

@@ -1,1 +1,1 @@
--XWiki.Xiaoye
++XWiki.Xiaoling

Content

@@ -1,16 +1,14 @@
--**Table of Contents:**
++     **Contents:**
  {{toc/}}
--
  = 1. Introduction =
--
  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:
  * No internet connection.
--* 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]]).
++* 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>>url:https://wiki.dragino.com/index.php/MQTT_Forward_Instruction]]).
  (((
  The basic of this feature is the decoding of (% style="color:red" %)**LoRaWAN ABP End Node**(%%). Requirements:
@@ -20,8 +20,6 @@
 . 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]]
 . 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/]](%%)**
--
--
  = 2. How it works =
@@ -32,15 +32,13 @@
  (% class="box infomessage" %)
  (((
--**AT+NWKSKEY=72 32 63 95 dd 8f e2 b2 13 66 e4 35 93 8f 55 df
++AT+NWKSKEY=72 32 63 95 dd 8f e2 b2 13 66 e4 35 93 8f 55 df
  AT+APPSKEY=b3 17 f8 14 7a 43 27 8a 6a 31 c4 47 3d 55 5d 33
--AT+DADDR=2602111D**
++AT+DADDR=2602111D
  )))
  (((
  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.
--
--
  )))
  We need to input above keys in LG308 and enable ABP decryption.
@@ -50,10 +50,8 @@
  Input the ABP keys in LG308
--
  == 2.1 Upstream ==
--
  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,7 +62,7 @@
  [[image:image-20220527161149-2.png]]
--LG308 log by "(% style="color:red" %)**logread -f**" (%%)command
++LG308 log by "logread -f" command
  The data of End Node is stored in the file /var/iot/channels/2602111D. We can use hexdump command to check it.
@@ -75,11 +75,10 @@
 c
  )))
--* **RSSI**: 4646 4646 4646 3946 = 0xFFFF FF9F : So RSSI = (0xFFFF FF9F - 0x100000000) = -97
--* **SNR**: 3030 3030 3030 3546 = 0x0000 005F = 95, need to divide 10 so SNR is 9.5
--* **Payload**: 0xcc0c 0b63 0266 017f ff7f ff00
++* RSSI: 4646 4646 4646 3946 = 0xFFFF FF9F : So RSSI = (0xFFFF FF9F - 0x100000000) = -97
++* SNR: 3030 3030 3030 3546 = 0x0000 005F = 95, need to divide 10 so SNR is 9.5
++* Payload: 0xcc0c 0b63 0266 017f ff7f ff00
--
  (% class="box" %)
  (((
  (% 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:
@@ -90,17 +90,14 @@
 c
  )))
--
  (% class="box" %)
  (((
--(% 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.
++(% 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.
  )))
--
  === 2.2.1 Decode Method ===
--
  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.
  For example we have a LHT65 , works in ABP mode and gateway successful get the data, which are:
@@ -113,7 +113,6 @@
 c
  )))
--
  If we choose ASCII decoder, the MQTT process will send out with mqtt-data:
  (% class="box" %)
@@ -123,7 +123,6 @@
  Sun Sep 27 04:33:16 2020 user.notice root: [IoT.MQTT]:mqtt_data[-m]: (% style="color:#037691" %)**ffffffe700000048ccd17fff7fff017fff7fff00**
  )))
--
  If we choose Decode_LHT65, the MQTT process will send out with mqtt-data
  (% class="box" %)
@@ -137,27 +137,21 @@
  Above scripts are store in /etc/lora/decoder/. User can put their scripts here and select it in the UI.
--
  === 2.2.2 How to Decode My End Node ===
++1/ Configure the ABP keys for your end node in the gateway. enable ABP decode in Web UI
--**1.** Configure the ABP keys for your end node in the gateway. enable ABP decode in Web UI
++2/ Don't choose MQTT service, use LoRaWAN.
--**2. **Don't choose MQTT service, use LoRaWAN.
++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
--**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
++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:
--**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:
--
  {{{/etc/lora/decoder/Dragino_LHT65 END_NODE_DEV_ADDR
  }}}
--**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.
++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:
--
--(% style="color:red" %)
--**Some notice:**
--
  * RSSI and SNR are added when gateway receive the packet, so there is always this field.
  * If you rename the file, please make it executable.
  * See this link for lua.bit module: [[http:~~/~~/luaforge.net/projects/bit/>>url:http://luaforge.net/projects/bit/]]
@@ -166,10 +166,8 @@
  * User can use other language ,not limited to Lua, just make sure the return is what you want to send.
--
  == 2.2 Downstream ==
--
  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
  The file should use below format:
@@ -180,28 +180,28 @@
  (% style="color:#037691" %)**dev_addr,imme/time,txt/hex,payload,txpw,txbw,SF,frequency,rxwindow**
--* **dev_addr:** Inptu the device address
--* **imme/time:**
++* dev_addr: Inptu the device address
++* imme/time:
  ** imme: send downstream immediately,For Class C end node.
  ** time: send downstream after receive device's uplink. For Class A end node
--* **txt/hex:**
++* txt/hex:
  ** txt: send payload in ASCII
  ** hex: send payload in HEX
--* **payload: **payload to be sent, payload lenght should match the LoRaWAN protocol requirement.
--* **txpw:** Transmit Power. example: 20
--* **txbw:** bandwidth:
++* payload: payload to be sent, payload lenght should match the LoRaWAN protocol requirement.
++* txpw: Transmit Power. example: 20
++* txbw: bandwidth:
  ** 1: 500 kHz
  ** 2: 250 kHz
  ** 3: 125 kHz
  ** 4: 62.5 kHz
--* **SF:** Spreading Factor : SF7/SF8/SF9/SF10/SF11/SF12
--* **Frequency:** Transmit Frequency: example: 923300000
--* **rxwindow:** transmit on Rx1Window or Rx2Window.
++* SF: Spreading Factor : SF7/SF8/SF9/SF10/SF11/SF12
++* Frequency: Transmit Frequency: example: 923300000
++* rxwindow: transmit on Rx1Window or Rx2Window.
--(% style="color:blue" %)**Completely exmaple:**
++Completely exmaple:
--* **Old version:** echo 018193F4,imme,hex,0101 > /var/iot/push/test
--* **New version:** echo 018193F4,imme,hex,0101,20,1,SF12,923300000,2 > /var/iot/push/test
++* Old version: echo 018193F4,imme,hex,0101 > /var/iot/push/test
++* New version: echo 018193F4,imme,hex,0101,20,1,SF12,923300000,2 > /var/iot/push/test
  (% style="color:#037691" %)**Downstream Frequency**
@@ -222,20 +222,26 @@
  (((
  we can use echo command to create files in LG308 for downstream.
  root@dragino-1d25dc:~~# echo 2602111D,time,hex,12345678 > /var/iot/push/test
++)))
--
--**1)** From logread -f of gateway, we can see it has been added as pedning.
++(% class="box" %)
++(((
++1) From logread -f of gateway, we can see it has been added as pedning.
  lora_pkt_fwd[4286]: INFO~~ [DNLK]Looking file : test
  lora_pkt_fwd[4286]: INFO~~ [DNLK]devaddr:2602111D, txmode:time, pdfm:hex, size:4, payload1:4Vx,payload_hex:77C1BB90
  lora_pkt_fwd[4286]: INFO~~ [DNLK] DNLINK PENDING!(1 elems).
++)))
--
--**2)** When there is an upstrea from end node, this downstream will be sent and shows:
++(% class="box" %)
++(((
++2) When there is an upstrea from end node, this downstream will be sent and shows:
  lora_pkt_fwd[4286]: INFO: tx_start_delay=1497 (1497.000000) - (1497, bw_delay=0.000000, notch_delay=0.000000)
  lora_pkt_fwd[4286]: [LGWSEND]lgw_send done: count_us=3537314420, freq=923300000, size=17
++)))
--
--**3)** and the end node will got:
++(% class="box" %)
++(((
++3) and the end node will got:
  [5764825]~*~*~*~** UpLinkCounter= 98 ~*~*~*~**
  [5764827]TX on freq 905300000 Hz at DR 0
  Update Interval: 60000 ms
@@ -247,9 +247,11 @@
  Rssi= -41
  Receive data
  (% style="color:#037691" %)**2:12345678**  (%%)  ~-~-> Hex
++)))
--
--**4) **If we use the command "echo 2602111D,time,txt,12345678 > /var/iot/push/test" for downstream, the end node will got:
++(% class="box" %)
++(((
++4) If we use the command "echo 2602111D,time,txt,12345678 > /var/iot/push/test" for downstream, the end node will got:
  [5955877]~*~*~*~** UpLinkCounter= 102 ~*~*~*~**
  [5955879]TX on freq 904100000 Hz at DR 0
  Update Interval: 60000 ms
@@ -264,15 +264,13 @@
  )))
--
  = 3. Example 1: Communicate with LT-22222-L =
--
  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]]
  (% class="box" %)
  (((
--//#!/bin/sh
++#!/bin/sh
  # This scripts shows how to use LPS8/LG308/DLOS8 to communicate with two LoRaWAN End Nodes, without the use of internet or LoRaWAN server
  #
  # Hardware Prepare:
@@ -305,45 +305,41 @@
  #  Device1: DI1: ON, DI2: ON , DO1: ON,  DO2: ON
  #  Device2: DI1: OFF, DI2: OFF , DO1: ON,  DO2: ON
  #  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
--#  whether the Device 2 has been changed.//
++#  whether the Device 2 has been changed.
  )))
++~1. Input keys
--**~1. Input keys**
--
  [[image:image-20220527162450-3.png]]
  Input Keys in LPS8
--**2. Make sure the LPS8 and LT use the same frequency bands, choose EU868 in this test.**
++2. Make sure the LPS8 and LT use the same frequency bands, choose EU868 in this test.
++3. Choose Built-in server
--**3. Choose Built-in server**
--
  [[image:image-20220527162518-4.png]]
  Choose Built-in server
--**4. Run the script.**
++4. Run the script.
--[[image:image-20220722115213-2.png]]
++[[image:image-20220527162552-5.png]]
  Run the script
--**5. Output:**
++5. Output:
--[[image:image-20220722115133-1.png]]
++[[image:image-20220527162619-6.png]]
  Output from LPS8
--
  = 4. Example 2: Communicate to TCP Server =
--
  [[image:image-20220527162648-7.png]]
  Network Structure
@@ -357,7 +357,6 @@
  (% style="color:red" %)**Note: Firmware version must be higher than lgw-5.4.1607519907**
--
  Assume we already set up ABP keys in the gateway:
  [[image:image-20220527162852-8.png]]
@@ -365,9 +365,8 @@
  Input Keys in LPS8
++run socket tool in PC
--**run socket tool in PC**
--
  [[image:image-20220527163028-9.png]]
@@ -374,20 +374,17 @@
  Socket tool
++Input Server address and port
--**Input Server address and port**
--
  [[image:image-20220527163106-10.png]]
  Input Server address and port
++See value receive in socket tool. :
--**See value receive in socket tool:**
++[[image:https://wiki.dragino.com/images/thumb/2/20/LPS8_TCP_4.png/600px-LPS8_TCP_4.png||height="219" width="600"]]
--[[image:image-20220527163144-11.png]]
--
  value receive in socket tool
--
  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.

image-20220722115133-1.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-35.1 KB

Content

image-20220722115213-2.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-27.7 KB

Content

Changes for page Communicate with ABP End Node without LoRaWAN Network Server --- LG308

Summary

Details

Applications

Navigation