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