Wiki source code of Communicate with ABP End Node on the LPS8-V2 Gateway
Last modified by Xiaoling on 2024/08/19 15:29
Show last authors
author | version | line-number | content |
---|---|---|---|
1 | (% class="wikigeneratedid" %) | ||
2 | **Table of Contents:** | ||
3 | |||
4 | {{toc/}} | ||
5 | |||
6 | |||
7 | |||
8 | |||
9 | = 1. Introduction = | ||
10 | |||
11 | |||
12 | The LPS8-V2 of Dragino LoRaWAN gateway can communicate with LoRaWAN ABP End Node, the working is based on the built-in server TTN-Stack. | ||
13 | |||
14 | |||
15 | **It can be used in some cases such as:** | ||
16 | |||
17 | * No internet connection. | ||
18 | * Users want to get data forward in the gateway and forward it to their server based on MQTT/HTTP. | ||
19 | * Forward the data to the built-in Application server Node-Red. | ||
20 | * Just storing the data on the gateway or external storage | ||
21 | |||
22 | |||
23 | **The basic of this feature is the decoding of** (% style="color:blue" %)**LoRaWAN ABP End Node**(%%). **Requirements:** | ||
24 | |||
25 | 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 | ||
26 | 1. LoRaWAN Gateway model: LPS8-V2 | ||
27 | 1. System version: Since V.12 | ||
28 | |||
29 | |||
30 | |||
31 | = 2. Quick Start = | ||
32 | |||
33 | |||
34 | The default factory version of LPS8-V2 is installed with the Built-in LoRaWAN Server: (% style="color:blue" %)**The Things Network - Stack (Open Source 3.19 Version).** | ||
35 | |||
36 | Once the gateway is DHCP an IPV4 address, and then you can access the build-in server TTN-Stack. | ||
37 | |||
38 | |||
39 | == 2.1. Configure the gateway mode == | ||
40 | |||
41 | |||
42 | You can access the gateway's Manage Web UI, via the URL ( (% style="color:blue" %)__**//http:~/~/<hostname> or http:~/~/<local-IPV4-address> //**__(%%)) in your browser | ||
43 | |||
44 | |||
45 | === (% style="color:#037691" %)**Selecting the right frequency band**(%%) === | ||
46 | |||
47 | |||
48 | [[image:image-20220802142103-1.png]] | ||
49 | |||
50 | |||
51 | === (% style="color:#037691" %)**Configure the Semtech UDP forwarder**(%%) === | ||
52 | |||
53 | |||
54 | [[image:image-20220802142147-3.png]] | ||
55 | |||
56 | |||
57 | == 2.2. Login to the built-in server TTN-Stack == | ||
58 | |||
59 | |||
60 | You can access the gateway's built-in server of (% style="color:blue" %)**The Things Network - Stack **(%%)via the URL( __**//http:~/~/<hostname>:8080 or http:~/~/<local-IPV4-address:8080> //**__) in your browser. | ||
61 | |||
62 | Such as __**//http:~/~/dragino-54ff12:8080 or [[http:~~/~~/<Local-IPV4-Address~>>>http://<Local-IPV4-Address>]]//**__ | ||
63 | |||
64 | |||
65 | **Login account:** | ||
66 | |||
67 | (% style="background-color:yellow" %)**User ID: ** ** admin** | ||
68 | |||
69 | (% style="background-color:yellow" %)**Password: ** ** dragino** | ||
70 | |||
71 | |||
72 | [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20All%20Gateway%20models/HP0C/WebHome/image-20220725171719-1.png?width=769&height=570&rev=1.1||alt="image-20220725171719-1.png"]] | ||
73 | |||
74 | |||
75 | == 2.3. Add the gateway & the sensor == | ||
76 | |||
77 | |||
78 | Here only show the image of the finish, more details about how to add the gateway & sensor refer to this wiki: | ||
79 | |||
80 | |||
81 | === (% style="color:#037691" %)**Add the gateway**(%%) === | ||
82 | |||
83 | |||
84 | [[image:image-20220802142946-5.png]] | ||
85 | |||
86 | |||
87 | === (% style="color:#037691" %)**Add the Sensor**(%%) === | ||
88 | |||
89 | |||
90 | [[image:image-20220802143031-6.png||height="794" width="1375"]] | ||
91 | |||
92 | |||
93 | == 2.4. Add the decoder == | ||
94 | |||
95 | |||
96 | If you use dragino sensors then you can find the recorder on this URL: | ||
97 | |||
98 | |||
99 | [[image:image-20220802143129-7.png]] | ||
100 | |||
101 | |||
102 | == 2.5. Visual Data == | ||
103 | |||
104 | |||
105 | In this section, you can be seen that the payload of the sensor has been interpreted as visual data. | ||
106 | |||
107 | And the next part will discuss where to let the data flow。 | ||
108 | |||
109 | |||
110 | [[image:image-20220802143214-8.png]] | ||
111 | |||
112 | |||
113 | = 3. Forward the data or store the data = | ||
114 | |||
115 | |||
116 | You are done most of the work, now you just need to plan the flow of data to where. | ||
117 | |||
118 | |||
119 | == 3.1 Forward data to an external server based on MQTT/HTTP. == | ||
120 | |||
121 | |||
122 | === (% style="color:blue" %)**MQTT**(%%) === | ||
123 | |||
124 | |||
125 | You need to connect to this public address on your external server and subscribe to the topic (% style="color:#037691" %)**(v3/<application_name>/devices/<devices_name>/up)**. | ||
126 | |||
127 | |||
128 | [[image:image-20220802144754-9.png]] | ||
129 | |||
130 | |||
131 | (% style="color:#037691" %)**subscribe to the topic and get the data** | ||
132 | |||
133 | [[image:image-20220802145408-10.png]] | ||
134 | |||
135 | |||
136 | |||
137 | === (% style="color:blue" %)**HTTP**(%%) === | ||
138 | |||
139 | |||
140 | [[image:image-20220802145450-11.png||height="676" width="1164"]] | ||
141 | |||
142 | |||
143 | == 3.2 Forward data to the built-in application server Node-Red. == | ||
144 | |||
145 | |||
146 | [[image:image-20220802150715-1.png||height="739" width="1171"]] | ||
147 | |||
148 | |||
149 | == 3.3 Just storing the data on the gateway or external storage. == | ||
150 | |||
151 | |||
152 | Data can be stored or read by subscribing to topics: (% style="color:#037691" %)**v3/<application_name>/devices/<devices_name>/up**. | ||
153 | |||
154 | Then add the storage node (% style="color:#037691" %)**(write file)**(%%), Users can download the Node-Red flowchart from this link to test data storage:[[attach:test_data_storage.json||target="_blank"]] | ||
155 | |||
156 | After the configuration is complete, users can find the node logs in the root/ directory | ||
157 | |||
158 | |||
159 | [[image:image-20220806153310-11.png||height="588" width="1166"]] | ||
160 | |||
161 | |||
162 | [[image:image-20220806153112-9.png||height="575" width="1167"]] | ||
163 | |||
164 | |||
165 | [[image:image-20220806153048-8.png||height="608" width="1165"]] | ||
166 | |||
167 | |||
168 | [[image:image-20220806153150-10.png]] | ||
169 | |||
170 | |||
171 | = 4. Sent the downlink to the sensor = | ||
172 | |||
173 | |||
174 | Downlinks can be scheduled by publishing the message to the topic (% style="color:#037691" %)** v3/<application_name>/devices/<devices_name>/down/push**. | ||
175 | |||
176 | |||
177 | (% style="color:red" %)**Note**: **Remember that the format of this topic for The Things Stack Open Source deployment would be (v3/<application_name>/devices/<devices_name>/down/push).** | ||
178 | |||
179 | |||
180 | [[MQTT Server ~| The Things Stack for LoRaWAN (thethingsindustries.com)>>url:https://www.thethingsindustries.com/docs/integrations/mqtt/]] | ||
181 | |||
182 | |||
183 | Instead of /push, you can also use /replace to replace the downlink queue. Replacing with an empty array clears the downlink queue. | ||
184 | |||
185 | Example: | ||
186 | |||
187 | (% class="box" %) | ||
188 | ((( | ||
189 | { | ||
190 | "downlinks": [{ | ||
191 | "f_port": 2, | ||
192 | "frm_payload": "AwAA", | ||
193 | "priority": "HIGH", | ||
194 | "confirmed": true | ||
195 | }] | ||
196 | } | ||
197 | ))) | ||
198 | |||
199 | [[image:image-20220802170358-4.png||height="656" width="898"]] | ||
200 | |||
201 | |||
202 | [[image:image-20220802164844-3.png||height="345" width="1131"]] | ||
203 | |||
204 | |||
205 | (% style="color:blue" %)**Node-red** | ||
206 | |||
207 | Users can download the Node-Red flowchart for testing [[attach:mqtt-test.json||target="_blank"]] | ||
208 | |||
209 | |||
210 | [[image:image-20220802172021-6.png||height="455" width="1240"]] | ||
211 | |||
212 | |||
213 | = 5. Trouble Shootings = | ||
214 | |||
215 | |||
216 |