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